5 Functional entities
24.5473GPPIdentity management - Service Enabler Architecture Layer for Verticals (SEAL)Protocol specificationRelease 17TS
5.1 SEAL identity management client (SIM-C)
The SIM-C is a functional entity that acts as the application client for VAL user identity related transactions.
To be compliant with the HTTP procedures in the present document the SIM-C shall:
– support the user authentication procedure specified in clause 6.2.2; and
– support the token exchange procedure specified in clause 6.2.3.
To be compliant with the CoAP procedures in the present document the SIM-C:
– shall support the role of CoAP client as specified in IETF RFC 7252 [17];
– should support CoAP over TCP and Websocket as specified in IETF RFC 8323 [18];
– shall support Internet draft ACE-OAUTH [19];
– shall support OSCORE profile of ACE-OAUTH [21];
– should support DTLS profile of ACE-OAUTH [20]; and
– shall support the procedures in clause 6.2.2.
5.2 SEAL identity management server (SIM-S)
The SIM-S is a functional entity that authenticates the VAL user’s identity by verifying the credentials provided by the VAL user.
To be compliant with the procedures in the present document the SIM-S shall:
– support the user authentication procedure specified in clause 6.2.2; and
– support the token exchange procedure specified in clause 6.2.3.
To be compliant with the CoAP procedures in the present document the SIM-S:
– shall support the role of CoAP server as specified in IETF RFC 7252 [17];
– should support CoAP over TCP and Websocket as specified in IETF RFC 8323 [18];
– shall support Internet draft ACE-OAUTH [19];
– shall support OSCORE profile of ACE-OAUTH [21];
– should support DTLS profile of ACE-OAUTH[20]; and
– shall support the procedures in clause 6.2.2.