Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.280  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.17…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C… 
11.5 Procedures and information flows  11.5.1 Connection authorisation mechanisms  11.5.1.1 General  11.5.1.2 Connection authorisation for non-3GPP devices that host an MC client  11.5.1.2.1 General  11.5.1.2.2 Information flows  11.5.1.2.2.1 Connection authorization request  11.5.1.2.2.2 Connection authorization response  11.5.1.2.3 Connection authorisation procedure  11.5.1.3 Connection authorisation for non-3GPP devices that do not host an MC client  11.5.1.3.1 General  11.5.1.3.2 Information flows  11.5.1.3.2.1 Connection authorization request  11.5.1.3.2.2 Connection authorization response  11.5.1.3.3 Connection authorisation procedure 
...

 

11.5  Procedures and information flows  p. 328

11.5.1  Connection authorisation mechanisms  p. 328

11.5.1.1  General  p. 328

The connection of non-3GPP devices via an MC gateway UE require authorisation verification by the MC system. Two different types of non-3GPP devices are supported, those which can host MC service client and those which cannot host MC service clients.

11.5.1.2  Connection authorisation for non-3GPP devices that host an MC client  p. 328

11.5.1.2.1  General  p. 328
The solution is applied to non-3GPP devices which can host an MC client. The MC server performs authorization for the use of the MC gateway UE by the MC gateway client, i.e. the binding between the MC gateway UE and the MC gateway client is authorized and controlled by the MC server. The MC gateway client informs MC clients about the connection status.
For the period of association between MC server, MC gateway client and MC gateway UE, the MC server maintains the assignment between MC clients to the MC gateway UE used. This assignment is cancelled again with the disconnection.
Up
11.5.1.2.2  Information flows  p. 329
11.5.1.2.2.1  Connection authorization request  p. 329
Table 11.5.1.2.2.1-1 describes the information flow connection authorization request sent from the MC gateway client, which resides on a non-3GPP device, to the MC gateway UE, and from the MC gateway UE to the MC server.
Information element Status Description
GW MC service IDMThe GW MC service ID of the requesting MC service user.
NOTE:
The GW MC service ID indicates for which MC service the connection is to be authorised.
Up
11.5.1.2.2.2  Connection authorization response  p. 329
Table 11.5.1.2.2.2-1 describes the information flow connection authorization response sent from the MC server to the MC gateway UE, and from the MC gateway UE to the MC gateway client residing on a non-3GPP device.
Information element Status Description
GW MC service IDMThe GW MC service ID of the requesting MC service user.
ResponseMResult of the connection authorization request, service feasibility, and connection evaluation.
Up
11.5.1.2.3  Connection authorisation procedure  p. 329
The procedure for connection authorisation via an MC gateway UE towards an MC server is shown in Figure 11.5.1.2.3-1.
Pre-conditions
  • The MC service user wishes to have access to MC services using a non-3GPP device.
  • The MC gateway client has been configured with the necessary parameters needed for connectivity with the MC gateway UE.
  • The MC gateway client hosted at the non-3GPP device has been provided with an appropriate GW MC service ID.
  • The MC gateway UE has performed service authorization for one or more MC services with the MC system as described in TS 23.379, TS 23.281, and TS 23.282.
  • The MC gateway client has selected an MC gateway UE or alternatively, the MC gateway client has performed a selection by internal criteria.
Reproduction of 3GPP TS 23.280, Fig. 11.5.1.2.3-1: Connection authorisation with an MC server via an MC gateway UE
Figure 11.5.1.2.3-1: Connection authorisation with an MC server via an MC gateway UE
Up
Step 1.
The MC gateway client requests connection authorization via the MC gateway UE with an MC server. The MC gateway client provides the GW MC service ID.
Step 2.
The MC gateway UE checks whether the requested MC service, as indicated by the GW MC service ID, is supported. The MC gateway UE may also check whether sufficient resources are available or if any other local criteria are met. If the MC service is supported, the procedure continues with step 3, otherwise the procedure proceeds with step 7.
Step 3.
The MC gateway UE sends the connection authorization request to the MC server.
Step 4.
The MC server performs an authorization check, to verify that access via the MC gateway UE is permitted. An MC server shall reject the connection authorization when the MC server receives connection authorization from a MC gateway client for a particular MC service for which the connection already exists with the same or different MC gateway UE.
Step 5.
The MC server sends the connection authorization response to the MC gateway UE.
Step 6.
The MC gateway UE marks the MC gateway client as authorized to have MC service access via the MC gateway UE.
Step 7.
The MC gateway UE sends the connection authorization response to the MC gateway client.
After successful connection with the MC gateway UE, the MC clients have access to the MC server and may continue with user authentication and service authorization.
If the MC service user wishes to have access to another MC service, the above procedure is repeated. The MC service user may select a different MC gateway UE for the new MC service, if multiple MC gateway UEs are available.
Up

11.5.1.3  Connection authorisation for non-3GPP devices that do not host an MC client  p. 330

11.5.1.3.1  General  p. 330
The clause is applied to non-3GPP devices which cannot host an MC client. The MC server performs authorization for the use of the MC gateway UE by the MC gateway client, i.e. the binding between the MC gateway UE and the MC client is authorized and controlled by the MC server.
Up
11.5.1.3.2  Information flows  p. 331
11.5.1.3.2.1  Connection authorization request  p. 331
Table 11.5.1.3.2.1-1 describes the information flow connection authorization request sent from the MC service client, which resides on a MC gateway UE, to the MC server.
Information element Status Description
GW MC service IDMThe GW MC service ID of the requesting MC service user.
NOTE:
The GW MC service ID indicates for which MC service the connection is to be authorised.
Up
11.5.1.3.2.2  Connection authorization response  p. 331
Table 11.5.1.3.2.2-1 describes the information flow connection authorization response sent from the MC server to the MC gateway client residing on the MC gateway UE.
Information element Status Description
GW MC service IDMThe GW MC service ID of the requesting MC service user.
ResultMSuccess or failure of the connection authorization request (authorization successful/failed; service not supported).
Up
11.5.1.3.3  Connection authorisation procedure  p. 331
The procedure for connection authorisation of an MC gateway client hosted by the MC gateway UE towards an MC server is shown in Figure 11.5.1.3.3-1.
Pre-conditions
  • The MC service user wishes to have access to MC services using a non-3GPP device, where the MC gateway client and MC clients are hosted by the MC gateway UE.
  • The MC gateway client has selected an MC gateway UE or alternatively, the non-3GPP has performed a selection by internal criteria.
  • The MC gateway client, which is hosted by the MC gateway UE, has been configured with the necessary parameters needed for connectivity with the MC gateway UE.
  • The MC gateway UE has performed service authorization for one or more MC services with the MC system as described in TS 23.379, TS 23.281, and TS 23.282].
Reproduction of 3GPP TS 23.280, Fig. 11.5.1.3.3-1: Connection authorisation of an MC gateway client hosted by an MC gateway UE
Figure 11.5.1.3.3-1: Connection authorisation of an MC gateway client hosted by an MC gateway UE
Up
Step 1.
The MC gateway client, hosted by the MC gateway UE, requests connection authorization with an MC server by providing the GW MC service ID. The MC gateway UE sends the connection authorization request to the MC server.
Step 2.
The MC server performs an authorization check, to verify that access using the MC gateway UE is permitted. An MC server shall reject the connection authorization when the MC server receives connection authorization from a MC gateway client for a particular MC service for which the connection already exists with the same or different MC gateway UE.
Step 3.
The MC server sends the connection authorization response to the MC gateway client residing on the MC gateway UE.
The MC gateway client has now access to the MC server and may continue with user authentication and service authorization.
If the MC service user wishes to have access to another MC service, the above procedure is repeated. The MC service user may select a different MC gateway UE for the new MC service, if multiple MC gateway UEs are available.
Up

Up   Top   ToC