A.4 Message flows

29.2283GPPIP Multimedia (IM) Subsystem Cx and Dx InterfacesRelease 17Signalling flows and message contentsTS

The following message flows give examples regarding which Diameter messages shall be sent in scenarios described in TS 23.228 [1].

A.4.1 Registration– user not registered

Figure A.4.1.1: Registration – user not registered

A.4.2 Registration – user currently registered

Figure A.4.2.1: Re-registration

A.4.3 UE initiated de-registration

Figure A.4.3.1: UE initiated de-registration

A.4.4 Network initiated de-registration

A.4.4.1 Registration timeout

Figure A.4.4.1.1: Network initiated de-registration – registration timeout

A.4.4.2 Administrative de-registration

Figure A.4.4.2.1: Network initiated de-registration – administrative de-registration

A.4.4.3 De-registration initiated by service platform

Figure A.4.4.3.1: Network initiated de-registration – initiated by service platform

A.4.5 UE Terminating SIP session set-up

Figure A.4.5.1: UE Terminating SIP session set-up

A.4.6 Initiation of a session to a non-registered user

Figure A.4.6.1: Initiation of a session to a non-registered user

A.4.6a AS originating session on behalf of a non-registered user

Figure A.4.6a.1: AS originating session on behalf of a non-registered user

A.4.7 User Profile update

Figure A.4.7.1: User profile update

Annex B (informative):
User profile UML model

The purpose of this UML model is to define in an abstract level the structure of the user profile downloaded over the Cx interface and describe the purpose of the different information classes included in the user profile.