IP Library Granted Patent US 7,757,211
Granted Patent B2
US 7,757,211 · App. 10/837,771 · Granted Jul 13, 2010

Managed object member architecture for software defined radio

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,757,211
App. No.
10/837,771
Granted
Jul 13, 2010
Kind
B2
Abstract

A method for managing a flow of information in an object oriented software environment. A master MOM ( 130 ) and at least a second MOM ( 135 ) can be initialized. A third MOM ( 140 ) also can be initialized. A change resolution ( 150 ), which includes data correlating to a change in a device in a system, can be automatically propagated from the second MOM to the master MOM. The change can be a change in configuration data or a change in a run-time state of the device. Data in the master MOM correlating to the change resolution can be updated. In response to the change resolution, a change publication ( 160 ), which includes data correlating to the change resolution, can be automatically propagated from the master MOM to at least the third MOM. Data in the third MOM correlating to the change publication can be updated.

Claims (29)

1. A method comprising:

storing update data in a temporary data structure in a first managed object member of a first remote node in a communication system, wherein the update data is received from a second remote node in the communication system; and

deleting the temporary data structure in response to transmitting the update data to a master remote node in the communication system;

wherein the master remote node comprises a master data structure with master data elements, and wherein the master data structure comprises a complete data set of the communication system; and

wherein the temporary data structure is configured to store at least a portion of the update data in an update data element that is different than the master data elements of the master data structure.

2. The method of claim 1 , wherein the update data is at least one of configuration data or run-time data.

3. The method of claim 1 , further comprising validating the update data at the first remote node prior to transmitting the update data to the master remote node.

4. The method of claim 1 , further comprising updating the master data structure with the update data in response to validation of the update data at the master remote node, wherein the master remote node comprises a master managed object member that includes the master data structure.

5. The method of claim 4 , further comprising initializing a second managed object member in a third remote node.

6. The method of claim 5 , wherein the second managed object member is initialized from at least one of the master managed object member, a parent managed object member, a backup managed object member, or a persistent data store.

7. The method of claim 5 , further comprising storing data in a fractional data structure of the second managed object member, wherein the fractional data structure comprises a subset of data from the master data structure.

8. The method of claim 5 , further comprising subscribing the second managed object member to a data topic, wherein the second managed object member receives updates from at least one of a parent managed object member or the master managed object member.

9. The method of claim 8 , further comprising receiving verification in response to successfully subscribing to the data topic, wherein the second managed object member periodically attempts to subscribe to the data topic until verification is received from at least one of the parent managed object member or the master managed object member.

10. The method of claim 8 , further comprising automatically propagating, in response to updating the master data structure, a change publication from the master managed object member to a subscribed managed object member, wherein the subscribed managed object member is subscribed to a data topic correlating to the update data.

11. The method of claim 10 , wherein the subscribed managed object member is at least one of the first managed object member or the second managed object member.

12. The method of claim 10 , wherein the change publication comprises the update data.

13. The method of claim 10 , wherein the change publication comprises an invitation for the subscribed managed object member to initiate communications with at least one of the parent managed object member or the master managed object member to facilitate retrieving the update data.

14. The communications system of claim 1 , wherein the communication system is at least one of a software defined radio system, a mobile radio communication system, a cellular telephone communication system, or a telemetry system.

15. The communications system of claim 1 , wherein at least one of the first remote node or the second remote node is individually at least one of an operations and maintenance center-radio (OMC-R) server, an OMC-R client, a base station system, or a base transceiver station.

16. A communications system comprising:

a first remote node comprising a memory and a first managed object member, wherein the first managed object member comprises a temporary data structure configured to store update data;

a second remote node comprising a memory, wherein the second remote node is configured to communicate the update data to the first remote node; and

a master remote node comprising a memory and a master data structure with master data elements, wherein the master data structure comprises a complete data set of the communication system;

wherein the first managed object member is configured to delete the temporary data structure in response to transmitting the update data to the master remote node; and

wherein the temporary data structure is configured to store at least a portion of the update data in an update data element that is different than the master data elements of the master data structure.

17. The communications system of claim 16 , further comprising a master managed object member of the master remote node, wherein the master managed object member includes the master data structure, and wherein the master data structure is updated with the update data in response to validation of the update data at the master remote node.

18. The communications system of claim 17 , further comprising a third remote node comprising a memory and a second managed object member, wherein the second managed object member is configured to be initialized from at least one of the master managed object member, a parent managed object member, a backup managed object member, or a persistent data store.

19. The communications system of claim 18 , wherein the second managed object member further comprises a fractional data structure configured to store a subset of data from the master data structure.

20. The communications system of claim 18 , wherein the second managed object member is configured to be subscribed to a data topic, and wherein the second managed object member is configured to receive updates from at least one of a parent managed object member or the master managed object member.

Assignments (3)
MERGER Recorded Dec 8, 2015
From: TREBLE INVESTMENTS LIMITED LIABILITY COMPANY
To: RATEZE REMOTE MGMT. L.L.C.
Reel/Frame 037238/0331 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 17, 2007
From: AIRNET COMMUNICATIONS CORPORATION
To: TREBLE INVESTMENTS LIMITED LIABILITY COMPANY
Reel/Frame 019974/0087 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 3, 2004
From: JORDAN, THOMAS L.; ADKINS, RONALD P.
To: AIRNET COMMUNICATIONS CORPORATION
Reel/Frame 015297/0534 →