Content for TS 23.180 Word version: 18.0.0
10 Procedures and information flows
10.1 User authentication in the IOPS mode of operation
10.2 IOPS discovery (IP connectivity functionality)
...
...
10 Procedures and information flows p. 19
10.1 User authentication in the IOPS mode of operation p. 19
10.1.1 General p. 19
The following clause describes a high level procedure used for the user authentication in the IOPS mode of operation.
10.1.2 Procedure p. 19
A procedure for the user authentication in the IOPS mode of operation is illustrated in Figure 10.1.2-1.
Step 1.
The IOPS connectivity client initiates the IOPS user authentication procedure with the IOPS MC connectivity function.
10.2 IOPS discovery (IP connectivity functionality) p. 20
10.2.1 General p. 20
The support of the IP connectivity functionality in the IOPS mode of operation enables that MC services are provided by the MC service clients via the IOPS MC connectivity function. An IOPS MC connectivity function provides IP connectivity for the communication among MC service users based on an IOPS discovery procedure.
The IOPS discovery procedure enables that the IOPS MC connectivity function discovers MC service users within the coverage of the system and receives connectivity information required to establish a communication between discovered users based on the IP connectivity functionality.
The following clauses specify the IOPS discovery procedure and information flows for the IP connectivity functionality in the IOPS mode of operation.
10.2.2 Information flows p. 20
10.2.2.1 IP connectivity request p. 20
Table 10.2.2.1-1 describes the information flow for the IP connectivity request from the IOPS connectivity client to the IOPS MC connectivity function.
| Information Element | Status | Description |
|---|---|---|
| IOPS MC service ID | M | The IOPS MC service ID of the user requesting support of the IP connectivity functionality |
10.2.2.2 IP connectivity response p. 20
Table 10.2.2.2-1 describes the information flow for the IP connectivity response from the IOPS MC connectivity function to the IOPS connectivity client.
| Information Element | Status | Description |
|---|---|---|
| IOPS MC service ID | M | The IOPS MC service ID of the user requesting support of the IP connectivity functionality |
| IP connectivity support | M | It indicates if the IP connectivity functionality is supported or not for the user |
10.2.2.3 IOPS discovery request p. 20
Table 10.2.2.3-1 describes the information flow for the IOPS discovery request from the IOPS connectivity client to the IOPS MC connectivity function.
| Information Element | Status | Description |
|---|---|---|
| IOPS MC service ID | M | The IOPS MC service ID of the requesting MC user |
| IP connectivity information | M | It includes the requesting MC service UE's IP address (NOTE 1) |
| List of IOPS MC service group ID (NOTE 2) | M | It includes the IOPS group (IOPS MC service group ID and its associated IOPS group IP multicast address) or list of IOPS groups the requesting MC user is configured with |
| Availability of connectivity information | O | It indicates if the connectivity information of the requesting MC user can be made available to other users on the system |
| List of IOPS MC service IDs (NOTE 2 and NOTE 3) | O | The specific list of IOPS MC service IDs that the requesting MC user's connectivity information can be shared with |
| Priority state | M | Indicates whether the requesting MC user is requesting higher priority or not |
|
NOTE 1:
The MC service UE's IP address is assigned by the IOPS EPS based on the PDN connection established by the MC user for the IOPS IP connectivity functionality.
NOTE 2:
The list of IOPS MC service IDs or IOPS MC service group IDs shall be of the same MC service as the MC user requesting to be discovered.
NOTE 3:
If present, the user's connectivity information availability can be only made available to the provided specific list of IOPS MC service IDs.
|
||
10.2.2.4 IOPS discovery response p. 21
Table 10.2.2.4-1 describes the information flow for the IOPS discovery response from the IOPS MC connectivity function to the IOPS connectivity client.
| Information Element | Status | Description |
|---|---|---|
| IOPS MC service ID | M | The IOPS MC service ID of the user requesting to be discovered |
| Connectivity status | M | It indicates the connectivity status of the requesting MC user on the system |
| IOPS discovery request periodicity | M | It indicates the periodicity at which the requesting MC user is required to transmit IOPS discovery requests (NOTE) |
|
NOTE:
An MC user is required to periodically transmit an IOPS discovery request. The periodic IOPS discovery requests are used by the IOPS MC connectivity function to verify the availability of the MC user and its IP connectivity information within the IOPS MC system.
|
||
10.2.3 Procedure p. 21
After an MC service user is authenticated on the IOPS MC connectivity function, the IOPS discovery procedure is initiated by the MC users requesting support of the IP connectivity functionality to the IOPS MC connectivity function. If the IOPS MC connectivity function indicates the support of the IP connectivity functionality, the MC service users can send an IOPS discovery request.
The procedure for requesting support of the IP connectivity functionality by the IOPS connectivity client to the IOPS MC connectivity function is described in Figure 10.2.3-1.
Pre-conditions:
- The MC service user is authenticated on the IOPS MC connectivity function.
- The MC service user has an active PDN connection to the IOPS MC connectivity function for the specific IP connectivity functionality procedure
- The IOPS connectivity client does not contain information about the support of the IP connectivity functionality by the serving IOPS MC connectivity function
Figure 10.2.3-1: IP connectivity functionality request in the IOPS mode of operation
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Step 1.
The procedure for the discovery of MC users in the IOPS mode of operation is described in Figure 10.2.3-2. The IOPS discovery is initiated by the MC users to support MC services based on the IP connectivity functionality.
As part of the IOPS discovery procedure, an MC user can request higher priority from the IOPS MC connectivity function by including a priority state indication within the IOPS discovery request. Based on this indication, the IOPS MC connectivity function can decide to handle with higher priority the transactions related to the MC user, e.g. the distribution of packets related to any MC communication from or to the corresponding MC user, subscriptions, and notifications. When an MC user intends to establish an IOPS emergency (group or private) call, the MC user can request a priority state from the IOPS MC connectivity function.
The MC user's priority state remains unchanged until the MC user explicitly changes it (i.e. by sending a new IOPS discovery request) or the discovery status of the MC user changes to not-discovered on the IOPS MC connectivity function.
Pre-conditions:
The IOPS connectivity client requests to the IOPS MC connectivity function the support of the IP connectivity functionality.
Step 2.
The IOPS MC connectivity function indicates to the IOPS connectivity client if the IP connectivity functionality is supported or not for the MC user.
- The MC service user is authenticated on the IOPS MC connectivity function.
- The MC service user has an active PDN connection to the IOPS MC connectivity function for the specific IP connectivity functionality procedure
- The IOPS MC connectivity function has indicated to the IOPS connectivity client the support of the IP connectivity functionality.
Step 1.
The MC user sends an IOPS discovery request to the IOPS MC connectivity function. The request includes providing connectivity information for the support of MC services based on the IP connectivity functionality.
Step 2.
The IOPS MC connectivity function stores the information received from the MC user and registers the user's connectivity status as discovered.
Step 3.
The IOPS MC connectivity function provides a response to the IOPS connectivity client indicating the success or failure of the discovery of the requesting MC user.
