hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.1 General
| LMR users homed in the IWF shall have the ability to enable, apply, or disable a functional alias in the MC system for the use in communication with MC service users.
The functional alias feature is not a requirement in 3GPP TS 22.179 [3] and is therefore an optional feature for systems that support 3GPP TS 22.179 [3].
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2 IWF information flows for functional alias management
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.1 IWF functional alias information query request
| Table 10.14.2.1-1 describes the information flow of the functional alias information query request from the IWF to the MC service server.
Table 10.14.2.1-1: IWF functional alias information query request
Information element
Status
Description
MC service ID
M
The identity of the requesting MC service user.
MC service ID
O
The identity of the MC service user to be queried.
Functional alias
O
The functional alias to be queried.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.2 IWF functional alias information query response
| Table 10.14.2.2-1 describes the information flow of the functional alias information query response from the MC service server to the user homed in the IWF.
Table 10.14.2.2-1: IWF functional alias information query response.
Information element
Status
Description
MC service ID
M
The identity of the MC service user that performed the query.
MC service ID
O
The identity of the MC service user that was queried.
Functional alias
O
The functional alias that was queried.
Query result
M
The functional alias or MC service ID information retrieved from the functional alias management server, i.e. the list of activated functional alias identities of the MC service user or the associated MC service IDs and status which correspond to the queried functional alias.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.3 IWF functional alias activation request
| Table 10.14.2.3-1 describes the information flow of the functional alias activation request from the IWF to the MC service server.
Table 10.14.2.3-1: IWF functional alias activation request
Information element
Status
Description
MC service ID
M
The identity of the requesting MC service user.
Functional alias list
M
A list of one or more functional aliases which the originator intends to activate.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.4 IWF functional alias activation response
| Table 10.14.2.4-1 describes the information flow of the functional alias activation response from the MC service server to the IWF.
Table 10.14.2.4-1: IWF functional alias activation response
Information element
Status
Description
MC service ID
M
The identity of the MC service user that originated the functional alias activation request.
Functional alias list
M
A list of one or more functional aliases which the originating party intended to activate.
Activation status per functional alias
M
Indicates the activation result for each functional alias in the list (activated, rejected, can be taken over).
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.5 IWF functional alias de-activation request
| Table 10.14.2.5-1 describes the information flow functional alias de-activation request from the IWF to the MC service server.
Table 10.14.2.5-1: IWF functional alias de-activation request
Information element
Status
Description
MC service ID
M
The identity of the requesting MC service user.
Functional alias list
M
A list of one or more functional aliases which the requesting MC service user intends to de-activate.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.6 IWF functional alias de-activation response
| Table 10.14.2.6-1 describes the information flow of the functional alias de-activation response from the MC service server to the user homed in the IWF.
Table 10.14.2.6-1: IWF functional alias de-activation response
Information element
Status
Description
MC service ID
M
The identity of the MC service user that originated the functional alias de-activation request.
Functional alias list
M
A list of one or more functional aliases which the originating party intends to de-activate.
De-activation status per functional alias
M
Indicates the de-activation result for every functional alias in the list.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.7 IWF functional alias status notification
| Table 10.14.2.7-1 describes the information flow of the functional alias notification from the MC service server to the IWF.
Table 10.14.2.7-1: IWF functional alias status notification
Information element
Status
Description
MC service ID
M
The identity of the MC service user that originated the functional alias activation, de-activation or take over request.
Functional alias list
M
A list of one or more functional aliases.
Operational status
M
Activation, de-activation or take over status per functional alias.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.8 IWF Functional alias take over request
| Table 10.14.2.8-1 describes the information flow of the functional alias take over request from the IWF to the MC service server.
Table 10.14.2.8-1: IWF functional alias take over request
Information element
Status
Description
MC service ID
M
The identity of the requesting MC service user.
Functional alias
M
A functional alias which the requester intends to take over.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.9 IWF Functional alias take over response
| Table 10.14.2.9-1 describes the information flow of the functional alias take over response from the MC service server to the IWF.
Table 10.14.2.9-1: IWF functional alias take over response
Information element
Status
Description
MC service ID
M
The identity of the requesting MC service user.
Functional alias
M
A functional alias which the requester intends to take over.
Activation status per functional alias
M
Indicates the take over request result (accepted, rejected).
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.2.10 IWF Functional alias revoke notification
| Table 10.14.2.10-1 describes the information flow of the functional revoke notification from the MC service server to the IWF.
Table 10.14.2.10-1: IWF functional alias revoke notification
Information element
Status
Description
MC service ID
M
The identity of the requesting MC service user.
Functional alias
M
The functional alias which is being revoked.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.3 IWF Functional alias management procedures
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.3.1 General
| The following subclauses describe the relevant functional alias management procedures between the MC system and the IWF to enable role based addressing of users homed in the IWF.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.3.2 User homed in the IWF retrieves active functional alias(es) for a certain MC service user
| An user homed in the IWF can request the active functional alias(es) for a certain MC service user.
Figure 10.14.3.2-1 below illustrates the active functional alias list query for a certain MC service user.
Figure 10.14.3.2-1: IWF active functional alias list query
1. The user homed in the IWF requests a list of active functional aliases for a certain MC service ID from the MC service server by sending an IWF functional alias information query request encompassing the MC service ID or the functional alias of the queried user.
2. The MC service server checks whether the querying user homed in the IWF is authorized to perform the query. If authorized, then the MC service server retrieves the requested functional alias information based on the corresponding MC service ID or the MC service IDs based on the functional alias.
3. The MC service server sends an IWF functional alias information query response including the active functional alias or MC service ID information to the user homed in the IWF.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.3.3 User homed in the IWF activates functional alias(es) within an MC system
| The procedure for the user homed in the IWF activates functional alias(es) within an MC system is illustrated in figure 10.14.3.3-1.
Pre-conditions:
1. The IWF has already been provisioned (statically or dynamically) with the functional alias(es) information that the user homed in the IWF is allowed to activate.
2. MC service server has retrieved the user subscription and functional alias policy e.g. which user(s) are authorized to activate to what functional alias, priority, and other configuration data.
Figure 10.14.3.3-1: IWF functional alias activation procedure within an MC system
1. The user homed in the IWF requests the MC service server to activate a functional alias or a set of functional aliases.
2. The MC service server checks if there are any conflicts with active functional alias(es).
3. If the user homed in the IWF is authorised to activate the requested functional alias(es) then the MC service server stores the functional alias(es) status of the requested functional alias(es).
If a certain functional alias(es) can be simultaneously active for multiple users and the upper limit of number of simultaneous MC service users is not reached, the MC service shall activate the functional alias(es) for the user homed in the IWF and inform all other user(s) with sharing the same functional alias(es) (step 5). If the limit of number of simultaneous users is reached or the functional alias is not allowed to be shared, the request is rejected, and the IWF is notified (step 4).
If the functional alias(es) is (are) already used by another user(s), an authorized user homed in the IWF gets an offer to take over the functional alias from the user currently using the functional alias(es).
4. MC service server sends an IWF functional alias(es) activation response to the user homed in the IWF.
5. The MC service server informs all other MC service user(s) and/or IWF sharing the same functional alias(es).
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.3.4 User homed in the IWF de-activates functional alias(es) within an MC system
| The procedure for the user homed in the IWF de-activates functional alias(es) within an MC system is illustrated in figure 10.14.3.4-1.
When a user homed in the IWF does not want to use a functional alias(es) anymore, then the user homed in the IWF can de-activate functional alias(es).
Pre-conditions:
1. MC service server has already subscribed to the functional alias(es) information from the functional alias management server and has stored the data of the functional alias(es) a user homed in the IWF has activated.
Figure 10.14.3.4-1: IWF functional alias de-activation procedure within an MC system
1. The user homed in the IWF requests the MC service server to de-activate a functional alias or a set of functional aliases.
2. Based on the MC service user subscription and stored functional alias policy, the MC service server checks if the user homed in the IWF is authorized to de-activate from the requested functional alias(es) and if the user homed in the IWF has activated to the requested functional alias(es).
3. If the user homed in the IWF is authorized to de-activate from the requested functional alias(es) then the MC service server updates the functional alias activation status of the user homed in the IWF.
4. MC service server provides to the user homed in the IWF the functional alias de-activation response.
5. The MC service server informs all other MC service user(s) and/or users homed in the IWF sharing the same functional alias(es).
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.14.3.5 User homed in the IWF takes over functional alias(es) within an MC system
| The procedure for the user homed to IWF takes over functional alias(es) within an MC system is illustrated in figure 10.14.3.5-1.
During functional alias(es) activation, if the functional alias(es) is (are) already used by another MC service user(s), an authorized user homed in the IWF can get an offer to take over the functional alias(es) from the MC service user currently using the functional alias(es).
Pre-conditions:
1. MC service client 1 has performed the functional alias(es) activation procedure.
2. As result of the functional alias(es) activation procedure, the user homed in the IWF is aware which functional alias(es) are already used but can be taken over.
3. The user homed in the IWF decides to take over a functional alias.
Figure 10.14.3.5-1: IWF functional alias taking over procedure within an MC system
1. The user homed in the IWF requests the MC service server to take over a functional alias by sending an IWF functional alias take over request.
2. The MC service server checks if there are any conflicts taking over the functional alias.
3. If the user homed in the IWF is authorised to take over the requested functional alias then the MC service server sends a functional alias revoke notification to inform MC service client 1 that the functional alias has been revoked and is not any longer active for the user of MC service client 1.
4. The MC service server stores the functional alias status of the requested functional alias.
5. MC service server sends an IWF functional alias take over response to the user homed in the IWF.
6. The MC service server informs all other MC service user(s) sharing the same functional alias, of the take over by sending a functional alias status notification.
7. The MC service server informs all user(s) homed in the IWF sharing the same functional alias of the take over by sending an IWF functional alias status notification.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15 First-to-answer call setup
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.1 Description
| The present document specifies the interworking between LMR users and MCPTT clients for first-to-answer calls. It can be used based on MCPTT IDs, or based on functional alias for interworking with alternative addressing scheme used by the LMR system.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.2 Information flows for first-to-answer call
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.2.1 IWF first-to-answer call request
| Table 10.15.2.1-1 describes the information flow IWF first-to-answer call request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.15.2.1-1: IWF first-to-answer call request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
(see NOTE)
O
The MCPTT ID of the called party
Functional alias (see NOTE)
O
The functional alias of the called party
Use floor control indication
M
This element indicates whether floor control will be used for the private call.
SDP offer
O
Media parameters of MCPTT client.
Implicit floor request
O
An indication that the user is also requesting the floor.
Location information
O
Location of the calling party
NOTE: One of these information elements must be present. If the information element MCPTT ID is present, it may consist of a set of MCPTT IDs. If the information element functional alias is present it must consist of a single functional alias.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.2.2 IWF first-to-answer call response
| Table 10.15.2.2-1 describes the information flow IWF first-to-answer call response from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.15.2.2-1: IWF first-to-answer call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Functional alias
O
The functional alias of the called party
SDP answer
M
Media parameters selected
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.2.3 IWF first-to-answer call cancel request
| Table 10.15.2.3-1 describes the information flow IWF first-to-answer call cancel request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.15.2.3-1: IWF first-to-answer call cancel request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ID
M
The MCPTT ID of the called party
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.2.4 IWF first-to-answer call cancel response
| Table 10.15.2.4-1 describes the information flow IWF first-to-answer call cancel response from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.15.2.4-1: MCPTT first-to-answer call cancel response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the called party
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.3 Procedures
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.3.1 MCPTT user initiating a first-to-answer call
| In this procedure, an MCPTT user is initiating an MCPTT first-to-answer call for communicating with an LMR user via an IWF.
Pre-conditions:
1. The calling MCPTT user has selected first-to-answer call.
2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7].
3. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.15.3.1-1: MCPTT first-to-answer call initiated by MCPTT user
1. The MCPTT user at the MCPTT client initiates an MCPTT first-to-answer call. The MCPTT client sends an MCPTT first-to-answer call request towards the MCPTT server. The MCPTT first-to-answer call request contains the MCPTT ID corresponding to the calling MCPTT party and called LMR party, and an SDP offer containing one or more media types. The called LMR party can consist of a set of potential target recipients represented by their MCPTT IDs, or a functional alias. The following parameters are also included that describe the MCPTT client's choices:
- the encryption algorithm;
- the encryption mode (encrypted or not);
- an indication of whether the MCPTT client is requesting the floor, and if the MCPTT client is requesting the floor, and
- an indication of whether the call is to be full or half duplex (whether to establish floor control).
2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to initiate the first-to-answer call. The MCPTT server checks whether the provided functional alias of the calling user, if present, can be used and has been activated for the MCPTT user.
3. If authorized, the MCPTT server sends the IWF first-to-answer call request that may or may not include location of the requestor, depending on the outcome of the privacy check towards the IWF, including the original parameters and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7].
NOTE: How the IWF first-to-answer call request is forwarded to the LMR system is out of scope of the present document.
4. The IWF sends an IWF first-to-answer call response to the MCPTT server, indicating that the IWF does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may include one or more alternatives to the parameter values contained in step 3.
5. The MCPTT server forwards the MCPTT first-to-answer call response to the MCPTT client. If the result parameter indicates success, then the MCPTT client proceeds to step 6. Otherwise, if the parameters returned in the MCPTT first-to-answer call response are acceptable to the MCPTT client, then the MCPTT client can send a new MCPTT first-to-answer call request with the new parameters and behaves according to those parameters. The calling MCPTT user may be notified of the change in parameters, for example, that the call is to be without floor control. The MCPTT user can choose to end the call rather than continue with the new parameters. If the parameters returned are not acceptable to the MCPTT client, then the call fails.
6. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The MCPTT system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.15.3.2 LMR user initiating a first-to-answer call
| In this procedure, an MCPTT user is initiating an MCPTT first-to-answer call for communicating with an LMR user via an IWF.
Pre-conditions:
1. The calling LMR user has selected first-to-answer call
2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7].
3. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.15.3.2-1: MCPTT first-to-answer call initiated by MCPTT user
1. The IWF sends an IWF first-to-answer call request towards the MCPTT server. The IWF first-to-answer call request contains the MCPTT ID corresponding to the calling LMR party and called MCPTT party, and an SDP offer containing one or more media types. The called MCPTT party can consist of a set of potential target recipients represented by their MCPTT IDs, or a functional alias. The following parameters are also included that describe the LMR party's choices:
- the encryption algorithm;
- the encryption mode (encrypted or not);
- an indication of whether the LMR user is requesting the floor, and if the LMR user is requesting the floor, and
- an indication of whether the call is to be full or half duplex (whether to establish floor control).
2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to receive the first-to-answer call. The MCPTT server checks whether the provided functional alias of the calling user, if present, can be used and has been activated for the LMR user.
3. If authorized, the MCPTT server sends the MCPTT first-to-answer call request towards the MCPTT client, including the original parameters and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7].
4. The MCPTT client sends an MCPTT first-to-answer call response to the MCPTT server, indicating that the MCPTT client does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may include one or more alternatives to the parameter values contained in step 3.
5. The MCPTT server sends the IWF first-to-answer call response to the IWF offering the same media type as that sent in step 4. If the parameters returned are not acceptable to the IWF, then the call fails. If the parameters returned in the IWF private call response are different but acceptable to the IWF, then the IWF can send a new IWF private call request with the new parameters starting with step 1, which is to essentially restart the call. If there is no change of parameter, then the call proceeds to step 6.
6. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The MCPTT system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.16 Enhanced status
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.16.1 General
| 3GPP TS 23.282 [6] clause 7.9 describes a high-level procedure to provide enhanced status information to all the receiving MCData users.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.16.2 Preset values for enhanced status
| The configuration of preset values into the group configuration data is described in 3GPP TS 23 282 [6] clause 7.9.2.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.16.3 Enhanced status for on-network
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.16.3.1 Procedure (MCData to IWF)
| The procedure for an MCData user requesting to share enhanced status to an MCData group is as specified in 3GPP TS 23.282 [6] clause 7.9.3 for the enhanced status for on-network use; one or more users using MCData clients 2-n may be LMR users behind an IWF that has affiliated to the MCData group (see clause 10.1.2 of the present document). The IWF behaves as a peer MCData server.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.16.3.2 Procedure (IWF to MCData)
| The procedure for an IWF requesting, on behalf of an LMR user, to share enhanced status to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.9.3 for the enhanced status for on-network use, with the exception that MCData client 1 is located behind an IWF and one or more of the MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see clause 10.1.2 of the present document). The IWF behaves as a peer MCData server to other MCData servers.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17 Ad hoc group call
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.1 General
| The following clauses define information flows and signalling procedures for ad hoc group calls, where the ad hoc group call is established based on criteria or based on a list of participants provided by the call initiator. The MCPTT server determines the list of users. The list consists of MCPTT users and one LMR user that is representing a group in LMR system (GSM-R) Then the MCPTT server acts as the call control server and individually calls each MCPTT user that the specific LMR user via the IWF.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.2 Information flows for ad hoc group call
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.2.1 General
| The following clauses define information flows for ad hoc group calls on the IWF-1 interface. Ad hoc group call related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.379 [7].
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.2.2 IWF ad hoc group call request (MCPTT server – IWF and IWF - MCPTT server)
| Table 10.17.2.2-1 describes the information flow IWF ad hoc group call request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.17.2.2-1 IWF Ad hoc group call request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ad hoc group ID
M
The MCPTT group ID to be associated with the ad hoc group communication
Preconfigured MCPTT group ID
O
Indicates pre-configured group configuration to be used for the ad hoc group call
MCPTT ID
O
MCPTT ID of the participant being invited for the ad hoc group call
SDP offer
M
Offered Media parameters
Implicit floor request (see NOTE 1)
O
When originating client requests the floor, this element shall be included
Broadcast indicator
(see NOTE 2)
O
Indicates that the ad hoc group call request is for a broadcast ad hoc group call
Imminent peril indicator (see NOTE 2)
O
Indicates that the ad hoc group call request is an MCPTT imminent peril ad hoc group call
Emergency Indicator (see NOTE 2)
O
Indicates that the ad hoc group call request is an MCPTT emergency ad hoc group call
Location information
O
Location of the calling party.
Criteria for determining the participants (see NOTE 3)
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both which will be used by the MCPTT server for determining the participants e.g., it can be a location based criteria to invite participants in a particular area
Additional application specific data (see NOTE 4)
O
Some LMR systems use additional information at the application layer.
Requested priority
O
Application priority level requested for this group call
NOTE 1: This element is included only when the originating client requests the floor.
NOTE 2: If used, only one of these information elements is present.
NOTE 3: This element can be used by the IWF together with the LMR system to determine the users to be invited in the LMR system.
NOTE 4: This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.2.3 IWF ad hoc group call response (IWF - MCPTT server and MCPTT server - IWF)
| Table 10.17.2.3-1 describes the information flow IWF ad hoc group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.17.2.3-1 IWF Ad hoc group call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ad hoc group ID
M
The MCPTT group ID associated with the ad hoc group call
SDP answer
O
Media parameters selected and present if the Result is success.
Result
M
Result of the group call request (success or failure)
Additional application specific data (see NOTE)
O
Some LMR systems use additional information at the application layer.
NOTE: This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.2.4 IWF ad hoc group call release request (MCPTT server – IWF and IWF - MCPTT server)
| Table 10.17.2.4-1 describes the information flow IWF ad hoc group call release request from the MCPTT server to the IWF from the IWF to the MCPTT server.
Table 10.17.2.4-1 IWF ad hoc group call release request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the user authorized to release the ad hoc group call
Functional alias
O
The functional alias of the authorized user requesting to release the ad hoc group call
MCPTT ad hoc group ID
M
The MCPTT group ID of the ad hoc group call on which call is released
Additional application specific data (see NOTE)
O
Some LMR systems use additional information at the application layer.
NOTE: This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
10.17.2.5 IWF ad hoc group call release response (IWF - MCPTT server)
Table 10.17.2.5-1 describes the information flow IWF ad hoc group call release response from the IWF to the MCPTT server.
Table 10.17.2.5-1 IWF ad hoc group call release response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the ad hoc group call participant
Functional alias
O
The functional alias of the ad hoc group call participant
MCPTT ad hoc group ID
M
The MCPTT group ID of the ad hoc group call that is released
Additional application specific data (see NOTE)
O
Some LMR systems use additional information at the application layer.
NOTE: This element can be present if the LMR system uses it (like GSM-R). GSM-R uses for example UUI as defined in ETSI TS 103 389 [10] and ETSI TS 102 610 [11].
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.2.6 IWF ad hoc group emergency alert request (MCPTT server – IWF and IWF - MCPTT server)
| Table 10.17.2.6-1 describes the information flow IWF ad hoc group emergency alert request from the MCPTT server to the IWF and from the IWF to the MCPTT server.
Table 10.17.2.6-1 IWF Ad hoc group emergency alert request information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the alerting party
Functional alias
O
The functional alias of the alerting party
Ad hoc group ID
M
The target group ID associated with the alert
Organization name
O
The alerting MCPTT user's mission critical organization name
Location information
O
The alerting MC service client's location
Additional information
O
The alerting party may provide additional information related to the alert, e.g., medical help needed or reason for the alert
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCPTT server used for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
10.17.2.7 IWF ad hoc group emergency alert request return (MCPTT server – IWF)
Table 10.17.2.7-1 describes the information flow IWF ad hoc group emergency alert request return from the MCPTT server to the IWF.
Table 10.10.2.7-1 IWF ad hoc group emergency alert request return information elements
Information Element
Status
Description
MC service ID
M
The identity of the alerting party
Functional alias
O
The functional alias of the alerting party
Authorization result
M
Indicate if authorization is success or failure
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.2.8 IWF ad hoc group emergency alert response (IWF - MCPTT server and MCPTT server - IWF)
| Table 10.17.2.8-1 describes the information flow IWF ad hoc group emergency alert response from the IWF to the MCPTT server and from the MCPTT server to the IWF.
Table 10.17.2.8-1 IWF Ad hoc group emergency alert response information elements
Information Element
Status
Description
MCPTT ID
M
The identity of the target party
Functional alias
O
The functional alias of the target party
Ad hoc group ID
M
The target group ID associated with the alert
Call resulting criteria for determining the participants
O
Carries the details of criteria or meaningful label identifying the criteria or the combination of both that the MCPTT server used for determining the participants e.g., it can be a location-based criteria to invite participants in a particular area
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.3 Procedures
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.3.1 Ad hoc group call initiated by an MCPTT user with MCPTT server determining the participant list
| In this procedure, an MCPTT user is initiating an ad hoc group call based on criteria involving both MCPTT users and LMR users.
NOTE 1: How the LMR users are determined and invited to the MCPTT ad hoc group call is outside the scope of the present document.
Pre-conditions:
1. The MCPTT user at MCPTT client 1 is authorized to initiate ad hoc group call.
2. The MCPTT user at MCPTT client 1 wants to invite MCPTT and LMR users who are satisfying certain criteria for the ad hoc group call.
3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 2: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.17.3.1-1: Ad hoc group call setup initiated by an MCPTT user in the MCPTT system
The procedure and information flows as defined in 3GPP TS 23.379 [7] clause 10.19.3.1.1 is applied with the following differences:
1-7. Same as clause 10.19.3.1.3 in 3GPP TS 23.379 [7].
8. The MCPTT server sends the IWF ad hoc group call request to the IWF.
NOTE 3: The MCPTT server can send this message any time after step 4, in particular it does not have to wait for the Ad hoc group call responses in steps 7a and 7b.
9. The IWF returns with an IWF ad hoc group call response to the MCPTT server.
NOTE 4: IWF can handle the IWF ad hoc group call as a normal group call towards the LMR user in the LMR system.
10. Same as step 10 in clause 10.19.3.1.3 in 3GPP TS 23.379 [7].
11. The MCPTT server may notify the initiating MCPTT user of all MCPTT users who acknowledged the ad hoc group call request and joined the ad hoc group call. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the MCPTT ad hoc group call. The authorized users (not shown in figure), who are configured to receive the participants information of ad hoc group call, are notified to receive the MCPTT IDs of the MCPTT users who acknowledged the ad hoc group call request and joined the ad hoc group call, when the MCPTT users joins late or leave the MCPTT ad hoc group call.
NOTE 5: For LMR users, notification of acknowledging the ad hoc group call is not applicable.
12. MCPTT client 1, MCPTT client 2, and the LMR users establish media plane and floor control resources.
10.17.3.1a Ad hoc group emergency alert initiated by an MCPTT user
Figure 10.10.3.1a-1 illustrates the procedure for the MCPTT client initiating an ad hoc group emergency alert initiated by an authorized MCPTT user involving both MCPTT users and LMR users.
NOTE 1: How the LMR users are determined and invited to the MCPTT ad hoc group emergency alert is outside the scope of the present document.
Pre-conditions:
1. The MCPTT user at MCPTT client 1 is authorized to initiate ad hoc group emergency alert.
2. The MCPTT user at MCPTT client 1 wants to invite MCPTT and LMR users who are satisfying certain criteria for the ad hoc group emergency alert.
3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 2: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.10.3.1a-1: Ad hoc group emergency alert initiated by an MCPTT user
The procedure and information flow as defined in 3GPP TS 23.280 [5] clause 10.10.3.3.1 is applied with the following differences:
1-8. Same as clause 10.10.3.3.1 in 3GPP TS 23.280 [5].
9. The MCPTT server sends the IWF ad hoc group emergency alert request to the IWF.
NOTE 3: The MCPTT server can send this message any time after step 5, it does not have to wait for the ad hoc group call responses in step 8.
10. The IWF returns with an IWF ad hoc group emergency alert response to the MCPTT server.
11. Same as step 9 in clause 10.10.3.3.1 in 3GPP TS 23.280 [5].
12. If configured, an MCPTT client may setup a subsequent MCPTT ad hoc group emergency call, using the ad hoc group ID from the ad hoc group emergency alert.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.3.2 Ad hoc group call initiated by an LMR user with MCPTT server determining the participant list
| In this procedure, an LMR user is initiating an ad hoc group call based on criteria involving both MCPTT users and LMR users.
NOTE 1: How the LMR users are determined and invited to the MCPTT ad hoc group call is outside the scope of the present document.
Pre-conditions:
1. The LMR user is authorized to initiate ad hoc group call.
2. An LMR user want to invite MCPTT users who are satisfying certain criteria for the ad hoc group call.
3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 2: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.17.3.2-1: Ad hoc group call setup initiated by an LMR user in the MCPTT system
The procedure and information flows as defined in 3GPP TS 23.379 [7] clause 10.19.3.1.1 is applied with the IWF acting as a MCPTT client.
10.17.3.2a Ad hoc group emergency alert initiated by an LMR user
Figure 10.10.3.2a-1 illustrates the procedure for an LMR user client initiating an ad hoc group emergency alert involving both MCPTT users and LMR users.
NOTE 1: How the LMR users are determined and invited to the MCPTT ad hoc group emergency alert is outside the scope of the present document.
Pre-conditions:
1. The LMR user or IWF is authorized to initiate an ad hoc group emergency alert.
2. An LMR user wants to invite MCPTT users who are satisfying certain criteria for the ad hoc group emergency alert.
3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE 2: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.10.3.2a-1: Ad hoc group emergency alert initiated by an LMR user
1. The IWF initiates the ad hoc group emergency alert on behalf of the LMR system by sending an ad hoc group emergency alert request containing the details of the criteria to be applied by the MC service server for determining the participants list or the list of participants. The IWF may select a functional alias used for the MC service group emergency alert.
2. The MC service server checks whether the user identified by the MCPTT ID supplied by the IWF is authorized for initiation of ad hoc group emergency alerts and whether the request is supported. The MC service server checks whether the provided functional alias, if present, can be used and has been activated.
3. The MC service server sends the ad hoc group emergency alert request return to the IWF containing the result of whether the ad hoc group call is authorized or not. If the ad hoc group emergency alert request is not authorized, the MC service server and the IWF shall not proceed with the rest of the steps.
4. The MC service server determines the list of participants to be invited for the ad hoc group emergency alert based on the information present in the information element Criteria for determining the participants. The MC service server stores the ad hoc group ID together with the list of participants for the duration of the ad hoc group emergency alert. The MC service server considers the alerted participants as implicitly affiliated to the ad hoc group. Depending on the criteria provided and based on local policy, the MC service server may modify the content of the criteria received in step 1 to determine the list of participants.
5. The MC service server sends an ad hoc group emergency alert request including the ad hoc group ID, and the call resulting criteria towards the MC service clients 1 and 2.
6. MC service users are notified of the ad hoc group emergency alert. The functional alias of the MC service user initiating the ad hoc group emergency alert and additional information related to the alert may be displayed.
7. The receiving MC service clients send the ad hoc group emergency alert response to the MC service server to acknowledge the ad hoc group emergency alert.
8. The MC service server sends the ad hoc group emergency alert response to the IWF to inform about successful alert establishment, containing the ad hoc group ID (generated by the MC service server in the case where the MC service ad hoc group ID created by the IWF is not acceptable or the case where the MC service ad hoc group ID was not provided by the IWF) and the call resulting criteria.
9. If configured, the IWF may initiate on behalf of the LMR user in the LMR system a subsequent MCPTT ad hoc group emergency call, using the ad hoc group ID from the ad hoc group emergency alert.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.3.3 IWF ad hoc group call released by the MC system
| In this procedure, the ad hoc group call is released by the MC system due to the release conditions or the ad hoc group call is released by an authorized user.
Pre-conditions:
1. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
NOTE: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.17.3.3-1: Release IWF ad hoc group call by the MC system
The procedure and information flows as defined in 3GPP TS 23.379 [7] clause 10.19.3.1.2 and 10.19.3.1.2a are applied to the interactions between the MCPTT client and the MCPTT server. In addition, new step 2a and 2b are introduced.
1. The IWF ad hoc group call is releasing at the MCPTT system either initiated by the server due to the release conditions are met as described in clause 10.19.3.1.2 in 3GPP TS 23.379 [7] or by an authorized user as described in clause 10.19.3.1.2a in 3GPP TS 23.379 [7].
2a-2b. The MCPTT server sends the IWF ad hoc group call release request to the IWF (2a), and the IWF returns the IWF ad hoc group call release response (2b).
3. MCPTT client 1, client 2 and LMR users have successfully released the floor control and media plane resources associated with the ad hoc group call that is terminated and the ad hoc group ceases to exist (i.e., further call is not possible over the same ad hoc group).
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.3.4 IWF ad hoc group call released by the LMR system
| In this procedure, the ad hoc group call is released by the LMR system due to a release condition on the LMR system.
NOTE 1: Release conditions on the LMR system are outside the scope of the present document.
Pre-conditions:
1. The LMR user that is sending the ad hoc group call release request to the MCPTT server is an authorized user as described in clause 10.19.3.1.2a in 3GPP TS 23.379 [7].
2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
Figure 10.17.3.4-1: Release IWF ad hoc group call by the LMR system
The procedure and information flows as defined in 3GPP TS 23.379 [7] clause 10.19.3.1.2a are applied to the interactions between the LMR user and the MCPTT server.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.17.3.5 IWF ad hoc group call initiated by an MCPTT user using a participants list
| In this procedure, an MCPTT user is initiating an ad hoc group call with both MCPTT users and LMR users.
Pre-conditions:
1. The MCPTT client 1 knows the MCPTT IDs of the participants, including both MCPTT users and LMR users, to be involved in this call.
2. MCPTT client 1 and MCPTT client 2 are registered, and their respective users are authenticated and authorized to use the MCPTT service.
NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation.
Figure 10.17.3.5-1: Ad hoc group call setup initiated by an MCPTT user in the MCPTT system
The procedure and information flows as defined in 3GPP TS 23.379 [7] clause 10.19.3.1.1 is applied with the following differences:
1-3. Same as clause 10.19.3.1.1 in 3GPP TS 23.379 [7].
4a-4b. For each of the LMR users, the MCPTT server sends the IWF ad hoc group call request to the IWF. The IWF returns the IWF ad hoc group call response to the MCPTT server.
NOTE 2: IWF can handle the IWF ad hoc group call as a normal group call towards the LMR user in LMR system.
5. Same as clause 10.19.3.1.1 in 3GPP TS 23.379 [7].
6. If the initiating MCPTT user requires the acknowledgement from the invited MCPTT users, and the required MCPTT users do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), then the MCPTT server may proceed with or abandon the call and then notify the initiating MCPTT user that the acknowledgements did not include all required members according to ad hoc group call policy from the user profile configuration. The MCPTT server may notify the initiating MCPTT user of all MCPTT users who did not acknowledge the ad hoc group call request within the configured time. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the MCPTT ad hoc group call.
NOTE 3: For LMR users notification of not acknowledging the ad hoc group call is not possible.
7. MCPTT client 1, MCPTT client 2, and the LMR users establish media plane and floor control resources.
Annex A (informative):
LMR standards for interworking with 3GPP MC services
This annex lists published LMR standards about LMR system interworking with 3GPP MC services on the LMR side.
NOTE 1: This is not an exhaustive list of LMR and MC service interworking standards.
TETRA interworking with 3GPP MC services is specified in [12].
NOTE 2: Study of Interworking between P25 LMR and 3GPP (MCPTT) Mission Critical Services is under progress by ATIS and not yet published.
NOTE 3: FRMCS/GMS-R interworking with 3GPP MC service is specified in ETSI TS 103 792 and not yet published.
Annex B (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2017-06
-
-
-
-
-
TS template
0.0.0
2017-07
SA6#18
Implementation of the following p-CRs approved by SA6:
S6‑170920, S6‑170976, S6‑170977, S6‑170978, S6‑170979, S6‑170981, S6‑171013, S6‑171016, S6‑171019, S6‑171065, S6‑171066, S6‑171067, S6‑171068, S6‑171069, S6‑171070, S6‑171071 and S6‑171072.
0.1.0
2017-10
SA6#19
Implementation of the following p-CRs approved by SA6:
S6‑171310, S6‑171311, S6‑171321, S6‑171325, S6‑171376, S6‑171420, S6‑171421, S6‑171423, S6‑171424, S6‑171427, S6‑171428, S6‑171429, S6‑171430, S6‑171431, S6‑171433, S6‑171434, S6‑171460, S6‑171461, S6‑171462 and S6‑171489.
0.2.0
2017-12
SA6#20
Implementation of the following p-CRs approved by SA6: S6‑171511, S6‑171533, S6‑171614, S6‑171723, S6‑171724, S6‑171725, S6‑171726, S6‑171727, S6‑171728, S6‑171733, S6‑171735, S6‑171738, S6‑171740, S6‑171741, S6‑171749, S6‑171751, S6‑171797, S6‑171801, S6‑171802, S6‑171803, S6‑171806, S6‑171808, S6‑171809, S6‑171827, S6‑171828, S6‑171853, S6‑171854, S6‑171875
0.3.0
2017-12
SA6#20
Rapporteur's editorial changes
0.3.1
2017-12
SA#78
SP-170902
Submitted to SA#78 for information
1.0.0
2018-01
SA6#21
Implementation of the following p-CRs approved by SA6: S6‑180055, S6‑180108, S6‑180109, S6‑180171, S6‑180175, S6‑180190, S6‑180199, S6‑180200, S6‑180214
1.1.0
2018-02
Editorial changes
1.1.1
2018-03
SA6#22
Implementation of the following p-CRs approved by SA6:
S6‑180248, S6‑180347, S6‑180358, S6‑180361, S6‑180362,
S6‑180363, S6‑180364, S6‑180374, S6‑180390, S6‑180440, S6‑180442, S6‑180444, S6‑180446, S6‑180447, S6‑180449, S6‑180450, S6‑180451, S6‑180452, S6‑180453, S6‑180454, S6‑180461, S6‑180462, S6‑180481, S6‑180491.
1.2.0
2018-03
Editorial fixes, missing LMR abbreviation from S6-180364.
1.2.1
2018-03
SA#79
SP-180159
Submitted for approval at SA#79
2.0.0
2018-04
SA#79
SP-180159
MCC Editorial update for publication after TSG SA approval (SA#79)
15.0.0
2018-06
SA#80
SP-180372
0001
2
F
Flow name update from MCPTT call end to MCPTT private call end
15.1.0
2018-06
SA#80
SP-180372
0002
1
F
Corrections to Imminent peril group call initiated by MCPTT user
15.1.0
2018-06
SA#80
SP-180372
0003
2
F
Corrections to Imminent peril group call initiated by LMR user
15.1.0
2018-06
SA#80
SP-180372
0004
F
Corrections to Imminent peril cancel
15.1.0
2018-06
SA#80
SP-180372
0005
3
F
Corrections to chat group call procedures and information flows
15.1.0
2018-06
SA#80
SP-180372
0006
1
F
Alignment of terminology emergency and imminent peril
15.1.0
2018-06
SA#80
SP-180372
0007
1
F
Alignment of terminology - pre-arranged group call
15.1.0
2018-06
SA#80
SP-180372
0008
1
F
IWF actions on Imminent peril group calls
15.1.0
2018-06
SA#80
SP-180372
0009
1
F
Corrections to emergency group call procedures
15.1.0
2018-09
SA#81
SP-180673
0017
2
F
IWF SDS fix
15.2.0
2018-09
SA#81
SP-180679
0014
1
F
IWF affiliation auth update
16.0.0
2018-09
SA#81
SP-180679
0015
1
F
IWF broadcast call fixes
16.0.0
2018-09
SA#81
SP-180679
0016
1
F
IWF alert cancel alignment
16.0.0
2018-12
SA#82
SP-181179
0019
F
IWF group call request broadcast indicator correction
16.1.0
2018-12
SA#82
SP-181179
0021
2
C
Add Implicit floor request to IWF group call request and IWF imminent peril group call request
16.1.0
2018-12
SA#82
SP-181179
0022
C
Add Location information to IWF floor request and IWF floor taken messages
16.1.0
2019-03
SA#83
SP-190076
0023
1
F
MCPTT ID in interworking floor control
16.2.0
2019-03
SA#83
SP-190076
0024
2
C
IWF alignment for talker location in requests for Group call and Group-broadcast group call setup
16.2.0
2019-03
SA#83
SP-190076
0025
1
C
IWF alignment for talker location in Chat group
16.2.0
2019-03
SA#83
SP-190076
0026
2
C
IWF alignment for talker location in Private call
16.2.0
2019-03
SA#83
SP-190076
0027
1
C
IWF alignment for talker Location related to Imminent peril groups
16.2.0
2019-03
SA#83
SP-190076
0028
1
C
IWF alignment for current talker location
16.2.0
2019-03
SA#83
SP-190076
0029
2
C
TS 23.379 alignment for late join
16.2.0
2019-03
SA#83
SP-190076
0030
2
B
Analogue FM interworking
16.2.0
2019-06
SA#84
SP-190487
0033
1
C
23.283 location with implicit floor request
16.3.0
2019-06
SA#84
SP-190488
0035
2
B
Functional Alias management for interworking between MC service system and LMR system
16.3.0
2019-09
SA#85
SP-190728
0038
4
B
IWF preconfigured groups
16.4.0
2019-09
SA#85
SP-190728
0039
4
B
IWF add user to temporary pre-configured group regroup
16.4.0
2019-09
SA#85
SP-190728
0041
2
B
IWF temporary group calls
16.4.0
2019-09
SA#85
SP-190728
0042
4
B
IWF user regroup with pre-configured group
16.4.0
2019-09
SA#85
SP-190728
0044
4
B
IWF preconfigured broadcast group calls
16.4.0
2019-09
SA#85
SP-190728
0045
2
B
IWF preconfigured broadcast group calls
16.4.0
2019-09
SA#85
SP-190728
0047
1
F
IWF identities wording correction
16.4.0
2019-09
SA#85
SP-190728
0051
1
F
Remove 10.5.2.17 Editor's Note
16.4.0
2019-09
SA#85
SP-190735
0036
2
B
Functional alias for private call interworking between an MC service system and an LMR system
17.0.0
2019-09
SA#85
SP-190735
0037
2
B
Functional alias for floor control interworking between MC service system and LMR system
17.0.0
2019-09
SA#85
SP-190735
0046
2
B
IWF functional alias restoration
17.0.0
2019-09
SA#85
SP-190735
0048
2
B
Add first-to-answer for interworking with GSM-R
17.0.0
2019-09
SA#85
SP-190735
0050
1
B
Add enhancements for interworking of MCData SDS with GSM-R SMS
17.0.0
2019-12
SA#86
SP-191113
0049
3
B
Add enhancements for interworking of MCPTT group calls with GSM-R
17.1.0
2019-12
SA#86
SP-191113
0052
1
F
Text improvements related to functional alias interworking
17.1.0
2020-09
SA#89
SP-200838
0054
1
A
Interworking private call floor control
17.2.0
2020-09
SA#89
SP-200846
0055
1
C
Implicit affiliation and interworking
17.2.0
2021-12
SA#94
SP-211520
0057
A
Correction to Disposition Notification handling when LMR system temporarily disables Disposition Notification
17.3.0
2021-12
SA#94
SP-211527
0059
2
F
Correction of Enhanced Status description
17.3.0
2022-06
SA#96
SP-220476
0061
F
Corrections to the use of MC service system
18.0.0
2023-03
SA#99
SP-230287
0066
2
B
LMR-3GPP Location Interworking
18.1.0
2023-03
SA#99
SP-230290
0067
1
F
Correction on optional use of Non-3GPP security message response
18.1.0
2024-09
SA#105
SP-241224
0076
2
B
Interworking ad hoc group call
19.0.0
2024-09
SA#105
SP-241224
0077
1
B
Interworking of private call with GSM-R
19.0.0
2024-09
SA#105
SP-241224
0078
1
B
Interworking ad hoc group call based on criteria
19.0.0
2024-09
SA#105
SP-241722
0080
1
B
Introduce annex about MCX-LMR interworking
19.1.0
2025-03
SA#107
SP-250199
0082
1
A
Resolve the EN in clause 10.13
19.2.0
2025-03
SA#107
SP-250203
0084
1
A
Resolve ENs in clause 10.14
19.2.0
2025-03
SA#107
SP-250196
0090
1
A
Handling of response to non-3GPP Security Message
19.2.0
2025-06
SA#108
SP-250605
0094
D
Editorial correction in 10.17.2
19.3.0
2025-06
SA#108
SP-250602
0097
A
Correction of information flow description - R19
19.3.0
2025-06
SA#108
SP-250606
0091
B
Interworking support for ad hoc group emergency alerts (MCPTT user initiated)
20.0.0
2025-06
SA#108
SP-250606
0092
1
B
Interworking support for ad hoc group emergency alerts (LMR initiated)
20.0.0
2025-06
SA#108
SP-250606
0093
B
Interworking support for ad hoc group emergency alerts (Information flows)
20.0.0
2026-01
SA#110
SP-251493
0101
1
A
Correction for LMR Key Management Messages to apply only to MCData service
20.1.0
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 1 Scope
| The present document defines the Stage 2 architecture enhancements for 5G System (5GS) to support network data analytics services in 5G Core network.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[5] Void.
[6] 3GPP TS 28.532: "Management and orchestration; Generic management services".
[7] 3GPP TS 28.550: "Management and orchestration; Performance Assurance".
[8] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[9] 3GPP TS 28.545: "Management and orchestration; Fault Supervision (FS)".
[10] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[11] ITU‑T Recommendation P.1203.3: "Parametric bitstream-based quality assessment of progressive download and adaptive audiovisual streaming services over reliable transport - Quality integration module".
[12] 3GPP TS 38.215: "NR; Physical layer measurements".
[13] Void.
[14] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[15] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[16] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[17] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes".
[18] 3GPP TS 29.510: "5G System; Network function repository services; Stage 3".
[19] 3GPP TS 28.533: "Management and orchestration; Architecture framework".
[20] 3GPP TS 37.320: "Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; stage 2".
[21] 3GPP TS 28.201: "Charging management; Network slice performance and analytics charging in the 5G System (5GS); stage 2".
[22] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[23] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[24] 3GPP TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[25] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[26] 3GPP TS 29.503: "Unified Data Management Services; Stage 3".
[27] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[28] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[29] 3GPP TS 26.118: "Virtual Reality (VR) profiles for streaming applications".
[30] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[31] 3GPP TS 26.512: "5G Media Streaming (5GMS); Protocols".
[32] 3GPP TS 26.531: "Data Collection and Reporting; General Description and Architecture".
[33] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[34] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[35] 3GPP TS 22.071: "Technical Specification Group Systems Aspects; Location Services (LCS)".
[36] 3GPP TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".
[37] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3".
[38] GSMA TS.06: "IMEI Allocation and Approval Process".
[39] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[40] ITU‑T Y.1540: "Internet protocol data communication service - IP packet transfer and availability performance parameters".
[41] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRMs). Integration Reference Point (IRP): Information Service (IS)".
[42] 3GPP TS 32.422: "Subscriber and equipment trace: Trace control and configuration management".
[43] 3GPP TS 26.532: "Data Collection and Reporting; Protocols and Formats".
[44] 3GPP TS 38.455: "NG-RAN; NR Positioning Protocol A (NRPPa)".
[45] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics (MDA)".
[46] 3GPP TS 28.537: "Management and orchestration; Management capabilities".
[47] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[48] 3GPP TS 29.515: "Gateway Mobile Location Services; Stage 3".
[49] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[50] 3GPP TS 28.558: "User Equipment (UE) level measurements for 5G system".
[51] 3GPP TS 29.564: "5G System; User Plane Function Services; Stage 3".
[52] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[53] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
[54] 3GPP TS 28.404: "Quality of Experience (QoE) measurement collection; Concepts, use cases and requirements".
[55] 3GPP TS 28.405: "Quality of Experience (QoE) measurement collection; Control and configuration".
[56] 3GPP TS 28.406: "Quality of Experience (QoE) measurement collection; Information definition and transport".
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 3 Definitions and abbreviations
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 23.501 [2] and TS 23.503 [4]. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Analytics Accuracy Information: Represent a performance measure of an Analytics ID provided by an NWDAF containing AnLF, which includes accuracy value of the Analytics ID and optionally the corresponding number of samples. The accuracy value is computed as the number of correct predictions divided by the total number of predictions.
Analytics Feedback Information: Indicates that the consumer NF has taken action(s) influenced by the previously provided analytics, which may or may not affect the ground truth data.
Label: A label is the training objective in supervised machine learning.
ML Model Accuracy Information: Represent a performance measure of a ML Model provided by an NWDAF containing MTLF, which includes accuracy value of the ML Model and optionally the corresponding number of samples. The accuracy value is computed as the number of correct predictions divided by the total number of predictions.
Vertical Federated Learning (VFL): A federated learning technique without exchanging/sharing local data set, wherein the local data set in different VFL Participant for local model training have different feature spaces for the same samples (e.g. UE IDs).
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2] and TS 23.503 [4] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
AI/ML Artificial Intelligence/Machine Learning
DCAF Data Collection Application Function
FL Federated Learning
HFL Horizontal Federated Learning
RE-NWDAF Roaming Exchange Network Data Analytics Function
VFL Vertical Federated Learning
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 4 Reference Architecture for Data Analytics
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 4.1 General
| The NWDAF (Network Data Analytics Function) is part of the architecture specified in TS 23.501 [2] and uses the mechanisms and interfaces specified for 5GC in TS 23.501 [2] and OAM services (see clause 6.2.3.1).
The NWDAF may support the following functionalities:
- Data collection based on subscription to events provided by AMF, SMF, UPF, PCF, UDM, NSACF, AF (directly or via NEF) and OAM;
- Analytics and Data collection using the DCCF (Data Collection Coordination Function);
- Retrieval of information from data repositories (e.g. from UDR via UDM for subscriber-related information or optinally via NEF(PFDF) for PFD information);
- Data collection of location information using LCS (finer granularity location information determined by LMF);
- Storage and retrieval of information from ADRF (Analytics Data Repository Function);
- Analytics and Data collection from MFAF (Messaging Framework Adaptor Function);
- Retrieval of information about NFs (e.g. from NRF for NF-related information);
- On demand provision of analytics to consumers, as specified in clause 6.
- Provision of bulked data related to Analytics ID(s).
- Provision of Accuracy information about Analytics ID(s).
- Provision or retrieval of ML Model Accuracy Information or ML Model accuracy degradation about a ML Model.
- Federated Learning.
NOTE 1: In this specification, the term Federated Learning (FL) refers to Horizontal Federated Learning.
- Vertical Federated Learning.
A single instance or multiple instances of NWDAF may be deployed in a PLMN. If multiple NWDAF instances are deployed, the architecture supports deploying the NWDAF as a central NF, as a collection of distributed NFs, or as a combination of both. If multiple NWDAF instances are deployed, an NWDAF can act as an aggregate point (i.e. Aggregator NWDAF) and collect analytics information from other NWDAFs, which may have different Serving Areas, to produce the aggregated analytics (per Analytics ID), possibly with Analytics generated by itself.
NOTE 2: When multiple NWDAFs exist, not all of them need to be able to provide the same type of analytics results, i.e. some of them can be specialized in providing certain types of analytics. An Analytics ID information element is used to identify the type of supported analytics that NWDAF can generate.
NOTE 3: NWDAF instance(s) can be collocated with a 5GS NF.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 4.2 Non-roaming architecture
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 4.2.0 General
| As depicted in Figure 4.2.0-1, the 5G System architecture allows NWDAF to collect data from any 5GC NF. The NWDAF belongs to the same PLMN as the 5GC NF that provides the data.
Figure 4.2.0-1: Data Collection architecture from any 5GC NF
The Nnf interface is defined for the NWDAF to request subscription to data delivery for a particular context, to cancel subscription to data delivery and to request a specific report of data for a particular context.
The 5G System architecture allows NWDAF to retrieve the management data from OAM by invoking OAM services.
The 5G System architecture allows NWDAF to collect data from any 5GC NF or OAM using a DCCF with associated Ndccf services as specified in clause 8.2.
The 5G System architecture allows NWDAF and DCCF to collect data from an NWDAF with associated Nnwdaf_DataManagement services as specified in clause 7.4. The 5G system architecture allows MFAF to fetch data from an NWDAF with associated Nnwdaf_DataManagement service as specified in clause 7.4.
Figure 4.2.0-1a: Data Collection architecture using Data Collection Coordination
As depicted in Figure 4.2.0-1a, the Ndccf interface is defined for the NWDAF to support subscription request(s) for data delivery from a DCCF, to cancel subscription to data delivery and to request a specific report of data. If the data is not already being collected, the DCCF requests the data from the Data Source using Nnf services. The DCCF may collect the data and deliver it to the NWDAF or the DCCF may rely on a messaging framework to collect data from the NF and deliver it to the NWDAF.
As depicted in Figure 4.2.0-2, the 5G System architecture allows any 5GC NF to request network analytics information from NWDAF containing Analytics logical function (AnLF). The NWDAF belongs to the same PLMN as the 5GC NF that consumes the analytics information.
Figure 4.2.0-2: Network Data Analytics Exposure architecture
The Nnwdaf interface is defined for 5GC NFs, to request subscription to network analytics delivery for a particular context, to cancel subscription to network analytics delivery and to request a specific report of network analytics for a particular context.
NOTE 1: The 5G System architecture also allows other consumers such as OAM and CEF (Charging Enablement Function) to request network analytics information from NWDAF.
The 5G System architecture allows any NF to obtain Analytics from an NWDAF using a DCCF function with associated Ndccf services, as specified in clause 8.2.
The 5G System architecture allows NWDAF and DCCF to request historical analytics from an NWDAF with associated Nnwdaf_AnalyticsSubscription services as specified in clause 7.2. The 5G system architecture allows MFAF to fetch historical analytics from an NWDAF with associated Nnwdaf_AnalyticsSubscription service as specified in clause 7.2.
Figure 4.2.0-2a: Network Data Analytics Exposure architecture using Data Collection Coordination
As depicted in Figure 4.2.0-2a, the Ndccf interface is defined for any NF to support subscription request(s) to network analytics, to cancel subscription for network analytics and to request a specific report of network analytics. If the analytics is not already being collected, the DCCF requests the analytics from the NWDAF using Nnwdaf services. The DCCF may collect the analytics and deliver it to the NF, or the DCCF may rely on a messaging framework to collect analytics and deliver it to the NF.
As depicted in Figure 4.2.0-3, the 5G System architecture allows NWDAF containing Analytics logical function (AnLF) to use trained ML Model provisioning services from another NWDAF containing Model Training logical function (MTLF).
NOTE 2: Analytics logical function and Model Training logical function are described in clause 5.1.
Figure 4.2.0-3: Trained ML Model Provisioning architecture
The Nnwdaf interface is used by an NWDAF containing AnLF to request and subscribe to trained ML Model provisioning services.
NOTE 3: The NWDAF trained ML Model provisioning services are described in clause 7.5 and clause 7.6.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 4.2.1 Analytics Data Repository Function
| As depicted in Figure 4.2.1-1, the 5G System architecture allows ADRF to store and retrieve the collected data, analytics and ML Model(s). The following options are supported:
- ADRF exposes the Nadrf service for storage and retrieval of data, analytics or ML Model(s) by other 5GC NFs (e.g. NWDAF) which access the data using Nadrf services.
- Based on the NF request or configuration on the DCCF, the DCCF may determine the ADRF and interact directly or indirectly with the ADRF to request or store data or analytics. The interaction can be:
- Direct: the DCCF requests to store data or analytics in the ADRF via an Nadrf service, or via an Ndccf_DataManagement_Notify (e.g. when ADRF requested data or analytics collection notification via DCCF). In addition, the DCCF retrieves data or analytics from the ADRF via an Nadrf service.
- Indirect: the DCCF requests that the Messaging Framework to store data or analytics in the ADRF i.e. via an Nadrf service or via an Nmfaf_3daDataManagement_Configure. The Messaging Framework may contain one or more adaptors that translate between 3GPP defined protocols.
NOTE 1: The internal logic of Messaging Framework is outside the scope of 3GPP, only the MFAF and the interface between MFAF and other 3GPP defined NF is under 3GPP scope.
- A Consumer NF may specify in requests to a DCCF that data or analytics provided by a Data Source needs to be stored in the ADRF.
- The ADRF stores data or analytics received in an Nadrf_DataManagement_StorageRequest sent directly from an NF, or data or analytics received in an Ndccf_DataManagement_Notify / Nmfaf_3caDataManagement_Notify or Nnwdaf_DataManagement_Notify from the DCCF, MFAF or from the NWDAF.
- The ADRF may store, provide or delete ML Model(s) based on the Nadrf_MLModelManagement service received from NWDAF.
- The ADRF checks if the Consumer is authorized to access ADRF services and provides the requested data, analytics or ML Model(s) using the procedures specified in clause 7.1.4 of TS 23.501 [2].
Figure 4.2.1-1: Storage architecture for Analytics, Collected Data and ML Model(s)
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 4.3 Roaming architecture
| Based on operator's policy and local regulations (e.g. privacy), data or analytics may be exchanged between PLMNs (i.e. HPLMN and VPLMN). In a PLMN, an NWDAF is used as exchange point to exchange analytics and to collect input data for analytics with other PLMNs. The NWDAF with roaming exchange capability is called Roaming Exchange NWDAF (RE-NWDAF).
Figure 4.3-1: Roaming Architecture to exchange Input Data or Data Analytics between VPLMN and HPLMN
Using the architecture shown in Figure 4.3-1:
- For outbound roaming users, the NF consumer in the HPLMN can retrieve analytics from the VPLMN via the H-RE-NWDAF in HPLMN and V-RE-NWDAF in VPLMN.
NOTE 1: The analytics from the VPLMN may be generated by the V-RE-NWDAF in the VPLMN or by other NWDAFs in the VPLMN.
- For outbound roaming users, the H-RE-NWDAF in HPLMN can collect data from the VPLMN via V-RE-NWDAF in VPLMN.
- For inbound roaming users, the NF consumer in the VPLMN can retrieve analytics from the HPLMN via V-RE-NWDAF in VPLMN and H-RE-NWDAF in HPLMN.
NOTE 2: The analytics from the HPLMN may be generated by H-RE-NWDAF in the HPLMN or other NWDAFs in the HPLMN.
- For inbound roaming users, the V-RE-NWDAF can collect data from the HPLMN via the H-RE-NWDAF.
NOTE 3: Both local breakout and home routed roaming architectures support the data or analytics exchanging between PLMNs.
NOTE 4: Interactions between RE-NWDAFs of different PLMNs may be via SEPPs, which are not depicted in the architecture for the sake of clarity.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 5 Network Data Analytics Functional Description
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 5.1 General
| The NWDAF provides analytics to 5GC NFs and OAM as defined in clause 7. An NWDAF may contain the following logical functions:
- Analytics logical function (AnLF): A logical function in NWDAF, which performs inference, derives analytics information (i.e. derives statistics and/or predictions based on Analytics Consumer request) and exposes analytics service i.e. Nnwdaf_AnalyticsSubscription or Nnwdaf_AnalyticsInfo.
- Model Training logical function (MTLF): A logical function in NWDAF, which trains Machine Learning (ML) models and exposes new training services (e.g. providing trained ML Model) as defined in clause 7.5 and clause 7.6.
NOTE 1: NWDAF can contain an MTLF or an AnLF or both logical functions.
NOTE 2: Pre-trained ML Model storage and provisioning to NWDAF is out of the scope of 3GPP.
Analytics information are either statistical information of the past events, or predictive information.
The NWDAF (MTLF) may also provide trained ML Models to the LMF, for LMF-based AI/ML Positioning as defined in TS 23.273 [39].
Different NWDAF instances may be present in the 5GC, with possible specializations per type of analytics. The capabilities of a NWDAF instance are described in the NWDAF profile stored in the NRF.
To guarantee the accuracy of analytics output for an Analytics ID, based on the UE abnormal behaviour analytics from itself or other NWDAF including abnormal UE list and the observed time window, the NWDAF is to detect and may delete the input data from the abnormal UE(s) and then may generate a new ML Model and/or analytics outputs for the Analytics ID without the input data related to abnormal UE list during the observed time window and then send/update the ML Model Information and/or analytics outputs to the subscribed NWDAF service consumer.
In order to support NFs to discover and select an NWDAF instance containing MTLF, AnLF, or both, that is able to provide the required service (e.g. analytics exposure or ML Model provisioning) for the required type of analytics, each NWDAF instance should provide the list of supported Analytics IDs (possibly per supported service) when registering to the NRF, in addition to other NRF registration elements of the NF profile. NFs requiring the discovery of an NWDAF instance that provides support for some specific service(s) for a specific type of analytics may query the NRF for NWDAFs supporting the required service(s) and the required Analytics ID(s).
The consumers, i.e. 5GC NFs and OAM, decide how to use the data analytics provided by NWDAF.
The interactions between 5GC NF(s) and the NWDAF take place within a PLMN.
The NWDAF has no knowledge about NF application logic. The NWDAF may use subscription data but only for statistical purpose.
The NWDAF architecture allows for arranging multiple NWDAF instances in a hierarchy/tree with a flexible number of layers/branches. The number and organisation of the hierarchy layers, as well as the capabilities of each NWDAF instance remain deployment choices.
In a hierarchical deployment, NWDAFs may provide data collection exposure capability for generating analytics based on the data collected by other NWDAFs, when DCCF, MFAF are not present in the network.
In order to make NWDAF discoverable in some network deployments, NWDAF may be configured (e.g. for UE mobility analytics) to register in UDM (Nudm_UECM_Registration service operation) for the UE(s) it is serving and for the related Analytics ID(s). Registration in UDM should take place at the time the NWDAF starts serving the UE(s) or collecting data for the UE(s). Deregistration in UDM takes place when NWDAF deletes the analytics context for the UE(s) (see clause 6.1B.4) for a related Analytics ID.
NOTE 3: The procedures for data collection for UE related analytics need to take user consent into account. The user consent for analytics is defined in clause 6.2.9.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 5.2 NWDAF Discovery and Selection
| The NWDAF service consumer selects an NWDAF that supports requested analytics information and required analytics capabilities and/or requested ML Model Information by using the NWDAF discovery principles defined in clause 6.3.13 of TS 23.501 [2].
Different deployments may require different discovery and selection parameters. Different ways to perform discovery and selection mechanisms depend on different types of analytics/data (NF related analytics/data and UE related analytics/data). NF related refers to analytics/data that do not require a SUPI nor group of SUPIs (e.g. NF load analytics). UE related refers to analytics/data that requires SUPI or group of SUPIs (e.g. UE mobility analytics).
In order to discover an NWDAF containing AnLF using the NRF:
- If the analytics is related to NF(s) and the NWDAF service consumer (other than an NWDAF) cannot provide an Area of Interest for the requested data analytics, the NWDAF service consumer may select an NWDAF with large serving area from the candidate NWDAFs from discovery response. Alternatively, in case the consumer receives NWDAF(s) with aggregation capability, the consumer preferably selects an NWDAF with aggregation capability with large serving area.
NOTE 1: If the selected NWDAF cannot provide the requested data analytics, e.g. due to the NF(s) to be contacted being out of serving area of the NWDAF, the selected NWDAF might reject the analytics request/subscription or it might query the NRF with the service area of the NF to be contacted to determine another target NWDAF.
- If the analytics is related to UE(s) and the NWDAF service consumer (other than an NWDAF) cannot provide an Area of Interest for the requested data analytics, the NWDAF service consumer may select an NWDAF with large serving area from the candidate NWDAFs from discovery response. Alternatively, in case the consumer receives NWDAF(s) with aggregation capability, the consumer preferably selects an NWDAF with aggregation capability with large serving area.
NOTE 2: If a selected NWDAF cannot provide analytics for the requested UE(s) (e.g. the NWDAF serves a different serving area), the selected NWDAF might reject the analytics request/subscription or it might determine the AMF serving the UE as specified in clause 6.2.2.1, request UE location information from the AMF and query the NRF with the tracking area where the UE is located to discover another target NWDAF serving the area where the UE(s) is located.
- If the analytics are related to UE(s) and if NWDAF instances indicate weights for TAIs in their NF profile (see clause 6.3.13 of TS 23.501 [2]), the NWDAF service consumer may use the weights for TAIs to decide which NWDAF to select.
- If the NWDAF service consumer needs to discover an NWDAF containing an AnLF with analytics accuracy checking capability, the consumer may query NRF providing also the analytics accuracy checking capability in the discovery request.
- If the NWDAF service consumer needs to discover an NWDAF containing AnLF which can use the Model provided by the specific NWDAF containing MTLF (e.g., in case of analytics context transfer), the consumer should discover the NWDAF(s) whose vendor ID is in the ML Model Interoperability indicator of the NWDAF containing MTLF.
If the NWDAF service consumer needs to discover an NWDAF that is able to collect data from particular data sources identified by their NF Set IDs or NF types or to collect data from particular NWDAF Serving Area, the consumer may query NRF providing the NF Set IDs or NF types or Area of Interest in the discovery request.
NOTE 3: The NF Set ID or NF Type of a data source serving a particular UE, can be determined as indicated in Table 5A.2-1.
In order to discover an NWDAF that has registered in UDM for a given UE:
- NWDAF service consumers or other NWDAFs interested in UE related data or analytics, if supported, may make a query to UDM to discover an NWDAF instance that is already serving the given UE.
If an NWDAF service consumer needs to discover NWDAFs with data collection exposure capability, the NWDAF service consumer may discover via NRF the NWDAF(s) that provide the Nnwdaf_DataManagement service and their associated NF type of data sources or their associated NF Set ID of data sources or NWDAF Serving Area information as defined in clause 6.3.13 of TS 23.501 [2].
In order to discover an NWDAF containing MTLF via NRF:
- When one or more trained ML Models are available for one or more Analytics ID(s) the NWDAF containing MTLF shall include the Analytics ID(s) that is(are) supported per service in the registration towards NRF. The NWDAF containing MTLF may wait to register in NRF the above services until at least one trained model is available. The NWDAF containing MTLF may provide to the NRF a list of Analytics IDs corresponding to the trained ML Models and possibly the ML Model Filter Information for the trained ML Model per Analytics ID(s), if available. In this Release of the specification, only the S-NSSAI(s) and Area(s) of Interest from the ML Model Filter Information for the trained ML Model per Analytics ID(s) may be registered into the NRF during the NWDAF containing MTLF registration. If supporting model training for the LMF-based AI/ML Positioning, the NWDAF containing MTLF provides its NF profile to the NRF during registration with an LMF-based AI/ML Positioning indication and positioning case information (i.e. NG RAN assisted LMF-based AI/ML Positioning case). If the NWDAF containing MTLF supports ML Model interoperability, the NWDAF containing MTLF includes, in the registration to the NRF, an ML Model Interoperability indicator for each Analytics ID.
NOTE 4: How to implement the LMF-based AI/ML Positioning indication in a backward compatible and extensible manner is up to stage 3.
- The ML Model Interoperability indicator comprises a list of NWDAF providers (vendors) that are allowed to retrieve ML Models from this NWDAF containing MTLF. It also indicates that the NWDAF containing MTLF supports the interoperable ML Models requested by the NWDAFs from the vendors in the list.
NOTE 5: The S-NSSAI(s) and Area(s) of Interest from the ML Model Filter Information are within the indicated S-NSSAI and NWDAF Serving Area information in the NF profile of the NWDAF containing MTLF, respectively.
- During the discovery of NWDAF containing MTLF, a consumer (e.g. an NWDAF containing AnLF, an NWDAF containing MTLF as FL server or FL client) may include in the request the target NF type (i.e. NWDAF), the Analytics ID(s), the S-NSSAI(s), Area(s) of Interest of the Trained ML Model required and Vendor ID. If the consumer is an LMF, it shall include in the request an LMF-based AI/ML Positioning indication that indicates the NWDAF shall support ML Model training for LMF-based AI/ML Positioning. The NRF returns one or more candidate instances of NWDAF containing MTLF to the NF consumer and each candidate instance of NWDAF containing MTLF includes the Analytics ID(s), possibly the ML Model Filter Information for the available trained ML Models and ML Model Interoperability indicator, if available.
- If the NWDAF service consumer needs to discover an NWDAF containing an MTLF with ML Model accuracy checking capability, the consumer may query NRF also providing the ML Model accuracy checking capability in the discovery request.
In order to discover an NWDAF containing MTLF with Horizontal Federated Learning (HFL) capability via NRF, in addition to the procedures described above for discovering NWDAF containing MTLF:
- An NWDAF containing MTLF supporting FL as a server shall additionally include FL capability type (i.e. FL server) and may include Time interval supporting FL as FL capability information during the registration in NRF.
- An NWDAF containing MTLF supporting FL as a client shall additionally include FL capability type (i.e. FL client) and may include Time interval supporting FL as FL capability information during the registration in NRF, and it may also include, NF type(s) and NWDAF Serving Area information and/or NF set ID(s) of the data source(s) where data can be collected as input for local model training.
NOTE 6: An NWDAF containing MTLF may indicate to support both FL server and FL client in the FL capability for specific Analytics ID. The FL capability type only applies for HFL to maintain backward compatibility.
- During the discovery of NWDAF containing MTLF as FL server, a consumer (e.g. a NWDAF containing MTLF) may include in the request the FL capability type as FL server and may include Time Period of Interest and ML Model Filter information for the trained ML Model(s) per Analytics ID(s), if available. The NRF returns one or more NF profiles of candidate instances of NWDAF satisfying the query parameters.
- During the discovery of NWDAF containing MTLF as FL client, a consumer (e.g. an FL server) may include in the request FL capability type as FL client and may include Time Period of Interest, a list of NF type(s) and/or NF set ID(s) of the data source(s). The NRF returns one or more NF profiles of candidate instances of NWDAF satisfying the query parameters.
NOTE 7: The service consumer to discover an NWDAF containing MTLF with FL capability is limited to NWDAF containing MTLF in this Release.
A PCF may learn which NWDAFs being used by AMF, SMF and UPF for a specific UE, via signalling described in clause 4.16 of TS 23.502 [3]. This enables a PCF to select the same NWDAF instance that is already being used for a specific UE.
In the roaming architecture, the NWDAF with roaming exchange capability (RE-NWDAF) to request analytics or input data is discovered via the NRF. A consumer in the same PLMN as the RE-NWDAF discovers the RE-NWDAF(s) by querying for NWDAF(s) where the roaming exchange capability is indicated in its (their) NF profile. A consumer in a peer PLMN (i.e. RE-NWDAF) discovers the RE-NWDAF(s) by querying for NWDAF(s) in the target PLMN that is (are) supporting the specific services defined for roaming. A RE-NWDAF discovers the RE-NWDAF(s) in a different PLMN (i.e. HPLMN or VPLMN) using the procedure defined in clause 4.17.5 (if delegated discovery is not used) or clause 4.17.10 (if delegated discovery is used) of TS 23.502 [3], where the detailed parameters are determined based on the analytics request or subscription from the consumer 5GC NF, operator policy, user consent and/or local configuration.
In order to support VFL training and inference, the NWDAF supporting VFL shall include its VFL capability information per supported Analytics ID during registering to NRF. The VFL capability information includes VFL capability type (i.e. VFL server or VFL client or both), VFL client aggregation capability and Time interval supporting VFL if available. For NWDAF as VFL client, NWDAF also includes its VFL interoperability indicator(s) per Analytics ID, optionally with supported feature ID(s) per VFL interoperability indicator and it may also include NF type(s) and NWDAF Serving Area information and/or NF set ID(s) of the data source(s), where data can be collected as input for local model training during registration to NRF. Only NFs (i.e. NWDAF(s) and/or AF(s)) that share the same VFL interoperability indicator can perform VFL together, only NFs sharing same VFL interoperability indicator can understand feature ID(s) and other VFL configurations from each other. Feature ID(s) represent the feature information supported by the NWDAF as VFL client per Analytics ID for VFL process (i.e. VFL training and/or VFL inference).
NOTE 8: VFL client aggregation capability implies that this VFL client can aggregate the intermediate results based on implementation and network deployment.
To discover NWDAF supporting VFL from NRF, the consumer should consider the VFL capability information. To discover NWDAF as VFL client via NRF, the consumer should also consider VFL interoperability indicator(s) and optionally consider Serving Area information and/or NF set ID(s) of the data source(s) and/or feature ID(s). The detailed procedure and parameters of NWDAF registration and discovery for VFL are as defined in clause 6.2H.2.1.
NOTE 9: There are no standardized feature ID in this release, and only feature IDs related to static/preconfigured feature information can be registered to NRF.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 5.3 Horizontal Federated Learning (FL) among multiple NWDAFs
| This clause describes Horizontal Federated Learning.
Federated learning among multiple NWDAFs is a machine learning technique in core network that trains an ML Model across multiple decentralized entities holding local data set, without exchanging/sharing local data set. This approach stands in contrast to centralized machine learning techniques where all the local datasets are uploaded to one server, thus allowing to address critical issues such as data privacy, data security, data access rights.
NOTE 1: Horizontal Federated Learning is supported among multiple NWDAFs, which means the local data set in different FL client NWDAFs have the same feature space for different samples (e.g. UE IDs).
For Federated Learning supported by multiple NWDAFs containing MTLF, there is one NWDAF containing MTLF acting as FL server (called FL server NWDAF for short) and multiple NWDAFs containing MTLF acting as FL client (called FL client NWDAF for short), the main functionality includes:
FL server NWDAF:
- discovers and selects FL client NWDAFs to participant in an FL procedure
- requests FL client NWDAFs to do local model training and to report local model information.
- generates global ML Model by aggregating local model information from FL client NWDAFs.
- sends the global ML Model back to FL client NWDAFs to perform an additional training iteration if needed.
FL client NWDAF:
- locally trains ML Model as tasked by the FL server NWDAF with the available local data set, which includes the data that may not be allowed to be shared with other FL client NWDAFs due to e.g. data privacy, data security, data access rights.
- reports the trained local ML Model information to the FL server NWDAF.
- receives the global ML Model from FL server NWDAF and perform an additional training iteration if needed.
FL server NWDAF or FL client NWDAF register to NRF with their FL capability information as described in clause 5.2.
The NWDAF containing MTLF determines to train an ML Model either based on local configuration or when it receives a request from NWDAF containing AnLF. The NWDAF containing MTLF further determines whether the ML Model should be trained via FL mechanism based on Analytic ID, Service Area/DNAI or when data can not be obtained directly from data producer NF (e.g. due to data privacy, data security). The NWDAF containing AnLF is not aware whether the ML Model is trained based on FL or not.
If the NWDAF containing MTLF can act as an FL server for the ML Model training, then FL procedure is initiated by the NWDAF containing MTLF as FL server NWDAF directly.
If the NWDAF containing MTLF determines to train an ML Model based on local configuration and the FL mechanism is required, but the NWDAF containing MTLF can't act as an FL server, the NWDAF containing MTLF should discover an FL server NWDAF as described in clause 5.2 and request the FL server NWDAF to provide the trained ML Model as described in clause 6.2C.2.2. The FL server NWDAF may determine to initiate FL procedure before providing the ML Model.
If the ML Model training is triggered by the request from NWDAF containing AnLF, the NWDAF containing MTLF determines the FL mechanism is required but it can not act as an FL server, the NWDAF containing MTLF should discover an FL server NWDAF as described in clause 5.2 and request the FL server NWDAF to provide the trained ML Model as described in clause 6.2C.2.2. The Notification Target Address and the Notification Correlation ID from the NWDAF containing AnLF is provided in the request message sent to the FL server NWDAF. The FL server NWDAF may determine to initiate FL procedure before providing the ML Model. The FL server NWDAF sends the ML Model information to the notification endpoint (e.g. the NWDAF containing AnLF) after the ML Model training success.
NOTE 2: The security procedure on authorizating FL server to initiate FL procedure on the FL client(s) is described in Annex X, clause X.9 of TS 33.501 [49]. The security procedure authorizing an MTLF to request ML Models on behalf of an AnLF to another MTLF (e.g., FL server NWDAF) is described in Annex X, clause X.10 of TS 33.501 [49].
Before FL procedure is initiated by FL server NWDAF, appropriate FL client NWDAFs should be discovered by FL server NWDAF as described in clause 5.2.
When starting an FL procedure, the FL server NWDAF is to provide an initial model to each FL client NWDAF, and then each FL client NWDAF is to perform local model training using its local data set. The detailed procedure for FL among Multiple NWDAFs is described in clause 6.2C.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 5.4 Vertical Federated Learning (VFL)
| Vertical Federated learning is a machine learning technique working without exchanging/sharing of local data set, while maintaining some level of coordination amongst VFL participants, i.e. VFL Server and VFL Client, when training and inference are performed on local ML Models, wherein the local data set in different VFL Participant for local model training have different feature spaces for the same samples (e.g. UE IDs). Vertical Federated Learning may involve multiple NWDAFs and AFs.
For Vertical Federated Learning, there may be one NWDAF or one AF acting as a VFL server and one or multiple NWDAF(s) and/or one or multiple AF(s) acting as VFL Client(s). Vertical Federated Learning is available among NWDAFs or between NWDAF(s) and AF(s) within a single PLMN or between an AF and NWDAF(s) in a single PLMN. When AF is acting as VFL Server, NWDAF(s) is VFL Client(s). When NWDAF is acting as VFL server, the VFL Clients can be NWDAF or AF.
The main functionalities of VFL server and VFL client include:
VFL server:
- An NWDAF or trusted AF acting as VFL server discovers and selects VFL client(s) (NWDAF(s) and/or AF(s)) to participate in a VFL procedure.
NOTE 1: When an untrusted AF is acting as VFL server, NEF discovers and selects candidate VFL client NWDAFs, then the AF determines final set of VFL clients.
- It requests VFL clients to do local ML model training for an Analytic ID, it assigns VFL correlation ID, and it requests to report intermediate training results.
- It optionally locally trains ML Model with the available local data set.
- It combines intermediate training results from VFL client(s) and VFL server and computes intermediate model training information (e.g. gradient information, loss information) using label for updating its own local ML Model and sends the intermediate model training information to VFL clients for updating the ML Models of VFL clients that involved in the VFL training process. VFL server may send and receive separate message for each VFL client.
NOTE 2: If VFL server does not have a local ML Model, it only combines intermediate training results from VFL client(s) and computes intermediate model training information which will be sent to the corresponding VFL Clients.
NOTE 3: NEF forwards the message from/to NWDAF to/from untrusted AF.
- It determines to terminate the VFL training process.
- It stores VFL correlation ID and locally trained ML Model after VFL training process.
- It initiates the VFL inference process using VFL correlation ID.
- It combines local inference result from VFL clients and generates the final VFL inference result.
- It may send the final VFL inference result to the consumer.
- It supports to monitor the ML Model metric (e.g. ML Model accuracy) of the VFL training and inference.
VFL client:
- It locally trains ML Model with the available local data set, which includes the data that may not be allowed to be shared with other VFL clients or VFL server due to e.g. data privacy, data security, data access rights.
- It computes the intermediate training results for their local ML Models involved in the VFL training and provide reports with the intermediate training results to the AF or NWDAF acting as VFL server.
- It updates their local ML model based on the intermediate model training information received by the VFL server.
- It stores VFL correlation ID and locally trained ML model after VFL training process.
- It performs inference based on the local model and local data and provides local inference results to VFL server.
Vertical Federated Learning includes the following procedures:
- Registration of the NF profile including a list of VFL related information to NRF. Registration of the NWDAF profile to NRF is described in clause 5.2. Registration of the AF profile to NRF is described in clause 5.5. The procedure for registration and discovery of VFL server and VFL client is described in clause 6.2H.2.1.
- Preparation for VFL including sample alignment to ensure that all the VFL participants have common samples when training ML models as described in clause 6.2H.2.2.
- Training for VFL as described in clause 6.2H.2.3.
- Inference for VFL as described in clause 6.2H.2.4.
In this Release, the same NF associated with a VFL Server or VFL Client capability during the VFL training for a VFL correlation ID is also the same NF during the VFL inference.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 5.5 AF Discovery and Selection for VFL
| The AF discovery and selection is defined in clause 6.3.25 of TS 23.501 [2]. In addition to support VFL training and inference, the following factors may be considered for AF discovery and selection:
- VFL capability information per supported AnalyticsID, which includes:
- VFL capability type (i.e. VFL client and/or optionally VFL server)
- optional Time interval supporting VFL.
- VFL interoperability indicator(s) of AF as VFL client per supported Analytics ID: indicating that a group of certain NFs (i.e. the AF as VFL client and other NWDAF(s) and/or AF(s)) that share the same VFL interoperability indicator, can perform VFL together.
- [Optional] supported feature ID(s): representing the feature information supported by the AF as VFL client.
A trusted AF registers the above factors in NRF. For an untrusted AF the NEF is configured via OAM to register the factors into NRF.
For the discovery of a trusted AF or untrusted AF, the consumer may select an AF instance considering the above factors. The detailed procedure and parameters of AF registration and discovery for VFL are as defined in clause 6.2H.2.1.
5A Data Collection Coordination and Delivery Functional Description
5A.1 General
Data Collection Coordination and Delivery coordinates the collection and distribution of data requested by NF consumers. It prevents data sources from having to handle multiple subscriptions for the same data and send multiple notifications containing the same information due to uncoordinated requests from data consumers.
Data Collection Coordination and Delivery is supported by a DCCF via Ndccf_DataManagement service or by an NWDAF via Nnwdaf_DataManagement service. Unless otherwise stated, capabilities specified in clause 5A for a DCCF are also applicable to an NWDAF.
In this Release of the specification Data Collection Coordination and Delivery is applicable to:
- NWDAFs that request data from a Data Source (e.g. for use in computing analytics).
- NF consumers that request analytics from an NWDAF Data Source.
- NF consumers that request data from an ADRF Data Source.
- ADRFs that receive data from an NF Data Source.
NOTE: Nnwdaf_DataManagement service can be used to collect historical data or runtime data. For collecting historical and runtime analytics, Nnwdaf_AnalyticsSubscription service is used.
5A.2 Data Collection Coordination
Data Collection Coordination is supported by a DCCF or an NWDAF. The Data Consumer may use an NRF to perform NF discovery and selection to find a DCCF that can coordinate data collection (DCCF discovery principles are defined in clause 6.3.19 of TS 23.501 [2]). Data Consumers send requests for data to the DCCF rather than directly to the NF Data Source. Whether the data consumers directly contact the NF Data Source or goes via the DCCF is based on configuration of the data consumers. For the Data Consumer and each notification endpoint in a data request, the Data Consumer may specify Formatting and Processing Instructions that determine how the data is to be provided. Upon receiving a request from a Data Consumer, the selected DCCF determines the NF instance that can be a Data Source if the Data Source is not indicated in the Data Consumer's request. The DCCF may also select an ADRF if the data is to be stored in an ADRF and an ADRF endpoint is not indicated in the Data Consumer's request. To retrieve data for a specific UE, the NRF, UDM or BSF can provide the DCCF with the identity of the Data Source using the services indicated in table 5A.2-1.
Table 5A.2-1: NF Services consumed by DCCF or NWDAF to determine which NF instances are serving a UE
Type of NF instance (serving the UE) to determine
NF to be contacted by DCCF
Service
Reference in TS 23.502 [3]
UDM
NRF
Nnrf_NFDiscovery (NOTE 1)
5.2.7.3
AMF
UDM
Nudm_UECM
5.2.3.2
SMF
UDM
Nudm_UECM
5.2.3.2
BSF
NRF
Nnrf_NFDiscovery (NOTE 1)
5.2.7.3
PCF
BSF
Nbsf_Management
5.2.13.2
NEF
NRF
Nnrf_NFDiscovery
5.2.7.3
NWDAF
NRF
UDM
Nnrf_NFDiscovery
Nudm_UECM
5.2.7.3
5.2.3.2
GMLC
NRF
Nnrf_NFDiscovery (NOTE 2)
5.2.7.3
NSACF
NRF
Nnrf_NFDiscovery
5.2.7.3
NOTE 1: Discovery can be based on a group ID. The group ID for a UE ID can be obtained using the Nudr_GroupIDmap service defined in clause 5.2.12.3 of TS 23.502 [3].
NOTE 2: Discovery of the GMLC serving a UE is described in clause 5.1a of TS 23.273 [39] and can also be based on DNS. A GMLC is supposed to be able to serve any UE in the PLMN; the GMLC will in turn discover an AMF serving the UE via the UDM as described in clause 6.1 of TS 23.273 [39].
The DCCF keeps track of the data actively being collected from the Data Sources it is coordinating. It may do so by maintaining a record of the active prior requests it sends to each Data Source. If a NWDAF subscribes for data directly with a Data Source, or a Data Source has stored data in an ADRF, the NWDAF or ADRF may register the data collection profile with the DCCF. The data collection profile may include the following parameters:
- "Service Operation" identifies the service used to collect the data or analytics from a Data Source (e.g. Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe);
- "Analytics/Data Specification" is the "Service Operation" specific parameters that identify the collected data (i.e. Analytics ID(s) / Event ID (s), Target of Analytics Reporting or Target of Event Reporting, Analytics Filter or Event Filter, etc.);
- NWDAF ID or ADRF ID specifies the ADRF or NWDAF which registers data collection profile.
The DCCF may then determine certain historical data may be available in the NWDAF or ADRF and coordinate collection of data from the NWDAF or ADRF based on the data collection profile.
When the DCCF receives a request for data, it determines the status of data collection from the Data Source. If parameters in a request for data from a Data Consumer match those in a prior request or in a data collection profile registration, the DCCF may determine that the requested data is already being collected from a Data Source or that a prior subscription to a Data Source may be modified to in addition satisfy the requirements of the new data request from a Data Consumer. This status is used in clause 5A.3 to deliver data to the Data Consumer and notification endpoints.
For persisting event exposure subscriptions for long-lived data collection, the DCCF may subscribe to the UDM to receive event notifications even if a Data Source that serves a UE changes.
The DCCF may subscribe to the NRF to receive event notifications if a Data Source changes (e.g. because of a NF life-cycle event).
NOTE: A DCCF can support multiple Data Sources, Data Consumers and Message Frameworks. However, to avoid duplicate data collection, each Data Source NF or Set of Data Source NF should be associated with only one DCCF instance or DCCF Set.
A DCCF may use the same mechanisms described in clause 6.2.2.1 to determine AMF and SMF to retrieve data related to "any UE".
If the data consumer requests to collect data for any UE in an area of interest, the data consumer shall first determine all DCCFs covering the area of interest and then contact these DCCFs to request for data collection.
5A.3 Data Delivery
5A.3.0 General
Data is provided to Consumers or notification endpoints according to the Delivery Option configured on the DCCF or NWDAF. Delivery Options are:
1. Delivery via DCCF or NWDAF: Consumers or Notification Endpoints receive the data from the DCCF or NWDAF.
2. Delivery via Messaging Framework: Consumers or Notification Endpoints receive the data from the Messaging Framework via the services offered by the MFAF.
5A.3.1 Data Delivery via the DCCF or NWDAF
Figure 5A.3.1-1: Data Delivery via DCCF
Data Delivery via DCCF is shown in Figure 5A.3.1-1. Each Event Notification received from a Data Source NF is sent to the DCCF which propagates it to all Data Consumers / Notification Endpoints specified by the Data Consumers or determined by the DCCF. Each Data Consumer may specify in its request to the DCCF multiple notification endpoints, which may include the requesting Data Consumer, an ADRF or other NFs. The DCCF may also select an ADRF or other notification endpoint based on configuration. The DCCF supports formatting and processing for each Consumer / notification endpoint so notifications comply with the data requests received from each Consumer NF.
Upon the DCCF determining the status of data collection for a data request (see clause 5A.2):
- If the requested data is not already being collected from a Data Source, the DCCF sends a new subscription/request towards the Data Source with the notification target specified as the DCCF.
- If the requested data is partially covered by existing subscriptions with the Data Source, the DCCF sends to the existing Data Source a request to modify the subscription and/or creates new subscription(s) to new Data Source for the newly requested data which cannot be provided by the current Data Source.
- If the requested data is already being collected from the Data Source, the DCCF determines that no subscriptions to the Data Source need to be created or modified.
When notifications are received by the DCCF, they are processed according to the Formatting and Processing Instructions for each Consumer and notification endpoint. The DCCF subsequently sends notifications to Consumers and notification endpoints via a Ndccf_DataManagement service.
The same functionality as described above applies for Data Delivery and bulked data collection via NWDAF with Nnwdaf services replacing corresponding Ndccf services.
5A.3.2 Data Delivery via a Messaging Framework
Figure 5A.3.2-1: Data Delivery via a Messaging Framework
Data Delivery via a Messaging Framework is shown in figure 5A.3.2-1. The Messaging Framework formats and processes data received from the Data Source NF and sends notifications to all Data Consumers and Notification Endpoints specified by Data Consumers or determined by the DCCF. Each Data Consumer may specify in its request to the DCCF multiple notification endpoints, which may include the requesting Data Consumer, an ADRF or other NFs. The DCCF may also select an ADRF or other notification endpoint based on configuration. While the Messaging Framework is not standardized by 3GPP, a Messaging Framework Adaptor NF (MFAF) offers 3GPP defined services that allow the 5GS to interact with the Messaging Framework. Internally, the Messaging Framework may for example support the pub-sub pattern, where received data are published to the Messaging Framework and requests from 3GPP Consumers result in Messaging Framework specific subscriptions. Alternatively, the Messaging Framework may support other protocols outside of the scope of 3GPP.
The Messaging Framework Adaptor NF offers services that enable the 5GS to interact with the Messaging Framework:
- 3GPP Consumer Adaptor (3CA) Data Management Service: Nmfaf_3caDataManagement Service delivers data or analytics to each Data Consumer or notification endpoint after formatting and processing of data or analytics received by the Messaging Framework.
- 3GPP DCCF Adaptor (3DA) Data Management Service: The consumer (e.g. DCCF) may configure MFAF using Nmfaf_3daDataManagement service to enable the MFAF to convey data or analytics received from data source NF to notification endpoints. The configuration may include data formatting and processing instruction and notification endpoints.
Upon the DCCF determining the status of data collection for a data request (see clause 5A.2):
- If the requested data is not currently being collected from a Data Source, the DCCF sends a new subscription/request towards the Data Source with the notification target specified as the Messaging Framework.
- If the requested data is partially covered by existing subscriptions with the Data Source, the DCCF sends a request to the Data Source to modify one or more subscriptions to accommodate both the previous requests for data and the new request for data and/or creates new subscription(s) to new Data Source for the newly requested data which cannot be provided by the current Data Source.
- If the requested data is already being collected from the Data Source, the DCCF determines that no subscriptions to the Data Source need to be created or modified.
NOTE: The internal logic of DCCF, e.g. how it decides on what modifications to do, is not specified.
- The DCCF uses the Nmfaf_3daDataManagement service to convey information so:
1. the Messaging Framework can recognize data that are received from a Data Source.
2. the MFAF can obtain data received by the Messaging Framework, process and format the data according to processing and formatting instructions for each Consumer / notification endpoint and send notifications or responses to the Data Consumers.
When data are received by the Messaging Framework (e.g. because of an event notification) they are processed according the Formatting and Processing Instructions for each Consumer / notification endpoint before notifications are sent to the Data Consumer or Notification Endpoints. Notifications sent via the Nmfaf_3caDataManagement service have the same content as those sent via a Ndccf_DataManagement service for Data Delivery via the DCCF.
The same functionality as described above applies for Data Delivery and bulk data collection via NWDAF with Nnwdaf services replacing corresponding Ndccf services.
5A.4 Data Formatting and Processing
Formatting and/or Processing instructions may be provided in requests by Data Consumers via the Ndccf_DataManagement service and Nnwdaf_DataManagement service. As an alternative to providing individual events, formatting can be used to aggregate notifications and processing can be used to extract and send summary information from multiple notifications. Data Formatting and Processing are applicable to notifications due to events as they occur at data sources (runtime data or analytics) and historical data as described in clause 5A.5.
When using the Messaging Framework, the DCCF sends the formatting and/or processing instructions to the Messaging Framework via the Nmfaf_3daDataManagement Service so the MFAF may format and/or process the data before sending notifications to the Data Consumers / notification endpoints. When using Data Delivery via the DCCF, the DCCF performs formatting and/or processing before sending notifications.
Formatting determines when a notification is sent to the Consumer. Formatting Instructions may indicate:
- Notification Event clubbing: Buffering and sending of several notifications in one message. The consumer may specify a minimum and/or maximum number of notifications to be clubbed.
- Notification Time Window (example: notifications are buffered and sent between 2 and 3 AM).
- Cross event reference-based notification: When a subscribing NF is subscribing to multiple events (e.g. event X and event Y) the notification for an Event-X is buffered and reported only when the Event-Y occurs.
- Consumer triggered Notification: Notifications containing data or analytics are buffered until the consumer requests delivery using Nnwdaf_DataManagement, Ndccf_DataManagement or Nmfaf_3caDataManagement Service. The consumer requests Consumer triggered notification by setting a "fetch flag" in its subscription request to the DCCF or NWDAF. When the requested data or analytics is available for retrieval, the DCCF, NWDAF or MFAF sends a notification containing fetch instructions to the consumer. The consumer must then fetch the data or analytics before an expiry time as provided in the fetch instructions.
NOTE: When this indication is set by the consumer, DCCF, NWDAF or MFAF notifications to the consumer contain Fetch Instructions (see clauses 8.2.4, 7.4.4 and 9.3.2).
- Exact time-based Notification: Notifications are sent to the Consumer at an exact time, irrespective of whether the event occurs (example: every 30 min). Exact time-based notifications may be periodic.
- Increasing time window based notification: Notifications are sent to the Consumer at an increasing periodicity (example: the first notification is sent immediately, subsequent received notifications are sent after 5 min, then after 10 min, then after 15 min, etc.).
For an ADRF endpoint, Formatting Instructions sent to the messaging framework may further specify whether Nmfaf services are used to deliver notifications to an ADRF, or whether the data are sent to the ADRF using a Nadrf service.
Processing instructions allow summarizing of notifications to reduce the volume of data reported to the Data Consumer. The processing results in summarizing of information from multiple notifications into a common report. Processing of data for inclusion in each notification sent to consumers occurs over a Processing Interval specified in the Processing Instructions. Notifications sent to consumers may represent partial intervals if formatting instructions or Event Reporting Information (as specified in table 4.15.1-1 of TS 23.502 [3]) require that a notification be sent to the consumer before the end of a processing interval. Processing Instructions are provided per Event ID or Analytics ID and are applied to multiple notifications that result from the same subscription and for the same Event ID or Analytics ID. Processing Instructions, in addition to the Processing Interval, may specify the parameter names, parameter values and the attributes to be determined and reported to the Consumer. Processing Instructions may also specify aggregation level (e.g. per-UEs, per AoIs) or temporal aggregation (e.g. per minute, per hour). The processed notifications may comprise the following depending on the Event and Processing Instructions:
- Event;
- Processing Interval;
- List of Event Parameter Name(s) and for each Event Parameter Name, one Event Parameter Values and sets of the following attributes as indicated in the processing instructions:
- Event Spacing: Average and variance of the time interval separating two consecutive occurrences of the same event and parameter value, or periodicity for periodic reporting;
- Event Duration: Average and variance of the Time for which the parameter value applies;
- Number of countable occurrences for the parameter (e.g. Mobility Registration Update);
- Average, variance, most frequent value, least frequent value and skew of the parameter (e.g.: number of UEs in an AoI);
- Maximum and minimum parameter values (e.g. number of UEs in an AoI).
Event Parameter Names are Event specific and not all attributes are applicable for all parameter names. Examples of Event Parameter Names and Parameter values are provided in table 5A.4-1.
Table 5A.4-1: Examples of Event Parameter Names, Parameter values
Event
Event parameter name
Parameter values
Attributes
Location Report
TAI
TAI-7
- Average and variance of the time interval between TA boundary crossings.
- Number of TA boundary crossing.
Number of UEs in a Region
Region
AMF-3
- Average and variance of the number of UEs in the Region.
UE Reachability (status change)
CM State
Connected
- Average and variance of time between CM connected state transitions.
- Average and variance of the time spent in CM connected state.
- Number of transitions to CM connected state.
PDU Session Establishment
DNN
Internet
- Average and variance of time between PDU Session establishments to the Internet DN.
- Average and variance of the duration of PDU Sessions established to the Internet DN.
- Number of PDU Session establishments to the Internet DN.
PDU Session Establishment
PDU Session Type
Ethernet
- Average and variance of time between Ethernet PDU Session establishments.
- Average and variance of the duration of Ethernet PDU Sessions.
- Number of Ethernet PDU Session establishments.
5A.5 Historical Data Handling
ADRF or NWDAF as a Data Source:
- When the DCCF receives a request for data that includes a period in the past and ADRF is deployed, the DCCF may obtain data from ADRF as the Data Source. The DCCF may also obtain historical data from an NWDAF. The data obtained from the ADRF or NWDAF is delivered to Consumers / Notification Endpoints according to a configured Delivery Option. The DCCF may determine that requested data may be available in an ADRF or NWDAF based on ADRF identification from the consumer, the data collection profile previously registered by the ADRF or NWDAF or by querying the ADRF or NWDAF.
ADRF or NWDAF as a Data Recipient:
- An ADRF or NWDAF may be a Consumer NF that initiates requests to the DCCF for data, the ADRF or NWDAF may be specified as a notification endpoint by another Consumer NF that wants to have data it requests archived, or the DCCF may be configured to archive certain data in a ADRF (e.g. all data from an AMF instance).
- If the ADRF or NWDAF instance is not specified in a request for data by a Consumer NF, the DCCF may select the ADRF or NWDAF instance based on provisioned information or information received from the NRF.
- Data is delivered to the ADRF or NWDAF according to a configured Delivery Option (via DCCF or Messaging Framework).
5B Analytics Data Repository Functional Description
5B.1 General
The ADRF offers services that enable a consumer to store, retrieve and delete data and analytics. The analytics are produced by the NWDAF as described in clause 6.1 and data are collected as described in clause 6.2. Multiple instances of ADRF may be deployed in a network, NF consumer selects a target ADRF instance using ADRF discovery mechanism defined in clause 6.3.20 of TS 23.501 [2].
Data may be stored in the ADRF by:
- a consumer sending the ADRF an Nadrf_DataManagement_StorageRequest containing the data or analytics to be stored. The ADRF response provides a result indication.
- a consumer sending the ADRF an Nadrf_DataManagement_StorageSubscriptionRequest requesting that the ADRF subscribes to receive data or analytics for storage. The ADRF then subscribes to the NWDAF or DCCF for data or analytics, providing ADRF Notification Address (+Notification Correlation ID). Analytics or Data are subsequently provided as notifications using DCCF, NWDAF or MFAF services (Ndccf_DataManagement Nnwdaf_DataManagement or Nmfaf_3caDataManagement service).
Data may be retrieved from the ADRF by:
- a consumer sending an Nadrf_DataManagement_RetrievalRequest request to the ADRF to retrieve data or analytics for a Storage Transaction Identifier or a Fetch Instructions received from the ADRF in an Nadrf_DataManagement_RetrievalNotify. The ADRF determines the availability of the data or analytics in its repository and sends in the response to the consumer either the data or analytics.
- a consumer sending an Nadrf_DataManagement_RetrievalSubscribe request to the ADRF to retrieve data or analytics for a specified data or analytics collection time window. If the time window includes the future and the ADRF has subscribed to receive the data or analytics, subsequent notifications received by the ADRF are sent by the ADRF to the notification endpoint.
The ADRF determines the availability of the data or analytics and sends a success/failure indication in the response to the consumer. The ADRF then sends one or more notifications using an Nadrf_DataManagement_RetrievalNotify to the Notification Address (+Notification Correlation ID) specified by the consumer. The notification(s) either provide the data or analytics or provide instructions to the endpoint to fetch the data or analytics using an Nadrf_DataManagement_RetrievalRequest.
Data may be deleted from the ADRF by:
- a consumer sending an Nadrf_DataManagement_Delete request. The ADRF response provides a result indication.
An ADRF may be configured to register the data it is collecting with a DCCF. The registration uses the Ndccf_ContextManagement service specified in clause 8.3.2. The registration may subsequently be used by the DCCF to obtain data from the ADRF as described in clause 6.2.6.3.6.
The ADRF offers services that enable a consumer to store, delete and retrieve ML Models. The ML Models are trained by NWDAF containing MTLF as described in clause 5.1.
ML Model(s) may be retrieved from the ADRF by:
- a consumer sending the ADRF an Nadrf_MLModelManagement_RetrievalRequest as described in clause 10.3.4, containing one or more tuples of unique ML Model identifier stored in ADRF or Storage Transaction Identifier. The ADRF response provides one or more tuples of unique ML Model identifiers and ML Model file address of ML Model file stored in ADRF.
ML Model(s) may be stored or updated in the ADRF by:
- a consumer sending the ADRF an Nadrf_MLModelManagement_StorageRequest as described in clause 10.3.2, containing the ML Model or ML Model address to be stored or updated. The ADRF response provides a result indication.
NOTE 1: When MTLF updates a model in ADRF, or even in MTLF itself, it could happen that multiple different ML models which are being used in the system have the same model identifier, which may lead to misoperations. It is up to MTLF implementation on how to avoid such situation if that can cause problems. For example, MTLF can only update models that are not provisioned yet.
ML Model(s) may be deleted from the ADRF by:
- a consumer sending an Nadrf_MLModelManagement_Delete request as described in clause 10.3.3. The ADRF response provides a result indication.
When a consumer requests data or analytics to be stored in an ADRF, it may specify Storage Handling information requesting:
- a lifetime indicating how long the data or analytics should be stored; and/or
- that a notification alerting the consumer be sent prior to data deletion from the ADRF.
The ADRF, DCCF or NWDAF may be configured with default operator storage policies. The policies specify how long data or analytics are to be stored and conditions when the default policy supersedes Storage Handling Information provided in a request from the Data or Analytics Consumer. Based on the default operator policy and the Storage Handling information, the ADRF, DCCF or NWDAF determines the Storage Approach that will be applied for the data or analytics.
The Storage Approach is comprised of the lifetime for how long the data or analytics will be stored and the notification requirement to be applied when data or analytics are to be deleted from the ADRF.
When more than one consumer requests a storage lifetime for the same data or analytics, the Storage Approach should be based on the longest requested storage lifetime.
The response to the consumer request for data or analytics includes the Storage Approach.
NOTE 2: The default operator policy for how long data or analytics are to be stored may be longer or shorter than the lifetime requested by the consumer. A default operator policy may for example accept only consumer requested lifetimes that are shorter or longer than the default policy.
The ADRF, DCCF or NWDAF determines when the data or analytics lifetime has expired. When data or analytics is to be removed from the ADRF, an alert is sent to the Consumer that the data is about to be deleted. The alert contains a Storage Transaction Identifier that can be used by the consumer to retrieve the data or analytics.
5C Analytics/ML Model Accuracy Monitoring Functional Description
5C.1 General
A NWDAF may have the accuracy checking capability for Analytics and/or ML Models. The NWDAF may provide the accuracy information to consumers when requested or use it for its internal processes.
Input data is collected from Data Producer NF(s) when there is a request for inference/prediction per analytics ID in NWDAF for a specific time period in future. Ground truth data are collected from those Data Producer NF corresponding to the requested analytic ID at the time to which the prediction refers.
The ground truth data is the actual measured data observed at the time which the prediction refers to.
NOTE 1: The ground truth data can be impacted when Analytics Feedback Information shows that an action is triggered by the analytics output in the consumer.
Analytics/ML Model Accuracy Monitoring is to be achieved by comparing the predictions using the current trained ML Model and its corresponding ground truth data i.e. the corresponding true observed events.
Analytics/ML Model Accuracy Information is to represent general performance measurements for analytics and ML Model respectively, which includes accuracy value and optionally the corresponding number of samples. The accuracy value is computed as the number of correct predictions divided by the total number of predictions.
NOTE 2: In this Release, only Analytics/ML Model Accuracy Information is supported for monitoring the performance of Analytics/ML Model.
NOTE 3: How an MTLF/AnLF determines whether a prediction is correct is up to implementation.
The NWDAF (containing AnLF) with accuracy checking capability decides to initiate Analytics Accuracy Monitoring based on:
- A request from an analytics accuracy consumer. The analytics accuracy consumer may be an NWDAF containing AnLF, NWDAF containing MTLF or an analytics consumer NF.
- Analytics Feedback Information which may be provided by an Analytics Consumer NF.
The AnLF with analytics accuracy checking capability as defined in clause 6.2D is able to provide or notify the accuracy information of Analytics IDs to the analytics consumers of such service and when the analytics accuracy does not meet the analytics consumer's requirements, the analytics consumer may stop using analytics for a period of time or obtain new analytics. In addition, updated analytics for the provided Analytics IDs may be provided to analytics consumers as requested, if the updated analytics is able to be generated within the correction time period. The AnLF with analytics accuracy checking capability is as defined in clause 6.2D.1 is able to determine Analytics Accuracy Information based on e.g.:
- Comparing predictions and its corresponding ground truth data, which are collected corresponding to the requested analytic ID at the time which the prediction refers to.
NOTE 4: The ground truth data and the corresponding prediction is to be defined per Analytics ID.
- Comparing changes in internal configuration for the analytics ID generation (e.g. change of data collection parameters, change in data distribution from a Data Source).
- Previous existent records of Analytics Accuracy Information.
- Analytics Feedback Information provided by an NF consumer.
- Determining analytics accuracy by comparing analytics accuracy using multiple ML Models that serve the same Analytics ID.
The MTLF with ML Model accuracy checking capability as defined in clause 6.2E is able to determine ML Model degradation based on e.g.:
- comparing/evaluating the data: including input data, analytics output and the ground truth data either collected from various data source NFs, DCCF, AnLF, ADRF or configured by OAM; or
- AnLF providing notifications of the Analytics Accuracy Information; or
- AnLF providing Analytics Feedback Information of the analytics generated by the ML Model.
The NWDAF containing MTLF may reselect a new ML Model or retrain the existing ML Model and consequently notify the ML Model accuracy degradation to the ML Model consumer(s). In addition, the NWDAF containing MTLF may consider the rating of untrusted AF(s) when used as data sources.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6 Procedures to Support Network Data Analytics
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.0 General
| This clause specifies procedures to support network data analytics function.
Clause 6.1 and clause 6.2 specify generic procedures which apply to all type of analytics, while clause 6.3 and onwards specify procedures specific to some type of analytics.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1 Procedures for analytics exposure
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.1 Analytics Subscribe/Unsubscribe
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.1.1 Analytics subscribe/unsubscribe by NWDAF service consumer
| This procedure is used by any NWDAF service consumer (e.g. including NFs/OAM) to subscribe/unsubscribe at NWDAF to be notified on analytics information, using Nnwdaf_AnalyticsSubscription service defined in clause 7.2. This service is also used by an NWDAF service consumer to modify existing analytics subscription(s). Any entity can consume this service as defined in clause 7.2.
Figure 6.1.1.1-1: Network data analytics Subscribe/unsubscribe
1. The NWDAF service consumer subscribes to or cancels subscription to analytics information by invoking the Nnwdaf_AnalyticsSubscription_Subscribe/ Nnwdaf_AnalyticsSubscription_Unsubscribe service operation. The parameters that can be provided by the NWDAF service consumer are listed in clause 6.1.3.
When a subscription to analytics information is received, the NWDAF determines whether triggering new data collection is needed.
If the service invocation is for a subscription modification, the NF service consumer includes an identifier (Subscription Correlation ID) to be modified in the invocation of Nnwdaf_AnalyticsSubscription_Subscribe. In addition, if the NWDAF service consumer has taken an action(s) influenced by the previously received analytics information at step 2, which may or may not affect the ground truth data corresponding to Analytics ID requested at the time which the prediction refers to, the NWDAF service consumer may include Analytics Feedback Information in the invocation of Nnwdaf_AnalyticsSubscription_Subscribe.
If the subscription relates to outbound roaming users, the NWDAF in the HPLMN may decide to retrieve or to subscribe to input data or analytics from the VPLMN and the detailed procedure is described in clause 6.1.5.3 for analytics retrieval and in clause 6.2.10 for data retrieval.
If the subscription relates to inbound roaming users, the NWDAF in the VPLMN may decide to retrieve or to subscribe to input data or analytics from the HPLMN and the detailed procedure is described in clause 6.1.5.2 for analytics retrieval and in clause 6.2.11 for data retrieval.
2. If NWDAF service consumer is subscribed to analytics information, the NWDAF notifies the NWDAF service consumer with the analytics information by invoking Nnwdaf_AnalyticsSubscription_Notify service operation, based on the request from the NWDAF service consumer, e.g. Analytics Reporting Parameters. If the NWDAF provides a Termination Request, then the consumer cancels subscription to analytics information by invoking the Nnwdaf_AnalyticsSubscription_Unsubscribe service operation.
When calculating the analytics/ML Model Accuracy Information with the retrieved Analytics Feedback Information, in addition to comparing predictions of ML Model and its corresponding ground truth data, the NWDAF may additionally determine/take into account whether the action(s) taken by the NWDAF service consumer affects the ground truth data corresponding to Analytics ID requested at the time which the prediction refers to as described in clauses 6.2D and 6.2E, which may affect the ML Model Accuracy Monitoring/Analytics Accuracy Monitoring.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.1.2 Analytics subscribe/unsubscribe by AFs via NEF
| The analytics exposure to AFs may be performed via NEF by using analytics subscription to NWDAF.
Figure 6.1.1.2-1 illustrates the interaction between AF and NWDAF performed via the NEF.
Figure 6.1.1.2-1: Procedure for analytics subscribe/unsubscribe by AFs via NEF
0. NEF controls the analytics exposure mapping among the AF identifier with allowed Analytics ID and associated inbound restrictions (i.e. applied to subscription of the Analytics ID for an AF) and/or outbound restrictions (i.e. applied to notification of Analytics ID to an AF).
In this Release, AF is configured with the appropriated NEF to subscribe to analytics information, the allowed Analytics ID(s) and with allowed inbound restrictions (i.e. parameters and/or parameter values) for subscription to each Analytics ID.
1. The AF subscribes to or cancels subscription to analytics information via NEF by invoking the Nnef_AnalyticsExposure_Subscribe/ Nnef_AnalyticsExposure_Unsubscribe service operation defined in TS 23.502 [3]. If the AF wants to modify an existing analytics subscription at NEF, it includes an identifier (Subscription Correlation ID) to be modified in the invocation of Nnef_AnalyticsExposure_Subscribe, in addition, if the AF has taken an action(s) influenced by the previously received analytics information at step 4, which may or may not affect the ground truth data corresponding to Analytics ID requested at the time which the prediction refers to, the AF may include Analytics Feedback Information in the invocation of Nnef_AnalyticsExposure_Subscribe. If the analytics information subscription is authorized by the NEF, the NEF proceeds with the steps below.
2. Based on the request from the AF, the NEF subscribes to or cancels subscription to analytics information by invoking the Nnwdaf_AnalyticsSubscription_Subscribe/ Nnwdaf_AnalyticsSubscription_Unsubscribe service operation.
If the parameters and/or parameters values of the AF request comply with the inbound restriction in the analytics exposure mapping, NEF forwards in the subscription to NWDAF service the Analytics ID, parameters and/or parameters values from the AF request.
If the request from AF does not comply with the restrictions in the analytics exposure mapping, NEF may apply restrictions to the subscription request to NWDAF (e.g. restrictions to parameters or parameter values of the Nnwdaf_AnalyticsSubscription_Subscribe service operations), based on operator configuration and/or may apply parameter mapping (e.g. geo coordinate mapping to TA(s)/Cell-id(s)).
The NEF records the association of the analytics request from the AF and the analytics request sent to the NWDAF.
The NEF selects an NWDAF that supports analytics information requested by the AF using the NWDAF discovery procedure defined in TS 23.502 [3].
If the subscription relates to outbound roaming users, the NWDAF in the HPLMN may decide to retrieve or to subscribe to input data or analytics from the VPLMN and the detailed procedure is described in clause 6.1.5.3 for analytics retrieval and in clause 6.2.10 for data retrieval.
If the AF request is for a modification of the existing analytics subscription(s), the NEF invokes Nnwdaf_AnalyticsSubscription_Subscribe to modify the analytics subscription identified by an identifier (Subscription Correlation ID) associated with the AF.
3. If the NEF has subscribed to analytics information, the NWDAF notifies the NEF with the analytics information or Termination Request by invoking Nnwdaf_AnalyticsSubscription_Notify service operation.
4. If the NEF receives the notification from the NWDAF, the NEF notifies the AF with the analytics information or Termination Request by invoking Nnef_AnalyticsExposure_Notify service operation defined in TS 23.502 [3]. NEF may apply outbound restrictions to the notifications to AFs (e.g. restrictions to parameters or parameter values of the Nnef_AnalyticsExposure_Notify service operation) based on analytics exposure mapping and may apply parameter mapping for external usage (e.g. TA(s), cell ID(s) to geo coordinate). The AF checks if a Termination Request is present in the Nnef_AnalyticsExposure_Notify as defined in step 2 in clause 6.1.1.1.
When calculating the analytics/ML Model Accuracy Information with the retrieved Analytics Feedback Information, in addition to comparing predictions of ML Model and its corresponding ground truth data, the NWDAF may determine/take into account whether the action(s) taken by the AF, when AF provides Analytics Feedback Information, affects the ground truth data corresponding to Analytics ID requested at the time which the prediction refers to or start rating AF(s) used as data sources, as described in clauses 6.2D, 6.2E and 6.2.13, which may affect the ML Model Accuracy Monitoring/Analytics Accuracy Monitoring.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.2 Analytics Request
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.2.1 Analytics request by NWDAF service consumer
| This procedure is used by the NWDAF service consumer (e.g. including NFs/OAM) to request and get from NWDAF analytics information, using Nnwdaf_AnalyticsInfo service defined in clause 7.3.
Figure 6.1.2.1-1: Network data analytics Request
1. The NWDAF service consumer requests analytics information by invoking Nnwdaf_AnalyticsInfo_Request service operation. The parameters that can be provided by the NWDAF service consumer are listed in clause 6.1.3.
When a request for analytics information is received, the NWDAF determines whether triggering new data collection is needed.
If the analytics request relates to outbound roaming users, the NWDAF in the HPLMN may decide to retrieve input data or analytics from the related VPLMN and the detailed procedure is described in clause 6.1.5.3 for analytics retrieval and in clause 6.2.10 for data retrieval.
If the analytics request relates to inbound roaming users, the NWDAF in the VPLMN may decide to retrieve input data or analytics, from the related HPLMN and the detailed procedure is described in clause 6.1.5.2 for analytics retrieval and in clause 6.2.11 for data retrieval.
2. The NWDAF responds with analytics information to the NWDAF service consumer. The NWDAF checks if a Termination Request is indicated as defined in step 2 in clause 6.1.1.1.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.2.2 Analytics request by AFs via NEF
| The analytics exposure to AFs may be performed via NEF by using analytics request to NWDAF.
Figure 6.1.2.2-1 illustrates the interaction between AF and NWDAF performed via the NEF.
Figure 6.1.2.2-1: Procedure for analytics request by AFs via NEF
0. NEF controls the analytics exposure mapping among the AF identifier with allowed Analytics ID(s) and associated inbound restrictions (i.e. applied to the Analytics ID requested by AF) and/or outbound restrictions (i.e. applied to the response of Analytics ID to AF).
In this Release, AF is configured, e.g. via static OAM configuration, with the appropriated NEF to subscribe to analytics information, the allowed Analytics ID(s) and with allowed inbound restrictions (i.e. parameters and/or parameter values) for requesting each Analytics ID.
1. The AF requests to receive analytics information via NEF by invoking the Nnef_AnalyticsExposure_Fetch service operation defined in TS 23.502 [3]. If the analytics information request is authorized by the NEF, the NEF proceeds with the steps below.
2. Based on the request from the AF, the NEF requests analytics information by invoking the Nnwdaf_AnalyticsInfo_Request service operation.
If the parameters and/or parameters values of the AF request comply with the restriction in the analytics exposure mapping, NEF forwards in the subscription to NWDAF service the Analytics ID, parameters and/or parameters values from AF in the request to NWDAF.
If the request from AF does not comply with the restrictions in the analytics exposure mapping, NEF may apply restrictions to the request to NWDAF (e.g. restrictions to parameters or parameter values of the Nnwdaf_AnalyticsInfo_Request service operations) based on operator configuration and/or may apply parameter mapping (e.g. geo coordinate mapping to TA(s), Cell-id(s)).
The NEF records the association of the analytics request from the AF and the analytics request sent to the NWDAF.
The NEF selects an NWDAF that supports analytics information requested by the AF using the NWDAF discovery procedure defined in TS 23.501 [2].
If the analytics request relates to outbound roaming users, the NWDAF in the HPLMN may decide to retrieve input data or analytics from the related VPLMN and the detailed procedure is described in clause 6.1.5.3 for analytics retrieval and in clause 6.2.10 for data retrieval.
3. The NWDAF responds with the analytics information to the NEF.
4. The NEF responds with the analytics information to the AF. NEF may apply restrictions to the response to AFs (e.g. restrictions to parameters or parameter values of the Nnef_AnalyticsExposure_Fetch response service operation) based on operator configuration. The AF checks if a Termination Request is present and then follows as defined in step 2 in clause 6.1.1.1.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.3 Contents of Analytics Exposure
| The consumers of the Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request service operations described in clause 7 provide the input parameters listed below.
- A list of Analytics IDs: identifies the requested analytics.
- Analytics Filter Information: indicates the conditions to be fulfilled for reporting Analytics Information. This set of optional parameter types and values enables to select which type of analytics information is requested. Analytics Filter Information is defined in the analytics related clauses.
- Target of Analytics Reporting: indicates the object(s) for which Analytics information is requested, entities such as specific list of UEs, i.e. a list of SUPIs, group of UEs, i.e. a list of Internal-Group-Ids, or any UE (i.e. all UEs).
- (Only for Nnwdaf_AnalyticsSubscription_Subscribe) A Notification Target Address (+ Notification Correlation ID) as defined in clause 4.15.1 of TS 23.502 [3], allowing to correlate notifications received from NWDAF with this subscription.
- (Only for Nnwdaf_AnalyticsSubscription_Subscribe) Subscription Correlation ID: identifies an existing analytics subscription that is to be modified.
- Related to analytic consumers that aggregate analytics from multiple NWDAF subscriptions:
- [OPTIONAL] (Set of) NWDAF identifiers of NWDAF instances used by the NWDAF service consumer when aggregating multiple analytics subscriptions. See clause 6.1A.
- Analytics Reporting Information with the following parameters:
- (Only for Nnwdaf_AnalyticsSubscription_Subscribe) Analytics Reporting Parameters as per Event Reporting parameters defined in Table 4.15.1-1 of TS 23.502 [3].
NOTE 1: When the Analytics Reporting Parameters indicates a periodic reporting mode and the periodicity of the report is equal to or greater than the Supported Analytics Delay associated with the Analytics ID (if available) defined in clause 6.2.6.2 of TS 23.501 [2], it is expected that the periodic reporting can be provided by the NWDAF as requested.
- (Only for Nnwdaf_AnalyticsSubscription_Subscribe) Reporting Thresholds, which indicate conditions on the level of each requested analytics that when reached shall be notified by the NWDAF.
- [OPTIONAL] Matching direction: A matching direction may be provided such as below, above, or crossed. If no matching direction is provided, the default direction is crossed.
- [OPTIONAL] Acceptable deviation: An acceptable deviation from the threshold level in the non-critical direction (i.e. in which the QoS is improving) may be set to limit the amount of signalling.
- Analytics target period: time interval [start..end], either in the past (both start time and end time in the past) or in the future (both start time and end time in the future). An Analytics target period in the past is a request or subscription for statistics. An Analytics target period in the future is a request or subscription for predictions. The time interval is expressed with actual start time and actual end time (e.g. via UTC time). When the Analytics Reporting Parameters indicate a periodic reporting mode, the time interval can also be expressed as positive or negative offsets to the reporting time, which indicates a subscription for predictions or statistics respectively. By setting start time and end time to the same value, the consumer of the analytics can request analytics or subscribe to analytics for a specific time rather than for a time interval.
- Time window for historical analytics: time interval [start..end]. The time window for historical analytics indicates the time interval during which the historical analytics was generated. If the time window for historical analytics is included, the NWDAF only needs to provide the existing analytics, and does not need to generate new analytics.
- [OPTIONAL] Data time window: if specified, only events that have been created in the specified time interval are considered for the analytics generation.
- [OPTIONAL] Preferred level of accuracy of the analytics ("Low", "Medium", "High" or "Highest").
- [OPTIONAL] Preferred level of accuracy per analytics subset ("Low", "Medium", "High" or "Highest"). When a preferred level of accuracy is expressed for a given analytics subset, it takes precedence for this subset over the above preferred level of accuracy of the analytics. Analytics subsets are defined in the "Output Analytics" clause of applicable analytics.
- [OPTIONAL] Dataset Statistical Properties: information in order to influence the data selection mechanisms to be used for the generation of an Analytics ID, assuring that the generated Analytics ID reflects the statistical characteristics of the data that are relevant for the NWDAF consumer. The following dataset statistical properties are allowed:
- Uniformly distributed datasets, which indicates the use of data samples that are uniformly distributed according to the different aspects of the requested analytics (e.g. equivalent data samples for each UE listed as a Target of Analytics Reporting or for S-NSSAIs included in the Analytics Filter Information).
- Datasets with or without outliers, which indicates that the data samples shall consider or disregard data samples that are at the extreme boundaries of the value range.
- Time when analytics information is needed (if applicable): indicates to the NWDAF the latest time the analytics consumer expects to receive analytics data provided by the NWDAF. It should not be set to a value less than the Supported Analytics Delay of the selected NWDAF if applicable. If the time is reached the consumer does not need to wait for the analytics information any longer, yet the NWDAF may send an error response or error notification to the consumer. "Time when analytics information is needed" is a relative time interval as the gap with respect to analytics request /subscription (e.g. "in 10 minutes").
NOTE 2: If the analytics request contains the parameter "Time when analytics information is needed" for Analytics ID(s), this parameter takes precedence over the requested periodicity, if a periodic reporting mode is requested.
NOTE 3: If the Time when analytics information is needed is provided and it is less than the Supported Analytics Delay per Analytics ID (if available) defined in clause 6.2.6.2 of TS 23.501 [2], it is expected that the NWDAF might not be able to treat the Analytics ID on time.
- [OPTIONAL] Maximum number of objects requested by the consumer (max) to limit the number of objects in a list of analytics per Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request response.
- [OPTIONAL] Preferred granularity of location information: "TA level", "cell level" or "longitude and latitude level".
NOTE 4: As defined in clause 4 of TS 23.032 [34], longitude and latitude level means the location information is expressed as longitude and latitude in geographical coordinate instead of TA ID or cell ID that is only known in 3GPP system. It also stands for the location information that is expressed as a reference point in local co-ordinate.
- [OPTIONAL] Spatial granularity size: maximum number of TA or cells used to define an area for which analytics are provided. When this parameter is provided, the NWDAF should provide analytics per group of TA of cells accordingly.
- [OPTIONAL] Temporal granularity size: minimum duration of each time slot for which analytics are provide. When this parameter is provided, the NWDAF should provide analytics per elementary time slot accordingly.
NOTE 5: It is up to NWDAF implementation to determine whether the data is taken into account that the UE locates in an area for a shorter time than the Temporal granularity size.
- [OPTIONAL] Preferred orientation of location information: ("horizontal", "vertical", "both").
- [OPTIONAL] Preferred order of results when a list of analytics is returned, possibly with a criterion for identifying the property of the results to which the preferred ordering is applied.
- [OPTIONAL] Maximum number of SUPIs (SUPImax) requested by the consumer to limit the number of SUPIs in an object. When SUPImax is not provided, the NWDAF shall return all SUPIs concerned by the analytics object. When SUPImax is set to 0, the NWDAF shall not provide any SUPI.
- [OPTIONAL] Output strategy: indicates the relevant factors for determining when the analytics reported. The following values are allowed:
- Binary output strategy: indicates that the analytics shall only be reported when the preferred level of accuracy is reached within a cycle of periodic notification as defined in the Analytics Reporting Parameters.
NOTE 6: If preferred level of accuracy is more important than providing an output, then the binary strategy is used so that all analytics outputs have equivalent confidence in the prediction.
- Gradient output strategy: indicates that the analytics shall be reported according to the periodicity defined in the Analytics Reporting Parameters irrespective if the preferred level of accuracy has been reached.
NOTE 7: If having an analytics output is more important than reaching the preferred level of accuracy, then the gradient output strategy is used so that each NWDAF will timely provide the output indicating the confidence of the prediction at the moment of the output generation.
NOTE 8: When no output strategy is included in the subscription, the analytics output will be generated based on the gradient strategy and includes the confidence of the prediction for the reporting period.
- [OPTIONAL] Analytics metadata request: indicates a request from one NWDAF to another NWDAF to provide the "analytics metadata information" related to the produced output analytics. This input parameter indicates which parameters in "analytics metadata information" are required to aggregate the output analytics for the requested Analytics ID(s).
- (Only for Nnwdaf_AnalyticsSubscription_Subscribe) Consumer NF's serving area or NF ID. During a pending analytics subscription transfer, this information can be used by the NWDAF to find out if the analytics consumers may change as described in clause 6.1B.2.
- (Only for Nnwdaf_AnalyticsSubscription_Subscribe) Information of previous analytics subscription. When setting up the analytics generation, this information may be used to retrieve analytics context from the previous NWDAF in order to build upon the context that is already related to this subscription as described in clause 6.1B.2.1.
- [OPTIONAL] Use case context: indicates the context of use of the analytics to select the most relevant ML Model.
NOTE 9: The NWDAF can use the parameter "Use case context" to select the most relevant ML Model, when several ML Models are available for the requested Analytics ID(s). NWDAF containing AnLF can additionally provide the parameter "Use case context" when requesting an ML Model from an NWDAF containing MTLF. The values of this parameter are not standardized. For example, the AMF can use a given value of "Use case context" when requesting UE Mobility analytics for optimizing the definition of a Registration Area, and a different value of "Use case context" when requesting UE Mobility analytics for determines a paging strategy.
- (Only for Nnwdaf_AnalyticsSubscription_Subscribe) [OPTIONAL] Analytics Feedback Information: indicates that the consumer NF has taken an action(s) influenced by the previously provided analytics, which may or may not affect the ground truth data corresponding to analytic ID requested at the time which the prediction refers to, and consequently affect the Analytics Accuracy Monitoring and/or ML Model Accuracy Monitoring by the subscription with following parameter(s):
- Corresponding Analytics ID(s) which has been used for taking an action(s);
- Indication whether the action will affect ground truth data (if available);
- Time stamp(s) of the action(s) taken.
NOTE 10: The consumer NF cannot include Analytics Feedback Information in initial subscription request. Analytics Feedback Information can be included in modification request for the existing analytics subscription.
- [OPTIONAL] Analytics Accuracy Request information with the following parameters:
- Analytics accuracy request: indicates NWDAF to provide accuracy information to the analytics consumer.
- [OPTIONAL] Analytics Accuracy Information time window: time interval [start. end], which indicates that analytics consumers only consider the accuracy information which is generated within this time interval.
- [OPTIONAL] Analytics Accuracy Information periodicity: time period, which indicates periodic reporting of accuracy information for the corresponding Analytics ID(s).
- [OPTIONAL] Analytics Accuracy threshold: a reporting threshold accuracy value, which indicates that:
- The NWDAF can provide analytics output and optionally analytics accuracy value to the analytics consumer(s) when the accuracy value is above this Analytics Accuracy threshold (i.e. the accuracy is sufficient according to the threshold);
- The NWDAF can provide "Stop Analytics Output Consumption indication", "Updated Analytics" or the Analytics Accuracy Information to the analytics consumer(s) when the accuracy value is under this threshold (This indicates the deviation of the predictions from the actual network data does not meet analytics accuracy requirement, i.e. the accuracy is not sufficient according to the threshold).
- [OPTIONAL] Minimal number of analytics output occurrences: determines the minimal number of analytics outputs provided by NWDAF that have to be considered in the determination of the accuracy information.
- [OPTIONAL] Updated Analytics flag: indicates that the NWDAF can provide updated analytics for provided Analytics ID(s), if updated analytics can be generated within Analytics Accuracy Information time window.
- [OPTIONAL] Correction time period: a relative time interval as the gap with respect to analytics is provided, which is indicated the time interval during which the updated analytics can be accepted by the analytics consumer.
- [OPTIONAL] Pause analytics consumption flag: is a flag indicating to NWDAF to stop sending the notifications of analytics outputs for a subscribed analytics ID, without unsubscribing to such analytics ID.
- [OPTIONAL] Resume Analytics Subscription request: is a flag indicating to NWDAF to resume the notification of analytics outputs for an existing analytics ID(s) subscription(s) that have been previously paused.
- [OPTIONAL] For Analytics ID set to "QoS and Policy Assistance", QoS parameter set(s) and corresponding value(s), optionally a requested QoE, as described in clause 6.23.
The NWDAF provides to the consumer of the Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request service operations described in clause 7, the output information listed below, using a Nnwdaf_AnalyticsSubscription_Notify service operation or the Nnwdaf_AnalyticsInfo_Request response, respectively:
- (Only for Nnwdaf_AnalyticsSubscription_Notify) The Notification Correlation Information.
- For each Analytics ID, the analytics information in the requested Analytics target period. If the analytics subset is subscribed or requested, then the corresponding analytics information shall be provided.
- Timestamp of analytics generation: allows consumers to decide until when the received information shall be used. For instance, an NF can deem a received notification from NWDAF for a given feedback as invalid based on this timestamp;
- Validity period: defines the time period for which the analytics information is valid.
NOTE 11: Validity period is determined by NWDAF internal logic and it is a subset of Analytics target period.
- Confidence: probability assertion, i.e. confidence in the prediction.
- [OPTIONAL] For each Analytics ID the Termination Request, which notifies the consumer that the subscription is requested to be cancelled as the NWDAF can no longer serve this subscription, e.g. due to user consent revoked, NWDAF overload, UE moved out of NWDAF serving area, etc.
- [OPTIONAL] Analytics metadata information: additional information required to aggregate the output analytics for the requested Analytics ID(s). This parameter shall be provided if the "Analytics metadata request" parameter was provided in the corresponding Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request service operation.
- Number of data samples used for the generation of the output analytics;
- Data time window of the data samples;
- Dataset Statistical Properties of the analytics output used for the generation of the analytics;
- [OPTIONAL] Data source(s) of the data used for the generation of the output analytics;
- [OPTIONAL] Data Processing, if applied on the data collected for the generation of the output analytics;
NOTE 12: This parameter is provided if the NWDAF provided Processing instructions when collecting data via Ndccf_DataManagement service or Nnwdaf_DataManagement service, as defined in clause 5A.4.
- Output strategy (i.e. gradient output strategy or binary output strategy) used for the reporting of the analytics.
- (Only for error response or error notification) Revised waiting time: indicates to the consumer a revised waiting value for "Time when analytics information is needed". Each NWDAF may include this as part of error response or error notification to "Time when analytics information is needed" as described in clause 6.2.5. Revised waiting time is the minimum time interval recommended by NWDAF to use as "Time when analytics information is needed" for similar future analytics requests/subscriptions.
- [OPTIONAL] Analytics Accuracy Information generated for each analytics ID, including:
- Analytics accuracy value for requested Analytics ID(s): a value shall be provided if "Analytics accuracy request" parameter was provided in the corresponding Nnwdaf_AnalyticsSubscription_Subscribe service operation. This parameter may be provided if the value crosses the analytics accuracy threshold(s) which is indicated in the subscribe request or locally configured, or the Analytics Accuracy Information periodicity indicated in the subscribe request is reached.
- [OPTIONAL] An indication that the determined accuracy value for the analytics ID does not meet the analytics accuracy threshold requested for the analytics ID.
- [OPTIONAL] Updated Analytics: NWDAF provides updated Analytics, which is generated within Analytics Accuracy Information time window, for provided Analytics ID(s), if "Updated Analytics flag" parameter was indicated in the corresponding Nnwdaf_AnalyticsSubscription_Subscribe service operation.
- [OPTIONAL] Stop Analytics Output Consumption indication: NWDAF provides to the consumer an indication to stop the consumption of the Analytics ID(s) related to the subscription ID based on NWDAF internal logic or specified analytics accuracy threshold.
- [OPTIONAL] Stop Analytics Output Consumption time window: NWDAF provides to the consumer a time window to stop the consumption of the Analytics ID(s) related to the subscription ID based on NWDAF internal logic or specified analytics accuracy threshold.
- [OPTIONAL] Resume Analytics Output Consumption indication: NWDAF provides to consumer an indication to resume the consumption of analytics output for existing subscription to the analytics ID(s) that was previously paused.
- [OPTIONAL] Accuracy Information Termination: NWDAF notifies the consumer that the subscription to the accuracy information for an analytics ID has been cancelled as the NWDAF does not support the accuracy checking capability, e.g. as an indication that a new target serving NWDAF supporting accuracy checking capability could not have been selected during the analytics transfer procedures.
NOTE 13: It is left to Stage 3 to decide whether the Accuracy Information Termination is a cause related to the Termination Request or not.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.4 Analytics Exposure using DCCF
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.4.1 General
| This clause specifies procedures for analytics exposure using DCCF services, with two options: analytics can be exposed via DCCF, according to clauses 6.1.4.2 and 6.1.4.3, or can be exposed via a messaging framework according to clauses 6.1.4.4 and 6.1.4.5. Which option to use is determined by DCCF configuration.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.4.2 Analytics Exposure via DCCF
| The procedure as depicted in Figure 6.1.4.2-1 is used by analytics consumer(s) (e.g. NFs/OAM) to subscribe/unsubscribe to NWDAF analytics and be notified of analytics information via the DCCF, using Ndccf_DataManagement_Subscribe service operation. Whether a NWDAF service consumer directly contacts the NWDAF or goes via the DCCF is based on NWDAF service consumer configuration.
Figure 6.1.4.2-1: Network data analytics subscription via DCCF
1. Analytics consumer subscribes to analytics information via DCCF by invoking the Ndccf_DataManagement_Subscribe (Nnwdaf service operation, Analytics Specification, Formatting Instructions, Processing Instructions, NWDAF (or NWDAF-Set) ID, ADRF Information) service operation. The analytics consumer may specify one or more notification endpoints. Analytics consumer decides to go via DCCF based on internal configuration. The "Analytics Specification" provides Nnwdaf service operation specific parameters, e.g. Analytics IDs, Target of Analytics Reporting and optional parameters used to retrieve the analytics. The analytics consumer may provide the identity of the NWDAF to collect analytics from. The analytics consumer may provide additional information on possible notification endpoints or ADRF information so analytics are archived.
2. If the NWDAF instance or NWDAF Set is not identified by the analytics Consumer, the DCCF determines the NWDAF instances that can provide analytics. If the consumer requested storage of analytics in an ADRF but an ADRF ID is not provided by the Analytics Consumer, or the collected analytics is to be stored in an ADRF according to configuration on the DCCF, the DCCF selects an ADRF to store the collected data.
3. The DCCF determines whether the analytics requested in step 1 are already being collected. If the requested analytics are already being collected by an Analytics Consumer, the DCCF adds the new analytics consumer to the list of analytics consumers that are subscribed for these analytics.
4. If the analytics subscribed in step 1 partially matches an analytics that is already being collected by the DCCF from an NWDAF and a modification of this subscription to the NWDAF would satisfy both the existing analytics subscriptions as well as the newly requested analytics, the DCCF invokes a modification of the previous subscription via Nnwdaf_AnalyticsSubscription_Subscribe service operation (as specified in clause 6.1.1.1) and the DCCF adds the analytics consumer to the list of analytics consumers that are subscribed for these analytics.
If the analytics requested at step 1 are not already available or not being collected yet, the DCCF subscribes to analytics from NWDAF using the Nnwdaf_AnalyticsSubscription_Subscribe procedure as specified in clause 6.1.1.1. The DCCF adds the analytics consumer to the list of analytics consumers that are subscribed for these analytics.
5. When new output analytics are available, the NWDAF notifies the analytics information to the DCCF by invoking Nnwdaf_AnalyticsSubscription_Notify service operation.
6. The DCCF uses Ndccf_DataManagement_Notify to send the analytics to all notification endpoints indicated in step 1. Analytics sent to notification endpoints may be processed and formatted by the DCCF so they conform to delivery requirements for each analytics consumer or notification endpoint as specified in clause 5A.4. The DCCF may store the analytics in the ADRF if requested by the consumer or if required by DCCF configuration, using procedure as specified in clause 6.2B.3.
NOTE: According to Formatting Instructions provided by the Analytics Consumer, multiple notifications from a NWDAF can be combined in a single Ndccf_DataManagement_Notify so many notifications from an NWDAF results in fewer notifications (or one notification) to the Analytics Consumer. Alternatively, a notification can instruct the analytics notification endpoint to fetch the analytics from the DCCF.
7. If a Ndccf_DataManagement_Notify contains a fetch instruction, the notification endpoint sends a Ndccf_DataManagement_Fetch request to fetch the analytics from the DCCF before an expiry time.
8. The DCCF delivers the analytics to the notification endpoint.
9. When the Analytics Consumer no longer wants analytics to be collected it invokes Ndccf_DataManagement_Unsubscribe (Subscription Correlation ID), using the Subscription Correlation ID received in response to its subscription in step 1. The DCCF removes the analytics consumer from the list of analytics consumers that are subscribed for these analytics.
10. If there are no other Analytics Consumers subscribed to the analytics, the DCCF unsubscribes with the NWDAF.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.4.3 Historical Analytics Exposure via DCCF
| The procedure as depicted in Figure 6.1.4.3-1 is used by an analytics consumer (e.g. NFs/OAM) to obtain historical analytics via the DCCF. Historical analytics may be previously computed statistics or predictions stored in an NWDAF or ADRF. Statistics may have been previously computed and stored in the ADRF or NWDAF and can be identified by a "target period" in the past (see clause 6.1.3). Requests for previously computed predictions have a "Time Window", which specifies an allowable span for when the predictions may have been computed. This allows the Analytics Consumer to request previously computed predictions for a target period.
The analytics consumer requests analytics via the DCCF, using Ndccf_DataManagement_Subscribe service operation. Whether the NWDAF service consumer directly contacts the NWDAF/ADRF or goes via the DCCF is based on configuration.
Figure 6.1.4.3-1: Historical Analytics Exposure via DCCF
1. The analytics consumer requests analytics via DCCF by invoking the Ndccf_DataManagement_Subscribe (Nnwdaf service operation, Analytics Specification, Time Window, Formatting Instructions, Processing Instructions, ADRF ID or NWDAF ID (or ADRF Set ID or NWDAF Set ID) service operation as specified in clause 8.2.2. The analytics consumer may specify one or more notification endpoints to receive the analytics.
Parameter "Nnwdaf service operation" is the service operation used to originally acquire the analytics and identifies this as a request for analytics, "Analytics Specification" provides Nnwdaf service operation specific parameters, e.g. Analytics IDs, Target of Analytics Reporting and optional parameters used to retrieve the analytics. "Time Window" specifies a past time period and comprises a start and stop time indicating when predictions were computed and "Formatting and Processing Instructions" are as defined in clause 5A.4. The analytics consumer may optionally include the ADRF or NWDAF instance (or ADRF Set or NWDAF Set) ID where the stored analytics resides.
2. If an ADRF or NWDAF instance or ADRF or NWDAF Set ID is not provided by the analytics consumer, the DCCF determines if any ADRF or NWDAF instances might provide the analytics as described in clause 5A and clause 5B.
3. (conditional) If the DCCF determines that an ADRF instance might provide the analytics, or an ADRF instance or Set was supplied by the analytics consumer, the DCCF sends a request to the ADRF, using Nadrf_DataManagement_RetrievalSubscribe (Analytics Specification, Notification Target Address=DCCF) service operation, as specified in clause 10.2. The ADRF responds to the DCCF with an Nadrf_DataManagement_RetrievalSubscribe response indicating if the ADRF can supply the analytics. If the analytics can be provided, the procedure continues with step 5.
4. (conditional) If the DCCF determines that an NWDAF instance might provide the analytics or an NWDAF instance or Set was supplied by the Analytics Consumer, the DCCF sends a request to the NWDAF using Nnwdaf_AnalyticsSubscription_Subscribe as specified in clause 7.2.2.
5. The ADRF uses Nadrf_DataManagement_RetrievalNotify or the NWDAF uses Nnwdaf_AnalyticsSubscription_Notify to send the requested analytics (e.g. one or more stored notifications archived from an NWDAF) to the DCCF. The analytics may be sent in one or more notification messages.
6. The DCCF uses Ndccf_DataManagement_Notify to send analytics to all notification endpoints indicated in step 1. Notifications are sent to the Notification Target Address(es) using the Analytics Consumer Notification Correlation ID(s) received in step 1. Analytics sent to notification endpoints may be processed and formatted by the DCCF, so they conform to delivery requirements specified by the analytics consumer.
NOTE: According to Formatting Instructions provided by the analytics consumer, multiple notifications from an ADRF or NWDAF can be combined in a single Ndccf_DataManagement_Notify so many notifications from the ADRF or NWDAF results in fewer notifications (or one notification) to the Analytics Consumer. Alternatively, a Ndccf_DataManagement_Notify can instruct the analytics notification endpoint to fetch the analytics from the DCCF before an expiry time.
7. If a notification contains a fetch instruction, the notification endpoint sends a Ndccf_DataManagement_Fetch request as specified in clause 8.2.5 to fetch the analytics from the DCCF.
8. The DCCF delivers the analytics to the notification endpoint.
9. When the analytics consumer no longer wants analytics to be collected or has received all the analytics it needs, it invokes Ndccf_DataManagement_Unsubscribe (Subscription Correlation ID), using the Subscription Correlation Id received in response to its subscription in step 1.
10. If the analytics are being provided by an ADRF and there are no other analytics consumers subscribed to the analytics, the DCCF unsubscribes with the ADRF using Nadrf_DataManagement_RetrievalUnsubscribe as specified in clause 10.2.7.
11. If the analytics are being provided by an NWDAF and there are no other analytics consumers subscribed to the analytics, the DCCF unsubscribes with the NWDAF using Nnwdaf_AnalyticsSubscription_Unsubscribe service operation as specified in clause 7.2.3.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.4.4 Analytics Exposure via Messaging Framework
| The procedure as depicted in Figure 6.1.4.4-1 is used by analytics consumer(s) (e.g. NFs/OAM) to subscribe/unsubscribe to NWDAF analytics and be notified of analytics information, using Ndccf_DataManagement_Subscribe service operation. The 3GPP DCCF Adaptor (3da) Data Management service and 3GPP Consumer Adaptor (3ca) Data Management service of the Messaging Framework Adaptor Function (MFAF) are used to interact with the 3GPP Network and the Messaging Framework. Whether a NWDAF service consumer directly contacts the NWDAF or goes via the DCCF is based on NWDAF service consumer configuration.
Figure 6.1.4.4-1: Network data analytics subscription via DCCF
1. Analytics consumer subscribes to analytics information via DCCF by invoking the Ndccf_DataManagement_Subscribe (Nnwdaf service operation, Analytics Specification, Formatting Instructions, Processing Instructions, NWDAF (or NWDAF-Set) ID, ADRF Information, Analytics Consumer Notification Target Address (+ Notification Correlation ID)) service operation. The analytics consumer may specify one or more notification endpoints. Analytics consumer decides to go via DCCF based on internal configuration. The "Analytics Specification" provides Nnwdaf service operation specific parameters, e.g. Analytics IDs, Target of Analytics Reporting and optional parameters used to retrieve the analytics. The analytics consumer may provide the identity of the NWDAF to collect analytics from. The analytics consumer may provide additional information on possible notification endpoints or ADRF information to archive analytics.
2. If the NWDAF instance or NWDAF Set is not identified by the analytics consumer, the DCCF determines the NWDAF instances that can provide analytics. If the consumer requested storage of analytics in an ADRF but an ADRF ID is not provided by the Analytics Consumer, or the collected analytics is to be stored in an ADRF according to configuration on the DCCF, the DCCF selects an ADRF to store the collected analytics.
3. The DCCF determines whether the analytics requested in step 1 are already being collected. If the requested analytics are already being collected by an analytics consumer, the DCCF adds the new analytics consumer to the list of analytics consumers that are subscribed for these analytics.
4. The DCCF sends an Nmfaf_3daDataManagement_Configure (Analytics Consumer Information, MFAF Notification Information, Formatting Conditions, Processing Instructions) to configure the MFAF to map notifications received from the NWDAF to outgoing notifications sent to endpoints and to instruct the MFAF how to format and process the outgoing notifications.
"Analytics Consumer Information" contains for each notification endpoint, the analytics consumer Notification Target Address (+ Analytics Consumer Notification Correlation ID) to be used by the MFAF when sending notifications in step 7.
"MFAF Notification Information" is included if an NWDAF is already sending the analytics to the MFAF. MFAF Notification Information identifies Event Notifications received from the NWDAF and comprises the MFAF Notification Target Address (+ MFAF Notification Correlation ID). If the MFAF does not receive MFAF Notification information from the DCCF, the MFAF selects an MFAF Notification Target Address (+ MFAF Notification Correlation ID) and sends the MFAF Notification Information, containing the MFAF Notification Target Address (+ MFAF Notification Correlation ID), to the DCCF in the Nmfaf_3daDataManagement_Configure Response.
5. If the analytics subscribed in step 1 partially matches analytics that are already being collected by the DCCF from a NWDAF and a modification of this subscription to the NWDAF would satisfy both the existing analytics subscriptions as well as the newly requested analytics, the DCCF invokes Nnwdaf_AnalyticsSubscription_Subscribe (Subscription Correlation ID) with parameters indicating how to modify the previous subscription (as specified in clause 6.1.1.1). The DCCF adds the analytics consumer to the list of analytics consumers that are subscribed for these analytics.
If the analytics requested at step 1 are not already available or not being collected yet, the DCCF subscribes to analytics from the NF using Nnwdaf_AnalyticsSubscription_Subscribe, setting the Notification Target Address (+Notification Correlation ID)) to the MFAF Notification Target Address (+ MFAF Notification Correlation ID) received in step 4. The DCCF adds the analytics consumer to the list of analytics consumers that are subscribed for these analytics.
6. When new output analytics are available, the NWDAF uses Nnwdaf_AnalyticsSubscription_Notify to send the analytics to the MFAF. The Notification includes the MFAF Notification Correlation ID.
7. The MFAF uses Nmfaf_3caDataManagement_Notify to send the analytic to all notification endpoints indicated in step 4. Notifications are sent to the Notification Target Address(es) using the Analytics Consumer Notification Correlation ID(s) received in step 4. Analytics sent to notification endpoints may be processed and formatted by the MFAF, so they conform to delivery requirements specified by the analytics consumer. The MFAF may store the information in the ADRF if requested by consumer or if required by DCCF configuration, using procedure as specified in clause 6.2B.3.
NOTE: According to Formatting Instructions provided by the Analytics Consumer, multiple notifications from a NWDAF can be combined in a single Nmfaf_3caDataManagement_Notify, so many notifications from the NWDAF results in fewer notifications (or one notification) to the analytics consumer. Alternatively, a notification can instruct the analytics notification endpoint to fetch the analytics from the MFAF before an expiry time.
8. If a Nmfaf_3caDataManagement_Notify contains a fetch instruction, the notification endpoint sends a Nmfaf_3caDataManagement_Fetch request to fetch the analytics from the MFAF.
9. The MFAF delivers the analytics to the notification endpoint.
10. When the analytics consumer no longer wants analytics to be collected, it invokes Ndccf_DataManagement_Unsubscribe (Subscription Correlation ID), using the Subscription Correlation Id received in response to its subscription in step 1. The DCCF removes the analytics consumer from the list of analytics consumers that are subscribed for these analytics.
11. If there are no other analytics consumers subscribed to the analytics, the DCCF unsubscribes with the NWDAF.
12. The DCCF de-configures the MFAF so it no longer maps notifications received from the NWDAF to the notification endpoints configured in step 4.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.4.5 Historical Analytics Exposure via Messaging Framework
| The procedure as depicted in Figure 6.1.4.5-1 is used by an analytics consumer (e.g. NFs/OAM) to obtain historical analytics via the messaging framework. Historical analytics may be previously computed statistics or predictions stored in an NWDAF or ADRF. Statistics may be previously computed and stored in the ADRF or NWDAF and can be identified by a "target period" in the past (see clause 6.1.3). Requests for previously computed predictions have a "Time Window", which specifies an allowable span for when the predictions may have been computed. This allows the analytics consumer to request previously computed predictions for a target period.
The analytics consumer requests analytics via the DCCF, using Ndccf_DataManagement_Request service operation. Whether the NWDAF service consumer directly contacts the NWDAF/ADRF, or goes via the DCCF is based on configuration.
Figure 6.1.4.5-1: Historical Analytics Exposure via Messaging Framework
1. The analytics consumer requests analytics via DCCF by invoking the Ndccf_DataManagement_Subscribe (Nnwdaf service operation, Analytics Specification, Time Window, Formatting Instructions, Processing Instructions, ADRF ID or NWDAF ID (or ADRF Set ID or NWDAF Set ID)). The analytics consumer may specify one or more notification endpoints to receive the analytics.
2. If an ADRF or NWDAF instance or ADRF or NWDAF Set ID is not provided by the Analytics Consumer, the DCCF determines if any ADRF or NWDAF instances might provide the analytics as described in clause 5A and clause 5B.
3. The DCCF sends an Nmfaf_3daDataManagement_Configure (Analytics Consumer Information, Formatting Conditions, Processing Instructions) to configure the MFAF to map notifications received from the ADRF or NWDAF to outgoing notifications sent to endpoints and to instruct the MFAF how to format and process the outgoing notifications.
"Analytics Consumer Information" contains for each notification endpoint, the analytics consumer Notification Target Address (+ Analytics Consumer Notification Correlation ID) to be used by the MFAF when sending notifications. The MFAF selects an MFAF Notification Target Address (+ MFAF Notification Correlation ID) and sends the MFAF Notification Information, containing the MFAF Notification Target Address (+ MFAF Notification Correlation ID), to the DCCF in the Nmfaf_3daDataManagement_Configure Response.
4. (conditional) If the DCCF determines that an ADRF instance might provide the analytics, or an ADRF instance or Set was supplied by the Analytics Consumer, the DCCF sends a request to the ADRF, using Nadrf_DataManagement_RetrievalSubscribe (Analytics Specification, MFAF Notification Information) as specified in clause 10.2.6. The MFAF Notification information contains the MFAF Notification Target Address (+ MFAF Notification Correlation ID) received in step 3.
5. The ADRF responds to the DCCF with an Nadrf_DataManagement_RetrievalSubscribe response indicating if the ADRF can supply the analytics. If the analytics can be provided, the procedure continues with step 8.
6. (conditional) If the DCCF determines that an NWDAF instance might provide the analytics or an NWDAF instance or Set was supplied by the Analytics Consumer, the DCCF sends a request to the NWDAF using Nnwdaf_AnalyticsSubscription_Subscribe as specified in clause 7.2.2. The MFAF Notification Information contains the MFAF Notification Target Address (+ MFAF Notification Correlation ID) received in step 3.
7. The NWDAF responds to the DCCF with an Nnwdaf_AnalyticsSubscription_Subscribe response indicating if the NWDAF can supply the analytics.
8. The ADRF uses Nadrf_DataManagement_RetrievalNotify or the NWDAF uses Nnwdaf_AnalyticsSubscription_Notify to send the requested analytics (e.g. one or more stored notifications archived from an NWDAF) to the MFAF. The analytics may be sent in one or more notification messages.
9. The MFAF uses Nmfaf_3caDataManagement_Notify to send analytics to all notification endpoints indicated in step 3. Notifications are sent to the Notification Target Address(es) using the Analytics Consumer Notification Correlation ID(s) received in step 3. Analytics sent to notification endpoints may be processed and formatted by the DCCF, so they conform to delivery requirements specified by the analytics consumer.
NOTE: According to Formatting Instructions provided by the Analytics Consumer, multiple notifications from an ADRF or NWDAF can be combined in a single Ndccf_DataManagement_Notify so many notifications from the ADRF or NWDAF results in fewer notifications (or one notification) to the Analytics Consumer. Alternatively, a Nmfaf_3caDataManagement_Notify can instruct the analytics notification endpoint to fetch the analytics from the DCCF before an expiry time.
10. If a notification contains a fetch instruction, the notification endpoint sends a Nmfaf_3caDataManagement_Fetch request as specified in clause 9.3.3 to fetch the analytics from the MFAF.
11. The DCCF delivers the analytics to the notification endpoint.
12. When the analytics consumer no longer wants analytics to be collected or has received all the analytics it needs, it invokes Ndccf_DataManagement_Unsubscribe (Subscription Correlation ID) as specified in clause 8.2.3, using the Subscription Correlation Id received in response to its subscription in step 1.
13. If the analytics are being provided by an ADRF and there are no other analytics consumers subscribed to the analytics, the DCCF invokes Nadrf_DataManagement_RetrievalUnsubscribe as specified in clause 10.2.7 to unsubscribe from the ADRF.
14. If the analytics are being provided by an NWDAF and there are no other analytics consumers subscribed to the analytics, the DCCF invokes Nnwdaf_AnalyticsSubscription_Unsubscribe service operation as specified in clause 7.2.3 to unsubscribe from the NWDAF
15. The DCCF de-configures the MFAF so it no longer maps notifications received from the NWDAF to the notification endpoints configured in step 3.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.5 Analytics Exposure in Roaming Case
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.5.1 General
| Based on roaming agreements (e.g. SLA), analytics may be exchanged between PLMNs (i.e. HPLMN and VPLMN of a UE served by the NWDAF analytics consumer). In this case, an NWDAF with roaming exchange capability (RE-NWDAF) is used as entry point in a PLMN to exchange analytics in roaming scenario with other PLMNs. It authorizes the analytics request according to roaming agreements, and filters the information exposed to other PLMNs. The roaming architecture is defined in clause 4.3.
The H-RE-NWDAF may provide analytics to the V-RE-NWDAF. The V-RE-NWDAF may provide analytics to the H-RE-NWDAF.
NOTE 1: The roaming agreements (e.g. SLA) between HPLMN and VPLMN on network analytics and data exchange takes into consideration all relevant regulatory requirements.
NOTE 2: It depends on the deployment whether analytics exchange between PLMNs is supported, and thus whether H-RE-NWDAF and V-RE-NWDAF are provided in a PLMN.
The H-RE-NWDAF or V-RE-NWDAF provides the Nnwdaf_RoamingAnalytics service for that purpose. An RE-NWDAF is the only consumer of these services, i.e. both NWDAF in HPLMN and NWDAF in VPLMN need to have the roaming exchange capability (in other words, be an H-RE-NWDAF or V-RE-NWDAF, respectively) when used as entry point or exit point to exchange analytics in roaming scenario.
NOTE 3: The access to the Nnwdaf_AnalyticsSubscription service and the Nnwdaf_AnalyticsInfo service is expected to be restricted by the NRF to NF service consumers within the same PLMN to prevent bypassing checks based on user consent and operator policy
NOTE 4: See clause X.7 and Annex V of TS 33.501 [49] for details of the user consent check procedures. See clause X.8 of TS 33.501 [49] for protection of analytics exchange in roaming case.
V-RE-NWDAF may request or subscribe to HPLMN analytics from the H-RE-NWDAF as described in clause 6.1.5.2, and then the analytics can be leveraged by the 5GC NF in the VPLMN, for example:
- In home routed roaming scenarios, HPLMN analytics (i.e. slice load level analytics, NF load analytics, etc.) can be leveraged by the AMF in the VPLMN for network slice selection and SMF selection for PDU Session management.
- UE-related analytics (e.g.. service experience analytics, etc.) can include statistics or predictions for outbound roaming UEs.
NOTE 5: Analytics that rely on input data from the VPLMN are preferably not provided from H-RE-NWDAF to V-RE-NWDAF, but generated by a NWDAF in the VPLMN.
H-RE-NWDAF may request or subscribe to VPLMN analytics from the V-RE-NWDAF as described in clause 6.1.5.3, and then the analytics can be leveraged by the 5GC NF in the HPLMN, for example:
- In home routed roaming scenarios, analytics information with statistics or predictions for outbound roaming UEs can be leveraged by the H-PCF for QoS control of the PDU Session.
- Analytics (i.e. service experience analytics, slice load level analytics, etc.) can be leveraged by the H-PCF for decision of NSSP in URSP rules provisioned to the UE roaming in the VPLMN.
NOTE 6: Analytics that rely on input data from the HPLMN are preferably not provided from V-RE-NWDAF to H-RE-NWDAF, but generated by a NWDAF in the HPLMN.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.5.2 Analytics Exposure from HPLMN to VPLMN
| Figure 6.1.5.2-1 shows the procedure where a V-RE-NWDAF requests network analytics (i.e. slice load level analytics, NF load analytics, service experience analytics, etc.) in HPLMN from a H-RE-NWDAF, upon receiving an analytics information request/subscribe from a service consumer NF (e.g. AMF) in the VPLMN.
Figure 6.1.5.2-1: Procedure for analytics exposure from HPLMN to VPLMN
1a. The Consumer NF in VPLMN (e.g. AMF) discovers a V-RE-NWDAF as described in clause 5.2 and sends an Analytics request/subscribe (Analytics ID, Analytics Filter Information, Target of Analytics Reporting) to the V-RE-NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request service operation or a Nnwdaf_AnalyticsSubscription_Subscribe service operation.
1b. For the inbound roaming UE(s) indicated in the Target of Analytics Reporting:
- The V-RE-NWDAF determines based on operator configuration and the requested analytics whether analytics or input data from the HPLMN are required, or the analytics can be derived locally. The subsequent steps only apply if analytics from the HPLMN are required. If input data from the HPLMN are required, the procedures in clause 6.2.11 apply.
NOTE 1: It is possible that the Target of Analytics Reporting sent by the Consumer NF to the V-RE-NWDAF includes both inbound roaming UE(s) and non-roaming UE(s).
-. V-RE-NWDAF checks the roaming agreements related to analytics from the HPLMN to determine if the roaming analytics request/subscribe can be accepted or must be rejected with a proper cause in the response to the Consumer NF. If the V-RE-NWDAF determined the roaming analytics request/subscribe is rejected, the following steps are skipped.
2. The V-RE-NWDAF discovers a H-RE-NWDAF as described in clause 5.2 if the V-RE-NWDAF determines the roaming analytics request/subscribe can be accepted. The V-RE-NWDAF sends a roaming analytics request/subscribe (Analytics ID, Analytics Filter Information, Target of Analytics Reporting) to H-RE-NWDAF by invoking a Nnwdaf_RoamingAnalytics_Request service operation or a Nnwdaf_RoamingAnalytics_Subscribe service operation, based on the Analytics request/subscribe received from the Consumer NF in the VPLMN. The Target of Analytics Reporting sent by the V-RE-NWDAF to the H-RE-NWDAF only contains the inbound roaming UE(s).
NOTE 2: The inbound roaming UE(s) are distinguished by the V-RE-NWDAF according to the UE ID(s) (i.e. SUPI(s)).
3a. The H-RE-NWDAF checks the roaming agreements between the HPLMN and the VPLMN, and user consent for analytics as defined in clause 6.2.9 if needed, to determine if the roaming analytics request/subscribe can be accepted or must be rejected with a proper cause in response to the V-RE-NWDAF (which then relays the response to the Consumer NF). If the roaming analytics request/subscribe is rejected, the following steps are skipped.
If the H-RE-NWDAF supports to generate the requested analytics, it collects data from the NF(s) and/or OAM in the HPLMN and derives the requested analytics; otherwise steps 3b and 3c are executed.
NOTE 3: See clause X.7 and Annex V of TS 33.501 [49] for details of the user consent check procedures. See clause X.8 of TS 33.501 [49] for protection of analytics exchange in roaming case.
3b-3c. [Optional] If the H-RE-NWDAF does not support to generate the requested analytics, it may request/subscribe to other NWDAF(s) in the HPLMN (if available) for the analytics and get corresponding response/notification.
4. The H-RE-NWDAF sends the HPLMN analytics information to the V-RE-NWDAF using either Nnwdaf_RoamingAnalytics_Request response or Nnwdaf_RoamingAnalytics_Notify service operation, depending on the service used in step 2. The H-RE-NWDAF may restrict the exposed analytics information based on HPLMN operator polices.
5. [Optional] If the Consumer NF also indicates request or subscription of analytics information available in the VPLMN (e.g. via Target of Analytics Reporting) in step 1, the V-RE-NWDAF collects data from the NF(s) and/or OAM in VPLMN and derives the requested analytics. These steps can be executed in parallel with steps 3-4. The V-RE-NWDAF may perform analytics aggregation with the analytics information received from the H-RE-NWDAF and analytics information generated by itself, based on the analytics request or subscription.
6. The V-RE-NWDAF sends the HPLMN analytics information received in step 4, or the aggregated analytics information if step 5 are performed, to the Consumer NF in the VPLMN using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify service operation, depending on the service used in step 1.
NOTE 4: The present document describes that the RE-NWDAF can perform analytics aggregation for roaming scenario, but whether and how the RE-NWDAF performs analytics aggregation for roaming scenario are up to implementation.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.5.3 Analytics Exposure from VPLMN to HPLMN
| Figure 6.1.5.3-1 shows the procedure that the H-RE-NWDAF requests network analytics (i.e. service experience analytics, slice load level analytics, etc.) in the VPLMN from the V-RE-NWDAF, upon receiving an analytics information request/subscription from the service consumer NF (e.g. PCF) in HPLMN.
Figure 6.1.5.3-1: Procedure for analytics exposure from VPLMN to HPLMN
1a. If the Consumer NF in the HPLMN (e.g. H-PCF) is aware that the UE(s) indicated in Target of Analytics Reporting is/are outbound roaming UE(s), the Consumer NF discovers a H-RE-NWDAF as described in clause 5.2 and sends an Analytics request/subscribe (Analytics ID, Target of Analytics Reporting, Analytics Filter Information) to the H-RE-NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request service operation or a Nnwdaf_AnalyticsSubscription_Subscribe service operation.
1b. For the outbound roaming UE(s) indicated in the Target of Analytics Reporting:
- The H-RE-NWDAF determines based on operator configuration and the requested analytics whether analytics or input data from the VPLMN are required, or the analytics can be derived locally. The subsequent steps only apply if analytics from the VPLMN are required. If input data from the VPLMN are required, the procedures in clause 6.2.10 apply.
- If the Consumer NF is unaware that the Target of Analytics Reporting includes roaming UE(s) and sends the Analytics request/subscribe to a H-NWDAF which does not support roaming exchange capability, then the H-NWDAF may perform either of the following after determining that the Target of Analytics Reporting includes roaming UE(s) (e.g. by inquiring the AMF(s) serving the UE(s) at the UDM with the Nudm_UECM service):
- forward the Analytics request/subscribe to a H-RE-NWDAF after discovering a H-RE-NWDAF as described in clause 5.2. The H-NWDAF may include the VPLMN ID in the Analytics request/subscribe; or
- reject the Analytics request/subscribe with a proper cause value in the response to the Consumer NF. And the following steps will not be performed.
NOTE 1: It is possible that the Target of Analytics Reporting sent by the Consumer NF to the H-RE-NWDAF includes both outbound roaming UE(s) and non-roaming UE(s).
NOTE 2: The H-NWDAF is not depicted in the flow.
- If PLMN ID of the VPLMN is not included in the Analytics request/subscribe, the H-NWDAF inquires it at the UDM for the UE(s) indicated as Target of Analytics Reporting. The H-RE-NWDAF checks user consent for analytics as defined in clause 6.2.9. The H-RE-NWDAF checks the roaming agreements between the HPLMN and the VPLMN to determine if the roaming analytics request/subscription can be accepted or must be rejected with a proper cause in the response to the Consumer NF. If the H-RE-NWDAF determined the roaming analytics request/subscribe is rejected, the following steps are skipped.
NOTE 3: See clause X.7 and Annex V of TS 33.501 [49] for details of the user consent check procedures. See clause X.8 of TS 33.501 [49] for protection of analytics exchange in roaming case.
2. The H-RE-NWDAF discovers the V-RE-NWDAF as described in clause 5.2 if the H-RE-NWDAF determined the roaming analytics request/subscribe can be accepted. The H-RE-NWDAF sends a roaming analytics request/subscribe (Analytics ID, Analytics Filter Information, Target of Analytics Reporting, [NF ID(s)]) to the V-RE-NWDAF by invoking a Nnwdaf_RoamingAnalytics_Request service operation or a Nnwdaf_RoamingAnalytics_Subscribe service operation, based on the Analytics request/subscribe received from the Consumer NF in HPLMN. The Target of Analytics Reporting sent by the H-RE-NWDAF to the V-RE-NWDAF only contains the outbound roaming user(s). The H-RE-NWDAF may obtain NF ID(s) of the NF(s) serving the roaming UE(s) in the VPLMN, e.g. AMF ID(s), SMF ID(s), from the UDM and include the NF ID(s) in the analytics request/subscribe.
3a. The V-RE-NWDAF checks the roaming agreements between the HPLMN and the VPLMN, to determine if the roaming analytics request/subscribe can be accepted or must be rejected with a proper cause in response to the H-RE-NWDAF (which then relays the response to the Consumer NF). If the roaming analytics request/subscribe is rejected, the following steps are skipped.
If the V-RE-NWDAF supports to generate the requested analytics, it collects data from the NF(s) serving the roaming UE(s) and/or OAM in VPLMN and derives the analytics; otherwise step 3b and step 3c are executed. The NF(s) serving the roaming UE(s), e.g. AMF(s) or SMF(s), if indicated in step 2, can be used as data source.
3b-3c. [Optional] If the V-RE-NWDAF does not support to generate the requested analytics, it may request/subscribe to other NWDAF(s) in the VPLMN (if available) for the analytics and get corresponding response/notification(s).
4. The V-RE-NWDAF sends the VPLMN analytics information to the H-RE-NWDAF using either Nnwdaf_RoamingAnalytics_Request response or Nnwdaf_RoamingAnalytics_Notify service operation, depending on the service used in step 2. The V-RE-NWDAF may restrict the exposed analytics information based on VPLMN operator polices.
5. [Optional] If the Consumer NF also indicates request or subscription of analytics information available in the HPLMN (e.g. via Target of Analytics Reporting) in step 1, the H-RE-NWDAF collects data from the NF(s) and/or OAM in HPLMN and derives the analytics. These steps can be executed in parallel with steps 3-4. The H-RE-NWDAF may perform analytics aggregation with the analytics information received from the V-RE-NWDAF and analytics information generated by itself, based on the analytics request or subscription.
6. The H-RE-NWDAF sends the VPLMN analytics information received in step 4, or the aggregated analytics information if step 5 are performed, to the Consumer NF in HPLMN using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
If the Analytics request/subscribe is forwarded to the H-RE-NWDAF by a H-NWDAF as described in step 1, the H-NWDAF forwards the analytics information received from the H-RE-NWDAF to the Consumer NF using either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 1.
NOTE 4: The present document describes that the RE-NWDAF may perform analytics aggregation for roaming scenario, but whether and how the RE-NWDAF performs analytics aggregation for roaming scenario are up to implementation.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.1.5.4 Contents of Analytics Exposure in roaming case
| When requesting or subscribing to analytics involving one or more roaming UEs, the Consumer NF shall send the request or subscription to an RE-NWDAF belonging to the same PLMN as the Consumer NF. The Consumer NF may indicate the following parameters in the Nnwdaf_AnalyticsInfo_Request service operation or the Nnwdaf_AnalyticsSubscription_Subscribe service operation:
- The parameters as defined in clause 6.1.3, with the following differences:
- Parameters related to analytics aggregation, analytics transfer or ML Model selection should not be included;
- If Target of Analytics Reporting is included and indicates specific UE(s) or a group of UEs, these UEs shall belong to the same HPLMN (if HPLMN analytics are subscribed/requested) or be served by the same VPLMN (if VPLMN analytics are subscribed/requested)
- Additionally, the following parameters:
- If the NWDAF service consumer in a VPLMN requests/subscribes to HPLMN analytics, in Analytics Filter Information:
- [OPTIONAL] PLMN ID of the HPLMN;
NOTE 1: If PLMN ID of the HPLMN is not provided by the NWDAF service consumer, the V-RE-NWDAF derives it from the SUPIs of UEs indicated as Target of Analytics Reporting.
- [OPTIONAL] mapped S-NSSAI of the HPLMN.
- [OPTIONAL] AOI (in the form of geographical area) in the HPLMN
- If the NWDAF service consumer in a HPLMN requests/subscribes to VPLMN analytics, in Analytics Filter Information:
- [OPTIONAL] PLMN ID of the VPLMN
- [OPTIONAL] AOI (in the form of geographical area) in the VPLMN
NOTE 2: If PLMN ID of the VPLMN is not provided by the NWDAF service consumer, the H-RE-NWDAF inquires it at the UDM for the UEs indicated as Target of Analytics Reporting.
NOTE 3: In this release of the specification, only one PLMN ID (of HPLMN or VPLMN) is supported in the Nnwdaf_AnalyticsInfo_Request service operation or the Nnwdaf_AnalyticsSubscription_Subscribe service operation.
Based on the analytics request or subscription from the NWDAF service consumer in the HPLMN, and local configuration, the H-RE-NWDAF may indicate the following parameters in the Nnwdaf_RoamingAnalytics_Request service operation or the Nnwdaf_RoamingAnalytics_Subscribe service operation to the V-RE-NWDAF, for requesting/subscribing to analytics in the VPLMN:
- Analytics ID;
- PLMN ID of the HPLMN;
NOTE 4: Security aspects for analytics exchange are covered in TS 33.501 [49].
- Analytics Filter Information:
- [OPTIONAL] HPLMN S-NSSAI;
NOTE 5: V-NWDAF maps that S-NSSAI to an S-NSSAI of the VPLMN which will be used in the Analytics Filter Information.
- other Analytics Filter Information (e.g. AOI in the form of geographical area in the VPLMN) as provided by NWDAF service consumer in the HPLMN, if applicable in the VPLMN.
- [OPTIONAL] NF ID(s) of the NF(s) (e.g. AMF(s), SMF(s)) serving the roaming UE(s) in the VPLMN;
- other parameters as provided by NWDAF service consumer in the HPLMN, if applicable in the VPLMN.
Based on the analytics request or subscription from the NWDAF service consumer in the VPLMN, and local configuration, the V-RE-NWDAF may indicate the following parameters in the Nnwdaf_RoamingAnalytics_Request service operation or the Nnwdaf_RoamingAnalytics_Subscribe service operation to the H-RE-NWDAF, for requesting/subscribing to analytics in the HPLMN:
- Analytics ID;
- PLMN ID of the VPLMN;
NOTE 6: Security aspects for analytics exchange are covered in TS 33.501 [49].
- Analytics Filter Information:
[OPTIONAL] HPLMN S-NSSAI;
NOTE 7: If an S-NSSAI but no mapped S-NSSAI is provided by the NWDAF service consumer in the Analytics Filter Information, the V-NWDAF maps the S-NSSAI to the S-NSSAI of the HPLMN and provides that mapped S-NSSAI of the HPLM as the Analytics Filter Information.
- other Analytics Filter Information (e.g. AOI in the form of geographical area in the HPLMN) as provided by NWDAF service consumer in the VPLMN, if applicable in the HPLMN.
- other parameters as provided by NWDAF service consumer in the VPLMN, if applicable in the HPLMN.
The RE-NWDAF provides the following output information to the consumer RE-NWDAF of the Nnwdaf_RoamingAnalytics_Request service operation or the Nnwdaf_RoamingAnalytics_Notify service operation:
- The output information as defined in clause 6.1.3, with the following differences:
- Information related to analytics aggregation (i.e. analytics metadata information) should not be included.
NOTE 8: The output of the analytics depends on the roaming agreements.
NOTE 9: UE specific data and analytics exchange between HPLMN and VPLMN and the possible storage is agreed between the operators bilaterally via roaming agreements (e.g. SLA) and takes into consideration all relevant regulatory requirements.
6.1A Analytics aggregation from multiple NWDAFs
6.1A.1 General
In a multiple NWDAF deployment scenario, an NWDAF instance may be specialized to provide Analytics for one or more Analytics IDs. Each of the NWDAF instances may serve a certain Area of Interest or TAI(s). Multiple NWDAFs may collectively serve the particular Analytics ID. An NWDAF may have the capability to support the aggregation of Analytics (per Analytics ID) received from other NWDAFs, possibly with Analytics generated by itself.
The procedure for analytics aggregation from multiple NWDAFs is as defined in clause 6.1A.3.
6.1A.2 Analytics Aggregation
The analytics aggregation from multiple NWDAFs is used to address cases where an NWDAF service consumer requests Analytics ID(s) that requires multiple NWDAFs to collectively serve the request. Analytic aggregation applies to scenarios where NWDAF service consumer requests or subscribes to analytics information with or without provisioning Area of Interest.
Aggregator NWDAF or aggregation point:
- Is an NWDAF instance with additional capabilities to aggregate output analytics provided by other NWDAFs. This is in addition to regular NWDAF behaviour such as collecting data from other data sources to be able to generate its own output analytics.
- Is able to divide the area of interest, if received from the consumer, into sub area of interest based on the serving area of each NWDAF to be requested for analytics and then send analytics requests including the sub area of interest as an Analytics Filter to corresponding NWDAFs. The Aggregator NWDAF may maintain information on the discovered NWDAFs, including their supported Analytics IDs, NWDAF Serving Areas, etc.
- Has "analytics aggregation capability" registered in its NF Profile within the NRF.
- Supports the requesting and exchange of "Analytics Metadata Information" between NWDAFs when required for the aggregation of output analytics. "Analytics Metadata Information" is additional information associated with the requested Analytics ID(s) as defined in clause 6.1.3.
- Supports dataset statistical properties, output strategy and data time window parameters per type of analytics (i.e. Analytics ID) as defined in clause 6.1.3.
NRF:
- Stores the NF Profile of the NWDAF instances, including "analytics aggregation capability" for Aggregator NWDAFs and "analytics metadata provisioning capability" when supported by the NWDAF.
- Returns the NWDAF(s) matching the attributes provided in the Nnrf_NFDiscovery_Request, as specified in clause 5.2.7.3 of TS 23.502 [3].
NWDAF service consumer:
- Requests or subscribes to receive analytics for one or more Analytics IDs, as specified in clause 6.1 of the present document.
- Does discovery and selection as defined in clause 6.3.13 of TS 23.501 [2] to identify NWDAFs with analytics aggregation capability and other capabilities (e.g. providing data/analytics for specific TAI(s)).
- Can differentiate and select the preferred NWDAF in case multiple NWDAFs are returned in the NWDAF discovery response based on its internal selection criteria (considering the registered NWDAF capabilities and information in NRF or UDM).
6.1A.3 Procedure for analytics aggregation
6.1A.3.1 Procedure for analytics aggregation with Provision of Area of Interest
The procedure depicted in figure 6.1A.3-1 is used to address cases where an NWDAF service consumer requests Analytics ID(s) for an Area of Interest that requires multiple NWDAFs that collectively serve the request.
Figure 6.1A.3.1-1: Procedure for analytics aggregation
1a-b. NWDAF service consumer discovers the NWDAF as specified in clause 5.2. When NRF is used, NRF may return multiple NWDAF candidates matching the requested capabilities, area of interest and supported Analytics ID(s). NWDAF service consumer selects an NWDAF (e.g. NWDAF1) with analytics aggregation capability (i.e. Aggregator NWDAF), based on its internal selection criteria, considering registered NWDAF capabilities and information in NRF including the Supported Analytics Delay per Analytics ID (if available).
2. NWDAF service consumer invokes Nnwdaf_AnalyticsInfo_Request or Nnwdaf_AnalyticsSubscription_Subscribe service operation from the selected Aggregator NWDAF (e.g. NWDAF1). In the request, NWDAF service consumer provides Analytics ID(s) (e.g. Analytics ID 1) Analytics Filter Information (area of interest, e.g. TAI-1, TAI-2, TAI-n, if known to the NWDAF service consumer), Target of Analytics Reporting as defined in clause 6.1.3. It may also provide "time when analytics information is needed" (e.g. T1). It is expected that T1 is equal or greater than the Supported Analytics Delay per Analytics ID (if available) of the Aggregator NWDAF. Otherwise, the aggregator NWDAF may reject the analytics request or analytics subscription.
3. On receiving the request in step 2, Aggregator NWDAF (e.g. NWDAF1), based on e.g. configuration, queries to NRF including the Real-Time Communication Indication per Analytics ID and queries to UDM for checking which NWDAF(s) is serving the Target of Analytics Reporting. Considering the request from the NWDAF service consumer (e.g. Analytics Filter Information, T1, etc.) and Supported Delay per Analytics ID per NWDAF instance (when Real-Time Communication Indication was included), Aggregator NWDAF determines the other NWDAF instances that collectively can cover the area of interest indicated in the request (e.g. TAI-1, TAI-2, TAI-n).
NOTE 1: In the discovery request sent to NRF, Aggregator NWDAF might indicate "analytics metadata provisioning capability" (e.g. as query parameter), thus, requesting to NRF to reply back with, if available, those NWDAF instance(s) which also supports "analytics metadata provisioning capability" functionality as indicated during particular NWDAF instance registration procedure.
4-5. Aggregator NWDAF (e.g. NWDAF1) invokes Nnwdaf_AnalyticsInfo_Request or Nnwdaf_AnalyticsSubscription_Subscribe service operation from each of the NWDAFs discovered/determined in step 3 (e.g. NWDAF2 and NWDAF3).
The request may optionally indicate "analytics metadata request" parameter to the determined NWDAFs (e.g. NWDAF-2 and/or NWDAF3), when analytics metadata is supported by these NWDAFs.
The request or subscription to the determined NWDAFs (e.g. NWDAF2 and/or NWDAF3) may also include the dataset statistical properties, output strategy and data time window. This indicates to the determined NWDAFs that the Analytics ID output shall be generated based on such parameters when requested.
If "time when analytics information is needed" (T1) was provided in step 2, the Aggregator NWDAF shall also provide a "time when analytics information is needed" to the determined NWDAFs, with a smaller value compared with T1 (e.g. T2).
NOTE 2: T2 in step 4-5 is smaller than T1 accounting for the analytics delay and processing time within the Aggregator NWDAF itself.
6-7a-b. The determined NWDAFs (e.g. NWDAF-2 and/or NWDAF3) reply or notify with the requested output analytics.
If "analytics metadata request" was included in the request received by such NWDAF (in steps 4-5), the NWDAF additionally returns the "analytics metadata information" used for generating the analytics output as defined in clause 6.1.3.
If the determined NWDAFs (e.g. NWDAF 2 and/or NWDAF 3) cannot reply or notify with the requested output analytics before the expiry of T2, they may send an error response or error notification to the Aggregator NWDAF including a "revised waiting time".
8. Aggregator NWDAF (e.g. NWDAF1) aggregates received Analytics information, i.e. generates a single output analytics based on the multiple analytics outputs and, optionally, the "analytics metadata information" received from the determined NWDAFs (e.g. NWDAF2 and NWDAF3).
The Aggregator NWDAF (e.g. NWDAF1) may also take its own analytics for TAI-n into account for the analytics aggregation.
9a-b. Aggregator NWDAF (e.g. NWDAF1) sends a response or notifies to the NWDAF service consumer the aggregated output analytics for the requested Analytics ID.
If the Aggregator NWDAF (e.g. NWDAF 1) cannot reply or notify with the requested output analytics before the expiry of T1 or anticipates that it cannot reply or notify with the requested output analytics before the expiry of T1 (e.g. due to error notification in step 6-7a-b), it may send an error response or error notification to the NWDAF service consumer including a "revised waiting time". The NWDAF service consumer may optionally use the "revised waiting time" to update the "time when analytics information is needed" parameter (i.e. T1) for future analytics requests/subscriptions to the same Aggregator NWDAF as defined in clause 6.2.5.2.
6.1A.3.2 Procedure for Analytics Aggregation without Provision of Area of Interest
The procedure depicted in Figure 6.1A.3.2-1 is used to address cases where an NWDAF service consumer requests Analytics ID(s) without providing an Area of Interest, but requires multiple NWDAFs to collectively serve the request.
Figure 6.1A.3.2-1: Procedure for analytics aggregation without provision of Area of Interest
1. This step is a NWDAF discovery procedure without providing any area of interest. The service consumer discovers an aggregation NWDAF (e.g. NWDAF1) as specified in clause 5.2. When NRF is used, NRF may return multiple NWDAF candidates matching the requested capabilities and supported Analytics ID(s).
Depending on the requested Analytics ID, the NWDAF service consumer, e.g. based on internal logic, can be able to determine which NWDAF should be selected for providing the required data analytics. If not, the NWDAF service consumer should select a NWDAF with large serving area from the candidate NWDAFs which supports analytics aggregation, e.g. NWDAF1.
2. NWDAF service consumer sends Analytics information or analytics subscription request to the aggregator NWDAF, i.e. NWDAF1 in the Figure 6.1A.3.2-1. In the request, NWDAF service consumer provides the requested Analytics ID(s), e.g. Analytics ID 1.
The NWDAF service consumer may also provide "time when analytics information is needed" (e.g. T1). It is expected that T1 is equal or greater than the Supported Analytics Delay per Analytics ID of the Aggregator NWDAF (if available). Otherwise, the aggregator NWDAF may reject the analytics request or analytics subscription.
Once receiving the request, the Aggregator NWDAF1 may decide to subscribe data analytics from other NWDAF instances which can provide the requested data analytics. Based on the Analytics ID, there are two cases for the Aggregator NWDAF1 to subscribe data analytics from other NWDAF instances.
3a. If the data analytics requires UE location information, e.g. for the Analytics IDs "UE Mobility", "Abnormal behaviour", or "User Data Congestion", then:
- 3a-1: (optional) The Aggregator NWDAF1 queries UDM to discover the NWDAF serving the UE, if it is supported.
- 3a-2: If step 3a-1 is not supported, was not executed, or did not return a suitable NWDAF serving the UE, the Aggregator NWDAF1 determines the AMF serving the UE as specified in the clause 6.2.2.1, then requests UE location information from the AMF to be used in the query to NRF in step 4.
NOTE: If an Aggregator NWDAF receives an Analytics request for a group of UEs, i.e. the Target of Analytics Reporting set to a list of Internal Group IDs, it performs NWDAF discovery based on location information of all UEs in each of the Internal Group Ids in the list and then requests all discovered NWDAFs to provide the required analytics.
3b. If the data analytics does not require to collect UE location information, e.g. for the Analytics IDs "Service Experience", "NF load information", or "UE Communication", the Aggregator NWDAF1 can determine the NFs to be contacted for data collection as specified in clause 6.2.2.1 and then it can retrieve NF service area for each of the data source NFs from NRF.
4. (conditional) With the data obtained in step 3, the Aggregator NWDAF1 queries the NRF for discovering the required NWDAF, by sending an NF discovery request which may include UE location (e.g. TAI-1) or NF serving area (e.g. TAI list-1) as a filter to NRF and obtains candidates target NWDAF(s) that can provide the required analytics. This step is skipped if a suitable NWDAF was discovered in step 3a-1. Additionally the Aggregator NWDAF1 may include in the NF discovery request the Real-Time Communication Indication per Analytics ID to request Supported Delay per Analytics ID per NWDAF instance.
Depending on the discovered NWDAF instance(s), there can be two cases:
5a. If a single target NWDAF (e.g. NWDAF2) can provide the requested analytics data, the Aggregator NWDAF (e.g. NWDAF1) can redirect the Nnwdaf_AnalyticsInfo_Request to that target NWDAF or request an analytics subscription transfer to that target NWDAF, depending on the type of the analytics request/subscription received by the NWDAF Service Consumer.
5b. If the Aggregator NWDAF decides to request data analytics from one or more target NWDAFs, the steps 4-9 of the analytics aggregation procedure in clause 6.1A.3.1 are executed.
6.1B Transfer of analytics context and analytics subscription
6.1B.1 General
In a multiple NWDAFs deployment scenario, procedures for transfer of analytics context and analytics subscription can be used to support the target NWDAF to produce the needed analytics.
When the analytics consumer provides the target NWDAF with information on the subscription that could be transferred from the source NWDAF, the target NWDAF may initiate the transfer of analytics context. The analytics consumer provides the information via Nnwdaf_AnalyticsSubscription_Subscribe service operation. When the analytics consumer is an AMF, the old subscription information (if related to a UE) may be provided by the source AMF to the target AMF using a UE context transfer procedure as specified in TS 23.502 [3].
An analytics subscription transfer to the target NWDAF may be initiated by the source NWDAF, followed by an analytics context transfer initiated by the target NWDAF. An NWDAF may transfer one or more of its analytics subscriptions to another NWDAF instance due to internal (e.g. load balancing, graceful shutdown) or external triggers (e.g. UE mobility). For external triggers, the NWDAF may subscribe to NF(s) to be notified about the corresponding events. As for UE mobility, upon the UE location change event notified by the AMF subscribed by the NWDAF, the NWDAF determines whether it can continue to provide the analytics service. If the NWDAF cannot continue to serve the consumer, it should either select a target NWDAF and initiate analytics subscription transfer, or notify the analytics consumer that it cannot provide the service anymore, so that the analytics consumer can select a new NWDAF.
Procedures for analytics subscription transfer allow one NWDAF instance to transfer its ongoing analytics subscriptions to another NWDAF instance. The transfer can be done for all subscriptions or just a selected subset of subscriptions related to specific area(s), specific Analytics ID(s), specific NF(s) and/or specific UE(s).
The procedure for prepared analytics subscription transfer can be used if the source NWDAF instance anticipates that it will soon not be able to continue its current analytics tasks.
6.1B.2 Analytics Transfer Procedures
6.1B.2.1 Analytics context transfer initiated by target NWDAF selected by the NWDAF service consumer
The procedure in Figure 6.1B.2.1-1 is used when an NF decides to select a new NWDAF instance due to internal or external triggers, e.g. the NF starts serving a UE with analytics subscription information received upon UE context transfer procedure as described in TS 23.502 [3], or the NF starts to request NF related analytics, or the NF receives a "Termination Request" for an existing analytics subscription from an NWDAF. The NF sends to the target NWDAF information about the NWDAF previously used for analytics subscription, if available, in Nnwdaf_AnalyticsSubscription_Subscribe service operation. The target NWDAF may initiate the transfer of the analytics context, using the Nnwdaf_AnalyticsInfo_ContextTransfer or Nnf_DataManagement_Subscribe service operation.
The procedure in Figure 6.1B.2.1-1 is also used when an Aggregator NWDAF decides to select a new NWDAF to request output analytics for analytics aggregation. For example, upon receiving a Termination Request from one of the NWDAFs that are collectively serving a request for analytics subscription as specified in clause 6.1A, the Aggregator NWDAF queries the NRF or UDM to select a target NWDAF as specified in clause 6.1A.3 using information e.g. the UE location, the 5GC NFs (identified by their NF Set IDs or NF types) serving the UE or to be contacted for data collection (if Area of Interest is not provisioned for the requested analytics), or the subset of AoI (if Area of Interest is provisioned for the requested analytics). Then, the Aggregator NWDAF sends information about the NWDAF previously used for analytics subscription, if available, in Nnwdaf_AnalyticsSubscription_Subscribe service operation towards the selected target NWDAF.
Figure 6.1B.2.1-1: Analytics context transfer initiated by target NWDAF selected by the NWDAF service consumer
1. The NWDAF service consumer determines to select an NWDAF instance. The consumer discovers and selects the target NWDAF as specified in clause 5.2.
2. The consumer sends a request for analytics subscription to the target NWDAF using Nnwdaf_AnalyticsSubscription_Subscribe service operation, including information on the previous analytics subscription (i.e. NWDAF ID, Analytics ID(s), SUPIs, Analytics Filter Information for UE-related Analytics, Subscription Correlation ID, the Analytics Accuracy Request information (as defined in clause 6.1.3) when the Target NWDAF supports accuracy checking capability) which relates to the requested analytics subscription, if available. If the target NWDAF accepts the analytics subscription request, it sends Nnwdaf_AnalyticsSubscription_Subscribe response with a Subscription Correlation ID.
If the target NWDAF does not receive information of previous analytics subscription in step 2, for UE related Analytics, the target NWDAF may discover previously used NWDAF in UDM as specified in clause 5.2.
NOTE 1: If the selected target NWDAF instance is the same as the source NWDAF instance (as received from the other consumer in step 0), the target NWDAF will update the existing analytics subscription to the new analytics consumer. Following steps are skipped.
NOTE 2: The consumer can provide information on the previous analytics subscription when, e.g. the consumer is an AMF and it received information from the old AMF, see clause 5.2.2.2.2 of TS 23.502 [3].
3a. [Option 1] If the target NWDAF decides to request an analytics context transfer from the previously used NWDAF, it may make use of information sent in step 2 (e.g. the provided Subscription Correlation ID) and use the analytics context transfer procedure as specified in clause 6.1B.3. The target NWDAF may receive an ADRF ID or DCCF ID for collecting the historical data and/or analytics.
If the target NWDAF supports the accuracy checking capability and the request received in step 2 contains the Analytics Accuracy Request information, the target NWDAF may include in the Nnwdaf_AnalyticsInfo_ContextTransfer request the field Requested Analytics Context Type with value set to Analytics accuracy related information and ML Model accuracy related information (both defined in clause 6.1B.4) in order to retrieve the necessary information for starting, respectively, the Analytics Accuracy Information generation as well as the registration as provider of ML Model Accuracy Information for the ML Model.
3b-c. [Option 2] If the target NWDAF decides to only request historical data and/or analytics, then it may collect the data and/or analytics via Nnf_DataManagement_Subscribe service, where the NFs may be either the ADRF, NWDAF or DCCF, as described in clauses 10.2.6, 7.4.2 and 8.2.2 respectively.
Target NWDAF is now ready to generate analytics information and if applicable, Analytics Accuracy Information, taking into account the information received in step 3. The target NWDAF is also able to perform the registration as a new provider for an existing ML Model Accuracy Information process as defined in clause 6.2E.3.2.
4. [Optional] Source NWDAF may purge analytics context after completion of step 3a, if performed and if not already done, unsubscribes from the data source(s) and/or model source(s) that are no longer needed for the remaining analytics subscriptions.
5. [Optional] Target NWDAF may subscribe to relevant data source(s) and/or model source(s), if it is not yet subscribed to the data source(s) and/or model source(s).
6.1B.2.2 Analytics Subscription Transfer initiated by source NWDAF
The procedure in Figure 6.1B.2.2-1 is used by an NWDAF instance to request the transfer of analytics subscription(s) to another NWDAF instance, using the Nnwdaf_AnalyticsSubscription_Transfer service operation defined in clause 7.2.5.
If the source NWDAF discovers that the analytics consumer may change concurrently to this procedure, the source NWDAF should not perform the procedure. In such a case, the source NWDAF may send a message to indicate to the analytics consumer that it will not serve this subscription anymore.
NOTE 1: To discover the possible change of analytics consumer, if the Analytics ID is UE related, the source NWDAF takes actions responding to external trigger (such as UE mobility), for example, checking if the Target of Analytics Reporting is still within the serving area of the analytics consumer, if the serving area information is available.
NOTE 2: Handling of overload situation or preparation for a graceful shutdown are preferably executed inside an NWDAF Set, when available, therefore, not requiring an analytics subscription transfer as described in this clause. The procedure in Figure 6.1B.2.2-1 is applicable for analytics subscription transfer across NF Sets or if the NWDAF is not deployed in a Set.
Figure 6.1B.2.2-1: Analytics subscription transfer initiated by source NWDAF
0. The analytics consumer subscribes to analytics from source NWDAF. The analytics consumer may send its NF ID or serving area, enabling NWDAF to determine whether the following analytics subscription transfer procedure is applicable. Optionally the source NWDAF subscribes to UE mobility events.
1. [Optional] Source NWDAF determines, e.g. triggered by a UE mobility event notification, to prepare an analytics subscription transfer to target NWDAF(s), as specified in the procedure illustrated in clause 6.1B.2.3.
2. Source NWDAF determines, e.g. based on the UE location information received and the analytics consumer's serving area either directly received in step 0 or indirectly received via NRF, to perform an analytics subscription transfer to target NWDAF(s). Therefore, the source NWDAF determines the analytics subscription(s) to be transferred to a target NWDAF.
3. Source NWDAF performs an NWDAF discovery and selects the target NWDAF. NWDAF discovery may be skipped if the target NWDAF had already been discovered as part of a prepared analytics subscription transfer. In the case of aggregated analytics from multiple NWDAFs, the source NWDAF may use the set of NWDAF identifiers related to aggregated analytics (see clause 6.1.3) to preferably select a target NWDAF that is already serving the consumer. If the analytics subscription to be relocated to a target NWDAF also includes the Analytics Accuracy Request information, the source NWDAF selects, if possible, a target NWDAF also with accuracy checking capability. If the source NWDAF does not discover a target NWDAF with accuracy checking capability, the source NWDAF notifies the analytics consumer with Accuracy Information Termination. Therefore, the consumer based on local policy may decide to unsubscribe the analytics ID or to keep using the analytics ID even without receiving the accuracy information.
4. Source NWDAF requests, using Nnwdaf_AnalyticsSubscription_Transfer Request service operation, a transfer of the analytics subscription(s) determined in step 2 to the target NWDAF. The request contains a callback URI of the analytics consumer. The request may also contain active data source ID(s) and ML Model related information, which are related to the analytics subscriptions requested to be transferred, if not already provided as part of the prepared analytics subscription transfer in the preparation procedure (see step 1). The ML Model related information contains the ID(s) of NWDAF(s) containing MTLF that provided the trained models and may contain the file address(es) of the trained ML Model(s), where the file address(es) of the trained ML Model(s) is included only when the source NWDAF itself provides the trained ML Model(s) for the analytics subscription(s) being transferred. The request message may also include "analytics context identifier(s)" indicating the availability of analytics context for particular Analytics ID(s).
5. Target NWDAF accepts the analytics subscription transfer and takes over the analytics generation and if applicable, the Analytics Accuracy Information generation, based on the information received from the source NWDAF.
The target NWDAF may use analytics accuracy request information included in the analytics subscription transfer received in step 4 to start the process of checking and generating Analytics Accuracy Information for the consumer of the transfer analytics subscription.
Target NWDAF may use the ML Model related information, if provided in the Nnwdaf_AnalyticsSubscription_Transfer request. If the ID(s) of NWDAF(s) containing MTLF is provided in the Nnwdaf_AnalyticsSubscription_Transfer request and the NWDAF(s) containing MTLF is part of the locally configured set of NWDAFs containing MTLF, target NWDAF may request or subscribe to the ML Model(s) from the indicated NWDAF(s) containing MTLF as specified in clause 6.2A and use the ML Model(s) for the transferred analytics subscription. If the file address(es) of the trained ML Model(s) is provided and if the NWDAF containing MTLF is part of the locally configured set of NWDAFs containing MTLF, the target NWDAF may retrieve the ML Model using the file address of the trained ML Model. If the provided ID(s) of NWDAF(s) containing MTLF are not part of the locally configured set of ID(s) of NWDAFs containing MTLF, the target NWDAF discovers the NWDAF(s) supporting MTLF that can provide trained ML Model(s) for the Analytics ID(s) as described in clause 5.2.
NOTE 3: If not yet done during a prepared analytics subscription transfer, the target NWDAF allocates a new Subscription Correlation ID to the received analytics subscriptions.
NOTE 4: The target NWDAF might already have received information on some/all of the analytics subscriptions as part of the prepared analytics subscription transfer request received in step 1 and, thus, might already have started to prepare for the analytics generation, e.g. by having already subscribed to relevant event notifications.
6. Target NWDAF informs the analytics consumer about the successful analytics subscription transfer using a Nnwdaf_AnalyticsSubscription_Notify message. A new Subscription Correlation ID, which was assigned by the target NWDAF, is provided in the Subscription Correlation ID and the old Subscription Correlation Id, which was allocated by the source NWDAF, is provided in the Subscription Change Notification Correlation ID parameter of this message as specified in clause 7.2.4.
NOTE 5: Notification correlation information in the Nnwdaf_AnalyticsSubscription_Notify message allows the analytics consumer to correlate the notifications (of analytics output and if applicable of Analytics Accuracy Information) to the initial subscription request made with the source NWDAF in step 0.
NOTE 6: The existing Analytics context in the source NWDAF is not deleted directly but will be purged first when it was collected by the target NWDAF.
NOTE 7: If this subscription is used as input for analytics aggregation by the analytics consumer, the analytics consumer might inform the other NWDAFs instance participating in this analytics aggregation that the Set of NWDAF identifiers of NWDAF instances used by the NWDAF service consumer for this analytics aggregation (see clause 6.1.3) has changed using the Nnwdaf_AnalyticsSubscription_Subscribe service operation.
7. [Conditional] If "analytics context identifier(s)" had been included in the Nnwdaf_AnalyticsSubscription_Transfer Request received in step 4, the target NWDAF requests the "analytics context". The analytics context transfer procedure is specified in clause 6.1B.3.
If the transfer request received by the target NWDAF also includes the Analytics Accuracy Request information, the target NWDAF will include in the Nnwdaf_AnalyticsInfo_ContextTransfer request the field Requested Analytics Context Type with value set to Analytics accuracy related information (as defined in clause 6.1B.4) in order to retrieve the necessary information for generating the Analytics Accuracy Information.
The target NWDAF may also retrieve from source NWDAF containing AnLF the ML Model Accuracy Information for the ML Model when ML Model accuracy related information context type is included in the "analytics context identifier(s)" in the transfer request. Based on the retrieved ML Model accuracy related information, the target NWDAF containing AnLF registers as provider of ML Model Accuracy Information for the ML Model as defined in clause 6.2E.3.2.
8. [Optional] Target NWDAF subscribes to relevant data source(s), if it is not yet subscribed to the data source(s) for the data required for the Analytics.
9. Target NWDAF confirms the analytics subscription transfer to the source NWDAF.
10. [Optional] Source NWDAF unsubscribes with the data source(s) that are no longer needed for the remaining analytics subscriptions. In addition, Source NWDAF unsubscribes with the NWDAF(s) containing MTLF, if exist, which are no longer needed for the remaining analytics subscriptions.
NOTE 8: At this point, the analytics subscription transfer is deemed completed, i.e. the source NWDAF can delete all information related to the successfully transferred analytics subscription.
11-12. Target NWDAF at some point derives new output analytics and Analytics Accuracy Information (if applicable) based on new input data and notifies the analytics consumer about the new analytics and new Analytics Accuracy Information (if applicable) using a Nnwdaf_AnalyticsSubscription_Notify message as specified in clause 6.1.1.
6.1B.2.3 Prepared analytics subscription transfer
The procedure in Figure 6.1B.2.3-1 is used by an NWDAF instance to request another NWDAF instance for a prepared analytics subscription transfer from the source NWDAF instance, using the Nnwdaf_AnalyticsSubscription_Transfer service operation defined in clause 7.2.5.
NOTE 1: The source NWDAF might determine that it needs to prepare to transfer analytics to another NWDAF instance, e.g. when the source NWDAF estimates for UE related analytics subscription that the UE might enter an area which is not covered by the source NWDAF (e.g. by subscribing to AMF event exposure service for UE mobility event notifications, by performing UE mobility analytics, or by subscribing to another NWDAF providing UE mobility analytics). If the source NWDAF discovers that the analytics consumer may change concurrently to this procedure, the source NWDAF does not perform the procedure. If the procedure makes use of predictions to determine the candidate NWDAFs, care must be taken with regards to load and signalling cost when sending data to an NWDAF that will not eventually start serving the UE.
NOTE 2: The source NWDAF might also determine that it needs to prepare to transfer analytics subscriptions to another NWDAF instance, as the source NWDAF wants to resolve an internal load situation or prepare for a graceful shutdown.
NOTE 3: Handling of overload situation or preparation for a graceful shutdown are preferably executed inside an NWDAF Set, when available.
Figure 6.1B.2.3-1: Prepared analytics subscription transfer
0. Analytics consumer subscribes to the source NWDAF for certain analytics as specified in clause 6.1.1.
0a. Source NWDAF starts data collection from relevant data source(s) (e.g. NFs or OAM) as specified in clause 6.2. Source NWDAF starts generating requested analytics.
0b. [Conditional] (Only if the source NWDAF does not serve the whole PLMN and the requested analytics involves UE related data) The source NWDAF subscribes, using Namf_EventExposure_Subscribe service operation, to receive notifications on UE mobility events from AMF.
1. The source NWDAF determines that it needs to prepare to transfer analytics to another NWDAF instance.
2. The source NWDAF discovers candidate target NWDAF instances (e.g. NWDAFy and NWDAFz) supporting the requested analytics information for the predicted target area(s). NWDAF discovery and selection is specified in clause 6.3.13 of TS 23.501 [2]. In the case of aggregated analytics from multiple NWDAFs, the source NWDAF may use the set of NWDAF identifiers related to aggregated analytics (see clause 6.1.3) to preferably select a target NWDAF that is already serving the consumer. In the case of the analytics subscription to be transferred also includes an Analytics Accuracy Request information as defined in clause 6.1.3, the source NWDAF takes into consideration in the selection process whether target NWDAF have the accuracy checking capability.
NOTE 4: In this procedure, NWDAFy and NWDAFz are examples for target NWDAF instances that are candidates to take over those analytic subscriptions.
3-4. In the case of a prepared analytics subscription transfer, the source NWDAF requests, using Nnwdaf_AnalyticsSubscription_Transfer Request, to the candidate target NWDAFs (e.g. NWDAFy and NWDAFz) to prepare for an analytics subscription transfer by including a "prepared analytics subscription transfer indication" in the request message. The request message includes information on the analytics subscriptions to be transferred. The request message may also include "analytics context identifier(s)" indicating the availability of analytics context for particular Analytics ID(s).
The candidate target NWDAFs (e.g. NWDAFy and NWDAFz) respond to the request from the source NWDAF using a Nnwdaf_AnalyticsSubscription_Transfer Response message.
5-6. [Conditional] If "analytics context identifier(s)" had been included in the Nnwdaf_AnalyticsSubscription_Transfer Request received in step 4, the determined target NWDAFs (e.g. NWDAFy and NWDAFz) may request the "analytics context" from the source NWDAF by invoking the "Nnwdaf_AnalyticsInfo_ContextTransferservice" operation. The analytics context transfer procedure is specified in clause 6.1B.3.
If the target NWDAF supports the accuracy checking capability and the request received in steps 3-4 contains the Analytics Accuracy Request information, the target NWDAF includes in the Nnwdaf_AnalyticsInfo_ContextTransfer request the field Requested Analytics Context Type with value set to Analytics accuracy related information (as defined in clause 6.1B.4) in order to retrieve the necessary information for starting the Analytics Accuracy Information. The target NWDAF may also include in the request the Requested Analytics Context Type with value set to ML Model accuracy related information in order obtain the proper information to register as a new provider of ML Model Accuracy Information for the ML Model as defined in clause 6.2E.3.2.
NOTE 5: The target NWDAFs (e.g. NWDAFy and NWDAFz) can allocate a new Subscription Correlation ID to the received analytics subscriptions.
7. [Optional] Based on the information received from the source NWDAF, the target NWDAFs (e.g. NWDAFy and NWDAFz) start data collection from NFs or OAM (as specified in clause 6.2), analytics generation for the indicated analytics subscriptions and if applicable the analytics accuracy checking and generation (as specified in clause 6.2D).
NOTE 6: After step 7, the source NWDAF initiates the analytics subscription transfer to the target NWDAF as specified in steps 4 to 12 of the analytics subscription transfer procedure illustrated in Figure 6.1B.2.2-1.
8. The source NWDAF cancels the prepared analytics subscription transfer to a candidate target NWDAF (e.g. NWDAFz), using Nnwdaf_AnalyticsSubscription_Transfer Request include an "analytics subscription transfer cancel indication". The target NWDAF (e.g. NWDAFz) confirms the cancelation to the source NWDAF and, if applicable, deletes any analytics data that is no longer needed. If the target NWDAF (e.g. NWDAFz), as part of the analytics subscription preparation, had already subscribed to entities to collect data or acquire ML Model, it unsubscribes to those entities if the subscriptions are not needed for other active analytics subscriptions with the target NWDAF. If the candidate NWDAF (e.g. NWDAFz), as part of the analytics subscription preparation, had already started the analytics accuracy generation (as specified in clause 6.2D), it cancels the generation and if any extra data collection has been started, this data collection is also stopped, if not used by any other process in the target NWDAF.
Step 8 may take place any time after step 4 if the NWDAF determines that the candidate target NWDAF (e.g. NWDAFz) does no longer need to prepare for the analytics subscription transfer. In particular, the source NWDAF shall cancel the prepared analytics subscription transfer to all remaining candidate target NWDAFs after one target NWDAF has accepted the analytics subscription transfer (see NOTE 6).
If the source NWDAF is not able to discover a target NWDAF with accuracy checking capability, the source NWDAF notifies the analytics consumer with Accuracy Information Termination. Therefore, the consumer may decide to unsubscribe the analytics ID or to keep using the analytics ID even without receiving the accuracy information.
6.1B.3 Analytics Context Transfer
The procedure depicted in Figure 6.1B.3-1 is used by an NWDAF instance to request analytics context from another NWDAF instance, using the Nnwdaf_AnalyticsInfo_ContextTransfer service operation as defined in clause 7.3.3. This procedure, for example, can be invoked in the procedures described in clause 6.1B.2 to request the transfer of relevant analytics context.
Figure 6.1B.3-1: Analytics Context Transfer
The procedure of analytics context information transfer comprises the following steps:
1. The consumer NWDAF requests analytics context by invoking Nnwdaf_AnalyticsInfo_ContextTransfer request service operation. The parameters that can be provided in the request are listed in clause 6.1B.4.
2. The provider NWDAF responds with analytics context to the consumer NWDAF. The analytics context that can be provided in the response is listed in clause 6.1B.4.
If the provider NWDAF stores analytics context (i.e. Historical output Analytics and/or Data related to Analytics) in ADRF, the provider NWDAF may include in the response the ADRF ID together with an indication of the Analytics Context Type stored in the ADRF (i.e. Historical output Analytics and/or Data related to Analytics).
Upon receiving the analytics context, the consumer NWDAF may:
- provide the pending output analytics or historical analytics information to the analytics consumer per the subscription/request;
- use the historical data and analytics metadata in the analytics context to generate analytics;
- use the analytics accuracy related information in the analytics context to activate the checking of Analytics Accuracy Information for the transferred analytics ID, generate and provide the Analytics Accuracy Information for the consumer.
NOTE: The consumer NWDAF can analyse the timestamps of the historical data included in the analytics context in order to obtain the inference configuration used at the source NWDAF for data collection and may decide to use the same inference configuration for the analytics accuracy generation.
- use the ML Model accuracy related information in the analytics context to determine the need for registration at the NWDAF containing MTLF with the information to enable the NWDAF containing MTLF to reassociated the data of the existing subscription for ML Model Accuracy Information to a new ML Model Accuracy Monitoring process at the target NWDAF containing AnLF, reusing the existing data (as further detailed in clause 6.2E.3).
- subscribe to data collected for analytics with the data sources indicated in the analytics context;
- if the ID(s) of the NWDAF(s) containing MTLF indicated in the analytics context is part of the locally configured (set of) IDs of NWDAFs containing MTLF, retrieve trained ML Model(s) from the indicated NWDAF(s) containing MTLF or based on the file address(es) of the trained ML Model(s) and use for analytics; and/or
- subscribe to output analytics from the indicated NWDAFs that collectively serve the transferred analytics subscription and perform analytics aggregation on the output analytics using the analytics metadata information, based on the analytics subscription aggregation information.
6.1B.4 Contents of Analytics Context
The Nnwdaf_AnalyticsInfo_ContextTransfer service operation is used to transfer analytics context from a source NWDAF instance to a target NWDAF instance, whereby the target NWDAF consumes the Nnwdaf_AnalyticsInfo_ContextTransfer service operation produced by the source NWDAF instance to request the analytics context as depicted in Figure 6.1B.3-1.
The consumers of the Nnwdaf_AnalyticsInfo_ContextTransfer service operation (as specified in clause 7.3.3) provide the following input parameters:
- A list of analytics context identifier(s): identify a set of analytics contexts that are available at the NWDAF instance providing this service and that are requested to be transferred to the consumer NWDAF instance. The analytics context identifier is provided as the following:
- Subscription Correlation ID: identifies the analytics subscription for which the related analytics context is requested; or
- A set of SUPI and associated Analytics ID for UE related Analytics; or
- An Analytics ID for NF related Analytics.
- [OPTIONAL] Requested Analytics Context Type per analytics context identifier: indicates which part of the analytics context the consumer wishes to receive. Following values are specified:
- Pending output Analytics;
- Historical output Analytics;
- Analytics subscription aggregation information;
- Data related to Analytics;
- Aggregation related information;
- ML Model related information;
- Analytics accuracy related information.
- ML Model accuracy related information.
NOTE: A list of "analytics context identifiers" can be provided by the source NWDAF to the target NWDAF in an analytics subscriptions transfer request as described in clause 6.1B.2.2. Information allowing to identify an analytics context can also be provided by the NWDAF consumer to the target NWDAF in the Nnwdaf_AnalyticsSubscription_Subscribe request and based on this information the target NWDAF derives the "analytics context identifier", as defined in clause 6.1B.2.1.
The producer NWDAF provides to the consumer of the Nnwdaf_AnalyticsInfo_ContextTransfer service operation (as specified in clause 7.3.3), the output information listed below:
- (Set of) Analytics context matching the input parameters of the Nnwdaf_AnalyticsInfo_ContextTransfer request. If no Requested Analytics Context type parameters are available in the request, all available analytics context types are sent. Analytics context includes the following information parts, if available:
- Analytics related:
- Pending output analytics (i.e. not yet notified to the consumer).
- Historical output analytics information. The content of the output analytics is specified in clause 6.1.3 as output information of the Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Request service operations.
- Timestamp(s) of the last output analytics provided to the analytics consumer(s). Value is set to 0 if no output analytics had been sent yet.
- Analytics subscription aggregation information (only provided when analytics context is related to analytics aggregation): information about the analytics subscriptions that the source NWDAF has with the NWDAFs that collectively serve the transferred analytics subscription, which includes IDs and analytics metadata information of these NWDAFs for specific Analytics ID(s) and optionally input parameters of analytics exposure as defined in clause 6.1.3.
- Data related to Analytics:
- Historical data that is available at the source NWDAF and that is related to the analytics to be handed over to the target NWDAF. If available, the time period of the collected data, NF ID(s) of the data source(s) and information (e.g. filter and event reporting parameters) on the subscriptions with those data sources which were used to generate this historical data.
- Aggregation related information: Related to analytic consumers that aggregate analytics from multiple NWDAF subscriptions:
- (Set of) NWDAF identifiers of NWDAF instances used by the NWDAF service consumer when aggregating multiple analytic subscriptions.
- ML Model related information:
- ID(s) of NWDAF(s) containing MTLF: Instance/Set ID(s) of the NWDAF(s) containing MTLF from which the source NWDAF currently subscribes to the ML Model Information used for the analytics.
- Optionally, file address(es) of the trained ML Model(s), which is included only when the source NWDAF itself provides the trained ML Model(s) for the analytics subscription(s) for which the related analytics context is requested.
- Analytics Accuracy related information: The information is related to the parameters of the Analytics Accuracy Request Information and status of the analytics subscription due to NF consumer and NWDAF interactions pausing or resuming the analytics output. It includes:
- Timestamp(s) of the last Analytics Accuracy Information provided to the analytics consumer(s). Value is set to 0 if no Analytics Accuracy Information had been sent yet;
- Indication whether analytics subscription is paused;
- Remaining time window of paused analytics subscription;
- Ground truth information: data types and data sources of the ground truth per analytics used for the accuracy information computation.
- ML Model accuracy related information: The information is related to the parameters of the ML Model Accuracy (i.e. Analytics accuracy for an ML model as described in clause 6.2E.3.3) Subscription Information requested by a NWDAF containing MTLF. It includes:
- original Subscription Correlation ID for the ML Model Accuracy Information associated with the ML Model and/or analytics ID at the source NWDAF containing AnLF;
- Analytics ID, Target of Analytics Reporting and the corresponding Analytics filter associated with the original ML Model Monitoring subscription at the source NWDAF containing AnLF;
- NWDAF containing AnLF NF ID of source NWDAF;
- The parameters used for the subscription for ML Model Accuracy Information for the given ML Model at the source NWDAF containing AnLF.
6.1C NWDAF Registration/Deregistration in UDM
6.1C.1 General
The procedures in this clause are applicable to UE-related analytics (e.g. UE mobility analytics) for some network deployments, e.g. such with an NWDAF co-located to an AMF or SMF, where the NWDAF is configured to register in UDM for the UEs that it is serving or collecting data for and for the related Analytics ID(s). The procedures in this clause are also applicable to analytics that are not UE-related, when the NWDAF collects UE-related data. This enables NWDAF service consumers to discover the NWDAF instance that is already serving the UE for one or more Analytics ID(s).
6.1C.2 NWDAF Registration in UDM
Figure 6.1C.2-1 shows the procedures for registration of the NWDAF in UDM for UE-related analytics or UE-related data collection.
Figure 6.1C.2-1: NWDAF registration in UDM
1. NWDAF triggers a registration in UDM, e.g. based on local configuration in the NWDAF, the reception of a new Analytics subscription request, start of collection of UE related data or an OAM configuration action.
2. The NWDAF registers into UDM for the served UE, by sending Nudm_UECM_Registration request (UE ID, NWDAF ID, Analytics ID(s)).
3. UDM sends a response to NWDAF.
6.1C.3 NWDAF De-registration from UDM
Figure 6.1C.3-1 shows the procedures for deregistration of the NWDAF in UDM.
Figure 6.1C.3-1: NWDAF de-registration from UDM
1. NWDAF triggers a de-registration from a previous registration in UDM. This trigger may be that, e.g. the NWDAF has purged the analytics context for the UE (see clause 6.1B.4) for related Analytics ID(s), the NWDAF is no longer collecting data related to the UE, or an administrative action.
2. NWDAF sends Nudm_UECM_Deregistration request (UE ID, NWDAF ID, Analytics ID(s)).
3. UDM sends a response to NWDAF.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2 Procedures for Data Collection
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.1 General
| The Data Collection feature permits NWDAF to retrieve data from various sources (e.g. NF such as AMF, SMF, PCF, NSACF, GMLC and AF; OAM), as a basis of the computation of network analytics.
All available data encompass:
- OAM global NF data,
- Data available in NFs, e.g. behaviour data related to individual UEs or UE groups (e.g. UE reachability) and pre-computed metrics covering UE populations (e.g. number of UEs present in a geographical area), per spatial and temporal dimensions (e.g. per region for a period of time),
- NF data available in the 5GC (e.g. NRF),
- Data available in AF.
When DCCF, ADRF, MFAF or NWDAF hosting DCCF or ADRF are present in the network, the data collection also follows the principles described in clause 6.2.6.
The NWDAF shall use at least one of the following services:
- the Generic management services as defined in TS 28.532 [6], the Performance Management services as defined in TS 28.550 [7] or the Fault Supervision services as defined in TS 28.545 [9], offered by OAM in order to collect OAM global NF data.
- the Exposure services offered by NFs in order to retrieve data and other non-OAM pre-computed metrics available in the NFs.
- Other NF services in order to collect NF data (e.g. NRF)
- DCCF data management service to retrieve data using DCCF.
The NWDAF shall obtain the proper information to perform data collection for a UE identified by a SUPI, a group of UEs identified by an Internal-Group-Id or any UE:
- For an Analytics ID, NWDAF is configured with the corresponding NF Type(s) and/or event ID(s) and/or OAM measurement types.
- NWDAF shall determine which NF instance(s) of the relevant NF type(s) are serving the UE, the group of UEs identified by an Internal-Group-Id or any UE, taking into account the S-NSSAI(s) and area of interest as defined in clause 7.1.3 of TS 23.501 [2].
- NWDAF invokes Nnf_EventExposure_Subscribe services to collect data from the determined NF instance(s) and/or triggers the procedure in clause 6.2.3.2 to subscribe to OAM services to collect the OAM measurement.
The NWDAF performs data collection from an AF directly as defined in clause 6.2.2.2 or via NEF as defined in clause 6.2.2.3. According to the data collection request, the AF may further perform data collection from UE (see clause 6.4.2 and clauses 6.5.2-6.5.4) as defined in clause 6.2.8.
The NWDAF shall be able to discover the events supported by a NF.
Data collection procedures enables the NWDAF to efficiently obtain the appropriate data with the appropriate granularity.
When a request or subscription for statistics or predictions is received, the NWDAF may not possess the necessary data to perform the service, including:
- Data on the monitoring period in the past, which is necessary for the provision of statistics and predictions matching the Analytics target period.
- Data on longer monitoring periods in the past, which is necessary for model training.
Therefore, in order to optimize the service quality, the NWDAF may undertake the following actions:
- The NWDAF may return a confidence parameter as stated in clause 6.1.3 expressing the confidence in the prediction produced. Prediction may be returned with zero confidence as described below. This confidence is likely to grow in the case of subscriptions.
- The value of the confidence depends on the level or urgency expressed by the parameter "preferred level of accuracy" as listed in clause 6.1.3, the parameter "time when analytics information is needed" as listed in clause 6.1.3 and the availability of data. If no sufficient data is collected to provide an estimation for the preferred level of accuracy before the time deadline, the service shall return a zero confidence. Otherwise, the NWDAF may wait until enough data is collected before providing a response or a first notification.
- In order to be prepared for future requests on analytics from NFs/OAM, the NWDAF, upon operator configuration, may collect data on its own initiative, e.g. on samples of UEs and retain the data collected in the data storage.
NOTE 1: The NWDAF can send an error response to the analytics consumer to indicate that statistics are unavailable if the NWDAF was not prepared for future requests and did not collect data on its own initiative.
The volume and maximum duration of data storage is also subject to operator configuration.
The NWDAF may decide to reduce the amount of data collected to reduce signalling load, by either prioritizing requests received from analytics consumers, or reducing the extent (e.g. duration, scope) of data collection, or modifying the sampling ratios. When using sampling ratio, the NWDAF may, depending on the analytics required and based on local configuration, provide additional partitioning criteria to the NFs to allow for a better UEs representation and to request that the NFs first partition the UEs before applying sampling ratio (see Event Reporting Information as specified in TS 23.502 [3]). The NWDAF may provide one or multiple partitioning criteria in its request for data collection from NFs.
In order to optimize the performance and accuracy of data collection and reporting and reduce the impact on data producers, the NWDAF may request subscriptions to the NFs with the variable reporting periodicity parameter. Depending on the condition provided as part of this parameter, different reporting periodicity are used. The condition is the load of the NF.
The NWDAF may skip data collection phase when the NWDAF already has enough information to provide requested analytics.
The data which NWDAF may collect is listed for each analytics in input data clause and is decided by the NWDAF.
NOTE 2: NWDAF can skip data collection phase for some specific input data per the requested analytics e.g. when some of the data is already available at NWDAF for the requested analytics, or when NWDAF considers that some of the data is not needed at all to provide the requested analytics as per the analytics consumer request (e.g. based on preferred level of accuracy or based on the time when analytics are needed).
Event exposure subscriptions for data collection from the AMF and the SMF may need to survive after the removal of UE context in the AMF including event exposure subscriptions, or upon the creation of new UE context in AMF or SMF. In order for event exposure subscriptions in AMF and SMF to be (re)created in these cases, the NWDAF may subscribe to the events in AMF and/or SMF via UDM for a UE identified by a SUPI or a group of UEs identified by an Internal-Group-Id, as specified in clause 4.15.4.4 of TS 23.502 [3].
In hierarchical interactions among NWDAFs, without standalone DCCF, or co-located DCCF, the efficiency of data collection can be achieved by inter-NWDAF instance cooperation among NWDAF instances on different levels of the hierarchy. An efficient data collection means that the same data required for the same Analytics ID or different Analytics IDs should not be collected multiple times by the different NWDAFs of the hierarchy.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.2 Data Collection from NFs
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.2.1 General
| The Data Collection from NFs and SCP is used by NWDAF to subscribe/unsubscribe at any 5GC NF to be notified for data on a set of events.
The Data Collection from NFs and SCP is based on the services of AMF, SMF, UDM, PCF, NRF, NSACF, UPF, LMF and AF (possibly via NEF):
- Event Exposure Service offered by each NF as defined in clause 4.15 and clause 5.2 of TS 23.502 [3].
- other NF services (e.g. Nnrf_NFDiscovery and Nnrf_NFManagement in NRF as defined in clause 4.17 of TS 23.502 [3])
This data collection service is used directly in order to retrieve behaviour data for individual UEs or groups of UEs (e.g. UE reachability) and also to retrieve global UE information (e.g. Number of UEs present in a geographical area).
Table 6.2.2.1-1: NF Services consumed by NWDAF for data collection
Service producer
Service
Reference in TS 23.502 [3] or other indicated specification
AMF
Namf_EventExposure (NOTE 2)
5.2.2.3
5.2.3.5
SMF
Nsmf_EventExposure (NOTE 2)
5.2.8.3
5.2.3.5
PCF
Npcf_EventExposure (for a group of UEs identified by an Internal-Group-Id or any UE)
Npcf_PolicyAuthorization_Subscribe (for a specific UE)
5.2.5.7
UDM
Nudm_EventExposure
5.2.3.5
NEF
Nnef_EventExposure
5.2.6.2
AF
Naf_EventExposure
5.2.19.2
NRF
Nnrf_NFDiscovery
5.2.7.3
Nnrf_NFManagement
5.2.7.2
NSACF
Nnsacf_SliceEventExposure
5.2.21.4
UPF
Nsmf_EventExposure or Nupf_EventExposure
5.2.8.3
5.2.26.2
SCP
Nscp_EventExposure Service
5.2.28.2
LMF
Nlmf_DataExposure
Clause 8.3.4 of TS 23.273 [39]
NOTE 1: There is no data collected from the PCF by the NWDAF defined in this Release of the specification.
NOTE 2: The Nudm_EventExposure can be used when NWDAF uses the procedures specified in clause 4.15.4.4 of TS 23.502 [3] to subscribe to AMF or SMF via UDM.
To retrieve data related to a specific UE, there are two cases:
- If no Area of interest is indicated by the consumer, the NWDAF shall first determine which NF instances are serving this UE as stated in table 6.2.2.1-2 unless the NWDAF has already obtained this information due to recent operations related to this UE.
- If an Area of interest is indicated, the NWDAF can:
- First determine the AMF serving the UE and subscribe UE location from the AMF. Once the UE is in or moves into the Area of interest, the NWDAF determines which NF instances are serving this UE as stated in table 6.2.2.1-2 unless the NWDAF has already obtained this information due to recent operations related to this UE; or
- Determine the NF instances of a given type of network function serving the Area of interest by querying NRF unless the NWDAF has already obtained this information due to recent operations related to this UE.
Table 6.2.2.1-2: NF Services consumed by NWDAF to determine which NF instances are serving a UE
Type of NF instance (serving the UE) to determine
NF to be contacted by NWDAF
Service
Reference in TS 23.502 [3]
UDM
NRF
Nnrf_NFDiscovery
5.2.7.3
AMF
UDM
Nudm_UECM
5.2.3.2
SMF
UDM
Nudm_UECM
5.2.3.2
BSF
NRF
Nnrf_NFDiscovery
5.2.7.3
PCF
BSF
Nbsf_Management
5.2.13.2
NEF
NRF
Nnrf_NFDiscovery
5.2.7.3
NWDAF
NRF
UDM
Nnrf_NFDiscovery
Nudm_UECM
5.2.7.3
5.2.3.2
NSACF
NRF
Nnrf_NFDiscovery
5.2.7.3
GMLC
NRF
Nnrf_NFDiscovery
5.2.7.3
The UDM instance should be determined using NRF as described in clause 4.17.4 of TS 23.502 [3] and factors to determine as described in clause 6.3.8 of TS 23.501 [2].
The AMF, SMF instances should be determined using a request to UDM providing the SUPI. To determine the SMF serving a PDU session, the NWDAF should in addition provide the DNN and S-NSSAI of this PDU Session; otherwise the NWDAF will obtain a list of possibly multiple SMFs (e.g. one per PDU session).
The BSF instance is discovered and selected according to TS 23.503 [4], clause 6.1.1.2.2.
The PCF instance serving UE PDU Session(s) should be determined using a request to BSF with the allocated UE address, DNN and S-NSSAI.
To collect data (e.g. current number of UEs registered in a network slice or current number of PDU Sessions established in a network slice) from NSACF, the NSACF instance is discovered and selected as specified in clause 6.3.22 of TS 23.501 [2].
When NWDAF receives a request addressed to an Internal Group ID from a consumer, NWDAF may need to initiate data collection from several 5GC NFs, such as AMF, SMF, UDM, PCF, AF (e.g. via NEF), etc. If an Area of interest is indicated by the consumer, NWDAF may first discover the instances of the required 5GC NFs deployed in the network, e.g. by querying NRF, otherwise:
- For discovering the UDM, NWDAF can query the NRF with the Internal Group ID as the target of the query.
- For discovering AMF, SMF, PCF, NEF and AF, NWDAF may need to discover all instances in the network by using the Nnrf_NFDiscovery service.
NOTE 3: It is assumed that all members of an Internal Group ID belong to the same UDM Group ID. NWDAF can select a UDM instance supporting the UDM Group ID of the Internal Group ID.
Then, if data needs to be collected from AMF, SMF, UDM and PCF, NWDAF may initiate the data collection with the Internal Group ID as the target, e.g. subscribing to the event exposure in all the instances of a given type of network function. This subscription to all the instances of required source of event exposure handles, e.g. mobility of UEs across AMFs, or initiation of new PDU sessions with different allocated SMFs.
For collecting data from AMF and SMF, NWDAF may collect the data directly from AMF and/or SMF, or indirectly via UDM, according to clause 4.15.4.4 of TS 23.502 [3]. The indirect method may be required if the event exposure subscription from NWDAF, for a UE identified by a SUPI or a group of UEs identified by an Internal-Group-Id, needs to survive the removal of UE context in the AMF including event exposure subscriptions, or upon the creation of new UE context in AMF or SMF serving the UE or group of UEs. In this case the UDM is responsible for (re)creating event exposure subscriptions in AMF and SMF, as specified in clause 4.15.4.4 of TS 23.502 [3].
The NWDAF determines to collect data from a trusted AF supporting specific Event ID(s) and serving specific application(s) based on internal configuration.
The NEF instance that is serving a specific network slices and/or applications of a UE should be determined using NRF using optional request parameters as defined in clause 6.3.14 of TS 23.501 [2]
If NWDAF needs to collect data from an AF deployed outside the operator's domain, the NWDAF shall contact NEF with a SUPI or Internal Group ID as the target of the data collection. NEF is responsible for translation of SUPI to GPSI, or internal to external group identifiers, by querying UDM, prior to contacting the AF.
NOTE 4: It is assumed that an AF is provisioned with the list of UE IDs (GPSIs or SUPIs) belonging to an External or Internal Group ID.
NWDAF may collect data directly from UPF for a specific UE identified by a SUPI, a group of UEs identified by an Internal-Group-Id or for any UEs as defined in clause 5.8.2 of TS 23.501 [2] and in clause 4.15.4.5 of TS 23.502 [3]. NWDAF may subscribe indirectly via SMF or directly to UPF for UPF data collection. The direct subscription to UPF event exposure service is only for data collection for any UE e.g., to collect user data usage information for NWDAF NF Load analytic, and if the subscription is not including any of the parameters described in Table 4.15.4.5.1-1 of TS 23.502 [3].
NOTE 5: To avoid causing high UPF load due to extensive reporting related to all traffic flows, the NWDAF can preferably subscribe for reporting for some UEs only.
To retrieve required data for any UE, the NWDAF may subscribe to events from the AMF and/or SMF instances or UPF instances it has determined, setting the target of event reporting to "any UE" and the event filter(s) according to the Analytics Filter Information. Alternatively, if the required data is communication related and for any UE within an Area of interest, the NWDAF can obtain from the AMF instances it has determined a list of UEs located within the Area of Interest. Based on the obtained UE list, for each UE in the list, the NWDAF retrieves the SMF serving the UE and the NWDAF subscribes to data from the relevant SMF per each specific UE. The indirect event exposure subscription to AMF or SMF via UDM is not available for "any UE" or "any UE within an Area of interest". If the required data is collected from UE via AF as described in clause 6.2.8 and the Target of Analytics Reporting received from consumer is "any UE", the NWDAF may either set the target of event reporting to "any UE" in the data collection request to the AF, or may determine a list of UEs from AMF and/or SMF based on the Analytics Filter Information and send the data collection request to the AF for the determined list of UEs.
NOTE 6: If NWDAF requires collecting data from either AMF or SMF for "any UE" or "any UE within an Area of Interest", NWDAF can use the direct Event Exposure subscription to AMF or SMF, since subscriptions to "any UE" or "any UE within an Area of Interest" are persistent by nature in AMF or SMF, due to not being linked to a UE context.
To retrieve data related to "any UE" based on Analytics Filter Information, the NWDAF shall first determine which NF instances are matching the Analytics Filter Information (see clause 6.7.5.1) as stated in table 6.2.2.1-3 unless the NWDAF has already obtained this information due to recent operations related to this Analytics Filter Information.
Table 6.2.2.1-3: NF Services consumed by NWDAF to determine which NF instances are matching analytics filters
Type of NF instance (matching analytics filters) to determine
NF to be contacted by NWDAF
Service
Reference in TS 23.502 [3]
AMF, SMF, UPF
NRF
Nnrf_NFDiscovery
5.2.7.3
To retrieve data related to Analytics IDs for "any UE" with Analytics Filter Information defining an area of interest in terms of TA or Cells and/or with specific S-NSSAIs, NWDAF requires the network slice association information to properly determine the AMFs to collect data from as well as the proper queries to OAM for data collection.
NOTE 7: Examples of Analytics ID requiring NWDAF to use network slice association information for data retrieval are: network performance clause 6.6.1; user data congestion clause 6.8.1; QoS Sustainability clause 6.9; Dispersion Analytics clause 6.10.1; observed service experience for a Network Slice clause 6.4.1; and slice load analytics clause 6.3.
The network slice association information comprises the TAs associated with each AMF and for each TAI its associated access type, cells and list of supported S-NSSAIs (including indication of S-NSSAIs restricted by AMF). Additionally, the mapping of cells per TAI and supported S-NSSAIs (including indication of S-NSSAIs restricted by AMF) for TAI for each AMF can change and NWDAF shall obtain this accurate information in order to properly retrieve data for analytics generation.
In order to derive the network slice association information, NWDAF may be configured with the mapping of cells per TAI and the S-NSSAIs per TAI. NWDAF may subscribe to the "S-NSSAIs per TAI mapping" event exposed by AMF. The NWDAF may use the configured information (when the analytics subscription or request is at cell granularity) and the area of interest in the analytics subscription or request to retrieve from AMF the list of supported S-NSSAIs (including indication of S-NSSAIs restricted by AMF) per TAI and access types per TAI for each AMF in the required area of interest. NWDAF consumes the "S-NSSAIs per TAI mapping" event exposed by AMF using, as target of event reporting, the list of TAIs based on the area of interest received in the Analytics Filter Information or identified by the mapping of the Cells per TAI matching to the Cell granularity included in the Analytics Filter Information. The AMF "S-NSSAIs per TAI mapping" event output contains, for each of the TAIs requested by NWDAF, its associated access type and the list of supported S-NSSAIs (including indication of S-NSSAIs restricted by AMF).
To retrieve data from SMFs for Analytics IDs subscription or requests for "any UE" including Analytics Filter Information with specific Applications, DNNs, DNAIs and area of interest per TA granularity, NWDAF shall first discover the SMF serving the area of interest via NRF.
NOTE 8: Examples of Analytics ID requiring NWDAF to collect data related to PDU sessions associated with an AoI with TA granularity are: network performance clause 6.6.1; user data congestion clause 6.8.1, QoS Sustainability clause 6.9.
NWDAF may directly consume events from the discovered and selected SMF using the event target set to "any PDU session" and event filters with the same parameters of the Analytics Filter Information, i.e. list of Application IDs and/or DNNs and/or DNAI and the area of interest related to the requested Analytics ID.
1. When SMF supports the exchange of UE Location parameter when SMF interacts with AMF via Nsmf_PDUSession_Create/Update/CreateSMContext/UpdateSMContext due to session establishment, modification, or release, service request, or handover procedures (as defined in clause 5.2.8.2 of TS 23.502 [3]), SMF can directly map the PDU sessions to an AoI with TA granularity.
If there are any changes in PDU sessions in the area of interest, for the Application ID and/or DNN and/or DNAI subscribed by NWDAF, SMF notifies the detected changes to NWDAF via Nsmf_EventExposure_Notify service operation, enabling NWDAF to keep an updated map of SMF and PDU sessions associated with the Analytics Filter Information in an area of interest.
2. When SMF does not support the exchange of UE Location parameter when SMF interacts with AMF but supports the mapping of PDU sessions per TA (as defined in clause 5.6.11 of TS 23.501 [2]), SMF may subscribe to UE mobility event notifications of AMF as described in clause 5.3.4.4 of TS 23.501 [2] using event ID "UE moving in or out of Area of Interest" and Event Filters as described in Table 5.2.2.3.1-1 from TS 23.502 [3] to retrieve the list of SUPIs (and GPSIs if available) in the area of interest. Based on the retrieved list of SUPIs in the area of interest, SMF identifies the PDU sessions in the area of interest.
3. When SMF does not support the exchange of UE Location parameter when SMF interacts with AMF nor supports the mapping of PDU sessions per TA (as defined in clause 5.6.11 of TS 23.501 [2]), SMF rejects the request from NWDAF. Upon the reject, NWDAF identifies the need to create the mapping of PDU sessions per TA. NWDAF subscribes to UE mobility event notifications of AMF as described in clause 5.3.4.4 of TS 23.501 [2] using event ID "UE moving in or out of Area of Interest" and Event Filters as described in Table 5.2.2.3.1-1 from TS 23.502 [3] to retrieve the list of SUPIs (and GPSIs if available) in the area of interest. Based on the retrieved list of SUPIs in the area of interest, NWDAF subscribes to the SMFs serving the UEs in the area of interest and derives the mapping of PDU sessions per TA.
To train an ML model or to do ML model performance monitoring for LMF-based AI/ML positioning, the NWDAF can collect input data from LMF as defined in clause 6.22.4 of TS 23.273 [39].
An NWDAF may require to discover and select other NWDAFs for UE related analytics. In this case, the NWDAF may discover from UDM if an NWDAF is already collecting data related to the UE, as specified in clauses 5.2 and 6.1C.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.2.2 Procedure for Data Collection from NFs
| The procedure in Figure 6.2.2.2-1 is used by NWDAF to subscribe/unsubscribe at NFs in order to be notified for data collection on a related event (s), using Event Exposure Services as listed in Table 6.2.2.1-1. Depending on local regulation requirements, user consent for UE related data collection and usage of collected data may be required. User consent is defined for a specific purpose such as, e.g. analytics or model training. NWDAF checks user consent taking the purpose for data collection and usage of these data into account.
Figure 6.2.2.2-1: Event Exposure Subscribe/unsubscribe for NFs
1. The NWDAF checks if data is to be collected for a user, i.e. SUPI or GPSI, then, depending on local policy and regulations, the NWDAF checks the user consent by retrieving the user consent information from UDM using Nudm_SDM_Get including data type "User consent". If user consent is not granted, NWDAF does not subscribe to event exposure for events related to this user and the data collection for this SUPI or GPSI stops here.
2. If the user consent is granted, the NWDAF subscribes to UDM to notifications of changes on subscription data type "User consent" for this user using Nudm_SDM_Subscribe.
3. The NWDAF subscribes to or cancels subscription for a (set of) Event ID(s) by invoking the Nnf_EventExposure_Subscribe/Nnf_EventExposure_Unsubscribe service operation.
NOTE 1: The Event ID(s) are defined in TS 23.502 [3].
4. If NWDAF subscribes to a (set of) Event ID(s), the NFs notify the NWDAF (e.g. with the event report) by invoking Nnf_EventExposure_Notify service operation according to Event Reporting Information in the subscription.
When the Reporting type is provided at step 1, the NWDAF determines that the events are disappeared, if the same events are included in the notification compared to the previous notification. Otherwise, NWDAF determines the events are newly appeared or changed. Also, the NWDAF restores the events that are not included in the notification, but included in the previous notification.
If the Granularity of dynamics is applied to the subscription, the NWDAF shall infer the events in the NF from the events in the previous notification with the applied Granularity of dynamics.
NOTE 2: The Event Reporting Information are defined in TS 23.502 [3].
NOTE 3: The NWDAF can use the immediate reporting flag as defined in Table 4.15.1-1 of TS 23.502 [3] to meet the request-response model for data collection from NFs.
NOTE 4: This procedure is also used when the NWDAF subscribes for data from a trusted AF.
5. The UDM may notify the NWDAF on changes of user consent at any time after step 2.
6-7. If user consent is no longer granted for a user for which data has been collected, the NWDAF shall unsubscribe to any Event ID to collect data for that SUPI or GPSI. The NWDAF may unsubscribe to be notified of user consent updates from UDM for each SUPI for which data consent has been revoked.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.2.3 Procedure for Data Collection from AF via NEF
| The procedure in Figure 6.2.2.3-1 is used by NWDAF to collect information from AFs via the NEF.
NOTE 1: In this release, AF registers its available data to NWDAF via OAM configuration at NEF.
The AF collectable data information includes: AF identification, AF service identification (e.g. endpoint information of Naf_EventExposure), available data to be collected per application (e.g. identified by Event ID(s)).
Figure 6.2.2.3-1: Data Collection from AF via NEF
1a. After the registration of AF available data at the NEF, NEF generates an event exposure with new EventID to be associated with available data to be collected from AF. NEF invokes Nnrf_NFManagement_NFUpdate_request service operation to update its registration information (i.e. NEF Profile) including the generated Event IDs and associated AF identification, Application ID(s) (i.e. internal application ID or Application ID known in the core network).
1b. NRF stores the received NEF registration information including available data to be collected from AF.
1c. NRF sends Nnrf_NFManagement_NFUpdate_response message to NEF.
1d. When NWDAF needs to discovery the available data from AFs and the appropriated NEF to collect this data, NWDAF invokes Nnrf_NFDiscovery_Request_request service operation using as parameter the NEF NF Type and optionally a list of Event ID(s), AF identification and application ID.
1e. NRF matches the requested query for available data in AFs with the registered NEF Profiles and sends this information via Nnrf_NFDiscovery_Request_response message to NWDAF.
NOTE 2: After the registration and discovery procedure described in step 1, NWDAF identifies the available data per AF per application and the proper NEF to collect such data.
2. The NWDAF subscribes to or cancels subscription to data in AF via NEF by invoking the Nnef_EventExposure_Subscribe or Nnef_EventExposure_Unsubscribe service operation. If the event subscription is authorized by the NEF, the NEF records the association of the event trigger and the NWDAF identity.
NOTE 3: User consent for retrieving user data in AF via NEF is not specified in this Release.
3. Based on the request from the NWDAF, the NEF subscribes to or cancels subscription to data in AF by invoking the Naf_EventExposure_Subscribe/ Naf_EventExposure_Unsubscribe service operation.
4. If the NEF subscribes to data in AF, the AF notifies the NEF with the data by invoking Naf_EventExposure_Notify service operation according to Event Reporting Information in the subscription.
5. If the NEF receives the notification from the AF, the NEF notifies the NWDAF with the data by invoking Nnef_EventExposure_Notify service operation.
When the Reporting type is provided at step 2, the NWDAF determines that the events are disappeared, if the same events are included in the notification compared to the previous notification. Otherwise, NWDAF determines the events are newly appeared or changed. Also, the NWDAF restores the events that are not included in the notification, but included in the previous notification.
If the Granularity of dynamics is applied to the subscription, the NWDAF shall infer the events in the AF from the events in the previous notification and the applied Granularity of dynamics.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.2.4 Procedure for Data Collection from NRF
| The NWDAF may use NRF services and Network Function service framework procedures as defined in clause 5.2.7 and clause 4.17 of TS 23.502 [3]:
- NF/NF service discovery procedures (in clause 4.17.4 of TS 23.502 [3]) and Nnrf_NFDiscovery service (in clause 5.2.7.3 of TS 23.502 [3]) in order to dynamically discover the NF instances and services of the 5GC. Such discovery may be performed on a periodic basis, or under specific circumstances.
- NF/NF service status subscribe/notify procedures (in clause 4.17.7 of TS 23.502 [3]) and Nnrf_NFManagement service (in clause 5.2.7.2 of TS 23.502 [3]) in order to be notified about the change of status of an NF. The service operations for obtaining status information are NFStatusSubscribe and NFStatusNotify, from the Nnrf_NFManagement service.
The information provided by the NRF to the NWDAF with the Nnrf_NFDiscovery_Request and the Nnrf_NFManagement_NFStatusNotify service operations are the NF Profiles which includes the supported NF services of the NFs as defined in clause 5.2.7 of TS 23.502 [3]. Such information can be used to set-up and maintain a consistent network map for data collection and also, depending on use cases, to perform analytics (e.g. NF load analytics as defined in clause 6.5).
If the NWDAF needs to keep a consistent network map for data collection from AMFs and SMFs associated with a list of TAs, the subscription to NFStatusSubscribe for such type of NFs may include the list of TAs target.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.2.5 Usage of Exposure framework by the NWDAF for Data Collection
| The NWDAF shall subscribe (and unsubscribe) to the Event exposure service from NF(s) reusing the framework defined in clause 4.15 of TS 23.502 [3]. This framework supports the possibility for the NWDAF to indicate/request:
- Events-ID: one or multiple Event ID(s) defined in clause 4.15.1 of TS 23.502 [3].
- Target of Event Reporting defined in clause 4.15.1 of TS 23.502 [3]: the objects targeted by the Events. Within a subscription, all Event ID(s) are associated with the same target of event reporting. In the case of NWDAF, the objects can be UE(s), UE group(s), any UE.
- Event Filter Information defined in clause 4.15.1 of TS 23.502 [3]. This provides Event Parameter Types and Event Parameter Value(s) to be matched against.
- A Notification Target Address and a Notification Correlation ID as defined in clause 4.15.1 of TS 23.502 [3], allowing the NWDAF to correlate notifications received from the NF with this subscription.
- Event Reporting Information described in TS 23.502 [3] Table 4.15.1-1 and the muted stored events exposure as described in clause 6.2.7.
- Expiry time as defined in clause 4.15.1 of TS 23.502 [3].
The notifications from NFs/AFs contain on top of the Event being reported (and of dedicated information being reported for this event):
- the Notification Correlation Information provided by the NWDAF in its request;
- (when applicable to the event) the Target Id e.g. UE ID (SUPI and if available GPSI); and
- a time stamp.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.3 Data Collection from OAM
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.3.1 General
| The NWDAF may collect relevant management data from the services in the OAM as configured by the PLMN operator.
‐ NG RAN or 5GC performance measurements as defined in TS 28.552 [8].
‐ 5G End to end KPIs as defined in TS 28.554 [10].
‐ 5G application layer measurements from the UEs in the specified area for specified end user service type as defined in TS 28.404 [54], TS 28.405 [55] and TS 28.406 [56].
NWDAF shall use the following services to have access to the information provided by OAM:
- Generic performance assurance and fault supervision management services as defined in TS 28.532 [6].
‐ PM (Performance Management) services as defined in TS 28.550 [7].
‐ FS (Fault Supervision) services defined in TS 28.545 [9].
- MDA (Management Data Analytics) services as defined in TS 28.104 [45].
NWDAF can be configured to invoke the existing OAM services to retrieve the management data that are relevant for analytics generation, which may include NF resources usage information (e.g. usage of virtual resources assigned to NF) and NF resource configuration information (e.g. life cycle changes of NF resource configurations).
OAM perform the required configuration in order to provide the information requested by NWDAF subscription and perform the tasks, e.g. data collection, data processing, associated with the subscribed request from NWDAF.
Another usage of OAM services is when the target of data collection is a specific UE, via MDT based retrieval of information:
- Measurement collection for MDT as defined in TS 37.320 [20].
In addition, NWDAF can be provisioned with Network Slice information (i.e. as defined by the NetworkSliceInfo specified in TS 28.541 [22]) when a slice is created or modified via OAM configuration mechanism as defined in TS 28.541 [22] and TS 28.532 [6].
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.3.2 Procedure for data collection from OAM
| The interactions between NWDAF and OAM for data collection are illustrated in Figure 6.2.3.2-1. The data collected depends on the use cases. This figure is an abstraction of the OAM performance data file report management service that is defined TS 28.532 [6]. The actual OAM services and reporting mechanisms that NWDAF may use are specified in TS 28.532 [6], TS 28.550 [7] or TS 28.545 [9].
The flow below assumes the NWDAF is configured on how to subscribe to the relevant OAM services.
OAM shall setup the required mechanisms to guarantee the continuous data collection requested by NWDAF.
Figure 6.2.3.2-1: Data collection from OAM performance data file report management service
1. (Clause 11.6.1.3.2 of TS 28.532 [6]), Subscribe (Input): NWDAF subscribes to the notification(s) related to the services provided by the management service producer.
2. (Clause 11.6.1.3.3 of TS 28.532 [6]), Subscribe (Output): management service producer responses to NWDAF if the subscription is success or not.
3. Data processing: management service producer prepares the data.
4. (Clause 11.6.1.1 of TS 28.532 [6]), Notification (notifyFileReady): management service producer notifies the data file is ready.
As the final step, NWDAF fetches data by using file transfer protocols as defined in clause 11.6.2 of TS 28.532 [6].
NOTE 1: The call flow in Figure 6.2.3.2-1 only shows a subscribe/notify model for the simplicity, however both request-response and subscription-notification models are supported.
NOTE 2: NWDAF is configured with the Network Slice information (i.e. NetworkSliceInfo including a DN (Distinguished Name) of the NetworkSlice managed object relating to the network slice instance associated to the S-NSSAI and NSI ID if available as defined in TS 28.541 [22]). Based on the Network Slice information, the NWDAF uses the DN (Distinguished Name) to identify the NetworkSlice managed object relating to the S-NSSAI and NSI ID and consumes the management services to collect the management data of the corresponding NetworkSlice managed object (including the NRF serving the network slice, the NFs associated to the network slice, the NG RAN or 5GC performance measurements defined in TS 28.552 [8], or the 5G end to end KPIs defined in TS 28.554 [10]) provided by OAM.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.4 Correlation between network data and service data
| The Correlation information in input data which helps NWDAF correlate data from different NFs, OAM and UE application(s) is defined in Table 6.2.4-1, which is subject to all the network data analytics.
NOTE: For simplicity, the correlation information is not listed in the input data per network data analytics.
Table 6.2.4-1: Correlation Information
Correlation Information
Description
Timestamp, IP address 5-tuple
To correlate the data from AF and from UPF.
Timestamp, AN Tunnel Info (Clause 9.3.2.2 of TS 38.413 [16])
To correlate the UPF data and OAM data which are reported by the RAN (e.g. Reference Signal Received Power or Reference Signal Received Quality as defined in Table 6.4.2-3).
Timestamp, UE IP address
To correlate the data from UPF and SMF.
Timestamp, SUPI
To correlate data from SMF and AMF.
Timestamp, SUPI, DNN, S-NSSAI or UE IP address
To correlate data from SMF and PCF.
Timestamp, RAN UE NGAP ID
(Clause 9.3.3.2 of TS 38.413 [16]) and Global RAN Node ID
To correlate the AMF data and OAM data reported by the RAN (e.g. Reference Signal Received Power or Reference Signal Received Quality as defined in Table 6.4.2-3).
Timestamp, Application ID, IP filter information
To correlate data from SMF and AF.
Timestamp, UE ID or UE IP address, Application ID, DNN, S-NSSAI
To correlate data from 5GC NF (e.g. SMF, UPF) and UE Application (via the AF).
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 6.2.5 Time coordination across multiple NWDAF instances
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.