Asynchronous Mobile Web Services:

1,266 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,266
On SlideShare
0
From Embeds
0
Number of Embeds
26
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Asynchronous Mobile Web Services:

  1. 1. IEEE CIT 2008 Fahad Aijaz Communication Networks (ComNets) Aachen University of Technology (RWTH Aachen) Germany IEEE International Conference on Computer and Information Technology 08-11 July 2008 Asynchronous Mobile Web Services: Concept and Architecture
  2. 2. Agenda <ul><li>Introduction (What?) </li></ul><ul><li>Motivation and Challenges (Why?) </li></ul><ul><li>Proposed Solution (How?) </li></ul><ul><li>Mobile Web Services Framework </li></ul><ul><li>Service Management </li></ul><ul><li>Service Deployment </li></ul><ul><li>Proof-of-Concept </li></ul><ul><li>Wrap up </li></ul>
  3. 3. Introduction (What?) (Evolution and Classification of Mobile Web Services) <ul><li>Mobile Web Services </li></ul><ul><li>Defines web service interaction between the mobile networks and devices </li></ul><ul><li>Self contained software components that can be identified by a URI </li></ul><ul><li>Hosted on mobile devices </li></ul>A B C A B C
  4. 4. Motivation and Challenges (Why?) <ul><li>Not all mobile web services need to be synchronous . </li></ul><ul><ul><li>Complex computations. </li></ul></ul><ul><ul><li>Long-lived collaborations. </li></ul></ul><ul><ul><li>Transactions and workflows. </li></ul></ul><ul><li>Synchronity in long lived mobile web services is a grave issue. </li></ul><ul><ul><li>Too much power consumption. </li></ul></ul><ul><ul><li>Unnecessary resource allocation. </li></ul></ul><ul><ul><li>Inefficient services involving human feedback. </li></ul></ul><ul><li>Due to unavailability of any API or middleware for asynchronous mobile web services, the development cost increases. </li></ul><ul><li>The deployment of such asynchronous services becomes a complex process . </li></ul><ul><li>No mechanisms for mobile web service monitoring . </li></ul><ul><ul><li>Status Information. </li></ul></ul><ul><ul><li>Expected completion time etc. </li></ul></ul><ul><li>No support for Dynamic Change Management (Control). </li></ul><ul><ul><li>Change in requirements at runtime. </li></ul></ul>
  5. 5. Proposed Solution (How?) <ul><li>A middleware for development and deployment of asynchronous mobile web services shall be developed. </li></ul><ul><li>Asynchronous services shall be capable of performing long-lived operations . </li></ul><ul><li>An API shall be provided to higher layers that facilitates the development of asynchronous communication system and reduces the development cost . </li></ul><ul><li>Service deployment process shall be made simple. </li></ul><ul><li>Mechanism for control and monitoring of such long-lived services shall be provided. </li></ul><ul><li>Performance evaluation shall to be done. </li></ul><ul><li>Proof of concept shall be developed. </li></ul>
  6. 6. Mobile Web Services Framework (1/2) (Existing System) Glue (IT World) Computing (Telco World) Communication
  7. 7. Mobile Web Services Framework (2/2) (Extension to the Existing System) Asynchronous Mobile Web Services: Concept and Architecture Asynchronous Communication Architecture Interaction Mechanisms Creation, Control & Monitoring Data Representation
  8. 8. Asynchronous Communication Architecture <ul><li>Request Handler processes all incoming requests, but handles only synchronous requests passing the asynchronous requests to ASAP Handler. </li></ul><ul><li>ASAP Handler handles asynchronous requests . </li></ul><ul><li>Asynchronous framework supports both Polling and Callback interaction techniques. </li></ul><ul><li>Synchronous and Asynchronous Services are deployed in a similar way by the same Deployment Interface. </li></ul>Mobile Web Services Framework Instance Factory Observer Notification UDP Listener HTTP Listener Response Handler ASAP Handler Request Handler Deployment Interface Mobile Web Service Request Mobile Web Service Response Notify Synchronous and Asynchronous Mobile Web Services Invocation, Control and Monitoring Asynchronous Request Management SOAP Server Asynchronous Communication Architecture Interaction Mechanisms Creation, Control & Monitoring
  9. 9. Peer-to-Peer Service Management (ISO/OSI Layer Model) <ul><li>SOAP messages comprise of service creation, control and monitoring signals. </li></ul><ul><li>Control messages : Change Status, Terminate, Wait etc. </li></ul><ul><li>Monitoring messages : Get Status, Get Properties etc. </li></ul>IP Layer Transport Layer SOAP WS-Addressing HTTP UDP SR-UDP TCP WS-Eventing Asynchronous Service Middleware ASAP SOAP Server ASAP Factory Instance Notification Control and Monitoring Observer Application Context Data Services IP Layer Transport Layer SOAP HTTP UDP SR-UDP TCP Asynchronous Service Middleware SOAP Server ASAP Application Control and Monitoring Factory Instance Notification Observer Services WS-Addressing WS-Eventing ASAP Context Data SOAP Creation, Control, Monitoring Context Data Alternative Protocols Bindings
  10. 10. Service Management Control Flow <ul><li>ASAP Handler </li></ul><ul><ul><li>Processes asynchronous requests </li></ul></ul><ul><ul><li>Performs appropriate request delegations. </li></ul></ul><ul><li>Factory aka. Manager </li></ul><ul><ul><li>Creates Instances. </li></ul></ul><ul><ul><li>Maintains a record of Instances. </li></ul></ul><ul><li>Instance aka. Worker </li></ul><ul><ul><li>Controls and Monitors the service. </li></ul></ul><ul><ul><li>Notify clients about updates. </li></ul></ul>Instance Factory Service Response Response Controls Creates Service Control Service Creation Service Monitoring ASAP Handler Service Request <ul><li>Service Control </li></ul><ul><li>open.notrunning </li></ul><ul><li>open.notrunning.suspended </li></ul><ul><li>open.running </li></ul><ul><li>closed.completed </li></ul><ul><li>closed.abnormalCompleted </li></ul><ul><li>closed.abnormalCompleted.terminated </li></ul><ul><li><soap:Envelope xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;> </li></ul><ul><li><soap:Header> </li></ul><ul><ul><li><wsa:To>http://asap.comnets.rwth-aachen.de/soaprpc</wsa:To> </li></ul></ul><ul><ul><li><wsa:Action>GetProperties</wsa:Action> </li></ul></ul><ul><ul><li><wsa:MessageId>uuid:cfdd9643-ffffff2c-1fc4bec-20b457d8</wsa:MessageId> </li></ul></ul><ul><ul><li><wsa:ReplyTo> </li></ul></ul><ul><ul><li><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address> </li></ul></ul><ul><ul><li></wsa:ReplyTo> </li></ul></ul><ul><li></soap:Header> </li></ul><ul><li><soap:Body> </li></ul><ul><li><inNetComRequest xmlns=&quot;urn:Services&quot; id=&quot;o0&quot; SOAP-ENC:root=&quot;1&quot;> </li></ul><ul><li><ServiceType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Asynchronous</ServiceType> </li></ul><ul><li><MethodType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Factory</MethodType> </li></ul><ul><li><getPropertiesRq xmlns=&quot;&quot; xsi:type=&quot;:getPropertiesRq&quot; /> </li></ul><ul><li></inNetComRequest> </li></ul><ul><li></soap:Body> </li></ul><ul><li></soap:Envelope> </li></ul>Service Monitoring
  11. 11. Data Representation and Service Deployment <ul><li>In order to develop and deploy and asynchronous mobile web service, a developer should: </li></ul><ul><ul><li>Create the asynchronous service. </li></ul></ul><ul><ul><li>Develop the Context and Result Data components, and </li></ul></ul><ul><ul><li>Implement the Client . </li></ul></ul><ul><li>Context and Result Data registers themselves with the Data Register , which fetches the corresponding Context and Result Data class for each specific service request. </li></ul><ul><li>Data Interface performs serialization and de-serialization functionality. </li></ul>Client Asynchronous Mobile Web Services Middleware Services Data Interface Serialization De-serialization Context/Result Data Data Register Context Data SOAP Message Result Data SOAP Message Context Data Java Object Result Data Java Object Data Representation
  12. 12. Proof-of-Concept (In-Network Communication and Computation for WSN) <ul><li>Sensor nodes gather data such as temp, humidity, smoke etc. </li></ul><ul><li>Collaboration nodes in the sensor networks perform computations. </li></ul><ul><li>Asynchronous server with collaborative network computation application deployed on the computation nodes. </li></ul><ul><li>The middleware is currently deployed on Sun Microsytem‘s Lab technology called Sun SPOTs. </li></ul>Picture Source: http://www.sunspotworld.com Sensor data sent for computation ACK: Data received Status Monitoring: Completed ? NACK Control Signal: Latest Data ACK Final ACK Collaborating Nodes Sensors Computation Nodes
  13. 13. Conclusion & Outlook <ul><li>Conclusion </li></ul><ul><li>The mobile web services middleware now supports the development and deployment of asynchronous long-lived services . </li></ul><ul><li>The middleware provides and API to developers that reduces the development time and costs. </li></ul><ul><li>Context Data representation has been designed to support context-awareness in long lived services. </li></ul><ul><li>Asynchronous mobile web services middleware supports Polling and Callback interaction techniques. </li></ul><ul><li>Control and Monitoring mechanisms have been designed to support dynamic service management. </li></ul><ul><li>Asynchronous mobile web services supports service collaboration between peers . </li></ul><ul><li>The performance of the middleware is dependent on the size of the Contextual Data. Results are expected soon. </li></ul><ul><li>Proof-of-Concept is presented. </li></ul><ul><li>Outlook </li></ul><ul><li>Performance optimization with RESTful architectural design for Mobile Web Services. </li></ul><ul><li>Agreement based services (SLA) for mobile grids. </li></ul><ul><li>Service Composition and Collaboration among mobile nodes. </li></ul><ul><li>Ultra-low cost battery efficient mobile terminals. </li></ul><ul><li>Gateway applications for infrastructureless environments. </li></ul>
  14. 14. Thank you for your attention ! Questions?
  15. 15. Performance Results (Memory Footprint – Non Obfuscated) <ul><li>Async. Server Size on Disk </li></ul><ul><ul><li>cnsoap.server: 60.9 KB. </li></ul></ul><ul><ul><li>cnsoap.asap: 92.3 KB. </li></ul></ul><ul><ul><li>cnsoap.asap.asapTypes: 43.4 KB. </li></ul></ul><ul><ul><li>cnsoap.util: 32.3 KB. </li></ul></ul><ul><ul><li>cnsoap.services: 111 KB. </li></ul></ul><ul><ul><li>cnsoap.ksoap: 70.1 KB. </li></ul></ul><ul><li>Server Memory Usage </li></ul><ul><ul><li>Maximum: 530.69 KB </li></ul></ul><ul><ul><li>Average: 191.01 KB </li></ul></ul><ul><li>Client Memory Usage </li></ul><ul><ul><li>Maximum: 531.6 KB </li></ul></ul><ul><ul><li>Average: 381.66 KB </li></ul></ul>Relative Numbers
  16. 16. Performance Results (Processing Latencies) <ul><li>Message processing time increases with the increase in the size of the context data. </li></ul><ul><li>7 fold increase in the size of the context data resulted in a 1.15 fold increase in the processing time . </li></ul><ul><li>Processing time of messages that do not send or receive context data remain unchanged for a given service. E.g: Control Messages. </li></ul>
  17. 17. Instance Creation Request Soap Envelope <ul><li><soap:Envelope xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;> </li></ul><ul><li><soap:Header> </li></ul><ul><ul><li><wsa:To>http://asap.comnets.rwth-aachen.de/soaprpc</wsa:To> </li></ul></ul><ul><ul><li><wsa:Action>CreateInstance</wsa:Action> </li></ul></ul><ul><ul><li><wsa:MessageId>asap-uuid:cfdd9643-ffffff2c-1fc4bec-20b457d8</wsa:MessageId> </li></ul></ul><ul><ul><li><wsa:ReplyTo> </li></ul></ul><ul><ul><li><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address> </li></ul></ul><ul><ul><li></wsa:ReplyTo> </li></ul></ul><ul><li></soap:Header> </li></ul><ul><li><soap:Body> </li></ul><ul><li><inNetComRequest xmlns=&quot;urn:Services&quot; id=&quot;o0&quot; SOAP-ENC:root=&quot;1&quot;> </li></ul><ul><ul><li><ServiceType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Asynchronous</ServiceType> </li></ul></ul><ul><ul><li><MethodType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Factory</MethodType> </li></ul></ul><ul><ul><li><createInstanceRq xmlns=&quot;&quot; xsi:type=&quot;:createInstanceRq&quot;> </li></ul></ul><ul><ul><li><StartImmediately xsi:type=&quot;xsd:boolean&quot;>true</StartImmediately> </li></ul></ul><ul><ul><li><ObserverEPR xsi:type=&quot;xsd:string&quot;>http://asynchronousmiddleware.com/observer/in-net-com</ObserverEPR> </li></ul></ul><ul><ul><li><Name xsi:type=&quot;xsd:string&quot;>In-Net-Com Service </Name> </li></ul></ul><ul><ul><li><Subject xsi:type=&quot;xsd:string&quot;>Network Computation Service</Subject> </li></ul></ul><ul><ul><li><Description xsi:type=&quot;xsd:string&quot;>Network Computation Service deployed on a Collector node</Description> </li></ul></ul><ul><ul><li><ContextData xsi:type=&quot;:ContextData&quot;> </li></ul></ul><ul><ul><li><smoke xsi:type=&quot;xsd:Integer&quot;>20,21,22,20,23,22,24,22,23,22,21,20,22,24,25 </li></ul></ul><ul><ul><li>23,22,20,24</smoke> </li></ul></ul><ul><ul><li></ContextData> </li></ul></ul><ul><ul><li></createInstanceRq> </li></ul></ul><ul><ul><li></inNetComRequest> </li></ul></ul><ul><li></soap:Body> </li></ul><ul><li></soap:Envelope> </li></ul>
  18. 18. Instance Creation Response Soap Envelope <ul><li><soap:Envelope xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;> </li></ul><ul><li><soap:Header> </li></ul><ul><ul><li><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To> </li></ul></ul><ul><ul><li><wsa:Action>CreateInstance</wsa:Action> </li></ul></ul><ul><ul><li><wsa:MessageId>asap-uuid:cfdd9643-ffffff2c-1fc4bec-20b457d8</wsa:MessageId> </li></ul></ul><ul><ul><li><wsa:RelatesTo>asap-uuid:cfd68f11-80-1fc4bec-fb0302df</wsa:RelatesTo> </li></ul></ul><ul><li></soap:Header> </li></ul><ul><li><soap:Body> </li></ul><ul><ul><li><inNetComResponse xmlns=&quot;urn:Services&quot; id=&quot;o0&quot; SOAP-ENC:root=&quot;1&quot;> </li></ul></ul><ul><ul><li><ServiceType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Asynchronous</ServiceType> </li></ul></ul><ul><ul><li><MethodType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Factory</MethodType> </li></ul></ul><ul><ul><li><createInstanceRs xmlns=&quot;&quot; xsi:type=&quot;:createInstanceRs&quot;> </li></ul></ul><ul><ul><li><InstanceEPR xsi:type=&quot;xsd:string&quot;>http://asynchronousmiddleware.com/ </li></ul></ul><ul><ul><li>instance/in-net-com/</InstanceEPR> </li></ul></ul><ul><ul><li></createInstanceRs> </li></ul></ul><ul><ul><li></inNetComResponse> </li></ul></ul><ul><li></soap:Body> </li></ul><ul><li></soap:Envelope> </li></ul>
  19. 19. Instance Creation and Completion Flow Mobile Web Services Framework Instance Factory Observer Notification UDP Listener HTTP Listener Response Handler ASAP Handler Request Handler Deployment Interface Mobile Web Service Request Mobile Web Service Response Notify Synchronous and Asynchronous Mobile Web Services Invocation, Control and Monitoring Asynchronous Request Management SOAP Server
  20. 20. Monitoring Request Soap Envelope <ul><li><soap:Envelope xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;> </li></ul><ul><li><soap:Header> </li></ul><ul><ul><li><wsa:To>http://asap.comnets.rwth-aachen.de/soaprpc</wsa:To> </li></ul></ul><ul><ul><li><wsa:Action>GetProperties</wsa:Action> </li></ul></ul><ul><ul><li><wsa:MessageId>asap-uuid:cfdd9643-ffffff2c-1fc4bec-20b457d8</wsa:MessageId> </li></ul></ul><ul><ul><li><wsa:ReplyTo> </li></ul></ul><ul><ul><li><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address> </li></ul></ul><ul><ul><li></wsa:ReplyTo> </li></ul></ul><ul><li></soap:Header> </li></ul><ul><li><soap:Body> </li></ul><ul><li><inNetComRequest xmlns=&quot;urn:Services&quot; id=&quot;o0&quot; SOAP-ENC:root=&quot;1&quot;> </li></ul><ul><li><ServiceType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Asynchronous</ServiceType> </li></ul><ul><li><MethodType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Factory</MethodType> </li></ul><ul><li><getPropertiesRq xmlns=&quot;&quot; xsi:type=&quot;:getPropertiesRq&quot; /> </li></ul><ul><li></inNetComRequest> </li></ul><ul><li></soap:Body> </li></ul><ul><li></soap:Envelope> </li></ul>
  21. 21. Monitoring Response Soap Envelope <ul><li><soap:Envelope xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;> </li></ul><ul><li><soap:Header> </li></ul><ul><ul><li><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To> </li></ul></ul><ul><ul><li><wsa:Action>GetProperties</wsa:Action> </li></ul></ul><ul><ul><li><wsa:MessageId>asap-uuid:cfdd9643-ffffff2c-1fc4bec-20b457d8</wsa:MessageId> </li></ul></ul><ul><ul><li><wsa:RelatesTo>asap-uuid:cfd68f11-80-1fc4bec-fb0302df</wsa:RelatesTo> </li></ul></ul><ul><li></soap:Header> </li></ul><ul><li><soap:Body> </li></ul><ul><ul><li><inNetComResponse xmlns=&quot;urn:Services&quot; id=&quot;o0&quot; SOAP-ENC:root=&quot;1&quot;> </li></ul></ul><ul><ul><li><ServiceType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Asynchronous</ServiceType> </li></ul></ul><ul><ul><li><MethodType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Factory</MethodType> </li></ul></ul><ul><ul><li><getPropertiesRs xmlns=&quot;&quot; xsi:type=&quot;:getPropertiesRs&quot;> </li></ul></ul><ul><ul><li><EPR xsi:type=&quot;xsd:string&quot;>http://asynchronousmiddleware.com/factory/in-net-com</EPR> </li></ul></ul><ul><ul><li><Name xsi:type=&quot;xsd:string&quot;>InNet Com Factory</Name> </li></ul></ul><ul><ul><li><Subject xsi:type=&quot;xsd:string&quot;>Factory of In Net Com Service</Subject> </li></ul></ul><ul><ul><li><Description xsi:type=&quot;xsd:string&quot;>Factory of In Net Com Service deployed on the collector node</Description> </li></ul></ul><ul><ul><li><ContextData xsi:type=&quot;:ContextData&quot;> </li></ul></ul><ul><ul><li><smoke xsi:type=&quot;xsd:Integer&quot;>20,21,22,20,23,22,24,22,23,22,21,20,22,24,25, </li></ul></ul><ul><ul><li>23,22,20,24</smoke> </li></ul></ul><ul><ul><li></ContextData> </li></ul></ul><ul><ul><li><ResultData xsi:type=&quot;xsd:string&quot;>Not Computed Yet!!</ResultData> </li></ul></ul><ul><ul><li></getPropertiesRs> </li></ul></ul><ul><ul><li></inNetComResponse> </li></ul></ul><ul><li></soap:Body> </li></ul><ul><li></soap:Envelope> </li></ul>
  22. 22. Monitoring Message Flow Mobile Web Services Framework Instance Factory Observer Notification UDP Listener HTTP Listener Response Handler ASAP Handler Request Handler Deployment Interface Mobile Web Service Request Mobile Web Service Response Notify Synchronous and Asynchronous Mobile Web Services Invocation, Control and Monitoring Asynchronous Request Management SOAP Server
  23. 23. Control/DCM Request Soap Envelope <ul><li><soap:Envelope xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;> </li></ul><ul><li><soap:Header> </li></ul><ul><ul><li><wsa:To>http://asap.comnets.rwth-aachen.de/soaprpc</wsa:To> </li></ul></ul><ul><ul><li><wsa:Action>ChangeState</wsa:Action> </li></ul></ul><ul><ul><li><wsa:MessageId>asap-uuid:cfdd9643-ffffff2c-1fc4bec-20b457d8</wsa:MessageId> </li></ul></ul><ul><ul><li><wsa:ReplyTo> </li></ul></ul><ul><ul><li><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address> </li></ul></ul><ul><ul><li></wsa:ReplyTo> </li></ul></ul><ul><li></soap:Header> </li></ul><ul><li><soap:Body> </li></ul><ul><li><inNetComRequest xmlns=&quot;urn:Services&quot; id=&quot;o0&quot; SOAP-ENC:root=&quot;1&quot;> </li></ul><ul><ul><li><ServiceType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Asynchronous</ServiceType> </li></ul></ul><ul><ul><li><MethodType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Instance</MethodType> </li></ul></ul><ul><ul><li><changeStateRq xmlns=&quot;&quot; xsi:type=&quot;:changeStateRq&quot;> </li></ul></ul><ul><ul><li><State xsi:type=&quot;xsd:string&quot;>closed.completed</State> </li></ul></ul><ul><ul><li></changeStateRq> </li></ul></ul><ul><ul><li></inNetComRequest> </li></ul></ul><ul><li></soap:Body> </li></ul><ul><li></soap:Envelope> </li></ul>
  24. 24. Control/DCM Response Soap Envelope <ul><li><soap:Envelope xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:soap=&quot;http://schemas.xmlsoap.org/soap/envelope/&quot;> </li></ul><ul><li><soap:Header> </li></ul><ul><ul><li><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To> </li></ul></ul><ul><ul><li><wsa:Action>ChangeState</wsa:Action> </li></ul></ul><ul><ul><li><wsa:MessageId>asap-uuid:cfdd9643-ffffff2c-1fc4bec-20b457d8</wsa:MessageId> </li></ul></ul><ul><ul><li><wsa:RelatesTo>asap-uuid:cfd68f11-80-1fc4bec-fb0302df</wsa:RelatesTo> </li></ul></ul><ul><li></soap:Header> </li></ul><ul><li><soap:Body> </li></ul><ul><ul><li><inNetComResponse xmlns=&quot;urn:Services&quot; id=&quot;o0&quot; SOAP-ENC:root=&quot;1&quot;> </li></ul></ul><ul><ul><li><ServiceType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Asynchronous</ServiceType> </li></ul></ul><ul><ul><li><MethodType xmlns=&quot;&quot; xsi:type=&quot;xsd:string&quot;>Instance</MethodType> </li></ul></ul><ul><ul><li><changeStateRs xmlns=&quot;&quot; xsi:type=&quot;:changeStateRs&quot;> </li></ul></ul><ul><ul><li><State xsi:type=&quot;xsd:string&quot;>closed.completed</State> </li></ul></ul><ul><ul><li></changeStateRs> </li></ul></ul><ul><ul><li></inNetComResponse> </li></ul></ul><ul><li></soap:Body> </li></ul><ul><li></soap:Envelope> </li></ul>
  25. 25. Control/DCM Message Flow Mobile Web Services Framework Instance Factory Observer Notification UDP Listener HTTP Listener Response Handler ASAP Handler Request Handler Deployment Interface Mobile Web Service Request Mobile Web Service Response Notify Synchronous and Asynchronous Mobile Web Services Invocation, Control and Monitoring Asynchronous Request Management SOAP Server

×