System and method for generating a wireless application from a web service definition

• US 20060234763A1
• Filed: 09/09/2005
• Published: 10/19/2006
• Est. Priority Date: 04/18/2005
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Research In Motion Limited (Blackberry Limited)
• Inventors: Debruin, David, Mateescu, Daniel, Goring, Bryan R.
• Granted Patent: US 7,769,897 B2
• Time in Patent Office: Days
• US Class Current: 455/552.100
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Abstract

System and method for creating a wireless application from a web service definition language employs an algorithm that analyzes each message of the web service definition an maps the message to a wireless application message and a wireless application data structure. The message maps are used by a proxy at an edge of a wireless network to convert web service messages to wireless messages, and vice versa.

Claims

1. A method for generating a wireless application from a web service definition, comprising:

accepting as input web service messages, determining whether each web service message is an input or an output message, creating a message object and a component mapping object for each web service message, linking the component mapping object to the message object and to the web service message, and mapping message parts of the web service message to message parts of the wireless application.

2. The method as claimed in claim 1 wherein mapping the message parts comprises creating a message field object, creating a field mapping object, and linking the field mapping object to the message field object and the web service message part.

3. The method as claimed in claim 2 further comprising:

selecting a message part;

determining whether the message part is an element declaration;

determining the element type if the message part is an element declaration; and

determining whether the message part is a simple data type, an enumeration or a complex type.

4. The method as claimed in claim 3 wherein if the message part is a simple data type, the method further comprises determining whether the simple data type is an atomic type, a list or a union.

5. The method as claimed in claim 4 wherein if the simple data type is an atomic type, the method comprises determining a corresponding data type using a translation table and updating the message field object based on the data type.

6. The method as claimed in claim 4 wherein if the simple data type is an enumeration, the method further comprises:

creating an enumeration object;

creating an enumeration mapping object;

linking the enumeration mapping object to the enumeration object and to a simple data type definition; and

for each enumeration value, creating an enumeration literal object and mapping it.

7. The method as claimed in claim 3 wherein if the message part is a complex type, the method further comprises:

creating a data object;

creating a component mapping object;

linking the component mapping object to the data object and to a complex type definition; and

determining whether the complex type has a base type.

8. The method as claimed in claim 7 wherein if the complex type has a base type, the method further comprises:

creating a data object;

creating a component mapping object;

linking the component mapping object to the data object and to a complex type definition;

setting the data object as a prototype for a current complex type; and

determining a category of the complex type.

9. The method as claimed in claim 8 further comprising:

determining whether the category is one of an empty, simple, mixed or element_only;

if the category is one of the empty, simple or element only, determining whether there are any fields in the data object; and

if there are no fields in the data object, discarding the data object and the component mapping object.

10. The method as claimed in claim 9 wherein if the category is mixed, the method comprises discarding the data object and the component mapping object.

11. The method as claimed in claim 9 wherein if the category is not one of the empty, simple, mixed or element_only, the method further comprises:

selecting an attribute of the complex type; and

determining whether the attribute is one of a fixed constraint and a prohibited use.

12. The method as claimed in claim 11 wherein if the attribute is not a fixed constraint or a prohibited use, the method further comprises:

creating a data field object;

creating a field mapping object;

linking the field mapping object to the data field object and to an attribute declaration; and

determining whether the attribute declaration is an enumeration or a simple data type.

13. The method as claimed in claim 9 wherein if the complex type has an “

Any”

attribute the method further comprises;

creating a data field object;

creating a field mapping object;

linking the field mapping object to the data field object and to the “

Any attribute”

;

setting the data field type to “

string”

;

determining whether there are any fields in the data object; and

discarding the data object and the component mapping object if the data object contains no fields.

14. The method as claimed in claim 9 wherein if the category type is simple, the method further comprises:

creating a data field object;

creating a field mapping object;

determining a content type of the simple category; and

determining whether the content is an enumeration or a simple data type.

15. The method as claimed in claim 9 wherein if the category type is element_only, the method further comprises determining whether a particle of the category is an element declaration, an “

Any”

type or a model group.

16. The method as claimed in claim 15 wherein if the particle is an element declaration or “

Any”

type, the method further comprises;

creating a data field object;

creating a field mapping object;

linking the field mapping object to the data field object and to the “

Any”

type;

setting the date field type to “

string”

;

determining a maximum occurrences value of the particle; and

if the maximum occurrences value is greater than one, setting a field array property to “

true”

17. The method as claimed in claim 16 wherein if the particle is a model group, the method further comprises:

for each particle in the model group;

creating a data field object;

creating a field mapping object;

linking the field mapping object to the data field object and to one of the element declaration and the “

Any”

type;

determining the maximum occurrences value of the particle;

if the maximum occurrences value is greater than one, setting a field array property to “

true”

; and

if the category type is “

Any”

, setting the date field type to “

string”

.

18. The method as claimed in claim 17 wherein if the maximum occurrences is 1 and the particle is an element declaration, the method further comprises:

determining whether the particle is a simple type.

19. A system for generating a wireless application from a web service definition, comprising an application developer workstation comprising computer executable code for accepting as input web service messages, determining whether each web service message is an input or an output message, creating a message object and a component mapping object for each web service message, linking the component mapping object to the message object and to the web service message, and mapping message parts of the web service message to message parts of the wireless application.

20. A vendible product comprising a computer readable memory storing computer executable code for accepting as input web service messages, determining whether each web service message is an input or an output message, creating a message object and a component mapping object for each web service message, linking the component mapping object to the message object and to the web service message, and mapping message parts of the web service message to message parts of the wireless application.