An apparatus and method control a connection between peripheral devices in a control server of a wireless communication system providing an ip-based communication service. The method for controlling the connection between peripheral devices includes registering at least one device in a group list classified by user identification information. The method also includes, if a control node including a user identifier of the group list requests a control of any one device included in the group list, checking an ip address of the device that is requested to be controlled by the control node. The method further includes sending a control command of the control node using the ip address.
|
1. A method for controlling a connection between devices in a control server of a wireless communication system providing an ip-based communication service, the method comprising:
registering devices in a group list classified by user identification information of a control node;
receiving a request from the control node to control a device included in the group list;
checking, at the control server, an ip address of the device that is requested to be controlled by the control node; and
sending a control command of the control node using the ip address.
13. A wireless communication system providing an ip-based communication service, comprising:
at least one device configured to request registration to a control server; and
the control server configured to register devices requesting registration in a group list classified by user identification information of a control node and, when a request is received from the control node to control a device included in the group list, check an ip address of the device that is requested to be controlled by the control node and send a control command of the control node using the ip address.
7. A control server for controlling a connection between devices of a wireless communication system providing an ip-based communication service, the control server comprising:
a communication interface configured to transmit and receive signals;
an ip address checker configured to check an ip address of at least one device;
a group controller configured to register devices in a group list classified by user identification information of a control node; and
a controller configured to check an ip address of a device that is requested to be controlled by the control node through the ip address checker when a request is received from the control node to control a device included in the group list through the communication interface, and send a control command of the control node using the ip address.
2. The method of
3. The method of
checking registration information of a device requesting registration;
if any one device requests a search, checking search request information received from the device requesting the search; and
if the registration information is matched with the search request information, adding the device requesting the registration to a group list classified by user identification information of the device requesting the search.
4. The method of
5. The method of
6. The method of
8. The control server of
9. The control server of
if at least one device requests registration, the group controller checks registration information of a device requesting registration,
if any one device requests a search, the group controller checks search request information received from the device requesting the search, and
if the registration information is matched with the search request information, the group controller adds the device requesting the registration to a group list classified by user identification information of the device requesting the search.
10. The control server of
11. The control server of
12. The control server of
14. The wireless communication system of
15. The wireless communication system of
16. The wireless communication system of
the control server checks registration information of a device requesting registration,
if any one device requests a search, the control server checks search request information received from the device requesting the search, and
if the registration information is matched with the search request information, the control server adds the device requesting the registration to a group list classified by user identification information of the device requesting the search.
17. The wireless communication system of
18. The wireless communication system of
19. The wireless communication system of
20. The wireless communication system of
|
The present application is related to and claims priority under 35 U.S.C. §119 to an application filed in the Korean Intellectual Property Office on Jun. 30, 2010 and assigned Serial No. 10-2010-0062555, the contents of which are incorporated herein by reference.
The present invention relates generally to an Internet Protocol (IP)-based wireless communication system, and more particularly, to an apparatus and method for controlling peripheral nodes using a control server in an IP-based wireless communication system.
In an IP-based wireless communication, when a mobile node is accessed to a network, the mobile node is allocated a dynamic IP address through a Dynamic Host Configuration Protocol (DHCP). Thereafter, the mobile node transmits or receives signals using the allocated IP as an address.
As described above, the mobile node transmits or receives signals using an IP allocated from a network as an address. In other words, a user should know the correspondent's IP address so that the user can communicate with a correspondent node. Accordingly, whenever the correspondent node's IP changes, the user should know the correspondent node's changed IP.
In addition, if a correspondent node a user intends to access has no display device, the user cannot check the correspondent's IP and thus cannot control the correspondent node easily.
An object of the present invention is to substantially solve at least the above problems and/or disadvantages and to provide at least the advantages below. Accordingly, an object of the present invention is to provide an apparatus and method for controlling peripheral nodes in an IP-based wireless communication system.
Another object of the present invention is to provide an apparatus and method for grouping peripheral nodes using user identification information as a category in an IP-based wireless communication system.
Another object of the present invention is to provide an apparatus and method for grouping peripheral nodes using user identification information as a category in a provider server of an IP-based wireless communication system.
Another object of the present invention is to provide an apparatus and method for registering peripheral nodes in a category of user identification information in an IP-based wireless communication system.
Another object of the present invention is to provide an apparatus and method for connecting a control node and peripheral nodes using group information of the peripheral nodes in a provider server of an IP-based wireless communication system.
According to an aspect of the present invention, a method for controlling a connection between devices in a control server of a wireless communication system providing an IP-based communication service is provided. The method includes registering at least one device in a group list classified by user identification information. The method also includes, if a control node including a user identifier of the group list requests a control of any one device included in the group list, checking an IP address of the device that is requested to be controlled by the control node. The method further includes sending a control command of the control node using the IP address.
According to another aspect of the present invention, an apparatus for controlling a connection between devices in a control server of a wireless communication system providing an IP-based communication service is provided. The apparatus includes a communication interface configured to transmit and receive signals. The apparatus also includes an IP address checker configured to check an IP address of at least one device. The apparatus further includes a group controller configured to register at least one device in a group list classified by user identification information. The apparatus still further includes a controller configured to check an IP address of a device that is requested to be controlled by the control node through the IP address checker, if a control node including a user identifier of the group list requests a control of any one device included in the group list through the communication interface, and send a control command of the control node using the IP address.
According to another aspect of the present invention, a wireless communication system providing an IP-based communication service is provided. The communication system includes at least one device configured to request registration to a control server. The communication system also includes the control server configured to register at least one device requesting registration in a group list classified by user identification information and, if a control node including a user identifier of the group list requests a control of any one device included in the group list, check an IP address of the device that is requested to be controlled by the control node and send a control command of the control node using the IP address.
Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses embodiments of the invention.
Before undertaking the DETAILED DESCRIPTION OF THE INVENTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation; the term “or,” is inclusive, meaning and/or; the phrases “associated with” and “associated therewith,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like. Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings in which:
Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures.
Exemplary embodiments of the present invention that provide a technique for controlling a connection between peripheral nodes in an IP-based wireless communication system will be described.
In the following description, nodes refer to devices that provide IP-based wireless communication functions. For example, the nodes may include a portable terminal using a communication scheme based on the Long Term Evolution (LTE) standard, a Personal Digital Assistant (PDA), and a notebook Personal Computer (PC).
In the following description, the wireless communication system registers one or more peripheral nodes in a control server, as illustrated in
In the following description, the control node refers to any one node that provides a control command among one or more nodes grouped by the control server, and the peripheral nodes refer to nodes, except the control node, among the grouped nodes. For example, if a user controls other nodes using a mobile device, the mobile device corresponds to the control node and the controlled nodes correspond to the peripheral nodes.
In the following description, the control server refers to a server that controls the control node, a group list of the peripheral nodes, and a connection between the control node and the peripheral nodes. It will be assumed that the control server is a provider server that provides a communication service and knows an IP allocated to each node.
As illustrated in
TABLE 1
Parameter
Description
Remarks
Device
Node type. Device Type is used for
PMP, digital photo
Type
indicating device ion or name in a
frame, digital
control node or for classifying
camera., MP3, etc.
categories of nodes.
Model
Model name is used because a user
Name
may have nodes with the same device
type. Model Name is used as a
registration key.
Serial
Serial Number is used as a
Registration and
Number
registration key.
grouping.
Support
1. Action: node function (reproduction
Ability
of moving picture, MP3 play, operation
of surveillance camera, cleaning)
2. Support Ability, Multimedia
format information
In Table 1 above, the device type is used for classification of categories in the user interface. When there are many nodes registered in the control server 110, the device type facilitates the expression of the user interface.
The model name and the serial number are used for identifying the peripheral nodes that are being registered.
The support ability includes information on functions that the peripheral nodes requesting registration can support. For example, when the peripheral node requesting registration is a multimedia device, the support ability includes information on codec available in the peripheral node.
When receiving the registration request of the peripheral node 120, the control server 110 maintains a registration waiting state with respect to the peripheral node 120 for a predetermined time. That is, when receiving the registration request of the peripheral node 120, the control server 110 determines whether the control node 110 requests a search for the peripheral node 120 for a predetermined time.
In step 133, the control node 100 requests the control server 110 to search the peripheral node in order to authenticate the peripheral node requesting registration to the control server 110. The control node 100 also sends peripheral node search information to the control server 110. The search information includes the model name and/or the serial number. For example, as illustrated in
In step 135, the control server 110 determines whether the registration request of the peripheral node 120 is matched with the search request of the control node 100. For example, the control server 110 determines whether the registration information of the peripheral node 120 is matched with the search information provided from the control node 100. If the registration information of the peripheral node 120 is not matched with the search information provided from the control node 100, the control server 110 cannot authenticate the peripheral node 120 and thus recognizes that the registration of the peripheral node 120 is failed. Although not shown, the control server 110 may send a registration fail signal to the control node 100 and the peripheral node 120.
Alternatively, if the registration information of the peripheral node 120 is matched with the search information provided from the control node 100, the control server 110 can authenticate the peripheral node 120 and thus recognizes that the peripheral node 120 can be registered in a group list.
Accordingly, the control server 110 adds the peripheral node 120 to the group list of the control node 100 in step 137. For example, the control server 110 adds the peripheral node 120 to the group list of the control node 100 grouped by the phone number. Although not shown, the control server 110 may also add the peripheral node 120 to a routing table of the control node 100.
In step 139, the control server 110 sends a response signal to the control node 100 with respect to the search request. The response signal with respect to the search request of the control node 100 includes the registration information of the peripheral node 120 and the updated group list.
In addition, the control server 110 sends a response signal to the peripheral node 120 with respect to the registration request in step 141. The response signal with respect to the registration request of the peripheral node 120 includes a group list of a group in which the peripheral node 120 is registered.
When the peripheral node 120 requests connection to the control server 110 in step 151, the control server 110 checks a version of the group list the peripheral node 120 has in step 153. If the version of the group list the peripheral node 120 has is different from the version of the group list the control server 110 has, the control server 110 sends the group list to the peripheral node 120 in step 155.
In the above-described embodiment, after the peripheral node 120 requests the registration, the control node 100 requests the search. A registration requesting process of the peripheral node 120 and a search requesting process of the control node 100 are performed in parallel. Accordingly, the registration requesting process of the peripheral node 120 and the search requesting process of the control node 100 may be performed at the same time. In addition, after the control node 100 requests the search, the peripheral node 120 may request the registration.
Referring to
If the peripheral node does not request the registration, the control server ends the algorithm.
Alternatively, if the peripheral node requests the registration, the control server proceeds to step 203 to check registration information of the peripheral node included in the registration request signal received from the peripheral node. For example, the control server checks the registration information of the peripheral node as shown in Table 1 above.
In addition, if the peripheral node requests the registration, the control server proceeds to step 205 to drive a first timer. The first timer is used for checking a registration waiting time with respect to the peripheral node. That is, the driving time of the first timer is identical to the registration waiting time.
The control server proceeds to step 207 to determine whether the driving time of the first timer is expired.
If the driving time of the first timer is expired, the control server cannot authenticate the peripheral node and thus recognizes that the registration of the peripheral node is failed. Accordingly, the control server ends the algorithm. Although not shown, the control server may send a registration fail signal to the control node and the peripheral node.
Alternatively, if the driving time of the first timer is not expired, the control server proceeds to step 209 to determine whether the control node requests the search. For example, the control server determines whether a search request signal is received from the control node.
If the control node does not request the search, the control server proceeds to step 207 to determine whether the driving time of the first timer is expired.
Alternatively, if the control node requests the search, the control server proceeds to step 211 to check the search information of the control node included in the search request signal received from the control node. If the control node requests the search, the control server terminates the driving of the first timer. The search information includes a model name and/or a serial number of the peripheral node.
Then, the control server proceeds to step 213 to determine whether the registration request of the peripheral node is matched with the search request of the control node. For example, the control server determines whether the registration information of the peripheral node is matched with the search information of the control node.
If the registration information of the peripheral node is not matched with the search information of the control node, the control server cannot authenticate the peripheral node and thus recognizes that the registration of the peripheral node is failed. Accordingly, the control server ends the algorithm. Although not shown, the control server may send a registration fail signal to the control node and the peripheral node.
Alternatively, if the registration information of the peripheral node is matched with the search information of the control node, the control server can authenticate the peripheral node and thus recognizes that the peripheral node can be registered in the group list of the control node. Accordingly, the control server proceeds to step 215 to add the peripheral node to the group list of the control node. For example, the control server adds the peripheral node to the group list grouped by the phone number of the control node. Although not shown, the control server may add the peripheral node to a routing table of the control node.
After the peripheral node is added to the group list, the control server proceeds to step 217 to send group list information to the control node and the peripheral node.
Then, the control server ends the algorithm.
In the above-described embodiment, the control server registers and groups the peripheral node using the registration request signal and the search request signal that are received from the peripheral node and the control node, respectively.
In another embodiment, the control server may receive the peripheral node information directly from the user or the provider, and register and group the corresponding peripheral node. In such an embodiment, the user includes the control node.
A method for controlling peripheral nodes using a group list and a control server will be described below.
As illustrated in
In step 333, the control server 310 checks information of the peripheral node 320 which is requested to be controlled by the control node 300. For example, the control server 310 checks registration information of the peripheral node 320 through the group identifier of the peripheral node 320. In step 335, the control server 310 requests connection to the peripheral node 320 using an IP address matched with the group identifier of the peripheral node 320 checked in a routing table.
If the control server 310 requests the connection, the peripheral node 320 determines whether an operation state thereof is an active state or an idle state. If the peripheral node 320 is in an idle state, the peripheral node 320 is switched to an active state.
In step 337, the peripheral node 320 sends a response signal, including active state information, to the control server 310.
In step 339, if the peripheral node 320 is in the active state, the control server 310 sends a control command of the control node 300 to the peripheral node 320.
In step 341, the peripheral node 320 executes the control command received from the control server 310. For example, if the peripheral node 320 is a robot cleaner, the robot cleaner may perform a cleaning function under the control of the control node 300.
If the control server 310 does not receive the response signal from the peripheral node 320 for a predetermined time, the control server 310 recognizes that it cannot control the peripheral node 320. Accordingly, the control server 310 may send a control fail signal to the control node 300.
In the above-described embodiment, when the control server 310 requests the connection to the peripheral node 320, the peripheral node 320 determines whether an operation state thereof is an active state or an idle state.
In another embodiment, when the control server 310 requests the connection to the peripheral node 320, the peripheral node 320 may check the operation state thereof and determine whether it can execute the control command of the control node 300. Then, the peripheral node 320 sends a response signal, including whether the peripheral node 320 executes a control command, to the control server 310. If the peripheral node 320 can perform the control command, the control server 310 sends the control command of the control node 300 to the peripheral node 320. Alternatively, if the peripheral node 320 cannot perform the control command, the control server 310 recognizes that it cannot control the peripheral node 320.
A method for controlling data transmission between peripheral nodes using a group list and a control server will be described below.
As illustrated in
In step 433, the control server 410 checks the information of the peripheral node 1 420-1 and the peripheral node 2 420-2 which are requested to be controlled by the control node 400. For example, the control server 410 checks IP addresses matched with the group identifiers of the source node and the destination node in a routing table.
In step 435, the control server 410 requests data transmission to the peripheral node 2 420-2 using the checked IP address of the source node. The control server 410 also sends the IP address information of the destination node to the peripheral node 2 420-2.
In step 439, the peripheral node 2 420-2 transmits data to the peripheral node 1 420-1 using the IP address of the destination node received from the control server 410.
The configuration of the control server for controlling communication between the nodes as described above will be described below.
As illustrated in
The communication interface 501 transmits/receives a signal to/from at least one node.
The controller 503 controls an overall operation of the control server 500. That is, the controller 503 controls nodes registered in the control server 500 and controls communication between the nodes. As one example, as illustrated in
The group controller 505 generates a group by user identifier under the control of the controller 503. For example, as illustrated in
In addition, the group controller 505 may check a version of the group list of the peripheral node requesting the connection, and update the group list of the peripheral node. For example, the group controller 505 may check the version of the group list of the peripheral node requesting the connection, as indicated in steps 151 to 155 in
The IP checker 507 checks the IP allocated to each node in a network.
The storage 509 stores information necessary for the driving of the control server 500. For example, the storage 509 stores the group list created by the group controller 505.
As described above, the peripheral nodes are managed by grouping using the user identifier information as the category in the IP-based wireless communication system. Therefore, the mobile node can easily connect to and control the correspondent node, even when it does not know the IP of the correspondent node.
While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the scope of the invention is defined not by the detailed description of the invention but by the appended claims, and all differences within the scope will be construed as being included in the present invention.
Patent | Priority | Assignee | Title |
Patent | Priority | Assignee | Title |
7925740, | Jul 28 2005 | Alcatel Lucent | System and method for service quality management for wireless devices |
7995489, | Jun 14 2004 | The Boeing Company | Topology and quality of service management apparatus and methods for communication networks |
8311042, | Jun 15 2007 | Alcatel-Lucent USA Inc | System and method for automatic detection and reporting of the mapping between device identity and network address in wireless networks |
20030161332, | |||
20060245393, | |||
20070071012, | |||
20080151876, | |||
20090128852, | |||
20110119076, | |||
20110145341, | |||
20110231508, | |||
20110252240, | |||
WO2005013569, | |||
WO2008154067, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jun 30 2011 | Samsung Electronics Co., Ltd. | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Date | Maintenance Schedule |
Mar 18 2017 | 4 years fee payment window open |
Sep 18 2017 | 6 months grace period start (w surcharge) |
Mar 18 2018 | patent expiry (for year 4) |
Mar 18 2020 | 2 years to revive unintentionally abandoned end. (for year 4) |
Mar 18 2021 | 8 years fee payment window open |
Sep 18 2021 | 6 months grace period start (w surcharge) |
Mar 18 2022 | patent expiry (for year 8) |
Mar 18 2024 | 2 years to revive unintentionally abandoned end. (for year 8) |
Mar 18 2025 | 12 years fee payment window open |
Sep 18 2025 | 6 months grace period start (w surcharge) |
Mar 18 2026 | patent expiry (for year 12) |
Mar 18 2028 | 2 years to revive unintentionally abandoned end. (for year 12) |