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.
The procedure for connection authorisation via an MC gateway UE towards an MC server is shown in Figure 126.96.36.199.3-1
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.
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.
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.
The MC gateway UE sends the connection authorization request to the MC server.
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.
The MC server sends the connection authorization response to the MC gateway UE.
The MC gateway UE marks the MC gateway client as authorized to have MC service access via the MC gateway UE.
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.