Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  18.1.0

Top   Top   Up   Prev   Next
1…   5…   7…   7.4…   7.5…   8…   9…   10…   10.1.2…   10.1.3…   10.1.5…   10.2…   10.2.3…   10.2.5…   10.3…   10.7…   10.7.3…   10.7.3.7…   10.7.3.10…   10.8…   10.8.4…   10.9…   10.9.3…   10.9.3.8…   10.10…   10.11…   10.12…   10.13…   10.13.3…   10.14…   10.15…   10.15.3…   11…   11.5…   11.5.2…   11.5.3…   A…   B…

 

11.5  Procedures and information flowsWord‑p. 267

11.5.1  Connection authorisation mechanismsWord‑p. 267

11.5.1.1  GeneralWord‑p. 267

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 clientWord‑p. 267

11.5.1.2.1  GeneralWord‑p. 267
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 client, i.e. the binding between the MC gateway UE and the MC client is authorized and controlled by the MC server.
11.5.1.2.2  Information flowsWord‑p. 267
11.5.1.2.2.1  Connection authorization requestWord‑p. 267
Table 11.5.1.2.2.1-1 describes the information flow connection authorization request sent from the MC 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 responseWord‑p. 267
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 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 procedureWord‑p. 267
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 client has been configured with the necessary parameters needed for connectivity with the MC gateway UE.
  • The MC client 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.
  • The MC service user has selected an MC gateway UE or alternatively, the MC client has performed a selection by internal criteria.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 11.5.1.2.3-1: Connection authorisation with an MC server via an MC gateway UE
Up
Step 1.
The MC client requests connection authorization via the MC gateway UE with an MC server. The client of the MC service user 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 by the MC service gateway. The MC gateway UE may also check whether sufficient resources are avaible 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.
Step 5.
The MC server sends the connection authorization response to the MC gateway UE.
Step 6.
The MC gateway UE marks the MC 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 client.
After successful connection with the MC gateway UE, the MC client has 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 clientWord‑p. 269

11.5.1.3.1  GeneralWord‑p. 269
The solution 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 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 flowsWord‑p. 269
11.5.1.3.2.1  Connection authorization requestWord‑p. 269
Table 11.5.1.3.2.1-1 describes the information flow connection authorization request sent from the MC 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 responseWord‑p. 269
Table 11.5.1.3.2.2-1 describes the information flow connection authorization response sent from the MC server to the MC 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 procedureWord‑p. 269
The procedure for connection authorisation of an MC 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 client is hosted by the MC gateway UE.
  • The MC service user has selected an MC gateway UE or alternatively, the non-3GPP has performed a selection by internal criteria.
  • The MC 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.
Copy of original 3GPP image for 3GPP TS 23.280, Fig. 11.5.1.3.3-1: Connection authorisation of an MC client hosted by an MC gateway UE
Up
Step 1.
The MC 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.
Step 3.
The MC server sends the connection authorization response to the MC client residing on the MC gateway UE.
The MC 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