5 Architecture

29.3643GPPIP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperabilityRelease 17TS

Figure 5-1 presents the functional architecture for AS interoperability.

Figure 5-1: Functional architecture for AS interoperability

The MMTEL communications of a given user equipment are routed to an AS according to the content of the filter criteria.

If AS interoperability is supported, the Service Data attached to a user shall be stored in the HSS and the AS shall access and update, when required, the Service Data via the Sh interface.

The user may configure some of its Service Data via the Ut interface, via SIP based user configuration as described in 3GPP TS 24.238 [18], or via other means.

Some Service Data is configured by the service provider e.g. from its OSS, either directly into the HSS or via an AS that will store these Service Data in the HSS.

The AS associated to a given user for MMTEL services may vary over time.

The same format of the Service Data stored in the HSS shall be supported for interoperability between ASs utilising the Service Data.