Method and apparatus for managing signaling data in mobile communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the invention discloses a method and a device for collecting, analyzing and managing signaling data between network entities in an edge computing system.

Description

Technical Field

[0001] This disclosure relates to mobile communication systems (or wireless communication systems), and more specifically, to methods and apparatus for collecting and managing signaling data between network devices (or network entities) in a mobile communication system. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands, including 28GHz and 39GHz, known as mmWave. Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz (THz) bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] At the outset of 5G mobile communication technology development, to support services and meet performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization was underway regarding beamforming and massive MIMO. This included mitigating radio wave path loss in millimeter waves and increasing transmission distance; parameter sets supporting dynamic operation (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and time slot formats; initial access technologies to support multi-beam transmission and broadband; the definition and operation of the bandwidth portion (BWP); new channel coding methods such as LDPC (low-density parity-check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and new channel coding methods for transmitting and receiving data. Additionally, network slicing was being developed to provide dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization already exists for technologies such as V2X (Vehicle-to-Everything), NR-U (New Radio Unlicensed), NR UE Power Saving, Non-Terrestrial Network (NTN), and positioning. V2X is used to assist autonomous vehicles in making driving decisions and enhancing user convenience based on vehicle location and status information transmitted by the vehicle. NR-U aims to comply with system operations related to various regulations in unlicensed frequency bands. NR UE Power Saving and Non-Terrestrial Network (NTN) are UE-satellite direct communication used to provide coverage in areas where communication with terrestrial networks is impossible.

[0005] In addition, standardization is underway for air interface architectures / protocols such as those for supporting new services through interoperability and convergence with other industries in the Industrial Internet of Things (IIoT); for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Stack) handover; and for two-step random access (2-step RACH for NR) to simplify the random access process. Standardization is also underway for 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and for system architectures / services for Mobile Edge Computing (MEC) based on UE location reception services.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices will increase exponentially, necessitating enhanced functionality and performance of 5G mobile communication systems, as well as integrated operation of connected devices. To this end, new research related to extended reality (XR) is being undertaken to effectively support AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), and other technologies by leveraging artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication, while also improving 5G performance and reducing complexity.

[0007] Furthermore, this development of 5G mobile communication systems will not only serve as the foundation for developing new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, such as full-dimensional MIMO (FD-MIMO), multi-antenna transmission technologies like array antennas and massive MIMO, metamaterial-based lenses and antennas for improving terahertz band signal coverage, and high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum) and RIS (reconfigurable smart surfaces), but will also serve as the foundation for developing full-duplex technologies to improve the frequency efficiency of 6G mobile communication technology and enhance system networks, AI-based communication technologies to achieve system optimization and internalize end-to-end AI support by leveraging satellites and AI (artificial intelligence) from the design stage, and next-generation distributed computing technologies to deliver services with complexity exceeding the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources.

[0008] Meanwhile, with the evolution of communication systems, the need for effectively managing signaling data between network entities is increasing. Summary of the Invention

[0009] [Technical Issues]

[0010] There is a need for a method to collect signaling-related data that may lead to anomalous network operations during mobile communication network operation. Existing signaling overload control between two directly communicating endpoint network devices is unsuitable for responding to rapid increases in signaling that occur in a cascading manner. For example, when an anomalous situation occurs where the same process is performed for multiple UEs or network functions or devices, signaling for all network functions or devices involved in the process may increase in a cascading manner. Therefore, it may be difficult to reduce signaling through one-to-one overload control between network functions or devices.

[0011] Therefore, this disclosure proposes a scheme that can reduce signaling overload between network entities or network functions by collecting and analyzing network signaling data, thereby achieving effective signaling processing.

[0012] [Technical Solution]

[0013] The method according to embodiments of the present disclosure may include: receiving a first control signal by a first network entity; processing the received first control signal; and sending a second control signal generated based on the processing result to a second network entity.

[0014] [Beneficial Effects]

[0015] According to various embodiments of this disclosure, signaling data between network entities can be collected and analyzed, thereby preventing signaling overload between network entities or network functions. Attached Figure Description

[0016] Figure 1 The structure of the communication system to which this disclosure belongs is shown.

[0017] Figure 2 This illustrates the process by which a network entity collects signaling data according to embodiments presented in this disclosure.

[0018] Figure 3 This illustrates a process by which a network entity collects signaling data from a Serving Communication Agent (SCP) according to embodiments of the present disclosure.

[0019] Figure 4 The process of searching and selecting SCPs to collect signaling data according to embodiments presented in this disclosure is illustrated.

[0020] Figure 5 The structure of a UE according to an embodiment of the present disclosure is shown.

[0021] Figure 6 The structure of a base station according to an embodiment of the present disclosure is shown.

[0022] Figure 7 The structure of a network function (or network entity) according to an embodiment of this disclosure is shown. Detailed Implementation

[0023] In the following, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that, in the drawings, the same or similar elements are represented by the same or similar reference numerals wherever possible. Furthermore, detailed descriptions of known functions or configurations that might obscure the subject matter of the present disclosure will be omitted.

[0024] In describing the embodiments in this specification, descriptions relating to technical content known in the relevant art and not directly related to this disclosure will be omitted. This omission of unnecessary descriptions is intended to prevent obscuring the main ideas of this disclosure and to more clearly convey them.

[0025] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the dimensions of each element do not perfectly reflect its actual size. In all the drawings, the same reference numerals are used to label the same or equivalent elements.

[0026] The advantages and features of this disclosure, as well as methods of implementing them, will become apparent from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

[0027] In this document, it should be understood that each block of the flowchart illustration, and combinations of blocks in the flowchart illustration, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can instruct the computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of writing including instruction means for implementing the functions specified in one or more flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in the flowchart blocks.

[0028] Furthermore, each box in the flowchart can represent a module, segment, or section of code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in the boxes may occur out of order. For example, depending on the functions involved, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order.

[0029] As used in embodiments of this disclosure, the term "unit" refers to a software element or hardware element, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), and a "unit" can perform certain functions. However, "unit" is not always limited to software or hardware. A "unit" can be configured to be stored in addressable storage media or to run one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a "unit" can be combined into a smaller number of elements or "units," or divided into a larger number of elements or "units." Furthermore, elements and "units" can be implemented as one or more CPUs within a playback device or secure multimedia card. Additionally, a "unit" in the embodiments may include one or more processors.

[0030] In the following description, for ease of description, terms for identifying access nodes, referring to network entities, referring to messages, referring to interfaces between network entities, referring to various types of identification information, etc., are used illustratively. Therefore, this disclosure is not limited to the terms described below, and other terms that refer to subjects with equivalent technical meanings may also be used.

[0031] In the following description, for ease of description, terms and names defined in the 3GPP Long Term Evolution (LTE) or New Radio (NR) standards are used. However, this disclosure is not limited to these terms and names and can be applied in the same manner to systems conforming to other standards.

[0032] In the following description, a base station (BS) is an entity that allocates resources to terminals and can be at least one of a radio access network (RAN) node, a next-generation node B (gNode B, gNB), an evolved Node B (eNode B, eNB), a node B, a radio access unit, a base station controller, and a node on a network. In this disclosure, for ease of description, the term "eNB" may be used interchangeably with the term "gNB." That is, a base station described as "eNB" may refer to a "gNB."

[0033] Terminals may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. Of course, examples of base stations and terminals are not limited to those mentioned above.

[0034] In this disclosure, for ease of description, terms referring to network entities or network functions, network nodes and entities of edge computing systems, terms referring to messages, terms referring to identification information, etc., are used illustratively. Therefore, this disclosure is not limited to the terms described below, and other terms referring to subjects with equivalent technical meanings may also be used.

[0035] Specifically, this disclosure can be applied to 3GPP NR (5th generation mobile communication standard). Furthermore, this disclosure can be applied to smart services based on 5G communication technology and Internet of Things (IoT) related technologies (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail businesses, security and safety-related services, etc.). In addition, the term "terminal" can refer not only to mobile phones, NB-IoT devices, and sensors, but also to any other wireless communication device.

[0036] Wireless communication systems are evolving towards broadband wireless communication systems, using communication standards such as 3GPP High-Speed ​​Packet Access (HSPA), LTE (Long Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE-A Advanced, LTE-Pro, 3GPP2 High-Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), IEEE 802.16e, and typical voice-based services to provide high-speed and high-quality packet data services.

[0037] As a typical example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink (UL). The uplink refers to the radio link through which a terminal (or UE) transmits data or control signals to a base station (or eNB or gNB), and the downlink refers to the radio link through which the base station transmits data or control signals to the UE. These multiple access schemes separate the data or control information of each user by allocating and manipulating time-frequency resources for transmitting data or control information to each user, thus avoiding overlap and establishing orthogonality.

[0038] As a post-LTE communication system, 5G communication systems must freely reflect the various requirements of users, service providers, and others, and therefore must support services that meet diverse needs. Services considered in 5G communication systems include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC), among others.

[0039] According to embodiments, eMBB is designed to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink for a single base station. Furthermore, the 5G communication system must provide the UE with increased user-aware data rates, as well as a maximum data rate. To meet these requirements, improvements to transmit / receive technologies, including further enhanced multiple-input multiple-output (MIMO) transmission technologies, may be necessary. Additionally, the data rates required by the 5G communication system can be achieved using a frequency bandwidth greater than 20 MHz in the 3 GHz to 6 GHz band or 6 GHz or higher, instead of using a transmission bandwidth of up to 20 MHz in the 2 GHz band used in LTE.

[0040] Furthermore, mMTC support for application services such as the Internet of Things (IoT) within 5G communication systems is being considered. To effectively deliver IoT, mMTC may have requirements such as supporting a large number of UEs within a cell, enhancing UE coverage, improving battery life, and reducing UE costs. Since IoT provides communication capabilities while being provided to various sensors and devices, it must support a large number of UEs within a cell (e.g., 1,000,000 UEs / km²). Additionally, UEs supporting mMTC may require wider coverage than other services provided by 5G communication systems because UEs may be located in shaded areas, such as building basements, which are not covered by the cell due to the nature of the service. UEs supporting mMTC must be configured to be inexpensive and may require very long battery lives, such as 10 to 15 years, due to the difficulty of frequently replacing UE batteries.

[0041] Finally, URLLC, as a cellular-based mission-critical wireless communication service, can be used for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, emergency alarms, and more. Therefore, URLLC must provide communication with both low latency (ultra-low latency) and high reliability (ultra-high reliability). For example, services supporting URLLC must meet an air interface latency of less than 0.5 ms and may also require a packet error rate of 10⁻⁵ or less. Therefore, for services supporting URLLC, 5G systems must provide shorter Transmission Time Intervals (TTIs) than other services and may also require designs that allocate significant resources in the frequency band to ensure the reliability of the communication link.

[0042] The three services considered in 5G communication systems—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, different transmit / receive technologies and parameters can be used between services to meet their varying requirements. However, mMTC, URLLC, and eMBB, as described above, are merely examples of different types of services, and the types of services to which this disclosure applies are not limited to those mentioned above.

[0043] Furthermore, in the following description, LTE, LTE-A, LTE Pro, 5G (or NR), or 6G systems will be described by way of example; however, the embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Moreover, based on the determination of those skilled in the art, the embodiments of this disclosure can also be applied to other communication systems with some modifications without significantly departing from the scope of this disclosure.

[0044] In the following description, for ease of description, the terms and names defined in the 5G system standards will be used to describe this disclosure, but this disclosure is not limited by these terms and names and can be applied in the same way to systems conforming to other standards.

[0045] Figure 1 The structure of a communication system related to this disclosure is shown.

[0046] 5G mobile communication system architecture can include various network entities or network functions (NFs). As an example, Figure 1 Some network entities or network functions are shown, including Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Unified Data Management (UDM), Data Network (DN) or local portion of a locally accessible DN, User Plane Function (UPF), (Radio) Access Network ((R)AN), and User Equipment (UE).

[0047] Each NF can support the following functions, and the functions described below are just examples.

[0048] -AMF provides access and mobility management functions on a UE-by-UE basis, and by default, a UE can connect to one AMF.

[0049] -DN can refer to, for example, carrier services, internet access, or third-party (third-party) services. The DN sends downlink protocol data units (PDUs) to the UPF or receives PDUs sent from the UE from the UPF. The local portion of the DN refers to a part of the DN that allows local access, thus forming a data network with short data transmission paths. The local portion of the DN can be used to indicate the DN in which edge application servers supporting edge computing services are deployed.

[0050] PCF provides the ability to determine policies such as mobility management policies and session management policies by receiving information about packet flows from the application server. Specifically, PCF supports a unified policy framework to control network operations, provides policy rules that enable control plane functions (or more) (e.g., AMF, SMF, etc.) to enforce policy rules, and implements front-ends to access subscription information related to policy decisions in the Unified Data Repository (UDR).

[0051] -SMF provides session management functionality, and when a UE has multiple sessions, the sessions can be managed by a different SMF for each session.

[0052] -UDM stores user subscription data, policy data, etc.

[0053] The UPF forwards downlink PDUs received from the DN to the UE via (R)AN, and forwards uplink PDUs received from the UE to the DN via (R)AN. The Uplink Classifier (ULCL) refers to a UPF that has the function of classifying and transmitting uplink data. The Local UPF (L-UPF) performs the role of session termination (i.e., PDU session anchor) for sessions sent to the local portion of the DN.

[0054] Network Data Analysis Functions (NWDAFs) perform the function of collecting data within the network and providing analysis services. An NWDAF can include logically separate functions, such as data collection, model training, and analysis service provision, and each function can be deployed as a single NWDAF instance within the network. Furthermore, each function can provide NWDAF services, and calls to NWDAF services between functions are possible.

[0055] Service Communication Agents (SCPs) can perform operations such as signaling transmission between network functions (supporting indirect communication between network functions), network function discovery, signaling communication security, and monitoring. Multiple SCPs can be distributed and deployed within a single mobile communication system. An SCP domain can be defined to include one or more SCPs and network function instances, and an SCP can communicate with all SCPs and network functions within its SCP domain.

[0056] Figure 2 This illustrates the process by which a network entity collects signaling data according to embodiments presented in this disclosure.

[0057] In Operation 1, the NF (i.e., the NWDAF consumer NF) can send an Analysis Service Request message to the NWDAF. This message can be an Nnwdaf_AnalyticsInfo_Request message or an Nnwdaf_AnalyticsSubscription_subscribe request message. The Analysis Service Request message may include information indicating that the analysis service request is related to the signaling payload, such as the analysis ID, which can be represented as a signaling transaction or signaling payload. Additionally, the Analysis Service Request message may include the target and analysis filter information for the analysis report. The Analysis Service Request message may include information indicating that at least one of the requested statistics or forecasts is needed, and may include a specific time window.

[0058] Analysis service request messages may also include information indicating a request for analysis information about a signaling transaction that occurs in relation to a specific network function service or process, such as an ID indicating the name of the specific network function service or network process.

[0059] In Operation 2, upon receiving an Analysis Service Request message, the NWDAF can initiate a process for collecting data about the Operation, Administration, and Maintenance (OAM; or Orchestration and Management) system. The information collected by the NWDAF from the OAM can include one or more types of information, such as the number of NF signaling occurrences, NF resource usage (the current use of virtual resources allocated for a specific NF instance (or multiple NF instances) – average usage of virtual CPU, memory, and disk) – and NF resource configuration (lifecycle changes of specific NF resources – e.g., NF operationalization or interruption during virtual or physical resource reconfiguration). Additionally, the NWDAF can collect UE-related information from the OAM (such as UE speed and UE orientation collected through Minimized Drive Test (MDT) operations).

[0060] In operation 3, the NWDAF can collect UE-related data. The NWDAF can collect UE data from the AF. The UE-related signaling transaction data collected by the NWDAF can include at least one of various parameters, such as signaling-related operations (e.g., information indicating specific operations, such as access and mobility management, session management, and UE configuration updates), the number of signaling occurrences, and the signaling time. For example, the NWDAF can invoke services provided by the AF to provide event IDs, collective actions, event filter information, event reporting targets, etc., and can receive UE-related data from the AF. In this case, the data provided by the AF is UE data collected by the UE, and the UE data collected by the UE can be stored in the AF and provided to the NWDAF in response to requests from the NWDAF. According to another embodiment, the NWDAF can collect data through various paths. For example, the NWDAF can collect UE-related signaling data via signaling through the AMF or via the user plane of the UPF.

[0061] In operation 4a, the NWDAF can determine the NFs for which signaling transaction-related data should be collected (e.g., NF1, NF2, and NF3 in the figure) based on the information received in operation 1, and can send a data provision request to each NF. For example, when the NWDAF receives a specific network function service, process name, or identifier in operation 1, the NWDAF can specify the network function providing the corresponding network function service or all network functions involved in the corresponding network process, thereby determining the network functions (or more) for which data should be collected (e.g., NF1, NF2, and NF3 in the figure). The NWDAF can send an NF signaling transaction data request message to the network functions (or more) for which data should be collected, as determined as above. The NF signaling transaction data request process can be executed in various ways. For example, the process can be executed by the NWDAF invoking an event exposure service provided by the network functions (or more) for the data to be collected, and by sending a subscription request for the service. To this end, each network function can provide the NWDAF with a service capable of providing signaling transaction-related data.

[0062] In operation 4b, each network function that has received a signaling transaction data collection request from the NWDAF can provide signaling transaction data to the NWDAF. The data provided to the NWDAF by each network function (NF1, NF2, and NF3 in the diagram) may include at least one of the following information.

[0063] -NF service name or ID, NF process name or ID

[0064] - Information on the number and timing of signaling occurrences related to a specific NF service or process

[0065] - Overload control occurrence information: Overload control occurrence information may include at least one of the following: the NF that underwent overload control, the number of times overload control was activated / executed, the time of activation / execution of overload control, and overload control scope information (e.g., NF service, NF instance-level scope, NF collection-level scope, etc.). Overload control executed by an NF may refer to an operation by which an NF service producer, based on a Hypertext Transfer Protocol (HTTP) status code, instructs or requests an NF service consumer to reduce service request signaling, or induces an NF service producer to reduce notification signaling.

[0066] In Operation 5, NWDAF can generate signaling transaction analysis by using data collected from previous operations. For example, NWDAF can analyze the collected data to generate signaling transaction statistics, or perform signaling transaction prediction by training a machine learning model using the collected data.

[0067] In operation 6, NWDAF can provide information to the NWDAF consumer NF regarding the statistical or predictive analytics generated in the previous operation. This process can be performed by sending an Nnwdaf_AnalyticsInfo_Request response message or an Nnwdaf_AnalyticsSubscription_Notify message.

[0068] In operations 7a to 7d, when the NWDAF has already performed a subscription request for data collection through operations 2 to 4 above, the NWDAF can receive notifications of updated data related to signaling transactions from the UE, OAM, and NF.

[0069] In Operation 8, NWDAF can update the statistical or predictive analysis generated in Operation 5 based on the updated data received in the previous operation.

[0070] In operation 9, NWDAF can provide updated signaling transaction analysis to the NWDAF consumer NF. This process can be performed by sending the Nnwdaf_AnalyticsSubscription_Notify message.

[0071] Figure 3 This illustrates a process by which a network entity collects signaling data from an SCP according to an embodiment of this disclosure.

[0072] In Operation 1, the NWDAF consumer (NF) can send an Analysis Service Request message to the NWDAF. This message can be either an Nnwdaf_AnalyticsInfo_Request message or an Nnwdaf_AnalyticsSubscription_subscribe request message. The Analysis Service Request message may include information indicating that the analysis service request is related to a signaling payload, such as an analysis ID, which can be represented as a signaling transaction or signaling payload. Additionally, the Analysis Service Request message may include the target and analysis filter information for the analysis report. The Analysis Service Request message may include information indicating that at least one of the requested statistics or forecasts is being requested, and may include a specific time window.

[0073] Analysis service request messages may also include information indicating a request for analysis information about a signaling transaction that occurs with respect to a specific network function service or process, such as an ID indicating the name of the specific network function service or network process.

[0074] In Operation 2, upon receiving an Analysis Service Request message, the NWDAF can initiate a data collection process targeting the OAM system. The information collected by the NWDAF from the OAM can include one or more types of information, such as the number of NF signaling occurrences, NF resource usage (the current use of virtual resources allocated for a specific NF instance (or multiple NF instances) – average usage of virtual CPU, memory, and disk) – and NF resource configuration (lifecycle changes of specific NF resources – e.g., NF operationalization or interruption during virtual / physical resource reconfiguration)). Additionally, the NWDAF can collect UE-related information from the OAM (such as UE speed and UE orientation, which is data collected through Minimized Drive Test (MDT) operations).

[0075] In operation 3, the NWDAF can collect UE-related data. The NWDAF can collect UE data from the AF. The UE-related signaling transaction data collected by the NWDAF can include at least one of various parameters, such as signaling-related operations (information indicating specific operations, such as access and mobility management, session management, and UE configuration updates), and information about the number and timing of signaling occurrences. For example, the NWDAF can invoke services provided by the AF to provide event IDs, collective actions, event filter information, event reporting targets, etc., and can receive UE-related data from the AF. In this case, the data provided by the AF is UE data collected by the UE, and the UE data collected by the UE can be stored in the AF and provided to the NWDAF in response to requests from the NWDAF. According to another embodiment, the NWDAF can collect data through various paths. For example, the NWDAF can collect UE-related signaling data via signaling through the AMF or via the user plane through the UPF.

[0076] In Operation 4, the NWDAF can determine, based on the information received in Operation 1, the network functions (or more) for which signaling transaction-related data should be collected (e.g., NF1, NF2, and NF3 in the diagram), and can identify whether SCPs are deployed and used. For example, the NWDAF can use information configured in the NWDAF or information collected from the NRF regarding NF1, NF2, and NF3 to determine whether the service mesh is configured and in use, or whether an SCP is used for the network functions (or more) for which data should be collected. The NWDAF can identify whether an SCP is used for the network functions (or more) for which data should be collected (or for NF services or for signaling transaction analysis processes), and can perform the discovery and selection of the appropriate SCP. Figure 4 The document details NWDAF's SCP discovery and selection procedures.

[0077] In operation 5, the NWDAF may send an NF signaling transaction data request message to the SCP selected in the previous operation. The request message may include information about the NF (or more) for which data is to be collected (e.g., NF1, NF2, and NF3 in the attached diagram) and at least one of an ID indicating a specific network function service name or network procedure name. This is to notify the SCP that the NWDAF is requesting the collection of data regarding signaling transactions occurring relative to a specific network function service or procedure.

[0078] The data provided by NWDAF to SCP for data collection may include at least one of the following information, and may include multiple pieces of information as exemplified below. Each piece of information described below can be used as a filter for selectively obtaining information collected by SCP.

[0079] -NF information (e.g., NF identifier and address information)

[0080] -NF service name or ID, NF process name or ID

[0081] -SCP domain information or service grid information

[0082] - Information on the number and timing of signaling occurrences related to a specific NF service or process

[0083] - Request for overload control information

[0084] In Operation 6, in response to a request from NWDAF, SCP may send at least one of the following messages to NWDAF as signaling transaction related data.

[0085] -NF information (e.g., NF identifier and address information)

[0086] -NF service name or ID, NF process name or ID

[0087] -SCP domain information or service grid information

[0088] - Information on the number and timing of signaling occurrences related to a specific NF service or process

[0089] - Overload control occurrence information: Overload control occurrence information may include at least one of the following: the NF that underwent overload control, the number of times overload control was activated / executed, the time when overload control was activated / executed, and overload control scope information (e.g., NF service, NF instance-level scope, or NF collection-level scope).

[0090] In Operation 7, the NWDAF can collect SCP payload information or SCP resource status information (SCP resource usage or SCP resource configuration), which may indirectly lead to signaling transaction congestion, and the NWDAF can collect such information through OAM or NRF.

[0091] In Operation 8, NWDAF can generate signaling transaction analysis by using data collected in previous operations. For example, NWDAF can generate signaling transaction statistics by analyzing the collected data, or it can perform signaling transaction prediction by training a machine learning model using the collected data.

[0092] In operation 9, NWDAF can provide information to the NWDAF consumer NF regarding the statistical or predictive analytics generated in the previous operation. This process can be performed by sending an Nnwdaf_AnalyticsInfo_Request response message or an Nnwdaf_AnalyticsSubscription_Notify message.

[0093] In operations 10a to 10d, when the NWDAF has already performed a subscription request for data collection through operations 2 to 7 above, the NWDAF can receive notifications of updated data related to signaling transactions from the UE, OAM, and SCP.

[0094] In Operation 11, NWDAF can update the statistical or predictive analysis generated in Operation 5 based on the updated data received in the previous operation.

[0095] In operation 12, NWDAF can provide updated signaling transaction analysis to the NWDAF consumer NF. This process can be performed by sending the Nnwdaf_AnalyticsSubscription_Notify message.

[0096] Figure 4The process of searching and selecting SCPs to collect signaling data according to embodiments presented in this disclosure is illustrated.

[0097] In Operation 1, the NWDAF consumer NF can send an analytics service request message to the NWDAF. This message can be either an Nnwdaf_AnalyticsInfo_Request message or an Nnwdaf_AnalyticsSubscription_subscribe request message. In addition to... Figure 3 or Figure 4 In addition to the information provided by NWDAF as described above, NWDAF consumer NFs can also send at least one of the following to NWDAF: information about the target SCP, information about the target service grid, information about the target process, and SCP domain information, in order to obtain analytical information related to the SCP.

[0098] In operation 2, NWDAF can perform data collection from OAM. The process of NWDAF collecting data from OAM can be referenced above. Figure 3 The described embodiments are the same or similar.

[0099] In operation 3, NWDAF can perform UE data collection. The process of NWDAF collecting UE data can be referenced above. Figure 3 The described embodiments are the same or similar.

[0100] In Operation 4, NWDAF can perform SCP discovery and selection operations. For example, NWDAF can identify the network functions (or more) to be analyzed (NF1, NF2, and NF3) and can perform operations to select the SCP responsible for the corresponding network functions (or more).

[0101] According to the embodiment ( Figure 4 Option 1), NWDAF can request and obtain service SCP information from each of NF1, NF2, and NF3. NWDAF can send service SCP information request messages to NF1, NF2, and NF3, and each network function can send configured service SCP information (identifier and address information) to NWDAF.

[0102] According to another embodiment ( Figure 4(Option 2) The NWDAF can provide information about NF1, NF2, and NF3 to the NRF, and can receive information from the NRF about the SCPs responsible for the corresponding NFs (or more). The NWDAF can send the network function service name or network procedure name, SCP domain information, and NF list to the NRF, and can receive SCP information in response. According to an embodiment, the SCP information that the NWDAF can obtain from the NRF can refer to the SCP profile information registered in the NRF. In this case, after deployment in the core network, the SCP can perform the NRF registration process by sending a service request message such as the NF_Management_NFRegister message to the NRF, and can provide the NRF with at least one of the following: SCP identifier and address information, information indicating whether event exposure functionality is supported (such as whether the functionality of providing information collected by the SCP to other NFs is supported), SCP domain information, and NF list (NF identifier and address list information).

[0103] In Operation 5, the NWDAF can send signaling transaction-related data requests to the SCP using the SCP information obtained through discovery in previous operations, and can also receive signaling transaction-related data from the SCP. The process of the NWDAF sending data requests to the SCP and receiving data from the SCP can be referenced above. Figure 3 The described embodiments are the same or similar.

[0104] In operation 6, NWDAF can generate signaling transaction analysis, and this process can be referenced above. Figure 3 The described embodiments are the same or similar.

[0105] In operation 7, NWDAF can provide NWDAF consumer NF with information about the generated statistical or predictive analysis, and can apply the above reference in the same or similar manner. Figure 3 The described embodiments.

[0106] Figure 5 The structure of a UE according to an embodiment of the present disclosure is shown.

[0107] like Figure 5 As shown, the UE disclosed herein may include a transceiver 510, a memory 520, and a UE controller (or processor) 530. The UE controller 530, transceiver 510, and memory 520 can operate according to the communication method of the UE described above. However, the components of the UE are not limited to the examples described above. For example, the UE may include more or fewer components than those described above. Furthermore, the UE controller 530, transceiver 510, and memory 520 may be implemented as a single chip.

[0108] Transceiver 510 refers to a UE receiver and UE transmitter as a whole, and can transmit / receive signals with a base station or network entity. Signals transmitted / received using the base station may include control information and data. For this purpose, transceiver 510 may include a radio frequency (RF) transmitter configured to up-convert and amplify the frequency of the transmitted signal, an RF receiver configured to amplify the received signal with low noise and down-convert its frequency, etc. However, this is only one embodiment of transceiver 510, and the components of transceiver 510 are not limited to RF transmitters and RF receivers.

[0109] Furthermore, transceiver 510 may include a wired / wireless transceiver and may include various components for transmitting / receiving signals. Additionally, transceiver 510 can receive signals via a radio channel, output them to UE controller 530, and transmit signals output from UE controller 530 via a radio channel. Furthermore, transceiver 510 can receive communication signals, output them to UE controller 530, and transmit signals output from UE controller 530 to a base station or network entity via a wired / wireless network.

[0110] The memory 520 can store programs and data required for the operation of the UE. Additionally, the memory 520 can store control information or data included in signals acquired by the UE. The memory 520 may include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0111] The UE controller 530 can control a series of processes that enable the UE to operate according to the embodiments described above in this disclosure. The UE controller 530 may include one or more processors. For example, the UE controller 530 may include a communication processor (CP) configured to perform control for communication, and an application processor (AP) configured to control upper-layer applications such as applications.

[0112] Figure 6 The structure of a base station according to an embodiment of the present disclosure is shown. Figure 6 The base station shown can correspond to the one mentioned above. Figures 1 to 4 The Radio Access Node (RAN) described in the document.

[0113] like Figure 6 As shown, the base station of this disclosure may include a transceiver 610, a memory 620, and a base station controller (or processor) 630. The base station controller 630, transceiver 610, and memory 620 of the base station can operate according to the communication method of the base station described above. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than those described above. According to an embodiment, Figure 6The overall functionality of a base station can be divided into functions implemented by the CU and DU, and in this case, the CU and DU can each perform functions assigned by the CU. Figure 6 This is part of the functions performed by the base station. Additionally, the base station controller 630, transceiver 610, and memory 620 can be implemented as a single chip.

[0114] Transceiver 610 refers to a base station receiver and base station transmitter as a whole, capable of transmitting / receiving signals with a UE and / or network equipment. The transmitted / received signals may include control information and data. For this purpose, transceiver 610 may include an RF transmitter configured to up-convert and amplify the frequency of the transmitted signal, an RF receiver configured to perform low-noise amplification and down-convert the frequency of the received signal, etc. However, this is only one embodiment of transceiver 610, and the components of transceiver 610 are not limited to RF transmitters and RF receivers. Transceiver 610 may include wired / wireless transceivers and may include various components for transmitting / receiving signals.

[0115] Additionally, transceiver 610 can receive signals via a communication channel (e.g., a radio channel), output them to base station controller 630, and transmit signals output from base station controller 630 via the communication channel. Furthermore, transceiver 610 can receive communication signals, output them to a processor, and transmit signals output from the processor to a UE or network entity via a wired / wireless network.

[0116] The memory 620 can store programs and data required for the operation of the base station. Additionally, the memory 620 can store control information or data included in signals acquired by the base station. The memory 620 may include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0117] The base station controller 630 can control a series of processes that enable the base station to operate according to the embodiments described above. The base station controller 630 may include one or more processors. The methods disclosed in the claims or the methods described in the embodiments of this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0118] Figure 7 The structure of a network function (or network entity) according to an embodiment of this disclosure is shown. Figure 7 The network functions (or network entities) shown in the diagram can correspond to the above-mentioned functions. Figures 1 to 4 The various functions or entities of the core network described in the document.

[0119] like Figure 7As shown, the network function (NF) (or network entity (NE)) of this disclosure may include a transceiver 710, a memory 720, and an NF controller (or processor) 730. The NF controller 730, transceiver 710, and memory 720 of the NF (or NE) can operate according to the communication methods described above for the NF (or NE). However, the components of the NF (or NE) are not limited to the examples described above. For example, the NF (or NE) may include more or fewer components than those described above.

[0120] Transceiver 710 refers to an NF (or NE) receiver and NF (or NE) transmitter as a whole, and can transmit / receive signals with a UE, a base station, and / or other NFs (or NEs). The transmitted / received signals may include control information and data. For this purpose, transceiver 710 can communicate with nodes or base stations in the core network via wired or wireless transceivers. However, this is only an example of transceiver 710, and transceiver 710 may also include an RF transmitter configured to up-convert and amplify the frequency of the transmitted signal, an RF receiver configured to amplify the received signal with low noise and down-convert its frequency, etc., and may include various components for signal transmission or reception.

[0121] Additionally, transceiver 710 can receive signals via a communication channel (e.g., a radio channel), output them to NF controller 730, and transmit signals output from NF controller 730 via the communication channel. Furthermore, transceiver 710 can receive communication signals, output them to NF controller 730, and transmit signals output from NF controller 730 to UE, base station, or network entity via wired / wireless networks.

[0122] The memory 720 can store the programs and data required for the operation of the NF (or NE). Additionally, the memory 720 can store control information or data included in signals acquired by the NF (or NE). The memory 720 can include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0123] The NF controller 730 can control a series of processes that enable the NF (or NE) to operate according to the foregoing embodiments of this disclosure. The NF controller 730 may include one or more processors. The methods disclosed in the claims or the methods described in the embodiments of this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0124] The methods disclosed in the claims and / or the methods of the embodiments described in this disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0125] When the method is implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. The at least one program includes instructions to cause the electronic device to perform a method according to various embodiments of the present disclosure as defined by the appended claims and / or disclosed herein.

[0126] These programs (software modules or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc ROM (CD-ROM), digital versatile optical disc (DVD), or other types of optical storage devices or magnetic tape cartridges. Alternatively, any combination of some or all of these can form a memory storing programs. Furthermore, multiple such memories can be included in an electronic device.

[0127] Furthermore, the program can be stored in an attachable storage device that can be accessed by the electronic device via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. Additionally, a separate storage device on the communication network can access portable electronic devices.

[0128] In the detailed embodiments described above, elements included in this disclosure are represented in a singular or plural form according to the presented embodiments. However, for ease of description, the singular or plural form is suitably chosen for the presented situation, and this disclosure is not limited to elements represented in a singular or plural form. Thus, an element represented in a plural form may also include a single element, or an element represented in a singular form may include multiple elements.

[0129] Although specific embodiments have been described in detail in this disclosure, it will be apparent that various modifications and changes can be made thereto without departing from the scope of this disclosure. For example, some or all of the embodiments may be combined with some or all of one or more other embodiments, and naturally, implementations of such combinations also correspond to the embodiments proposed in this disclosure. Therefore, the scope of this disclosure should not be limited to the embodiments set forth herein, but should be defined by the appended claims and their equivalents.

Claims

1. A method performed by a Network Data Analysis Function (NWDAF) entity in a wireless communication system, the method comprising: Receive a first message from the first network function entity requesting analysis services; Select the Service Communication Agent (SCP) entity; Send a second message to the selected SCP entity to request data related to signaling transactions; Receive a third message containing data related to signaling transactions from the selected SCP entity; Analysis results are generated based on data related to signaling transactions; as well as Send a fourth message, including the analysis results, to the first network functional entity.

2. The method according to claim 1, wherein, Selected SCP entities include: Request information from the second network functional entity regarding SCP entities related to the second network functional entity; and Receive information about SCP entities from the second network functional entity.

3. The method according to claim 1, wherein, Selected SCP entities include: Request information from the Network Repository Function (NRF) entity regarding SCP entities related to the second network function entity; and Receive information about SCP entities from NRF entities.

4. The method according to claim 1, wherein, The second message includes at least one of the following: information about the network function entity to be analyzed, information about the services of the network function, information about the network process, SCP domain information, service mesh information, information about the number and timing of signaling occurrences, and information about the occurrence of overload control.

5. The method according to claim 1, further comprising: Receive information about the terminal from Operation, Administration and Maintenance (OAM). The information about the terminal includes information about its speed and direction.

6. The method according to claim 1, wherein, The first message includes information indicating a request for an analysis service associated with a signaling transaction.

7. A method performed by a Serving Communication Agent (SCP) entity in a wireless communication system, the method comprising: Receive the first message from the Network Data Analysis Function (NWDAF) entity requesting data related to signaling transactions; as well as Send a second message to the NWDAF entity, which includes data related to the signaling transaction.

8. The method according to claim 7, wherein, The first message includes at least one of the following: information about the network function entity to be analyzed, information about the services of the network function, information about the network process, SCP domain information, service mesh information, information about the number and timing of signaling occurrences, and information about the occurrence of overload control.

9. A Network Data Analysis Function (NWDAF) entity in a wireless communication system, the NWDAF entity comprising: transceiver; as well as The controller is connected to the transceiver. The controller is configured as follows: Receive a first message from the first network function entity requesting analysis services; Select the Service Communication Agent (SCP) entity; Send a second message to the selected SCP entity to request data related to signaling transactions; Receive a third message containing data related to signaling transactions from the selected SCP entity; Analysis results are generated based on data related to signaling transactions; and Send a fourth message, including the analysis results, to the first network functional entity.

10. The NWDAF entity according to claim 9, wherein, The controller is configured as follows: Request information from the second network functional entity regarding SCP entities related to the second network functional entity; and Receive information about SCP entities from the second network functional entity.

11. The NWDAF entity according to claim 9, wherein, The controller is configured as follows: Request information about SCP entities related to the second network function entity from the Network Repository Function (NRF) entity; and Receive information about SCP entities from NRF entities.

12. The NWDAF entity according to claim 9, wherein, The second message includes at least one of the following: information about the network function entity to be analyzed, information about the services of the network function, information about the network process, SCP domain information, service mesh information, the number and timing of signaling occurrences, and information about the occurrence of overload control.

13. The NWDAF entity according to claim 9, wherein, The controller is configured to receive information about the terminal from the Operations, Administration and Maintenance (OAM) system. The information about the terminal includes information about its speed and direction.

14. A Service Communication Agent (SCP) entity in a wireless communication system, the SCP entity comprising: transceiver; as well as The controller is connected to the transceiver. The controller is configured as follows: Receive the first message from the Network Data Analysis Function (NWDAF) entity requesting data related to signaling transactions; and Send a second message to the NWDAF entity, which includes data related to the signaling transaction.

15. The SCP entity according to claim 14, wherein, The first message includes at least one of the following: information about the network function entity to be analyzed, information about the services of the network function, information about the network process, SCP domain information, service mesh information, the number and timing of signaling occurrences, and information about the occurrence of overload control.

Images