Terminal data format and a communication control system and method using the terminal data format

• US 20060149824A1
• Filed: 12/30/2005
• Published: 07/06/2006
• Est. Priority Date: 12/30/2004
• Status: Abandoned Application

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Kim, Hye-Jong, Shim, Hyun-Sik, Park, Jae-Seok, Kang, Bo-Hyun
• Application Number:
  US11/323,775
• Publication Number:
  US 20060149824A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A terminal data format capable of efficiently controlling various network-based robots in a ubiquitous robotic companion (URC)-based infrastructure, a communication control system using the terminal data format, and a method thereof are provided. The data format includes a Protocol Discriminator field including information on a protocol identifier (ID) in order to permit interfacing between a robot, a server, and a client; a Session ID field for identifying a currently connected session; a Profile ID field for identifying a profile performed by any one of the robot, the server, and the client; an MSG Type field including information on types of messages transceived between the robot, the server, and the client; and a Payload field for performing a service for a corresponding function according to data defined in the MSG Type field and the profile information included in the Profile ID field.

Claims

1. A data format for transmitting data between a terminal and a server, the data format comprising:

a Protocol Discriminator field for permitting interfacing between the terminal and the server;

a Session identification (ID) field for setting up an ID to identify the terminal;

a Data Direction field for setting up a direction to transmit the data between the terminal and the server;

a Data Type field for representatively defining at least one of the format and content of the data;

a Service ID field for determining if a message service to be performed by at least one of the terminal and the server is used, and setting up an ID to identify the determination; and

a Payload field for setting up the data defined in the Data Type field and an available service determined in the Service ID field, and assigning a message to enable the terminal and the server to use the service.

2. The data format according to claim 1, wherein the message of the Payload field is divided into messages for video, audio, and movement, the message for video and the message audio having file number and size, and video data, and the message for movement having robot movement, robot status control, robot status report, robot error status, and command type of camera control according to a control form to control the movement.

3. The data format according to claim 2, wherein:

the file number is formed of a client type, a client ID, and a file generation sequence;

the robot movement is a message for controlling movement and has x-axis movement distance and y-axis movement distance of the terminal, a position angle of the terminal, and a camera angle to control the movement;

the robot status control has a status report and a reporting period of the terminal in order to confirm a current status of the terminal in real time;

the robot status report is a message indicating a service result of the terminal and has messages of status information such as an unmanned alarm set status according to the robot movement status, a movement status of the terminal, a monitoring status, an abnormal status, an identity confirmation status, an alarm status, position information of the terminal, and action completion information;

the robot error status is a message indicating an operation condition of the terminal to determine if at least one terminal is abnormal; and

the camera control is a message related with video transmission.

4. The data format according to claim 2, wherein the Payload field further comprises:

a Client Type field;

a Client ID field;

a User ID field;

an Authorization code field; and

a Message Type Field,

provide ASR (Automatic Speech Recognition) data for recognizing voice, TTS (Text To Speech) data to output voice, FR (Face Recognition)/MD (Motion Detection) data for identifying a face and detecting motion, Authorization data for authorization, Movement data, and VoIP data.

5. The data format according to claim 4, wherein:

the Client Type field indicates a kind of terminal corresponding to the directionality information of the Data Direction field;

the Client ID field sets up an ID corresponding to at least one terminal and is used to identify a terminal corresponding to the directionality information of the Data Direction field;

the User ID field sets up an ID with which the server recognizes the at least one terminal, the ID having a message corresponding to a number of registered users; and

the Authorization Code field provides authorization numbers of each of the at least one terminals.

6. The data format according to claim 4, wherein the Message Type field provides procedures for connection initialization between the terminal and the server, response, synchronization, authorization, and data transmission, and

wherein the message transmitted between the terminal and the server includes a message for a first message group to connect the terminal to the server, a second message group to make an authorization between the terminal and the server, a message for continuity of the first and second message groups, a Payload message to be transmitted between the authorized terminal and server, and a termination message.

7. The data format according to claim 6, wherein the first message group comprises:

a Request Message;

a Acknowledgement Response Message; and

Error Acknowledgement Response Message,

the second message group comprises;

an Authorization Message;

a Positive Authorization Message; and

Negative Authorization Message, the message for continuity is Synchronization Message,

wherein the Payload message is a Data Message, and the termination message is a Close Report Message.

8. The data format according to claim 1, wherein the terminal includes at least one of at least one robot and at least one client terminal.

9. The data format according to claim 1, further comprising a Protocol Version field for indicating an update status of the data format.

10. A communication control system utilizing a specialized data format on a basis of wired and wireless communication, the system comprising:

a terminal for performing at least one service for video, audio, and movement according to Payload contents of the specialized data format; and

a server for recognizing user commands through the terminal to transmit and receive the specialized data format to and from the terminal according to corresponding protocol, and controlling to perform the service with the data format,

wherein the specialized data format includes a Protocol Discriminator field for permitting interfacing between the terminal and the server, a Session identification (ID) field for setting up an ID to identify the terminal, a Data Direction field for setting up a direction to transmit the data between the terminal and the server, a Data Type field for defining at least one of the format and content of the data, a Service ID field for determining if a message service to be performed by at least one of the terminal and the server is used, and setting up an ID to identify the determination, and a Payload field for setting up the data defined in the Data Type field and an available service determined in the Service ID field, and assigning a message to enable the terminal and the server to use the service.

11. The communication control system according to claim 10, wherein the terminal comprises at least one of at least one robot and at least one client terminal.

12. The communication control system according to claim 11, wherein the at least one robot processes the voice message from a user into a data format to operate by itself, provides the server with the data format, and performs a corresponding service message to inform the user of the result, and

the client terminal processes the user'"'"'s desired service message into the data format in order to control the robot, transmits the data format to the server, and receives the service result of the robot from the server to inform the user of the result.

13. The communication control system according to claim 12, wherein the message is a Payload message including a message for authorization number and procedure, a video recognition message, a speech recognition message, and a control message for movement, and provides the user with unmanned security and remote monitoring services.

14. A method of transmitting a terminal data format between at least one terminal and a server using a corresponding protocol on a basis of wired and wireless communication, the method comprising the steps of:

confirming an authorization between the terminal and the server using the terminal data format according to an authorization procedure;

assigning a Session identification (ID) to identify each of the at least terminal using the terminal data format after the authorization;

inputting a voice command of a user to a corresponding terminal assigned the Session ID;

transmitting a Payload message of the terminal data format having voice data to the server;

analyzing the Payload message in order to call back to the Service ID; and

transmitting, by the corresponding terminal performing an operation according to the Service ID, the result to the server as a Payload message of the packet.

15. The method according to claim 14, wherein the service corresponding to the Service ID performs unmanned security, remote monitoring, speech recognition, video recognition, and movement control.

16. The method according to claim 14, wherein the authorization procedure comprises the steps of:

attempting access, by the terminal, to the server by sequentially performing Request Message, Acknowledge response Message, and Error Acknowledge response Message of Message Type corresponding to an internal field of the Payload message of the data format; and

assigning an authorization number according to an authorization request of the terminal by sequentially performing Authorization Message, Positive Authorization Message, and Negative Authorization Message of the Message Type after making the connection.

17. The method according to claim 16, wherein, when the terminals include a plurality of terminals, the step of assigning the authorization number further comprises the steps of:

receiving a list of the plurality of terminals; and

transmitting an authorization request message to a desired corresponding terminal using a Select Message.

18. The method according to claim 14, wherein the terminal is formed of at least one of at least one robot and at least one client terminal.

19. A data format for a terminal, in which the data format is transceived between a robot, a server, and a client in order to control the robot, the data format comprising:

a Protocol Discriminator field including information on a protocol identifier (ID) in order to permit interfacing between the robot, the server, and the client;

a Session ID field including unique ID information for identifying a currently connected session;

a Profile ID field including information for identifying a profile performed by any one of the robot, the server, and the client;

an MSG Type field including information on types of messages transceived between the robot, the server, and the client; and

a Payload field including the message for performing a service for a corresponding function according to data defined in the MSG Type field and the profile information included in the Profile ID field.

20. The data format according to claim 19, wherein the profile of the server comprises at least one of:

an authentication profile for authenticating the robot and the client;

a remote control profile for providing an interface that enables the client to remotely control the robot;

an event profile for enabling one of the server and the client to control an event of the robot;

a speech recognition profile for recognizing a voice of a voice command received from the robot;

a speech synthesis profile for synthesizing speech recognition data with text data;

an image recognition profile for recognizing image information transmitted from the robot; and

a motion detection profile for detecting motion of the robot.

21. The data format according to claim 19, wherein the profile of the robot comprises at least one of:

a move profile for robot position movement;

a navigation profile;

a speech detection profile of a voice command;

a sound profile for outputting data to voice synthesis provided from the server;

a motion profile for controlling movement of the robot; and

an emotion profile for performing an emotion expression function of the robot.

22. The data format according to claim 21, wherein the profile of the robot further comprises an event provision profile for providing information on a movement transition event to one of the server and client, when a movement control message of the robot is received from one of the server and client and a movement state of each component of the robot is in transition.

23. The data format according to claim 22, wherein the movement transition event divides the movement state of each component of the robot into IDLE and ACTIVE states, and divides events of START and END when one of the robots states transitions to the other.

24. The data format according to claim 20, wherein the profile of the server further comprises a Heartbeat request profile for transmitting a Heartbeat request message by periods in order to detect a network connection status of the robot.

25. The data format according to claim 21, wherein the profile of the robot further comprises a Heartbeat response profile of transmitting a Heartbeat response message to the server according to a Heartbeat request message transmitted from the server by periods in order to detect a network connection status of the robot.

26. A communication control system comprising:

a robot for performing at least one of video, audio, and movement services according to content of Payload of a previously set data format;

a server for recognizing a command of a user through the robot, for transceiving the data format with respect to the robot according to a corresponding protocol, and for performing the service with the data format; and

a client for performing a remote control and monitoring service of the robot through the server at a remote position.

27. The communication control system according to claim 26, wherein the robot provides information on a movement transition event to one of the server and client when a control message for controlling each component included in the robot is received from one of the server and client to drive the corresponding component and a movement state of the corresponding component is in transition.

28. The communication control system according to claim 27, wherein the movement transition event information divides the movement state of each component of the robot into IDLE and ACTIVE states, and includes information on events of START and END, when one of the states transitions to the other.

29. The communication control system according to claim 26, wherein the server transmits a Heartbeat request message by periods in order to detect a network connection status of the robot, and detects the network connection status of the robot depending on if a Heartbeat response message is received from the robot.

30. The communication control system according to claim 29, wherein the robot transmits the Heartbeat response message to the server according to the Heartbeat request message transmitted from the server by periods.

31. The communication control system according to claim 26, wherein the server performs authentication of the client in order to enable the client to remotely control the robot, provides information on a list of the robots connected therewith to the client, and provides an interface between the robot and the client when the robot to be controlled is allocated by the client.

32. The communication control system according to claim 26, wherein the data format set previously between the robot, the server, and the client comprises:

a Protocol Discriminator field including information on a protocol identifier (ID) in order to permit interfacing between the robot, the server, and the client;

a Session ID field including unique information for identifying currently connected sessions;

a Profile ID field including information for identifying a profile performed by any one of the robot, the server, and the client and the other profiles performed by the others;

an MSG Type field including information on types of messages transceived between the robot, the server, and the client; and

a Payload field including the message for performing a service for a corresponding function according to data defined in the MSG Type field and the profile information included in the Profile ID field.

33. The communication control system according to claim 32, wherein the profile of the server comprises at least one of:

an authentication profile for performing authentication of the robot and the client;

a remote control profile for providing an interface to enable the client to remotely control the robot;

an event profile for enabling one of the server and the client to control an event of the robot;

a speech recognition profile for recognizing a voice of a voice command received from the robot;

a speech synthesis profile for synthesizing speech recognition data with text data;

an image recognition profile for recognizing image information transmitted from the robot; and

a motion detection profile for detecting movement of the robot.

34. The communication control system according to claim 32, wherein the profile of the robot comprises at least one of:

a move profile for robot position movement;

a navigation profile;

a speech detection profile for a voice command;

a sound profile for outputting data to voice synthesis provided from the server;

a motion profile for controlling movement of the robot; and

an emotion profile for performing an emotion expression function of the robot.

35. A method of controlling at least one robot using at least one remote client in a communication control system having the at least one remote client, the at least one robot, and a server providing an interface between the at least one remote client and the at least one robot, the method comprising the steps of:

providing, by the at least one remote client, connection to the server in order to perform a service for remote control;

monitoring any of the at least one robots;

requesting authentication and information on a list of the at least one robot connected to the server;

performing, by the server, the authentication of the at least one remote client;

transmitting the list information of the at least one robot connected with the server to the at least one remote client;

selecting, by the at least one remote client, the at least one robot to be controlled using the robot list information transmitted from the server;

transmitting the corresponding information to the server;

setting, by the server, an interface between the robot selected by the at least one remote client and the at least one remote client in order to transceive a message for the robot remote control; and

monitoring service.

36. The method according to claim 35, wherein when the interface is set between the at least one remote client and the at least one robot selected by the at least one client, the method further comprising the steps of:

subscribing to, by the at least one remote client, various service channels for controlling the robot through the server;

making, by the at least one remote client, a request to the robot for information on an image picked up by the robot and information on a status of the robot through the server after subscribing to the channels;

transmitting a control message for controlling an arbitrary function of the robot according to the image information and the status information that are transmitted from the robot by periods;

performing, by the robot, a corresponding function according to the control message transmitted from the at least one remote client through the server;

transmitting information on events of a start time point and end time point of the corresponding function to the client through the server;

transmitting, by the at least one remote client, a message of requesting to terminate connection with the robot to the server when the robot remote control and monitoring service is finished; and

logging out the connection with the robot.

37. The method according to claim 36, further comprising the steps of:

transmitting, by the server, a Heartbeat request message to the robot by periods in order to check a network connection status of the robot;

transmitting, by the robot, a Heartbeat response message according to the Heartbeat request message transmitted from the server; and

notifying information on the network connection status to the server.