Mobility-assisted method and apparatus for network data collection and analysis in wireless communication networks
The NWDAF entity optimizes network data collection and analysis by transferring subscriptions between NWDAFs and NFs, addressing mobility and load challenges, thereby reducing signaling loads and enhancing network automation in complex wireless communication networks.
Patent Information
- Application Number
- JP2022570728
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-09-04
- Filing Date
- 2021-05-21
- Publication Date
- 2025-09-25
- Estimated Expiration
- 2041-05-21
AI Technical Summary
Existing wireless communication networks face challenges in automating network management due to increased complexity and diversity, particularly in managing mobility and network load, leading to increased signaling message loads during NWDAF reassignment.
A method and apparatus for a Network Data Collection and Analysis Function (NWDAF) entity that supports mobility by transferring analysis subscriptions between NWDAFs and NFs based on terminal location, consumer NFs, and target areas, using a subscription transfer mechanism to optimize network data collection and analysis.
This approach reduces signaling message loads and enhances network automation by efficiently managing NWDAF changes due to terminal mobility or network load, facilitating seamless handovers and data analysis in complex wireless communication networks.
Smart Images

Figure 0007744367000004 
Figure 0007744367000005 
Figure 0007744367000006
Abstract
Description
[Technical Field]
[0001] The present invention relates to a method and apparatus for supporting mobility in collecting and analyzing network data to automate the management of wireless communication networks. [Background technology]
[0002] Since the commercialization of 4G (4th-Generation) communication systems, efforts have been made to develop improved 5G (5th-Generation) or pre-5G communication systems to meet the increasing demand for wireless data traffic. For this reason, 5G or pre-5G communication systems are also called beyond 4G network communication systems or systems beyond LTE (long term evolution) / LTE-A (LTE advanced) systems.
[0003] To achieve higher data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band, etc.) To mitigate radio wave propagation loss and increase radio wave transmission distances in the ultra-high frequency bands, beamforming, massive multiple input multiple output (MIMO), full dimensional multiple input multiple output (FD-MIMO), array antennas, analog beamforming, and large scale antenna technologies are being discussed for 5G communication systems.
[0004] In addition, to improve the system's network, technologies being developed for 5G communication systems include advanced small cells, cloud Radio Access Networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and receiver interference cancellation.
[0005] Other advanced coding modulation (ACM) technologies being developed for 5G systems include hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC), as well as advanced access technologies such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA).
[0006] Meanwhile, the Internet is evolving from a human-centered connection network where humans generate and consume information to an IoT (Internet of Things) network where information is exchanged and processed between distributed components such as things. IoE (Internet of Everything) technology is an example of IoT technology being combined with big data processing technology through connections to cloud servers.
[0007] To realize IoT, technological elements such as sensing technology, wired and wireless communication, network infrastructure, service interface technology, and security technology are required, so recently, technologies such as sensor networks for connecting things, M2M (Machine to Machine) communication, and MTC (Machine Type Communication) have been researched.
[0008] In an IoT environment, intelligent IT (Internet Technology) services that create new value in human life can be provided by collecting and analyzing data generated between connected things. Through the fusion and combination of existing IT technologies with various industries, IoT has the potential to be applied to a variety of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.
[0009] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, 5G communication technologies such as sensor networks, M2M communications, and MTC are being realized using techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN), the aforementioned big data processing technology, is another example of the fusion of 5G and IoT technologies.
[0010] As mobile communication systems have developed as described above, it has become possible to provide a variety of services, and as wireless communication networks have become more complex and diverse, there has been an emerging need for technology to automate the management of wireless communication networks. Summary of the Invention [Problem to be solved by the invention]
[0011] The present invention defines a method and apparatus that provides analysis and collection of network data to automate the management of wireless communication networks.
[0012] The present invention defines a method and apparatus for supporting mobility in a Network Data Collection and Analysis Function (NWDAF) entity that provides network data collection and analysis in a wireless communication network.
[0013] The present invention defines a method and apparatus for controlling signal flow between an NWDAF and a network function (NF) in a mobility management procedure.
[0014] The present invention defines a method and apparatus for controlling signal flow between NWDAF entities to support mobility.
[0015] The present invention defines a method and apparatus for supporting NWDAF changes due to terminal mobility or network load.
[0016] The present invention defines a method and apparatus for supporting handover between NWDAF entities due to terminal mobility or network load. [Means for solving the problem]
[0017] In order to achieve the above object, one aspect of the present invention provides a method for mobility support by a Network Data Collection and Analysis Function (NWDAF) entity in a wireless communication network, the method including the steps of: determining a transfer of one or more analysis subscriptions to at least one Network Function (NF); determining a target NWDAF to which the one or more analysis subscriptions are to be transferred based on at least one of a terminal location, the one or more analysis subscriptions, at least one consumer NF, and a target area; transmitting a subscription transfer request message to the target NWDAF, the subscription transfer request message including first subscription information related to the one or more analysis subscriptions; receiving from the target NWDAF a subscription transfer response message including second subscription information related to at least one analysis subscription generated based on the first subscription information; and requesting a source NF to unsubscribe from a corresponding analysis subscription among the at least one analysis subscription based on the second subscription information.
[0018] Another aspect of the present invention, which has been made to achieve the above object, is a method for mobility support by a Network Data Collection and Analysis Function (NWDAF) entity in a wireless communication network, characterized in that it includes the steps of receiving a subscription transfer request message from a source NWDAF, the subscription transfer request message including first subscription information regarding one or more analysis subscriptions for at least one network function (NF); sending a subscription transfer response message to the source NWDAF, the subscription transfer response message including second subscription information regarding at least one analysis subscription generated based on the first subscription information; and sending a subscription request message to a source NF associated with a corresponding analysis subscription among the at least one analysis subscription based on the second subscription information.
[0019] In order to achieve the above object, one aspect of the present invention provides an apparatus for a Network Data Collection and Analysis Function (NWDAF) entity in a wireless communication network, comprising: a transceiver; and a processor operatively connected to the transceiver, wherein the processor is configured to: determine a transfer of one or more analysis subscriptions to at least one Network Function (NF); determine a target NWDAF to which the one or more analysis subscriptions are to be transferred based on at least one of a terminal location, the one or more analysis subscriptions, at least one consumer NF, and a target area; send a subscription transfer request message to the target NWDAF, the subscription transfer request message including first subscription information for the one or more analysis subscriptions; receive from the target NWDAF a subscription transfer response message, the subscription transfer response message including second subscription information for at least one analysis subscription generated based on the first subscription information; and, based on the second subscription information, request a source NF to unsubscribe from a corresponding analysis subscription among the at least one analysis subscription.
[0020] Another aspect of the present invention, which has been made to achieve the above object, provides an apparatus for a Network Data Collection and Analysis Function (NWDAF) entity in a wireless communication network, comprising: a transceiver; and a processor functionally connected to the transceiver, wherein the processor is configured to receive a subscription transfer request message from a source NWDAF, the subscription transfer request message including first subscription information regarding one or more analysis subscriptions for at least one network function (NF), send a subscription transfer response message to the source NWDAF, the subscription transfer response message including second subscription information regarding at least one analysis subscription generated based on the first subscription information, and send a subscription request message to a source NF associated with a corresponding analysis subscription among the at least one analysis subscription, based on the second subscription information. [Effects of the Invention]
[0021] According to the present invention, an efficient communication method and apparatus are provided in a wireless communication system that supports network slicing, and can facilitate the collection and analysis of network data. [Brief explanation of the drawings]
[0022] [Figure 1] 1 is a block diagram of a wireless communication network including a network data collection and analysis function (NWDAF) according to one embodiment of the present invention. [Figure 2] 3 is a signal flow diagram illustrating network data collection and analysis operations according to one embodiment of the present invention. [Figure 3] 1 is a diagram showing a schematic structure of a system for collecting and analyzing network data according to an embodiment of the present invention; [Figure 4] FIG. 1 illustrates a problem that may arise due to NWDAF reassignment in a wireless communication network including multiple NWDAFs. [Figure 5]FIG. 1 illustrates a mobility management procedure with NWDAF reassignment in a wireless communication network according to an embodiment of the present invention. [Figure 6] FIG. 1 illustrates a mobility management procedure with source NF change in a wireless communication network according to an embodiment of the present invention. [Figure 7a] 1 is a signal flow diagram illustrating a mobility management procedure with NWDAF reassignment in a wireless communication network according to an embodiment of the present invention. [Figure 7b] 1 is a signal flow diagram illustrating a mobility management procedure with NWDAF reassignment in a wireless communication network according to an embodiment of the present invention. [Figure 8] 1 is a signal flow diagram illustrating a mobility management procedure initiated by a target NWDAF in a wireless communication network according to an embodiment of the present invention. [Figure 9] FIG. 1 is a diagram illustrating mobility management in a wireless communication network having a hierarchical NWDAF structure according to one embodiment of the present invention. [Figure 10a] 1 is a signal flow diagram illustrating a procedure for updating a subscription to support mobility when there is a local NWDAF associated with a consumer NF in a wireless communication network according to an embodiment of the present invention. [Figure 10b] 1 is a signal flow diagram illustrating a procedure for updating a subscription to support mobility when there is a local NWDAF associated with a consumer NF in a wireless communication network according to an embodiment of the present invention. [Figure 11] FIG. 1 illustrates the configuration of a network function (NF) entity according to an embodiment of the present invention. [Figure 12] FIG. 1 illustrates the configuration of a Network Data Collection and Analysis Function (NWDAF) entity according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION
[0023] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
[0024] When describing embodiments of the present invention, if a detailed description of related functions or configurations is deemed to unnecessarily obscure the gist of the present invention, the detailed description will be omitted. Furthermore, the terms described below are defined in consideration of the functions of the present invention, and may vary depending on the intentions or practices of users or operators. Therefore, the definitions will be based on the contents throughout this specification.
[0025] For the same reason, some components may be exaggerated, omitted, or shown in a schematic manner in the drawings. Furthermore, the size of each component does not completely reflect the actual size. The same reference numerals are used to designate the same or corresponding components in the drawings.
[0026] The advantages and features of the present invention, as well as methods for achieving them, will become apparent from the following detailed description of the embodiments accompanied by the drawings. However, the present invention is not limited to the embodiments disclosed below, and can be embodied in various forms. The embodiments are provided solely for the purpose of completeness of the description of the present invention and to fully convey the technical scope of the invention to those skilled in the art.
[0027] In this regard, it will be understood that each block of the process flowchart diagrams and combinations thereof are implemented by computer program instructions. These computer program instructions can be implemented in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, generate means for performing the functions set forth in the blocks of the flowchart diagrams. These computer program instructions can also be stored in a computer-usable or computer-readable memory that directs the computer or other programmable data processing apparatus to perform functions in a particular manner, such that the instructions stored in the computer-usable or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions set forth in the blocks of the flowchart diagrams. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus, such that a sequence of operational steps are executed on the computer or other programmable data processing apparatus to generate a computer-implemented process, such that the instructions executing on the computer or other programmable data processing apparatus provide the steps for performing the functions set forth in the blocks of the flowchart diagrams.
[0028] Furthermore, each block represents a module, segment, or portion of code that includes one or more executable instructions for performing a particular logical function. Also, it should be noted that in some alternative implementations, the functions noted in the blocks may occur out of order. For example, two blocks shown in succession may be executed substantially simultaneously, or the blocks may be executed in reverse order according to their corresponding functions.
[0029] As used herein, the term "unit" or "part" refers to software or hardware components, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), configured to perform a specific function. However, the term "unit" is not limited to software or hardware. A "unit" may be configured on an addressable storage medium and executed by one or more processors. Thus, by way of example, a "unit" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within components and units may be combined into fewer components and units or further separated into additional components and units. Furthermore, components and units may be implemented to represent one or more CPUs within a device or a security multimedia card. Furthermore, in embodiments, a "unit" may include one or more processors and / or devices.
[0030] For ease of explanation, some terms and names defined in 3GPP (registered trademark) (3rd Generation Partnership Project Long Term Evolution)-based communication standards (e.g., specifications for 5G, NR, LTE, or similar systems) are used below. However, the present invention is not limited by the terms and names and can be applied to systems conforming to other specifications as well.
[0031] In the following description, terms for identifying connection nodes, network entities, messages, interfaces between network objects, or various identification information are provided as examples for the sake of convenience. Therefore, the present invention is not limited to the terms described below, and other terms having equivalent technical meanings may be used.
[0032] In describing the embodiments of the present invention in detail, the main focus will be on New RAN (NR), which is a radio access network based on the 5G mobile communication standard specified by 3GPP, a mobile communication standardization organization, and packet core (5G System, or 5G Core Network, or NG Core: Next Generation Core), which is a core network. However, the main gist of the present invention can be applied with slight modifications to other communication systems having a similar technical background without significantly departing from the technical scope of the present invention, and this would be possible at the discretion of a person skilled in the technical field of the present invention.
[0033] In the 5G system, a Network Data Collection and Analysis Function (NWDAF) is defined, which is a network function that analyzes and provides data collected in the 5G network to support network automation. The NWDAF collects, stores, and analyzes information from the 5G network and provides the results to at least one Network Function (NF), and the analysis results are used independently by each NF.
[0034] In a 5G mobile communication system, NFs are supported to use the results of collection and analysis of network-related data (hereinafter referred to as network data) through the NWDAF. This is to enable each NF to collect and analyze network data necessary to effectively provide its provided functions in a centralized manner. The NWDAF collects and analyzes network data using a network slice as a basic unit. However, the technical scope of the present invention is not limited to network slice units, and the NWDAF may further use various information (e.g., including service quality) obtained from a user equipment (UE), a PDU session, an NF state, and / or an external service server.
[0035] The analysis results from the NWDAF are transmitted to each NF that requested the analysis results, and the transmitted analysis results are used to optimize network management functions such as quality of service (QoS) assurance / improvement, traffic control, mobility management, and / or load balancing.
[0036] A unit node that performs each function provided by the 5G network system is defined as an NF (also referred to as an NF entity or NF node). Each NF includes, for example, at least one of an access and mobility management function (AMF) that manages access and mobility of a terminal (user equipment: UE) to an access network (AN), a session management function (SMF) that performs session-related management, a user plane function (UPF) that manages the user data plane, or a network slice selection function (NSSF) that selects a network slice instance available to the terminal.
[0037] FIG. 1 is a block diagram of a wireless communication network including a Network Data Collection and Analysis Function (NWDAF) according to one embodiment of the present invention.
[0038] 1 , the NWDAF 105 collects network data in various ways from at least one source NF, for example, an NF in a 5G core network, such as an AMF 110, an SMF 115, or a UPF (125, 130, 135), an Application Function (AF), a network exposure function (NEF), or an Operation, Administration, and Maintenance (OAM) for efficient service provision. The AMF 110 is connected to a terminal 100 and a radio access network (RAN) 120, and the UPF (125, 130, 135) connects user traffic of the terminal 100 via the RAN 120 to at least one data network (DN) 140.
[0039] Additionally, the NWDAF 105 provides at least one consumer NF with analysis of network data collected in the network or externally. The NWDAF 105 collects and analyzes load levels of network slice instances and provides them to the NSSF for use in selecting available ones for a particular UE.
[0040] To request analytical data or transmit analytical information including analytical results between the NFs (110, 115) and the NWDAF 105, a service-based interface defined in the 5G network can be used, and the transmission method may be, for example, HTTP (hypertext transfer protocol) and / or JSON (JavaScript object notation) documents.
[0041] In one embodiment, the collected data of the NWDAF 105 may include at least one of an application identifier (Application ID) from the Point Coordination Function (PCF), IP filter information, media / application bandwidth, a terminal identifier from the AMF, location information, a destination data network name (DNN) from the SMF, a terminal IP, a QoS flow bit rate, a QoS Flow ID (QFI), a QoS flow error rate, a QoS flow delay, or a traffic usage report from the UPF.
[0042] The NWDAF can also collect at least one of the following information from the OAM, which is an entity that may affect the connection between the terminal and the service server in addition to the NFs that constitute the core network: NF resource status, NF processing capability (Throughput), SLA (Service Level Agreement) information, UE status from the terminal, UE application information, UE Usage Pattern, application identifier of the service provided by the AF, service experience, or traffic pattern, and use it for analysis.
[0043] Tables 1 to 3 below show examples of network data collected by NWDAF. The period and time when NWDAF collects network data from each entity may vary depending on the entity. In addition, correlation IDs for correlating the data of each collected target and timestamps for recording the collection time are used to distinguish the correlation of collected data.
[0044] [Table 1]
[0045] [Table 2]
[0046] [Table 3]
[0047] FIG. 2 shows a schematic structure for collecting and analyzing network data according to one embodiment of the present invention.
[0048] 2, in step 210, the NWDAF collects network data from NFs such as RAN, AMF, SMF, and UPF, in step 220, collects service data from NEF or AF, in step 230, collects management data from OAM, and in step 240, collects UE data from UE. Examples of the collected data are shown in Tables 1 to 3. In step 250, the NWDAF analyzes the collected data and provides the analysis results to the corresponding NF upon request.
[0049] FIG. 3 shows a schematic structure of a system for collecting and analyzing network data according to an embodiment of the present invention.
[0050] 3, each of the network entities constituting the core network, such as the AMF, SMF, OAM, or RAN, operates as a consumer NF 310 that requests analysis information generated as an analysis result from the NWDAF 305 (operation 1). The NWDAF 305 collects and analyzes data from a source NF 315, such as an NF, AF, or OAM, (operation 2) to generate the requested analysis information for the consumer NF 310. The NWDAF 305 transmits the analysis information to the consumer NF 310 that sent the request (operation 3). The consumer NF 310 uses the analysis information received from the NWDAF 305 in the process of determining control parameters and operations for its own functions.
[0051] The NWDAF 305 collects the necessary data from the NFs 315 in the network to provide the analysis information requested by the consumer NF 310. The data collection by the NWDAF 305 is performed based on the subscription by the NF. The source NF 315 receives the subscription request of the NWDAF 305 and provides the requested network data.
[0052] In a wireless communication network, due to the movement of a terminal or fluctuations in network load, the NF that processes the terminal's signaling messages may change depending on its location and time. During this process, the network entity associated with the terminal may change from demand NF#1 to demand NF#2, or from source NF#1 to source NF#2. As a result, the subscription between the NWDAF and demand NF#1 becomes invalid, and for network automation, the changed demand NF#2 must start the subscription procedure to the NWDAF from the beginning. Furthermore, because the subscription between the NWDAF and source NF#1 is also invalid, the NWDAF must cancel the subscription and perform the subscription procedure with source NF#2 again. This additional procedure increases the signaling message load within the network.
[0053] Similar to the coverage of some NFs, an NWDAF has a limited coverage area. For example, the coverage area of an NWDAF may occupy the entire public land mobile network (PLMN) corresponding to an operator's network, or an operator may have multiple NWDAFs within the network, each with its own coverage area. In such cases, technologies are needed to facilitate data collection and analysis while supporting mobility between NWDAFs.
[0054] FIG. 4 is a diagram illustrating problems that may arise due to NWDAF reassignment in a wireless communication network including multiple NWDAFs.
[0055] Referring to Figure 4, NWDAF#1 (405) is subscribed to source NF#1 (420) for data collection, and consumer NF#1 (415) is subscribed to NWDAF#1 (405) for requesting analysis information. Due to certain criteria (e.g., terminal mobility and / or network load distribution), NWDAF reassignment from NWDAF#1 (405) to NWDAF#2 (410) may occur. As a result, the subscription between NWDAF#1 (405) and consumer NF#1 (415) and the subscription between NWDAF#1 (405) and source NF#1 (420) may no longer be valid, and for network automation, consumer NF#1 (415) may need to resubscription to the new NWDAF#2 (410). Furthermore, since the subscription between NWDAF#1 (405) and source NF#1 (420) is no longer valid, NWDAF#2 (405) must perform a subscription procedure with source NF#1 (420) for data collection. This additional procedure increases the signaling message load in the network.
[0056] In order to solve the above problems, the present invention proposes an embodiment for supporting mobility of NWDAF.
[0057] 5 illustrates a mobility management procedure with NWDAF reassignment in a wireless communication network according to an embodiment of the present invention. Various embodiments of the present invention may include at least one of the operations described below.
[0058] Referring to FIG. 5, NWDAF#1 (505) detects that a terminal has moved into the service area of NWDAF#2 (510). In one embodiment, NWDAF#1 (505) determines that the analysis task of the terminal needs to be transferred to another NWDAF (e.g., NWDAF#2 (510)) for some reason, for example, for load balancing purposes. To identify a handover candidate, NWDAF#1 (505) queries the NRF (Network Repository Function) 515, which manages network function profiles, for relevant information as in operation 1), and, referring to the information received from the NRF 515, selects a new NWDAF (e.g., NWDAF#2 (510)) suitable for the terminal and performs an NWDAF reassignment procedure. Here, NWDAF#1 (505) becomes the source NWDAF and NWDAF#2 (510) becomes the target NWDAF. For example, the NWDAF #1 (505) transmits at least one of the following information to the NRF 515: the terminal location, the subscribed analysis information, the customer NF list, and the target area. Here, the target area refers to the service area including the destination to which the terminal moves. Based on the above information, the NRF 515 responds to the source NWDAF #1 (505) with information about the target NWDAF #2 (510).
[0059] The source NWDAF#1 (505) sends a message to the selected target NWDAF#2 (510) requesting the transfer of registered subscriptions as in operation 2). The target NWDAF#2 (510) selects subscriptions it wishes to support from the list of subscriptions received via the above message, includes the list of selected subscriptions in a response message, and transmits the list of selected subscriptions to the source NWDAF 505 as in operation 3). The source NWDAF 505 updates information about the selected subscriptions using the list of selected subscriptions provided by the target NWDAF 510, and performs a procedure to update the subscription information of the consumer NF 525 and the source NF 520 in operation 4). In one embodiment, in operation 4), the source NWDAF#1 (505) sends information about the updated subscriptions to the consumer NF 525 and cancels the subscription of the source NF 520. In one embodiment, in operation 5), the source NWDAF#1 (505) notifies the target NWDAF#2 (510) that the subscription renewal is complete and conveys the network data collected from the source NF520.
[0060] In one embodiment, the target NWDAF #2 (510) performs additional update procedures with the source NF 520 and the consumer NF 525, as necessary, as in operation 6), to complete the subscription information update procedure due to NWDAF reassignment.
[0061] 6 illustrates a mobility management procedure with a change of source NF in a wireless communication network according to an embodiment of the present invention. Various embodiments of the present invention may include at least one of the following operations:
[0062] Referring to Figure 6, NF#1 (620) belongs to the service area of NWDAF#1 (610), and NF#2 (615) belongs to the service area of NWDAF#2 (605). For example, due to the movement of a terminal, a handover procedure is performed from NF#1 (520) to NF#2 (615). Then, in operation 1), NF#1 (620) identifies itself as the source NF of NWDAF#1 (610) and sends a handover request message to NF#2 (615) including the old NWDAF ID indicating the NWDAF#1 (610) to which it is subscribed and information about the analysis subscription.
[0063] In operation 2), NF#2 (615) sends a handover response message corresponding to the handover request message to NF#1 (620), and in operation 3), requests NWDAF#2 (602) to update the subscription. In one embodiment, NWDAF#2 (605) identifies NWDAF#1 (610) based on information (e.g., old NWDAF ID) obtained from NF#2 (615) or from another network entity during the handover process, and requests information about the subscriptions of at least one consumer NF (e.g., including consumer NF 625) and a source NF (e.g., including NF#1 (620)) from NWDAF#1 (610) as in operation 4), and in operation 5), NWDAF#1 (610) responds to NWDAF#2 (605) with the information about the requested subscriptions. NWDAF#2 (605) uses the received subscription information to update the subscriptions with consumer NFs (e.g., including consumer NF 625) and source NFs (e.g., including NF#2 (615)) to complete the NWDAF change procedure. In operation 6), NWDAF#2 (605) notifies consumer NF 625 of the updated subscription information.
[0064] 7a and 7b (hereinafter referred to as FIG. 7) are signal flow diagrams illustrating a mobility management procedure with NWDAF reassignment in a wireless communication network according to an embodiment of the present invention. Various embodiments of the present invention may include at least one of the steps described below.
[0065] 7, in step 711, the NWDAF#1 (704) receives a subscription request message Nnwdaf_Analytics_Subscription Request from the consumer NF 702, requesting the provision of network analysis data. In one embodiment, the subscription request message includes at least one of Analytics ID, Target of Reporting, Event Reporting Information, or Notification ID. Here, the Analytics ID indicates the type of analysis data that the consumer NF 702 wishes to receive, the Target of Reporting indicates the terminal (or a terminal group or all terminals, etc.) that is the target of analysis, and the Event Reporting Information is a parameter that indicates the reporting period, accuracy, filtering information, etc. of the analysis data. The Notification ID is a value set by the consumer NF 702 and is a parameter for distinguishing analysis data report messages (in the illustrated example, it is set to #1).
[0066] In step 712, the NWDAF#1 (704) selects at least one source NF708 that provides source data necessary to provide analysis data from the subscription request message received from the consumer NF702, and transmits an event subscription request message (Nnf_Event_Subscription Request) to the source NF708 to request the provision of data. In one embodiment, the event subscription request message includes at least one of an Event ID for indicating the type of data to be received, Reporting Information for specifying the reporting period and the format of the reporting data, etc., or a Notification ID (set to #2 in the illustrated example) specified by the NWDAF#1 (704) to distinguish the reporting message that conveys data to the NWDAF#1 (704).
[0067] In step 713, the source NF 708, which has received the event subscription request message from the NWDAF#1 (704), sends an event subscription response message Nnf_Event_Subscription Response including an acknowledgement of the subscription request of step 712 to the NWDAF#1 (704). In one embodiment, the event subscription response message includes, along with the Event ID, a Subscription ID set by the source NF 708 to identify the subscription request (set to #2 in the illustrated example).
[0068] In step 714, the NWDAF#1 (704) sends a subscription response message Nnwdaf_Analytics_Subscription Response to the consumer NF 702, which message includes acceptance of the subscription request of step 711. In one embodiment, the subscription response message includes at least one of an Analytics ID, a Target of Reporting, Event Reporting information, or a Subscription ID (set to #1 in the illustrated example) set by the NWDAF#1 (704) to identify the subscription request. The Subscription ID and Notification ID are used as identifiers to identify the required subscription when updating the subscription in response to mobility in a subsequent step.
[0069] In step 715, the NWDAF#1 (704) determines that an NWDAF change is necessary according to predetermined criteria (e.g., including at least one of terminal movement and / or network load balancing). In one embodiment, this determination may be based on the terminal moving out of the service area of the NWDAF#1 (704). In one embodiment, the above determination is made by analyzing data collected from the NF or based on signaling messages generated in the terminal's mobility management procedure. These determination procedures can be performed in various ways depending on the implementation, and details will be omitted.
[0070] In step 716, the NWDAF#1 (704) sends an NF information request message (Nnf_NFInfo_Request) to the NRF 710, which provides profile information of each NF, to select a target NWDAF for transferring the subscription (i.e., the analytics subscription). In one embodiment, the NF information request message includes at least one of an NF type indicating the type of NF requested by the NWDAF#1 (704), an Analytics ID specifying the type of analytics data the target NWDAF should provide, a target area specifying the desired service area, the location of the terminal, and a terminal identifier. In one embodiment, the NF information request message includes the NF type set to a value representing “NWDAF” to request candidates for selecting a target NWDAF. In response to the request from the NWDAF#1 (704), the NRF 710 transmits to the NWDAF#1 (704) information on at least one NWDAF that provides the specified type of analytics data and is in the specified service area and may be a candidate for subscription transfer.
[0071] In step 717, based on the received information, NWDAF#1 (704) selects NWDAF#2 (706) as the target NWDAF and sends a Subscription Transfer Request message to NWDAF#2 (706) to transfer network data analysis subscriptions (i.e., analytics subscriptions). The Subscription Transfer Request message includes subscription information for the subscriptions requested for transfer. In one embodiment, the subscription information includes subscription parameters that the source NWDAF#1 (704) has established with the consumer NF 702 and information about event subscriptions that the source NWDAF#1 (704) has established with each source NF for which it provides analytics data.
[0072] In one embodiment, in the case of an analytics data subscription with the consumer NF 702, {Analytics ID, Target of Reporting, Event Reporting Information, Notification ID, Subscription ID, Consumer NF ID, etc.} is included in the subscription information. In one embodiment, in the case of an event subscription with the source NF 708, {Event ID, Reporting Information, Notification ID, Subscription ID, NF ID, etc.} may be included in the subscription information. In one embodiment, the Subscription ID and Notification ID of each subscription in the subscription information may be set to values set to identify each subscription during the subscription process.
[0073] In step 718, the target NWDAF#2 (706) selects subscriptions (i.e., analysis subscriptions) that it intends to support based on the subscription information received via the subscription transfer request message, and transmits the subscription information for the selected subscriptions to the source NWDAF#1 (704) in a subscription transfer response message. In one embodiment, the target NWDAF#2 (706) modifies at least one parameter (e.g., including the reporting period and / or reporting information) for each selected subscription as needed, and transmits the modified at least one parameter to the source NWDAF#1 (704) in the subscription information transmitted in the subscription transfer response message. In one embodiment, the target NWDAF#2 (706) sets a new Notification ID (set to #3 in the illustrated example) for each selected subscription, and transmits the set new Notification ID to the source NWDAF#1 (704) in the subscription information transmitted in the subscription transfer response message.
[0074] In steps 719 and 720, the source NWDAF#1 (704) updates the subscription information for the source NF 708 and the subscriptions using the subscription information for the subscriptions transmitted by the target NWDAF#2 (706). In one embodiment, the source NWDAF#1 (704) sends an event subscription request message to the source NF 708, including the new Notification ID (=#3) received from the target NWDAF#2 (706) and NWDAF#2, which is the identifier of the target NWDAF#2 (706). In one embodiment, for each subscription, the value of the Subscription ID received from the source NF 708 in step 713 is maintained as is in the event subscription request message. The source NF (708) finds the subscription to update based on the value of the Subscription ID received via the event subscription request message. Furthermore, the target NWDAF#2 (706) maintains the subscription using the same value of the Subscription ID and receives data from the source NF 708 based on the subscription.
[0075] In steps 721 and 722, the source NWDAF#1 (704) uses the subscription information of the selected subscriptions received in step 718 to identify subscriptions that have not been selected by the target NWDAF#2 (706), requests the source NF708 to unsubscribe from the subscriptions that have not been selected by the target NWDAF#2 (706), and receives a response thereto.
[0076] In step 723, the source NWDAF #1 (704) sends a subscription response message to the consumer NF 702 requesting that the selected subscriptions received from the target NWDAF #2 (706) be updated. In one embodiment, the subscription response message includes, for each subscription to be updated, at least one of the Subscription ID set by the target NWDAF #2 (706) (set to #3 in the illustrated example) and the new NWDAF ID set as the identifier value of the target NWDAF #2 (706).
[0077] In one embodiment, for each subscription, the value of Notification ID received from the consumer NF 702 in step 711 is maintained as is in the subscription response message for update in step 723. The target NWDAF#2 (706) reports analysis data to the consumer NF 702 using the same value of Notification ID.
[0078] In one embodiment, in order for the consumer NF702 to understand that step 723 relates to a subscription that replaces the existing Subscription ID#1 between the source NWDAF#1 (704) and the consumer NF702, the target NWDAF#2 (706) includes at least one of the subscription information received from the source NWDAF#1 (704), the previous Subscription ID#1, or the Notification ID that the consumer NF702 set during the subscription creation process with the source NWDAF#1 (704) in a subscription response message Mnwdaf_Analytics_Subscription Response and sends it to the consumer NF702.
[0079] In step 724, the source NWDAF#1 (704) sends a Subscription Transfer Complete message to the target NWDAF#2 (706) notifying that the updates for the selected subscriptions have been completed. In one embodiment, the Subscription Transfer Complete message includes subscription information for the subscriptions being transferred from the source NWDAF#1 (704) to the target NWDAF#2 (706). In one embodiment, the Subscription Transfer Complete message transmits history data for each subscription to the target NWDAF#2 (706), including at least one of data previously collected by the source NWDAF#1 (704) from the source NF708 and analytical data reported by the source NWDAF#1 (704) to the consumer NF702. Upon receiving the Subscription Transfer Complete message, the target NWDAF#2 (706) is now able to communicate with the consumer NF702 and the source NF708 using the updated subscription information for the selected subscriptions.
[0080] In one embodiment, at least one of step 725, step 726, and step 727 can replace at least one of step 719, step 720, and step 723. In this embodiment, instead of the source NWDAF#1 (704) performing the subscription renewal process, the target NWDAF#2 (706) selects subscriptions to be renewed based on the subscription information received from the source NWDAF#1 (704), and performs the subscription renewal process with the consumer NF702 and the source NF708 for the selected subscriptions.
[0081] In steps 725 and 726, the target NWDAF#2 (706) updates the subscription information of the source NF708 and the subscription using the subscription information of the selected subscription. In one embodiment, the target NWDAF#2 (706) sends an event subscription request message to the source NF708, including the new value of Notification ID (=#3) set by the target NWDAF#2 (706) and the target NWDAF ID that identifies the target NWDAF#2 (706). In one embodiment, for each subscription, the value of the Subscription ID received from the source NF708 in step 713 is maintained as is in the event subscription request message. The source NF708 finds the subscription to update based on the value of the Subscription ID received via the event subscription request message. Furthermore, the target NWDAF#2 (706) maintains the subscription using the same value of the Subscription ID and receives data from the source NF708 based on the subscription.
[0082] In step 727, the target NWDAF#2 (706) sends a subscription response message to the consumer NF 702 requesting that the subscription information be updated for the selected subscriptions. In one embodiment, the subscription response message includes, for each subscription to be updated, at least one of the Subscription ID set by the target NWDAF#2 (706) (set to #3 in the illustrated example) and the new NWDAF ID set as the identifier of the target NWDAF#2 (706).
[0083] When steps 725, 726, and 727 are performed, steps 719, 720, and 723 can be omitted. In one embodiment, although not shown in this example, a procedure is performed to cancel subscriptions with the consumer NF 702 for subscriptions that are not selected in the process of performing step 723 or step 727. In one embodiment, after step 723 or step 727, a cancellation procedure similar to steps 720 and 721 is performed, for example.
[0084] In one embodiment, when step 727 is executed, the target NWDAF#2 (706) includes at least one of the subscription information received from the source NWDAF#1 (704), the previous Subscription ID#1, and the Notification ID#1 provided by the consumer NF702 in a subscription response message Nnwdaf_Analytics_Subscription Response and sends it to the consumer NF702 so that the consumer NF702 knows that step 727 relates to a subscription that replaces the existing Subscription ID#1 between the source NWDAF#1 (704) and the consumer NF702.
[0085] In one embodiment, although omitted in this example, depending on the implementation, after step 727, a message (e.g., a subscription transfer completion message) reporting that the subscription update requested by the source NWDAF#1 (704) has been completed by the target NWDAF#2 (706) with the source NF708 and the consumer NF702 may be transmitted from the target NWDAF#2 (706) to the source NWDAF#1 (704). In one embodiment, the subscription transfer completion message of step 727 may include the Notification ID#1 obtained in step 711 and the old subscription ID#1 obtained in step 714.
[0086] 8 is a signal flow diagram illustrating a mobility management procedure initiated by a target NWDAF in a wireless communication network according to an embodiment of the present invention. The illustrated procedure is similar to that of FIG. 7 described above, with the difference that a target NWDAF is selected by a consumer NF and a subscription transfer procedure is performed by the target NWDAF. Various embodiments of the present invention may include at least one of the steps described below.
[0087] Referring to FIG. 8, in step 0, consumer NF#1 (802) is subscribed to source NWDAF#1 (806) for data analysis, and source NWDAF#1 (806) is subscribed to source NF810 for data collection.
[0088] Steps 811 and 812 illustrate a case where subscription information is transmitted between consumer NFs (802, 804) during a mobility management process, and the specific procedures may vary depending on the implementation. In step 811, the consumer NF#2 (804) recognizes that an NWDAF change and / or a consumer NF change has occurred based on a predetermined criterion (e.g., UE mobility and / or network load distribution), and transmits a Handover Context Request message to the consumer NF#1 (802), which is the handover source, requesting information for handover. In one embodiment, the Handover Context Request message includes a UE ID that identifies the consumer that is the target of handover, analytics supported information that indicates the type of analytical data that the consumer NF#2 (804) intends to use, along with other handover-related parameters.
[0089] In step 812, the consumer NF#1 (802) refers to the analytics supported information provided by the consumer NF#2 (804) along with the UE ID and the UE context, and includes the old NWDAF ID, which is the identifier of the NWDAF#1 (806) to which the consumer NF#1 (802) is subscribed, and the subscription information of the currently configured subscription in a handover context response message and sends it to the consumer NF#2 (804). In one embodiment, the handover context response message includes the identifier of the network data analysis function without the subscription information, and the consumer NF#2 (804) receives the subscription information directly from the new NWDAF in a later step.
[0090] In step 813, the consumer NF#2 (804) selects a desired subscription based on the subscription information of the received subscription, and sends a subscription request message including the subscription information of the selected subscription to the NWDAF#2 (808). In one embodiment, the subscription information includes at least one of an Analytics ID, a Target of Reporting, Event Reporting Information, or a Notification ID (set to #1 in the illustrated example) associated with the subscription information. In one embodiment, the subscription request message includes the old NWDAF ID received from the consumer NF#1 (802), and the NWDAF#2 (808) recognizes that the subscription request message was sent for a mobility update based on the old NWDAF ID.
[0091] In step 814, NWDAF#2 (808) finds NWDAF#1 (806) based on the old NWDAF ID and sends a subscription transfer request message to NWDAF#1 (806) requesting subscription information related to the subscriptions configured for the terminal. In one embodiment, the subscription information included in the subscription transfer request message includes information for identifying each of the selected subscriptions, and NWDAF#1 (806) selects each subscription related to the terminal from the above information. In step 815, in response to the subscription transfer request message, NWDAF#1 (806) sends a subscription transfer response message to NWDAF#2 (808) including at least one of the UE ID, subscription information, collected data, or historical data.
[0092] In step 816, the NWDAF#2 (808) sends a subscription response message for updating the subscription information to the consumer NF#2 (804), and in steps 817 and 818, exchanges a subscription request message and a subscription response message for updating the subscription information with the source NF 810. In one embodiment, the subscription response message transmitted from the NWDAF#2 (808) to the consumer NF#2 (804) in step 816 includes a Subscription ID newly assigned by the NWDAF#2 (808) for the updated subscription.
[0093] In step 819, a subscription transfer completion message notifying that the renewal of the selected subscription has been completed may be received by NWDAF#1 (806) from NWDAF#2 (808). In steps 820 and 821, NWDAF#1 (806) performs a subscription cancellation procedure with the source NF 810 for subscriptions that have not been selected (e.g., including the subscription with Subscription ID#x).
[0094] FIG. 9 is a diagram illustrating mobility management in a wireless communication network having a hierarchical NWDAF structure according to an embodiment of the present invention.
[0095] Referring to FIG. 9, there are local NWDAFs #1 and #2 (915 and 920) that are individually associated with each consumer NF #1 and #2 (925 and 930). The central NWDAF 905 collects network data from the source NF #1 (935) and transmits analysis data to the consumer NFs (925 and 930) via the local NWDAFs #1 and #2 (915 and 920). In one embodiment, the central NWDAF 905 transmits the data collected from the source NF #1 (935) to the local NWDAFs #1 and #2 (915 and 920). The local NWDAFs #1 and #2 (915 and 920) transmit analysis data for the consumer NFs #1 and #2 (925 and 930) that is generated based on the collected data to the consumer NFs #1 and #2 (925 and 930).
[0096] In the illustrated network, the NWDAFs (905, 915, 920) are configured in multiple stages, with some analysis data provided by the central NWDAF 905 and subscription information for some analyses changing during the mobility process. During the mobility process, subscriptions to some analyses are transferred from the local NWDAF 915 or 920 to the central NWDAF 905 or from the central NWDAF 905 to the local NWDAF 915 or 920. In one embodiment, the local NWDAF 915 or 920 is implemented in conjunction with a consumer NF 925 or 930. In this case, signaling between the local NWDAF 915 or 920 and the consumer NF 925 or 930 can be replaced with internal signaling.
[0097] 10a and 10b (hereinafter referred to as FIG. 10) are signal flowcharts illustrating a procedure for updating subscription information to support mobility when a local NWDAF associated with a consumer NF exists in a wireless communication network according to an embodiment of the present invention. Various embodiments of the present invention include at least one of the following operations.
[0098] Referring to Figure 10, in step 0, consumer NF#1 (1002) is subscribed to local NWDAF#1 (1006) for data analysis, and local NWDAF#1 (1006) is subscribed to source NF 1012 for data collection. Consumer NF#1 (1002) is associated with local NWDAF#1 (1006), and consumer NF#2 (1004) is associated with local NWDAF#2 (1008).
[0099] The operations in steps 1021 to 1026 and step 1029 are the same as those in steps 811 to 816 and step 819 in FIG.
[0100] After completing the subscription information transfer procedure via steps 1024 to 1026, the local NWDAF#1 (1006) sends an analytics unsubscription request message, Nnwdaf_Analytics_Unscription Request, to the central NWDAF 1010 in step 1027. In one embodiment, the analytics unsubscription request message may include the Subscription ID (e.g., Subscription ID#x) of each subscription to be unsubscribed, along with the Analytics ID. In step 1028, when the local NWDAF#1 (1006) receives an analytics unsubscription response message, Nnwdaf_Analytics_Unsubscription Response, corresponding to the analytics unsubscription request message, from the central NWDAF 1010, the unsubscription at the local NWDAF#1 (1006) is completed.
[0101] During the subscription renewal procedure (e.g., after receiving the subscription transfer response message of step 1025), the new local NWDAF#2 (1008) decides that at least some of the analytics data (e.g., related to at least one analytics subscription) previously provided to the consumer NF#1 (1002) by the previous local NWDAF#1 (1006) will be provided by the central NWDAF 1110 instead of the local NWDAF#2 (1008). In this case, in step 1030, an analytics subscription request message Nnwdaf_Analytics_Subscription Request message for the new subscription request is sent from the local NWDAF#2 (1008) to the central NWDAF (1010).
[0102] In one embodiment, the analytics subscription request message includes an Analytics ID, Reporting Information (and other subscription information), or Subscription ID (set to #1 in the illustrated example) related to the analytics data that the central NWDAF (1010) wants to provide. In step 1031, the central NWDAF (1010) sends an analytics subscription response message Nnwdaf_Analytics_Subscription Response message including the Analytics ID and Subscription ID (set to #1 in the illustrated example) to the local NWDAF #2 (1008) in response to the analytics subscription request message.
[0103] Steps 1030 and 1031 make it possible to change the entity providing analytical data from local NWDAF #1 (1006) to central NWDAF (1010) during the process of changing from local NWDAF #1 (1006) to local NWDAF #2 (1008).
[0104] In one embodiment, when data collection of the source NF (1012) is performed via the central NWDAF (1010), the subscriptions related to the data collection of the central NWDAF (1010) are not changed, and therefore the subscription update procedure with the source NF (1012) is omitted.
[0105] 11 illustrates a configuration of a network function (NF) entity according to an embodiment of the present invention. The illustrated configuration can be applied to a consumer NF or a source NF according to at least one of the embodiments of the present invention.
[0106] 11 , the NF entity includes a transceiver 1110, a memory 1115, and a processor 1105. The transceiver 1110, the memory 1115, and the processor 1105 of the NF entity operate in accordance with the above-described NF operation. The configuration of the NF entity is not limited to the example shown in the figure; for example, the NF entity may be configured to include more or fewer components. The transceiver 1110, the memory 1115, and the processor 1105 may be embodied in at least one chip. In one embodiment, the NF entity may include at least one of entities included in the RAN and the core network, such as an AMF, an SMF, or a UPF.
[0107] The transceiver 1110 may be configured to transmit and receive signaling messages, collected data, and analyzed data to and from a terminal, another NF entity, or an NWDAF. The memory 1115 may be configured to store programs and data necessary for the operation of the NF entity. Furthermore, the memory 1115 may be configured to store control information or data included in signals acquired by the NF entity. The memory 1115 may be configured as a storage medium or a combination of storage media, such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, or a DVD. The memory 1115 may also be configured as a plurality of memories.
[0108] The processor 1115 according to an embodiment of the present invention controls a series of operations to cause the NF entity to operate in accordance with at least one of the above-described embodiments. According to some embodiments, the NF entity subscribes to an NWDAF, sends a request for available analysis data, and receives a response including the available analysis data from the NWDAF. According to some embodiments, the NF entity receives a subscription request from an NWDAF and sends collected data to the subscribed NWDAF. According to some embodiments, the NF entity exchanges signaling messages and subscription information to support mobility with other NF entities and NWDAF entities. The processor 1105 performs only some of the operations of the above-described embodiments, but is not limited to this, and the processor 1105 controls all processes to cause the NF entity to operate in accordance with all or part of the above-described embodiments.
[0109] 12 illustrates a configuration of an NWDAF entity according to one embodiment of the present invention. The illustrated configuration may be applied to a source NWDAF, a target NWDAF, a local NWDAF, or a central NWDAF according to at least one of the embodiments of the present invention.
[0110] 12, the NWDAF entity includes a transceiver 1210, a memory 1215, and a processor 1205. The transceiver 1210, the memory 1215, and the processor 1205 of the NWDAF entity operate in accordance with the NWDAF operations described above. The configuration of the NWDAF entity is not limited to the example shown in the figure; for example, the NWDAF entity may be configured to include more or fewer components. The transceiver 1210, the memory 1215, and the processor 1205 may be embodied in at least one chip.
[0111] The transceiver 1210 may be configured to transmit and receive signaling messages, collected data, and analyzed data to and from the NF entity. The memory 1215 may be configured to store programs and data necessary for the operation of the NWDAF entity. Furthermore, the memory 1215 may be configured to store control information or data included in signals acquired by the NWDAF entity. The memory 1215 may be comprised of a storage medium or combination of storage media, such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, or a DVD. The memory 1215 may also be comprised of multiple memories.
[0112] The processor 1215 according to an embodiment of the present invention controls a series of operations to enable the NWDAF entity to operate in accordance with at least one of the above-described embodiments. According to some embodiments, the NWDAF entity receives subscription requests for data analysis from consumer NFs and transmits responses to the subscribed consumer NFs that include available analyzed data. According to some embodiments, the NWDAF entity transmits subscription requests to source NFs and receives collected data from the source NFs. According to some embodiments, the NWDAF exchanges signaling messages and subscription information to support mobility with at least one NF and other NWDAFs. The processor 1205 may perform only some of the operations of the above-described embodiments, but is not limited thereto. The processor 1205 may control all processes to enable the NWDAF entity to operate in accordance with all or part of the above-described embodiments.
[0113] According to various embodiments, a method for mobility support by a Network Data Collection and Analysis Function (NWDAF) entity in a wireless communication network includes determining a transfer of one or more analysis subscriptions to at least one Network Function (NF); determining a target NWDAF to which to transfer the one or more analysis subscriptions based on at least one of a terminal location, one or more analysis subscriptions, at least one consumer NF, and a target area; sending a subscription transfer request message to the target NWDAF, the subscription transfer request message including first subscription information related to the one or more analysis subscriptions; receiving a subscription transfer response message from the target NWDAF, the subscription transfer response message including second subscription information related to at least one analysis subscription generated based on the first subscription information; and requesting, based on the second subscription information, a source NF to unsubscribe from the at least one analysis subscription.
[0114] In one embodiment, the second subscription information includes at least one of an Analytics ID, a Target of Reporting, an Event Reporting Information, a Notification ID, a Subscription ID, and a Consumer NF ID for an analytics subscription with the consumer NF.
[0115] In one embodiment, the second subscription information includes at least one of an Event ID, Reporting Information, a Notification ID, a Subscription ID, and an NF ID for an analysis subscription with the source NF.
[0116] In one embodiment, the second subscription information includes, for each of the at least one analytical subscription, a Notification ID set to a new value and a Subscription ID set to the same value as in the first subscription information.
[0117] In one embodiment, the method may further include a step of requesting a subscription renewal of a corresponding analysis subscription among the at least one analysis subscription from the consumer NF based on the second subscription information.
[0118] A method for mobility assistance by a Network Data Collection and Analysis Function (NWDAF) entity in a wireless communication network according to various embodiments includes receiving a subscription transfer request message from a source Network Function (NF), the subscription transfer request message including first subscription information related to one or more analysis subscriptions for at least one NF; transmitting a subscription transfer response message to the source NWDAF, the subscription transfer response message including second subscription information related to at least one analysis subscription generated based on the first subscription information; and transmitting a subscription request message to a source NF associated with one of the at least one analysis subscription based on the second subscription information.
[0119] In one embodiment, the second subscription information includes at least one of an Analytics ID, a Target of Reporting, an Event Reporting Information, a Notification ID, a Subscription ID, and a Consumer NF ID for an analytics subscription with the consumer NF.
[0120] In one embodiment, the second subscription information includes at least one of an Event ID, Reporting Information, a Notification ID, a Subscription ID, and an NF ID for an analysis subscription with the source NF.
[0121] In one embodiment, the second subscription information includes, for each of the at least one analytical subscription, a Notification ID set to a new value and a Subscription ID set to the same value as in the first subscription information.
[0122] In one embodiment, the subscription request message includes the target NWDAF ID and the Notification ID set to the new value.
[0123] In one embodiment, the subscription request message further includes a Subscription ID set to the same value as the first subscription information.
[0124] In one embodiment, the method may further include sending, to the consumer NF, a subscription update request message for the analysis subscription among the at least one analysis subscription, based on the second subscription information.
[0125] In one embodiment, the subscription update request message includes a New NWDAF ID and at least one of the first subscription information or a Subscription ID obtained from the first subscription information for the corresponding analysis subscription.
[0126] According to various embodiments, an apparatus for a Network Data Collection and Analysis Function (NWDAF) entity in a wireless communication network may include a transceiver and a processor operatively coupled to the transceiver, wherein the processor may be configured to: determine a transfer of one or more analysis subscriptions to at least one Network Function (NF); determine a target NWDAF to transfer the one or more analysis subscriptions to based on at least one of a terminal location, the one or more analysis subscriptions, the at least one consumer NF, and a target area; send a subscription transfer request message to the target NWDAF, the subscription transfer request message including first subscription information for the one or more analysis subscriptions; receive from the target NWDAF a subscription transfer response message including second subscription information for the at least one analysis subscription generated based on the first subscription information; and request the source NF to unsubscribe from the at least one analysis subscription based on the second subscription information.
[0127] According to various embodiments, an apparatus for a Network Data Collection and Analysis Function (NWDAF) entity in a wireless communication network may include a transceiver and a processor operatively coupled to the transceiver, wherein the processor may be configured to receive a subscription transfer request message from a source NWDAF, the subscription transfer request message including first subscription information related to one or more analysis subscriptions for at least one network function (NF), send a subscription transfer response message to the source NWDAF, the subscription transfer response message including second subscription information related to the at least one analysis subscription generated based on the first subscription information, and send a subscription request message to a source NF associated with one of the at least one analysis subscription based on the second subscription information.
[0128] Meanwhile, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples presented to easily explain the technical content of the present invention and facilitate understanding of the present invention, and are not intended to limit the technical scope of the present invention. In other words, it is obvious to those skilled in the art that other modifications based on the technical concept of the present invention are possible. Furthermore, the above-described embodiments can be combined with each other as needed. For example, at least a portion of each of the embodiments of the present invention can be combined with each other and operated by a base station or a terminal.
[0129] In the specific embodiments of the present invention described above, elements included in the disclosure are expressed in the singular or plural form according to the specific embodiment presented. However, the expressions in the singular or plural form are selected to suit the presented situation for the convenience of explanation, and the present invention is not limited to the singular or plural elements, and elements expressed in the plural form may be composed in the singular form, and elements expressed in the singular form may be composed in the plural form.
[0130] The embodiments disclosed in the specification and drawings are merely specific examples that are presented to easily explain the technical contents of the present invention and to facilitate understanding of the present invention, and are not intended to limit the scope of the present invention. Furthermore, the above-described embodiments of the present invention are merely examples, and it will be understood by those skilled in the art that various modifications and equivalent embodiments are possible. [Explanation of symbols]
[0131] 100 UE (terminal) 105, 305, 405, 410, 605, 610, 808 NWDAF 110 AMF 115 SMF 120 RAN (Radio Access Network) 125, 130, 135 UPF 140 DN (Data Network) 310, 415, 525, 625, 702, 802, 804, 925, 930, 1002, 1004 Consumer NF 315, 420, 520, 708, 810, 935, 1012 Source NF 515, 710 NRF 505, 704, 806 Source NWDAF 510, 706 Target NWDAF 615, 620 NF 905, 1010 Central NWDAF 915, 920, 1006, 1008 Local NWDAF 1105, 1205 processors 1110, 1210 Transmitter / Receiver 1115, 1215 memory
Claims
1. 1. A method by a source Network Data Collection and Analysis Function (NWDAF) entity, comprising: determining, based on at least one of a terminal (UE) movement event, UE location information, or information for at least one consumer network function (NF), to transfer one or more analysis subscriptions associated with the at least one consumer NF to a target NWDAF; sending a subscription transfer request message to the target NWDAF, the message including information about the one or more analysis subscriptions to be transferred; and after sending the subscription transfer request message, receiving a subscription transfer response message related to the one or more analysis subscriptions to be transferred from the target NWDAF.
2. The information regarding the one or more analytics subscriptions to be transferred includes:
2. The method of claim 1, wherein the analytics subscription for the consumer NF includes at least one of an Analytics ID, a Target of Reporting, an Event Reporting Information, a Notification ID, a Subscription ID, or a Consumer NF ID.
3. The information regarding the one or more analytics subscriptions to be transferred includes:
2. The method of claim 1, wherein for an analytical subscription of a source NF, the method includes at least one of an Event ID, a Reporting Information, a Notification ID, a Subscription ID, and an NF ID.
4. The subscription transfer response message comprises:
2. The method of claim 1, wherein the target NWDAF includes, for each analysis subscription selected, a Notification ID set to a new value and a Subscription ID set to the same value as each analysis subscription included in the subscription transfer request message.
5. requesting a subscription renewal from the consumer NF for at least one of the one or more analytical subscriptions; or 10. The method of claim 1, further comprising at least one of the steps of requesting a source NF to unsubscribe from at least one analytic subscription of the one or more analytic subscriptions.
6. In a source Network Data Collection and Analysis Function (NWDAF) entity device, a transceiver and a processor operatively connected to the transceiver; The processor: Determine to transfer one or more analysis subscriptions associated with the at least one consumer network function (NF) to a target NWDAF based on at least one of a terminal (UE) movement event, UE location information, or information for at least one consumer network function (NF); sending a subscription transfer request message to the target NWDAF, the message including information about the one or more analysis subscriptions to be transferred; and after sending the subscription transfer request message, receiving from the target NWDAF a subscription transfer response message related to the one or more analysis subscriptions to be transferred.
7. The information regarding the one or more analytics subscriptions to be transferred includes:
7. The apparatus of claim 6, wherein the analytics subscription for the consumer NF includes at least one of an Analytics ID, a Target of Reporting, an Event Reporting Information, a Notification ID, a Subscription ID, or a Consumer NF ID.
8. The information regarding the one or more analytics subscriptions to be transferred includes: The apparatus of claim 6 , wherein for an analytical subscription of a source NF, the information includes at least one of an Event ID, a Reporting Information, a Notification ID, a Subscription ID, and an NF ID.
9. The subscription transfer response message comprises:
7. The apparatus of claim 6, wherein the target NWDAF includes, for each analysis subscription selected, a Notification ID set to a new value and a Subscription ID set to the same value as each analysis subscription included in the subscription transfer request message.
10. The processor: an operation of requesting a subscription renewal for at least one of the one or more analytical subscriptions from the consumer NF; or 7. The apparatus of claim 6, configured to perform at least one of the following operations: requesting a source NF to unsubscribe from at least one analysis subscription of the one or more analysis subscriptions.
11. A method by a targeted Network Data Collection and Analysis Function (NWDAF) entity, comprising: receiving a subscription transfer request message from a source NWDAF, the message including information regarding one or more analysis subscriptions to be transferred associated with at least one consumer NF; in response to receiving the subscription transfer request message, sending a subscription transfer response message associated with the one or more analysis subscriptions to the source NWDAF; sending a subscription request message to a source NF associated with at least one analysis subscription of the one or more analysis subscriptions to be transferred.
12. The information regarding the one or more analytical subscriptions to be transferred includes:
12. The method of claim 11, wherein for each consumer NF analytics subscription, the analytics subscription includes at least one of an Analytics ID, a Target of Reporting, an Event Reporting Information, a Notification ID, a Subscription ID, or a Consumer NF ID.
13. The subscription request message:
12. The method of claim 11, wherein the subscription transfer request message includes at least one of an NWDAF ID of the target NWDAF, a Notification ID set to a new value for each analysis subscription selected by the target NWDAF, and a Subscription ID set to the same value as each analysis subscription included in the subscription transfer request message.
14. The subscription transfer response message:
12. The method of claim 11, wherein the target NWDAF includes, for each analysis subscription selected, a Notification ID set to a new value and a Subscription ID set to the same value as each analysis subscription included in the subscription transfer request message.
15. A target Network Data Collection and Analysis Function (NWDAF) entity device, comprising: A transmitter / receiver, a processor operatively connected to the transceiver; The processor: receiving a subscription transfer request message from a source NWDAF, the message including information regarding one or more analysis subscriptions to be transferred associated with at least one consumer NF; In response to receiving the subscription transfer request message, sending a subscription transfer response message related to the one or more analysis subscriptions to the source NWDAF; 10. The apparatus, comprising: an apparatus configured to send a subscription request message to a source NF associated with at least one analysis subscription of the one or more analysis subscriptions to be transferred.
16. The information regarding the one or more analytical subscriptions to be transferred includes:
16. The apparatus of claim 15, wherein for each consumer NF analytics subscription, the analytics subscription includes at least one of an Analytics ID, a Target of Reporting, an Event Reporting Information, a Notification ID, a Subscription ID, or a Consumer NF ID.
17. The subscription request message:
16. The apparatus of claim 15, further comprising at least one of an NWDAF ID of the target NWDAF, a Notification ID set to a new value for each analysis subscription selected by the target NWDAF, and a Subscription ID set to the same value as each analysis subscription included in the subscription transfer request message.
18. The subscription transfer response message:
16. The apparatus of claim 15, wherein for each analysis subscription selected by the target NWDAF, the notification ID is set to a new value and the subscription ID is set to the same value as for each analysis subscription included in the subscription transfer request message.
Citation Information
Patent Citations
Network data collection method, device and system
CN110677299A