Patent Description:
In a communication system, various components need information to perform their tasks. An example is a component performing network analytics, e.g. analysis of the load of the communication system or parts of the communication system which may need information from components such as radio access network components about data traffic, number of sessions etc. Since collection of data generates signalling traffic in the communication system, efficient approaches for collecting data in a communication system, such as a cellular mobile communication system like a <NUM> communication system, are desirable.

<NPL>) discloses processes to coordinate data collection in a mobile network.

<NPL>) discloses processes to mitigate the load in 5GC for data collection.

According to a first aspect of the present invention, a communication system component of a communication system is provided according to claim <NUM>.

According to a second aspect of the present invention, a method for collecting data in a communication system according to claim <NUM> is provided.

According to a further aspect of the present invention a computer program and a computer readable medium according to claim <NUM> is provided.

Additional features for advantageous embodiments of the present invention are provided in the dependent claims.

The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and aspects of this disclosure in which the invention may be practiced.

In the following, various examples will be described in more detail.

<FIG> shows a radio communication system <NUM>.

The radio communication system <NUM> includes a mobile radio terminal device <NUM> such as a UE (user equipment), a nano equipment (NE), and the like. The mobile radio terminal device <NUM>, also referred to as subscriber terminal, forms the terminal side while the other components of the radio communication system <NUM> described in the following are part of the mobile radio communication network side, i.e. part of a mobile radio communication network (e.g. a Public Land Mobile communication network PLMN).

Furthermore, the radio communication system <NUM> includes a radio access network <NUM>, which may include a plurality of radio access network nodes, i.e. base stations configured to provide radio access in accordance with a <NUM> (Fifth Generation) radio access technology (<NUM> New Radio). It should be noted that the radio communication system <NUM> may also be configured in accordance with LTE (Long Term Evolution) or another radio communication standard (e.g. Wi-Fi) but <NUM> is herein used as an example. Each radio access network node may provide a radio communication with the mobile radio terminal device <NUM> over an air interface. It should be noted that the radio access network <NUM> may include any number of radio access network nodes.

The radio communication system <NUM> further includes a core network <NUM> including an Access and Mobility Management Function (AMF) <NUM> connected to the RAN <NUM>, a Unified Data Management (UDM) <NUM> and a Network Slice Selection Function (NSSF) <NUM>. Here and in the following examples, the UDM may further consist of the actual UE's subscription database, which is known as, for example, the UDR (Unified Data Repository). The core network <NUM> further includes an AUSF (Authentication Server Function) <NUM> and a PCF (Policy Control Function) <NUM>.

The core network <NUM> may have multiple network slices <NUM>, <NUM> and for each network slice <NUM>, <NUM>, the operator may create multiple network slice instances (NSIs) <NUM>, <NUM>. For example, the core network <NUM> includes a first core network slice <NUM> with three core network slice instances (CNIs) <NUM> for providing Enhanced Mobile Broadband (eMBB) and a second core network slice <NUM> with three core network slice instances (CNIs) <NUM> for providing Vehicle-to-Everything (V2X).

Typically, when a network slice is deployed, network functions (NFs) are instantiated, or (if already instantiated) referenced to form a network slice instance (NSI) and network functions that belong to a network slice instance are configured with a network slice instance identification.

Specifically, in the shown example, each instance <NUM> of the first core network slice <NUM> includes a first Session Management Function (SMF) <NUM> and a first User Plane Function (UPF) <NUM> and each instance <NUM> of the second core network slice <NUM> includes a second Session Management Function (SMF) <NUM> and a second User Plane Function (UPF) <NUM>.

The core network <NUM> may further include an NRF (Network Repository Function) <NUM>, which provides network function/network function service registration, network function/network function service discovery. The NRF may have an interface to any network function in the mobile radio communication network side, e.g. have an interface to the AMF <NUM>, the SMFs <NUM>, <NUM>. For simplicity, only the interface between the NRF <NUM> and the AMF <NUM> is depicted.

The radio communication system <NUM> may further include an OAM (Operation, Administration and Maintenance) function (or entity) <NUM>, e.g. implemented by one or more OAM servers which is connected to the RAN <NUM> and the core network <NUM> (connections are not shown for simplicity).

Further, the radio communication system <NUM> may include a NWDAF (Network Data and Analytics Function) <NUM>.

The NWDAF <NUM> is responsible for providing network analysis information upon request from network functions or communication system components (such as AMF, SMF etc.). For example, a network function may request specific analysis information on the load level of a particular network slice. Alternatively, the network function can use the subscribe service to ensure that it is notified by the NWDAF if the load level of a network slice changes or reaches a specific threshold.

To be able to provide analysis results, the <NUM> system architecture allows the NWDAF <NUM> to collect data from any NF. The NWDAF belongs to the same PLMN where the network function that notifies the data is located, i.e. the interactions between the NWDAF and the other NFs are currently only considered in the case of the same PLMN (i.e. roaming is currently not considered in 3GPP (<NUM>rd generation partnership project of release-<NUM> specification).

Any NF may request network analytics information from the NWDAF <NUM>.

<FIG> illustrates an interface <NUM> for an NWDAF <NUM> to acquire data from a network function <NUM>.

<FIG> illustrates an interface <NUM> for a network function <NUM> to acquire data analytics information (i.e. analysis result information) from an NWDAF <NUM>.

<FIG> illustrates an approach for data collection in a communication network.

A plurality of NWDAF instances <NUM>, grouped to NWDAF sets <NUM>, get data from a data collection coordination function (DCCF) <NUM>. If the DCCF <NUM> does not have data that one of the NWDAFs <NUM> requests it gets the data from a respective network function instance <NUM> (of network function groups <NUM>). The DCCF <NUM> can thus be seen to work as a proxy for the NWDAFs <NUM>.

In the following, alternatives to the approach of <FIG> are described that do not require a DCCF including logic to acquire data from data sources (such as data producing components like network functions or RAN components).

<FIG> illustrates an approach for data collection in a communication network according to an embodiment.

The communication network includes a DCS <NUM> (Data Collection Function/Service) which stores all NWAF collected data, i.e. data collected by NWAFs (Network Analytics Function) <NUM> and/or statistical and/or analytical information i.e. derived statistical and/or analytical information based on collected data by NWAFs (Network Analytics Functions) <NUM>.

An NWAF is similar to an NWDAF <NUM>, however, an NWAF is not required to maintain collected data.

The DCS <NUM> provides collected data and/or analytical information on request to one or more network functions <NUM> (e.g. an NWDAF <NUM>), one or more RANs <NUM> or an OAM <NUM> or an UE <NUM>.

The DCS <NUM> authenticates and authorizes components <NUM>, <NUM>, <NUM> before letting them access the stored data (like a gateway function).

An NWAF <NUM> can keep collected data temporarily (e.g. as temporary data) if needed. When an NWAF <NUM> has obtained (i.e. collected) data, e.g. from a data producer such as an NF <NUM>, a component of a RAN <NUM> or an OAM <NUM>, the NWAF <NUM> provides the collected data to the DCS <NUM> along with a data profile e.g. indicating one or more of the following for the collected data:.

Similarly, the NWAF <NUM> provides the analytic and/or statistical information to the DCS <NUM> along with a data profile e.g. indicating one or more of the following for the analytic information:.

<FIG> shows a message flow diagram <NUM> illustrating a method for collecting data.

The message flow takes place between a network function <NUM>, e.g. corresponding to one of the network functions <NUM> or UE <NUM>, a first NWAF (NWAF#<NUM>) <NUM> and a second NWAF (NWAF#<NUM>) <NUM>, e.g. corresponding to two of the NWAFs <NUM>, and a DCS <NUM>, e.g. corresponding to the DCS <NUM>.

In <NUM>, NWAF#<NUM> determines that it needs to collect data, e.g. for a request by a network function NFx for analytics which requires the data from a specific NF <NUM>. Before contacting the NF <NUM>, the NWAF#<NUM> checks with the DCS <NUM> whether the data is available in the DCS <NUM>.

In this example, it is assumed that the required data is not available in the DCS <NUM>. Therefore, in <NUM>, NWAF#<NUM> determines that is needs to collect the data from the specific NF <NUM>.

In <NUM> and <NUM>, NWAF#<NUM> gets the required data from the specific NF <NUM>.

In <NUM>, NWAF#<NUM> performs the data analytics.

Additionally, NWAF#<NUM> sends the data collected from NF <NUM> to the DCS <NUM> by means of a data store request in <NUM>. In addition, NWAF#<NUM> may also send the analytics information along with collected data.

In addition to the collected data, NWAF#<NUM> also provides a data profile for the collected data e.g. including a data type, a timestamp, a validity, a location (e.g. for which the data is valid or to which it pertains), producer NF <NUM> details, etc..

Upon reception of the collected data the DCS <NUM> stores the collected data and may create a future reference ID for the data (e.g. for any future data update). It provides this ID to NWAF#<NUM> with an acknowledgement message in <NUM>.

In <NUM>, NWAF#<NUM> determines that it needs specific data (assumed to be data of the NF <NUM>). Similarly to NWAF#<NUM> in <NUM> NWAF#<NUM> requests the data (e.g. indicating a data type) from the DCS <NUM> in <NUM>. The DCS <NUM> determines which data has been requested (e.g. based on data type). If the requested data is available in the DCS <NUM> (e.g. if the requested data is included in the data collected by NWAF#<NUM> from the NF <NUM>), the DCS <NUM> sends the data to NWAF#<NUM> in <NUM>. Before sending the data to the NWAF#<NUM>, the DCS <NUM> may perform an authorization procedure for NWAF#<NUM> (i.e. check access rights to the data of NWAF#<NUM>). Depending on the success of the authorization (e.g. based on rights of NWAF#<NUM>) the DCS <NUM> either sends the data to NWAF#<NUM> or rejects the request. If NWAF#<NUM> requests data which is not available in the DCS <NUM> and DCS <NUM> thus determines that the data is not available, the DCS <NUM> sends a "Data not available" notification in response.

In <NUM>, depending on the response by the DCS <NUM>, NWAF#<NUM> either decides to acquire the required data (or at least additional data in case the DCS <NUM> has provided data which was not sufficient) from the NF <NUM> or performs analytics.

Assuming, in this example, that NWAF#<NUM> decides to get the data, NWAF triggers data acquisition from the NF <NUM>.

In <NUM> and <NUM>, NWAF#<NUM> acquires the data from the NF <NUM> (e.g. by a data event request/response pair).

After the collecting of the acquired data in <NUM> (e.g. bringing it in a certain form, supplementing it with data profile information), NWAF#<NUM> updates the DCS <NUM> with the acquired data (e.g. for use by another NWAF). For example, NWAF#<NUM> uses the data reference ID received in <NUM> for the update in <NUM>. If the DCS <NUM> did not provide a reference ID in <NUM>, NWAF#<NUM> provides the acquired data as new data set to the DCS <NUM>. The DCS <NUM> acknowledges the update in <NUM>.

According to an embodiment, it may also be possible that NWAF#<NUM> can communicate directly with NWAF#<NUM> for collecting required data or analytical information.

While in the above examples, the DCS <NUM>, <NUM> serves for storing data for NWAFs for performing analytics, it may, as illustrated in <FIG>, act as a central data collection for the whole communication system, i.e. for multiple communication network components of various types as well as communication terminals.

<FIG> shows a communication system arrangement <NUM> according to an embodiment.

The communication system arrangement <NUM> includes a DCS <NUM> which is connected to one or more NWAFs <NUM> (e.g. similarly to <FIG>), one or more network functions <NUM>, one or more UEs <NUM>, one or more radio access networks <NUM> and an OAM <NUM>.

For example, the DCS <NUM> stores data from RAN nodes of the RANs <NUM> (e.g. RANs for both 3GPP and Non-3GPP access), the NFs <NUM> (e.g. AMF, SMF, UPF, MME, SGW (Serving Gateway), LCS(Location Services), the UEs <NUM>, the NWAFs <NUM> and the OAM <NUM> (including system e.g. <NUM> and <NUM>). For example, AMF stores the serving UE <NUM> location information in the DCS <NUM> or SMF stores information about active and inactive PDU Sessions or RAN stores radio condition information. Any NF <NUM> or RAN <NUM> or UE <NUM> can get the these stored information from DCS. However, DCS only forwards any information based on policy conditions and successful authentication. For example, NWAF <NUM> can get directly the UE location information from DCS <NUM> instead of getting from the AMF.

<FIG> shows a flow diagram <NUM> illustrating a procedure for data storage and data retrieval by a consumer <NUM>, e.g. corresponding to one of the elements <NUM> to <NUM>), in/from a DCS <NUM> (e.g. corresponding to DCS <NUM>).

For storing data, the consumer <NUM> may, in <NUM>, send a data store request including data to be stored and data profile information (such as a data type, a timestamp, validity or location information) to the DCS <NUM>. The DCS <NUM> stores the data and acknowledges in <NUM> providing a data storage reference.

For updating data, the consumer <NUM> may, in <NUM>, send a data update request including update data for updating data stored in the DCS. The data update request includes a data storage reference to identify the data to be updated. The consumer <NUM> may further include data profile information into the data update request.

The DCS <NUM> updates the data and acknowledges in <NUM>.

For data retrieval from the DCS <NUM> by a consumer <NUM> requesting data, the DCS <NUM> may decide based on the result of an authorization and policy conditions i.e. whether to provide (e.g. share or update) data to the requesting consumer <NUM> or not.

For this, DCS <NUM> may maintain specific authenticated keys and security mechanism to share the data and may maintain policies and conditions specifying to which elements (e.g. devices or NFs) data may be shared.

An authorized consumer <NUM> may, in <NUM>, subscribe for a specific data notification (e.g. to a data update, for a specific interest in specific data, etc.) from the DCS <NUM>. Based on subscription conditions, the DCS <NUM> provides, when it determines in <NUM> that respective subscription conditions are satisfied, a data notification to each subscribed consumer <NUM> in <NUM>.

In summary, according to various embodiments, a communication system component of a communication system is provided as illustrated in <FIG>.

<FIG> shows a communication system component <NUM> of a communication system according to an embodiment.

The communication system component <NUM> includes a data retrieval interface <NUM> configured to request data from a data storage component of the communication system.

Further, the communication system component <NUM> includes a data acquisition interface <NUM> configured to acquire the data from one or more other components of the communication system if the data is not available for the communication system component in the data storage component.

The communication system component further includes and a data storage interface <NUM> configured to provide the acquired data to the data storage component for storing the acquired data in the data storage component.

According to various embodiments, in other words, a central storage is provided in a communication system which stores data for components of the communication system. A component of the communication system in need of specific data checks whether it can acquire the data from the central storage and if it cannot have the data from the central storage it gathers the data by other means (e.g. an entity producing the data) and stores the data in the central storage for later use by other components. Thus, it can be achieved that the other components do not need to gather the data themselves but can retrieve it from the central storage. In other words, data is gathered only once. Signalling load in the communication system may thus be reduced.

The communication system component <NUM> for example carries out a method as illustrated in <FIG>.

<FIG> shows a flow diagram <NUM> illustrating a method for collecting data in a communication system.

In <NUM>, a communication system component requests data from a data storage component of the communication system.

In <NUM>, if the data is not available for the communication system component in the data storage component, the communication system component acquires the data from one or more other components of the communication system.

In <NUM>, the communication system component providing the acquired data to the data storage component for storing the acquired data in the data storage component.

Claim 1:
A communication system component of a communication system (<NUM>), comprising:
a data retrieval interface configured to request data from a data storage component (<NUM>) of the communication system (<NUM>);
a data acquisition interface configured to acquire the requested data from one or more other components of the communication system (<NUM>) if the requested data is not available for the communication system component in the data storage component (<NUM>); and
a data storage interface configured to provide the acquired data to the data storage component (<NUM>) for storing the acquired data in the data storage component (<NUM>);
wherein the communication system (<NUM>) comprises one or more communication terminals (<NUM>) and a communication network serving the one or more communication terminals, wherein the communication system component is a component of the communication network;
wherein the communication network comprises a radio access network (<NUM>) and a core network (<NUM>) and wherein the communication system component is a component of the radio access network or the core network;
wherein the communication system component is further configured to perform an analysis of an operation of the communication system (<NUM>) and to provide analysis results to one or more further components of the communication system;
wherein the one or more other components of the communication system (<NUM>) comprise one or more core network functions and/or one or more radio access network components; and
wherein the data requested by the data retrieval interface comprises collected data and/or statistical and/or analytical data.