IP Library Granted Patent US 7,949,735
Granted Patent B2
US 7,949,735 · App. 10/885,754 · Granted May 24, 2011

Transaction process for the provisioning of rules in a rule-based network

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,949,735
App. No.
10/885,754
Granted
May 24, 2011
Kind
B2
Abstract

The invention proposes a transaction process for the provisioning of rules in a network which includes at least one rule server and one rule server client. The process includes a first stage of transmission from the server to the client of a request for acceptance of the provisioning of a set of rules. The process also includes a second stage of reservation by the client of the resources necessary for the reception and the putting into application of the rules if the request is accepted by the client. The process includes a third stage of response to the request, from the client to the server, and a fourth stage for provisioning the set of rules to the client if the response to the request is favorable. When the network has several clients, each of the clients responds to the request from the server, and the provisioning stage is executed only if each response is favorable.

Claims (46)

1. A transaction process for the provisioning of rules in a network that includes a rule server and a server client, the rule server comprising at least a processor, the transaction process comprising:

(a) transmission from the server to the client of a request for acceptance of the provisioning of a set of rules, where the client is attributed to a group of clients;

(b) reservation by the client of the necessary resources for the reception and putting into application of the rules, if the request is accepted by the client;

(c) response to the request, from the client to the server; and

(d) provisioning of functional rules from the server to the client if the response in stage (c) is favorable and responses from other client in the group are favorable,

wherein prior to the provisioning, the client checks whether the provisioning process comprising executing the functional rules will be executed correctly or not in the client, and the client transmits a response indicating that the provisioning process will be executed correctly, the client reserves resources necessary for reception and execution of the rules,

wherein the favorable responses indicate that the provisioning can be implemented in a respective client and the responses are transmitted prior to the provisioning of the rules on the client by the server, and

wherein stages (a), (b) and (c) are carried out for each of the clients in the group, each responding to the request from the server during stage (c), and in which provisioning stage (d) with respect to each client is carried out only if each client response is favorable, and

wherein if the client provides the favorable response and one of other clients in the group does not provide a favorable response, the client is not provisioned, and

wherein the network further comprises a rule manager that modifies one or more rules in the set of rules if one of the clients responds unfavorably and provides the modified set of rules to the server for transmission to the client.

2. A process according to claim 1 , further comprising a stage (e) for releasing the resources reserved by the clients at stage (b), if a response from at least one of the client is not favorable.

3. A process according to claim 1 , which also includes a stage (c′) for the transmission of an error message from the client to the server if the response to the request is not favorable.

4. A process according to claim 3 , where the process further comprises a stage (c″) for transmission from the server to the rule manager of a message that includes at least part of the information contained in the error message sent at stage (c′).

5. A process according to claim 1 , where the network also includes:

several network elements which are clients of the server client, and

a network element manager,

in which reservation of the resources by the client at stage (b) is effected following a preliminary stage (a′) of communication between the server client and the network element manager.

6. A process according to claim 5 , where the network element manager is an integral part of the server client, and in which the communication stage (a′) is an operation within the server client.

7. The process according to claim 1 , wherein the provisioning comprises configuring the client with the rules from the server.

8. The process according to claim 1 , wherein prior to the provisioning, each of the clients in the network receives an inquiry from the server and transmit a response regarding whether the corresponding client has the necessary resources to execute the provisioning of the rules from the server.

9. The process according to claim 1 , wherein:

the provisioning of the rules from the server is applied to the client and at least one additional client,

the provisioning of the rules from the server is not applied to the clients when one of the clients cannot execute the provisioning correctly.

10. The process according to claim 9 , wherein:

prior to the provisioning and after the check, each of the clients transmits a response to the server indicating whether the provisioning process will be executed correctly or not, and

waiting by the server for the response from each of the clients and based on the responses received from all the client, the server determines whether to execute the provisioning of the rules.

11. The process according to claim 10 , wherein when one of the clients transmits a response to the server indicating that provisioning process cannot be executed correctly, the server determines not to execute the provisioning of the rules on all of the clients and instructs the remaining clients to release resources reserved for the provisioning of the rules.

12. The process according to claim 10 ,

prior to the provisioning, each of the clients checks whether the provisioning process will be executed correctly or not in the respective client, and

the provisioning of the rules from the server is not applied to the clients when one of the clients cannot execute the provisioning correctly.

13. The process according to claim 1 , wherein the provisioning of the rules from the server to the client is implemented only after the server receives the favorable response from the client and wherein the request for acceptance of the provisioning of the set of rules includes general characteristics of the set of rules without providing data necessary for implementing actual provisioning of the rules.

14. The process according to claim 1 , wherein the necessary resources are the resources used in the provisioning of the rules from the server when the response is favorable.

15. The process according to claim 1 , wherein said checking whether the provisioning process will be executed correctly or not comprises determining whether the client is capable of receiving and executing the rules and wherein the group of clients are each provisioned independently by same rules.

16. The process according to claim 1 , wherein said checking whether the provisioning process will be executed correctly or not by each of the clients in the group comprises determining whether the resources are available in a local part of the network, which are managed by the server, and whether the resources are sufficient to allow reception and execution of the rules such that same rules are executed in each of the clients in the group.

17. A rule server which has resources to implement a transaction process for the provisioning of rules in a network that includes the rule server and a server client, the rule server comprising at least a processor, the transaction process comprising:

(a) transmission from the server to the client of a request for acceptance of the provisioning of a set of rules, where the client is attribute to a group of clients and the request includes general characteristics of the rules;

(b) checking by the client whether the provisioning process will be executed correctly in the client based on the general characteristics of the rules;

(c) transmitting a favorable response from the client to the server if the client determines that the provisioning process will be executed correctly in the client, and transmitting an unfavorable response if the client determines that the provisioning process will not be executed correctly in the client; and

(d) provisioning of functional roles from the server to the client if the server receives the favorable response from each client in the group,

wherein prior to the provisioning of functional rules, a resource necessary for reception and execution of the functional rules is reserved by the client if the client determines that the provisioning process comprising executing the functional rules will be executed correctly in each client of the group,

wherein the responses indicate that the provisioning can be implemented in a respective client and the responses are transmitted prior to the provisioning of the rules on the client by the server, and

wherein stages (a), (b) and (c) are carried out for each of the clients in the group, each responding to the request from the server during stage (c), and in which provisioning stage (d) with respect to each client is carried out only if each client response is favorable, and

wherein if the client provides the favorable response and one of other clients in the group does not provide a favorable response, the client is not provisioned, and

wherein the network further comprises a rule manager that modifies one or more rules in the set of rules if one of the clients responds unfavorably and provides the modified set of rules to the server for transmission to the client.

18. The rule server according to claim 17 , wherein said checking whether the provisioning process will be executed correctly or not comprises determining whether the client is capable of receiving and executing the rules and wherein the group of clients are each provisioned independently by same rules.

19. The rule server according to claim 17 , wherein said checking whether the provisioning process will be executed correctly or not by each of the clients in the group comprises determining whether the resources are available in a local part of the network, which are managed by the server, and whether the resources are sufficient to allow reception and execution of the rules such that same rules are executed in each of the clients in the group.

Assignments (11)
CHANGE OF NAME Recorded Jan 27, 2022
From: FACEBOOK, INC.
To: META PLATFORMS, INC.
Reel/Frame 058871/0336 →
RELEASE OF SECURITY INTEREST Recorded Dec 12, 2018
From: NOKIA USA INC.
To: PROVENANCE ASSET GROUP, LLC
Reel/Frame 047791/0566 →
RELEASE OF SECURITY INTEREST Recorded Dec 12, 2018
From: NOKIA USA INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC
Reel/Frame 049139/0088 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 3, 2018
From: PROVENANCE ASSET GROUP LLC
To: FACEBOOK, INC.
Reel/Frame 047190/0360 →
PARTIAL RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 043967/0001 Recorded Aug 30, 2018
From: CORTLAND CAPITAL MARKET SERVICES LLC
To: PROVENANCE ASSET GROUP, LLC
Reel/Frame 046981/0600 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
RELEASE OF SECURITY INTEREST Recorded Sep 30, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 033868/0001 →
SECURITY AGREEMENT Recorded Jan 30, 2013
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 029821/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 8, 2004
From: EDWIGES, MAURICE; ROBINSON, JULIEN
To: ALCATEL
Reel/Frame 015559/0689 →