Method and apparatus for supporting mobility of collecting and analyzing network data in a wireless communication network

Abstract

A method and apparatus for supporting mobility of a NWDAF in a wireless communication network are disclosed. The method can include the steps of deciding an analytics subscription of a network function (NF) to be transferred, determining a target NWDAF to which the analytics subscription is to be transferred based on at least one of a terminal location, the analytics subscription, a consumer NF, and a target area, transmitting a subscription transfer request message including first subscription information related to the analytics subscription to the target NWDAF, receiving a subscription transfer response message from the target NWDAF, the subscription transfer response message including second subscription information related to at least one analytics subscription generated based on the first subscription information, and requesting, based on the second subscription information, a subscription cancellation of the corresponding analytics subscription in the at least one analytics request to a source NF.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a method and apparatus for supporting collection and analysis of mobility of network data to automate management of a wireless communication network. BACKGROUND

[0002] To meet increasing demand for wireless data traffic since the 4th generation (4G) communication systems came to the market, efforts have been made to develop enhanced 5th generation (5G) communication systems or pre-5G communication systems. For this reason, 5G communication systems or pre-5G communication systems are called beyond 4G networks or post long term evolution (LTE) / LTE-A systems.

[0003] To achieve a higher data transmission rate, 5G communication systems are considered to be implemented in a super high frequency band (mmWave) such as 60 GHz. To mitigate path loss of the super high frequency band and increase a range of radio waves, 5G communication systems consider the following technologies, such as beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam forming, and large scale antenna.

[0004] Various technologies for enabling 5G communication systems with enhanced network are also being developed, such as evolved or advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-point (CoMP), and reception interference cancellation.

[0005] For 5G systems, other various schemes are also being developed, such as hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM) scheme, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access scheme.

[0006] The Internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the Internet of Things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of the IoT technology and the Big Data processing technology through connection with a cloud server, has emerged as a new paradigm for the IoT.

[0007] As the IoT implementation requires a technical element such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology", research is being conducted in sensor network, machine-to-machine (M2M) communication, machine type communication (MTC), and the like.

[0008] Such an IoT environment can provide intelligent Internet Technology (IT) services that create a new value for humans by collecting and analyzing data generated among connected things. IoT can be applied to a number of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances, and advanced medical services through convergence and combination between existing Information Technology (IT) and various industrial applications.

[0009] Therefore, various efforts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, Machine Type Communication (MTC), and Machine-to-Machine (M2M) communication can be implemented by beamforming, MIMO, and array antennas. Application of a cloud Radio Access Network (RAN) as a big data processing technology as described above can also be considered an example of convergence between the 5G technology and the IoT technology.

[0010] Along with development of mobile communication systems as described above, various services can be provided, and as wireless communication systems become more complex and diverse, a technology that automates management of wireless communication systems is needed. SUMMARY

[0011] TECHNICAL PROBLEM

[0012] The present disclosure defines a method and apparatus for providing network data analytics and collection to automate management of a wireless communication network.

[0013] The present disclosure defines a method and apparatus for supporting mobility of a Network Data Analytics Function (NWDAF) entity that provides network data analytics and collection in a wireless communication network.

[0014] The present disclosure defines a method and apparatus for controlling signal flow between a NWDAF and a network function (NF) in a mobility management procedure.

[0015] The present disclosure defines a method and apparatus for controlling signal flow between NWDAF entities to support mobility.

[0016] The present disclosure defines a method and apparatus for supporting change of a NWDAF caused by mobility of a user equipment (UE) or network load.

[0017] The present disclosure defines a method and apparatus for supporting handover between NWDAF entities caused by mobility of a UE or network load.

[0018] TECHNICAL SOLUTION

[0019] According to an embodiment of the disclosure, a method of supporting mobility of a network data analytics function (NWDAF) entity in a wireless communication network can include determining one or more analytics subscriptions to at least one network function (NF) to be transferred; determining a target NWDAF to which the one or more analytics subscriptions are to be transferred based on at least one of a user equipment (UE) location, the one or more analytics subscriptions, at least one consumer NF, and a target area; transmitting a subscription transfer request message including first subscription information about the one or more analytics subscriptions to the target NWDAF; receiving a subscription transfer response message from the target NWDAF, the subscription transfer response message including second subscription information about at least one analytics subscription generated based on the first subscription information; and requesting, from a source NF, an unsubscription for a corresponding analytics subscription among the at least one analytics subscription based on the second subscription information.

[0020] According to an embodiment of the disclosure, a method of supporting mobility of a NWDAF entity in a wireless communication network can include receiving a subscription transfer request message from a source NWDAF, the subscription transfer request message including first subscription information about one or more analytics subscriptions to at least one NF; transmitting a subscription transfer response message to the source NWDAF, the subscription transfer response message including second subscription information about at least one analytics subscription generated based on the first subscription information, and transmitting a subscription request message related to a corresponding analytics subscription among the at least one analytics subscription to a source NF based on the second subscription information.

[0021] According to an embodiment of the disclosure, a device of a NWDAF entity in a wireless communication network can include a transceiver and a processor operably coupled to the transceiver. The processor can be configured to determine one or more analytics subscriptions to at least one NF to be transferred; determine a target NWDAF to which the one or more analytics subscriptions are to be transferred based on at least one of a UE location, the one or more analytics subscriptions, at least one consumer NF, and a target area; transmit a subscription transfer request message including first subscription information about the one or more analytics subscriptions to the target NWDAF; receive a subscription transfer response message from the target NWDAF, the subscription transfer response message including second subscription information about at least one analytics subscription generated based on the first subscription information; and request, from a source NF, an unsubscription for a corresponding analytics subscription among the at least one analytics subscription based on the second subscription information.

[0022] According to an embodiment of the disclosure, an apparatus of a NWDAF entity in a wireless communication network can include a transceiver and a processor operably coupled to the transceiver. The processor can be configured to: receive, from a source NWDAF, a subscription transfer request message including first subscription information about one or more analytics subscriptions to at least one NF; transmit, to the source NWDAF, a subscription transfer response message including second subscription information about at least one analytics subscription generated based on the first subscription information; and transmit, to a source NF, a subscription request message related to a corresponding analytics subscription among the at least one analytics subscription based on the second subscription information. BRIEF DESCRIPTION OF DRAWINGS

[0023] Figure 1 FIG. 1 is a diagram illustrating a configuration of a wireless communication network including a network data analytics function (NWDAF) according to an embodiment of the disclosure.

[0024] Figure 2 FIG. 2 is a diagram illustrating a signal flow for a network data collection and analytics operation according to an embodiment of the disclosure.

[0025] Figure 3 FIG. 3 is a diagram illustrating an overall structure of a network data collection and analytics system according to an embodiment of the disclosure.

[0026] Figure 4 FIG. 4 is a diagram illustrating a problem possibly caused by NWDAF relocation in a wireless communication network including a plurality of NWDAFs according to an embodiment of the disclosure.

[0027] Figure 5 FIG. 5 is a diagram illustrating a mobility management procedure caused by NWDAF relocation in a wireless communication network according to an embodiment of the disclosure.

[0028] Figure 6 FIG. 6 is a diagram illustrating a mobility management procedure caused by a change of a source network function (NF) in a wireless communication network according to an embodiment of the disclosure.

[0029] Figure 7a and Figure 7b FIG. 7 is a diagram illustrating a signal flow of a mobility management procedure caused by NWDAF relocation in a wireless communication network according to an embodiment of the disclosure.

[0030] Figure 8 FIG. 8 is a diagram illustrating a signal flow of a mobility management procedure initiated by a target NWDAF in a wireless communication network according to an embodiment of the disclosure.

[0031] Figure 9is a diagram illustrating mobility management in a wireless communication network with a hierarchical NWDAF architecture according to an embodiment of the disclosure.

[0032] Figure 10a and Figure 10b is a diagram illustrating a signal flow of a procedure to update a subscription to support mobility in a wireless communication network in a case where there is a local NWDAF associated with a consumer NF according to an embodiment of the disclosure.

[0033] Figure 11 is a diagram illustrating a configuration of an NF entity according to an embodiment of the disclosure.

[0034] Figure 12 is a diagram illustrating a configuration of an NWDAF entity according to an embodiment of the disclosure. DETAILED DESCRIPTION

[0035] Embodiments of the disclosure will be described below with reference to the accompanying drawings.

[0036] Detailed descriptions of well-known functions or structures incorporated herein can be avoided to avoid obscuring the subject matter of the disclosure. Although terms are defined in consideration of functions in the disclosure as described later, the terms can be changed according to the intention or custom of the user or operator. Therefore, the definition should be made according to the meaning of each term.

[0037] For the same reason, some components can be exaggerated, omitted, or schematically illustrated in the drawings. Also, the drawing size of each component does not exactly reflect its actual size. In each drawing, the same reference numerals are assigned to the same or corresponding components.

[0038] The advantages and features of the disclosure and the method of achieving the same will become apparent by referring to the embodiments described below in detail in connection with the accompanying drawings. However, the disclosure can be implemented in various ways, and is not limited to the embodiments set forth herein. Rather, these embodiments are provided so that the disclosure is complete and thorough and fully conveys the scope of the disclosure to those skilled in the art, and the disclosure is limited only by the claims attached hereto.

[0039] It will be understood that each of the blocks of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be loaded onto a general purpose computer, 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 the flowchart block or blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory that can direct a 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 memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block or blocks.

[0040] Furthermore, the respective blocks can illustrate portions of a module, a segment, or a computer that include one or more executable instructions for performing certain logical functions. Moreover, it should be noted that in alternative implementations, the functions of the blocks can be performed in a different order. For example, two blocks that are consecutive can be performed substantially simultaneously according to their functions or can be performed in reverse order.

[0041] As used herein, the term "unit" refers to, but is not limited to, a software or hardware component such as a field programmable gate array (FPGA) or application specific integrated circuit (ASIC) that performs certain tasks. A "unit" can advantageously be configured to reside on the addressable storage medium and configured to execute on one or more processors. Thus, a "unit" can include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functionality provided for in the components and "units" can be combined into fewer components and "units" or further separated into additional components and "units". In addition, the components and "units" can be implemented such that they execute one or more central processing units (CPUs) in a device or a secure multimedia card. Further, in embodiments, a "unit" can include one or more processors and / or a device.

[0042] For ease of description, some terms and names are defined in a communication standard based on the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) (e.g., 5G, NR, LTE, or similar system standards). However, the disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0043] For convenience of description, terms identifying an access node, terms indicating a network entity, terms indicating a message, terms indicating an interface between network entities, and terms indicating various types of identification information used in the following description are given. Accordingly, the present disclosure is not limited to the terms of the following description, and the terms can be replaced by other equivalent terms in technical meaning.

[0044] Although embodiments of the present disclosure are described mainly in the context of a new radio access network (NR), 3GPP, and a packet core (5 system, 5G core network or next generation (NG) core) as a core network specified by a mobile communication standard standardization organization in a 5G mobile communication standard, the subject matter of the present disclosure is applicable to other communication systems having a similar technical background with slight modifications, as judged by one of ordinary skill in the art.

[0045] In the 5G system, a network data collection and analytics function (NWDAF) can be defined to support automation of the network, which is a network function (NF) that provides a function of analyzing and providing data collected from the 5G network. The NWDAF can collect information from the 5G network / store information therein / analyze the information thereof and provide a result to at least one NF, and the analysis result can be independently used in each NF.

[0046] The 5G mobile communication system supports an NF to use a result of network-related data (hereinafter, referred to as network data) collection and analysis by the NWDAF. This is done to provide network data collection and analysis required for each NF in order to efficiently provide a function provided by the NF in a centralized manner. The NWDAF can perform network data collection and analysis using a network slice as a basic unit. However, the scope of the present disclosure is not limited to the unit of the network slice, and the NWDAF can additionally use various pieces of information obtained from a user equipment (UE), a PDU session, an NF state, and / or an external service server (e.g., including quality of service).

[0047] The analysis result from the NWDAF can be delivered to each NF that requested the analysis result, and used to optimize network management functions such as quality of service (QoS) guarantee / improvement, traffic control, mobility management, and / or load balancing.

[0048] A unit node performing each function provided by a 5G network system can be defined as an NF (or referred to as an NF entity or an NF node). The NF can include at least one of, for example, an access and mobility management function (AMF) managing access of a UE to an access network (AN) and mobility of the UE, a session management function (SMF) performing session-related management, a user plane function (UPF) managing a user data plane, or a network slice selection function (NSSF) selecting available network slice instances of a UE.

[0049] Figure 1 is a diagram illustrating a configuration of a wireless communication network including a NWDAF according to an embodiment of the disclosure.

[0050] Referring to Figure 1 , the NWDAF 105 can collect network data from at least one source NF in various ways, for example, NFs in a 5G core network such as the AMF 110, the SMF 115, or the UPFs 125, 130, and 135, an application function (AF) for efficient service provision, a network exposure function (NEF), or an operation, administration, and maintenance (OAM). The AMF 110 can be connected to the UE 100 and a radio access network (RAN) 120, and the UPFs 125, 130, and 135 can connect user traffic of the UE 100 to at least one data network (DN) 140 through the RAN 120.

[0051] Further, the NWDAF 105 can provide analysis of network data collected from the network or externally to at least one consumer NF. The NWDAF 105 can collect and analyze a load level of a network slice instance and provide it to the NSSF so that a specific UE is selected for use. A service-based interface defined in the 5G network can be used to request analysis data or to transfer analysis information including analysis results between the NFs 110 and 115 and the NWDAF 105, and, for example, a hypertext transfer protocol (HTTP) and / or a JavaScript object notation (JSON) file can be used for delivery.

[0052] In an embodiment, data collected by the NWDAF 105 can include at least one of an application identifier (ID), IP filter information, and media / application bandwidth from a point coordination function (PCF), a UE ID or location information from an AMF, a destination data network name (DDN), a UE IP, a QoS flow bit rate, a QoS flow ID (QFI), a QoS flow error rate, and QoS flow delay from an SMF or traffic usage reporting from a UPF.

[0053] The NWDAF can additionally collect at least one of, for example, NF resource status, NF throughput, or service level agreement (SLA) information from an OAM, which is an entity that can affect a connection between a UE and a service server; UE status, UE application information, or UE usage pattern from a UE; or service application ID, service experience, or traffic pattern from an AF and a NF of a core network, and use the additionally collected information for analysis.

[0054] Tables 1 to 3 below illustrate examples of network data collected by the NWDAF. The period and time point of network data collection by the NWDAF from each entity can be different for each entity. In addition, the correlation of the collected data can be identified by a correlation ID for correlating the data of each collection target and a time stamp recording the collection time.

[0055] [Table 1]

[0056]

[0057] [Table 2]

[0058]

[0059]

[0060] [Table 3]

[0061]

[0062] Figure 2 FIG. 1 is an illustration showing an overall structure for collecting and analyzing network data according to an embodiment of the present disclosure.

[0063] Referring to FIG. 1, a network data collection and analysis system according to an embodiment of the present disclosure can include a network data analytics function (NWDAF) 100, a radio access network (RAN) 110, an access and mobility management function (AMF) 120, a session management function (SMF) 130, a user plane function (UPF) 140, a network exposure function (NEF) 150, an application function (AF) 160, and an operations and maintenance (OAM) 170. Figure 2 In operation 210, the NWDAF can collect network data from NFs such as the RAN, the AMF, the SMF, and the UPF, service data from the NEF or the AF in operation 220, management data from the OAM in operation 230, and UE data from the UE in operation 240. Examples of the collected data are shown in Tables 1 to 3. In operation 250, the NWDAF can analyze the collected data and provide the analysis result to the corresponding NF upon request.

[0064] Figure 3 FIG. 2 is an illustration showing an overall structure of a network data collection and analysis system according to an embodiment of the present disclosure.

[0065] Referring to FIG. 2, a network data collection and analysis system according to an embodiment of the present disclosure can include a network data analytics function (NWDAF) 200, a radio access network (RAN) 210, an access and mobility management function (AMF) 220, a session management function (SMF) 230, a user plane function (UPF) 240, a network exposure function (NEF) 250, an application function (AF) 260, and an operations and maintenance (OAM) 270. Figure 3Each network entity (which can be an AMF, an SMF, an OAM, or a RAN included in a core network) can operate as a consumer NF 310 that requests analytics information generated as a result of analytics in the NWDAF 305, as in operation 1). The NWDAF 305 can collect data from source NFs 315, such as NFs, AFs, or OAMs, and analyze the collected data to generate analytics information requested by the consumer NF 310, as in operation 2). As in operation 3), the NWDAF 305 can transmit the analytics information to the consumer NF 310 that has transmitted the request. The consumer NF 310 can use the analytics information received from the NWDAF 305 in determining control parameters and operations of its own functions.

[0066] The NWDAF 305 can collect required data from NFs 315 in the network to provide analytics information requested by the consumer NF 310. Data collection of the NWDAF 305 can be performed based on a subscription of the corresponding NF. The source NF 315 can receive a subscription request from the NWDAF 305 and provide requested network data.

[0067] In a wireless communication network, an NF that processes signaling messages of a UE can become another NF according to a location or a change in a network load due to movement of the UE. In this process, a network entity related to the UE can change from a consumer NF #1 to a consumer NF #2, or from a source NF #1 to a source NF #2. Then, a subscription between the NWDAF and the consumer NF #1 is no longer valid, and for network automation, the changed consumer NF #2 can have to perform a subscription procedure to the NWDAF again from the beginning. In addition, since a subscription between the NWDAF and the source NF #1 is also invalid, the NWDAF should unsubscribe and perform a subscription procedure again with the source NF #2. This additional procedure increases a load of signaling messages in the network.

[0068] Similar to a coverage range of some NFs, the NWDAF can have a limited coverage range. For example, the coverage range of the NWDAF can cover a public land mobile network (PLMN) corresponding to an operator network, or a plurality of NWDAFs each having its coverage range can be developed in an operator network. In this case, techniques can be required to seamlessly process procedure data collection and analytics while supporting mobility between NWDAFs.

[0069] Figure 4 is a diagram illustrating a problem that can occur due to NWDAF relocation in a wireless communication network including a plurality of NWDAFs.

[0070] Reference Figure 4NWDAF #1 405 subscribes to Source NF #1 420 for data collection, and Consumer NF #1 415 subscribes to NWDAF #1 405 for requesting analytics information. NWDAF relocation from NWDAF #1 405 to NWDAF #2 410 can occur due to predetermined criteria (e.g., UE mobility and / or network load balancing). Then, the subscription between NWDAF #1 405 and Consumer NF #1 415 and the subscription between NWDAF #1 405 and Source NF #1 420 will no longer be valid, and Consumer NF #1 415 can have to perform the subscription procedure again with the new NWDAF #2 410. In addition, since the subscription between NWDAF #1 405 and Source NF #1 420 is also invalid, NWDAF #2 405 should perform the subscription procedure with Source NF #1 420 for data collection. This additional procedure increases the signaling message load in the network.

[0071] The present disclosure proposes embodiments for supporting mobility of NWDAF to solve the above problems.

[0072] Figure 5 A mobility management procedure caused by NWDAF relocation in a wireless communication network according to embodiments of the present disclosure is shown. Various embodiments of the present disclosure can include at least one of the following operations.

[0073] Reference Figure 5 NWDAF #1 505 can detect that the UE has moved into the coverage of NWDAF #2 510. In an embodiment, NWDAF #1 505 can determine that it is necessary to transfer the analytics of the UE to another NWDAF (e.g., NWDAF #2 510) for some reason, e.g., for load balancing. NWDAF #1 505 can perform a NWDAF relocation procedure by querying a Network Repository Function (NRF) 515 of network functions profiles managing relevant information to identify handover candidates as in operation 1), and selecting a new NWDAF (e.g., NWDAF #2 510) suitable for the UE referring to the information received from the NRF 515. NWDAF #1 505 is a source NWDAF, and NWDAF #2 510 is a target NWDAF. For example, NWDAF #1 505 can transmit at least one of a UE location, subscribed analytics information, a list of consumer NFs, or a target area to query the NRF 515. The target area means a service area including a destination to which the UE is to move. The NRF 515 can respond to the source NWDAF #1 505 with information about the target NWDAF #2 510 based on the information.

[0074] Source NWDAF #1 505 can transmit a message requesting to transfer the registered subscriptions to the selected target NWDAF #2 510 as in operation 2). Target NWDAF #2 510 can select the subscriptions it wants to support from the list of subscriptions received in the message and transmit a response message including the selected list of subscriptions to source NWDAF 505 as in operation 3). Source NWDAF 505 can update the information about the selected subscriptions using the selected list of subscriptions provided by target NWDAF 510 and in operation 4), perform the procedure to update the subscription information about consumer NF 525 and source NF 520. In an embodiment, source NWDAF #1 505 can transmit the updated information about the subscriptions to consumer NF 525 and unsubscribe from the subscription of source NF 520 in operation 4). In an embodiment, source NWDAF #1 505 can inform target NWDAF #2 510 that the subscriptions have been completely updated and transmit the network data collected from source NF 520 in operation 5).

[0075] In an embodiment, target NWDAF #2 510 can perform additional update procedures with source NF 520 and consumer NF 525 when needed to complete the subscription information update procedure caused by NWDAF relocation as in operation 6).

[0076] Figure 6 A mobility management procedure caused by a change of a source NF in a wireless communication network according to an embodiment of the disclosure is illustrated. Various embodiments of the disclosure can include at least one of the following operations.

[0077] Reference Figure 6 , NF #1 620 belongs to the coverage of NWDAF #1 610 and NF #2 615 belongs to the coverage of NWDAF #2 605. For example, a handover procedure from NF #1 520 to NF #2 615 can be performed by the movement of the UE. Then, in operation 1), NF #1 620 can identify that it is a source NF of NWDAF #1 610 and transmit an old NWDAF ID of NWDAF #1 610 indicating its subscription and information about the analytics subscription to NF #2 615 in a handover request message.

[0078] In operation 2), the NF #2 615 transmits a handover response message corresponding to the handover request message to the NF #1 620, and in operation 3), requests an update of the corresponding subscription from the NWDAF #2 602. In an embodiment, the NWDAF #2 605 can identify the NWDAF #1 610 based on information obtained from the NF #2 615 (e.g., old NWDAF ID) or information obtained from another network entity during the handover procedure, and request information related to the subscription of at least one consumer NF (e.g., including the consumer NF 625) and a source NF (e.g., including the NF #1 620) from the NWDAF #1 610 as in operation 4). In operation 5), the NWDAF #1 610 responds to the NWDAF #2 605 with the requested information related to the subscription. The NWDAF #2 605 completes the NWDAF change procedure by updating the subscription of the consumer NF (e.g., including the consumer NF 625) and the source NF (e.g., the NF #2 615) with the received information related to the subscription. In operation 6), the NWDAF #2 605 can notify the consumer NF 625 of information about the updated subscription.

[0079] Figure 7a and Figure 7b FIG. 7 (hereinafter referred to as FIG. 7) is a diagram illustrating a signal flow of a mobility management procedure caused by NWDAF relocation in a wireless communication network according to an embodiment of the disclosure. Various embodiments of the disclosure can include at least one of the following operations.

[0080] Referring to FIG. 7, in operation 711, the NWDAF #1 704 can receive a subscription request message Nnwdaf_Analytics_Subscription request requesting to provide network analytics data from the consumer NF 702. In an embodiment, the subscription request message can include at least one of an analytics ID, a reporting target, event reporting information, and a notification ID. The analytics ID is a parameter indicating a type of analytics data that the consumer NF 702 wants to receive, the reporting target is a parameter indicating a UE (or a group of UEs or all UEs) to be analyzed, and the event reporting information is a parameter indicating a reporting period, accuracy, and filtering information of the analytics data. The notification ID is a value set by the consumer NF 702, and is a parameter for identifying a reporting message of the analytics data (in the illustrated example, it is set to #1).

[0081] In operation 712, the NWDAF #1 704 can select at least one source NF 708 capable of providing source data required for providing analytics data from the subscription request message received from the consumer NF 702, and transmit an event subscription request message Nnf_Event_Subscription Request requesting data provision to the source NF 708. In an embodiment, the event subscription request message can include at least one of an event ID indicating a type of data to be received, reporting information indicating a reporting period and a reporting data format, or a notification ID set by the NWDAF #1 704 to identify a reporting message carrying data to the NWDAF #1 704 (in the illustrated example, it is set to #2).

[0082] In operation 713, upon receiving the event subscription message from the NWDAF #1 704, the source NF 708 can transmit an event subscription response message Nnf_Event_Subscription Response including acceptance of the subscription request of operation 712 to the NWDAF #1 704. In an embodiment, the event subscription response message can include an event ID and a subscription ID set by the source NF 708 (in the illustrated example, it is set to #2).

[0083] In operation 714, the NWDAF #1 704 can transmit a subscription response message Nnwdaf_Analytics_Subscription Response including acceptance of the subscription request of operation 711 to the consumer NF 702. In an embodiment, the subscription response message can include at least one of an analytics ID, a reporting target, event reporting information, or a subscription ID set by the NWDAF #1 704 to identify the subscription request (in the illustrated example, it is set to #1). The subscription ID and the notification ID can be used as identifiers for identifying the subscription required when updating the subscription according to mobility in a subsequent operation.

[0084] In operation 715, the NWDAF #1 704 can determine that NWDAF relocation is required according to a predetermined criterion (for example, including at least one of UE mobility and / or network load balancing). In an embodiment, the determination can be made based on the fact that the UE has moved out of the coverage range of the NWDAF #1 704. In an embodiment, the determination can be made based on analysis of data collected from NFs or signaling messages generated in a mobility management procedure of the UE. This determination procedure can be performed in various ways according to implementation, and the details thereof will be omitted.

[0085] In operation 716, the NWDAF #1 704 can transmit an NF information request message Nnf_NFInfo_Request to the NRF 710 providing profile information about each NF to select a target NWDAF for a subscription (i.e., analytics subscription) delivery. In an embodiment, the NF information request message can include at least one of: an NF type indicating a type of NF requested by the NWDAF #1 704, an analytics ID specifying a type of analytics data to be provided by the target NWDAF, a target area specifying a desired service area, a UE location, or a UE ID. In an embodiment, the NF information request message can include an NF type set to indicate "NWDAF" in order to request a candidate in which a target NWDAF is to be selected. Upon the request of the NWDAF #1 704, the NRF 710 can transmit information about at least one NWDAF capable of providing a specified type of analytics data and possibly a candidate for delivering a subscription in a specified service area.

[0086] In operation 717, the NWDAF #1 704 can select the NWDAF #2 706 as a target NWDAF based on the received information, and transmit a subscription delivery request message for delivering an analytics subscription (i.e., analytics subscription) of a subscription of network data analytics to the NWDAF #2 706. The subscription delivery request message can include subscription information about the subscription requested to be delivered. In an embodiment, the subscription information can include parameters of the subscription of the source NWDAF #1 704 to the consumer NF 702 and information about an event subscription of each source NF to the source NWDAF #1 704 to provide analytics data.

[0087] In an embodiment, in case of the analytics data subscription of the consumer NF 702, {analytics ID, reporting target, event reporting information, notification ID, subscription ID, consumer NF ID, etc.} can be included in the subscription information. In an embodiment, in case of the event subscription of the source NF 708, {event ID, reporting information, notification ID, subscription ID, NF ID, etc.} can be included in the subscription information. In an embodiment, a subscription ID and a notification ID of each subscription can be set to a value set to identify the subscription in a subsequent procedure in the subscription information.

[0088] In operation 718, the target NWDAF #2 706 can select the subscriptions (i.e., analytics subscriptions) to be supported by the target NWDAF #2 706 based on the subscription information received in the subscription transfer request message, and transmit the subscription information about the selected subscriptions to the source NWDAF #1 704 in a subscription transfer response message. In an embodiment, the target NWDAF #2 706 can change at least one parameter (e.g., including a reporting period and / or reporting information) of each of the selected subscriptions, and transmit the at least one changed parameter in the subscription information delivered in the subscription transfer response message to the source NWDAF #1 704. In an embodiment, the target NWDAF #2 706 can set a new notification ID (in the illustrated example, set to #3) for each of the selected subscriptions, and transmit the new notification ID to the source NWDAF #1 704 in the subscription information included in the subscription transfer response message.

[0089] In operations 719 and 720, the source NWDAF #1 704 can update the subscription information about the subscriptions with the source NF 708 using the subscription information about the subscriptions received from the target NWDAF #2 706. In an embodiment, the source NWDAF #1 704 can transmit the new notification ID (= #3) and the ID of the target NWDAF #2 706, NWDAF #2 received from the target NWDAF #2 706 to the source NF 708 in an event subscription request message. For each subscription, the value of the subscription ID received from the source NF 708 in operation 713 can still be maintained in the event subscription request message. The source NF 708 can detect the subscription to be updated based on the value of the subscription ID received in the event subscription request message. Further, the target NWDAF #2 706 can maintain the subscription using the same value of the subscription ID and receive data from the source NF 708 based on the subscription.

[0090] In operations 721 and 722, the source NWDAF #1 704 can identify the subscriptions not selected by the target NWDAF #2 706 using the subscription information about the selected subscriptions received in operation 718, request the source NF 708 to unsubscribe from the subscriptions not selected by the target NWDAF #2 706, and receive a response to the request.

[0091] In operation 723, the source NWDAF #1 704 can transmit to the consumer NF 702 a subscription response message received from the target NWDAF #2 706 requesting update of the selected subscription. In an embodiment, the subscription response message can include at least one of a subscription ID set by the target NWDAF #2 706 for each updated subscription (set to #3 in the illustrated example) or a new NWDAF ID set to a value of the identifier of the target NWDAF #2 706.

[0092] In an embodiment, the value of the notification ID for each subscription received from the consumer NF 702 in operation 711 can be kept in the subscription response message of operation 723 for the update. The target NWDAF #2 706 can use the same value of the notification ID to report the analytics data to the consumer NF 702.

[0093] In an embodiment, the target NWDAF #2 706 can transmit to the consumer NF 702 in the subscription response message Nnwdaf_Analytics_Subscription Response 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 NF 702 has set during the subscription procedure with the source NWDAF #1 704 through the consumer NF 702.

[0094] In operation 724, the source NWDAF #1 704 transmits a subscription transfer complete message to the target NWDAF #2 706, indicating completion of the update of the selected subscription. In an embodiment, the subscription transfer complete message can include the subscription information about the subscription transferred from the source NWDAF #1 704 to the target NWDAF #2 706. In an embodiment, historical data including at least one of the data previously collected by the source NWDAF #1 704 from the source NF 708 or the analytics data reported by the source NWDAF #1 704 to the consumer NF 702 for each subscription can be transmitted to the target NWDAF #2 706 in the subscription transfer complete message. Upon receiving the subscription transfer complete message, the target NWDAF #2 706 is able to communicate with the consumer NF 702 and the source NF 708 by using the updated subscription information about the selected subscription.

[0095] In an embodiment, at least one of operation 725, operation 726, or operation 727 can replace at least one of operation 719, operation 720, or operation 723. In this embodiment, the target NWDAF #2 706 can select the subscription to be updated based on the subscription information received from the source NWDAF #1 704, and perform a subscription update procedure for the selected subscription with the consumer NF 702 and the source NF 708, instead of the source NWDAF #1 704 performing the subscription update procedure.

[0096] In operations 725 and 726, the target NWDAF #2 706 can update the subscription information about the subscription with the source NF 708 using the subscription information about the selected subscription. In an embodiment, the target NWDAF #2 706 can transmit the notification ID (= #3) of the new value set by the target NWDAF #2 706 and the target's NWDAF ID identifying the target NWDAF #2 706 to the source NF 708 in the event subscription request message. In an embodiment, for each subscription, the value of the subscription ID received from the source NF 708 in operation 713 can be maintained in the event subscription request message. The source NF 708 can detect the subscription to be updated based on the value of the subscription ID received in the event subscription request message. The target NWDAF #2 706 can also maintain the subscription using the same value of the subscription ID, and receive data from the source NF 708 based on the subscription.

[0097] In operation 727, the target NWDAF #2 706 can transmit a subscription response message requesting to update the subscription information about the selected subscription to the consumer NF 702. In an embodiment, the subscription response message can include at least one of the subscription ID set by the target NWDAF #2 706 for each updated subscription (set to #3 in the illustrated example) or a new NWDAF ID set to the ID of the target NWDAF #2 706.

[0098] If operations 725, 726, and 727 are performed, operations 719, 720, and 723 can be omitted. In an embodiment, although not shown in this example, for a subscription not selected in the procedure of performing operation 723 or 727, a procedure of unsubscribing from the subscription with the consumer NF 702 can be performed. In an embodiment, after operation 723 or operation 727, a procedure of unsubscribing, for example, similar to operations 720 and 721 can be performed.

[0099] In an embodiment, when operation 727 is performed, target NWDAF #2 706 can transmit one of the subscription information received from source NWDAF #1 704, previous subscription ID #1, or notification ID #1 provided by consumer NF 702 in the subscription response message Nnwdaf_Analytics_Subscription response to consumer NF 702 to enable consumer NF 702 to identify that operation 727 is related to the subscription of previous subscription ID #1 between source NWDAF #1 704 and consumer NF 702 is replaced. In an embodiment, although omitted in this example, according to implementation, target NWDAF #2 706 can transmit a message (e.g., subscription transfer completion message) to source NWDAF #1 704 after operation 727 that target NWDAF #2 706 has completed updating the subscription for source NF 708 and consumer NF 702 requested by source NWDAF #1 704. In an embodiment, the subscription transfer completion message of operation 727 can include notification ID #1 obtained in operation 711 and old subscription ID #1 obtained in operation 714. Figure 8 is a diagram illustrating a signal flow of a mobility management procedure initiated by a target NWDAF in a wireless communication network according to an embodiment of the disclosure. Although the procedure shown is similar to the case of FIG. 7 described above, the former differs from the latter in that the target NWDAF is selected by a consumer NF and performs a subscription transfer procedure. Various embodiments of the disclosure can include at least one of the following operations.

[0100] Reference Figure 8 In operation 0, consumer NF #1 802 subscribes to source NWDAF #1 806 for data analytics, and source NWDAF #1 806 subscribes to source NF 810 for data collection.

[0101] Operations 811 and 812 are for the case where subscription information is transferred between consumer NFs 802 and 804 in a mobility management procedure, and the specific procedure can vary according to implementation. In operation 811, consumer NF #2 804 can recognize that a NWDAF change and / or a consumer NF change has occurred based on predetermined criteria (e.g., UE mobility and / or network load balancing), and transmits a handover context request message requesting handover information to consumer NF #1 802 as a handover source. In an embodiment, the handover context request message can include a UE ID identifying a UE for which handover is to be performed and analytics support information indicating the type of analytics data that consumer NF #2 804 wants to use, as well as other handover-related parameters.

[0102] In operation 812, the consumer NF #1 802 can include the old NWDAF ID (which is the ID of the NWDAF #1 806) that the consumer NF #1 802 has subscribed to and the subscription information about the current subscription, as well as the UE ID and the corresponding UE context in the handover context response message, thereby referring to the analytics support information provided by the consumer NF #2 804, and transmit the handover context response message to the consumer NF #2 804. In an embodiment, the handover context response message can include the ID of the NWDAF without the subscription information, and the consumer NF #2 804 can receive the subscription information directly from the new NWDAF in a subsequent operation.

[0103] In operation 813, the consumer NF #2 804 can select a desired subscription based on the received subscription information about the subscription, and transmit a subscription request message including a subscription message about the selected subscription to the NWDAF #2 808. In an embodiment, the subscription information can include at least one of an analytics ID, a reporting target, event reporting information, or a notification ID related to the subscription information (which is set to #1 in the illustrated example). In an embodiment, the subscription request message can include the old NWDAF ID received from the consumer NF #1 802, and the NWDAF #2 808 can identify that the subscription request message has been transmitted for an update caused by mobility based on the old NWDAF ID.

[0104] In operation 814, the NWDAF #2 808 can detect the NWDAF #1 806 based on the old NWDAF ID, and transmit a subscription transfer request message requesting subscription information about the subscription configured for the UE to the NWDAF #1 806. In an embodiment, the subscription information included in the subscription transfer request message can include information identifying each of the above-described selected subscriptions, and the NWDAF #1 806 can select each subscription related to the UE from the information. In operation 815, the NWDAF #1 806 can transmit a subscription transfer response message including at least one of the UE ID, the subscription information, collected data, or historical data to the NWDAF #2 808 in response to the subscription transfer request message. In operation 816, the NWDAF #2 808 can transmit a subscription response message for updating the subscription information to the consumer NF #2 804, and in operations 817 and 818, a subscription request message and a subscription response message are exchanged for updating the subscription information of the source NF 810. In an embodiment, the subscription response message transmitted from the NWDAF #2 808 to the consumer NF #2 804 in operation 816 can include a subscription ID newly allocated to the updated subscription by the NWDAF #2 808.

[0105] In operation 819, the NWDAF #1 806 can receive a subscription delivery complete message from the NWDAF #2 808 indicating completion of the update of the selected subscription. In operations 820 and 821, the NWDAF #1 806 can perform an unsubscribe procedure for the unselected subscriptions (e.g., including the subscription with subscription ID #x) of the source NF 810.

[0106] Figure 9 FIG. 10 is a diagram illustrating a mobility management in a wireless communication network with a hierarchical NWDAF architect, according to an embodiment of the disclosure.

[0107] Reference Figure 9 There can be local NWDAFs #1 915 and #2 920 associated with consumer NFs #1 925 and #2 930, respectively. The central NWDAF 905 can collect network data from the source NF1 935 and transmit analytics data to the consumer NFs 925 and 930 through the local NWDAFs #1 915 and #2 920. In an embodiment, the central NWDAF 905 can transmit data collected from the source NF1 935 to the local NWDAFs #1 915 and #2 920. The local NWDAFs #1 915 and #2 920 can transmit analytics data for the consumer NFs #1 925 and #2 930 generated based on the collected data to the consumer NFs #1 925 and #2 930.

[0108] In the illustrated network, the NWDAFs 905, 915, and 920 can be configured in multiple tiers, some analytics data can be provided by the central NWDAF 905, and some analytics subscription information can change in the process of handling mobility. In the process of handling mobility, some analytics subscriptions can be 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 an embodiment, the local NWDAF 915 or 920 can be implemented by merging with the consumer NF 925 or 930. In this case, the signaling between the local NWDAF 915 or 920 and the consumer NF 925 or 930 can be replaced with internal signaling.

[0109] Figure 10a and Figure 10b FIG. 10 (hereinafter referred to as FIG. 10) is a diagram illustrating a signal flow of a procedure of updating subscription information 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 disclosure. Various embodiments of the disclosure can include at least one of the following operations.

[0110] Referring to FIG. 10, in operation 0, the consumer NF #1 1002 subscribes to the local NWDAF #1 1006 for data analytics, and the local NWDAF #1 1006 subscribes to the source NF 1012 for data collection. The consumer NF #1 1002 is associated with the local NWDAF #1 1006, and the consumer NF #2 1004 is associated with the local NWDAF #2 1008.

[0111] Operations 1021 to 1026 and operation 1029 can be the same as operations 811 to 816 and operation 819 of FIG. 8. Figure 8

[0112] After the transfer procedure of the subscription information is completed in operations 1024 to 1026, in operation 1027, the local NWDAF #1 1006 can transmit an analytics unsubscription request message Nnwdaf_Analytics_Unscription request to the central NWDAF 1010. In an embodiment, the analytics unsubscription request message can include a subscription ID (e.g., subscription ID #x) of each subscription to be unsubscribed and an analytics ID. In operation 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 can be completed in the local NWDAF #1 1006.

[0113] ​In the subscription update procedure (e.g., after receiving the subscription transfer response message in operation 1025), the new local NWDAF #2 1008 can determine that the central NWDAF 1110 is to provide at least a part of the analytics data (e.g., related to at least one analytics subscription) that was provided by the old local NWDAF #1 1006 to the consumer NF #1 1002 instead of the old local NWDAF #1 1006. In this case, in operation 1030, an analytics subscription request message Nnwdaf_Analytics_Subscription Request of a new subscription request can be transmitted from the local NWDAF #2 1008 to the central NWDAF 1010. In an embodiment, the analytics subscription request message can include an analytics ID related to the analytics data that the central NWDAF 1010 wants to provide, reporting information (and other subscription information), or a subscription ID (which is set to #1 in the illustrated example). In operation 1031, the central NWDAF 1010 can transmit an analytics subscription response message Nnwdaf_Analytics_Subscription Response including the analytics ID and the subscription ID (which is set to #1 in the illustrated example) to the local NWDAF #2 1008 in response to the analytics subscription request message.

[0114] In operations 1030 and 1031, in the process of changing the local NWDAF #1 1006 to the local NWDAF #2 1008, the entity that provides the analytics data can change from the local NWDAF #1 1006 to the local NWDAF #2 1008.

[0115] In an embodiment, when data is collected from the source NF 1012 by the central NWDAF 1010, a subscription related to the data collection of the central NWDAF 1010 can not change, and thus an update procedure for the subscription of the source NF 1012 can be skipped.

[0116] Figure 11 A configuration of an NF entity according to an embodiment of the disclosure is illustrated. According to at least one of the embodiments of the disclosure, the illustrated configuration can be applied to a consumer NF or a source NF.

[0117] Reference Figure 11The NF entity can include a transceiver 1110, a memory 1115, and a processor 1105. The transceiver 1110, the memory 1115, and the processor 1105 of the NF entity can operate according to the above-described NF operations. The configuration of the NF entity is not limited to the illustrated example, and for example, the NF entity can include more or less components. The transceiver 1110, the memory 1115, and the processor 1105 can be implemented as at least one chip. In an embodiment, the NF entity can include at least one of the entities included in the RAN or the core network, for example, the AMF, the SMF, or the UPF.

[0118] The transceiver 1110 can be configured to transmit and receive signal messages, collected data, and analytics data to and from the UE, another NF entity, or the NWDAF. The memory 1115 can be configured to store programs and data required for the operation of the NF entity. Furthermore, the memory 1115 can be configured to store control information or data included in a signal obtained by the NF entity. The memory 1115 can be configured to store a medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. Furthermore, the memory 1115 can include a plurality of memories.

[0119] According to an embodiment of the disclosure, the processor 1105 can control a series of operations so that the NF entity can operate according to at least one of the above-described embodiments. According to some embodiments, the NF entity can subscribe to the NWDAF to transmit a request for available analytics data and receive a response including the available analytics data from the NWDAF. According to some embodiments, the NF entity can exchange signal messages and subscription information for supporting mobility with another NF entity and the NWDAF entity. The processor 1105 can perform only some operations of the above-described embodiments. The processor 1105 can control all processes so that the NF entity operates according to all or some of the above-described embodiments, without being limited to some operations.

[0120] Figure 12 A configuration of the NWDAF entity according to an embodiment of the disclosure is illustrated. The illustrated configuration can be applied to the source NWDAF, the target NWDAF, the local NWDAF, or the central NWDAF according to at least one of the embodiments of the disclosure.

[0121] Reference Figure 12The NWDAF entity can include a transceiver 1210, a memory 1215, and a processor 1205. The transceiver 1210, the memory 1215, and the processor 1205 of the NWDAF entity can operate according to the above-described NWDAF operations. The configuration of the NWDAF entity is not limited to the illustrated example, and for example, the NWDAF entity can include more or fewer components. The transceiver 1210, the memory 1215, and the processor 1205 can be implemented as at least one chip. In an embodiment, the NWDAF entity can include at least one of entities included in a RAN or a core network, for example, an AMF, an SMF, or a UPF.

[0122] The transceiver 1210 can be configured to transmit and receive signal messages, collected data, and analysis data to and from NF entities. The memory 1215 can be configured to store programs and data required for the operation of the NWDAF entity. Furthermore, the memory 1215 can be configured to store control information or data included in signals obtained by the NWDAF entity. The memory 1215 can be configured to store media or a combination of storage media, such as ROM, RAM, a hard disk, a CD-ROM, and a DVD. Furthermore, the memory 1215 can include a plurality of memories.

[0123] According to an embodiment of the disclosure, the processor 1205 can control a series of operations so that the NWDAF entity can operate according to at least one of the above-described embodiments. According to some embodiments, the NWDAF entity can receive a subscription request for data analysis from a consumer NF, and can transmit a response including available analysis data to the subscribed consumer NF. According to some embodiments, the NWDAF entity can transmit a subscription request to a source NF and receive collected data from the source NF. According to some embodiments, the NWDAF can exchange signal messages and subscription information for supporting mobility with at least one NF entity and another NWDAF entity. The processor 1205 can perform only some operations of the above-described embodiments. The processor 1205 can control all processes so that the NWDAF entity operates according to all or some of the above-described embodiments, without being limited to some operations.

[0124] According to various embodiments, a method of supporting mobility of a NWDAF in a wireless communication network can include determining one or more analytics subscriptions to at least one NF are to be transferred, determining a target NWDAF to which the one or more analytics subscriptions are to be transferred based on at least one of a UE location, the one or more analytics subscriptions, at least one consumer NF, and a target area, transmitting a subscription transfer request message including first subscription information on the one or more analytics subscriptions to the target NWDAF, receiving a subscription transfer response message from the target NWDAF, the subscription transfer response message including second subscription information on at least one analytics subscription generated based on the first subscription information, and requesting, based on the second subscription information, an unsubscription to a corresponding analytics subscription of the at least one analytics subscription from a source NF.

[0125] According to an embodiment, the second subscription information can include at least one of an analytics ID, a reporting target, event reporting information, a notification ID, a subscription ID, and a consumer NF ID of an analytics subscription of the consumer NF.

[0126] According to an embodiment, the second subscription information can include at least one of an event ID, reporting information, a notification ID, a subscription ID, and an NF ID of an analytics subscription of the source NF.

[0127] According to an embodiment, for each of the at least one analytics subscription, the second subscription information can include a notification ID set to a new value and a subscription ID set to a same value in the first subscription information.

[0128] According to an embodiment, the method can further include requesting, based on the second subscription information, a subscription update to the corresponding analytics subscription of the at least one analytics subscription from the consumer NF.

[0129] According to various embodiments, a method of supporting mobility of a NWDAF entity in a wireless communication network can include receiving, from a source NWDAF, a subscription transfer request message including first subscription information on one or more analytics subscriptions to at least one NF, transmitting a subscription transfer response message to the source NWDAF, the subscription transfer response message including second subscription information on at least one analytics subscription generated based on the first subscription information, and transmitting, based on the second subscription information, a subscription request message related to a corresponding analytics subscription of the at least one analytics subscription to a source NF.

[0130] According to an embodiment, the second subscription information can include at least one of an analytics ID, a reporting target, event reporting information, a notification ID, a subscription ID, and a consumer NF ID of an analytics subscription of the consumer NF.

[0131] According to an embodiment, the second subscription information can include at least one of an event ID, reporting information, a notification ID, a subscription ID, and an NF ID of an analytics subscription of the source NF.

[0132] According to an embodiment, for each of the at least one analytics subscription, the second subscription information can include a notification ID set to a new value and a subscription ID set to the same value in the first subscription information.

[0133] According to an embodiment, the subscription request message can include a target NWDAF ID and a notification ID set to a new value.

[0134] According to an embodiment, the subscription request message can further include a subscription ID set to the same value in the first subscription information.

[0135] According to an embodiment, the method can further include transmitting, based on the second subscription information, a subscription update request message for the corresponding analytics subscription among the at least one analytics subscription to a consumer NF.

[0136] According to an embodiment, for the corresponding analytics subscription, the subscription update request message can include a new NWDAF ID and at least one of the first subscription information or a subscription ID obtained from the first subscription information.

[0137] According to various embodiments, an apparatus of a NWDAF entity in a wireless communication network can include a transceiver and a processor operably coupled to the transceiver. The processor can be configured to determine that one or more analytics subscriptions of at least one NF are to be transferred, determine a target NWDAF to which the one or more analytics subscriptions are to be transferred based on at least one of a UE location, the one or more analytics subscriptions, at least one consumer NF, and a target area, transmit a subscription transfer request message including first subscription information about the one or more analytics subscriptions to the target NWDAF, receive a subscription transfer response message from the target NWDAF, the subscription transfer response message including second subscription information about at least one analytics subscription generated based on the first subscription information, and request, based on the second subscription information, an unsubscription for a corresponding analytics subscription among the at least one analytics subscription from a source NF.

[0138] According to various embodiments, an apparatus of a NWDAF entity in a wireless communication network can include a transceiver and a processor operably coupled to the transceiver. The processor can be configured to receive a subscription transfer request message from a source NWDAF, the subscription transfer request message including first subscription information about one or more analytics subscriptions of at least one NF; transmit a subscription transfer response message to the source NWDAF, the subscription transfer response message including second subscription information about at least one analytics subscription generated based on the first subscription information; and transmit a subscription request message related to a corresponding analytics subscription of the at least one analytics subscription to a source NF based on the second subscription information.

[0139] The embodiments of the disclosure disclosed in the specification and drawings are presented only as specific examples in order to easily explain the technical idea of the disclosure and help understanding of the disclosure, and are not intended to limit the scope of the disclosure. That is, it will be obvious to those skilled in the art that other modifications based on the technical spirit of the disclosure can be made. In addition, the above embodiments can be operated in combination as needed. For example, a base station (BS) and a UE can operate in a combination of parts of different embodiments of the disclosure.

[0140] In the specific embodiments disclosed above, the elements included in the disclosure are expressed in singular or plural according to the specific embodiments. However, for convenience of description, singular or plural expression is appropriately selected in the context, and the disclosure is not limited to singular or plural components. Even if the component is expressed in plural, it can be singular. Even if expressed in singular, it can be plural.

[0141] The embodiments of the disclosure disclosed in the specification and drawings are presented only as specific examples in order to easily explain the technical idea of the disclosure and help understanding of the disclosure, and are not intended to limit the scope of the disclosure. In addition, the foregoing embodiments of the disclosure are merely illustrative, and those skilled in the art will understand that various modifications and embodiments of the equivalent scope of the embodiments are possible. Therefore, the true technical protection scope of the disclosure should be defined by the appended claims.

Claims

1. A method by a source network data analytics function (NWDAF) entity, the method comprising: determining to transfer one or more analytics subscriptions related to at least one consumer network function (NF) to a target NWDAF based on at least one of a user equipment (UE) mobility event, UE location information, or information of the at least one consumer NF, transmitting a subscription transfer request message including information related to the one or more analytics subscriptions to the target NWDAF, and receiving a subscription transfer response message related to the one or more analytics subscriptions from the target NWDAF after transmitting the subscription transfer request message.

2. The method of claim 1, wherein the information related to the one or more analytics subscriptions includes at least one of an analytics ID, a reporting target, event reporting information, a notification ID, a subscription ID, and a consumer NF ID of an analytics subscription of the consumer NF.

3. The method of claim 1, wherein the information includes at least one of an event ID, reporting information, a notification ID, a subscription ID, and a NF ID of an analytics subscription of the source NF.

4. The method of claim 1, wherein the subscription transfer response message includes, for each analytics subscription, a notification ID set to a new value and a subscription ID set to the same value as the subscription transfer request message.

5. The method of claim 1, further comprising at least one of: requesting a subscription update to at least one analytics subscription of the one or more analytics subscriptions from a consumer NF, and requesting an unsubscription of at least one analytics subscription of the one or more analytics subscriptions from a source NF.

6. A method by a target network data analytics function (NWDAF) entity, the method comprising: receiving a subscription transfer request message from a source NWDAF, the subscription transfer request message including information related to one or more analytics subscriptions, transmitting a subscription transfer response message related to the one or more analytics subscriptions to the source NWDAF in response to receiving the subscription transfer request message, and transmitting a subscription request message to a source NF related to at least one analytics subscription of the one or more analytics subscriptions based on the information.

7. The method of claim 6, wherein the information related to the one or more analytics subscriptions includes at least one of an analytics ID, a reporting target, event reporting information, a notification ID, a subscription ID, and a consumer NF ID of an analytics subscription of the consumer NF.

8. The method of claim 6, wherein the information includes at least one of an event ID, reporting information, a notification ID, a subscription ID, and a NF ID of an analytics subscription of the source NF.

9. The method of claim 6, wherein the subscription transfer response message includes, for each analytics subscription, a notification ID set to a new value and a subscription ID set to the same value as the subscription transfer request message.

10. The method of claim 6, wherein the subscription request message includes a NWDAF ID of a target NWDAF and a notification ID set to a new value.

11. The method of claim 10, wherein the subscription request message further includes a subscription ID set to a same value as the subscription delivery request message.

12. The method of claim 6, further comprising transmitting a subscription update request message to a consumer NF for at least one analytics subscription of the one or more analytics subscriptions.

13. The method of claim 12, wherein for each analytics subscription, the subscription update request message includes a new NWDAF ID and at least one of the information and a subscription ID obtained from the information.

14. A device of a source network data analytics function (NWDAF) entity, the device comprising: a transceiver and a processor operably coupled to the transceiver, wherein the processor is configured to: determine to deliver one or more analytics subscriptions related to at least one consumer network function (NF) to a target NWDAF based on at least one of a user equipment (UE) mobility event, UE location information, or information of the at least one consumer NF, transmit a subscription delivery request message including information related to the one or more analytics subscriptions to the target NWDAF, and receive a subscription delivery response message related to the one or more analytics subscriptions from the target NWDAF after transmitting the subscription delivery request message.

15. A device of a target network data analytics function (NWDAF) entity, the device comprising: a transceiver and a processor operably coupled to the transceiver, wherein the processor is configured to: receive a subscription delivery request message from a source NWDAF, the subscription delivery request message including information related to one or more analytics subscriptions, in response to receiving the subscription delivery request message, transmit a subscription delivery response message related to the one or more analytics subscriptions to the source NWDAF, and transmit a subscription request message to a source NF related to at least one analytics subscription of the one or more analytics subscriptions based on the information.

Images