Monitoring and control of administration systems

• US 20060012672A1
• Filed: 06/30/2005
• Published: 01/19/2006
• Est. Priority Date: 07/01/2004
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Tandberg Telecom AS (Cisco Systems, Inc.)
• Inventors: Schrader, Thies, Ingebrigtsen, Tom
• Granted Patent: US 7,675,538 B2
• Time in Patent Office: Days
• US Class Current: 348/14.80
• CPC Class Codes: H04N 7/15 Conference systems

Abstract

The present invention allows administrators of conference equipment, remotely localized from the ordinary managing interface, to execute simple commands for solving a problem that may have occurred during a conference or at conference set up. This is provided by a parser translating user terminal commands transmitted from the user terminal (e.g. a cellular phone) of the system administrator to Conference Management System codes, which are executed on the conference equipment in question from the Conference Management System. The present invention also allows system administrators to be alerted by a message (e.g. SMS) at any errors occurring during a conference or conference set up, and to correct the errors by responding to the alert without the need of addressing the equipment in which the errors occur

Claims

1. A method for providing control and scheduling of conference devices connected to a Conference Management System (CMS) having predefined CMS scheduling and control codes, characterized in

I. receiving a user terminal originated command at least attaching one or more device identifications in a Parser connected to the Conference Management System,

II. making a look up in a first mapping table for said user terminal originated command,

III. if a match between said user terminal originated command and a record in said first mapping table is found, then

a. fetching an CMS scheduling or control code, or a data address pointing at an CMS scheduling or control code, associated with said user terminal originated command from said first mapping table,

b. executing said scheduling or control code on one or more conference device(s) identified by said device identification(s) in the Conference Management System.

2. A method according to claim 1, characterized in

IV. if a match between said user terminal originated command and a record in said first mapping table is not found, then

a. returning an error message to a mobile device from which said mobile device originated command originated.

3. A method according to claim 2, characterized in that the step III further includes:

c. returning a confirmation message to a terminal from which said user terminal originated command originated.

4. A method according to claim 3, characterized in that the conference devices are endpoints, Multi Control Units and/or Gateways.

5. A method according to one of the claims 3, characterized in that said scheduling or control command is a scheduling command further attaching a start and an end time for a conference to be scheduled involving the conference device(s) identified by said device identification(s).

6. A method according to one of the preceding claims, characterized in that said user terminal originated command and device identification(s) originally are captured in an SMS message and addressed by a service number identifying the Conference Management System.

7. A method for providing control and monitoring of conference devices connected to a Conference Management System (CMS) having predefined CMS alerts and control codes, characterized in

I. receiving an CMS alert at least attaching a user terminal address and a conference device identification from the Conference Management System in a Parser connected thereto,

IV. making a look up in a second mapping table for said CMS alert,

V. if a match between said CMS alert and a record in said second mapping table is found, then

a. fetching an user terminal alert associated with said CMS alert from said second mapping table

b. transmitting said user terminal alert including said conference device identification to a user terminal identified by said user terminal address.

8. A method according to claim 7, characterized in

II. creating a Session in said Parser,

III. storing said user terminal address and conference device identification in the Session,

VI. if a user terminal originated command originating from a user terminal identified by said user terminal address is received before a predefined time interval started at the time said Session was created is elapsed, then

a. requesting the session for said stored conference device identification,

b. making a look up in a first mapping table for said user terminal originated command,

c. if a match between said user terminal originated command and a record in said first mapping table is found, then

i. fetching a CMS scheduling or control code, or a data address pointing at a CMS scheduling or control code, associated with said user terminal originated command from said first mapping table,

ii. executing said scheduling or control code on a conference device identified by said device identification in the Conference Management System.

VII. closing said Session in said Parser.

9. A method according to claim 8, characterized in that the step VI further includes:

d. if a match between said user terminal originated command and a record in said first mapping table is not found, then

i. returning an error message to a user terminal from which said user terminal originated command originated.

10. A method according to claim 9, characterized in that the step c further includes:

iii. returning a confirmation message to a user terminal from which said user terminal originated command originated.

11. A method according to one of the claims 10, characterized in that the conference devices are endpoints, Multi Control Units and/or Gateways.

12. A method according to one of the claims 7-11, characterized in that said user terminal originated command originally are captured in an SMS message and addressed by a service number identifying the Conference Management System.

13. A system for providing control, scheduling and monitoring of conference devices connected to a Conference Management System (CMS) having predefined CMS alerts, scheduling and control commands, characterized in

a storing device including a first mapping table mapping the predefined CMS alerts with associated user terminal alerts and a second mapping table mapping the predefined CMS scheduling and control codes, or data addresses respectively pointing at CMS scheduling or control codes, with associated user terminal commands,

a Parser adjusted to make a look up in said first mapping table for one of the predefined CMS alerts and to fetch an associated one of said user terminal alerts, and further adjusted to make a look up in said second mapping table for one of said user terminal commands and to fetch an associated one of the CMS scheduling and control codes, or the respective data addresses,

a communication network adjusted to receive user terminal alerts transmitted from said Parser, and to transmit user terminal commands to said Parser, and

that the CMS is configured to transmit CMS alerts each attaching a user terminal address and one or more conference device identification(s) to said Parser and to instantaneously execute the CMS scheduling and control codes received or disclosed from the Parser.

14. A system according to claim 13, characterized in that the Parser is configured to create a Session when receiving an CMS alert and storing a user terminal address and conference device identification attached to said CMS alert in the Session, and further to interpret a user terminal command, originating from a user terminal identified by said stored user terminal address, received within a time interval started when said Session was crated, as a response to said CMS alert, and then addressing an CMS control code associated with said user terminal command with said stored conference device identification.

15. A system according to claim 13 or 14, characterized in that said communication network is a GSM or UMTS network, wherein said user terminal commands transmitted from said network are provided to said Parser from a CPA (Content Provider Access) gateway originating from SMS messages transmitted to said CPA from an SMS server associated with said GSM or UMTS network, said CPA is further configured to provide said user terminal alerts transmitted from the Parser to said GSM or UMTS network via said SMS server.