|
Diameter Credit-Control Application
Diameter Credit-Control Application, is a networking protocol for Diameter application used to implement real-time credit-control for a variety of end user services. It is an IETF standard first defined in RFC 4006, and updated in RFC 8506. Purpose The purpose of the diameter credit control application is to provide a framework for real-time charging, primarily meant for the communication between gateways/control-points and the back-end account/balance systems (typically an Online Charging System). The application specifies methods for: * Quota management (Reserve, Reauthorize, Abandon) * Simple Debit/Credit * Balance checks * Price inquiries The diameter credit control application does not specify which type units are bought/used and which items are charged. This is left to the service context that has to be specified separately, as is some of the semantics. Examples of units used/bought: * Time * Upload/Download bytes * SMS (Text Messages) Examples of items charged: * Mon ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Diameter (protocol)
Diameter is an authentication, authorization, and accounting protocol for computer networks. It evolved from the earlier RADIUS protocol. It belongs to the application layer protocols in the internet protocol suite. ''Diameter Applications'' extend the base protocol by adding new commands and/or attributes, such as those for use with the Extensible Authentication Protocol (EAP). Comparison with RADIUS The name is a play on words, derived from the RADIUS protocol, which is the predecessor (a diameter is twice the radius). Diameter is not directly backward compatible but provides an upgrade path for RADIUS. The main features provided by Diameter but lacking in RADIUS are: * Support for SCTP * Capability negotiation * Application layer acknowledgements; Diameter defines failover methods and state machines (RFC 3539) * Extensibility; new commands can be defined * Aligned on 32 bit boundaries Also: Like RADIUS, it is intended to work in both local and roaming AAA situatio ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Online Charging System
Online charging system (OCS) is a system allowing a communications service provider to charge their customers, in real time, based on service usage. Architecture Event based charging An event-based charging function (EBCF) is used to charge events based on their occurrence rather than their duration or volume used in the event. Typical events are SMS, MMS, purchase of content (application, game, music, video on demand, etc.). Event-based charging function is used when the CC-Request-Type AVP = 4 i.e. for event request ex: diameter-sms or diameter-..... Let us consider one example of Event-based charging. 1. Cost of one apple is Rupees 25/- You pay the amount, take the apple and go. Similarly, if you send a text message it may cost you Rupee 1/- and that's it. You subscribe to Caller Ring Back Tone (CRBT) which costs you Rs.30/- a month irrespective of the number of calls you receive in a month. So we can term event-based charging as a one-time cost or one-time occurrence cost. S ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
HTTP
The Hypertext Transfer Protocol (HTTP) is an application layer protocol in the Internet protocol suite model for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web, where hypertext documents include hyperlinks to other resources that the user can easily access, for example by a mouse click or by tapping the screen in a web browser. Development of HTTP was initiated by Tim Berners-Lee at CERN in 1989 and summarized in a simple document describing the behavior of a client and a server using the first HTTP protocol version that was named 0.9. That first version of HTTP protocol soon evolved into a more elaborated version that was the first draft toward a far future version 1.0. Development of early HTTP Requests for Comments (RFCs) started a few years later and it was a coordinated effort by the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C), with work later moving t ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Wireless Application Protocol
Wireless Application Protocol (WAP) is a technical standard for accessing information over a mobile wireless network. A WAP browser is a web browser for mobile devices such as mobile phones that use the protocol. Introduced in 1999, WAP achieved some popularity in the early 2000s, but by the 2010s it had been largely superseded by more modern standards. Almost all modern handset internet browsers now fully support HTML, so they do not need to use WAP markup for web page compatibility, and therefore, most are no longer able to render and display pages written in WML, WAP's markup language. Before the introduction of WAP, mobile service providers had limited opportunities to offer interactive data services, but needed interactivity to support Internet and Web applications such as email, stock prices, news and sports headlines. The Japanese i-mode system offered another major competing wireless data protocol. Technical specifications WAP stack The WAP standard described a ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Internet Protocols
The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the set of communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP). In the development of this networking model, early versions of it were known as the Department of Defense (DoD) model because the research and development were funded by the United States Department of Defense through DARPA. The Internet protocol suite provides end-to-end data communication specifying how data should be packetized, addressed, transmitted, routed, and received. This functionality is organized into four abstraction layers, which classify all related protocols according to each protocol's scope of networking. An implementation of the layers for a particular application forms a protocol stack. From lowest to high ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
