You will have to have a business relationship with AT&T in order to use our APIs, but you can distribute your application or service yourself.
Charging Trigger Function (CTF), Charging Data Function (CDF), and Charging Gateway Function (CGF) are the billing service elements.
Not necessarily. A single PDP context can accommodate different media applications.
IMS is capable of handling both prepaid and postpaid offers. The functionality offered by this new service includes 3G, 2.5G, and 2G network technology.
No, IMS will not provide that sort of impact; rather, quality of service mechanisms may improve the user experience.
IMS has defined the Geologic Quadrangle (Gq) interface to specify quality of service (QoS). To date, four levels of QoS, ranging from conversational voice down to best effort, have been defined in the 3GPP standards.
GSM World of which AT&T is a member, is sponsoring interoperability tests between carriers to address interoperability issues while IMS is in its infancy. AT&T is actively participating in these interoperability tests.
There is a theoretical limit, we have written applications using up to eight sessions.
3GPP has transitioned the standardization of specific applications to OMA to ensure that different vendors' products can work together. OMA is working on applications of IMS such as push-to-talk, instant messaging, and presence enablers.
The main difference between Session Initiation Protocol (SIP)and the International Steering Committee (ISC) interface is that the ISC interface uses SIP as its foundation.
Unlicensed Mobile Access (UMA) is much more limited in functionality. AT&T has decided that, although it may take longer to launch services, in the long run IMS will be more beneficial than UMA.
If you have a system that uses Simple Network Paging Protocol (SNPP), Simple Mail Transfer Protocol (SMTP), or Short Message Service (SMS) to send messages to users, you will not have to modify your code to be compatible with IMS. If you need to send a message using IMS, you will not have to write a SIP message.
You may choose to modify your application to integrate new media and new features that IMS will make possible, but you won't have to change your current application if such enhancements are not planned.
We expect it will depend on the types of terminal and applications. On terminals with rich user interfaces, such as WWAN-enabled PCs, we can imagine a robust dashboard for communication across multiple types of media. Handhelds can also handle these types of media, but developers will need to pay close attention to delivering simple, intuitive UIs on these types of devices. SIP will help these be standard.
The quality of the user experience does not degrade elegantly in each session, meaning that the voice quality does not suffer as a user opens multiple video streams.
The PDF is responsible for taking into account the various user requirements in order to provide sufficient quality of service.
There is an element within the IMS architecture called the IM-SSF which handles interworking legacy IN applications (CAMEL) and the IMS network. 3GPP TS 23.002 (3rd Generation Partnership Project Technical Specification) provides additional explanation of this architecture.
We have been following and participating in Java APIs for Integrated Networks (JAIN) and Java Service Logic Execution Environment (JSLEE) development. We have not fully defined how we will use it, but we are investigating it. We believe several implementations of JAIN/JSLEE are ready for prime time.
| 通信人家园 (https://www.txrjy.com/) | Powered by C114 |