Shareable storage method and system for network data analysis

Abstract

A method and system for unified data transfer and storage in a communication network is provided. The method comprises a coordinator associated with a set of network data analytics function (NWDAF) service instances determining data required by more than one NWDAF service instance in the set of NWDAF service instances, the coordinator requesting the data from a set of network function service instances if the data required by the more than one NWDAF service instance is the same, and receiving the data from a data storage function, the set of network function service instances notifying the data storage function of the request from the coordinator associated with the set of NWDAF service instances.

Description

[0001] This application is a divisional application of the original application with the application number 201980079979.7 and the original filing date of December 7, 2019, the contents of which are incorporated herein by reference in its entirety.

[0002] Cross Reference to Related Applications

[0003] This application claims priority to U.S. Non-Provisional Patent Application No. 16 / 677,634, filed November 7, 2019, entitled “SHAREABLE STORAGE METHOD AND SYSTEM FOR NETWORK DATA ANALYSIS,” which claims priority to U.S. Provisional Patent Application No. 62 / 791,536, filed January 11, 2019, entitled “SHAREABLE STORAGE METHOD AND SYSTEM FOR NETWORK DATA ANALYSIS,” the contents of which are incorporated by reference in their entirety. TECHNICAL FIELD

[0004] The present invention relates to the field of network communication, and more particularly, to a system and method of network shareable architecture. BACKGROUND

[0005] To improve the operation efficiency of mobile networks, a Network Data Analytic Function (NWDAF) is introduced in the 3GPP Fifth Generation (5G) Core Network (CN) to provide data analytics functions. The NWDAF needs to collect data from network functions (NFs), network management functions such as operations administration and maintenance (OAM) systems, user equipment (UE), external application servers (ASs) or application functions (AFs). However, there are many problems in the existing solutions.

[0006] Figure 1A CN network model 100 is shown, where there is one NWDAF set (NWDAF set 110) and two NF sets (NF-A set 120 and NF-B set 130). The NF sets can also be referred to as NF Service Instance (SI) sets. One NF set can have one or more NF instances, one NF instance can include one or more NF service sets, and each NF service set can have one or more NF service instances. Each NF set can provide one or more services to other NF sets. The NF-A set 120 can be a set of Access and Mobility Management Functions (AMFs) and the NF-B set 130 can be a set of Session Management Functions (SMFs). For example, the NWDAF set 110 can have two NWDAF SIs (NWDAF SI 111 and NWDAF SI 112). In one example, the NWDAF SIs 111 and 112 can provide the same service, such as UE mobility analytics. In another example, the NWDAF set 110 can provide two services, where the NWDAF SIs 111 and 112 can provide UE mobility analytics and traffic routing analytics, respectively. To provide the UE mobility analytics and network traffic routing analytics information, the NWDAF SIs 111 and 112 can both need UE mobility information, such as UE location, number of connections. This information can be provided by the NF-A set 120 and the NF-B set 130. Therefore, the NWDAF SIs 111 and 112 both need to collect the same data from the NF-A set 120 and the NF-B set 130. Further, the NWDAF SIs 111 and 112 need to temporarily store the collected data in a storage function belonging to the NWDAF set, which can be an Unstructured Data Storage Function (UDSF). It is apparent that both NWDAF SIs 111 and 112 collect the same data and this same data is stored in memory twice. This redundant storage resource and signaling in the CN results in a double signaling load and double storage capacity requirement.

[0007] Figure 1Another problem with the storage solution is providing data analysis from different NWDAF collections. This is because when an NWDAF collection is removed, for example, when the NWDAF collection 110 from one vendor is replaced by a new NWDAF collection from another vendor, the data stored in the NWDAF collection storage (e.g., the NF-A service instance collection data storage 121 and the NF-B service instance collection data storage 131) may be inaccessible due to the proprietary format. This means that the new NWDAF vendor may not be able to use the existing collected data for analysis.

[0008] Reference below Figure 2 , illustrates a scenario 200 in which another network entity (such as OAM 240) collects network data and then shares the collected data with NWDAF 210. In scenario 200, OAM 240 may first collect network data for its own data analysis. NWDAF 210 may then request the network data or a subset of the collected data. OAM 240 may send the requested data to NWDAF 210. NWDAF 240 may store the data from OAM 240 for future analysis. Therefore, in this scenario, the same collected data is stored in OAM data storage 241 and NWDAF SI aggregate data storage 211, resulting in a waste of storage resources for both OAM 240 and NWDAF 210.

[0009] The background information herein is provided to reveal information believed by the applicant to be potentially relevant to the present invention. No admission is intended, nor should it be construed, that any of the foregoing information constitutes prior art against the present invention. Summary of the Invention

[0010] It is an object of embodiments of the present invention to provide an improved system and method for unifying data transmission and storage in a communication network, including a wireless communication network.

[0011] An embodiment of the present invention provides a data collection method, which includes: a coordinator associated with a network data analysis function (NWDAF) collects requests from at least one NWDAF service instance in an NWDAF set associated with the NWDAF (such as an NWDAF service instance set), wherein the request is used to obtain data items associated with at least one of the data types and attributes included in the request; the coordinator subscribes to the data items from the network function set based on the request; and the coordinator receives the data items from a data storage function that can communicate with the NWDAF and the network function set.

[0012] Embodiments of the invention provide a data collection method, the method comprising: a data storage function receiving, from a coordinator associated with a network data analytics function (NWDAF), via a first interface between the data storage function and the NWDAF, a subscription for a data item associated with at least one of a data type and a property; the data storage function subscribing, from a set of network functions, via a second interface between the data storage function and the set of network functions, to the data item in accordance with the received subscription; the data storage function receiving, from the set of network functions, via the second interface, the data item; and the data storage function sending, to the NWDAF, the data item in response to the subscription by the NWDAF.

[0013] Embodiments of the invention provide a communication system comprising a coordinator and a data storage function configured to perform the methods as described above, respectively. Optionally, the system comprises a set of network functions. Further, embodiments of the invention provide an apparatus configured to perform the methods as described above.

[0014] Embodiments of the invention provide a method of supporting data analytics in a data network. The method comprises a coordinator determining a data item that is required by more than one NWDAF service instance in a set of network data analytics functions (which can be a set of NWDAF service instances). The coordinator is associated with one of: a set of network data analytics functions (NWDAFs); a set of network functions (which can be a set of network function service instances); and a data storage function outside of the set of NWDAFs and the set of network functions. The method further comprises the coordinator initiating communication of the data item by the set of network functions, the data storage function, or both, to the more than one NWDAF service instance. The communication of the data item comprises sending a message containing part or all of a single instance of the data item, the more than one NWDAF service instance receiving the data item based on the communication of the same single instance.

[0015] An embodiment of the present invention provides a device for supporting data analysis in a data network. The device includes a processor, a memory, and a network interface configured to implement a coordinator function. The device can be implemented as a standalone device, or as a virtualized device in a data center, for example. The device (coordinator) is configured to determine the data items that are commonly required by more than one NWDAF service instance in the NWDAF set. The coordinator is associated with one of the following: a set of network data analysis function (NWDAF) service instances; a set of network functions; and a data storage function outside the NWDAF set and the network function set. The device (coordinator) is further configured to initiate data item communication between the network function set, the data storage function, or both and more than one NWDAF service instance. The delivery of the data item includes sending a message containing part or all of a single instance of the data item, and the more than one NWDAF service instance receives the data item based on the communication of the same single instance.

[0016] In one aspect, embodiments herein provide a method, comprising: a coordinator associated with a set of network data analysis function (NWDAF) service instances determining what data is required by more than one NWDAF service instance in the set of NWDAF service instances. If the more than one NWDAF service instances require the same data, the coordinator associated with the set of NWDAF service instances requests the data from the set of network function service instances. The method further comprises: receiving data from a data storage function, the set of network function service instances notifying the data storage function of the request from the coordinator associated with the set of NWDAF service instances.

[0017] In one aspect, a coordinator associated with the NWDAF service instance set sends a request to the network function service instance set, the request indicating that the data is required by an identified subset of NWDAF service instances in the NWDAF service instance set.

[0018] In another aspect, a coordinator associated with the set of NWDAF service instances receives a message including the data.

[0019] In yet another aspect, the method includes receiving, at a data storage function, a message indicating coordinator-requested data associated with a set of NWDAF service instances.

[0020] In one aspect, the embodiments herein further provide a method comprising a coordinator associated with a set of network function service instances determining whether data required by more than one NWDAF service instance is the same. And if the data required by more than one NWDAF service instance is the same, the coordinator associated with the set of network function service instances instructs a data storage function to send the data to the more than one NWDAF service instance in one message or in multiple messages.

[0021] In one aspect, the more than one NWDAF service instance is comprised in one set of NWDAF service instances or in different sets of NWDAF service instances.

[0022] The embodiments herein further provide a method comprising a coordinator associated with a set of network function service instances determining what data is required by an operations, administration and management function (OAM). The method further comprises the coordinator associated with the set of network function service instances instructing a data storage function to send the data to the OAM.

[0023] In one aspect, the method further comprises receiving, at the OAM, a request for data from a NWDAF service instance, and transferring the data to the NWDAF service instance by the data storage function.

[0024] The embodiments herein further provide a method comprising a unified data manager function (UDM) subscribing, from a NWDAF, user equipment (UE) mobility information, and receiving the subscribed UE mobility information. The method further comprises, when receiving a request for UE subscription and UE mobility information from an access and mobility management function (AMF), the UDM sending the requested information to the AMF based on the information subscribed from the UDM.

[0025] In one aspect, the method is associated with a UE registration procedure.

[0026] In another aspect, the method further comprises, when receiving a request for at least one of UE subscription and UE mobility information from a session management function (SMF), the UDM sending the requested information to the SMF based on the information subscribed from the UDM.

[0027] In yet another aspect, the method further comprises receiving, at the SMF, a request associated with a protocol data unit (PDU) session from the AMF, and the SMF sending the request to the UDM.

[0028] In one aspect, embodiments herein also provide a method comprising a plurality of network data analytics functions (NWDAFs) of one or more NWDAF SI sets requesting data for SI retrieval by a plurality of network functions of a plurality of network function sets, each network function set being associated with a network function group SI set coordinator (SC). The method further comprises receiving unified data at the plurality of NWDAF SIs, the data being unified for transmission and storage at least according to data type identification and data collection attributes. The method further comprises performing at least one network data analytics operation at the plurality of NWDAF SIs based on the unified data.

[0029] In yet another aspect, the method further comprises storing results of the at least one data analytics operation, the at least one data analytics operation being accessible in conjunction with a unified data management (UDM) function of a storage function (SF), the storage function (SF) being shared with the plurality of NWDAF SIs and the at least one NWDAF SI set, and at least one of a network function and a network management function (such as OAM) accessing the results of the at least one data analytics operation via the UDM function. In one embodiment, the storage function (SF) is shared with the plurality of NWDAF SIs and at least one NWDAF set of the plurality of NWDAF sets, whereby the unified data received by the NWDAF SIs is received from the SF. In yet another embodiment, the results pertain to UE parameters, the UE parameters comprising at least one of a UE mobility pattern parameter and a UE communication pattern parameter.

[0030] In yet another aspect, the data collection attributes can comprise at least one of: a start collection time, an end collection time, information related to a network slice of a communication network (where the communication network is a virtualized network), a domain network name (DNN), a user equipment (UE) identifier (ID) of a single UE or a group of UEs, a UE location, location information related to at least one of a radio access network (RAN) address, a cell ID, a tracking area comprising one or more cell IDs, a registration area comprising one or more cell IDs, and a service area comprising at least one of a user plane function service area and a control plane service area.

[0031] In one aspect of the embodiments presented herein, the data type identification may include at least one of an event identification (ID), a protocol data unit (PDU) session ID, a quality of service (QoS) flow ID, a QoS profile ID, a QoS rule, and a packet data filter (PDF).

[0032] On another aspect, embodiments of the present invention further provide a network element in a communication network, comprising a processor, a network interface for communicating with at least one network storage function (SF) and a network management function (such as an OAM system), and a non-transitory computer-readable memory storing instructions executable in the processor. The instructions are executable to configure the network element to implement a network data analysis function (NWDAF) to request data obtained by multiple network function SIs in multiple network function sets by multiple NWDAF SIs, each network function set being associated with an NF service instance set coordinator (SI SC). The instructions are further executable to receive unified data at the multiple NWDAF SIs, the data being unified for transmission and storage based on at least a data type identifier and a data collection attribute. The instructions are further executable to perform at least one network data analysis operation at the multiple NWDAF SIs based on the unified data.

[0033] The embodiments herein further provide a method, comprising: the OAM checking whether data requested by the NWDAF service instance is available. The method further comprises, based on the checking result, notifying the NWDAF service instance of an address to obtain the data.

[0034] In one aspect, the method further includes the NWDAF service instance obtaining data according to the received address.

[0035] Embodiments herein further provide a method, the method including a unified data manager function (UDM) subscribing to a type of analysis data from a NWDAF and receiving the subscribed analysis data. The method also includes: upon receiving a request for UE subscription and analysis data from an access and mobility management function (AMF), the UDM sending the requested information to the AMF based on the information subscribed from the UDM.

[0036] In one aspect, the method is associated with a UE registration procedure.

[0037] In another aspect, the method further includes, when receiving a request for at least one of UE subscription and analysis data from a session management function (SMF), the UDM sending the requested information to the SMF according to the requested information from the UDM.

[0038] In yet another aspect, the method further includes receiving, at the SMF, a request associated with a protocol data unit (PDU) session from an AMF, and the SMF sends the request to a UDM.

[0039] In one aspect, embodiments herein also provide a method comprising a plurality of network data analytics function (NWDAF) service instances requesting data obtained by a plurality of network function service instances in a plurality of network function service instance sets, each network function service instance set being associated with a network function SISC. The method further comprises receiving, at the plurality of NWDAF service instances, unified data, the data being unified for transmission and storage according to at least a data type identity and a data collection attribute. The method further comprises performing, at the plurality of NWDAF service instances, at least one network data analytics operation based on the unified data.

[0040] In one aspect, the unified data received at the plurality of NWDAF service instances is sent from a network function SISC, and the data is unified according to at least a data type identity and a data collection attribute.

[0041] In another aspect, the data received at the plurality of NWDAF service instances is received from a NWDAF SISC associated with a NWDAF set, the NWDAF set being associated with a subset of the plurality of NWDAF service instances.

[0042] In yet another aspect, the method further comprises a storage function (SF) accessible by the plurality of NWDAF service instances and at least one NWDAF set of the plurality of NWDAF sets, wherein the unified data received by the NWDAF service instances is received from the SF. In some embodiments, the method further comprises storing results of at least one data analytics operation accessible in conjunction with a unified data management (UDM) function of the SF shared with the plurality of NWDAF service instances and the at least one NWDAF set, and at least one of a network function and an operations, administration and management (OAM) function accessing the results of the at least one data analytics operation via the UDM function. In some embodiments, the results pertain to UE parameters including at least one of a UE mobility pattern parameter and a UE communication pattern parameter.

[0043] In yet another aspect, the data type identity comprises at least one of an event identity (ID), a protocol data unit (PDU) session ID, a quality of service (QoS) flow ID, a QoS profile ID, a QoS rule, and a packet data filter (PDF).

[0044] In yet another aspect, the data collection attributes include at least one of: a start collection time, an end collection time, information related to a network slice of the communication network (where the communication network is a virtualized network), a domain network name (DNN), a user equipment (UE) ID of a single UE or a group of UEs, a UE location, location information related to at least one of a radio access network (RAN) address, a cell ID, a tracking area including one or more cell IDs, a registration area including one or more cell IDs, and a service area including at least one of a user plane function service area and a control plane service area. The start collection time and / or the end collection time can indicate a past or a future time.

[0045] In yet another aspect, the data includes at least one of network entity data, network operation data, user equipment (UE) mobility data, network maintenance data, and network measurement reports acquired by at least one of a UE, an application function (AF), and an operations, administration, and management (OAM) function of the communication network.

[0046] In yet another aspect, at least one of the plurality of NWDAF service instances includes at least one of a plurality of network entities selected from the group consisting of: an electronic device, a radio access network (RAN) function, a user plane function, a control plane function, and a management plane function, and the unified data includes network measurement data acquired at an access node of a respective network entity of the plurality of network entities.

[0047] In yet another aspect, the embodiments herein also provide a network element in a communication network, comprising a processor, a network interface in communication with at least one network storage function (SF) and a network management function (such as an OAM system), and a non-transitory computer-readable memory storing instructions executable in the processor. The instructions are executable to configure the network element to implement a network data analytics function (NWDAF) to request data acquired by a plurality of network function service instances of a plurality of network function sets, each network function set being associated with a network function SISC, from a plurality of network data analytics function (NWDAF) service instances. The instructions are further executable to receive unified data at the plurality of NWDAF service instances, the data being unified for transmission and storage according to at least a data type identification and data collection attributes. The instructions are further executable to perform at least one network data analytics operation at the plurality of NWDAF SIs based on the unified data.

[0048] In one aspect of the embodiments presented herein, the unified data received at the plurality of NWDAF service instances is transmitted directly from the network function SISCs, where the data is unified according to at least a data type identification and data collection attributes.

[0049] In another aspect of embodiments presented herein, the data received at the plurality of NWDAF service instances is received from a NWDAF SISC associated with a set of NWDAFs associated with a subset of the plurality of NWDAF service instances.

[0050] In yet another aspect of embodiments presented herein, the network further comprises a storage function (SF) shared with at least one set of NWDAFs of the plurality of NWDAF service instances and the plurality of sets of NWDAFs, wherein the unified data received by the NWDAF service instances is received from the SF.

[0051] In yet another aspect of embodiments presented herein, the instructions are further executable to store results of at least one data analytics operation accessible in conjunction with a unified data management (UDM) function of the SF shared with the plurality of NWDAF service instances and the at least one set of NWDAFs, and at least one of a network function and an operations, administration and management (OAM) function accesses the results of the at least one data analytics operation via the UDM function.

[0052] In yet another aspect of embodiments presented herein, the results pertain to UE parameters comprising at least one of a UE mobility pattern parameter and a UE communication pattern parameter.

[0053] In yet another aspect of embodiments presented herein, the data type identification comprises at least one of an event ID, a protocol data unit (PDU) session ID, a quality of service (QoS) flow ID, a QoS profile ID, a QoS rule and a packet data filter (PDF).

[0054] In yet another aspect of embodiments presented herein, the data collection attributes comprise at least one of a start collection time, an end collection time, information related to a network slice of a communication network (where the communication network is a virtualized network), a domain network name (DNN), a user equipment (UE) ID of a single UE or a group of UEs, a UE location, location information related to at least one of a radio access network (RAN) address, a cell ID, a tracking area comprising one or more cell IDs, a registration area comprising one or more cell IDs, and a service area comprising at least one of a user plane function service area and a control plane service area.

[0055] In yet another aspect of embodiments presented herein, the data comprises at least one of network entity data, network operation data, user equipment (UE) mobility data, network maintenance data and network measurement reports acquired by at least one of a UE, an application function (AF) and an operations, administration and management (OAM) function of a communication network.

[0056] In another aspect of the embodiments presented herein, at least one of the multiple NWDAF service instances includes at least one of a plurality of network entities selected from the group consisting of: an electronic device, a radio access network (RAN) function, a user plane function, a control plane function, and a management plane function, and the unified data includes network measurement data obtained at an access node of a corresponding network entity among the multiple network entities. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Other features and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0058] Figure 1 The data collection of different network data analysis functions (NWDAF) SIs in a communication network in an example embodiment is shown.

[0059] Figure 2 An example embodiment is shown in which a network management function (eg, an OAM system) shares collected data with the NWDAF.

[0060] Figure 3A A scheme for sharing storage functionality between NWDAF SIs in an example embodiment is shown.

[0061] Figure 3B An alternative approach to sharing storage between NWDAF SIs is shown, where the data storage function takes a more active role and is coordinated using an NWDAF SI collective coordinator.

[0062] Figure 3C An alternative to sharing storage between NWDAF SIs is shown, where the data storage function takes a more active role and utilizes the NWDAF SIs for coordination.

[0063] Figures 4AA-4AC An example signaling process for data collection and data analysis provision is shown.

[0064] Figures 4BA-4BC Another example signaling process for data collection and data analysis provision is shown, which is customized to Figure 3B The functions of the NWDAF collection and NF collection are described in.

[0065] Figures 4CA-4CB Another example signaling process for data collection and data analysis provision is shown, which is customized to Figure 3C The functions of the NWDAF collection and NF collection are described in.

[0066] Figures 5A-5C Another example signaling process for data collection and data analysis provision is shown.

[0067] Figure 6 An example embodiment of a data sharing scheme between an OAM system and a NWDAF is shown.

[0068] Figure 7A and 7B An embodiment signaling procedure for message exchange between NFs, OAM and NWDAF for network data collection is shown.

[0069] Figure 8A and 8B An example signaling procedure for storing and sharing analytics data produced by a NWDAF is shown.

[0070] Figure 9 An example method for unified data transport and storage in a communication network is shown.

[0071] Figure 10 An architecture of a computing system that can be used to implement the devices and methods disclosed herein in an example embodiment is shown.

[0072] Figure 11 Embodiments of some signaling messages as part of a UE registration procedure in order to access and use resources of a mobile network are shown.

[0073] Figure 12 Embodiments of some additional signaling messages that can be performed during a UE registration procedure are shown.

[0074] Figure 13 Embodiments of signaling messages that can be part of a PDU session establishment procedure in order to establish a new PDU session for a UE are shown.

[0075] Figure 14 Embodiments of an Access and Mobility Function (AMF) initiating a PDU session creation request to a SMF in a variant of a PDU session establishment procedure are shown.

[0076] It should be noted that in all the figures, identical features are identified by the same reference signs. DETAILED DESCRIPTION

[0077] Embodiments of the present invention relate to systems and methods for unified data transport and storage in a communication network including a wireless communication network.

[0078] Multiple NF Sis of an NF can be grouped into an NF SI set. An NF SI set is also referred to as an NF set. An NF SI set is identified by an NF SI set ID or an NF set ID. In an NF SI set, an NF SI set can access an NF SI set data storage entity, such as a UDS F SI. Each NF SI set can have, for example, one function named NF SI set coordinator (SC). The NF SI SC can perform general jobs to coordinate the operation of the NF Sis, such as load balancing among the NF Sis, selecting an NF SI to fulfill a request of another NF SI. More functions of the NF SI SC will be described in this document.

[0079] In some embodiments, the organization of the NF Sis in an NF set can be multi-level. One NF SI set can contain one or more NF instances. One NF instance can be identified by an NF instance ID. An NF instance can have an address(es) (such as FQDN(s) or IP address(es)) for other NFs to communicate with. One NF instance can have one or more NF service sets, each NF service set identified by an NF service set ID. One NF service set can have an address(es) for other NFs to communicate with. One NF service set can have one or more NF service instances (Sis). Each NF SI can have a service name, an NF SI ID, and an endpoint address(es) to communicate with other NFs. An NF service instance can provide one or more services to other NF consumers.

[0080] When an NF (i.e., a service consumer or consumer) uses the service of another NF (i.e., a service producer or producer), the NF producer can indicate the binding level to the NF consumer. For example, the binding level can be an NF SI, an NF service set, an NF instance, or an NF set. The binding indication can include an NF SI ID, an NF service set ID, an NF instance ID, an NF set ID. The NF consumer can send a message to the address of the NF entity, such as an NF SI address, an NF service set address, an NF instance address, or an NF set address provided by the NF producer. In the following embodiments, for the purpose of illustration, the binding level is an NF SI set (or an NF set), an NF instance, or an NF SI. This means that an NF set, an NF instance, or an NF SI can be discovered and provide services to other NFs.

[0081] Figure 3AA storage scheme 300 is shown that shares storage functionality among the NWDNA instance(s) or NWDAF SIs (e.g., NWDAF instance / SI 311, NWDAF instance / SI 312, NWDAF instance / SI 321, and NWDAF instance / SI 322) in an example embodiment. In this example architecture, each NWDAF instance / SI of a set of NWDAF instances / SIs (e.g., NWDAF SI set 310 and NWDAF SI set 320) can request or subscribe to operational data of one or more sets of NFs (SIs) (e.g., NF-A set 330 and NF-B set 340). In a data collection request message, the NWDAF instance / SI (e.g., NWDAF instance / SI 311, NWDAF instance / SI 312, NWDAF instance / SI 321, and NWDAF instance / SI 322) can indicate an identifier of the (data) storage function 350, such as an IP address or a Fully Qualified Domain Name (FQDN) of the storage function 350.

[0082] The type of data to be collected can be represented by a data type identifier (ID). In some embodiments, the data type ID can be an event ID described in 3GPP TS 23.502 clause 4.15.1. For example, a SMF can provide PDU session data, which is represented as a data type ID of “PDU session context data”. The PDU session context data can include a PDU session ID, a QoS flow ID, a QoS profile, a QoS rule, a packet data filter, a start and end time (or timestamp) of the PDU session, a traffic volume, a time (or timestamp) when a user plane (uplink) N3 and / or N9 interface is activated or deactivated, a measured traffic volume per QoS flow, a measured QoS parameter such as a measured maximum flow bit rate (MFBR) of a QoS flow, a measured UE aggregate maximum bit rate (UE-AMBR).

[0083] Each data type can have a set of data collection attributes, which can include one or more of the following attributes:

[0084] a. a start collection time;

[0085] b. an end collection time;

[0086] c. Network slice information: e.g., Network Slice Instance Identifier (NSI ID), Single Network Slice Selection Assistance Information (S-NSSAI);

[0087] d. DNN;

[0088] e. Internal group ID of the UE;

[0089] f. UE ID (e.g., Subscription Permanent Identifier (SUPI), Generic Public Subscription Identifier (GPSI));

[0090] g. Location information: RAN address(s), cell ID(s), tracking area (e.g., each tracking area includes one or more cell IDs), registration area (e.g., each registration area can include one or more tracking areas), User Plane Function (UPF) service area, control plane (CP) function service area (e.g., AMF service area, SMF service area); and

[0091] h. Application information (e.g., application ID, or service-application ID of an application function).

[0092] For illustration purposes, in the remainder of this disclosure, the NF-A SI set 330 or the NF-B SI set 340 will be used.

[0093] The NF SI SC (e.g., NF-A SI SC 335) of each NF SI set (e.g., NF-A set 330) receives the data collection request. The NF SI SC should identify whether the requested data collection has been requested fully or partially by other NWDAF SI of the same NWDAF SI set. If the requested data is the same, the NF-A SI SC 335 can not request the NF-A instance(s) / SI(s) (e.g., NF-A instance / SI 333, NF-A instance / SI 334) to send data to avoid duplicate data collection. If the requested data is the same but some attributes are different, e.g., the collection time is different, then the NF SI SC can send a message to the NF instance / SI to modify the data collection attributes. One way to modify (or update) an existing subscription is to send a unsubscribe message to cancel the existing subscription and send another subscription message with new data collection attributes.

[0094] The NF-A SI SC 335 then forwards the data collection request of the NWDAF SI (e.g., NWDAF instance / SI 311, NWDAF instance / SI 312, NWDAF instance / SI 321, and NWDAF instance / SI 322) to the NF-A instance / SI (e.g., NF-A instance / SI 333 or NF-A instance / SI 334) that is capable of providing the requested data. For example, in one SMF set, some SMF instances / SIs can have the capability to handle eMBB IP PDU session type and some other SMF instances / SIs can have the capability to handle Ethernet PDU session type. If the data collection request is for IP PDU session type, the SMF SI SC can forward the data collection request to the SMF SI that handles IP PDU session type.

[0095] In the illustrated embodiment, the NF-A instance / SI (e.g., NF-A instance / SI 333 or NF-A instance / SI 334) can send network data to the storage function 350 directly or indirectly via the NF-A SI SC 335.

[0096] Figure 3A The system described in the middle can be modified in different ways. For example, some of the functions of the coordinator function of the NF sets (such as the NWDAF SI SCs 315 and 325, the NF-A SI SC 335, and / or the NF-B SI SC 345) can be implemented in the data storage function. For example, the data storage function can be configured to receive data from the NFs directly or indirectly via the NF SI SCs. Figure 3BIn one example shown, when the NWDAF SI SC 315 receives a data request from the NWDAF service instance(s) 311 / 312, the NWDAF set coordinator 315 can not necessarily check whether the data has been pre-requested or subscribed. The NWDAF SI SC 315 can create a data request message and send it to the data storage function 350. The data storage function 350 can communicate with other NFs to perform data collection. The data storage function 350 can check whether the data has been collected or not collected prior to collection, or whether existing data collection operations need to be modified to accommodate the data request of the NWDAF SI SC 315.

[0097] In Figure 3C In another example shown, the NWDAF instances / service instances (e.g., NWDAF instances / service instances 311, 312, 321, and 322) can send data requests or data subscriptions directly to the data storage function 350, rather than the NWDAF service instance set coordinators 315 and 325. Data collection and storage management functions are shifted from the NWDAF SI SC 315 and 325 to the data storage function 350. The data storage function 350 can communicate with other NFs to perform data collection. The data storage function 350 can check whether the data has been collected or not collected prior to collection, or whether existing data collection operations need to be modified to accommodate the data requests of the NWDAF SI SC 315 and 325. The data storage function 350 stores the collected data and can send the collected data to the NWDAF service instance(s) (e.g., NWDAF instances / service instances 311, 312, 321, and 322) of one or more NWDAF sets 310 and 320.

[0098] According to embodiments of the present invention, NWDAF service instances are coordinated, for example, via a NWDAF SI SC. Still further, a data storage function is introduced, which can be used to store retrieved data for provision to NWDAF instances / service instances. In some cases, the data storage function can include a coordinator function that coordinates the provision of data to NWDAF instances / service instances. When multiple NWDAF service instances request the same data, the coordination can include eliminating message passing, redundancy of data storage, or both. Redundancy elimination can correspond to consolidating message passing operations, data storage operations, or both, in repeated operations. This can involve identifying duplicate or redundant data requests. The screening or filtering of duplicates can be performed by a coordinator that resides in the NWDAF service instance set, the NF service instance set, or the data storage function. The data storage function can be operably coupled to multiple NWDAF service sets.

[0099] In various embodiments, a NWDAF SISC (also referred to as a framework function) processes data collection on behalf of one or more NWDAF instances or service instances in a set of service instances. The NF SISC can collect the required data and send it to the NWDAF SISC, a NWDAF service instance, or both. The data is sent via a data storage function, which can store the data for fast retrieval (e.g., if the same data is requested again later).

[0100] In various embodiments, a coordinator in the data storage function receives data requests from the NWDAF SISC or NWDAF instances or NWDAF service instances, determines whether the data has already been collected and stored in the data storage function, and if necessary, requests the data from the NF on behalf of the NWDAF SISC or NWDAF service instance. Thus, the data storage function can handle data requests from the NWDAF to reduce duplication in data requests, responses, and storage, while also providing previously collected data to the NWDAF when available.

[0101] Thus, a coordinator function (which can be implemented in the network, e.g., using computing and communication devices in a data center) operates to support data analytics. The coordinator can be associated with one of: a set of network data analytics function (NWDAF) service instances (or a set of NWDAFs); a set of network function service instances (or a set of NFs); and a data storage function outside of the set of NWDAF service instances and the set of network function service instances. The coordinator can operate to determine data items that are generally needed by more than one of the set of NWDAF service instances. This can involve receiving multiple requests for such data items and identifying redundancies inherent in the multiple requests. The coordinator can then eliminate these redundancies. The coordinator can initiate the delivery of the data items from the set of network function service instances, the data storage function, or both, to the more than one NWDAF instance or NWDAF service instance. This initiation can involve initiating retrieval of the data items from the NF instances or NF service instances or the data storage function. The initiation can involve checking whether the data items are stored by the data storage function. The delivery of the data items can include sending a message containing part or all of a single instance of the data item such that the more than one NWDAF instance / service instance receives the data item based on communication of that same single instance. In other words, although multiple NWDAF instances / service instances can receive the data item, the delivery of the data item to different ones of the NWDAF instances / service instances can be at least partially consolidated to eliminate redundancies.

[0102] When the coordinator is associated with a set of NWDAF service instances, initiating the transfer of the data item can include requesting the data item from the set of network function service instances, and the transfer of the data item can include sending a message from the data storage function when the set of network function service instances notifies of the request from the coordinator. The coordinator can accordingly send a first request to the set of network function service instances indicating that the data item is required by a subset of the identities of more than one NWDAF instance / service instance in the set of NWDAF service instances. The transfer of the data item can then involve the coordinator receiving a message including the data item. Still further, the data storage function can receive a message indicating that the data item is requested by the coordinator.

[0103] When the coordinator is associated with a set of network function service instances, initiating the transfer of the data item can include instructing the data storage function to send the data item in one message or multiple messages to more than one NWDAF instance / service instance. The more than one NWDAF instance / service instance can be included in one set of NWDAF service instances or be included in different sets of NWDAF service instances. Initiating the transfer of the data item can include sending the data item from the set of network function service instances to the data storage function.

[0104] When the coordinator is associated with a data storage function, determining the data item can be based on one or more requests from one or both of: Figure 3B one or more other coordinators of a set of NWDAF service instances in the network function service instances, and Figure 3C one or more of the NWDAF instances or NWDAF service instances in the network function service instances. Initiating the transfer of the data item can include initiating the data storage function to transfer the data item when the data item is stored by the data storage function, and otherwise initiating the provision of the data item from the set of network function service instances to the data storage function when the data item is not in storage of the data storage function. When the data item is provided from the set of network function service instances, the coordinator can request the data item from the set of network function service instances. Upon receiving the data item at the data storage function, the data storage function or the coordinator can store the data item and forward the data item to more than one NWDAF instance or NWDAF service instance.

[0105] Figures 4AA-4ACAn example signaling procedure 400 is shown for data collection and data analytics provisioning, including detailed procedures to support data collection and provision of analytics results. In the illustrated procedure, there are two representative sets of NFs (NF-A set 330 and NF-B set 340) and one NWDAF set 310. For illustration purposes, each NF set has two NF Sis. The data storage function 350 can be a Unified Data Repository (UDR), or a UDSF, or any storage function.

[0106] In the illustrated embodiment, each of the NWDAF instances / Sis 311 and 312 can perform discovery of the set(s) of NFs (e.g., NF-A set 330 and NF-B set 340) and / or subset(s) of NFs and / or NF Si(s) (e.g., NF-A instance / Si 333, NF-A instance / Si 334) that are capable of provisioning network data for data analytics. The subset of NFs can serve a service area, which can be represented by a NF subset ID or a NF service area ID. The subset of NFs can also be referred to as a NF Si subset.

[0107] When a NF SI or NF Set is instantiated, the NF SI or NF Set registers itself with the NRF 401 by providing the NF profile or metadata to the NRF 401. The NF profile can include the information described in clause 6.2.6 of 3GPP TS 23.501, Release 15.4.0, published in December 2018, and some other information. For example, the NF profile or metadata of the NWDAF SI Set 310 or NWDAF SI Subset or NWDAF instance / SI 311 / 312 can include one or more of the following information: type(s) of data analytics service(s) that can be provided by the NWDAF SI Set 310 or NWDAF SI Subset or NWDAF instance / SI 311 / 312 (e.g., mobility management, traffic routing, UPF load, IoT security, UE mobility pattern, UE communication pattern), address of the NWDAF (e.g., IP address or FQDN or ID), Public Land Mobile Network (PLMN) ID, S-NSSAI(s) that the NWDAF can serve, Service Area and / or Service Zone ID, service instance ID, Set ID, Subset ID, number of SIs within the NF Set or within the NF Subset, PLMN ID, UE ID, UE group information (e.g., internal group ID, external group ID), Local Area Data Network (LADN) ID(s), Public Land Mobile Network (PLMN) ID(s).

[0108] The NF profile can include one or more of the following information:

[0109] a. storage capacity (e.g., 100 trillion bytes) and current usage capacity (e.g., 50 trillion bytes);

[0110] b. Supported communication rate: e.g. 10,000 queries per second, 1 Giga Byte per second (GByte / s) data rate. This parameter helps the NWDAF to select a storage function to meet its processing requirements. For example, some data analytics require a lot of data queries but the data volume is small. Analyzing UE mobility patterns can be an example of this type of data queries. Some functions such as AMF or SMF can request UE mobility pattern analysis periodically. In some other examples, the number of queries is small but the data volume is large. For example, analyzing traffic routing and QoS or QoE. The NWDAF instance / SI 311 or 312 can analyze QoS or QoE performance for a large number of UEs once a day. For example, the NWDAF instance / SI can send one request to the storage function to get data from a set of UEs with 1 million UEs. The storage function can send back a lot of data records such as 10 million data records for 1 million UEs.

[0111] c. Data type(s): e.g. data collected from UE(s) such as QoS, QoE information, UE location information; data collected from NFs such as PDU session information, UE location information.

[0112] d. Data type ID(s) and data collection attribute(s) currently collected by other NWDAF set(s) and / or NWDAF instance(s) / SI(s). The NWDAF instance / SI 311 or 312 can use this information to identify other NWDAF set(s) or NWDAF instance(s) / SI(s) that are collecting the same data type ID(s) with the same or different data collection attributes. The NWDAF instance / SI 311 or 312 can use this information to avoid duplicate data collection. For example, the NWDAF instance / SI 311 or 312 can not send a data collection request or a data collection subscription to the same NF set(s) 330 or 340 and / or NWDAF instance(s) / SI(s) 311 or 312 that already provide the same data to be collected. The NWDAF instance / SI 311 or 312 can adjust the data collection attributes to avoid duplicate data collection where the data type ID is requested by two or more NWDAF sets and / or two or more NWDAF instances / SIs with the same or partial data collection attributes.

[0113] e. SF address such as IP address or FQDN of the SF set or SF subset or SF SI.

[0114] After a NF SI set (e.g., NF-A set 330 and NF-B set 340) or a NF SI subset or NF SI registers with NRF 401, NRF 401 may subscribe to the NF SI set or NF SI subset or NF SI to receive load information. In the case of NWDAF, a set of NWDAF instances / SIs 311 or 312 may provide load information, such as how many NWDAF instances / SIs are currently busy or idle, or the percentage of the resources of the NWDAF set that are currently busy or idle.

[0115] refer to Figure 4AA At step 410, the NF instance / SI (e.g., NF-A instance / SI 333) needs to use the data analysis service of NWDAF. The NF-A instance / SI 333 sends a message to the network repository function (NRF) (e.g., NRF 401) to discover the NWDAF set 310 and / or the NWDAF instance / SI (e.g., NWDAF instance / SI 311). This message may carry one or more of the following information: service type of NF-A instance / SI 333, service type of NWDAF or data analysis service(s) type of NWDAF (e.g., mobility management, traffic routing, UPF load, IoT security, UE mobility mode, UE communication mode), duration of using data analysis service (e.g., start and end time of using data analysis service(s) by NF-A instance / SI 333), network information (e.g., S-NSSAI(s), NSI-ID(s), DNN(s), PLMN ID(s), LADN ID(s), UE information (e.g., internal group ID, UE ID(s)), application information (e.g., application ID), NF information (e.g., NF ID). The data analysis service will be performed based on the input information.

[0116] The message at step 410 may be implemented by using the NF discovery service of the NRF 401, such as the Nnrf_NFDiscovery service described in 3GPP TS 23.502, clause 5.2.7.3. The NF-A SI 333 may send an Nnrf_NFDiscovery_Request message to the NRF 401 to discover the NWDAF set 310 or NWDAF instance / SI 311 that can support the requested service of the NF-A SI 333.

[0117] At step 412, the NRF 401 can send information, such as NF profile or metadata, to identify: a NF set, e.g., the NWDAF set 310; and / or a NF instance ID, which is a NWDAF instance; and / or a NF SI, e.g., the NWDAF SI 311. The NWDAF set 310 can be identified by a NF set ID, which is a NWDAF set ID (identifier), and / or a NF set address(es), which is a NWDAF set IP address(es), and / or a FQDN of the NWDAF SI 311. The NWDAF instance can be identified by a NWDAF instance ID and or a NWDF set ID. The NWDAF SI 311 can be identified by a NWDAF set ID and / or a NWDAF subset ID and / or a NWDAF service set ID and / or a NWDAF SI set ID and / or a NWDAF instance ID and / or a NWDAF SI ID. The NWDAF subset ID and the NWDAF SI ID can be IP address(es) or FQDN.

[0118] In some embodiments, the NWDAF instance / SI 311 can be accessed by other NF instances / SIs. In this case, the NWDAF SI ID and / or the NWDAF SI endpoint address(es) can be used by other NF instances / SIs to request one or more data analytics services.

[0119] In some other embodiments, the NWDAF SI 311 is hidden within the NWDAF SI set 310. In this case, the NRF 401 can only provide the NF-A instance / SI 333 with the NWDAF SI set ID and / or the NFWDAF address(es).

[0120] In another embodiment, the NF SI set can be distributed across multiple data centers or geographical locations. In this case, the NRF 401 can provide the NF-A SI 333 with the NWDAF SI set ID and / or a NWDAF SI subset ID (or a NWDAF service area ID). Using the NF received from the NRF, the NF-A instance / SI 333 can select a NWDAF SI set 310 or a NWDAF SI subset of the NWDAF instance / SI 311.

[0121] At step 414, the NF-A instance / SI 333 can send a data analytics request or a data analytics subscription message to the NWDAF SI set 310 or the NWDAF instance / SI 311 to request or subscribe to analytics data.

[0122] a. If the NRF 401 provides a NWDAF SI set ID, the NF-A instance / SI 333 sends a message to the address of the NWDAF SI set 310 with the NWDAF SI set ID;

[0123] b. If the NRF 401 provides a NWDAF SI set ID and / or a NWDAF SI subset ID, the NF-A SI 333 sends a message to the address of the NWDAF SI subset with the NWDAF SI subset ID.

[0124] c. If the NRF 401 provides a NWDAF SI ID, the NF-A instance / SI 333 sends a message to the address of the NWDAF instance / SI 311 with the NWDAF instance / SI ID.

[0125] d. If the NRF 401 provides a NWDAF SI set ID and / or a NWDAF service set ID, the NF-A instance / SI 333 sends a message to the address of the NWDAF service set with the NWDAF service set ID.

[0126] The message from the NF-A SI 333 can carry one or more of the following information: type(s) of data analytics service, data analytics attributes. The data analytics attributes can include one or more of the following attributes:

[0127] a. Network information: e.g. PLMN ID(s), S-NSSAI(s), NSI-ID(s), Data Network Name(s) (DNN), Data Network Access Identifier(s) (DNAI);

[0128] b. UE information: UE ID(s) (e.g. SUPI, GPSI), internal group ID;

[0129] c. NF information: e.g. UPF(s), AMF set ID, RAT, RAN ID(s), Cell ID(s);

[0130] d. Application information: such as Application ID, AF-Service-ID; and

[0131] e.Data analytics duration: In case NF-A instance / SI 333 sends a subscription message, NF-A instance / SI 333 can indicate when NF-A instance / SI 333 wants to receive past or future analytics data, and the specific time period(s) of the day that NF-A instance / SI 333 can receive analytics data. For example, NF-A SI 333 can want to receive analytics data from day 1 to day 2 and / or at 1:00-1:30 AM and / or every day of the week.

[0132] In one embodiment, the signaling and messaging of step 414 can be implemented by using a NWDAF service, such as Nnwdaf_Analyticslnfo_Request or Nnwdaf_EventsSubscription_Subscribe, such as described in 3GPP TS 23.502 version 15.3.0. In the Nnwdaf_Analyticslnfo_Request or Nnwdaf_EventsSubscription_Subscribe message, NF-A instance / SI 333 can include some of the parameters described above. The NWDAF can provide analytics information to NF-A instance / SI 333 according to the information provided with the data analytics attributes. For example, if the type(s) of data analytics service is UE mobility analytics information, and the target UE ID is provided in the UE information, then the NWDAF will provide the UE mobility analytics information for the target UE ID.

[0133] At step 416, if NF-A SI 333 sent a NWDAF set ID and / or a NWDAF subset ID, then the NWDAF SI SC function (or can be referred to as the NWDAF framework function) 315 can receive the message from NF-A SI 333. The NWDAF SI SC function 315 can select a NWDAF instance or a NWDAF SI, such as NWDAF instance / SI 311, in order to serve the data analytics service for NF-A SI 333.

[0134] At step 418, the NWDAF SI SC 315 or the selected NWDAF instance / SI 311 can send a data analytics request / subscription confirmation to NF-A instance / SI 333. This message can include one or more of the following information: the NWDAF SI ID that was selected to serve the NF-A instance / SI 333 request / subscription.

[0135] At step 420, the NWDAF SISC 315 can check whether a (data) storage function (e.g., data storage function 350) has been selected. A storage function needs to be selected so that data collected from NFs, UEs, AFs can be stored in the storage function. If a storage function has been selected by the NWDAF SISC 315 or by the NWDAF instance / SI 311, the storage function ID can be stored in the NWDAF SISC 315 and / or the NWDAF instance / SI 311. The NWDAF instance / SI 311 and the NWDAF SISC 315 can communicate to identify the selected storage function. The (data) storage function 350 can be any storage function, such as a UDR SI of a UDR set and / or a UDR set; or a UDSF SI of a UDSF set and / or a UDSF set.

[0136] At step 422, if the (data) storage function 350 is not selected, or the storage function needs to be re-selected, the NWDAF instance / SI 311 can send a discovery storage function request or a discovery storage function set request message to the NRF 401. The message can include one or more of the following information: type(s) of data collected or data type ID(s) (e.g., PDU session context information, QoS information, QoS notification control message, UE mobility information), duration of data collection, time of day when data can be collected, service area, internal group ID(s) of UE group(s), external group ID(s), UE ID(s), S-NSSAI.

[0137] At step 424, the NRF 401 can send one or more SF profiles of (multiple) storage function (SF) SI set(s), SF SI subset(s), SF instance(s), SF service set, or SF SI(s). The (data) storage function 350 can be a UDSF, a UDR, or any storage function. The NWDAF instance / SI 311 can select a SF instance, or a SF SI set or SF SI subset of SF SI from the SF profiles provided by the NRF 401.

[0138] At step 426, the NWDAF instance / SI 311 can send a data notification subscription message to the selected SF set or SF subset or SF instance or SF SI ID for data type ID(s). The message can include data type ID(s), one or more attributes of data collection attributes for each data type ID, such as S-NSSAI, DNN, UE location, NF address(es), internal group ID(s).

[0139] The messaging of step 426 can be implemented, for example, by using the data management subscription service (Nudr_DM_Subscribe) of the UDR. The NWDAF instance / SI 311 can request data collection from other NFs, such as the AMF. The AMF instance / SI can send the collected data to the UDR. The UDR will notify the NWDAF instance / SI 311 that new data is available by using the Nudr_DM_Notify service. The UDR can send one notification for one data chunk, such as every 100 data records. The UDR can send one notification for one data chunk only when the amount of collected data reaches a threshold, for example, 10 megabytes of data. The UDR can send one notification at a specific time of the day, for example, every day at 1:00 AM. The notification can indicate the data type(s) ID(s) and can include one or more associated information, such as the NF ID providing the data, the duration, the UE location, the UE group ID (e.g., internal group ID, UE ID(s)).

[0140] At step 428, the SF 350 SI set, or the SF 350 SI subset, or the SF 350 instance, or the SF service set, or the SF 350 SI can send a data notification subscription acknowledgement to the NWDAF instance / SI 311 to acknowledge the receipt of the message at step 426.

[0141] Referring now to Figure 4AB At step 430, the NWDAF instance / SI 311 can need to collect data from one or more network functions, such as the NF-A set 330 and the NF-B set 340. For illustration, the NWDAF instance / SI 311 can need to collect data from the NF-A set 330. The NWDAF instance / SI 311 can send a request to the NRF 401 to discover the NF(s) that can include, but are not limited to, the NF-A set 330 and / or the NF-A subset, and / or the NF-A instance / SIs 333 and 334. The NWDAF instance / SI 311 can include one or more of the following information:

[0142] a. Network information: for example, PLMN ID(s), S-NSSAI(s), NSI-ID(s), DNN(s), DNAI(s) from which to collect data;

[0143] b. UE information: UE ID(s) (e.g., SUPI, GPSI) for which to collect data, internal group ID;

[0144] c. NF information: for example, UPF ID(s), AMF set ID, RAT, RAN ID(s), cell ID(s) for which to collect data;

[0145] d. Application information: such as Application ID for collecting data, AF-Service-ID.

[0146] e. Location information: e.g. (geo) area ID(s), (R)AN ID, cell (ID);

[0147] f. Storage duration: e.g. SF 350 will store data from start and end time;

[0148] g. Required storage capacity: estimated storage capacity that might be needed to store collected data; and

[0149] h. Data type ID(s): data type(s) to be collected.

[0150] The NWDAF instance / SI 311 can use the NRF 401 services, such as the Nnrf NFDiscovery service, to discover NF SI set(s) (e.g. NF-A set 330 and NF-B set 340), NF SI subset(s), NF instance(s), NF service set, NF SI (e.g. NF-A instance / SI 333, NF-A instance / SI 334, NFB instance / SI 343, NFB instance / SI 344). The NWDAF instance / SI 311 can use Nnrf NFManagement NFStatusSubscribe to subscribe to new NF registration, deregistration or NF profile update.

[0151] At step 432, based on the input information provided by the NWDAF instance / SI 311, the NRF 401 can configure one or more NF SI set 330 and 340 and / or NF SI subset(s) and / or one or more NF instance(s) and / or NF service set(s) and / or NF SI 333, 334, 343 and 344 profile(s).

[0152] Based on the NF profile information from the NRF 401, the NWDAF instance / SI 311 can select NF set(s) and / or NF subset(s) and / or NF instance(s) and / or NF service set(s) and / or NF SI to send data collection request or subscribe to the address of the selected NF entity. In this embodiment, as one example, NF-A 330 is selected for the NWDAF instance / SI 311 to collect data. But in general, the NWDAF instance / SI 311 can select any NF to collect network data for its analytics.

[0153] At step 434, if the NRF 401 provided NF-A set ID(s) and / or NF-A subset ID(s) and / or NF-A instance(s) and / or NF-A service set(s), the NWDAF SI 311 can send a data collection request / subscription to the address of the NF-A set 330 or NF-A subset, NF-A instance(s), or NF-A service set, which is received by the NF-A SI SC 335 that manages the NF-A set 330 or NF-A subset, or NF-A instance(s), NF-A service set, or NF-A SI. For example, the NF-A SI SC 335 receives a request from the NWDAF instance / SI 311. This message can include one or more of the following information:

[0154] a. Network information: e.g. PLMN ID(s), S-NSSAI(s), NSI-ID(s), DNN(s), DNAI(s) from which to collect data;

[0155] b. UE information: UE ID(s) (e.g. SUPI, GPSI) from which to collect data, internal group ID;

[0156] c. NF information: such as NF set ID(s), NF subset ID(s), NF SI ID(s) from which to collect data, e.g. UPF ID(s), AMF set ID, RAT, RAN ID(s), cell ID(s);

[0157] d. Application information: such as application ID, AF-service-ID from which to collect data.

[0158] e. Location information: e.g. geographical area ID(s);

[0159] f. Duration information: e.g. start and end time of data collection, which can be immediate or at some future time. The end time can be omitted, meaning that the NWDAF instance / SI 1 can send another message to unsubscribe from data collection;

[0160] g. Type of data to collect: e.g. PDU session information (start and end time of PDU session, QoS profile, QoS rule, type of PDU session, S-NSSAI, DNN), UE location, event ID(s);

[0161] h. ID or address (e.g. IP address or FQDN) of the SF set, or SF subset, or SF instance, or SF service set, or SF SI to which the collected data can be sent; and

[0162] i. ID and / or address (e.g., IP address or FQDN) of the set of NWDAFs, or subset of NWDAFs, or NWDAF instance, or set of NWDAF services or NWDAF SI that sent the data collection request. The NF-A instance / SI or NF-AS ISC can use this ID or address to which the collected data is sent, or send a notification of collected data, or acknowledge the request.

[0163] The messaging of step 434 can be implemented by using an event exposure service of the NF. For example, the SMF can provide the Nsmf_EventExposure service, in which the NWDAF instance / SI 311 can subscribe to session management events, such as a PDU session release event.

[0164] At step 436, the NF-A SI SC 335 can send a data collection request or a subscription acknowledgement to the NWDAF instance / SI 311. This is to acknowledge that the NF-A SI SC 335 received the request for data collection.

[0165] In some embodiments, step 438 can be performed after step 434 and before step 436. In some other embodiments, step 438 can be performed after step 436.

[0166] At step 438, the NF-A SI SC 335 can check the following conditions to avoid duplicating data collection:

[0167] a. If some other NF instance(s) / SI of the same NF set (in this embodiment, the NWDAF set 310) have already requested the same data type (same data type ID) with the same or different data collection attributes. If some other NF instance / SI (in this embodiment, the NWDAF instance / SI 311 and 312) have already requested the same data type ID(s), the NF-A SI SC 335 will update the existing data collection job within the NF-A set. If some other NF SI of the same NWDAF set have already requested the same data type, the collected data can be sent to the same storage function, so that the collected data can be shared among the NF SI of the same NF set (in this embodiment, the NWDAF set 310).

[0168] b. If some other NF SI of some other set of NFs (in this embodiment, the set of NWDAFs 310) has already requested the same data type, the collected data can be stored in the same or different storage function. If the collected data has already been sent to the same storage function, the NF-A SI SC 335 can update the existing data collection setting in the NF-A set 330 so that no additional data collection request is sent to the NF-A instances / SIs 333 and 334 of the NF-A SI set 330.

[0169] If the collected data has already been sent to another storage function, the NF-A SI SC 335 can update the data collection job within the NF-A set 330 so that the collected data can be sent to one or more storage functions. Alternatively, in step 436, the NF-A SI SC 335 can send to the NWDAF instance / SI 311 the address or ID of the storage function currently used to store the same collected data type(s). The NWDAF instance / SI 311 can access the notified storage function to obtain the required data.

[0170] At step 440, depending on the functionality of the NF-A instances / SIs 333 and 334, the NF-A SI SC 335 can send to the NF-A instances / SIs 333 and 334 capable of providing the required data either an NF data collection request or an NF data collection modification.

[0171] If the requested data type(s) has / have not been collected yet, the NF-A SI SC 335 can send to the NF-A instance(s) / SI(s) 333 and / or 334 an NF data collection request. This message can include one or more of the following information: data type ID(s), data collection attribute(s) per data type ID, address of the storage function (such as SF ID, SF IP address). If the NF-A SI SC 335 is responsible for sending the collected data to the NWDAF instance / SI 311 or the SF 350, the address of the SF 350 can be omitted.

[0172] If the requested data type(s) has / have been collected, the NF-A SI SC 335 can send to the NF-A instance(s) / SI(s) 333 an NF data collection modification. This message can include the data type ID(s) and one or more new attributes of the data collection attributes per data type ID. If the collected data can be sent to the address of another SF SI, another set of SF SIs, or additional SF SI or additional set of SF SIs, the message can include the SF address.

[0173] At step 442, the NF-A instance / SI 333 can send an NF data collection response to the NF-A SI SC 335 to acknowledge the receipt of the NF data collection request or modification of step 440.

[0174] At step 444, the NF-A instance / SI 333 collects data according to the data type ID(s) and data collection attributes received in step 440. For each collected data record, the NF-A instance / SI 333 can include a timestamp of the time the data is collected, the address and / or ID of the NF-A SI set 330 and / or NF-A SI subset and / or NF-A instance / SI 333 and / or one or more attributes described in the data collection attributes (e.g., UE ID, S-NSSAI, NSI-ID, application ID, UE location (e.g., represented by a geographical location in two or three dimensions and / or (R)AN address and / or cell ID)).

[0175] According to the parameters provided in step 440, the NF-A instance(s) / SI(s) 333 can send a data transfer request to the SF or NF-A SI SC 335 or the NWDAF instance / SI 311. The message can carry the collected data according to the parameters provided in step 440. The NF-A instance(s) / SI(s) 333 can send the collected data immediately or at certain configured schedule time or time period when the network load can be low to avoid network congestion. The message in step 444 can be implemented by using the event exposure notification service of the NF-A. For example, the AMF can use the Namf_EventExposure_Notify service to send data to the NFs that have subscribed to receive UE mobility events. In another example, the SMF can use the Nsmf_EventExposure_Notify service to send data to the NFs that have subscribed to receive session management events.

[0176] If the collected data is sent from the NF-A instance / SI 333 to the NF-A SI SC 335, the NF-A SI SC 335 can collect data from one or more NF-A instance / SI 333 and 334 to send in one or more batches or immediately after receiving from the NF-A instance(s) / SI(s) 333 to the SF and / or the NWDAF instance / SI 311. The NF-A SI SC 335 can send the collected data to the SF and / or the NWDAF instance / SI 311 at a schedule time or time period when the network load can be low to avoid congestion.

[0177] At step 446, the (data) SF 350 or the NWDAF instance / SI 311 can send a data transfer response to the NF-A instance / SI 333 or the NF-A SI SC 335, depending on which entity has sent the data transfer request in step 444.

[0178] At step 448, the (data) SF 350 can send a data notification to the NWDAF instance / SI 311 if the NWDAF instance / SI 311 has subscribed to the data collection notification in step 426. The message can indicate whether one or more attributes of the data type(s) and data collection attributes, such as collection period, UE location (e.g., RAN address(s), RAN cell ID(s), registration area), S-NSSAI, DNN, internal group ID, have been received.

[0179] The messaging of step 448 can be implemented, for example, by using the Nudr_DM_Notify service of the UDR. The UDR can notify the NWDAF instance / SI 311 about the newly collected data records, e.g., new records of data type(s) ID, and some information associated with the data collection attributes, such as UE ID(s), UE group information (e.g., internal group ID), NF ID(s).

[0180] Reference Figure 4AC At step 450, in some embodiments, the NF-A SI(s) 333 can store the collected data in the NF-A SI set (data) storage 332. The message NF data storage request can contain one or more of the following information: collected data record(s), and for each collected data record, the NF-A instance / SI 333 can include a timestamp of the collection data time, NF-A set ID and / or NF-A subset ID, NF-A service set ID and / or NF instance ID and / or NF SI ID and / or one or more attributes described in the data collection attributes (e.g., UE ID, S-NSSAI, NSI-ID, application ID).

[0181] At step 452, the NF-A set SF 332 can send an NF data storage response to the NF-A instance / SI 333 to acknowledge the received data and / or to acknowledge that the data is successfully stored. If the data storage has an error (such as the storage is full), the NF-A SI set data storage 332 can send an error code indicating the reason.

[0182] At step 454, the NF-A instance / SI 333 can send a data availability notification to the NF-A SI SC 335 to inform the NF-A SI SC 335 that one or more data records have been stored in the NF-ASI set data store 332.

[0183] At step 456, the NF-A SI SC 335 can send a NF data retrieval request to the NF-ASI set data store 332. This message can be sent immediately after step 454, or at a time when network load can be lower. This message can contain one or more of the following parameters: data type ID(s), time period for which data records are to be retrieved.

[0184] The messaging of step 456 can be implemented, for example, by using the Nudr_DM_Query service of the UDR. For example, the AMF can send a Nudr_DM_Query request to the UDR set or UDR SI to retrieve the collected data.

[0185] In another embodiment, the messaging of step 456 can be implemented, for example, by using the Nudsf_UnstructuredDataManagement_Query service of the UDSF to retrieve the collected data.

[0186] At step 458, the NF-A SI set data store 332 can send the requested data records to the NF-A SI SC 335.

[0187] At step 460, the NF-A set SI SC 335 can send the data records to the SF 350. Each data record can have a timestamp as well as one or more attributes of the data collection attributes.

[0188] The messaging of step 460 can be implemented, for example, by using the Nudr_DM_Create Request service of the UDR. For example, the AMF can send a Nudr_DM_Query request to the UDR SI to store the collected data.

[0189] In another embodiment, the messaging of step 460 can be implemented, for example, by using the Nudsf_UnstructuredDataManagement_Create service of the UDSF to store the collected data.

[0190] At step 462, the (data) SF 350 can send a data transfer response to the NF-AS ISC 335 to acknowledge the step 460 of receiving the data. For example, the data transfer response can be implemented by using the Nudr_DM_Create response service or Nudr_DM_Query response of the UDR.

[0191] At step 464, the SF 350 can send a data notification to the NWDAF instance / SI 311 if the NWDAF instance / SI 311 has subscribed to the data collection notification in step 426. The message can indicate whether one or more attributes of the data collection attributes and the data type(s) have been received, such as the collection period, location (e.g., RAN address(es), RAN cell ID(s), registration area, S-NSSAI, DNN, internal group ID).

[0192] As an alternative to step 460, the NF-AS ISC 335 can send the data record(s) directly to the NWDAF instance / SI 311 that requested the data collection. Each data record can have a timestamp of the data record, and one or more attributes of the data collection attributes. This message is not shown in Figures 4AA-4AC . The NWDAF instance / SI 311 can send an acknowledgement to the NF-AS ISC 335.

[0193] At step 466, the NF-AS ISC 335 can send a data collection response or notification to the NWDAF instance / SI 311 to inform that the data to be collected has been sent to the SF 350. The notification can include one or more of the following information: the number of data records collected, the time period of the data collected (start and end time), the location(s) of the data collected (e.g., RAN address(es) or RAN cell ID(s), geographic area ID(s)).

[0194] At step 468, the NWDAF instance / SI 311 can retrieve the collected data from one or more NF sets. The NWDAF instance / SI 311 can send a data retrieval request to the SF 350 to get the collected data. The message can include one or more of the following information: one or more attributes of the data collection attributes and the data type(s) ID, such as the collection time period(s), location(s), S-NSSAI, internal group ID, DNN, NF ID(s), NF set ID(s), NF instance ID(s), NF service set ID(s), NF SI ID(s).

[0195] The messaging of step 468 can be implemented, for example, by using the Nudr_DM_Query service of the UDR. For example, the NWDAF instance / SI 311 can send an Nudr_DM_Query request to the UDR to retrieve the collected data.

[0196] In another embodiment, the messaging in step 468 can be implemented, for example, by using the Nudsf_UnstructuredDataManagement_Query request service of the UDSF to retrieve the collected data.

[0197] At step 470, the SF 350 can send one or more data retrieval response messages carrying the requested data to the NWDAF instance / SI 311. If the SF is a UDSF, the messaging in step 470 can be implemented by using, for example, the Nudsf_UnstructuredDataManagement_Query response service of the UDSF.

[0198] The NWDAF instance / SI 311 can store the received data in the NWDAF set storage 313, such as the UDSF storage function.

[0199] At step 472, the NWDAF instance / SI 311 performs the data analytics service received at step 414.

[0200] At step 474, the NWDAF instance / SI 311 can send a data analytics response or a data analytics notification to the NF that sent the message at step 414.

[0201] The messaging of step 474 can be implemented by using the Nnwdaf_AnalyticsInfo response or the Nnwdaf_EventsSubscription_Notify service of the NWDAF.

[0202] Figures 4BA-4BC Another data collection method 4000 is shown, wherein Figures 4AA-4AC Some steps of Figure 3B The functions of the NWDAF set and the NF set described in Figure 3B The functions of the NWDAF set and the NF set described in Figure 3A The functions of the NWDAF set and the NF set described in

[0203] Figure 4BA Steps 4010 to 4024 of Figure 4AA Steps 410 to 424 of

[0204] At step 4026, the NWDAF instance / SI 311 may send a data notification subscription or data request or data subscription request message to the address of the DSF set or DSF subset or DSF instance or DSF service set or DSF SI for the data type ID(s). The message may include the data type ID(s), one or more attributes of the data collection attributes for each data type ID, such as PLMN ID, S-NSSAI(s), DNN(s), UE location, NF address(es), internal group ID.

[0205] At step 4028 , the DSF 350 entity, such as DSF 350 SI SC, or DSF 350 instance, or DSF 350 service set, or DSF 350 SI, may send a data notification subscription confirmation to the NWDAF instance / SI 311 to confirm receipt of the message in step 4026 .

[0206] At step 4030, instead of Figure 4AB In step 430, the NWDAF instance (or SI) 311 sends a Discover NF (Set) Request, and the Data Storage Function (DSF) 350 may send a Discover NF (Set) Request to the NRF 401. This message is intended to discover one or more NF entities (such as (multiple) NF instances and / or (multiple) NWDAF sets and / or (multiple) NWDAF SIs) that can provide the requested data.

[0207] At step 4032, instead of Figure 4AB In step 430 , the NWDAF instance / SI 311 receives the Discover NF Response, and the DSF 350 may receive the Discover NF Set Response from the NRF 401 .

[0208] At step 4034, instead of Figure 4ABThe DSF 350 can send a data collection request / subscription to the discovered NF(s), such as NF-A SI SC 335, or NF-A instance(s) or NF-A SI, in step 436 of the method of

[0209] In step 4036, instead of Figure 4AB the DSF 350 can receive a data collection request / subscription confirmation for the message sent in step 4034, the confirmation coming from NF-A SI SC 335, NF-A instance(s) or NF-A SI.

[0210] Steps 4038 to 4072 are substantially similar to steps 438 to 474 of the method of Figure 4AB and 4AC One difference is that step 466 of the method shown in Figures 4BA-4BC may not be needed, because NF-A 330 can not communicate directly with the functions of the NWDAF set 313. Figure 4AC

[0211] Figure 4CA and 4CB shows another data collection method 4100, in which some steps of the method of Figure 3C are modified according to the functions of the NWDAF set and the NF set described in Figures 4AA-4AC . Figure 3C The functions of the NWDAF set and the NF set described in Figure 3A are modified from the functions described in

[0212] Figure 4CA Steps 4110 and 4112 of the method of Figure 4AA are substantially similar to steps 410 and 412 of the method of

[0213] ​At step 4114, there may be possible modifications to the information of the NWDAF set 310 obtained at steps 4110 and 4112. For example, at step 4112, the NRF 401 may provide information of the NWDAF set 310 (such as a profile of the NWDAF set 310) or (multiple) NWDAF instances or NWDAF SI (NWDAF instance / SI) 311 profiles. Similar to Figure 4AA At step 414, if the NF-A instance / SI 333 selects the NWDAF set 310, the NF-A instance / SI 333 may send a data analytics request / subscription to the NWDAFSI SC 315. If the NF-A instance / SI 333 selects the NWDAF instance / SI 311, at step 4114, the NF-A SI 333 may send a data analytics request / subscription to the selected NWDAF instance(s) / SI(s) 311.

[0214] At step 4116, if data has been collected and is available in the NWDAF collection 310, the NWDAF instance / SI 311 may access the collected data and perform data analysis.

[0215] At step 4118, the selected NWDAF instance / SI 311 may send a data analysis response or subscription confirmation to the NF-A instance / SI 333. If the data required for the analysis is already available in the NWDAF collection 310 or the NWDAF instance 311, or the required analysis is available, then in step 4118, the NWDAF instance / SI 311 may send a data analysis response to the NF-A instance / SI 333. This message carries the requested analysis. Steps 4120 to 4144 may be skipped. This means that the NWDAF instance / SI 311 may not need to discover the DSF 350, as shown in steps 4122 and 4124; the NWDAF instance / SI 311 may not need to discover (multiple) NFs to collect data, as shown in steps 4126 and 4128.

[0216] If, in step 4114 , the NF-A instance / SI 333 sends a data analytics subscription to the NWDAF instance / SI 311 , then in step 4114 , the NWDAF instance / SI 311 may send a data analytics subscription confirmation to the NF-A instance / SI 333 .

[0217] At step 4120, as in Figure 4AA As described in step 420 of , the NWDAF instance / SI 311 may communicate with the NWDAFSI SC 335 .

[0218] At step 4122, the NWDAF instance / SI 311 may use the services of the NRF 401 to discover the NF(s) that can provide the required data. This step is similar to Figure 4AA Step 422.

[0219] At step 4124, the NRF 401 may inform the NWDAF instance / SI 311 of the NF set(s) and / or NF instance(s) and / or NF SI(s) that may provide the data.

[0220] At step 4126, the NWDAF instance / SI 311 may use the services of the NRF 401 to discover NF sets and / or NF instances and / or NF service sets and / or NF SIs that can provide the required data. The NWDAF instance / SI 311 may send a Discover NF (set) request to the NRF 401.

[0221] In step 4128, the NRF 401 may send a Discover NF (aggregate) response to the NWDAF instance 311. The message may include (multiple) NF aggregate profiles and / or (multiple) NF instance profiles.

[0222] At step 4130, the NWDAF instance / SI 311 may send a data request or data subscription to the DSF 350. The message may include NF set ID(s) and / or NF instance ID(s) and / or NF service set ID(s) and / or NF SI ID(s) and / or their NF addresses(s) that can provide data, data types to be collected, and data attributes to be collected.

[0223] At step 4132, the DSF 350 can check if the requested data is already stored in the DSF 350. If the requested data is already stored in the DSF 350, then steps 4132 and 4134 can be skipped. In step 4136, the DSF 350 can send the requested data to the NWDAF instance / SI 311. If the data is not stored in the DSF 350, the DSF 350 can forward the data request or data subscription to the NF set(s) and / or NF instance(s) and / or NF SI(s) according to the information received in step 4130. If the DSF 350 has already subscribed to the NF set(s) and / or NF instance(s) / SI(s) for the type of data to be collected, but one or more attributes are different from the previous subscription, the DSF 350 can send a data subscription modification (or update) to the NF set(s) and / or NF instance(s) / SI(s) to modify or update the existing data subscription. Another method to modify (or update) the existing subscription is to send an unsubscribe message for the existing subscription and send another subscription message that carries the parameters of the previous subscription and additional new parameters.

[0224] One example of message 4130 is to send a subscription to an AMF instance / SI to receive UE location notifications. The message is a Namf_EventExposure_Subscribe request with, for example, UE IDs = 12345, 12346, 12347. If the DSF 350 finds that it has previously subscribed to UE location information for UE ID = 12345, the DSF 350 can modify the previous subscription by sending two messages in any order at step 4132: one message is a Namf_EventExposure_UnSubscribe request to unsubscribe to receive location information for UE ID 12345, and the other message is a Namf_EventExposure_Subscribe request to subscribe to UE location information for UE IDs = 12345, 12346, 12347. Another method to modify the existing data subscription is that since the UE 12345 location information was previously subscribed to, the DSF can send a Namf_EventExposure_Subscribe request for UE IDs = 12346, 12347 at step 4132.

[0225] At step 4134, if the DSF 350 sent a data request at step 4132, the NF instance(s) / SI(s) 333 or NF Set Coordinator (e.g., NF-A SI SC 335) can send the requested data in a data response message to the DSF 350. If in step 4132, the DSF 350 sent a data subscription (or data subscription update), the NF instance(s) / SI(s) (or NF Set Coordinator) can send a data subscription acknowledgement.

[0226] At step 4136, if in step 4130, the NWDAF instance / SI 311 sent a data request to the DSF 350, the DSF 350 can send a data response to the NWDAF instance / SI 311 that carries the requested data.

[0227] If in step 4130, the NWDAF instance / SI 311 sent a data subscription message, the DSF 350 can send a data subscription acknowledgement to the NWDAF instance / SI 311.

[0228] At step 4138, if the DSF 350 sent a data subscription or data subscription update in step 4132, the NF instance(s) / SI(s) 333 or NF Set Coordinator (e.g., NF-A SI SC 335) can send a data notification to the DSF 350. This message can contain the requested data.

[0229] At step 4140, the DSF 350 can store the received data in a storage unit. The DSF 350 can forward the received data to the NWDAF instance / SI 311.

[0230] At step 4142, the DSF 350 can perform data analytics to produce the requested analytics.

[0231] At step 4144, the NWDAF instance / SI 311 can send a data analytics response to the NF Set (e.g., NF-A Set 330) and / or NF instance / SI 331 that requested the analytics at step 4114.

[0232] Figures 5A-5C Another example signaling procedure 500 is shown that illustrates data collection and data analytics provisioning. In this example, the DSF 350 sends a data subscription request to the NF-A SI SC 335 at step 5010. The data subscription request can include a data analytics request. Figures 5A-5C In the embodiment shown in FIG. 5, the DSF 350 can send a data subscription request to the NF-A SI SC 335 at step 5010. The data subscription request can include a data analytics request. The data analytics request can include a data analytics request ID, a data analytics request type, and a data analytics request description. The data analytics request type can be a data analytics request type for a data analytics request. The data analytics request description can include a description of the data analytics request.

[0233] Reference is made to Figure 5AAt step 510, one or more NF Sis (e.g., NF-A Sis 333 and / or 334) need data analytics service(s) using NWDAF. The NF-A instance / Si 333 and / or 334 communicates with the NF-A SI SC 335 to indicate which data analytics service(s) are needed. The NF-A SI SC 335 sends a message to the NRF 401 to discover a NWDAF set and / or a NWDAF subset and / or a NWDAF instance and / or a NWDAF service set and / or a NWDAF Si. The message can carry information similar to the information in step 410 in FIG. 4, such as one or more of the following: type of data analytics service (e.g., mobility management, traffic routing, UPF load, IoT security, UE mobility pattern, UE communication pattern), duration of using the data analytics service (such as start and end time that the NF-A instance / Si 333 can use the data analytics service(s)), network information (such as S-NSSAI(s), NSI-ID(s), DNN(s), PLMN ID(s), LADN ID(s)), UE information (such as internal group ID, UE ID(s)), application information (such as application ID), NF information of the NF-A 33 (such as NF-A ID, and / or service(s) of the NF-A set and / or service(s) of the NF-A instance / Si 333). The data analytics service(s) will be performed based on the input information.

[0234] At step 512, the NRF 401 can send information such as NF profile of the NWDAF to identify the NF Si set(s) (which are the NWDAF Si set(s) 310, for example) and / or the NF instance(s) and / or the NF service set(s) (which are the NWDAF service set(s)) and / or the NF Si(s) (which are the NWDAF Si 311). The NWDAF Si set (or NWDAF set) 310 can be identified by the NF Si set ID as a NWDAF set ID (identifier) and / or the NF instance ID(s) and / or the NF Si set address(es) as the NWDAF Si set IP address(es) and / or the FQDN of the NWDAF Si 311. The NWDAF Si 311 can be identified by the NWDAF Si set ID and / or the NWDAF Si ID and / or the NWDAF instance ID and / or the NWDAF service set ID. The NWDAF Si address can be IP address(es) or FQDN or endpoint address(es).

[0235] In some embodiments, the NWDAF SI 311 can be accessed by other NF SIs 311. In this case, the NWDAF SI ID and / or endpoint address(es) can be used by other NF SIs to request data analytics services.

[0236] In other embodiments, the NWDAF instance / SI 311 is hidden within the NWDAF SI set 310. In this case, the NRF 401 can only provide the profile of the NWDAF set 310 to the NF- A SI SC 335.

[0237] In other embodiments, the NWDAF SI 311 is hidden within the NWDAF instance. In this case, the NRF 401 can only provide the profile of the NWDAF instance to the NF- A SI SC 335.

[0238] In some embodiments, the NF SI set can be distributed across multiple data centers or geographical locations. In this case, the NRF 401 can provide the profile of the NWDAF SI set 310 and / or a subset of NWDAF SIs (or a NWDAF SI service area) to the NF- A SI SC 335.

[0239] The NF-A SI SC 335 can use the NWDAF profile(s) provided by the NRF 401 to select one NWDAF set (e.g., the NWDAF set 310) or one NWDAF subset or one NWDAF instance or one NWDAF service set or one NWDAF SI (e.g., the NWDAF SI 311) to provide data analytics services.

[0240] At step 514, the NF-A SI SC 335 can send a data analytics request or data analytics subscription message to the selected NWDAF SI set 310. The NWDAF SI SC 315 receives the message.

[0241] If the NRF 401 provided the NWDAF SI set ID and / or address (such as IP address or FQDN), the NF-ASISC 335 sends the message to the address of the NWDAF SI set 310 with the NWDAF SI set ID.

[0242] If the NRF 401 provided the NWDAF SI set ID and / or address (such as IP address or FQDN) and / or the NWDAF SI subset ID and / or address (such as IP address or FQDN), the NF- A SI SC 335 sends the message to the address of the NWDAF SI subset with the NWDAF SI subset ID.

[0243] If the NRF 401 provides a NWDAF SI ID and / or address (such as IP address or FQDN), the NF-AS ISC 335 sends the message to the address of the NWDAF SI 311 with the NWDAF SI ID or address.

[0244] If the NRF 401 provides a NWDAF instance ID and / or address (such as IP address or FQDN), the NF-AS ISC 335 sends the message to the address of the NWDAF instance.

[0245] The message from the NF-AS ISC 335 can carry one or more of the following information: type(s) of data analytics service, data analytics attributes. The data analytics attributes can include one or more of the following attributes:

[0246] a. Network information: e.g., PLMN ID(s), S-NSSAI(s), NSI-ID(s), DNN(s), DNAI(s) for which analytics information is fetched;

[0247] b. UE information: UE ID(s) (e.g., SUPI, GPSI), internal group ID for which analytics information is fetched;

[0248] c. NF information: e.g., UPF ID(s), AMF set ID, RAT, RAN ID(s), Cell ID(s) for which analytics information is fetched;

[0249] d. Application information: such as Application ID, AF-Service-ID for which analytics information is fetched;

[0250] e. Data analytics duration: In case the NF-AS ISC 335 sends a subscription message, the NF-AS ISC 335 can indicate when in the future the NF-AS ISC 335 wants to receive analytics data, and the specific time period(s) of the day in which the NF-AS ISC 335 can receive analytics data. For example, the NF-AS ISC 335 can want to receive analytics data from day 1 to day 2, 1 :00-1 :30 AM, every day.

[0251] At step 516, if the NF-A SISC 335 sent the NWFDA Set ID and / or the NWDAF Subset ID, the NWDAF SISC 315 can receive a message from the NF-A SISC 335. The NWDAF SISC 315 can select a NWDAF instance / SI, such as the NWDAF instance / SI 311, to provide data analytics services for the NF-A SISC 335.

[0252] At step 518, the NWDAF SISC 315 or the selected NWDAF instance / SI 311 can send a data analytics request / subscription confirmation to the NF-A SISC 335. The message can include one or more of the following information: the NWDAF instance / SI ID that is selected to serve the NF-A SISC request / subscription.

[0253] At step 520, the NWDAF SISC 315 can check if a data storage function (e.g., the data storage function 350) has been selected. The storage function needs to be selected so that the data collected from the NF, UE, AF can be stored in the storage function. If the storage function has been selected by the NWDAF SISC 315 or by the NWDAF instance / SI 311, the storage function ID can be stored in the NWDAF SISC 315 and / or the NWDAF instance / SI 311. The NWDAF instance / SI 311 and the NWDAF SISC 315 can communicate to identify the selected storage function.

[0254] At step 522, if the (data) storage function 350 is not selected or the storage function needs to be re-selected, the NWDAF SISC 315 can send a discovery storage function request or a discovery storage function set request message to the NRF 401. The message can include one or more of the following information: the type(s) of data collected (e.g., PDU session context information, QoS information, QoS notification control message, UE mobility information), the duration of data collection, the time of day that data can be collected, the service area, the DNN.

[0255] At step 524, the NRF 401 can send one or more SF profiles of the (multiple) Storage Function (SF) SI set or (multiple) SF SI subset or (multiple) or (multiple) SF instance or SF service set or (multiple) SF SI to the NWDAF SI SC 315. The Storage Function 350 can be a UDSF, UDR or any storage function. The NWDAF SI SC 315 can select one SF SI set and / or SF SI subset and / or SF instance and / or SF service set and / or SF SI from the received (multiple) SF profiles for storing collected data.

[0256] At step 526, the NWDAF SI SC 315 can send a data notification subscription message to the selected SF set 350 or SF subset or SF instance ID or SF service set or SF SI ID for the (multiple) data type ID. The message can include one or more attributes of the data collection attributes per data type ID, such as S-NSSAI, DNN, UE location, (multiple) NF address, internal group ID.

[0257] At step 528, the SF 350 SI set or SF 350 SI subset or SF instance or SF service set or SF 350 SI can send a data notification subscription acknowledgement to the NWDAF SI SC function 315 to acknowledge the receipt of the message of step 526.

[0258] Reference Figure 5B At step 530, the NWDAF SI SC 315 can need to collect data from one or more network functions, such as NF-A set 330 and NF-B set 340. For illustration, the NWDAF SI SC 315 can need to collect data from NF-A 330. The NWDAF SI SC 315 can send a request to the NRF 401 to discover the (multiple) NF-A SI set 330 and / or (multiple) NF-A subset and / or (multiple) NF-A instance and / or NF-A service set and / or (multiple) NF-A SI 333 and 334. The NWDAF SI SC 315 can include one or more of the following information:

[0259] a. Network information: e.g. (multiple) PLMN ID, (multiple) S-NSSAI, (multiple) NSI-ID, (multiple) DNN, (multiple) DNAI from which to collect data;

[0260] b. UE information: (multiple) UE ID (e.g.: SUPI, GPSI), internal group ID for which to collect data;

[0261] c. NF information: such as NF-A set ID(s), and / or NF subset ID(s), and / or NF SIID(s). The NF-A information can be, for example, UPF ID(s) for collecting data, AMF set ID, RAT, RAN ID(s), cell ID(s);

[0262] d. Application information: such as application ID for collecting data, AF-service-ID.

[0263] e. Location information: for example, geographic area ID(s);

[0264] f. Duration of data collection: for example, start and end time of when the NF-A 330 will collect data;

[0265] g. Type of data to be collected.

[0266] At step 532, based on the input information provided by the NWDAF SI SC, the NRF can send the NF profile of NF set(s) and / or NF subset(s) and / or NF instance(s) and / or NF service set(s) and / or SF SI to the NWDAF SI SC 315. In some embodiments, the NRF 401 can be aware of the status of the NF set, NF subset, NF instance, NF service set, NF SI in the past and for a period of time in the future. The NF status can be, for example, available or unavailable, registered or deregistered. If the NF set or NF subset or NF instance, NF service set or NF SI is available for any period of time within the duration of data collection, the NRF 401 can send the NF discovery information to the NWDAF SI SC 315.

[0267] At step 534, if the NF profile(s) provided by the NRF 401 contains NF-A set ID and / or NF-A subset ID and / or NF-A instance ID and FQDN or IP address(es) of the NF instance and / or NF-A SI ID and FQDN or IP address(es) or endpoint address(es) of the NF SI, the NWDAF SI SC 315 can send a data collection request / subscription to the address of the NF-A set 330 or NF-A subset, which can be received by the NF-A SI SC that manages the NF-A set 330 or NF-A subset. For example, the NF-A SI SC 335 receives the request from the NWDAF SI SC 315. The message can include one or more of the following information:

[0268] a. Network information: e.g. PLMN ID(s), S-NSSAI(s), NSI-ID(s), DNN(s), DNAI(s) from which data is collected;

[0269] b. UE information: e.g. UE ID(s) (e.g. SUPI, GPSI), internal group ID for which data is collected;

[0270] c. NF information: e.g. UPF ID(s), AMF set ID, RAT, RAN ID(s), Cell ID(s) for which data is collected;

[0271] d. Application information: e.g. Application ID, AF-Service-ID for which data is collected.

[0272] e. Location information: e.g. Geographical Area ID(s) for which data is collected;

[0273] f. Duration information: e.g. start and end time for which data is to be collected, can be immediate or at some time in the future. The end time can be omitted, which means that the NWDAF instance / SI 1 can send another message to unsubscribe from data collection; the start time and / or end time can indicate a past or future time.

[0274] g. Type of data collected: e.g. PDU session information (start and end time of PDU session, QoS profile, QoS rule, type of PDU session, S-NSSAI, DNN), UE location, Event ID(s).

[0275] h. Address or ID of the SF set or SF subset or SF service set or SF instance / SI to which the collected data can be sent.

[0276] i. Address or ID of the NWDAD SI SC 315 to which the collected data can be sent.

[0277] The NF-A SI SC 315 can use the information received in the request from the NWDAF as matching rules to identify the type of data for which to collect, e.g. which NF-A SI (e.g. NF-A instance / SI 333, NF-A instance / SI 334) can provide the requested type of data for which UE, at which UE location.

[0278] At step 536, the NF-A SI SC function 335 can send a data collection request or subscription confirmation to the NWDAF SI SC function 315. This is to confirm that the NF-A SI SC 335 received the request for data collection.

[0279] In some embodiments, step 538 can be performed after step 534 and before step 536. In some other embodiments, step 538 can be performed after step 536.

[0280] The NF-A SI SC 335 can check the following conditions to avoid duplicate data collection:

[0281] a. If some other NF SI of the same NF SI set (in this embodiment, the NWDAF SI set) has already requested the data type(s) with the same data type(s) (same data type ID(s)) and the same or different data collection attributes. If some other NF SI has already requested the same data type ID(s), the NF-A SI SC 335 will update the existing data collection job within the NF SI set. If some other NF instance / SI of the same NWDAF SI set has requested the same data type(s), the collected data can be sent to the same storage function so that the collected data can be shared among the NF SI of the same NF SI set (in this embodiment, the NWDAF set 310).

[0282] b. If some other NF instance / SI of some other NF set (in this embodiment, the NWDAF set 310) has already requested the same data type(s), the collected data can be stored in the same or different storage function. If the collected data has already been sent to the same storage function, the NF-A SI SC 335 can update the existing data collection setting in the NF-A SI set so that no additional data collection request is sent to the NF-A instances / SIs 333 and 334 of the NF-A SI set 330.

[0283] If the collected data has already been sent to another storage function, the NF-A SI SC 335 can update the data collection job within the NF-A SI set 330 so that the collected data can be sent to one or more storage functions. Alternatively, in step 536, the NF-A SI SC 335 can send the address of the storage function currently used to store the same collected data type(s) to the NWDAF instance / SI 311. The NWDAF instance / SI 311 can access the notified storage function to obtain the required data. The NWDAF SI 311 can subscribe to the notified SF 350 for data notification service as performed in steps 526 and 528.

[0284] At step 540, depending on the function of the NF-A instance / SI 333 and 334, the NF-A SI SC 335 can send an NF data collection request or NF data collection modification to the NF-A instance / SI 333 and 334 that is able to provide the required data. For example, if the NF-A 330 is an SMF SI 18 managing IP PDU session type and the data type ID is IP PDU session data, the SMF SI SC will send a data collection request to the SMF SI 18.

[0285] If the requested data type(s) has not been collected yet, the NF-A SI SC 335 can send an NF data collection request to the NF-A SI(s) 333. This message can include one or more of the following information: data type ID(s), data collection attribute(s) per data type ID, address of the storing function (such as SF ID, SF IP address). If the NF-A SI SC function 335 is responsible for sending the collected data to the NWDAF instance / SI 311 or SF 350, the address of the SF 350 can be omitted.

[0286] If the requested data type(s) has been collected, then the NF-A SI SC 335 can send an NF data collection modification to the NF-A instance / SI(s) 333. This message can include the data type ID(s) and one or more new attributes of the data collection attributes per data type ID. If the collected data can be sent to another SF or additional SFs, this message can include the SF address(es).

[0287] At step 542, the NF-A instance / SI 333 can send an NF data collection response to the NF-A SI SC 335 to confirm the reception of the NF data collection request or modification of step 540.

[0288] At step 544, the NF-A instance / SI 333 collects data according to the data type ID(s) and data collection attributes received in step 540. For each collected data record, the NF-A instance / SI 333 can include a timestamp of the time when the data is collected, the ID of the NF-A SI set 330 and / or NF-A SI subset ID and / or one or more attributes described in the data collection attributes (e.g. UE ID, S-NSSAI, NSI-ID, application ID).

[0289] Based on the parameters provided in step 540, the NF-A instance(s) / SI(s) 333 can send a data transfer request to the SF or NF-A SISC 335 or NWDAF SISC 315. This message can carry the collected data to the SF or NF-A SISC 335 or NWDAF SISC 315 based on the parameters provided in step 540. The NF-A instance(s) / SI(s) 333 can send the collected data immediately or at some configured schedule time or time period when the network load can be low to avoid network congestion.

[0290] If the collected data is sent from the NF-A instance / SI 333 to the NF-A SISC 335, the NF-A SISC 335 can collect data from one or more NF-A instance(s) / SI(s) 333 and 334, send in one or more batches, or send to the SF 350 and / or NWDAF SISC 315 immediately after receiving the collected data from the NF-A instance(s) / SI(s) 333 / 334. The NF-A SISC 335 can send the collected data to the SF 350 and / or NWDAF SISC 315 at a schedule time or time period when the network load can be low to avoid congestion.

[0291] At step 546, the (data) SF 350 or NWDAF SISC 315 can send a data transfer response to the NF-A SISC 335 or NF-A instance / SI 333, depending on which entity has sent the data transfer request in step 544.

[0292] At step 548, the (data) SF 350 can send a data notification to the NWDAF SISC 315 if the NWDAF SISC 315 has subscribed to the data collection notification in step 526. This message can indicate whether one or more attributes of the data type(s) and data collection attributes, such as collection period, location (e.g., RAN address(s), RAN cell ID(s), registration area, S-NSSAI, DNN, internal group ID) have been received.

[0293] Reference Figure 5CAt step 550, in some embodiments, the NF-A instance(s) / SI 333 can store the collected data in the NF-A SI set data store function 332. The message NF data store request can contain one or more of the following information: the collected data record(s), and for each collected data record, the NF-A instance / SI 333 can include a timestamp of the collection data time, an ID (and / or address) of the NF-A SI set 330 and / or NF-A SI subset ID and / or an ID (and / or address) of the NF instance and / or an ID (and / or address) of the NF-A SI 333 and / or one or more of the attributes described in the data collection attributes (e.g., UE ID, S-NSSAI, NSI-ID, Application ID).

[0294] At step 552, the NF-A SI set SF 332 can send an NF data store response to the NF-A instance / SI 333 to acknowledge the received data and / or to acknowledge that the data was successfully stored. If there was an error with the data store, such as the memory is full, then the NF-A SI set data store 332 can send an error code indicating the cause.

[0295] At step 554, the NF-A instance / SI 333 can send a data availability notification to the NF-A SI SC 335 to inform the NF-A SI SC 335 that one or more data records have been stored in the NF-A SI set data store 332.

[0296] At step 556, the NF-A SI SC 335 can send an NF data retrieval request to the NF-A SI set data store 332. This message can be sent immediately after step 554, or at a time when the network load can be lower. This message can contain one or more of the following parameters: data type ID(s), time period to retrieve collected data records.

[0297] At step 558, the NF-A SI set data store 332 can send the requested data records to the NF-A SI SC 335.

[0298] At step 560, the NF-A set SI SC 335 can send the data records to the SF 350. Each data record can have a timestamp and one or more of the attributes of the data collection attributes.

[0299] At step 562, the SF 350 can send a data transfer response to the NF-A SI SC 335 to acknowledge the receipt of the data in step 560.

[0300] At step 564, if the NWDAF SISC 315 has subscribed to the data collection notification in step 526, the SF 350 can send a data notification to the NWDAF SISC 315. This message can indicate whether one or more attributes of the data type(s) and data collection attributes, such as collection period, location (e.g., RAN address(es), RAN cell ID(s), registration area, S-NSSAI, DNN, internal group ID) have been received.

[0301] As an alternative to step 560, the NF-A SISC 335 can send the data record(s) directly to the NWDAF SISC 315 that requested the data collection. Each data record can have a timestamp, and one or more attributes of the data collection attributes. This message is not shown in Figures 5A-5C

[0302] At step 566, the NF-A SISC 335 can send a data collection response or notification to the NWDAF SISC 315 to inform that the data to be collected has been sent to the SF 350. This notification can include one or more of the following information: data type ID(s) and corresponding information for each data type ID, such as the number of data records collected, the time period (start and end time) of the data collected, the location(s) of the data collected (e.g., RAN address(es) or RAN cell ID(s), geographic area ID(s)), one or more attributes of the data collection attributes.

[0303] At step 568, the NWDAF SISC 315 can send a data notification to the NWDAF instance / SI 311 to inform that the requested data for analytics is available. This message can contain the data type ID(s) and corresponding information for each data type ID, such as the number of data records collected, the time period (start and end time) of the data collected, the location(s) of the data collected (e.g., RAN address(es), or RAN cell ID(s), geographic area ID(s)), and / or one or more attributes of the data collection attributes for each data type ID.

[0304] ​At step 570, based on the notification received in step 568, the NWDAF instance / SIs 311 can retrieve collected data from one or more SF SI sets and / or SF Sis. The NWDAF instance / SIs 311 can send a data retrieval request to the SF SI set(s) and / or SF instance / SIs to get the collected data. This message can include one or more of the following information: one or more data type IDs and one or more of the data collection attributes such as collection time period(s), location(s), S-NSSAI, internal group ID, DNN, NF ID(s).

[0305] At step 572, the SFs 350, such as SF SI SCs and / or SF Sis, can send one or more data retrieval response messages carrying the requested data to the NWDAF SI 311.

[0306] The NWDAF instance / SIs 311 can store the received data in the NWDAF SI set data store 313.

[0307] At step 574, the NWDAF instance / SIs 311 perform the data analytics service received at step 514.

[0308] At step 576, the NWDAF instance / SIs 311 can send a data analytics response or data analytics notification to the NFs that sent the message at step 514.

[0309] It should be understood that: Figures 5A-5C The described embodiments include the following advantages:

[0310] a. Each NWDAF instance / SI (e.g., NWDAF instance / SIs 311 and 312) does not have to discover other NF SI sets or other NF Sis for data collection.

[0311] b. The NF SI sets and / or NF Sis are discovered by the NWDAF SI SC (e.g., NWDAF SI SC 315).

[0312] c. Each NF instance / SI does not need to know where to send the data to be reported.

[0313] d. The NF SI SC of each NF SI set is responsible for collecting data from the NF instances / Sis and forwarding the collected data to the data storage function.

[0314] Figure 6An example embodiment of a data sharing scheme 600 between an OAM system and NWDAFs is shown. In this embodiment, an OAM system 610 is used to perform various network management tasks, such as configuring NFs, setting user subscription data in a UDM and / or UDR, creating policies for users, PDU sessions, traffic routing in PCFs, monitoring network performance. The OAM system 610 can receive requests or subscriptions from NWDAFs (such as NWDAF SI 310 and / or NWDAF SI SC) for data to be analyzed. The OAM 610 can configure NFs, or request data collection from AFs and / or UEs. The collected data can be stored in a data storage function (e.g., data storage function 350). The OAM function 610 can inform the address of the storage function 350 so that the NWDAF SI SC or NWDAF SI 310 can access the data storage function 350 to retrieve data.

[0315] Figure 7A and 7B An embodiment signaling procedure 700 for message exchange between NFs (e.g., NF-A set 330), OAM (e.g., OAM 610), and NWDAFs (e.g., NWDAF SI set 310) for network data collection is shown. Among other advantages, Figure 7A and 7B An embodiment shows signaling support to the OAM 610 to indicate which storage function stores network data for data analysis.

[0316] When a NWDAF instance / SI (e.g., NWDAF instance / SI 311) or a NWDAF SI SC (e.g., NWDAF SI SC 315) of the NWDAF SI set 310 receives a request from a NF instance / SI (e.g., NF-A SI 333) or a NF SI SC of another NF set, the NWDAF SI SC 315 or the NWDAF instance / SI (e.g., NWDAF instance / SI 311 in this embodiment) can send a request or a subscription to the OAM 610 to get network data for analysis.

[0317] At step 710, if the NWDAF SI SC 315 is responsible for collecting data from the OAM 610, the NWDAF SI SC 315 can send a data request or a data subscription message to the OAM 610.

[0318] At step 712, if the NWDAF instance / SI 311 (or NWDAF instance / SI 312) is responsible for collecting data from the OAM 610, the NWDAF instance / SI 311 can send a data request or a data subscription message to the OAM 610.

[0319] In step 710 or 712, the data request or data subscription message can include data type ID(s) and data collection attributes. For each data request, the OAM 610 can later send a data request response to the NF that sent the data request when all the needed data is available. For example, the NWDAF instance / SI 311 can send a data request for UPF load information in a specific network area for a specific time period. After all the data is received from the NFs and / or UEs operating and / or matching the data collection attributes in the required network area and / or for the required time period, the OAM 610 can send a data request response message to the NF requesting the data. More details will be provided in other steps.

[0320] In step 710 or 712, the data subscription message can indicate which data type ID(s) the NWDAF SI SC or NWDAF instance(s) / SI wants to get immediately when the record(s) of the data type ID(s) are available, e.g., when the data record is received by the OAM function 610. For example, the NWDAF instance / SI 311 can want to receive data types indicating high load conditions in NFs such as RAN nodes, UPFs, SMFs, AMFs. When the OAM 610 receives the high load message, the OAM 610 can send a data notification message to the NWDAF instance / SI 311.

[0321] At step 714, if in step 710, the OAM 610 receives the message from the NWDAF SI SC 315, the OAM 610 can send a data request acknowledgement or data subscription acknowledgement to the NWDAF SI SC 315. The message is used to acknowledge the receipt of the message in step 710. If the requested data is available, the message can include an indication that the data is available and the address(es) (e.g., IP address, or FQDN or ID) of the data storage function(s) (e.g., storage function 350) where the NWDAF SI SC 315 can access to retrieve all or some of the data types. If the data is not available, and can be collected later and provided to the NWDAF SI SC 315 according to the data collection attributes, the OAM 610 can include the address(es) of the SF(s) (e.g., storage function 350) where the NWDAF SI SC 315 can retrieve all or some of the data types in the future.

[0322] The NWDAF SI SC 315 can forward the SF information received from the OAM 610 to the NWDAF SI 311 that has been selected to provide the data analytics service requested by some NF instance(s) / SI (e.g., NF-A instance / SI 333) or some NF SI SC of the other NF set.

[0323] At step 716, if the OAM 610 receives the message from the NWDAF instance / SI 311 in step 712, the OAM 610 can send a data request acknowledgement or a data subscription acknowledgement to the NWDAF instance / SI 311. The message is used to acknowledge the receipt of the message in step 712. If the requested data is available, the message can include an indication of the data type(s) available and the address(es) of the data storage function(s) (e.g., storage function 350) where the NWDAF instance / SI 311 can access to retrieve all or some of the data types. If the data is not available and can be collected later and provided to the NWDAF instance / SI 311 according to the data collection attributes, the OAM 610 can include the address(es) of the SF(s) (e.g., storage function 350) where the NWDAF instance / SI 311 can retrieve the data in the future.

[0324] Each SF SI set or SF SI subset or SF service set or SF instance or SF SI can store one or more data types. Therefore, the OAM 610 can need to inform the NWDAF SI SC 315 (or the NWDAF SI subset or the NWDAF instance(s) or the NWDAF service set(s) or the NWDAF SI(s) 311) which SF SI set(s) and / or which SF instance(s) / SI store which data type(s).

[0325] If the OAM 610 indicates that the requested data is already available in some SFs, steps 718 to 752 can be skipped. In step 754, the NWDAF instance / SI 311 can retrieve the data from the SF SI set(s) and / or the SF instance(s), the SF service set(s) and / or the SF SI(s) of the SF SI set(s) to perform the data analytics.

[0326] At step 718, if the OAM 610 indicated the SF SI set(s) and / or SF SI subset(s) and / or SF instance ID(s) and / or address(es) of SF SI ID(s) in step 714, the NWDAF SI SC 315 can send a data notification subscription or data request message to the SF SI set(s) or SF SI subset(s) or SF instance or SF service set or SF SI. This message can indicate which data type ID(s) the NWDAF SI SC 315 can want to receive a notification of when a data record is received by the SF 350.

[0327] At step 720, if the OAM 610 indicated the SF SI set(s) ID and / or SF SI subset(s) ID and / or SF instance ID and / or SF service set and / or address(es) of SF SI ID(s) in step 716, the NWDAF SI 311 can send a data notification subscription or data request message to the SF SI set(s) or SF SI subset(s) or SF SI. This message can indicate which data type ID(s) the NWDAF SI 311 can want to receive a notification of when a data record is received by the SF 350.

[0328] At step 722, the SF 350 (e.g., SF instance(s) of SF SI set(s) or SF SI SC(s) / SI(s)) can send a data notification subscription acknowledgement to the NWDAF SI SC 315 to acknowledge receipt of the message in step 718. Alternatively, if data becomes available, the SF 350 (e.g., SF instance(s) of SF SI set(s) or SF SI SC(s) / SI(s)) can send a data response to the NWDAF SI SC 315 to transmit the data requested in step 718.

[0329] At step 724, the SF 350 can send a data notification subscription acknowledgement to the NWDAF SI 311 to acknowledge receipt of the message of step 720. Alternatively, if data becomes available, the SF 350, e.g., SF SI of SF SI SC or SF SI set(s), can send a data response to the NWDAF instance / SI 311 to transmit the data requested in step 720.

[0330] If the requested data is to be collected from NFs (e.g., NF-A set 330), the OAM 610 can send a measurement request or data collection request to the NF set(s). This message is to request data collection for the data type ID(s) and data collection attributes that are requested by the NWDAF (e.g., NWDAF set 310).

[0331] At step 726, if the NF-A SISC 335 receives the request for data collection from the OAM function 610, the NF-A SISC 335 can forward the request of the OAM 610 to the NF-A instance(s) / SI(s) that are capable of providing the requested data (e.g., NF-A instance / SI 333, NF-A instance / SI 334).

[0332] At step 728, if the OAM function 610 sends the measurement request to the NF-A SI, such as NF-A SI 333, the NF-A SI 333 can receive the message.

[0333] In step 726 or 728, the OAM 610 can include the address(es) (e.g., IP address, SF ID, SF FQDN) of the SF SI set(s) and / or SF SI subset(s) and / or SF instance(s) and / or SF service set(s) and / or SF SI(s) and data type ID(s) that can be stored in each SF, such as SF SI set or SF SI subset or SF instance or SF SI. Each SF instance / SI or SF SI set can be used to store one or more data type IDs.

[0334] At step 730, the NF-A SISC 335 can send a measurement request acknowledgement to the OAM 610 to acknowledge the receipt of the message in step 726.

[0335] At step 732, the NF-A instance / SI 333 can send a measurement request acknowledgement to the OAM 610 to acknowledge the receipt of the message in step 728.

[0336] Reference Figure 7BAt step 734, the NF-A instance / SI 333 can perform the necessary measurements or collect the required event(s) in the data type(s) ID and data collection attributes. If the measurement request was sent to the NF-A instance / SI 333 by the NF-A SI SC 335 in step 726, the NF-A instance / SI 333 can send a measurement report to the NF-A SI SC 335. Alternatively, the NF-A instance / SI 333 can send a measurement report or event notification to the OAM 610 in step 728 upon receiving the request from the OAM 610.

[0337] At step 736, the OAM 610 can send a data transfer request that can carry the received record(s) of the data type to one or more SFs 350, such as SF SI set(s), SF SI subset(s), SF instance(s), SF SI(s).

[0338] At step 738, the SF 350, such as SF SI set(s), SF SI subset(s), SF instance(s), SF SI(s), can send a data transfer acknowledgement to the OAM function 610 to confirm that the data record has been received and stored in the SF 350.

[0339] At step 740, the OAM 610 can send a measurement report acknowledgement to the NF-A set 330, which is received by the NF-A SI SC 335 or the NF-A instance(s) / SI(s), such as the NF-A SI 333.

[0340] If the OAM 610 provides the address(es) of the SF 350(s) in steps 726 and / or 728, steps 730 to 738 can be skipped.

[0341] At step 742, the NF-A instance / SI 333 can send a measurement report to the NF-A SI SC 335, and the NF-A SI SC 335 can send a measurement report to the SF 350, such as SF set(s), SF subset(s), SF instance(s) / SI(s). Alternatively, the NF-A instance / SI 333 can send a measurement report directly to the SF 350.

[0342] At step 744, the SF 350 may send a measurement report confirmation to the NF-A instance 330, e.g., to the NF-A SI SC 335 if the NF-A SISC 335 sent the data record(s) to the SF 350. If the NF-A instance / SI 333 sent the data record(s) to the SF 350, the SF 350 may send a measurement report confirmation to the NF-A instance / SI 333.

[0343] At steps 746 and 748, if the OAM 610 receives the measurement report(s) in step 734, the OAM 610 may send a data notification to the NWDAF SI set(s) 310, the NWDAF SI subset(s), and / or the NWDAF instance(s) / SI(s) 311 / 312. The data notification message may include one or more of the following information: an SF SI set ID or address, an SF SI subset ID or address, an SF SI ID or address, data type ID(s), and one or more attributes of the data collection attributes for each data type ID.

[0344] The NWDAF SI SC 315 or the NWDAF instance / SI 311 may receive the data notification message.

[0345] For example, in step 746, if the NWDAF SI SC 315 sent a data request or data subscription message in step 710, the NWDAF SI SC 315 may receive a data notification from the OAM function 610. The NWDAF SI SC 315 may send the data notification to the NWDAF instance / SI 311, which is the function that will perform the data analysis.

[0346] At step 748 , if the NWDAF instance / SI 311 sent a data request or data subscription message in step 710 , the NWDAF instance / SI 311 may receive a data notification from the OAM function 610 .

[0347] At step 750, if the NWDAF SI SC 315 subscribes to the data notification service of the SF 350, for example in step 718, the SF 350 may send a data notification message to the NWDAF SI SC 315. The NWDAF SI SC 315 may send the data notification message to the NWDAF instance / SI 311, which is the NWDAF instance / SI 311 selected to provide the data analysis service.

[0348] At step 752 , if the NWDAF SI 311 subscribes to the data notification service of the SF 350 , for example, in step 718 , the SF 350 may send a data notification message to the NWDAF SI 311 .

[0349] At step 754, the NWDAF instance / SI 311 may send a data retrieval request to the SF 350 to retrieve the data. The message may include one or more of the following information: SF SI set ID (or FQDN, or IP address), SF SI subset ID (or SQDN, IP address), SF instance ID (or FQDN, or IP address), SF SI ID (or FQDN, or IP address), data type ID(s), and one or more attributes of the data collection attributes for each data type ID.

[0350] At step 756 , the SF 350 may send the data record with the data type(s) of the requested attributes provided in step 754 .

[0351] At step 758, the NWDAF instance / SI 311 may store the received data record in the NWDAF SI aggregate data storage function 313. The NWDAF instance / SI 311 may perform data analysis and provide the analysis results to the requesting NF. The analysis results may be statistics and / or predictions and / or recommendations of network operation parameters, such as some UE parameters (such as mobility pattern parameters, communication pattern parameters), NF load statistics at a specific time period of the day, day of the week, or expected QoS parameters at a specific time period of the day, day of the week, and at a specific network location (such as (multiple) RAN cell IDs).

[0352] exist Figures 4AA-4ACIn the methods described in 4BA to 4BC, 4CA and 4CB, 5A to 5C, 7A and 7B, the data collection request or data collection subscription can be implemented by using event exposure or NF status services of network functions such as AMF, SMF, PCF and NRF. For example, the NWDAF can subscribe to the event exposure Namf_EventExposure_Subscribe service of the AMF as described in 3GPP TS 23.502 clause 5.2.2.3, the UE location Namf_Location service of the AMF as described in 3GPP TS 23.502 clause 5.2.2.5, the event exposure Nudm_EventExposure service function of the UDM function as described in 3GPP TS 23.502 clause 5.2.3.5, the user subscription update Nudm_SDM_Subscribe service of the UDM as described in 3GPP TS 23.502 clause 5.2.3.3.4, the event exposure Npcf_EventExposure service of the PCF as described in 3GPP TS 23.502 clause 5.2.5.7, the event exposure Nsmf_EventExposure service of the SMF. By using the event exposure service of the NF, the data type ID can be represented by an event ID, and the data collection attribute of the data type ID can be represented by an event filter corresponding to the event ID.

[0353] One of the event types that the SMF can provide is referred to as “PDU Session Event”. The PDU Session Event can include the following events: when a PDU Session is established or released, when the uplink of a PDU Session is activated or deactivated, when the UE enters the CM-IDLE state and the RRC idle state, or when the UE enters the CM-CONNECTED state and the RRC-Connected state, or when the CM-CONNECTED and RRC-Inactive state. When one of these events occurs, the SMF can send one or more PDU Session contexts to the NFs that subscribe to the PDU Session Event, such as: UE ID, UE location (e.g., RAN ID or cell ID), DNN, S-NSSAI, traffic volume, UPF load, measured QoS parameters of QoS flows of the PDU Session in uplink and downlink (such as MFBR, MFBR, measured UE-AMBR, average bit rate of QoS flows, measured average UE bit rate), duration of QoS flows with downlink and / or uplink data activity in one or more periods before the PDU Session event occurs, average packet delay or packet error rate.

[0354] Figure 8A and 8BAn example signaling procedure 800 is shown that stores and shares analytics data produced by NWDAFs (e.g., the set of NWDAFs 310), including a solution that allows multiple NFs to use the same output analytics data of a NWDAF. Among other advantages, the embodiment of Figure 8 provides and uses a common storage function to store data analytics results produced by NWDAFs. This is to avoid multiple NFs requesting the same analytics data, and to avoid processing overload in NWDAFs, and to reduce processing delay.

[0355] A UE mobility pattern describes the location(s) of a UE over a certain time period. For example, one UE mobility pattern can include a list of cell ID(s) or (R)AN node ID(s) from 9:00:00 AM to 12:00:00 PM where the UE can be served. An AMF and / or an SMF and / or a PCF can use a UE mobility pattern to determine multiple parameters. For example, an AMF and a PCF can use a UE mobility pattern to optimize the registration area, the tracking area of the UE. An SMF can use a UE mobility pattern to select a UPF during a PDU session establishment procedure, a handover procedure, a service request procedure, and other procedures that require selection or reselection of a UPF to route the traffic of the UE in uplink and downlink.

[0356] There are other parameters, such as a UE communication pattern, that can describe, for example, how often a UE enters a connected state and accesses a certain data network. An AMF can use a UE communication pattern to optimize a DRX (discontinuous reception) cycle. An SMF can use a UE communication pattern to determine when to release a user plane connection of a PDU session if no uplink or downlink data is detected.

[0357] A NWDAF can collect data from UEs, network functions, OAM, and AFs to analyze UE behavior and to derive network operation parameters, such as UE mobility patterns and UE communication patterns. If multiple NFs request the same parameters from a NWDAF, the NWDAF can need to analyze a large amount of collected data multiple times. These repeated requests can cause processing overload in the NWDAF and can cause long time delay for the signaling procedures that require the results of the NWDAF analysis. For example, during a PDU session establishment, an SMF can request a UE mobility pattern. If the response from the NWDAF is too long, the SMF can consider the NWDAF failed to send the UE mobility pattern. The SMF can select a UPF without the input of the NWDAF. The selected UPF can not be the best, and the UE has to wait a longer time for the PDU session establishment.

[0358] In this embodiment, a solution to solve the above problem is introduced. The UDM function can request or subscribe the NWDAF for analytics results, including but not limited to, such as UE related parameters (such as UE mobility pattern, UE communication pattern), QoS parameters (such as UE aggregate bit rate), total traffic of some services (such as background data transfer) and / or application related parameters or any related analytics results that can be used by other NFs and / or AFs and / or OAM and / or UE. The NWDAF sends analytics results, such as statistics and / or predictions and / or recommendations of the requested parameters, to the UDM. The UDM stores the analytics results sent from the NWDAF and / or can further derive parameters based on the analytics results. Whenever a network entity (such as AMF, PCF and SMF, OAM, UE) requests UE related parameters or any other parameters, the UDM can send the analytics results or derived parameters to the network entity. In this way, the NFs or other network entities can not need to request analytics data from the NWDAF to avoid long time delay and overload in the NWDAF.

[0359] Similar to the concept described for the UDM function, the concept can be applied to the PCF. The PCF can request or subscribe the NWDAF for QoS related statistics, routing statistics. The PCF can provide derived parameters and subsequently provide to other NFs.

[0360] At step 810, the UDM SI set (e.g., UDM SI set 801) or UDM instance / SI (e.g., UDM instance / SI 802 or 803) or UDM SI SC (e.g., UDM SI SC 805) of the UDM SI subset can be configured by OAM to handle communication with the NWDAF 310 in order to obtain data analytics related to network operation parameters such as UE mobility patterns, UE communication patterns, UE aggregate maximum bit rate, application related parameters. The UDM instance / SI 802 or UDM SI SC 805 can discover the NWDAF SI set(s) 310 and / or the NWDAF instance(s) / SI(s) 311 that are capable of providing the required analytics services, for example, by storing in the UDM SI SC 805 or in the UDM instance / SI 802 or in the UDM SI set data storage function 804 or in the OAM configuration of any logical or physical entity of the UDM set 801. Alternatively, the UDM SI SC 805 or UDM instance / SI 802 can discover the NWDAF SI set(s) 310 and / or the NWDAF instance(s) / SI(s) 311 by requesting or subscribing to the NRF service. The NRF can provide the UDM SI SC 805 or UDM instance / SI 802 with the NF profile(s) of the NWDAF set(s) 310 or the NWDAF SI subset(s) or the NWDA instance(s) or the NWDAF service set(s) or the NWDAF SI(s) 311. The NRF can also provide the UDM SI SC 805 or UDM instance / SI 802 with the profile(s) of the NWDAF instance(s) / SI(s) 311 or the NWDAF SI subset(s) or the NWDAF SI set(s) 310 where the service(s) of the NWDAF are indicated as such as UE related analytics services, NF related analytics services, traffic routing assistance analytics services. The UDM SI SC 805 or UDM instance / SI 802 selects the NWDAF SI set (e.g., NWDAF SI set 310) or the NWDAF SI subset or the NWDAF instance / SI (e.g., NWDAF instance / SI 311) to provide the analytics data.

[0361] At step 812, if the UDM SI SC 805 is configured to communicate with the NWDAF to obtain analysis data, the UDMSI SC 805 may select an NWDAF SI set 310 or an NWDAF subset or one of the NWDAF SIs 311 from the NWDAF information provided by the NRF. The UDM SI SC 805 may send a data analysis request or a data analysis subscription message to the address of the selected NWDAF instance / SI 311 or to the address of the selected NWDAF SI set 310 or to the address of the selected NWDAF SI subset, which may be received by the NWDAF SI SC 315 of the NWDAF SI set 310 or NWDAF SI subset.

[0362] At step 814, if the UDM instance / SI 802 is configured or selected by the UDM SI SC 805 to communicate with the NWDAF to obtain analysis results, the UDM instance / SI 802 may select an NWDAF SI set (e.g., NWDAF SI set 310) from one of the NWDAF sets, or select one of the NWDAF instances / SIs (e.g., NWDAF instance / SI 311) from the NWDAF information provided by the NRF. The UDM instance / SI 802 may send a data analysis request or data analysis subscription message, or the address of the selected NWDAF instance / SI 311, NWDAF SI set 310, NWDAF SI subset, or NWDAF service set. If the message is sent to the NWDAF SI set 310 or NWDAF SI subset, the NWDAF SI SC 315 of the NWDAF SI set 310, NWDAF SI subset, or NWDAF service set may receive the message.

[0363] If the UDM SI SC 805 or the UDM instance / SI 802 discovers or selects the NWDAF instance / SI 311, the following step 816 may be skipped.

[0364] At step 816 , if NWDAF SI SC 315 receives a message from UDM SI SC 805 or UDM instance / SI 802 , NWDAF SI SC 805 may select one of the NWDAF SIs (eg, NWDAF SI 311 ) to process the request from UDM SI SC 805 or UDM instance / SI 8022 .

[0365] At step 818, if the message in step 812 or 814 has been sent to the NWDAF SISC 315, the NWDAF SISC 315 forwards the request received in step 812 or step 814 to the selected NWDAF instance / SI 311. If the message in step 812 or 814 has been sent to the NWDAF instance / SI 311, step 818 is skipped.

[0366] At steps 820 and 822, the NWDAF instance / SI 311 can retrieve the collected data from the NWDAF set storage function 313. The steps of collecting data have been described in earlier embodiments. The NWDAF SI set data storage 3133 can be an internal storage function of the NWDAF SI set 310, or can be the UDSF instance / SI, or can be the UDSF SI set, or any storage function.

[0367] At steps 824 and 826, alternatively, the NWDAF instance / SI 311 can retrieve the collected data from another storage function (e.g., storage function 350) outside the NWDAF set. The steps of collecting data have been described in earlier embodiments. The external storage function can be a UDR storage function, or a UDSF storage function.

[0368] At step 828, after obtaining the data, the NWDAF instance / SI 311 performs data analysis to produce analysis data, such as statistics or predictions or recommendations of the parameters requested in step 812 or step 814.

[0369] At step 830, if the UDM SISC 805 requests the analysis data in step 812, the NWDAF instance / SI 311 can send the analysis data to the UDM SISC 805.

[0370] At step 832, if the UDM instance / SI 802 requests the analysis data in step 814, the NWDAF instance / SI 311 can send the analysis data to the UDM instance / SI 802 by using a data analysis response or data analysis notification message.

[0371] At step 834, the UDM SISC 805 can store the received analysis data to a storage function of the UDM SI set 801 (e.g., UDM SI set storage function 804).

[0372] At step 836, the UDM SI 802 can store the received analysis data to a storage function of the UDM SI set 801 (e.g., UDM SI set storage function 804).

[0373] At step 838, the UDM SI SC 805 can store the received analytics data to a storage function (e.g., storage function 350) outside of the UDM set 801.

[0374] At step 840, the UDM instance / SI 802 can store the received analytics data to a storage function (e.g., storage function 350) outside of the UDM SI set 801.

[0375] At step 838 or step 840, the storage function outside of the UDM set 801 (e.g., storage function 350) can be a UDR function, such as a UDR SI set or a UDR SI subset or a UDR instance or a UDR SI.

[0376] At step 842, the NF-A instance / SI 333 can send a request or subscription message to the UDM 801 to request one or more network operation parameters. The UDM SI SC function 805 can receive the request from the NF-A 330. The UDM SI SC 805 can select a UDM instance / SI 802 and send the request received from the NF-A instance / SI 333 to the selected UDM instance / SI 802.

[0377] At step 844, which is an alternative to step 842, the NF-A instance / SI 333 can send a request or subscription message to the UDM instance / SI 802 to request one or more network operation parameters.

[0378] At step 846, the network operation parameters can include analytics results obtained from the NWDAF 310. At step 834 or 836 or 838 or 840, the UDM instance / SI 802 can retrieve the analytics results from the storage function 804. The UDM instance / SI 802 can send the network operation parameters, including analytics data received from the NWDAF 310, or parameters derived by the UDM 801 based on analytics data received from the NWDAF 310 and data received from other network entities, such as AF, UE, OAM, to the NF-A instance / SI 333 by using a data response service or a data notification service of the NWDAF 310.

[0379] For example, during a UE registration procedure, the AMF can request the UDM 801 to provide access and mobile subscription data. The UDM 801 can send to the AMF one or more types of analytics data obtained from the NWDAF 310, including but not limited to UE behavior information and / or mobility patterns and / or communication patterns. The AMF can use the analytics data to optimize the UE’s mobility management parameters, such as the registration area, the tracking area. During the UE registration procedure, the AMF can transfer the analytics data received from the UDM 801, such as UE behavior information and / or mobility patterns and / or communication patterns, to the PCF, while during the PDU session establishment procedure to the SMF. The AMF can implicitly or explicitly subscribe to the UDM 801 to receive updates of the analytics information, such that whenever the NWDAF 310 sends an update of the analytics information, the UDM 801 will send to the AMF an update of the analytics information; the AMF can send the updates of the analytics data to the PCF and the SMF.

[0380] In another example, during a PDU session establishment procedure, the SMF can request the UDM 801 to provide session management subscription data. The UDM 801 can send to the SMF the session management subscription data and analytics data related to the UE, such as UE behavior information and / or mobility patterns and / or communication patterns. The SMF can use this analytics data to select a UPF, to set a deactivation timer to deactivate the user plane, so that the UPF monitors uplink and downlink data activity. During the PDU session establishment procedure, the SMF can transfer the analytics data received from the UDM 801, such as UE behavior information and / or mobility patterns and / or communication patterns, to the PCF. The SMF can implicitly or explicitly subscribe to the UDM 801 to receive updates of the analytics information, such that whenever the NWDAF 310 sends an update of the analytics information, the UDM 801 will send to the SMF an update of the analytics information; the AMF can then send the updates of the analytics data to the PCF and the SMF.

[0381] In another example, during a PDU session establishment procedure, the AMF can forward to the SMF one or more analytics data received from the UDM 801, e.g., UE behavior information and / or mobility patterns and / or communication patterns. The SMF can use this analytics data to select a UPF, to set a deactivation timer to deactivate the user plane, so that the UPF monitors uplink and downlink data activity.

[0382] At step 850, the NF-A instance / SI 333 can store in the storage function 335 or the NF-A SI set data storage function 332 of the NF-A instance / SI 333 the network operation parameters received from the UDM instance / SI 802, including analytics data or data derived from analytics data.

[0383] Figure 9 An example method 900 of unified data transmission and storage in a communication network is shown.

[0384] The method includes, at operation 910, a plurality of network data analytics function (NWDAF) instances / SIs requesting data to be acquired by a plurality of network function SIs in a plurality of network function SI sets, each network function SI set being associated with a network function SI SC.

[0385] The method further includes, at operation 920, receiving unified data at the plurality of NWDAF SIs, the data being unified for transmission and storage at least according to data type identification and data collection attributes.

[0386] The method further includes, at operation 930, performing at least one network data analytics operation based on the unified data at the plurality of NWDAF SIs.

[0387] The above introduced system and method can be used to optimize data collection and storage in a mobile network, such that the plurality of NWDAF SIs and / or the plurality of network function SI sets can analyze network operation data and produce analytics data.

[0388] A method of transmitting analytics data produced by a NWDAF to other network functions is introduced below.

[0389] Figure 11 An example flow 1100 of some signaling messages as part of a UE registration procedure is shown. In order to access and use the resources of a mobile network, a UE needs to perform a registration procedure with the mobile network. 3GPP TS 23.502 clause 4.2.2.2.2 describes one possible signaling flow to support UE registration. To simplify the discussion, only NF names, such as AMF, SMF, PCF, UDM, NWDAF, are used in Figure 11 and in other Figure 12 , 13 , 14. However, the NF names can be replaced by NF instances / SIs, or NF SI SCs, or any entity designed to provide a set of services of the NF. For example, the NF AMF can be replaced by an AMF instance / SI or an AMF SI SC. Accordingly, in this implementation, a service instance (or simply instance) of a set of network functions AMF or a set of SI coordinators of a set of network functions AMF can perform the signaling as described in Figure 11 , 12 , 13, 14.

[0390] In Figure 11In the middle, during the UE registration procedure, the AMF 1101 can obtain the UE subscription data in step 1110. The messages in step 1110 can be implemented by using UDM services, such as Nudm_UECM_Registration, Nudm_SDM_Get, Nudm_SDM_Subscribe in one or more of steps 14a, 14b, 14c described in clause 4.2.2.2.2 of 3GPP TS 23.502. In this step, the AMF 1101 uses Nudm_SDM_Get to retrieve the access and mobility subscription data, SMF selection subscription data, and UE context in the SMF data. This requires the UDM 1102 can retrieve this information from the UDR by Nudr_DM_Query. After receiving the successful response, the AMF 1101 subscribes to be notified when the requested data is modified using Nudm_SDM_Subscribe, the UDM can subscribe to the UDR by Nudr_DM_Subscribe. If GPSI is available in the UE subscription data, the GPSI is provided to the AMF 1101 in the access and mobility subscription data from the UDM 1102. The UDM 1102 can provide an indication to indicate the subscription data is updated for the UE to update the network slice. Note that the UDR is not drawn in the middle. Figure 11

[0391] At step 1115, the UDM 1102 sends the data required for the UE registration to the AMF 1101.

[0392] At step 1120, the AMF 1101 can request the PCF 1103 to provide network policies, such as access and mobility (AM) policies, to support the UE communication. This step 1120 can be similar to step 16 of clause 4.2.2.2.2 of 3GPP TS 23.502, where Figure 11 The messages in step 1120 can be implemented by some signaling messages for the AM policy association establishment during the registration. More details are described in clause 4.16.1 of 3GPP TS 23.502, where the AMF 1101 can use Npcf_AMPolicyControl_Create request to obtain the access and mobility policies for the UE. Note that this Npcf_AMPolicyControl_Create response message in 3GPP TS 23.502 version 15.4.0 published in December 2018 does not provide any analytics data produced by the NWDAF 1104.

[0393] At step 1125, the PCF 1103 can interact to request or subscribe the NWDAF 1104 to obtain the UE mobility analytics information.​

[0394] At step 1130, the NWDAF 1104 can provide the UE mobility analytics information to the PCF 1103. Using the UE mobility analytics information, the PCF 1103 can derive some policy parameters for the UE, such as the service area restriction for the UE.

[0395] At step 1135, the PCF 1103 can provide the AM policy to the AMF 1101.

[0396] At step 1140, the AMF 1101 can request or subscribe the NWDAF 1104 to obtain the UE mobility analytics information.

[0397] At step 1145, the NWDAF 1104 can provide the UE mobility analytics information to the AMF 1101.

[0398] Figure 11 The above steps can be part of the UE registration procedure. The problem with this procedure is that the PCF 1103 and the AMF 1101 need to obtain the UE mobility analytics information from the NWDAF 1104 in steps 1125 and 1130, and steps 1140 and 1145, respectively. These messages cause additional delay to the UE registration procedure, as the NWDAF 1104 needs to process a large number of requests from the AMF 1101 and the PCF 1103. This problem can be avoided by using the present solution (shown in Figure 12 ).

[0399] Figure 12 An example flow 1200 showing some signaling messages that can be performed during the UE registration procedure as described in 3GPP TS 23.502 clause 4.2.2.2.2 is shown. At step 1210, the UDM 1102 can request or subscribe the NWDAF 1104 to obtain some type of analytics data, such as UE-related analytics data, application-related analytics data, QoS-related analytics data.

[0400] At step 1215, the NWDAF 1104 sends the requested analytics data to the UDM 1102.

[0401] The UDM 1102 can store the analytics data in the UDR. This signaling message is not drawn in Figure 12 .

[0402] Note that steps 1210 and 1215 can be performed at any time before the UE requests the UE registration procedure. Therefore, the implementation of steps 1210 and 1215 can not cause any delay to the UE registration procedure.

[0403] At step 1220, the AMF 1101 can request the UDM 1102 to provide the UE subscription data and / or analytics data. The AMF 1101 can also implicitly or explicitly subscribe the UDM 1102 to provide notifications of receiving updates of the UE subscription data and analytics data.

[0404] At step 1225, the UDM 1102 can provide the AMF 1101 with the UE subscription data and / or related analytics data that can be used to support the access and mobility management of the UE.

[0405] At step 1230, the AMF 1101 can request and / or subscribe the AM policy from the PCF 1103. In this message, the AMF 1101 can provide some or all of the UE subscription data received from the UDM in step 1225, some AM connection parameters, and some or all of the analytics data to the PCF 1103.

[0406] At step 1235, the PCF 1103 provides the AM policy to the AMF 1101 in a response or notification message. The AM policy parameters can take into account the analytics data received from the AMF 1101.

[0407] In Figure 12 In this case, there is no communication between the AMF 1101 and the NWDAF 1104, and there is no communication between the PCF 1103 and the NWDAF 1104. Thus, there is no additional delay to the UE registration procedure, while the AMF 1101 and the PCF 1103 can still receive analytics data produced by the NWDAF 1104.

[0408] Figure 13 An example flow 1300 is shown that illustrates some of the signaling messages that can be part of a PDU session establishment procedure in order to establish a new PDU session for a UE. The PDU session establishment can be implemented as described in, for example, 3GPP TS 23.502, version 15.4.0, clause 4.3.2.2.1, published in December 2018.

[0409] At step 1310, the AMF 1101 can send a PDU session creation request to the SMF 1301. This step can be similar to step 3 of 3GPP TS 23.502, clause 4.3.2.2.1.

[0410] At step 1315, the SMF 1301 can send a UE subscription data request to the UDM 1102.

[0411] At step 1320, the UDM 1102 can provide the UE subscription data to the SMF 1301. The UDM 1102 can obtain the UE subscription data stored in the UDR. The signaling between the UDM 1102 and the UDR is not shown in Figure 13 .

[0412] Steps 1315 and 1320 can be similar to steps 4 of 3GPP TS. 23.502 clause 4.3.2.2.1. Note that steps 4 of 3GPP TS. 23.502 clause 4.3.2.2.1, published in December 2018, version 15.4.0, does not provide analytics data to the SMF.

[0413] At step 1325, the SMF 1301 can request the PCF 1103 to provide session management (SM) policies.

[0414] At step 1330, the PCF 1103 can request or subscribe to the services of the NWDAF 1104 to provide analytics data related to the UE and the application to optimize the SM policies.

[0415] At step 1335, the NWDAF 1104 provides analytics data to the PCF 1103. The PCF 1103 can use the analytics data and other information to create SM policies for the UE.

[0416] At step 1340, the PCF 1103 can provide the SM policies to the SMF 1301.

[0417] Steps 1325 and 1340 can be implemented by using SM policy association establishment or SM policy association modification initiated by the SMF 1301 as described in step 7b of 3GPP TS 23.502 clause 4.3.2.2.1. Note that the procedure in step 7b of 3GPP TS 23.502 clause 4.3.2.2.1, published in December 2018, version 15.4.0, does not include steps 1330 and 1335, which means that the PCF in step 7b of 3GPP TS 23.502 clause 4.3.2.2.1 does not use analytics data provided by the NWDAF (e.g., NWDAF 1104) to create SM policies. Figure 13

[0418] At step 1345, the SMF 1301 can request or subscribe to the NWDAF 1104 to obtain UE mobility analytics data. The UE mobility analytics data can be used to select a UPF.

[0419] At step 1350, the NWDAF 1104 can provide the UE mobility analytics data to the SMF 1301.

[0420] ​exist Figure 13 In the example, PCF 1103 and SMF 1301 may obtain analysis data from NWDAF 1104 in steps 1330 and 1335 and steps 1345 and 1350, respectively. These steps result in additional delays in the PDU session establishment process. Figure 14 In, an alternative method 1400 is provided to overcome this problem.

[0421] exist Figure 14 In step 1410, AMF 1101 may send a PDU session creation request to SMF. This step is similar to Figure 13 Step 1310.

[0422] At step 1420, SMF 1301 may request UDM 1102 to provide UDM subscription data and analysis data. Figure 12 In the method described in steps 1210 and 1215 , UDM 1102 already has some type of analysis data.

[0423] As step 1430, UDM 1102 may provide UE subscription data and analysis data to SMF 1301. The analysis data may include relevant data of SMF 1301 to optimize service routing, system parameters of UE's PDU session. UDM 1102 may obtain UE subscription data and analysis data stored in UDR. Signaling between UDM 1102 and UDR is not performed in Figure 14 Shown in.

[0424] At step 1440, SMF 1301 may request SM policy from PCF 1103. This message is similar to Figure 13 The difference is that the SMF 1301 may send a portion of the entire analysis data received from the UDM 1102 in step 1430 to the PCF 1103, so that the PCF 1103 can use the relevant analysis data to create an SM policy.

[0425] In step 1450 , the PCF provides the SM policy to the SMF 1301 .

[0426] Figure 14 The method in avoids signaling messages between the SMF 1301 and the NWDAF 1104 and between the PCF 1103 and the NWDAF 1104. Therefore, the SMF 1301 and the PCF 1103 can obtain analysis data from the UDM 1102, which analysis data has been generated by the NWDAF 1104, but without any additional signaling delay.

[0427] The following description Figure 12 and14 more detailed implementations of the signaling messages illustrated in the figures.

[0428] In one embodiment, the UDM 1102 can use the services of the NWDAF 1104 to obtain analytics data. For example, the UDM 1102 can use Nnwdaf_EventsSubscription_Subscribe / Nnwdaf_EventsSubscription_Unsubscribe to subscribe or unsubscribe to one or more notifications of one or more types of analytics data. The UDM 1102 can use the Nnwdaf_Analyticslnfo_Request service of the NWDAF 1104 to request one or more types of analytics data.

[0429] The analytics data can be one or more of UE-related analytics data, application-related analytics data, QoS-related analytics data, policy-related analytics data, NF analytics data, network slice analytics data, security analytics data, or any analytics data or any combination.

[0430] The UE-related analytics data can include analytics information of UE behavior parameters. The analytics information or analytics data of a parameter can be a statistics or a prediction or a recommendation of the parameter. The UE behavior parameters can include, but are not limited to, the parameters described in 3GPP TS 23.501 and TS 23.502, such as “expected UE activity behavior”, i.e., the expected pattern of UE changes between CM-CONNECTED and CM-IDLE state; “expected HO behavior”, i.e., the expected interval between inter-RAN handovers; “expected UE mobility”, i.e., whether the UE is expected to be stationary or mobile; “expected UE mobility trajectory”, which can indicate the positions of the UE in a sequential list, e.g., geographical positions, or (R)AN node IDs, or cell ID(s).

[0431] Some other UE behavior parameters can be described in 3GPP TS 23.682. For example, a "stationary indication" identifies whether the UE is stationary or mobile; a "periodic time" is the interval time for periodic communication, e.g., every hour; a "scheduled communication time" is the time and date in a week when the UE is available for communication; a "battery indication" identifies the power consumption critical state of the UE: if the UE is powered by a non-rechargeable / non-replaceable battery, by a rechargeable / replaceable battery, or not by a battery; a "traffic profile" identifies the type of data transmission: single-packet transmission (uplink and / or downlink), double-packet transmission (uplink with subsequent downlink or downlink with subsequent uplink), multi-packet transmission; a "scheduled communication type" indicates whether the scheduled communication type is downlink only or uplink only or bidirectional. For example, the analytics information for "periodic time" can be statistics for "periodic time" where the UE can perform data transmission in uplink every day at 3:00-3:10 PM with 95% confidence. The analytics information for "expected UE mobility trajectory" can be a (ordered or not) list of cell IDs: cell 100, cell 103, cell 105.

[0432] Application-related analytics data can contain analytics results related to a specific application. For example, a video clip of a social network website can have a video length of 3 minutes with an average bit rate of 2 Mbit / s. Another example is that the average data volume for a background data transmission service of certain vehicle services (V2X) is 100 megabits in uplink, and 90% of the UEs can send 90 to 110 megabits of background data to the V2X application server. Another example is an IoT service where an IoT UE can send an average of 10 messages per month to an application server on uplink, and the average length of each message can be 100 bytes. Another example is the maximum data burst volume parameter (MDBV) of a QoS flow of some applications, which can require low packet delay during the transmission from the traffic source to the UE. This type of QoS flow can be a latency-critical GBR QoS flow. The MDBV can represent the maximum data volume that a network such as a RAN of a fourth generation (4G) or 5G mobile system needs to serve in a time period of the 5G-AN packet delay budget (PDB), i.e., the 5G-AN part of the PDB. The NWDAF 1104 can collect the data volume of the QoS flow in different sizes of time windows to analyze the typical MDBV of the traffic of the application that needs to be transmitted in different time windows.

[0433] The NWDAF 1104 can collect information related to QoS parameters during network operation. QoS parameters are described in 3GPP TS 23.502 clause 5.7 QoS Model. QoS parameters in uplink or downlink or both can include: flow bit rate, such as Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR); aggregate bit rate, such as per session aggregate maximum bit rate (session-AMBR), per UE aggregate maximum bit rate (UE-AMBR); maximum packet loss rate; resource type (GBR, delay-critical GBR, or non-GBR), priority level; packet delay budget; packet error rate; average window (only applicable for GBR and delay-critical GBR resource types); maximum data burst volume (only applicable for delay-critical GBR resource type). QoS related analytics data can contain analytics QoS parameters related to a single UE or a group of UEs or an application. For example, for a particular UE 20, the weekly data volume consumption can be less than 1 gigabyte. In another example, the data consumption of UEs of a group of UEs can be between 3 to 4 gigabytes per month with 95% confidence. The average UE Aggregate Maximum Bit Rate (UE-AMBR) for certain video applications is 4-5 megabits per second with a Guaranteed Flow Bit Rate (GFBR) of 4-5 megabits per second to achieve a quality of experience (QoE) level 4 in the range of 1-5. In another example, for a group of V2X UEs with different driving automation levels, such as remote driving or platooning, a GFBR of 15-20 megabits per second meets the requirement of driving automation level 1, and a GFBR of 10-15 megabits per second meets the requirement of driving automation level 2. The QoS related analytics data for an application can be the maximum data burst volume (MDBV) parameter, which has an average of 200 bytes per data packet, a minimum of 50 bytes, and a maximum of 300 bytes.

[0434] When the NWDAF 1104 sends the analysis results related to the UE and the application or other analysis results to the UDM, the NWDAF 1104 also sends the associated information, such as the time information and the location information and the confidence and the network parameters, such as the DNN, the S-NSSAI, the application ID, the DNAI, the AF-Service ID, the internal group ID. The time information can be described by a start time and an end time. The location information can be described by one or more geographical locations (such as two-dimensional or three-dimensional locations), one or more geographical areas, one or more (R)AN nodes or cell IDs, one or more registration areas, one or more tracking areas, one or more service areas, for example, of a network function (such as the AMF 1101 or the SMF 1301 or the UPF). For example, a UE behavior parameter can be associated with one or more time periods and / or one or more locations. For example, from Monday to Friday, from 9:00 to 11:59 in the morning, at the (R)AN node (or cell ID) numbered 100, the “expected UE active behavior” is that the UE is more likely to be in the CM-CONNECTED state, the “expected HO behavior” is “0”, which means a high probability of being stationary (or no handover). In another time period, from 12:00 to 5:00 in the afternoon, the “expected UE mobility trajectory” is that the UE can move within the coverage area of three cells, from the cell numbered 100 to another cell numbered 120, and then to another cell numbered 130.

[0435] After receiving the analytics data, the UDM 1102 can store the analytics data in the UDR by using the services of the UDR. For example, the UDM 1102 can insert a new analytics data record in the UDR by using the Nudr_DM_Create service. The UDM 1102 can provide one or more of the parameter data set identifier, the data key(s), the data subset identifier(s), the data sub-key(s) in the Nudr_DM_Create request message, as described in 3GPP Technical Specification (TS) 23.502, clause 5.2.12.2. The data set identifier can be “Analytical Data” for the analytics data. The data key can be a SUPI (Subscription Permanent Identifier) representing a UE identifier or an internal group ID representing a group of UEs or an application ID representing an application. The data sub-key can be one or more of “UE analytics data”, “application analytics data”, “policy analytics data”, “QoS analytics data”, “security analytics data”, or any other type of analytics data.

[0436] The analytics data can be organized in the UDR in some alternative ways. For example, in the Data Set Identifier “Access and Mobile Subscription Data” or “Session Management Subscription Data” described in 3GPP TS 23.502, version 15.4.0, clause 5.2.3.3, released in December 2018, one or more data sub-keys indicating analytics data type(s) such as one or more of “UE analytics data”, “Application analytics data”, “Policy analytics data”, “QoS analytics data”, “Security analytics data”, or any other type of analytics data can be included.

[0437] When the NWDAF 1104 sends an update of analytics data for some UEs, the UDM can use the Nudr_DM_Update service of the UDR to update the existing data records in the UDR that contain analytics data. For example, the UDM 1102 can send an Nudr_DM_Update Request message to the UDR to update an existing analytics data record. The Nudr_DM_Update Request message can include one or more of the parameters Data Set Identifier, Data Key(s), Data Subset Identifier(s), Data Sub-key(s).

[0438] The UDM 1102 can obtain analytics data stored in the UDR by using the Nudr_DM_Query service of the UDR. The UDM 1102 can need to obtain analytics data stored in the UDR when another NF such as the AMF 1101, the SMF 1301, or the PCF 1103 requests analytics data from the UDM 1102, or the analytics data is part of or a subset of other data sets such as “Access and Mobile Subscription Data” or “Session Management Subscription Data”, or the analytics data can be sent together with other data such as “Access and Mobile Subscription Data” or “Session Management Subscription Data”. The UDM 1102 can send an Nudr_DM_Query message to the UDR, which can include one or more of the parameters Data Set Identifier, Data Key(s), Data Subset Identifier(s), Data Sub-key(s).

[0439] The PCF 1103 can obtain analytics data stored in the UDR by using the Nudr_DM_Query service of the UDR.

[0440] AMF 1101 can obtain profiling data from UDM 1102 using its Nudm_SDM_Subscribe service. AMF 1101, SMF 1301, PCF 1103, or any other network function consumer can subscribe to updates to the UE's subscriber data indicated by the "Subscription Data Type" input. UDM 1102 should check whether the requesting consumer is authorized to subscribe to the requested updates. AMF 1101, SMF 1301, PCF 1103, or any other network function consumer can subscribe to updates to the profiling data indicated by the "Profiling Data Type" input. One or more types of profiling data can be part of the subscription data type.

[0441] The input parameters of the Nudm_SDM_Subscribe message may include one or more of the following parameters: subscription data type(s), key(s) for each subscription data type, data subkey(s). The UDM 1102 will send the requested information to the consumer function (such as AMF 1101, SMF 1301, and PCF 1103).

[0442] For analysis data, the subscription data type may be named "Analysis Data", the key for each subscription data type may be a SUPI (Subscription Permanent Identifier), and the data subkey may be one or more of "UE Analysis Data", "Application Analysis Data", "Policy Analysis Data", "QoS Analysis Data", "Security Analysis Data", or any other type of analysis data. The data subkeys may be organized in some alternative ways. For example, the existing "Access and Mobility Subscription Data" or "Session Management Subscription Data" described in clause 5.2.3.3 of 3GPP Technical Specification (TS) 23.502 version 15.4.0, released in December 2018, may include a data subkey that may indicate "UE Analysis Data", "Application Analysis Data", "Policy Analysis Data", "QoS Analysis Data", or any other type of analysis data.

[0443] like Figure 12 As shown in step 1220 of , the AMF 1101 may use Nudm_SDM_Subscribe to obtain analysis data from the UDM. For example, in 3GPP TS 23.502 version 15.4.0, clause 4.2.2.2.2, at step 14c, the AMF may use Nudm_SDM_Subscribe to obtain analysis data from the UDM. The AMF may use analysis data, such as UE mobility analysis data, to optimize some operating parameters of the UE, such as registration area and tracking area.

[0444] The AMF 1101, or any similar SMF 1301, PCF 1103 NF, can obtain analytics data from the UDM 1102 by using another service of the UDM 1102 defined to handle analytics data. Such service can be referred to as Nudm_AnalyticalData_Request and Nudm_AnalyticalData_Response to request and receive analytics data, or as Nudm_AnalyticalData_Subscribe, Nudm_AnalyticalData_Unsubscribe, and Nudm_AnalyticalData_Notify to subscribe, unsubscribe, and be notified of analytics data.

[0445] As described in step 1230 of Figure 12 The AMF 1101 can send one or more analytics data to the PCF, such as UE mobility analytics data received from, for example, the UDM 1101 or the NWDAF 1104 or an AF, as described in step 1230 of Figure 12 The message in step 1230 of Figure 12 The message in step 1230 of

[0446] The AMF 1101 can send one or more analytics data to the SMF 1301, said analytics data received from, for example, the UDM 1102 or the NWDAF 1104 or an AF. For example, at step 3 of 3GPP TS 23.502 clause 4.3.2.2.1, the AMF can send an Nsmf_PDUSession_CreateSMContext request message to the SMF. This message can include one or more types of analytics data to the SMF, such as UE mobility information, analytics data of UE communication patterns.

[0447] The AMF 1101 can use analytics data, such as UE mobility analytics data, to select the SMF 1301. For example, during the PDU session establishment procedure, at step 2 of clause 4.3.2.2.1 of TS 23.502, the AMF can have information such as one or more SMF SI sets, SMF SI subsets, NF profiles of SMF SI that the AMF can select based on the fact that the UE can move within a certain location and / or based on the fact that the UE can have communication within a certain time period according to the UE communication pattern analytics information, to serve the UE.

[0448] The SMF 1301 can obtain analytics data from the UDM 1102 as described in steps 1420 and 1430 of TS 23.502. Figure 14 For example, during the PDU session establishment procedure, at step 4 of clause 4.3.2.2.1 of TS 23.502, the SMF performs a registration / subscription retrieval / subscription with the UDM by using the Nudm_SDM_Subscribe service of the UDM. The SMF 1301 can request “session management subscription data” which can include “analytics data” as part of the “session management subscription data”. Alternatively, if analytics data is a separate data type, the SMF 1301 can request one or more types of “analytics data”.

[0449] The AMF 1101, SMF 1301, or PCF 1103 can request the NWDAF 1104 to obtain analytics data by using similar methods as previously described for the UDM 1102. However, if the AMF 1101 or SMF 1301 or PCF 1103 communicates with the NWDAF 1104 to obtain analytics data, this signaling can cause additional delay in the connection establishment of the UE, such as in the UE registration procedure, PDU session establishment procedure, service request procedure, and handover procedure described in 3GPP TS 23.502 version 15.4.0 published in December 2018.

[0450] In this method, a common storage function, such as the UDR, is used to hold analytics data produced by the NWDAF 1104. Other network functions, such as the AMF 1101, SMF 1301, and PCF 1103, can obtain some relevant analytics data from the UDM 1102 or UDR in conjunction with other data stored in the UDR 1102. This is a unified approach to avoid additional delay in the signaling procedures in the communication system.

[0451] Figure 10An architecture 1000 of a computing system that can be used to implement the devices and methods disclosed herein is shown in an example embodiment. With reference to Figure 9 The described operations can be performed by one or more functional modules of a computing device, which can be one or more server computing devices including at least a microprocessor 1005, a network communication interface 1010, and a memory 1015 that operate in conjunction to perform any of the above-described operations. The memory 1015 can include instructions executable within the processor 1005 for performing operations as described above.

[0452] From the description of the foregoing embodiments, it can be seen that the present application can be implemented only by using hardware or by using software and a necessary general hardware platform. Based on such an understanding, the technical solutions of the present application can be implemented in the form of a software product. The software product can be stored in a non-volatile or non-temporary storage medium, which can be a compact disc read-only memory (CD-ROM), a USB flash disk, or a removable hard disk. The software product includes a plurality of instructions that enable a computer device (a personal computer, a server, or a network device) to perform the methods provided in the embodiments of the present application. For example, such execution can correspond to simulating the logical operations described herein. According to the embodiments of the present application, the software product can additionally or alternatively include a plurality of instructions that enable a computer device to perform operations for configuring or programming a digital logic device.

[0453] Although the present application has been described with reference to particular features and embodiments, it is evident that various modifications and combinations can be made thereto without departing from the application. Accordingly, the description and drawings are to be regarded simply as a description of the present application as defined by the appended claims, and are contemplated to cover any and all modifications, variations, combinations or equivalents that fall within the scope of the present application.

Claims

1. A data collection method, characterized by, The method comprises: a data storage function receiving, from a network data analytics function NWDAF, a subscription for a data item via a first interface between the data storage function and the NWDAF, wherein the subscription comprises at least one of: a data type to be collected and one or more attributes of the data to be collected; the data storage function subscribing, from a set of network functions NFs, to the data item according to the received subscription via a second interface between the data storage function and the set of NFs; the data storage function receiving the data item from the set of NFs via the second interface; and the data storage function sending the data item to the NWDAF in response to the subscription by the NWDAF.

2. The method of claim 1, wherein, The subscription further comprises information indicating NFs that can provide the data.

3. The method of claim 2, wherein, The information indicating NFs that can provide the data comprises at least one of: one or more NF set identities and one or more NF SI IDs.

4. The method according to any one of claims 1-3, characterized in that, If the one or more attributes of the data to be collected are different from a previous subscription, the data storage function sends a data subscription modification or update to the set of NFs in order to modify or update the previous subscription.

5. The method according to any one of claims 1-3, characterized in that, There is no interface configured for the subscription by the NWDAF between the NWDAF and the set of network functions.

6. The method according to any one of claims 1-3, characterized in that, The method further comprises: based on the received subscription from the NWDAF, the data storage function determines whether the data item of the subscription is associated with at least one of a different data type or a different attribute compared to a previous data type or attribute associated with a data item of a previous subscription; if so, the data storage function subscribes to a data item from the set of NFs based on the determined difference associated with at least one of a data type or an attribute.

7. The method according to any one of claims 1-3, characterized in that, The method further comprises: the data storage function receiving, from the NWDAF via the first interface between the data storage function and the NWDAF, a second subscription for a second data item, wherein the second data item is associated with at least one of a same data type or a same attribute as a data type or an attribute of the data item of the subscription; and without a new subscription for the second data item from the set of NFs, the data storage function sends the data item to the NWDAF in response to the second subscription by the NWDAF.

8. The method of any one of claims 1-3, wherein, The method further comprises: the data storage function receiving, from a coordinator via the first interface between the data storage function and the NWDAF, a second subscription for a second data item, wherein the second data item is the same as the data item of the subscription; and without a new subscription for the second data item from the set of NFs, the data storage function sends the data item to the coordinator in response to the second subscription.

9. The method of claim 1 or 2, wherein, The data item associated with at least one of the data type and the attribute comprises information indicating at least one of an event that has occurred and an event that will occur.

10. The method of claim 1 or 2, wherein, The method further comprises: The coordinator collects a request from at least one NWDAF service instance in a set of NWDAFs associated with the NWDAF, wherein the request is for obtaining a data item included in the request; The coordinator subscribes to the data item from the set of NFs according to the request; and The coordinator receives the data item from a data storage function that is capable of communicating with the NWDAF and the set of NFs.

11. The method of claim 1 or 2, wherein, The type of data to be collected is represented by an event ID.

12. The method of claim 1 or 2, wherein, One or more attributes of the data to be collected are represented by filtering information of an event corresponding to the data to be collected.

13. A data collection method characterized by, The method comprises: A first network function receives a subscription message from a network data analytics function, NWDAF, the subscription message being for subscribing to first data, the first network function being for storing data and coordinating provision of data to the NWDAF, wherein the subscription message indicates at least one of: a type of the first data and one or more attributes of the first data; The first network function determines whether the first data has already been collected; The first network function obtains the first data; and The first network function sends the first data to the NWDAF in response to the subscription message from the NWDAF.

14. The method of claim 13, wherein, The first network function determines that the first data has not been collected, the first network function obtaining the first data comprises: The first network function subscribes to the first data from a set of network functions, NFs; The first network function receives the first data from the set of NFs.

15. The method according to claim 13 or 14, characterized in that, The subscription message further comprises information indicating NFs capable of providing the first data.

16. The method of claim 15, wherein, The information indicating NFs capable of providing the first data comprises at least one of: one or more NF set identities and one or more network function service instance, NF SI, IDs.

17. The method of claim 13 or 14, wherein, The type of the first data is represented by an event ID.

18. The method of claim 13 or 14, wherein, One or more attributes of the first data are represented by filtering information of an event corresponding to the first data.

19. The method of claim 13 or 14, wherein, The first network function determines that the first data has not been collected and that the first data has been subscribed to in a previous subscription, if one or more attributes of the first data are different from one or more attributes of data of the previous subscription, the method further comprises: The first network function sends a data subscription modification or update to the set of NFs.

20. A method of communication, comprising: The method comprises: A network data analytics function, NWDAF, sends a subscription message to a first network function, the subscription message being for subscribing to first data, the first network function being for storing the first data and coordinating provision of the first data to the NWDAF, wherein the subscription message indicates at least one of: a type of the first data and one or more attributes of the first data; The NWDAF receives the first data, there being an interface between the first network function and a network function, NF, capable of providing the first data.

21. The method of claim 20, wherein, The subscription message further comprises information indicating NFs capable of providing the first data.

22. The method of claim 21, wherein, The information of the NFs that can provide the first data comprises at least one of the following: one or more NF set identifiers and one or more network function service instance, NF SI, IDs.

23. The method of claim 20 or 21, wherein, The type of the first data is indicated by an event ID.

24. The method of claim 20 or 21, wherein, One or more attributes of the first data are indicated by filtering information of the event corresponding to the first data.

25. The method of claim 20 or 21, wherein, The method further comprises: The NWDAF receives a data analytics request, and the NWDAF determines to subscribe to the first data according to the data analytics request.

26. The method of claim 20 or 21, wherein, The first data is collected by the first network function from the NFs that can provide the first data.

27. An apparatus comprising a processor coupled with a memory that stores instructions, wherein the processor is configured to: When the processor executes the instructions, the processor performs the method of any one of claims 1-12, or performs the method of any one of claims 13-19, or performs the method of any one of claims 20-26.

28. A communication system, characterized by The first communication device is configured to perform the method of any one of claims 1-12, or perform the method of any one of claims 13-19, and the second communication device is configured to perform the method of any one of claims 20-26.

29. The communication system of claim 28, wherein, Further comprising a set of NFs configured to perform one or more of the following: collect data and provide the data in response to a subscription to the data.

30. A computer-readable storage medium, characterized in that, The computer readable storage medium stores instructions that, when executed by a processor, cause the processor to perform the method of any one of claims 1-26.

Images