Method and apparatus for generating and utilizing user plane-related information in mobile communication network system

The NWDAF entity in 5G systems collects and analyzes user plane information to enhance network performance by optimizing traffic patterns and processing operations, addressing inefficiencies in existing systems.

WO2026235521A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096731
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-08
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face challenges in efficiently managing and optimizing user plane-related information collection and analysis, which is crucial for enhancing network performance and supporting diverse services, especially as the number of connected devices increases.

Method used

A method involving a network data analytics function (NWDAF) entity that receives analytics service requests, determines a session management function (SMF) entity, and collects user plane information to improve traffic patterns and processing operations, utilizing transceivers, processors, and memory to transmit service request messages.

Benefits of technology

Enables improved network performance by optimizing traffic patterns and processing specific packets, facilitating better management of user plane operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096731_12112026_PF_FP_ABST
    Figure KR2026096731_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. According to an embodiment of the present disclosure, a method performed by a network data analytics function (NWDAF) entity may comprise the steps of: receiving, from a network function (NF) entity, an analytics service request message including an analytics identifier; on the basis of the analytics service request message, determining a session management function (SMF) entity related to payload header handling; and transmitting, to the determined SMF entity, a service request message for requesting information collection.
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for generating and utilizing user plane-related information in a mobile communication network system

[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure proposes a method for supporting a user plane-related information collection and analysis service in a mobile communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz (THX) band (e.g., the 3 terahertz band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

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

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The purpose of the present disclosure is to propose a method for collecting information related to a user plane within a mobile communication system and providing an analysis service to a network function based thereon.

[0009] According to one embodiment of the present disclosure, a method performed by a network data analytics function (NWDAF) entity in a wireless communication system may include the steps of: receiving an analytics service request message including an analytics identifier from a network function (NF) entity; determining a session management function (SMF) entity related to payload header handling based on the analytics service request message; and transmitting a service request message to the determined SMF entity to request information collection.

[0010] Meanwhile, according to another embodiment of the present disclosure, a network data analytics function (NWDAF) entity in a wireless communication system may include at least one transceiver, at least one processor connected to communicate with the at least one transceiver, and a memory that stores an instruction to transmit a service request message containing an analytics identifier from a network function (NF) entity through the at least one transceiver, determine a session management function (SMF) entity related to payload header handling based on the analytics service request message, and transmit a service request message to the determined SMF entity to request information collection.

[0011] According to one embodiment of the present disclosure, new information related to a packet transmitted through a user plane is obtained, thereby enabling improvement and adjustment of traffic patterns and the operation of processing a specific packet in a network device of the user plane.

[0012] FIG. 1 is a diagram showing a 5G system structure supporting NWDAF according to one embodiment of the present disclosure.

[0013] FIG. 2 is a sequence diagram illustrating a method for collecting user plane data-related information according to one embodiment of the present disclosure.

[0014] FIG. 3 is a sequence diagram illustrating a method for registering an NWDAF that supports user plane-related analytics and an NF that supports a payload header handling function according to one embodiment of the present disclosure.

[0015] FIG. 4 is a block diagram of a terminal or user equipment according to one embodiment of the present disclosure.

[0016] FIG. 5 is a block diagram of a base station according to one embodiment of the present disclosure.

[0017] FIG. 6 is a block diagram of a network entity performing network functions according to one embodiment of the present disclosure.

[0018] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0019] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0020] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same or different reference numbers.

[0021] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0022] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0023] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.

[0024] As used in the embodiments of the present disclosure, the term “part” refers to a software or hardware component, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part” performs certain roles. However, the term including “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run on one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” In addition, the components and 'parts' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0025] As stated above, it should be noted that the blocks of each flowchart and combinations of flowcharts described in this disclosure may be executed by one or more computer programs including instructions. The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.

[0026] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors is a circuitry that performs processing and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry.

[0027] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0028] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), and said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed alone or collectively by one or more processors of an electronic device.

[0029] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program containing code for implementing a device or method according to any one of the claims of this specification, and a non-transient machine-readable storage medium storing such program.

[0030] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0031] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0032] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0033] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0034] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0035] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0036] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0037] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.

[0038] Furthermore, throughout this specification, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or essentially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same magnitude measured or applied in different situations, or may represent different magnitudes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the specification and claims.

[0039] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.

[0040] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.

[0041] Furthermore, the expressions 'if' and 'in case that' described in this disclosure or claims may be interpreted, depending on the context, as meaning 'when or upon,' 'in response to,' 'based on,' or 'according to,' and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes, provided that they do not impair the technical features of this disclosure.

[0042] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.

[0043] Additionally, the phrase "transmitting a message containing A and B" as described in this specification may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.

[0044] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.

[0045] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the circumstances presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.

[0046] The drawings or flowcharts described below illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.

[0047] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.

[0048] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they may be understood by interchangeably, substituted, or combined.

[0049] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in the 3GPP (3rd generation partnership project) Technical Specifications (TS).

[0050] Hereinafter, the base station, as the entity performing resource allocation for terminals, may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on a network. Additionally, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for wireless resource processing of the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU as described above.

[0051] The terminal may include a UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions.

[0052] In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station.

[0053] In addition, while a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0054] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."

[0055] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, ...), RRC (radio resource control), MAC (medium access control), CE (control element), NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0056] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI (downlink control information), a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.

[0057] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0058] The operating principle of the present disclosure will be explained in detail below with reference to the attached drawings.

[0059] FIG. 1 is a diagram showing a 5G system structure supporting NWDAF according to one embodiment of the present disclosure.

[0060] A 5G system architecture supporting NWDAF may include various network functions (NF), and FIG. 1 illustrates some of these, including an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), an application function (AF), unified data management (UDM), a data network (DN), a user plane function (UPF), a (radio) access network ((R)AN), and user equipment (UE).

[0061] Each NF can support the following functions.

[0062] - AMF provides functions for connectivity and mobility management at the UE level, and each UE can be connected to one AMF by default.

[0063] - DN may refer to a network outside the 5GS where, for example, operator services, internet access, or third-party services exist. DN can transmit downlink protocol data units (PDUs) to the UPF or receive PDUs transmitted from the UE from the UPF.

[0064] - The PCF can receive information about packet flows from the application server and provide functions for determining policies such as mobility management and session management. Specifically, the PCF can support functions such as supporting a unified policy framework to control network behavior, providing policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce policy rules, and implementing a front end to access relevant subscription information within the user data repository (UDR) for policy decisions.

[0065] - SMF provides session management functions, and if a UE has multiple sessions, each session can be managed by a different SMF.

[0066] - UDM can store user sign-up data, policy data, etc.

[0067] - The UPF can forward downlink PDUs received from the DN to the UE via the (R)AN, and forward uplink PDUs received from the UE to the DN via the (R)AN. The UPF can identify or detect packet header information (or payload header information) and report the relevant information to the SMF or NWDAF. Based on payload header handling control information received from the SMF, the UPF can detect packet header information of specific traffic or add information to the header of a specific packet.

[0068] - AF can interact with the 3GPP core network to provide services (e.g., support for functions such as application impact on traffic routing, access to network capability exposure, and interaction with policy frameworks for policy control).

[0069] - NWDAF includes at least one of an analytics logical function (AnLF) and a model training logical function (MTLF) and can collect data within a 5G system and provide analytics services based on the collected data. For example, it can train a machine learning model based on the data and provide analysis data necessary for network operation and behavior based on the trained model.

[0070] - The NEF (network exposure function) acts as a relay for services provided by 3GPP network functions between the inside and outside of the 3GPP network. Additionally, through the NEF, information or parameters provided by external application functions can be configured for 3GPP internal network functions.

[0071] The present invention proposes a method for collecting information related to a user plane within a mobile communication system and providing an analysis service to a network function based thereon. Specifically, the invention proposes a method for obtaining header information of a packet transmitted through a user plane within a mobile communication system and a method for supporting a network analysis service through said information.

[0072] FIG. 2 is a sequence diagram illustrating a method for collecting user plane data-related information according to one embodiment of the present disclosure.

[0073] As a step prior to specifically performing the method for collecting user plane data-related information described in FIG. 2, a Consumer NF (200) (e.g., PCF or SMF) or OAM device may transmit an NF discovery request message to an NRF (not shown) containing at least one of the following information in order to search for and discover an NWDAF (201) that supports user plane traffic analysis or user plane packet handling-related analytics service.

[0074] - Analytics ID Information: Analytics ID corresponding to user plane traffic analysis or user plane packet handling analytics

[0075] - Information including DNN or S-NSSAI for a request to analyze user plane traffic of a specific PDU session

[0076] - S-NSSAI information or network slice instance ID information for specifying a particular slice

[0077] - Area of ​​interest: e.g., TAI (tracking area ID), Cell ID, civic address, geological area information (regional information consisting of GPS coordinate values)

[0078] - Time of interest: The time zone subject to analysis (for example, it can be specified by two time stamp values ​​or expressed as an index designating the time zone.)

[0079] - Terminal information: UE identifier, UE group identifier, subscriber category information, or any UE (any terminal that can be identified by a combination of DNN or S-NSSAI)

[0080] An NRF that has received at least one of the above information may provide address information for an NWDAF (201) that supports user plane traffic analysis or user plane packet handling-related analytics services to a consumer NF (200) by taking into account the received information. In order to support discovery and selection operations for such an NWDAF (201) that supports user plane traffic analysis or user plane packet handling-related analytics services, information about the NWDAF (201) may need to be registered in the NRF. Related detailed operations will be described later in FIG. 3.

[0081] In step S210, the Consumer NF (200) (e.g., PCF or SMF) or OAM device may call the Nnwdaf_AnalyticsInfo service to request an analytics service from NWDAF (201) and send an analytics service request message containing at least one of the following information.

[0082] - Analytics ID Information: Analytics ID corresponding to user plane traffic analysis or user plane packet handling analytics

[0083] - Information including DNN or S-NSSAI for a request to analyze user plane traffic of a specific PDU session

[0084] - S-NSSAI information or network slice instance ID information for specifying a particular slice

[0085] - Header information for requesting traffic analysis information for packets on a specific user plane that contain specific payload header information

[0086] - Protocol information for requesting analysis information regarding packets being transmitted and received using a specific user plane protocol (e.g., information that can identify protocols such as TCP, UDP, RTP)

[0087] - Area of ​​interest: e.g., TAI (tracking area ID), Cell ID, civic address, geological area information (regional information consisting of GPS coordinate values)

[0088] - Time of interest: The time zone subject to analysis (for example, it can be specified by two time stamp values ​​or expressed as an index designating the time zone.)

[0089] - Terminal information: UE identifier, UE group identifier, subscriber category information, or any UE (any terminal identifiable by a combination of DNN or S-NSSAI)

[0090] - Specific NF information: Information including at least one of NF name, NF identifier, NF type, NF instance ID, and NF address information, which can be used to collect data related to a specific SMF or UPF involved in user plane packet processing.

[0091] - Application ID: An identifier for a specific application, which may be set to a value corresponding to information for identifying or detecting the traffic of the application (e.g., packet filter information such as an IP address or port number).

[0092] - Application server IP address / FQDN: May contain information related to the endpoint address of a specific application server.

[0093] - Packet filter information (or service data flow template information, packet filter description, or traffic description): May include information that can be used to detect or identify specific packets.

[0094] - Expected report time: Information on when results for the analytics service are expected to be provided (can be used as information indicating when NWDAF should report analytics out to the consumer NF)

[0095] - Reporting threshold for signaling frequency threshold: Information that can be used to obtain analysis or statistical results regarding the frequency of signaling related to the user plane. It can be used to configure NWDAF to report this information to the consumer NF when the frequency of signaling related to the user plane exceeds a specific threshold.

[0096] - User plane event information: Information that can be used to request analytics for specific events related to the user plane. For example, information on whether an event has occurred that processes the header information of a user plane packet.

[0097] In relation to step S210, if the consumer NF (200) is a PCF according to one embodiment, the conditions under which the PCF requests an analytics service for user plane traffic analysis or user plane packet handling analytics provided by the NWDAF (201) may be, for example, as follows (for example, the analytics service may be requested based on a condition formed by at least one of the following conditions or a combination of multiple conditions below).

[0098] - When an update notification regarding information related to terminal session management (application data or subscription data) is received from the UDR

[0099] - If the carrier policy or local configuration set within the PCF is configured to be referenced when creating or updating the session management policy

[0100] - When creating or modifying a session management policy for a specific DNN or S-NSSAI or a combination of both (e.g., when a PDU session that can be identified by a specific DNN or S-NSSAI is created or modified, or when a request to create or modify a session management policy association is received from the SMF for a PDU session that can be identified by a specific DNN or S-NSSAI, etc.)

[0101] - When creating or modifying session management policies for a specific application or service

[0102] In step S220, NWDAF (201) can perform the following operation to select an NF to collect data from by considering the information included in the analytics service request message received from the consumer NF (200).

[0103] - Using the NF ID, NF name, and NF type received through step S210, NWDAF (201) can request information about the data source NF from NRF.

[0104] - Using information that can identify a PDU session such as a DNN, S-NSSAI, received through step S210, NWDAF (201) can send a request for information to the NRF for the SMF (203) or UPF (204) to discover / select the SMF managing the PDU session or the UPF transmitting the PDU session traffic.

[0105] - When NWDAF (201) receives information regarding a request for analysis information related to header information for requesting traffic analysis information for packets having specific payload header information among packets on a specific user plane received through step S210, or protocol information for requesting analysis information for packets being transmitted and received using a specific user plane protocol (e.g., information that can identify protocols such as TCP, UDP, RTP), NWDAF (201) can send a request to NRF to search for and select a UPF (204) that supports payload header handling functions or an SMF (203) that manages a UPF (204) performing payload header handling operations (e.g., an SMF that supports payload header handling functions).

[0106] - When NWDAF (201) receives information regarding a request for analysis information related to header information for requesting traffic analysis information for packets having specific payload header information among packets on a specific user plane received through step S210, or protocol information for requesting analysis information for packets being transmitted and received using a specific user plane protocol (e.g., information that can identify protocols such as TCP, UDP, RTP), NWDAF (201) can send a request to NRF or SMF (203) to search for and select a UPF (204) that supports payload header handling functions or a UPF (204) that is performing payload header handling operations.

[0107] - When an analysis information request is received that includes both information regarding an analysis information request related to header information for requesting traffic analysis information for packets having specific payload header information among packets on a specific user plane received through step S210, or protocol information for requesting analysis information for packets being transmitted and received using a specific user plane protocol (e.g., information that can identify protocols such as TCP, UDP, RTP), and information that can identify a specific terminal (e.g., terminal identifier), NWDAF (201) may request information from UDM regarding an SMF (203) that manages the PDU session for the terminal (or an SMF that manages the SM context of the terminal, or an SMF that has registered information regarding a specific PDU session of the terminal) in order to find the SMF (203) that is performing session management for the terminal. When NWDAF (201) requests information related to the SMF (203) from UDM to perform this operation, it may provide terminal identifier, DNN, and S_NSSAI information. NWDAF (201) may include at least one of the terminal identifier, DNN, and S_NSSAI information in the message that calls the Nudm_UECM service to perform the above operation.

[0108] Through at least one of the above operations, NWDAF (201) can receive at least one of the SMF address and identifier information from NRF or UDM. Or, through at least one of the above operations, NWDAF (201) can receive at least one of the UPF address and identifier information from NRF or SMF (203).

[0109] In step S230, NWDAF (201) may request that the relevant SMF (203) collect and transmit related information based on the SMF information obtained in the above-described step, while providing the information received from the consumer NF (200) in step S210. For example, NWDAF (201) may transmit to SMF (203) at least one of the following information within an SMF event exposure service request message: application id, DNN, S_NSSAI, event ID (e.g., information such as user data usage measures, user data usage trends, user data packet handling record, packet handling trend, etc.), packet filter information, Target payload header info, Target protocol info, Reporting window (reporting urgency info indicate delay tolerant), and the last valid reporting time.

[0110] According to one embodiment of the present disclosure, the event exposure service request message to the SMF (203) may be provided with at least one of the information above and the information in Table 1 below.

[0111] InformationUE identificationAny UEDNNS-NSSAIAOIBSSID / SSIDDNAIUPF IdType of MeasurementGranularity of MeasurementApplication IDTraffic Filtering InformationReporting suggestion informationRemaining data reporting indicationTarget payload header info, Target protocol info

[0112] In step S240, when SMF (203) receives a data collection and transmission request from NWDAF (201), it can send a data collection and reporting request to UPF (204) by taking into account the information contained in the message received through step S230.

[0113] SMF (203) can transmit at least one of the following information to UPF (204) by taking into account the information included in the data collection and transmission request from NWDAF (201).

[0114] - Traffic Filtering Information,- Target payload header info, Target protocol info

[0115] - Packet handling control information

[0116] Header Detection ReferenceA reference to a UPF configuration which defines how to detect the protocol or the message in a protocol for which to perform the header handling actions.Header Handling Reporting EndpointNotification endpoint, i.e. per notification endpoint a Notification Target Address and a Notification Correlation ID.Header Handling Control ReferenceA reference to a Header Handling Action related information pre-configured in the UPF.Header Handling DirectionIndicates if the header handling applies to UL or DL direction.Header Handling ActionIndicates the action to be performed on a specific header field.Header InformationA reference to a UPF configuration which defines how to identify or build a specific header field for which to perform the header handling action.Header ValueA string providing the value (or a reference to information to be provided by SMF) of the specific header field.Header Handling ConditionIndicates the condition for performing the header handling actionHeader Handling ReportingIndicates whether reporting is requested for the performed Header Handling Action.

[0117] SMF (203) can set values ​​corresponding to each parameter of Table 2 above by considering information received from NWDAF (201) and perform the operation of setting them to UPF (204). According to one embodiment, the operation of setting the information to UPF (204) can be performed through an N4 session establishment / modification procedure, an N4 association-related procedure, or a UPF event exposure subscription procedure.

[0118] SMF (203) can choose one of the methods in which data collected by UPF (204) is transmitted to SMF (203) or transmitted to NWDAF (201) without passing through SMF (203), depending on the operator policy or local configuration. And depending on the selected transmission path, SMF (203) can send to UPF (204) by setting the notification target address to the address of SMF (203) or NWDAF (201) that sent the data collection request to SMF (203).

[0119] In step S250, the SMF (203) may send a message to the NWDAF (201) indicating that the event exposure request has been successfully processed. According to one embodiment, the message may include at least one piece of information such as a subscription correlation ID and a notification correlation ID for the event exposure.

[0120] In step S260, the UPF (204) can collect data based on information received through the SMF (203). The collected data may include at least one of the information disclosed in Table 3.

[0121] InformationUE identificationDNNS-NSSAIDNAIUPF IdType of MeasurementGranularity of MeasurementApplication IDTraffic Filtering InformationTarget payload header info, Target protocol infoPacket handling event (packet buffered, packet dropped or packet loss occurrence)

[0122] In step S270, if the report conditions included in the information received from the SMF (203) are satisfied, the UPF (204) can transmit the data collected through the operation of step S260 to the notification target (e.g., SMF (203) or NWDAF (201)) set through step S240. In this embodiment, an example in which the UPF (204) transmits directly to the NWDAF (201) is described.

[0123] In step S280, NWDAF (201) may generate analytics results using information collected from UPF (204). The analytics results may include analysis results regarding packets with a specific payload header set, packets transmitted or received through a specific protocol, or traffic flows consisting of such packets, and may provide analysis results associated with at least one of the information disclosed in Table 4 below. According to one embodiment, NWDAF (201) may generate statistical information from UPF (204) regarding how packets having specific payload header information were processed by UPF (204) for a specific terminal's PDU session. NWDAF (201) may obtain statistics regarding the transmitted and received data volume of packets having specific payload header information transmitted or received within the specific terminal's PDU session, the degree of buffering by UPF (204), and how often packet drops or packet losses occurred for such packets at UPF (204).

[0124] According to another embodiment, NWDAF (201) can generate statistical information on how many pack drops or packet losses have occurred for a specific terminal's PDU session or specific application service traffic. NWDAF (201) can also generate statistical information including information on what packet header information the packets that actually experienced drops or losses have.

[0125] [Table 4]

[0126]

[0127] According to one embodiment of the present disclosure, NWDAF can collect data from UPF, SMF, or OAM and provide user plane-related analysis information as shown in Table 5 below.

[0128] [Table 5]

[0129]

[0130] According to one embodiment of the present disclosure, the analytics information that NWDAF (201) can generate may include parameters indicating that a specific event is detected or inferred, as disclosed in Table 5 above. For example, NWDAF (201) may determine that a large amount of packets or traffic corresponding to specific transport protocol information has occurred based on information obtained from SMF (203), UPF (204), or OAM (not shown), and that a specific event has been detected based on the header information of each packet collected for the traffic corresponding to the transport protocol information, and include this in the analytics information. For example, NWDAF (201) may collect the amount of packets or traffic transmitted and received via TCP and the header information of the TCP packets (e.g., SYN flag information or information indicating that it is a SYN packet in the header) from SMF (203) or UPF (204), and detect that an abnormally large amount of SYN packets are being transmitted and received. NWDAF (201) can notify NF that sent an analysis request to NWDAF (201) that TCP SYN flooding is occurring based on the analysis information from this data collection.

[0131] In step S290, NWDAF (201) can provide the analytics information generated in the aforementioned step S280 to the consumer NF (200).

[0132] In step S291, if the Consumer NF (200) is an SMF (203) or a PCF, adjustments to the session management policy or updates to the user plane packet handling rule can be performed by taking into account the corresponding NWDAF analytics information.

[0133] For example, if the packet drop ratio or packet loss rate of a packet containing specific payload header information received through step S290 is greater than a certain value, a decision may be made to relax or exclude the application of rate limit control or gating control to that packet.

[0134] In step S292, the Consumer NF (200) may transmit an SM Policy association Modification to the SMF (203). The SM Policy association Modification may include a Header Handling Control rule. According to one embodiment of the present disclosure, the Header Handling Control rule may be header handling control information including at least one of an exemption rule and / or header handling reporting information.

[0135] FIG. 3 is a sequence diagram illustrating a method for registering an NWDAF that supports user plane-related analytics and an NF that supports a payload header handling function according to one embodiment of the present disclosure.

[0136] Specifically, FIG. 3 is a sequence diagram showing the procedure for registering functions related to NRF (303) to support discovery and selection for NWDAF (300) supporting user plane-related analytics and NF (e.g., SMF (301), UPF (302)) supporting payload header handling functions.

[0137] In step S310, if NWDAF (300) supports user plane traffic analysis or user plane packet handling analytics, it may send a registration request message to NRF (303) that includes at least one of the associated Analytics ID information, NWDAF address information, and identifier. According to one disclosure, NWDAF (300) may send a register analytics ID for UP packet handling analytics to NRF (303).

[0138] In step S320, NRF (303) can successfully store the information received from NWDAF (300). And NRF (303) can send a response message to the registration request to NWDAF (300).

[0139] In step S330, if the SMF (301) supports a payload header handling function, it may transmit a registration message to the NRF (303) containing at least one of the following: DNN, S-NSSAI, DNAI List, SMF service area information managed by the SMF (301), and information related to the payload header handling capability. For example, the SMF (301) may transmit the register payload header handling capability to the NRF (303).

[0140] In step S340, NRF (303) can successfully store the information received from SMF (301). And NRF (303) can send a response message to the registration request to SMF (301).

[0141] In step S350, if UPF (302) supports payload header handling functionality, UPF (302) may send a registration request message to NRF (303) containing at least one of the following information: UPF location information, DNN, S-NSSAI, whether payload header handling related functions are supported, UE IPv4 Address Ranges and / or IPv6 Prefix Range(s) per (S-NSSAI, DNN), supported UPF event exposure service and supported Event IDs, and support of handling of Payload Headers functionality.

[0142] In step S360, NRF (303) can successfully store the information received from SMF (301). And NRF (303) can send a response message to the registration request to UPF (302).

[0143] In one embodiment of the present invention, the PCF can perform the creation and modification of the following Policy and charging control rule (PCC rule) based on the functions and operations described in FIG. 2 and FIG. 3.

[0144] When the PCF performs gating control or session AMBR application on a PDU session that can be identified by a terminal identifier, a specific DNN, or an S-NSSAI, it may send a user plane packet handling analytics request message to the NWDAF that includes at least one of the terminal identifier, DNN, S-NSSAI, packet filter information, and payload header information. The PCF can make decisions regarding PCC rule creation and adjustment by checking statistical information on how user plane handling was applied to the PDU session identified by the aforementioned information or the application traffic within that session, and what situation the packets of that traffic experienced in the UPF. For example, the PCF may receive statistics from the NWDAF regarding packets containing specific payload header information such as TCP SYN or TCP SYN ACK, and check the packet drop or packet loss rate for TCP SYN packets or TCP ACK packets among the information in the statistics. If the packet drop or packet loss rate for the packets is above a certain condition or is expected to be above that condition, the PCF may generate a PCC rule that includes payload header information capable of distinguishing between TCP SYN packets or TCP ACK packets, and a payload header handling control rule that instructs to exclude packets containing said payload header information from gating control or session AMBR enforcement control. The PCF may transmit the PCC rule containing said payload header handling control rule to the SMF.

[0145] Meanwhile, FIG. 4 is a block diagram of a terminal or user equipment (400) according to one embodiment of the present disclosure.

[0146] The terminal (400) is an electronic device capable of wireless communication and may include user equipment (UE), mobile phones, smartphones, tablets, Internet of Things (IoT) devices having various form factors, and can perform wireless communication with a base station through a wireless channel.

[0147] Referring to FIG. 4, the terminal (400) may include at least one transceiver (401) (hereinafter, transceiver), at least one processor (402) (hereinafter, processor), and at least one memory (403) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (401), processor (402), and memory (403) of the terminal (400) may be operated. However, the components of the terminal (400) are not limited to the examples of components shown in FIG. 4. In other embodiments, the terminal (400) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (401), processor (402), or memory (403) may be integrated into a single component.

[0148] The transceiver (401) may be a basic communication circuit or communication circuitry that enables the terminal (400) to perform wireless communication with a node or entity of a network. For example, the transceiver (401) may enable the terminal (400) to transmit and receive signals to and from a base station via cellular wireless communication, or to transmit and receive signals to and from another terminal via cellular wireless communication. For example, the transceiver (401) may be 3G (3rd generation), 4G (4th generation), LTE (long-term evolution), 5G (5th generation), NR (new radio), 6G (6th It can support at least one of various cellular wireless communication technologies including generation), and the various cellular wireless communication technologies supported by the transceiver (401) may include all subsequent evolved generations of wireless communication.

[0149] According to one embodiment, the terminal (400) may include a plurality of transceivers, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access) - NR dual connectivity), it may include a first transceiver supporting 4G LTE wireless communication and a second transceiver supporting 5G NR wireless communication. According to another embodiment, when the terminal (400) supports NR-DC (NR Dual Connectivity), the terminal (400) may include a plurality of transceivers supporting 5G NR wireless communication. According to another embodiment, if the terminal (400) supports short-range wireless communication, the terminal (400) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).

[0150] According to one embodiment, the transceiver (401) may include various circuit structures used to transmit and receive signals to and from a base station via a wireless channel. The signals may include control information and data. For example, the transceiver (401) may be configured to include a radio frequency (RF) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (401) may output the signal received via the wireless channel to a processor (402) and transmit the signal output from the processor (402) via the wireless channel.

[0151] The processor (402) can control the overall operation of the terminal (400) according to an embodiment of the present disclosure. The processor (402) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (402) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (403) individually, collectively, or in any combination. Additionally, the processor (402) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0152] The processor (402) is electrically, operatively, or communicatively coupled to the transceiver (401) so as to control the transceiver (401).

[0153] The processor (402) may include at least one processor (or, processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (402) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (402) may be included in one chip, and another part of the processor (402) may be included in a separate chip. Alternatively, at least one processor may be included in other components, e.g., a transceiver (401) or a memory (403).

[0154] The processor (402) may perform, cause, or control the operation of a terminal to perform at least one or a combination of the methods according to the embodiments of the present disclosure. For example, the processor (402) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (402) may control other components of the terminal (400) to perform various operations by executing computer programs, code, or instructions stored in memory (403).

[0155] Memory (403) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (403) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0156] The memory (403) can be electrically, operatively, or communically coupled with the processor (402) and can be accessed by the processor (402).

[0157] A computer program, code, or instruction that can be executed by a processor (402) may be stored in the memory (403). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (402) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (402) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (403).

[0158] According to one embodiment of the present disclosure, the operation of the terminal (400) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (403), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0159] FIG. 5 is a block diagram of a base station (500) according to one embodiment of the present disclosure.

[0160] The base station (500) can perform wireless communication with at least one terminal within the area of ​​the base station (500) through a wireless channel.

[0161] Referring to FIG. 5, a base station (500) may include at least one transceiver (501) (hereinafter, transceiver), at least one processor (502) (hereinafter, processor), and at least one memory (503) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (501), processor (502), and memory (503) of the base station (500) may be operated. However, the components of the base station (500) are not limited to the examples of components shown in FIG. 5. In other embodiments, the base station (500) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (501), processor (502), or memory (503) may be integrated into a single component.

[0162] The transceiver (501) may be a communication circuit or communication circuitry that enables the base station (500) to perform wireless communication with a node or entity of the network. For example, the transceiver (501) may enable the base station (500) to transmit and receive signals with a terminal (X00) via cellular wireless communication or to transmit and receive signals with another network entity via wireless communication. For example, the transceiver (501) may be 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation) Various cellular wireless communication technologies, including (generation), etc., can be supported, and the various cellular wireless communication technologies supported by the transceiver (501) may include all subsequent evolved generations of wireless communication. According to one embodiment, the transceiver (501) may include various circuit structures used to transmit and receive signals to and from a terminal through a wireless channel. The signals may include control information and data. For example, the transceiver (501) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (501) may output the signal received through the wireless channel to a processor (502) and transmit the signal output from the processor (502) through the wireless channel.

[0163] Meanwhile, according to one embodiment of the present disclosure, a base station (500) may communicate with an entity or node of a network via wired or wireless communication. For example, the base station (500) may communicate via wired or wireless communication with an entity or node of an adjacent base station or core network via a backhaul network. Although not shown in the drawings, when the base station (500) performs wired communication, the base station (500) may include a separate network interface for wired communication in addition to the transceiver (501). The network interface may be referred to as network interface circuitry, communication interface circuitry, etc.

[0164] The processor (502) can control the overall operation of the base station (500) according to an embodiment of the present disclosure. The processor (502) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (502) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (503) individually, collectively, or in any combination. Additionally, the processor (502) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0165] The processor (502) is electrically, operatively, or communicatively coupled to the transceiver (501) so as to control the transceiver (501).

[0166] The processor (502) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (502) may be included in one chip, and another part of the processor (502) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a transceiver (501) or memory (503).

[0167] The processor (502) may perform, cause, or control the operation of a base station to execute at least one or a combination of methods according to embodiments of the present disclosure. For example, the processor (502) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (502) may control other components of the base station (500) to perform various operations by executing computer programs, codes, and instructions stored in memory (503).

[0168] Memory (503) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (503) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0169] The memory (503) can be electrically, operatively, or communically coupled with the processor (502) and can be accessed by the processor (502).

[0170] A computer program, code, or instruction that can be executed by a processor (502) may be stored in the memory (503). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (502) may be stored in a single memory device or may be separated and distributed among two or more memory devices. The processor (502) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (503).

[0171] According to one embodiment of the present disclosure, the operation of a base station (500) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (503), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions.

[0172] A terminal or a base station can perform various communication procedures related to the control plane or user plane by interacting with network entities based on communication through a wireless channel. For example, a terminal can communicate with network entities such as an access and mobility management function (AMF) or a session management function (SMF) through a base station. Alternatively, the base station can perform at least one communication procedure by directly transmitting and receiving signals or relaying them with network entities. The structure of the above-mentioned network entities will be explained in more detail through the drawings below.

[0173] FIG. 6 is a block diagram of a network entity (600) that performs network functions according to one embodiment of the present disclosure.

[0174] A network entity (600) may include one or more network functions (NF) that constitute a core network (e.g., 5G (5th generation) core, 5GC) in a communication system, or entities (devices, devices, nodes, or servers, etc.) that perform part of a network function. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across multiple network entities. Additionally, when an NF is implemented within a network entity, the NF may be implemented in the form of software, and in such cases, a program for running the NF may be loaded into the memory of the network entity (600).

[0175] A single NF can be implemented as one or more instances and can operate by being distributed across the same network entity or multiple network entities. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.

[0176] The above NF may include any one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0177] Referring to FIG. 6, a network entity (600) may include at least one network interface (601), at least one processor (602) (hereinafter referred to as processor), and at least one memory (603) (hereinafter referred to as memory). As described above, the NF may be implemented in the form of a physical device such as the network entity (600), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as illustrated in FIG. 6. In such cases, the instance may be composed of one or more logical functional units and may be logically represented.

[0178] According to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure, the network interface (601), processor (602), and memory (603) of the network entity (600) may be operated. However, the components of the network entity (600) are not limited to the examples of components shown in FIG. 6. In other embodiments, the network entity (600) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in one embodiment, the network interface (601), processor (602), or memory (603) may be implemented as a single component.

[0179] The network interface (601) is a collective term for the transmitting and receiving parts of a network entity and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or other network entities. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the network interface (601) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network entities via wireless or wired communication. The network interface (601) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol). Depending on the convenience of explanation and technical implementation, the network interface (601) may be referred to as a communication circuitry, a network interface circuitry, or a communication interface circuitry.

[0180] The processor (602) may control the overall operation of the network entity (600) according to an embodiment of the present disclosure. In one embodiment, the processor (602) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (602) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (603) individually, collectively, or in any combination. Additionally, the processor (602) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (602) may not necessarily be composed of physical hardware when the network function (600) is implemented in an instance form according to another embodiment.

[0181] According to one embodiment, the processor (602) is electrically, operatively, or communicatively coupled to the network interface (601) so as to control the network interface (601).

[0182] The processor (602) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (602) may be included in one chip, and another part of the processor (602) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a network interface (601) or memory (603).

[0183] The processor (602) may perform or control the operation of a network entity (600) to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (602) may control the operation of the network entity (600) to exchange control plane messages or user plane messages with terminals, base stations, or other core network entities via wireless or wired communication using various protocols (e.g., NAS protocols). To this end, the processor (602) may control other components of the network entity (600) to perform various operations by executing computer programs, code, or instructions stored in memory (603).

[0184] Memory (603) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (603) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0185] According to one embodiment, the memory (603) may be electrically, operatively, or communically coupled with the processor (602) and may be accessed by the processor (602).

[0186] A computer program, code, or instruction that can be executed by a processor (602) may be stored in the memory (603). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (602) may be stored in a single memory or separated and distributed across two or more memories. The processor (602) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (603).

[0187] According to one embodiment of the present disclosure, the operation of a network entity (600) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (603), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0188] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. A method performed by a network data analytics function (NWDAF) entity in a wireless communication system, A step of receiving an analysis service request message containing an analysis identifier from a network function (NF) entity; A step of determining a session management function (SMF) entity related to payload header handling based on the analysis service request message above; and A method comprising the step of transmitting a service request message to the determined SMF entity to request information collection.

2. In Paragraph 1, The above-mentioned determining step is, If the analysis service request message contains information capable of identifying a protocol data unit (PDU) session, the step of transmitting a request for information regarding an SMF entity associated with the PDU session to a network repository function (NRF) entity; and A method characterized by further including the step of obtaining information associated with the SMF entity from the NRF entity.

3. In Paragraph 1, A method characterized in that the above analysis identifier is an analysis identifier corresponding to user plane traffic analysis or user plane packet handling analysis.

4. In Paragraph 1, A method characterized in that the above service request message includes at least one of target payload header information, target protocol information, reporting window information, and last valid reporting time information.

5. In Paragraph 1, A method characterized by further comprising the step of receiving, when a data collection report and report request is transmitted to a user plane function (UPF) entity by the above SMF entity, a message regarding the completion of an event exposure request including information associated with an event exposure from the above SMF entity.

6. In Paragraph 5, The method further comprises the step of receiving a message from the above UPF entity containing information collected based on the data collection report and report request; and The information collected above is, A method characterized by including information associated with packet loss data.

7. In Paragraph 1, A step of collecting data to obtain analysis information; and The method further includes the step of transmitting the acquired analysis information to the NF entity; A method characterized by the fact that, based on the analysis information, adjustment of the session management policy or update of the user plane packet handling rule is performed by the above NF entity.

8. In the network data analytics function (NWDAF) entity in a wireless communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The NWDAF entity is connected to communicate with at least one processor and is executable individually or in any combination of the at least one processor, so that the NWDAF entity Receiving an analysis service request message including an analysis identifier from a network function (NF) entity through the at least one transceiver, and Based on the above analysis service request message, the session management function (SMF) entity related to payload header handling is determined, and NWDAF entity comprising: memory storing a command to transmit a service request message to request information collection to the above-determined SMF entity.

9. In Paragraph 8, The above memory is, If the analysis service request message above contains information that can identify a protocol data unit (PDU) session, a request for information about the SMF entity associated with the PDU session is sent to the network repository function (NRF) entity, and An NWDAF entity characterized by further storing a command to obtain information associated with the SMF entity from the above NRF entity.

10. In Paragraph 8, An NWDAF entity characterized in that the above analysis identifier is an analysis identifier corresponding to user plane traffic analysis or user plane packet handling analysis.

11. In Paragraph 8, The above service request message is an NWDAF entity characterized by including at least one of target payload header information, target protocol information, reporting window information, and last valid reporting time information.

12. In Paragraph 8, The above memory is, An NWDAF entity characterized by further storing a command to receive, from the SMF entity, a message regarding the completion of an event exposure request including information associated with an event exposure, when a data collection report and report request is transmitted to a user plane function (UPF) entity by the above SMF entity.

13. In Paragraph 12, The above memory is, Further storing a command to receive a message containing information collected based on the data collection report and report request from the above UPF entity, and The information collected above is, NWDAF entity characterized by including information associated with packet loss data.

14. In Paragraph 8, The above memory is, Collect data to obtain analysis information, Further storing a command to transmit the above-mentioned acquired analysis information to the above-mentioned NF entity, and An NWDAF entity characterized by the fact that, by the above NF entity, adjustment of the session management policy or update of the user plane packet handling rule is performed based on the analysis information.