|
|
Fast Web Services for Service-Oriented ArchitecturesThe Fast Web Services concept was introduced by Sun Microsystems in August 2003. The concept uses ASN.1 definitions instead of XML schemes for defining data types within the web services architecture. Data sent over any application layer are transfered either in a binary or character encoded format. Any XML-based protocols, such as SOAP (web services), use character encodings. In ASN.1, the Packet Encoding Rule (PER) and the Basic Encoding Rule (BER) are binary encoding rules. Both encoding formats have their respective advantages and disadvantages. In telecommunication applications binary encoding rules are predominantly used, while XML based character encoding can be predominantly seen in the web services architecture. With the advent of character encodings in ASN.1, especially XML Encoding Rule (XER) and the Extended XML Encoding Rule (E-XER), we could bridge the two different worlds of performance (e.g., telecommunication applications) and interoperability (web service - service oriented architecture). We were successful in developing a sample application for the mobile telecommunication network that uses an ASN.1 definition of the SOAP layer and several definitions of standard mobile telecommunication messages. Traditional telecommunication messages of the SS7 network already rely on ASN.1 definitions. By using E-XER, traditional network nodes can be enabled for network independent service nodes deployed in a Service-Oriented Architecture. The prototype uses an object-based Next Generation Profile Register (NGPR) as a service node. PER as a binary encoding is used in order to fetch the real time access criteria of the NGPR. I would like to thank Bruno Konik and uniGone for the valuable support and for providing the uniGone ASN.1 Compiler. The draft version of the whitepaper can be downloaded here. If you came via an external link to this page you can visit diehl-develop.com here. |
diehl-develop.com Home