8.2.2 MSGin5G UE De-Registration

23.5543GPPApplication architecture for MSGin5G ServiceRelease 18Stage 2TS

By de-registering, the MSGin5G UE informs the MSGin5G Server that it wishes to terminate its association with the MSGin5G Server.

NOTE 1: De-registration implies that Client Triggering Information and the Client Communication Availability Information are no longer valid.

The procedure assumes that the MSGin5G UE is responsible for initiating the de-registration from the MSGin5G Server. The signalling flow for MSGin5G UE de-registration is illustrated in figure 8.2.2-1.

Pre-conditions:

1. The MSGin5G UE is registered to the MSGin5G Server.

Figure 8.2.2-1: MSGin5G UE de-registration

1. The MSGin5G UE determines to de-register from the MSGin5G Server.

2. The MSGin5G UE sends an MSGin5G UE de-registration request to the MSGin5G Server that includes the UE Service ID, as detailed in Table 8.2.2-1.

Table 8.2.2-1: MSGin5G UE de-registration request

Information element	Status	Description
UE Service ID	M	UE service identifier assigned to the MSGin5G UE.

3. The MSGin5G Server may initiate authentication procedures with the MSGin5G Client and authorizes the MSGin5G Client. The MSGin5G Server deletes any applicable UE Service ID and associated MSGin5G Client Profile information that it has stored.

NOTE 2: The authentication procedures in step 3 are built on top of the transport layer mechanism specified in Annex Y.2 of 3GPP TS 33.501 [16].

4. The MSGin5G Server an MSGin5G UE de-registration response as detailed in Table 8.2.2-2 to the MSGin5G UE.

Table 8.2.2-2: MSGin5G UE de-registration response

Information element	Status	Description
UE Service ID	M	UE service identifier assigned to the MSGin5G UE.
De-registration result	M	Indication if the de-registration is success or failure
Failure Cause	O	The reason for failure