Integrated method and apparatus to manage mobile devices and services

• US 20060069743A1
• Filed: 02/18/2005
• Published: 03/30/2006
• Est. Priority Date: 09/16/2004
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Oommen, Paul
• Granted Patent: US 8,065,359 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/026 using e-messaging for transporting management information, e.g. email, instant messaging or chat
• CPC Class Codes: H04L 41/0266 using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation

Abstract

Disclosed herein is a method, a system, a network node and a computer program executable by a data processor or data processors to accommodate a non-IP OTA protocol using an end-to-end IP protocol. The method includes receiving a message from a non-IP entity; using a markup language, such as XML, for message and content representation, where in an XML message non-IP protocol content is identified using an XML ‘Meta’ element, where the Meta element describes the content type as ‘non-IP protocol name’ and sending the XML message. The step of using XML preferably includes encapsulating received content in an XML message and using the XML Meta element to enable a receiver of the XML message to extract the content. The message received from the non-IP entity may be an IS-683 message.

Claims

1. A method to accommodate a non-IP Over-the-Air (OTA) protocol using an end-to-end IP protocol, comprising:

receiving a message from a non-IP entity;

using markup language for message and content representation, where in a message non-IP protocol content is identified using an ‘

Meta’

element, where the Meta element describes the content type as ‘

non-IP protocol name’

; and

sending the message with the “

Meta”

element.

2. A method as in claim 1, where using markup language comprises encapsulating received content in an markup language message by using the Meta element.

3. A method as in claim 1, where the message received from the non-IP entity comprises an IS-683 message, including different versions of the IS-683 protocol.

4. A method as in claim 1, where the markup language message includes additional information for the processing of Meta content comprised of at least one of a URI and one or more commands, where at least one command invokes a process in the receiver of the markup language message to handle the Meta content.

5. A method as in claim 1, where Meta data is encoded by a format specified by a format element.

6. A method as in claim 5, where the format is base 64 (b64) encoded

7. A method as in claim 1, where the message received from the non-IP entity comprises a Nokia-Ericsson OTA message.

8. The method of claim 1, where the markup language message comprises a SyncML DM message.

9. The method of claim 1, where the markup language message comprises an OMA DM message.

10. A method as in claim 1, where a markup language protocol comprises a 3GPP2 IOTA-DM message.

11. A network node operable to accommodate a non-IP Over-the-Air (OTA) protocol using an end-to-end IP protocol, comprising a receiver to receive a message that contains non-IP protocol content and a processor operable with markup language for message and content representation to encapsulate in a markup language message the non-IP protocol content that is identified to a potential receiver of the markup language message as such using an ‘

Meta’

element, where the Meta element describes the Meta content type as ‘

non-IP protocol name’

, and further comprising a transmitter to transmit the markup language message containing the non-IP protocol content towards a recipient and via a wireless network.

12. A network node as in claim 11, where the received message comprises an IS-683 protocol message.

13. A network node as in claim 11, where the markup language message comprises additional information related to processing of the Meta content.

14. A network node as in claim 13, where the additional information comprises a URI.

15. A network node as in claim 13, where the additional information comprises at least one command to invoke a process in the receiver of the markup language message to handle the Meta content.

16. A network node as in claim 11, where the Meta content is base 64 (b64) encoded.

17. A network node as in claim 11, where an encoding of the Meta content is specified by a ‘

Format’

element that comprises part of the markup language message.

18. A network node as in claim 11, where the received message comprises a Nokia-Ericsson OTA message.

19. A network node as in claim 11, where the markup language message comprises a SyncML DM message.

20. A network node as in claim 11, where the markup language message comprises a OMA DM message.

21. A network node as in claim 11, where a markup language protocol comprises a 3GPP2 IOTA-DM message.

22. A mobile station, comprising a non-IP client and a receiver to receive a markup language message that contains a non-IP protocol Over-the-Air (OTA) content message using an end-to-end IP protocol and a processor operable with markup language for message and content representation to extract the non-IP based content message from the received markup language message in response to a presence of an markup language ‘

Meta’

element that describes the Meta content type as ‘

non-IP protocol name’

.

23. A mobile station as in claim 22, and further comprising a transmitter coupled to the processor to transmit an markup language message containing a non-IP protocol content response message towards an originator of the non-IP protocol content message.

24. A mobile station as in claim 23, where said processor is further operable to direct the extracted non-IP based content message to the non-IP client, and where the non-IP protocol content response message is originated by the non-IP client.

25. A mobile station as in claim 22, where the non-IP protocol content message comprises an IS-683 protocol message.

26. A mobile station as in claim 22, where the markup language message comprises additional information related to processing of the Meta content.

27. A mobile station as in claim 26, where the additional information comprises a URI.

28. A mobile station as in claim 26, where the additional information comprises at least one command to invoke a process to handle the Meta content.

29. A mobile station as in claim 22, where the Meta content is base 64 (b64) encoded.

30. A mobile station as in claim 22, where an encoding of the Meta content is specified by a ‘

Format’

element that comprises part of the markup language message.

31. A mobile station as in claim 22, where the non-IP protocol content message comprises a Nokia-Ericsson OTA message.

32. A mobile station as in claim 22, where the markup language message comprises a SyncML DM message.

33. A mobile station as in claim 22, where the markup language message comprises an OMA DM message.

34. A mobile station as in claim 22, where a markup language protocol comprises a 3GPP2 IOTA-DM message.

35. A computer readable data storage medium storing computer program instructions for causing a computer that comprises part of a network node to accommodate a non-IP Over-the-Air (OTA) protocol using an end-to-end IP protocol by performing operations of receiving a message that contains non-IP protocol content;

encapsulating in a markup language message the non-IP protocol content that is identified to a potential receiver of the markup language message as such using an markup language ‘

Meta’

element, where the Meta element describes the Meta content type as ‘

non-IP protocol name’

; and

transmitting the markup language message containing the non-IP protocol content towards a recipient.

36. A computer readable data storage medium storing computer program instructions for causing a computer that comprises part of a mobile station having a non-IP client to perform operations of receiving a markup language message that contains a non-IP protocol Over-the-Air (OTA) content message using an end-to-end IP protocol;

and extracting the non-IP based content message from the received markup language message in response to a presence of a markup language ‘

Meta’

element that describes the Meta content type as ‘

non-IP protocol name’

.

37. A computer readable data storage medium as in claim 36, and further comprising an operation of transmitting a markup language message containing an encapsulated non-IP protocol content response message towards an originator of the non-IP protocol content message.

38. A computer readable data storage medium as in claim 37, further comprising an operation of directing the extracted non-IP based content message to the non-IP client, where the non-IP protocol content response message is originated by the non-IP client.

39. A network node operable to accommodate a non-IP Over-the-Air (OTA) protocol using an end-to-end IP protocol, comprising receiver means for receiving a message that contains non-IP protocol content, said receiver means coupled to data processor means operable with markup language for message and content representation for encapsulating in a markup language message the non-IP protocol content that is identified to a potential receiver of the markup language message as such using a markup language ‘

Meta’

element, where the Meta element describes the Meta content type as ‘

non-IP protocol name’

, and further comprising transmitter means coupled to said data processor means for transmitting the markup language message containing the non-IP protocol content towards a recipient and via a wireless network.

40. A network node as in claim 39, where the received message comprises an IS-683 protocol message.

41. A network node as in claim 39, where the markup language message comprises additional information related to processing of the Meta content.

42. A network node as in claim 41, where the additional information comprises at least one of a URI and at least one command to invoke a process in the receiver of the markup language message to handle the Meta content.

43. A method for accommodating a non-IP Over-the-Air (OTA) protocol using an end-to-end IP protocol, comprising:

a step for receiving a message from a non-IP entity;

a step for using markup language for message and content representation, where in a message non-IP protocol content is identified using an ‘

Meta’

element, where the Meta element describes the content type as ‘

non-IP protocol name’

; and

a step for sending the message with the “

Meta”

element.

44. A method as in claim 43, where the step for receiving the message receives an IS-683 protocol message.

45. A method as in claim 43, where the step for using markup language comprises using additional information from the message related to processing of the Meta content.

46. A method as in claim 45, where using the additional information comprises using at least one of a URI and at least one command to invoke a process in the receiver of the markup language message to handle the Meta content.