Software deployment in a data communications network

• US 20020165976A1
• Filed: 10/04/2001
• Published: 11/07/2002
• Est. Priority Date: 05/02/2001
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Richer, Eric, Gonthier, Jean-Charles, Van Bunningen, Thomas, Jodoin, Pierre-Luc, Maltais, Robert-Claude, Host, Gerald
• Application Number:
  US09/682,678
• Publication Number:
  US 20020165976A1
• Time in Patent Office: Days
• US Class Current: 709/237
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0869 for achieving mutual authentication cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/43 Billing software details
• CPC Class Codes: H04M 15/48 Secure or trusted billing, e.g. trusted elements or encryption
• CPC Class Codes: H04M 15/50 for cross-charging network operators
• CPC Class Codes: H04M 15/51 for resellers, retailers or service providers
• CPC Class Codes: H04M 15/52 for operator independent billing system
• CPC Class Codes: H04M 15/53 using mediation
• CPC Class Codes: H04M 15/56 for VoIP communications
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 15/73 Validating charges
• CPC Class Codes: H04M 15/80 Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/81 Dynamic pricing, e.g. change of tariff during call
• CPC Class Codes: H04M 17/00 : Prepayment of wireline communication systems, wireless communication systems or telephone systems using a coded card to authorise calls from a telephone set H04M1/675
• CPC Class Codes: H04M 2215/0112 : Dynamic pricing, e.g. change of tariff during call
• CPC Class Codes: H04M 2215/0152 : General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
• CPC Class Codes: H04M 2215/0156 : Secure and trusted billing, e.g. trusted elements, encryption, digital signature, codes or double check mechanisms to secure billing calculation and information
• CPC Class Codes: H04M 2215/0164 : Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• CPC Class Codes: H04M 2215/0172 : Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
• CPC Class Codes: H04M 2215/0196 : Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking
• CPC Class Codes: H04M 2215/202 : VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/22 : Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/52 : Interconnection, inter-exchange, reseller billing, billing agreements between different operators, e.g. billing identifier added on the CDR in order to cross charge the other operator, inter-operator accounting, reconciliation, bill directly resellers customers
• CPC Class Codes: H04M 2215/54 : Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
• CPC Class Codes: H04M 2215/7072 : Validate charges

Abstract

The invention is a method for software deployment in a data communications network comprising an Initiator, a Service Provider, and a Peer. The Initiator selects a service and sends an interface request related to the service to the Service Provider. The Service Provider authenticates the request and responds with the interface that the Initiator uses to prepare a service request that is sent to the Service Provider. The Service Provider sends an invitation to the Peer that, if it accepts the service, sends an accept service message to the Service Provider that builds the software for the service and distributes it to the Initiator and the Peer that both install the software, and the service is initiated.

Claims

1. A method for software deployment in a data communications network that comprises an Initiator having an address, a Service Provider, and at least one Peer having an address, the method comprising the steps of:

sending a service request comprising the address of the at least one Peer from the Initiator to the Service Provider;

sending an invitation for the service from the Service Provider to the at least one Peer;

if the at least one Peer accepts the service, sending an accept service message from the at least one Peer to the Service Provider;

building by the Service Provider the software for the service;

distributing by the Service Provider the software to the Initiator and the Peer;

installing the software by the Initiator;

installing the software by the at least one Peer; and

initiating the service.

2. The method for software deployment according to claim 1, further comprising, prior to the step of sending an invitation from the Service Provider to the at least one Peer, the step of registering by the Service Provider the service request.

3. The method for software deployment according to claim 1, further comprising, prior to the step of installing the software by the Initiator, the step of authenticating the software by the Initiator.

4. The method for software deployment according to claim 1, further comprising, prior to the step of installing the software by the at least one Peer, the step of authenticating the software by the at least one Peer.

5. The method for software deployment according to claim 1, further comprising, prior to the step of sending a service request comprising the address of the at least one Peer from the Initiator to the Service Provider, the steps of:

selecting by the Initiator a service;

sending an interface request relating to the selected service from the Initiator to the Service Provider;

sending the requested interface from the Service Provider to the Initiator; and

preparing by the Initiator a service request using the interface.

6. The method for software deployment according to claim 5, further comprising, prior to the step of sending the requested interface from the Service Provider to the Initiator, the step of authenticating by the Service Provider the interface request.

7. The method for software deployment according to claim 1, further comprising, after the step of initiating the service, the steps of:

terminating the service; and

sending a final accounting message from the Initiator to the Service Provider.

8. The method for software deployment according to claim 7, further comprising, prior to the step of terminating the service, the step of sending at least one interim accounting message from the Initiator to the Service Provider.

9. The method for software deployment according to claim 1, further comprising, after the step of terminating the service, the step of removing by the Initiator the software.

10. The method for software deployment according to claim 1, further comprising, after the step of terminating the service, the step of removing by the at least one Peer the software.

11. The method for software deployment according to claim 5, wherein the interface request comprises:

the address of the Initiator;

a unique identifier for the interface request;

an indication of the requested service;

a random number to be used for authentication; and

an electronic signature that authenticates the Initiator to the Service Provider.

12. The method for software deployment according to claim 11, wherein the indication of the requested service comprises options relevant for the presentation of the requested service.

13. The method for software deployment according to claim 11, wherein the interface comprises:

the unique identifier from the Interface Request;

the requested service interface;

a random value;

a key;

an electronic signature that authenticates the Service Provider to the Initiator.

14. The method for software deployment according to claim 13 wherein the service request comprises:

the unique identifier in the interface request;

a unique identifier for the service request;

an identification of the requested service;

an electronic signature that authenticates the Initiator to the Service Provider; and

a list of at least one Peer, for each Peer comprising;

the address of the Peer;

a notification describing the service;

an identifier of the Initiator;

the key from the interface; and

an electronic signature that authenticates the Initiator.

15. The method for software deployment according to claim 14, wherein the identification of the requested service comprises configuration options.

16. The method for software deployment according to claim 15, wherein the invitation comprises:

a unique identifier for the invitation;

the identification of the offered service with the configuration options;

an interface;

the address of the Initiator;

the identifier of the Initiator;

information about who the Initiator is and what the service is;

the key from the interface; and

an electronic signature authenticating the Initiator to the at least one Peer.

18. The system for software deployment according to claim 17, wherein the Service Provider further registers the service request.

19. The system for software deployment according to claim 17, wherein the Initiator further authenticates the software.

20. The system for software deployment according to claim 17, wherein the at least one Peer further authenticates the software.

21. The system for software deployment according to claim 17, wherein:

the Initiator further;

selects a service;

sends an interface request relating to the selected service to the Service Provider; and

prepares a service request using the interface; and

the Service Provider further sends the requested interface to the Initiator.

22. The system for software deployment according to claim 21, wherein the Service Provider further authenticates the interface request.

23. The system for software deployment according to claim 17, wherein the Initiator further sends a final accounting message to the Service Provider.

24. The system for software deployment according to claim 23, wherein the Initiator further sends at least one interim accounting message to the Service Provider.

25. The system for software deployment according to claim 17, wherein the Initiator further removes the software.

26. The system for software deployment according to claim 17, wherein the at least one Peer further removes the software.

27. The system for software deployment according to claim 21, wherein the interface request comprises:

the address of the Initiator;

a unique identifier for the interface request;

an indication of the requested service;

a random number to be used for authentication; and

an electronic signature that authenticates the Initiator to the Service Provider.

28. The system for software deployment according to claim 27, wherein the indication of the requested service comprises options relevant for the presentation of the requested service.

29. The system for software deployment according to claim 27, wherein the interface comprises:

the unique identifier from the Interface Request;

the requested service interface;

a random value;

a key;

an electronic signature that authenticates the Service Provider to the Initiator.

30. The system for software deployment according to claim 29 wherein the service request comprises:

the unique identifier in the interface request;

a unique identifier for the service request;

an identification of the requested service;

an electronic signature that authenticates the Initiator to the Service Provider; and

a list of at least one Peer, for each peer comprising;

the address of the Peer;

a notification describing the service;

an identifier of the Initiator;

the key from the interface; and

an electronic signature that authenticates the Initiator.

31. The system for software deployment according to claim 30, wherein the identification of the requested service comprises configuration options.

32. The system for software deployment according to claim 31, wherein the invitation comprises:

a unique identifier for the invitation;

the identification of the offered service with the configuration options;

an interface;

the address of the Initiator;

the identifier of the Initiator;

information about who the Initiator is and what the service is;

the key from the interface; and

an electronic signature authenticating the Initiator to the at least one Peer.

17. A system for software deployment in a data communications network, the system comprising:

an Initiator, having an address, that;

sends a service request comprising the address of at least one Peer to a Service Provider; and

installs software received from the Service Provider;

a Service Provider that;

sends an invitation for the service to the at least one Peer;

builds the software for the service; and

distributes the software to the Initiator and the at least one Peer; and

at least one Peer, having an address, that;

sends an accept service message to the Service Provider; and

installs software received from the Service Provider.

33. An Initiator of software deployment in a data communications network that further comprises a Service Provider, and at least one Peer having an address, the Initiator comprising:

a communication unit that;

sends a service request comprising the address of the at least one Peer to the Service Provider; and

receives the software for the service from the Service Provider; and

a processing unit that;

installs the software.

34. The Initiator of software deployment according to claim 33, wherein the processing unit further authenticates the software.

35. The Initiator of software deployment according to claim 33, wherein:

the processing unit further;

selects a service; and

prepares a service request using the interface; and

the communication unit further;

sends an interface request relating to the selected service from the Initiator to the Service Provider; and

sends the requested interface from the Service Provider to the Initiator.

36. The Initiator of software deployment according to claim 33, wherein the communication unit further sends a final accounting message to the Service Provider.

37. The Initiator of software deployment according to claim 33, wherein the communication unit further sends at least one interim accounting message to the Service Provider.

38. The Initiator of software deployment according to claim 33, wherein the processing unit further removes the software.

40. The Peer in software deployment according to claim 39, wherein the processing unit further authenticates the software.

41. The Peer in software deployment according to claim 39, wherein the processing unit further removes the software.

39. A Peer in software deployment in a data communications network that further comprises an Initiator and a Service Provider, wherein the Peer comprises:

a communication unit that;

receives an invitation from the Service Provider;

sends an accept service message to the Service Provider; and

receives software from the Service Provider; and

a processing unit that;

installs the software.

42. A Service Provider for software deployment in a data communications network, the network further comprising an Initiator and at least one Peer having an address, the Service Provider comprising:

a communication unit that;

receives a service request comprising the address of the at least one Peer from the Initiator;

sends an invitation to the at least one Peer;

receives an accept service message from the at least one Peer; and

distributes the software to the Initiator and the at least one Peer; and

a processing unit that;

builds the software for the service.

43. The Service Provider for software deployment according to claim 42, wherein the processing unit further registers the service request.

44. The Service Provider for software deployment according to claim 42,

wherein the communication unit further:

receives an interface request relating to the selected service from the Initiator; and

sends the requested interface to the Initiator.

45. The Service Provider for software deployment according to claim 44, wherein the processing unit further authenticates the interface request.

46. The Service Provider for software deployment according to claim 42, wherein the communication unit further receives a final accounting message from the Initiator.

47. The Service Provider for software deployment according to claim 46, wherein the communication unit further receives at least one interim accounting message from the Initiator.