WO2006019226A1 - Procede et dispositif d'interfaçage d'evenements entre des applications et une bibliotheque de maitre dans un reseau domestique - Google Patents

Procede et dispositif d'interfaçage d'evenements entre des applications et une bibliotheque de maitre dans un reseau domestique Download PDF

Info

Publication number
WO2006019226A1
WO2006019226A1 PCT/KR2005/002163 KR2005002163W WO2006019226A1 WO 2006019226 A1 WO2006019226 A1 WO 2006019226A1 KR 2005002163 W KR2005002163 W KR 2005002163W WO 2006019226 A1 WO2006019226 A1 WO 2006019226A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
library
network
function
callback function
Prior art date
Application number
PCT/KR2005/002163
Other languages
English (en)
Inventor
Hu Soon Choi
Jin Ho Son
Jin Young Kim
Jin Sung Park
Tong Hyon Kim
Sun Mi Han
Original Assignee
Lg Electronics Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020040052662A external-priority patent/KR100556759B1/ko
Priority claimed from KR1020040110718A external-priority patent/KR20060071744A/ko
Application filed by Lg Electronics Inc. filed Critical Lg Electronics Inc.
Publication of WO2006019226A1 publication Critical patent/WO2006019226A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
    • H04L12/282—Controlling appliance services of a home automation network by calling their functionalities based on user interaction within the home
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
    • H04L12/2821—Avoiding conflicts related to the use of home appliances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2823—Reporting information sensed by appliance or service execution status of appliance services in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L2012/284—Home automation networks characterised by the type of medium used
    • H04L2012/2843—Mains power line

Definitions

  • the present invention relates to a method and apparatus for interfacing between programs such as control applications executing on a home network server and a library for accessing remote devices .
  • the electronic appliances existing on a home network may be manufactured by different manufacturers. If manufacturers are different, libraries that come with electronic products for supporting access to home networks can also be different.- Different libraries require different interfacing with application programs such as control programs.
  • the present invention provides a method for obtaining the list of home network devices.
  • the present invention provides a method for obtaining detailed information about a home network device.
  • the present invention provides a method for modifying the list of home network devices (e.g., deletion or addition of a device) .
  • the present invention provides a driving procedure between an application and library of a home network master (server) .
  • the present invention provides a method and apparatus for notifying changes in a home network device.
  • the present invention provides a method for monitoring the status of home network devices individually.
  • the present invention provides a method for controlling home network devices individually.
  • the present invention provides a method for command synchronization between an application and library of a home network server.
  • the present invention provides a method for setting the home code, which is a unique identifier of a network, when a home network is set up.
  • the present invention provides a method for setting or modifying the address of a home network device.
  • the present invention provides a method for setting operation options of a home network device (e.g., alive status reporting period, time, event reporting activation, etc) .
  • a home network device e.g., alive status reporting period, time, event reporting activation, etc.
  • FIG. 1 illustrates a brief diagram of a home network in which the present invention may be advantageously embodied
  • FIG. 2 illustrates a flow diagram showing the steps executed during startup of the devices shown in FIG. 1;
  • FIG. 3a illustrates a flow diagram showing the procedure for the library in FIG. 1 to handle events individually;
  • FIG. 3b illustrates a flow diagram showing the procedure for the library in FIG. 1 to handle events in an integrated manner;
  • FIG. 4 illustrates the structure for commands exchanged between the application and library for monitoring/modifying/controlling home network devices . individually;
  • FIGS. 5a through 5c illustrates flow diagrams for the library to set a home code in each of the home network devices
  • FIG. 6 illustrates a flow diagram for assigning address to a device on the home network.
  • FIG. 1 is a brief diagram showing a home network comprising a server and controlled devices in accordance with the present invention.
  • the server in accordance with the present invention comprises a user application 100 (e.g., a home network management program) , a library 110 including functions and execution routines required for accessing a home network, and a physical interface 120 for accessing a physical network 200 (e.g., power lines or LAN cables) .
  • the library is also called LnCP (living network control protocol) library.
  • the home network shown in FIG. 1 includes remote devices 301, and 302 controlled by the server. The state of the devices is monitored, modified, and/or controlled by the execution routines of the library 110. Commands for such operations are called by the user application 100 (referred to as control application hereinafter) via the API defined by the library 110, which will be described in detail.
  • the control application 100 calls the following function of the library 110 get_active_device__list (&active_device_list) .
  • the library 110 then passes the information on the active devices on the home network via the input argument (i.e., active_device_list) .
  • the information includes the total number of active devices and the list of devices.
  • Information on each device is defined as follows: typedef struct device ⁇ device_descriptor_t dd; device_type_t device_type; device_mode_t device_mode; ⁇ device_t.
  • the information on each device includes a protocol index, device descriptor information, and device type and mode.
  • the type specifies the type of the device (e.g., refrigerator or washing machine) .
  • the mode indicates whether the device is a master or a slave.
  • the library 110 allocates its internal memory for each active device.
  • the control application 100 removes the list of active devices to release the memory allocated for the active devices by calling the following function release_active_device_list (&active_device_list) .
  • release_active_device_list &active_device_list
  • the following description elaborates the way in which the server obtains more detailed information on an active device existing on the home network.
  • the control application 100 can obtain more detailed information on a device by calling the following function get_device_info_by_dd(device_descriptor_t dd, device_info_t *ret_entry) , wherein ' dd' is a device descriptor that uniquely identifies the device on the home network.
  • ret_enty is a pointer to a data structure defined as typedef struct device__info ⁇ device_descriptor_t dd; unsigned short address; device_type_t device_type; char model [MAX_MODEL_NAME_LEN] ; unsigned char location;
  • ⁇ device_info_t wherein ' address' is a value obtained by a combination of the type and serial number of the device, ' model' is a text describing the model name, and ' location' is information indicative of the physical location of the device (e.g., living room or bed room) .
  • control application 100 After obtaining information on a specific device in the aforementioned way, the control application 100 calls appropriate functions of the library 110 to execute user- required commands. If it is determined that the attained information is not necessary, the control application 100 calls a function of the library 110 to release the memory that the library 110 allocated for the device, thereby allowing the memory to be used for other purposes.
  • the control application 100 registers the event that occurs when a device is removed (i.e., device removal event) and the callback function to be executed when the event occurs in the library 110 by calling the following function: add_sys_event_func_entry (EVT_SYSTEM_PLUG_OUT, plugout_event_handler) .
  • the function add_sys_event_func_entry() of the library 110 registers the event and callback function therefor in the system event handler table.
  • the library 110 executes the callback function associated with the event after finding the callback function by searching the system event handler table. For example, if the event is EVT_STSTEM_PLUG_OUT, the callback function associated with the event ,i.e., plugout_event_handler () , is called automatically.
  • the library 110 passes the device descriptor or protocol index value to the callback function via the input argument dd, i.e., the library 110 calls the following function plugout_event_handler (sys_event_value_t dd) , which removes the specified device from the list of active devices.
  • control application 100 If the control application 100 does not want to receive the device removal event after the removal event is registered in the library 110, the control application 100 removes the ⁇ registered event and callback function by calling the following function del_sys_event_func_entry (EVT_SYSTEM_PLUG_OUT, plugout_event_handler) , wherein the event and the callback function to be removed are given as the input arguments to the function.
  • del_sys_event_func_entry EKT_SYSTEM_PLUG_OUT, plugout_event_handler
  • the function del_sys_event_func_entry () of the library 110 then removes the event and callback function therefor passed via the arguments to the function from the system event handler table.
  • FIG. 2 is a flow diagram showing the required procedure.
  • the control application 100 When executed, the control application 100 first loads the user interface (S21) and makes a request for initialization of the library 110 (S22) . Information on the devices to be controlled is passed to the library 110 when the request is made. The control application 100 then finds active devices and makes a request for initialization of the devices as mentioned earlier (S23) . Subsequently, the control application 100 registers system events (e.g., plug-in event or plug-out event) and event handlers (callback functions) to handle the events (S24) .
  • System events refer to events that occur when a device joins to or is released from the home network.
  • the LnCP library 110 calls the callback function associated with the system event which is registered in the event handler table to deal with the event (S25) .
  • control application 100 may remove a registered event and its callback function from the event handler table by calling function del_sys_event_func_entry() with proper input arguments .
  • system events events that occur when a device is added to or removed from the network by another master and events that occur in the case of no response from devices.
  • the way to deal with these system events are all the same.
  • Each of the system event codes and associated callback functions are registered by calling the function add_s ⁇ s_event_func_entry () of the library 110. If an event that has been registered occurs, then the associated callback function is called automatically by the library 110 to handle the event, thereby allowing the control application 100 to processing the event appropriately.
  • the system events can be received from a device or another master (e.g., when a device is newly registered in the network by another master) .
  • the system event is received in the form of a packet by a packet parsing module of the library 110. If the packet parsed by the packet parsing module has no error, the library 110 determines if the information conveyed by the packet is a system event by comparing the event code to the event codes registered in the system event handler table. If a matched event code is found, the callback function associated with the event code is called, where information contained in the packet such as device identification information is passed to the callback function via arguments to the callback function.
  • the packet is ignored. If the received packet has an error, the packet is ignored. If the received packet does not contain a system event, it is determined if the event is an individual status event by searching another event table and the event is processed accordingly.
  • Devices supporting access to a home network are equipped with the function of generating events automatically in case of a change in the device status (e.g., changes in power status, operation status, operating temperature, operating mode, selected course, etc) .
  • the device passes an event code for indicating the type of the event and an event value, which is the value of the status at which the event is generated.
  • the control application 100 first registers the event callback function to deal with the event.
  • the control application 100 registers the callback function defined as typedef void (*user_event_func__t) (event_valuel_t event_value) along with device descriptor ' dd' and event code ' ec' in the library 110 by calling the function int add_event_handler (device_descriptor_t dd, event_code_t ec, user_event_func_t uefunc) , where ' ec' is the event type that the library 110 will report and ' uefunc' is the pointer to the callback function.
  • the library 110 searches its hash table for the device descriptor and event code associated with the event and calls the associated callback function using the registered function pointer uefunc (301 in FIG. 3a) .
  • the library 110 passes ' event_value' as the input argument to the function.
  • ⁇ event_value' is the value of the status at which the event is generated.
  • the control application 100 notifies the user of the occurrence of the event or performs predefined operations depending on the value.
  • the control application 100 registers the callback function defined as typedef void (*user_all_event_func_t) (unsigned short device_addr, unsigned char size, unsigned char *event_data) in the library 110 by calling the function int add_all_event_handler (user_all_event_func_t func) .
  • the library 110 When the callback function is registered in the library 110, the library 110 always executes the callback function via function pointer ' func' whenever an event is generated by a ' device on the network (302 in FIG. 3b) .
  • the library 110 provides ' device_addr' and event_data' as the input arguments to the callback function so that the device that generated the event and the event type can be identified.
  • the ' device_addr' is type and serial number for identifying the device on the home network.
  • ' event_data' is a pointer value that points to location of the event code and value.
  • the called routine in the control application 100 handles the event accordingly based on the information passed as input arguments.
  • the way in which the control application 100 controls devices individually by calling routines of the library 110 will now be described.
  • the control application 100 needs the following information in order to call device control functions of the library 110.
  • the control application 100 should know the ID of the device to control (device descriptor) and the code of the command to execute.
  • the command code may be provided internally by the library 110.
  • the control application 100 should provide information required for device control via input arguments (e.g., POWER_ON or POWER_OFF in the case of power control of a washing machine)
  • the library 110 calls its internal function control_device () with storing the arguments, including the command options, in a structure of command_t type defined in FIG. 4.
  • the structure command_t defined in FIG. 4 includes variables of ' cc' , ' args' of command_args_t (401) type, rets' of command_ret_t type (402), and ' option' of command_option_t type.
  • the variables ' cc' which represents the command code, ' args' , and ' option' are determined depending on the user input.
  • the var_arg field in the command_args_t structure (401) and var_ret field in the command__ret_t structure (402) are pointers to the command and response, respectively.
  • the internal function control_device After registering a function for handling the response with the address of the device to control and command code as the key, the internal function control_device () generates a protocol packet to control the device and passes the protocol packet to the device 301 or 302 via the physical interface 200
  • the function control_device calls the function registered to handle the response. If necessary information is contained in the response from the device, the function control_device () stores the information in a structure of command_t type and returns the structure. The device control function interprets the information contained in the command_t structure and returns the information and control result to the control application 100 via output parameters of the function, which completes the individual device control operation requested by the control application 100.
  • control application 100 monitors the status of individual devices by calling routines of the library 110.
  • the method for status monitoring of individual devices is the same as the above method for control of individual devices except for the following parts .
  • command mode and timeout are given as a command option defined as follows : typedef struct command_option ⁇ unsigned char async; unsigned long wait_time; // unit: sec ⁇ command_option_t;
  • variable ' async' has a value of either SYNC_COMMAND or ASYNC_COMMAND (0 or 1) .
  • SYNC_COMMAND means that the control application 100 will wait for the response to the command that it issued.
  • ASYNC_COMMAND means that the control application 100 will not wait for the response to the command.
  • variable ' async' is set to SYNC_COMMAND
  • the control application 100 will wait for the response during the time interval stored in the variable ' wait_time' . If a response is received before the timeout occurs, the command is completed normally. Otherwise, the control application 100 executes commands to deal with TIME_OUT event. If the variable async' is set to ASYNC_COMMAND, the variable ' wait_time' is simply ignored.
  • a command_option_t type pointer variable may be declared as a global variable as follows: static command_option_t *func_option. Because the control application 100 can call more than one function of the library 110 simultaneously, it is also possible to add a variable for storing the command code to the command_option structure as follows : typedef struct command_option ⁇ unsigned char ccc; // command code unsigned char async; unsigned long wait_time; // unit: seconds ⁇ command_option_t; Though a variable of the command_option__t type defined above is declared as global, the control application 100 and library 110 can execute appropriately according to synchronous or asynchronous mode because the code of the command to be executed is contained in the structure. The method to initialize the home network and to modify settings will now be described in detail. The initialization method will be described first.
  • a home code is used.
  • the home code is a unique code that identifies the home network from other networks and a home network device can only communicate with other devices having the same home code.
  • the control application 100 can set the home code by calling the following function int set_home_code () ; of the library 110.
  • the library 110 executes the steps shown in FIG. 5a.
  • the library 110 broadcasts a message that accompanies a response from devices (e.g., a message requesting the device name) through the physical network 200 (S51) .
  • the message uses the home code set in the physical interface 120. If there is a response to the message (S52) and the message is aimed to add a device to the network, the library 110 broadcasts another message for setting the home code (S56) .
  • the library 110 issues a command for generating a home code to the physical interface 120 (e.g., powerline modem) (S53) and then broadcasts another message that accompanies a response (e.g., a name requesting message) through the network again (S54) . If there is a response to the message (S55) , it indicates that the home code has been already used and therefore the library 110 performs the steps to generate a home code again (S53 and S54) . If there is no response, the library 110 broadcasts a message for setting the created home code through the home network (S56) .
  • the physical interface 120 e.g., powerline modem
  • the electronic appliances can communicate with each other with no disturbance from external home networks due the home code uniquely assigned to the home network.
  • FIG. 5b is a flow diagram for determining if the home network is set up for the first time or a new device gets connected to the existing home network in the above procedure.
  • the method for setting the home code differs depending on whether the home network is set up for the first time or a new device gets added to an existing home network. If there is a response to the message for requesting the device name (S503 and S504), it is determined that a new device gets added to an existing home network (S506) . If there is no response until the message is broadcast three times, for example, it is determined that the home network is set up for the first time (S505) .
  • FIG. 5c is a flow diagram showing the steps S53 through S55 shown in FIG. 5a in more detail.
  • the present method commands the physical interface 120 (e.g., home network modem) to create a new home code (S511) and broadcasts the created home code so that modems for other home networks can set the home code after making sure that the created home code does not conflict with home codes of other home networks.
  • the decision for determining whether there is a conflict with the created home code can be made by broadcasting a name requesting packet (S513) .
  • the handler for handling the response to the name requesting packet is registered in a table before the packet is broadcast (S512) . If a response is received, the response is handled by the handler (S515) .
  • This function clears the home code set in the home network modem by transmitting a command packet for clearing the home code to the home network modem connected to the master.
  • the above procedure for creating/clearing a home code is repeated until a unique home code is obtained.
  • the home code of the home network is broadcast so that the home code can be set in the home network modem of the new device (S56) .
  • Registering a user-defined home code can be done by calling the following function int push_home_code (unsigned long home_code) of the library 110. If the function is called, the library 110 broadcasts the home__code, which is the input argument to the function, so that the code can be set in the modem of each of the devices 301 and 302.
  • the library 110 allows the control application 100 to assign addresses to the network devices easily by providing routines required for assigning addresses.
  • a device which wants to join the home network broadcasts a plug-in notification message in order to obtain a unique address, (S61) .
  • the library 110 of the master that receives the plug-in notification message assigns an address to the device after processing the message.
  • the library 110 registers a handler for the plug-in notification message in its response function hash table before processing the plug-in notification packet.
  • the handler for the plug-in notification packet finds out the type of the device that transmits the packet and searches its database for an unused address based on the device type (S62) . If an unused address is found, the handler passes the address via an argument to the address change command (S63) .
  • the address change command is given as follows: int change_address (old_addr, new_addr) ;
  • the arguments to function change_address () are the current address and a new address that will be used instead of the current address. If the device is a new device connected to the home network for the first time, ' old_addr' is a default address (e.g., usually 0) .
  • the function change_address () returns a value indicative of whether the address change operation is successful or not.
  • the device that receives the address change command sets the passed address as its address and transmits a response. If the function change_address () receives the response, the function stores the address in its database (S64) because it means that the address change operation is successful. In addition, the function sends a DB update command to inform other network managers that a new device is registered (S65) .
  • the library 110 After changing the device address, the library 110 makes requests for additional information to the device that sets the new address (S66 and S67) and stores the received information in the database. For example, the library 110 finds whether the device is a master or a slave by sending device search command (S66) and obtains the model name thereof using model request command (S67) .
  • S66 device search command
  • S67 model request command
  • the library 110 of a master device of the home network should check which devices are connected to the network and which devices are active. To this end, the library 110 requests each of the devices to periodically send a message indicating that the device is active. The message is called alive" message.
  • the control application 100 of the master initializes the network, the control application 100 notifies the period of " alive" message of the devices. The library 110 therefore knows which devices are active because . it receives periodical " alive" messages from active devices.
  • the function of the library 110 which the control application 100 calls to set the period, inputted from a user or operator, of the " alive" message is as follows: int set_alive_message_interval (time) ;
  • the library 110 passes the value of the variable ' time' , which is the period of the " alive” message, to each of the devices on the home network so that the devices send the " alive” message periodically with the period afterwards.
  • control application 100 calls the following function int set_clock (hour,min, sec) ; of the library 110.
  • the library 110 When the function is executed, the library 110 generates a packet containing the values of the variables ' hour' , minute' , and ' second' and transmits the packet to the devices. Also, the library 110 informs the control application 100 of the result via the return value based on responses from the devices . The home network devices notify changes in the status to other devices and master devices through events .
  • the control application 100 can enable or disable the status notification function through the library 110. To enable the status notification function, the control application 100 calls function int event_enable (enable) ; of the library 110.
  • the library 110 sends a command for enabling or disabling the status notification function to a corresponding device based on the input argument. Receiving a response to the command, the library 110 returns a value corresponding to the response to the control application 100.
  • control applications and libraries are standardized, users can enjoy more freedom in purchasing electronic appliances for constructing a home network because compatibility is guaranteed for electronic appliances without regard to manufacturers thereof.
  • the standardization also helps manufacturers reduce the cost for device development and warranty service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé et un dispositif permettant l'interfaçage entre diverses applications exécutées dans un réseau domestique, et une bibliothèque, de manière à assurer leur compatibilité. L'invention porte notamment sur un procédé de traitement d'événements, dans lequel une application appelle la routine de fonction d'une bibliothèque, laquelle opère l'enregistrement d'un événement système tout en fournissant une fonction de rappel pour le traitement d'un événement système, p. ex. un événement de suppression ou d'ajout d'unité dans la bibliothèque, par l'intermédiaire d'augments d'entrée de la routine de fonction. Si par la suite un événement système, tel que la suppression ou l'ajout d'une unité, se produit dans un réseau, la bibliothèque appelle la fonction de rappel enregistrée dans l'application en utilisant des arguments d'entrée contenant des informations d'identification d'une unité ajouté au réseau ou supprimée de ce dernier.
PCT/KR2005/002163 2004-07-07 2005-07-06 Procede et dispositif d'interfaçage d'evenements entre des applications et une bibliotheque de maitre dans un reseau domestique WO2006019226A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR1020040052662A KR100556759B1 (ko) 2004-07-07 2004-07-07 ＬｎＣＰ 기반의 시스템 이벤트 처리 방법 및 장치
KR10-2004-0052662 2004-07-07
KR10-2004-0110718 2004-12-22
KR1020040110718A KR20060071744A (ko) 2004-12-22 2004-12-22 홈 네트워크 마스터의 어플리케이션과 라이브러리의인터페이싱 방법

Publications (1)

Publication Number Publication Date
WO2006019226A1 true WO2006019226A1 (fr) 2006-02-23

Family

ID=35907599

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2005/002163 WO2006019226A1 (fr) 2004-07-07 2005-07-06 Procede et dispositif d'interfaçage d'evenements entre des applications et une bibliotheque de maitre dans un reseau domestique

Country Status (1)

Country Link
WO (1) WO2006019226A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010148727A1 (fr) * 2009-12-28 2010-12-29 中兴通讯股份有限公司 Procédé et terminal pour rappel d'instructions d'atome
CN112667488A (zh) * 2020-12-29 2021-04-16 深圳市慧为智能科技股份有限公司 按键处理方法、装置、设备及计算机可读存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1345381A2 (fr) * 2002-03-12 2003-09-17 Samsung Electronics Co., Ltd. Appareil et procédé pour fournir par internet des informations concernant les appareils d'un réseau de domotique
EP1345360A2 (fr) * 2002-03-15 2003-09-17 Samsung Electronics Co., Ltd. Procédé et appareil pour commander des dispositifs connectés à un réseau domestique

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1345381A2 (fr) * 2002-03-12 2003-09-17 Samsung Electronics Co., Ltd. Appareil et procédé pour fournir par internet des informations concernant les appareils d'un réseau de domotique
EP1345360A2 (fr) * 2002-03-15 2003-09-17 Samsung Electronics Co., Ltd. Procédé et appareil pour commander des dispositifs connectés à un réseau domestique

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010148727A1 (fr) * 2009-12-28 2010-12-29 中兴通讯股份有限公司 Procédé et terminal pour rappel d'instructions d'atome
CN112667488A (zh) * 2020-12-29 2021-04-16 深圳市慧为智能科技股份有限公司 按键处理方法、装置、设备及计算机可读存储介质
CN112667488B (zh) * 2020-12-29 2022-07-26 深圳市慧为智能科技股份有限公司 按键处理方法、装置、设备及计算机可读存储介质

Similar Documents

Publication Publication Date Title
US20060230128A1 (en) Method and apparatus interfacing for controlling a device between an application and a library of a master on home network
CN108702389B (zh) 用于遥控iot(物联网)设备的架构
US8019855B2 (en) Method and apparatus interfacing between an application and a library of a master for network managing
KR100559023B1 (ko) 홈 네트워크 시스템 및 이를 위한 구성장치
US20070242815A1 (en) Method for exchanging information between devices in case of a change in network configuration and home network system therefore
US20090024727A1 (en) Network system management method
US20070133569A1 (en) Home network system and its configuration system
US20090160626A1 (en) Method for Setting Home Code in Network System and Device for Network
JP2016528621A (ja) 関連プラグインの管理方法、装置およびシステム
JP2005517311A (ja) ホームネットワーキング通信装置及び方法
US8005915B2 (en) Method for providing download and upload service in network control system
CN104750544A (zh) 应用于分布式系统中的进程管理系统及进程管理方法
JP5499917B2 (ja) 電源管理装置、電力供給制御システム、電力供給制御方法、および電力供給制御プログラム
WO2006004378A1 (fr) Procede et appareil d'interfaçage d'evenements entre des applications et une bibliotheque de maitre sur un reseau familial
US7568024B2 (en) Method for deciding network manager in home network
WO2006019226A1 (fr) Procede et dispositif d'interfaçage d'evenements entre des applications et une bibliotheque de maitre dans un reseau domestique
US8001415B2 (en) Program control method for network devices and network system
CN102025576A (zh) 一种家庭自动化系统及其控制方法
KR101486771B1 (ko) 제어 포인트의 연결 상태에 기초하여 ＵＰｎＰ 디바이스의자원을 관리하는 방법 및 장치
US20060161926A1 (en) Method and apparatus interfacing for querying a device between an application and a library of a master on home network
KR20130015980A (ko) Ｃｐｎｓ시스템에서 개인망과 ｃｐｎｓ서버의 접속 관리 방법
KR20060071753A (ko) 홈 네트워크 마스터의 어플리케이션과 라이브러리의인터페이싱 방법
KR20060071749A (ko) 홈 네트워크 마스터의 어플리케이션과 라이브러리의인터페이싱 방법
KR20060071746A (ko) 홈 네트워크 마스터의 어플리케이션과 라이브러리의인터페이싱 방법
KR20060071751A (ko) 홈 네트워크 마스터의 어플리케이션과 라이브러리의인터페이싱 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase