hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.11.4.2.2 Location information notification procedure
|
10.11.4.2.2.1 Location information notification procedure (IWF to LMS)
The IWF in the LMR system provides location information, based on some decision or event, to the LMS. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.2.1-1 illustrates the high level procedure of notification of location information.
Figure 10.11.4.2.2.1-1: Event-triggered location information notification procedure
1. The IWF in the LMR system determines that it has location information available that is to be notified to the LMS in the MC system.
2. The IWF in the LMR system sends the IWF Location information notification to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.5.
10.11.4.2.2.2 Location information notification procedure (LMS to IWF)
The LMS in the MC system provides location information to the IWF in the LMR system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.2.2-1 illustrates the high level procedure of notification of location information.
Figure 10.11.4.2.2.2-1: Event-triggered location information notification procedure
1. The LMS in the MC system determines that it has location information available that is to be notified to the IWF in the LMR system.
2. The LMS in the MC system sends the IWF Location information notification to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.5.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.11.4.2.3 Location information subscription procedure
|
10.11.4.2.3.1 Location information subscription procedure (LMS to IWF)
An IWF Location information subscription request is sent from the MC system to the IWF. The IWF in the LMR system sends an IWF location information subscription response. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.3.1-1 illustrates the high level procedure of subscription to location information from the LMS in the MC system to the IWF in the LMR system.
Figure 10.11.4.2.3.1-1: Location information subscription procedure
1. The MC service server or the LMC in the MC system sends a request for subscription to event-triggered location information of LMR users that appear as MC service users in the LMR system by sending a location information subscription request to the LMS in the MC system, according to the described information flows in clause 10.9.2.5 in 3GPP TS 23.280 [5].
2. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.
3. The LMS in the MC system determines that the request has a target in an LMR system.
4. The LMS in the MC system sends the IWF Location information subscription request to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.3.
5. The IWF in the LMR system can check if the provided information along with the configuration permit the request to proceed.
6. The IWF in the LMR system applies the subscription.
7. The IWF in the LMR system sends the IWF Location information subscription response to the LMS in the MC system according to the described information flow in clause 10.11.4.1.4. The LMS in the MC system can respond to the LMC or MC server in the MC system per the procedures of 3GPP TS 23.280 [5].
10.11.4.2.3.2 Location information subscription procedure (IWF to LMS)
An IWF Location information subscription request is sent from the MC system to the IWF. The IWF in the LMR system sends an IWF Location information subscription response. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.3.2-1 illustrates the high level procedure of subscription to location information from the LMS in the MC system to the IWF in the LMR system.
Figure 10.11.4.2.3.2-1: Location information subscription procedure
1. The IWF in the LMR system determines that it needs to subscribe to location information notifications for an MC service user.
2. The IWF in the LMR system determines that the request has a target in the MC system.
3. The IWF in the LMR system sends the IWF Location information subscription request to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.3.
4. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
5. The LMS in the MC system applies the subscription.
6. The LMS in the MC system sends the IWF Location information subscription response to the LMS in the MC system according to the described information flow in clause 10.11.4.1.4.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.11.4.2.4 Location information cancel subscription procedure
|
10.11.4.2.4.1 Location information cancel subscription procedure (LMS to IWF)
The LMC in the MC system receives location information updates according to the subscriptions requested in the LMR system per clause 10.11.4.2.3. Those subscriptions can be cancelled anytime from the MC system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.4.1-1 illustrates the high level procedure of the subscription cancellation to location information from the MC system to the LMR system.
Figure 10.11.4.2.4.1-1: Location information cancel subscription procedure
1. The MC service server or the LMC in the MC system requests the cancellation of subscriptions to event-triggered location information of LMR users that appear as MC service users in the LMR system by sending location information cancel subscription requests to the LMS in the MC system, according to the described information flows in clause 10.9.2.8 in 3GPP TS 23.280 [5].
2. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
NOTE: Whether the authorization check is a specific MC service user based check or is a general policy check is outside the scope of this procedure.
3. The LMS in the MC system determines that the request has a target in an LMR system.
4. The LMS in the MC system sends the IWF Location information cancel subscription request to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.6.
5. The IWF in the LMR system can check if the provided information along with the configuration permit the request to proceed.
6. The IWF in the LMR system cancels the subscription.
7. The IWF in the LMR system sends the IWF Location information cancel subscription response to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.7. The LMS can forward the location information cancel subscription response per the procedures in 3GPP TS 23.280 [5].
10.11.4.2.4.2 Location information cancel subscription procedure (IWF to LMS)
The IWF in the LMR system receives location information updates according to the subscriptions requested in the MC system per clause 10.11.4.2.3.2. Those subscriptions can be cancelled anytime from the LMR system. The IWF can translate, as needed, between MC service identities and identities used within the LMR system.
Figure 10.11.4.2.4.2-1 illustrates the high level procedure of the subscription cancellation to location information from the LMR system to the MC system.
Figure 10.11.4.2.4.2-1: Location information cancel subscription procedure
1. The IWF in the LMR system determines that a location information subscription is to be cancelled.
2. The IWF in the LMR system determines that the request has a target in the MC system.
3. The IWF in the LMR system sends the IWF Location information cancel subscription request to the LMS in the MC system, according to the described information flow in clause 10.11.4.1.6.
4. The LMS in the MC system checks if the provided information along with the configuration permit the request to proceed.
5. The LMS in the MC system cancels the subscription.
6. The LMS in the MC system sends the IWF Location information cancel subscription response to the IWF in the LMR system, according to the described information flow in clause 10.11.4.1.7.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.12 LMR security transport
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.12.1 Information flows for LMR security transport
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.12.1.1 Non-3GPP security message
|
Table 10.12.1.1-1 describes the information flow non-3GPP security message from the MC service server to the IWF, from the IWF to the MC service server, from the MC service server to the MC service client and from the MC service client to the MC service server.
Table 10.12.1.1-1: Non-3GPP security message
Information Element
Status
Description
MC service ID
M
The MC service identity supporting the sending LMR security entity
MC service ID
M
The MC service identity supporting the LMR security entity towards which the data is sent
LMR type
O
The LMR technology, e.g. TETRA, P25. Required when sent toward the MC service client.
Payload
M
Opaque payload. Contents and format are out of 3GPP scope.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.12.1.2 Void
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.12.2 LMR key management messages
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.12.2.1 General
|
This subclause defines end to end messaging to convey the non-3GPP, LMR security information opaquely (message contents are out of 3GPP's scope) across the MC system, between the IWF and the LMR aware MC service client. The end to end messages are service independent, any MC service may support them.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.12.2.2 MC service client initiated
|
Figure 10.12.2.2-1 describes the case where an MC service client sends LMR security information to the IWF.
Pre-conditions:
1. The MC service client is registered and the user is authenticated and authorized to use the MC service server.
Figure 10.12.2.2-1: Non-3GPP security messaging, MC service client to the IWF
1. The MC service client sends a non-3GPP security message to the MC service server. The contents of the message are opaque to the MC service and are out of scope of 3GPP.
2. The MC service server forwards the contents of the non-3GPP security message to the IWF.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.12.2.3 IWF initiated
|
Figure 10.12.2.3-1 describes the case where the IWF sends LMR security information to an MC service client.
Pre-conditions:
1. The MC service client is registered and the user is authenticated and authorized to use the MC service server.
Figure 10.12.2.3-1: Non-3GPP security messaging, from the IWF to MC service client
1. The IWF sends a non-3GPP security message to the MC service server. The contents of the message are opaque to the MC service and are out of scope of 3GPP.
2. The MC service server forwards the contents of non-3GPP security message to the MC service client.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.13 Analogue FM/TIA-603-D and other legacy LMR interworking
| |
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.13.1 General
|
An IWF representing an LMR user can support interworking with legacy analogue FM radio systems that are compliant with the TIA-603-D [9] Standard. This type of legacy LMR system is sometimes referred to as conventional FM radio.
Characteristics of legacy conventional FM radio include:
- Voice media is conveyed without the use of a voice codec.
- There is no possibility of end-to-end encryption between an LMR user and a MC user.
- Group communication is possible using various means to identify a group such as a single channel / FM frequency, or sub-audible data as defined in [3]. The means for identifying groups within the legacy conventional FM system is outside the scope of the present document.
- The ID of the talking party is generally not available. Various means to identify a talker are available in legacy conventional FM systems, but this is outside the scope of the present document.
- Indication of call priority (e.g. emergency) is generally not available. Various means to identify priority are available in legacy conventional FM systems, but this is outside the scope of the present document.
Other legacy LMR systems such as digital conventional (e.g. P25 conventional), trunked analogue FM systems, non-standard legacy LMR systems, both conventional and trunked, can also be supported as long as they conform to the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.13.2 Interworking Concepts
|
Procedures defined in the present document are applicable to interworking with legacy analogue FM radio systems.
Architecture concepts for interworking are summarized below, including general information for other legacy conventional radio systems.
- The IWF is configured with knowledge of groups and users from legacy conventional LMR radio systems. Translations to MCPTT Group and MCPTT User IDs is performed by the IWF as specified in the present document. How the legacy LMR conventional system supports groups, such as mapping a group to a channel/frequency, or using a Group ID (i.e. P25 conventional), or mapping some other protocol element or tone signalling to a group is outside the scope of the present document.
- Interworking to a legacy conventional LMR system can make use of the following procedures as defined in the present document:
- affiliation;
- group management including group regrouping
- group calls including pre-arranged, chat, and broadcast;
- priority calls including emergency and imminent peril; and
- private calls.
NOTE 1: Some analogue FM conventional LMR systems and digital conventional LMR systems support various schemes for private call. These can be supported as long as they conform to the present document.
- Interworking to a legacy conventional LMR system can make use of the following functions of the MCPTT system, as defined in the present document:
- transcoding.
- Interworking to a legacy conventional LMR system can make use of the following functions of the MCPTT system, as defined in the present document, with some limitations:
- caller ID / talker ID;
- priority indication (e.g. emergency);
- end-to-end encryption;
- location; and
- short data service.
NOTE 2: Some digital conventional LMR systems, such as P25 Conventional, natively support group IDs, user IDs, short data, and priority indication. In some cases, the talker ID becomes available sometime after the call starts.
NOTE 3: Some analogue FM conventional LMR systems support various schemes for caller ID, emergency, and other features (e.g. Multi-tone, Type 99). These can be supported as long as they conform to the present document. In some cases, the talker ID becomes available sometime after the call starts.
NOTE 4: Some digital conventional LMR systems, such as P25 Conventional, can support end-to-end encryption between the LMR user and a MC user. There is no possibility of end-to-end encryption between an analogue FM LMR user and a MC user.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.13.3 Procedures
|
As described above, existing procedures in this document can be used for interworking with legacy conventional LMR radio systems.
The following procedures describe special cases where the MCPTT ID (i.e. talker ID) is updated during a media transmission within a call. This mechanism of updating the MCPTT ID part way through an MCPTT media transmission may be used for any MCPTT media transmission described elsewhere in the present document.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.13.3.1 Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system
|
In this procedure, an LMR user in a legacy conventional FM radio system initiates a group call on an interworking group defined in the MCPTT system. The talker ID is not known at the start of the call and is updated after media transmission begins. The signalling procedure is described in figure 10.13.3.1-1.
This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the interworking group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. The LMR user in a legacy conventional FM radio system initiates a group call.
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.13.3.1-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system
1. The IWF sends an IWF group call request to the MCPTT server for call establishment. In this case floor control is also requested and an indication of implicit floor request is included. The IWF uses its pre-configured MCPTT ID in the group call request.
2. The MCPTT server calls the affiliated users from the MCPTT system as described in 3GPP TS 23.379 [7]. The LMR user is in a legacy conventional FM radio system so E2EE is not specified, and transcoding is needed at the IWF.
3. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF group call request is sent to the IWF for each affiliated LMR user.
NOTE 2: Steps 2 and 3 can occur in any order.
NOTE 3: How the LMR users from the LMR system are being called is outside the scope of the present document.
4. The IWF returns IWF group call response(s) to the MCPTT server.
5. The MCPTT server confirms the successful establishment of the group call by sending an IWF Group call response to the IWF.
NOTE 4: How the group call response is returned to the initiating LMR user is outside the scope of the present document.
6. The interworking group call has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control.
NOTE 5: How the floor control is managed in the LMR system is outside the scope of the present document.
7. Because the group call request contained an imlicit floor request, and no other users are requesting the floor, the MCPTT server sends an IWF floor granted message to the IWF confirming that the IWF has the floor. The MCPTT server also sends Floor taken messages to the affiliated users in the MCPTT system. The MCPTT ID in the floor taken messages is the pre-configured IWF MCPTT ID.
8. If the group has other affiliated LMR users than the calling party, and the MCPTT server has received individual affiliations from those LMR users, an individual IWF floor taken message is sent to the IWF for each affiliated LMR user.
9. At some time after media transfer begins, the IWF receives knowledge of the LMR user's talker ID.
NOTE 6: How the IWF learns the LMR user's talker ID is outside the scope of the present document. In some LMR conventional systems, the talker ID becomes available shortly after the start of the call; in other systems, it is not available until the end of the call.
10. The IWF sends an IWF talker ID update to the MCPTT server informing the server that a new talker is using the floor, but the floor should not be released.
11. The MCPTT server sends Floor taken messages to the affiliated users in the MCPTT system. The MCPTT ID in the floor taken messages is the new talker ID contained in the IWF talker ID update.
NOTE 7: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn the identity of the newly granted talker.
12. If the group has other affiliated LMR users than the calling party, and the MCPTT server has received individual affiliations from those LMR users, an individual IWF floor taken message is sent to the IWF for each affiliated LMR user.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.13.3.2 Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system
|
In this procedure, an LMR user in a legacy conventional FM radio system initiates a group call on an interworking group defined in the LMR system. The talker ID is not known at the start of the call and is updated after media transmission begins. The signalling procedure is described in figure 10.13.3.2-1.
This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2.
Pre-conditions:
1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system.
2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service.
3. The users in this interworking group have been affiliated to the interworking group.
4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF.
5. The LMR user in a legacy conventional FM radio system initiates a group call.
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.13.3.2-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system
1. The IWF sends an IWF group call request(s) to the MCPTT server for call establishment. An individual IWF group call request is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. In this case floor control is also requested and an indication of implicit floor request is included. The IWF uses its pre-configured MCPTT ID in the group call request.
2. The MCPTT server sends a group call request(s) to the target MCPTT user(s) as described in 3GPP TS 23.379 [7]. The LMR user is in a legacy conventional FM radio system so E2EE is not specified, and transcoding is needed at the IWF.
3. MCPTT client(s) receiving the group call request, acknowledge towards the MCPTT server by sending a group call response.
4. The MCPTT server acknowledges the IWF group call request(s) by sending an IWF group call response(s) to the IWF.
NOTE 2: How the IWF group call response(s) is handled in the IWF / LMR system and how the other LMR users are being called is outside the scope of the present document.
5. The interworking group call has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control.
NOTE 3: How the floor control is managed in the LMR system is outside the scope of the present document.
6. Because the group call request contained an implicit floor request, and no other users are requesting the floor, the IWF sends an IWF floor taken message to the MCPTT server confirming that the IWF has the floor. An individual IWF floor taken message is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2.
7. The MCPTT server sends Floor taken to the target MCPTT user(s) in the MCPTT system. The MCPTT ID in the floor taken messages is the pre-configured IWF MCPTT ID.
8. At some time after media transfer begins, the IWF receives knowledge of the LMR user's talker ID.
NOTE 4: How the IWF learns the LMR user's talker ID is outside the scope of the present document. In some LMR conventional systems, the talker ID becomes available shortly after the start of the call; in other systems, it is not available until the end of the call.
9. The IWF sends an IWF floor taken to the MCPTT server informing the server that a new talker is using the floor, but the floor should not be released. An individual IWF floor taken message is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2
10. The MCPTT server sends Floor taken messages to the target MCPTT user(s) in the MCPTT system. The MCPTT ID in the floor taken messages is the new talker ID contained in the IWF talker ID update.
NOTE 5: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn the identity of the newly granted talker.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.14 IWF functional alias management
| |
206be7a57129464f73be1aa9d853095b
|
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].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.14.2 IWF information flows for functional alias management
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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).
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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).
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.14.3 IWF Functional alias management procedures
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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).
|
206be7a57129464f73be1aa9d853095b
|
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).
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.15 First-to-answer call setup
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.15.2 Information flows for first-to-answer call
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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
|
206be7a57129464f73be1aa9d853095b
|
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
|
206be7a57129464f73be1aa9d853095b
|
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
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.15.3 Procedures
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.16 Enhanced status
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.16.3 Enhanced status for on-network
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.17 Ad hoc group call
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.17.2 Information flows for ad hoc group call
| |
206be7a57129464f73be1aa9d853095b
|
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].
|
206be7a57129464f73be1aa9d853095b
|
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].
|
206be7a57129464f73be1aa9d853095b
|
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].
|
206be7a57129464f73be1aa9d853095b
|
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].
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
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].
* * * Next Change * * * *
|
206be7a57129464f73be1aa9d853095b
|
23.283
|
10.17.3 Procedures
| |
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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).
|
206be7a57129464f73be1aa9d853095b
|
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.
|
206be7a57129464f73be1aa9d853095b
|
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
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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".
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
3 Definitions and abbreviations
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
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 is composed of the number of correct predictions of the analytics ID out of all predictions and the corresponding number of samples.
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 is composed of the number of correct predictions by the ML Model out of all predictions and the corresponding number of samples.
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).
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
4 Reference Architecture for Data Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
4.2 Non-roaming architecture
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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)
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
5 Network Data Analytics Functional Description
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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 indication of supporting model training for LMF-based AI/ML Positioning and positioning case information (e.g. UE assisted LMF-based AI/ML Positioning case, NG RAN assisted LMF-based AI/ML Positioning case, or both). 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 indication of supporting model training for LMF-based AI/ML Positioning in a backward compatible and extensible manner is up to stage 3.
Editor's note: Whether the AI/ML positioning model needs to be trained per case (i.e. case 2b, case 3b) is FFS, this needs coordination with RAN WGs.
- 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 may include in the request an indication that supporting of ML Model training for LMF-based AI/ML Positioning is required. 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) and Time interval supporting VFL if available.
To discover NWDAF supporting VFL from NRF, the consumer should consider the VFL capability information. For NWDAF as VFL server or NWDAF as VFL client, NWDAF also includes its VFL interoperability indicator(s) per Analytics ID, optionally with supported feature ID(s) 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. When NFs (i.e. NWDAF and/or AF) 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, i.e. VFL training and/or VFL inference. 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 8: There are no standardized feature ID in this release, and only feature IDs related to static/preconfigured feature information can be registered to NRF.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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, 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).
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 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.
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 accuracy of the VFL model.
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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 certain NFs (i.e. NWDAF and/or AF) 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_3daData Management 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_3daData_Management 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 are composed of the number of correct predictions out of all predictions and the corresponding number of samples.
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.
- Accuracy 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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6 Procedures to Support Network Data Analytics
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.1 Procedures for analytics exposure
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.1.1 Analytics Subscribe/Unsubscribe
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.1.2 Analytics Request
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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 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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.1.4 Analytics Exposure using DCCF
| |
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
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.
|
e596a2ada7ffa79b8d63b0ea972e234a
|
23.288
|
6.1.5 Analytics Exposure in Roaming Case
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.