Abstract:
A system and a method for beacon scheduling for preventing beacon collision are provided to select a beacon transmission time efficiently when the routers of a sensor network are activated and allow a sink node to manage the entire beacon collision of the routers, thereby constructing the sensor network environment of a beacon mode with stability, low energy consumption, and high performance. A method for beacon scheduling for preventing beacon collision comprises the following steps of: allowing all router nodes to transfer messages including received slot numbers and beacon scan completion times to a sink node(S420); allowing the sink node to check whether there is the same slot number in the messages transferred from the router nodes(S440); updating the scan time of a corresponding slot number entry of a table when there is no same slot number in the messages(S440); considering that two routers have a change of beacon collision if the two routers use the same slot and a scan time interval is less than or equal to N*beacon interval(N=1,2,3,4,...)(S460); and applying a reset command to a router which transfers a slot allocation message recently out of active routers(S470).
Abstract:
A beacon scheduling method in a wireless sensor network is provided to support a more stable communication environment by avoiding beacon collision between neighbor routers, and enhance utilization of sensing data . An event generation node receives beacons from a PAN coordinator and neighbor nodes such as neighbor routers and recognizes super-frame slots used by the neighbor routers and parent routers of the neighbor routers(301). The event generation node determines its parent router by using beacon information obtained from received beacons(302). The event generation node obtains its routing depth information based on address information of its parent router and recognizes the number of available beacon slots in a super-frame duration(303). The event generation node checks whether beacons, starting the right beacon slot, are being used by other routers(304). If a beacon slot is not used, the event generation node determines the corresponding beacon slot as an optimum beacon slot(305). The event generation node transmits sensing data to the parent router in the super-frame duration of its parent router(306).
Abstract:
A method for constituting an independent cluster by each sensor node on a sensor network is provided to enable each node to constitute new nodes as a cluster node on the basis of information about a cluster after setting the initial cluster for providing a specific service, thereby automatically and efficiently constituting the cluster with necessary nodes according to a state and the condition of each node. A method for constituting an independent cluster by each sensor node on a sensor network comprises the following steps of: forming a cluster(501); detecting a new sensor node in a range of the cluster(502); requesting an authority key value which the sensor node has previously obtained(503); transferring a corresponding cluster membership if the authority key value is satisfied(504); transmitting a cluster program with the cluster membership(505); and upgrading the program of the sensor node(506).
Abstract:
본 발명은 차량의 센서 정보의 처리기술에 관한 것으로, 특히 텔레매틱스 단말기와 이씨유의 통신연결을 위한 통신방법 및 차량의 센서 정보 처리방법 및 장치에 관한 것으로, 센서 정보는 차량 이씨유에서 처리되어 통신게이트웨이를 통해 텔레매틱스 단말기에 전달되고 전달된 센서정보는 텔레매틱스 단말기의 소프트웨어 모듈에서 관리된다. 본 발명은 차량 센서정보의 처리를 위한 통신방법과 텔레매틱스 단말기내 센서정보를 전달받아 처리하는 소프트웨어 모듈로 구성된다. 센서정보 처리를 위한 통신방법은 각종 센서들로부터 정보를 받아서 처리하는 차량 이씨유와 텔래매틱스 단말기의 사이에서 통신게이트웨이가 각각 캔통신과 시리얼 통신에 의한 통신 처리를 수행한다. 텔레매틱스 단말기는 캔통신을 위한 별도의 통신모듈 없이 캔통신과 시리얼통신을 연결하는 통신게이트웨이를 통해 이씨유로부터 센서정보를 전달받는다. 텔레매틱스 단말기의 센서정보를 처리하는 소프트웨어 모듈은 전달받은 센서정보에 대한 처리와 관리를 담당한다. 센서정보의 종류로는 장애정보와 성능정보가 존재한다. 본 발명은 통신게이트웨이를 이용하여 차량의 센서정보를 처리하는 이씨유와 텔레매틱스 단말기간 연결이 별도의 통신모듈 없이 연결되며, 차량 센서정보의 분류와 관리 테이블을 통해 차량의 이상유무에 대한 상태변화를 체계적으로 관리할 수 있다.
Abstract:
본 발명은 텔레매틱스 서버와 텔레매틱스 단말기 간의 데이터를 동기화하기 위하여, 텔레매틱스 서버 또는 텔레매틱스 단말기에 구현되는 동기화 장치로서, 데이터 및 데이터의 생성 시간 정보를 포함하는 동기화 요청 메세지를 수신하는 수신부, 데이터 및 데이터의 생성 시간 정보를 생성시간에 따라 순차적으로 저장하는 데이터 베이스부,데이터베이스부에 저장된 가장 최근의 데이터 생성 시간 정보와 동기화 메세지 내의 데이터 생성 시간 정보가 일치하는지 판단하는 데이터 갱신 판단부 및 데이터 생성 시간 정보가 일치하지 않는 경우, 동기화 요청 메세지를 기초로 데이터베이스부를 갱신하는 갱신부를 포함한다. 이로써 갱신된 정보에 대해서만 동기화가 이루어지므로 동기화에 따른 통신 부담이 감소 된다. 동기화, 텔레매틱스 센터, 텔레매틱스 단말기
Abstract:
PURPOSE: An apparatus and a method for interfacing between TMN(Telecommunication Management Network) management agent and ATM(Asynchronous Transfer Mode) exchange are provided to minimize physical or logical modification of a network operator by using an interface applicable to a TMN management agent structure existing in a computing environment outside the exchange. CONSTITUTION: A gateway module(240) connects to an exchange/operator interface(310) in exchanges(300) to transceive messages of the exchange(300) and a TMN system. A server(230a) and client(210a) process an instruction request from a TMN management agent(140). A server(210a) and client(230c) process a result of processing the instruction. An event processing server(210c) and event processing client(230c) process an exchange fault generating or operation status reporting. A CORBA(Common Object Request Broker Architecture)(220) remotely communicates with the servers and clients. An auto message interpreter(260) extracts parameters needed for constructing a CORBA IDL(Interface Definition Language).
Abstract:
PURPOSE: An operator interfacing method in HANbit ACE64 exchange to provide a compatibility with a heterogeneous operating system is provided to easily connect to various types of operating system or network management system by allowing the exchange to provide an interface that has high portability and utility. CONSTITUTION: A network management system makes a CORBA(Common Object Request Broker Architecture) client(S1), and then activates a corresponding command receiving server(S2). At this time, a CORBA server performs the activated and called CORBA operation(S3). The performed result is transferred to an input command generating part(S4), and an IMD(Input Command) is created(S5). The created IMD is transferred to a corresponding block in the exchange and performed(S6-S8). The performed result is transferred from the function block to OMP(Operation and Maintenance Processor)(S9) and transmitted to an output message interpreting part(S10). The output message interpreting part interprets an OMD(Output Command) and extracts parameters to be used in assembling CORBA IDL by a message transmitting CORBA client(S11). The extracted parameters are transferred to the message transmitting CORBA client(S12). The message transmitting CORBA client assembles the corresponding IDL(S13) and calls a corresponding CORBA server in the operating system(S14).
Abstract:
The method for generating processor load data suitable to relations registered to a data administration system and for generating data to be reference to distributed data base system. The method comprises the steps of: (A) verifying input station data necessary to operate an exchange; (B) sending error message when errors are detected from the input station data; (C) generating relation data by processor units and generating object files; (D) generating tuple data and constructing files by processor units; (E) generating relation data; (F) generating relation search data; and (F) generating process or load data by linking results of the step (A)-(E).
Abstract:
The method for using user's own program directly without recompiling regardless DB version comprises steps: (a) generating list files corresponding to the reference and request DB versions when the synchronisation request for the relation number of the new generated DB version by the operator is received; (b) comparing each relation numbers and names of the requested and the reference DB versions; (c) if the compared numbers are different, the reference relation number is allocated to the requested relation number, but repeating the (b) step as much as the relation number of the requested DB version; (d) after comparing process is ended, the relation number of the requested DB version is synchronized to the relation number of the reference DB version.