22.2283GPPRelease 16Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS)Stage 1TS
IP multimedia applications shall, as a principle, not be standardised, allowing operator specific variations. It shall be possible to enable rapid service creation and deployment using service capabilities.
It is important that commercially available IP multimedia applications are supported. In general compatibility shall be with these IP multimedia applications instead of building 3GPP-specific solutions.
The following options shall be available in the 3GPP standards to enable service delivery:
– an architectural framework shall be created that enables maximum flexibility in the end user device and network servers, similar in concept to that used in the Internet.
This framework shall enable an operator to efficiently deploy IP multimedia applications in a network-agnostic manner without having to wait for these applications or additional enabling technology, to be standardised in 3GPP.
– service capabilities (enhanced to control IP multimedia applications), which will allow IP multimedia applications to be deployed in a vendor independent manner
CAMEL , MExE , SAT  and OSA , should be improved to support IP multimedia applications, e.g. additions to APIs, service capability features, service capability servers, user profile etc.
– the IM CN Subsystem user related data to be stored in a standardised format and to be managed and accessed using standardised mechanisms of the 3GPP Generic User Profile (GUP) .
– mechanisms which allow the network or the application to understand the limitations of the mobile and thereby take appropriate actions.
Note: There is a concern that with a large variety of toolkits to create applications, service interworking between terminals and networks may be compromised and needs to be addressed.