WO2004049658A1 - Procede de construction d'une adresse commune et d'une table d'adresse pour le transfert de donnees entre differents protocoles de reseau, et architecture y relative - Google Patents

Procede de construction d'une adresse commune et d'une table d'adresse pour le transfert de donnees entre differents protocoles de reseau, et architecture y relative Download PDF

Info

Publication number
WO2004049658A1
WO2004049658A1 PCT/KR2003/002543 KR0302543W WO2004049658A1 WO 2004049658 A1 WO2004049658 A1 WO 2004049658A1 KR 0302543 W KR0302543 W KR 0302543W WO 2004049658 A1 WO2004049658 A1 WO 2004049658A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
network
packet
common
home
Prior art date
Application number
PCT/KR2003/002543
Other languages
English (en)
Inventor
Kwang-Soon Choi
Kwangmo Jung
Original Assignee
Korea Electronics Technology Institute
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
Application filed by Korea Electronics Technology Institute filed Critical Korea Electronics Technology Institute
Priority to AU2003282428A priority Critical patent/AU2003282428A1/en
Publication of WO2004049658A1 publication Critical patent/WO2004049658A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • 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
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/604—Address structures or formats

Definitions

  • the present invention relates to an architecture of a common address and an address table for transferring data between different network protocols and a constructing method thereof and, more particularly, a common address usable in a protocol for internal and external networks in home networking or a common protocol for data communications between various protocols and an address table for address conversion between a common address and a physical address.
  • the information home appliances mean digital home appliances having a network communication function additionally so that a user can access to the Internet through the home appliances in a home.
  • a network for communications between home appliances or between home appliances and information terminals in a home is being constructed.
  • Such a network is called a home network or a home area network.
  • various network protocols based on various protocols such as IP, Bluetooth, IEEE 1394, and LonTalk have to be employed.
  • ISPs internet service providers
  • ISPs internet service providers
  • each computer globally connected through networks exchanges data with other computers according to mutual common rules and, therefore, each computer connected to the Internet needs a specific address by which each computer can be distinguished from other computers on the Internet.
  • a computer is given a different IP address by the ISP every time it accesses to the Internet, and, therefore, external users cannot know the changed IP address. Even so, it is impossible for each of all information appliances in a home to have a unique IP address because the number of IP addresses is deficient under the present IP address format.
  • the specific address on the Internet is expressed by means of numeric figures or English letters.
  • the address expressed by means of numeric figures, what is called an IP address is an address for computers by which a computer can easily look for a specific computer among communication devices connected to a communication network.
  • the address expressed by means of English letters, what is called a domain name is an address for users by which a user can easily understand an address of a computer on the Internet.
  • each communication device connected to the Internet has to have a unique address that is not redundant globally with any other device in both the IP address and the domain name. First, if a user inputs a domain name through a web browser, the web browser queries an IP address corresponding to the domain name to a domain name server through the Internet.
  • the domain name server searches its own database responding to the request of the web browser and, then, provides the IP address corresponding to the domain name. Subsequently, the web browser exchanges data with a web server having the domain name using the IP address received.
  • DNS domain name system
  • a domain name associated with an IP address has to be registered on a DNS server that is authorized on the Internet.
  • an IP address corresponding to a domain name is required in a domain name service. If an IP address of a device changes each time, it is impossible to provide the domain name service and to access to a home network from outside accordingly.
  • a plurality of network terminals cannot share an authorized IP address on the Internet.
  • a user has to set up information about a network structure and service servers by himself/herself, but it is not easy for general users with little knowledge about network to understand protocols and constitute a server.
  • Devices connected to home networks have a characteristic address hierarchy on each network.
  • the characteristic address hierarchy on each network is not compatible with each other and, therefore, a device in a network can transmit a signal to a device in another network only through a home gateway system.
  • the home gateway system converts a signal in a network into a form acceptable in a destination network.
  • the home gateway system converts a signal in a network into a known existing form to transmit the signal and the signal transmitted is converted into a form acceptable in the destination network.
  • U.S. Patent No. 5,852,660 discloses a network protocol conversion module within a telecommunications system.
  • the above-mentioned U.S. patent provides a method and apparatus for enabling telecommunications signals containing application layer data generated by a first SS7 (Signaling System No. 7) telecommunications network to be transported across a second SS7 telecommunications network, wherein the first SS7 telecommunications network and the second SS7 telecommunications network are incompatible.
  • SS7 Signal-SS7
  • SS7 Signal-SS7 telecommunications network
  • such a conventional method has a problem that protocol conversion is performed using a physical device, thereby causing inconvenience due to installation of the physical device. Therefore, a need exists for methods of performing protocol conversion using logical address conversion between protocols .
  • address conversion methods according to protocol conversion methods are classified into three classes. First, there is an address conversion method in 1 to 1 protocol conversion.
  • This method converts an address used at a particular protocol layer into an address required at a corresponding layer of another protocol, based on the seven- layered OSI reference model.
  • a lot of conversion methods are required and, therefore, there are problems that a home gateway accepting various protocols has to manage a very large address table and treat complicated conversion processes.
  • This address conversion method converts n network protocols into a particular network protocol selected from the n network protocols.
  • (n-1) conversion methods are required and, therefore, (n-1) address conversion methods are required.
  • this address conversion method shows reduction in complexity and size of address table compared to the first method, it still requires a lot of address conversion.
  • IP-over-IEEE 1394 IP-over- ATM
  • IP-over-IEEE 1394 IP-over- ATM
  • IEEE 1394 or ATM layer There are structures that an Internet protocol, IP, is laid on an IEEE 1394 or ATM layer. They do not perform particular conversions and are not data exchange methods between network protocols.
  • IP-over-IEEE 1394 an apparatus in an IEEE 1394 network transmits IEEE 1394 data laid on the IP and receives data through the IP. The data received through the IP is passed through the IEEE1394 layer so that the IEEE1394 apparatus can accept the data. Therefore, it cannot be referred to as data exchange between different network protocols.
  • U.S. Patent No. 5,715,250, Watanabe discloses an ATM- LAN (asynchronous transfer mode local area network) connection apparatus capable of connecting terminals of different protocol standards.
  • the U.S. patent provides a small-scale ATM-LAN connection apparatus which enables communications between first and second ATM terminals of different standards, namely, the first ATM terminal of a LAN emulation protocol and the second ATM terminal of an IP over ATM protocol.
  • the above-mentioned address conversion methods increase complexity and size of address table because the number of address conversion methods increases in proportion to the number of network protocols to be converted and the number of layers in the network protocols to be converted.
  • the complexity increases according to the number and structure of packets that are related to address mapping at each protocol layer, e.g., ARP and ping, because the protocol layer architecture and role of each layer in each network protocol are very different from each other based on the seven-layered OSI reference model.
  • the present invention is directed to an architecture of a common address and an address table for transferring data between different network protocols and a constructing method thereof, which substantially obviate one or more problems due to limitations and disadvantages of the related art.
  • An object of the present invention is to provide a method of communication of different networks with each other using application programs only, without address conversion between existing protocol layers, by designing a common address structure usable in a common protocol layer and using a common address of a common protocol layer in or under an application layer.
  • Another object of the present invention is to provide a method of identifying whether devices in different networks are working and a new device is installed in the networks and identifying types of devices and protocols used in the devices only through a common address.
  • Another object of the present invention is to provide an address table which supports rapid mapping between a physical address and a common address (logic address) on each network.
  • the present invention provides a structure of a common address for transferring data between different network protocols, wherein the structure being used for understanding different addresses of different protocols in a common protocol layer which enables different networks to communicate with each other by accepting various protocols of a home network system comprising at least two networks with different source coding methods and transfer speeds, the structure of a common address comprising: a domain address including information about a network; a cluster address including information about devices using the same protocol in the network; a device use address (category address #1) including information about use of a device in the network; a device type address (category address #2) including information about a type of a device in the network; a device ID including information about a specific number assigned to each device in the network; and a reserved field for use in address extension in a future.
  • the present invention provides a method of constructing a common address for transferring data between different network protocols, wherein the method for understanding different addresses of different protocols in a common protocol layer which enables different networks to communicate with each other by accepting various protocols of a home network system comprising at least two networks with different source coding methods and transfer speeds, the method comprising the steps of: forming a domain address including information about a network; forming a cluster address including information about devices using the protocol in the network; forming a device use address including information about use of a device in the network; forming a device type address including information about a type of a device in the network; forming a device ID including information about a specific number assigned to a device in the network; and forming a reserved field for use in address extension in a future.
  • the present invention provides an address table structure for transferring data between different network protocols as a structure to support rapid mapping between a common address (logic address) and a physical address of each network device, the address table structure comprising: an address table memory capable of storing a physical address of a network device in an address space in an external memory of a home station chipset; and an address table controller for finding out a physical address corresponding to a common address (logic address) of a network device from the address table memory.
  • the present invention provides a method of constructing an address table for transferring data between different network protocols, as a method to support rapid mapping between a common address (logic address) and a physical address of a network device, the method comprising the steps of: transferring a common address (logic address) of a network device from an external interface of a home station to an address table controller in a home station chipset; finding out an address space containing a physical address corresponding to the common address from an external memory of the home station chipset; taking out the corresponding physical address from the address space; and transferring the physical address to the address table controller.
  • the present invention provides a method of registering a device adopting a common protocol for transferring data between different network protocols, as a method of registering a device using a common protocol in a common protocol layer which enables different networks to communicate with each other by accepting various protocols of a home network system comprising at least two networks with different source coding methods and transfer speeds, the method comprising: a first step of initializing an address table when power of a device is turned on; a second step of sending a device registration request packet to a home station after the device begins to work and waiting for a device registration response packet from the home station for a predetermined time; a third step of setting a domain address and a device ID, storing an address table, and working normally so as to inform users of devices cormected to a home network, if the device has received the device registration response packet; and a fourth step of waiting until the home station is turned on and returning to the second step after receiving an HRIND packet from the home station, if the device has not received the device registration response packet.
  • the present invention provides a method of registering a home station of devices adopting a common protocol for transferring data between different network protocols, as a method of registering a home station using a common protocol in a common protocol layer which enables different networks to communicate with each other by accepting various protocols of a home network system comprising at least two networks with different source coding methods and transfer speeds, the method of comprising: a first step of initializing an address table when a home station begins to work; a second step of sending an HRREQ packet; a third step of setting the address table if an HRRES packet is received for a first predetermined time; a fourth step of checking whether the HRRES packet has been received or not after the first predetermined time; a fifth step of setting an unused number as a domain address if the HRRES packet has been received; a sixth step of setting an initial value as the domain address if the HRRES packet has not been received; and a seventh step of sending an HRIND packet and working normally.
  • Fig. 1 is a stracture chart illustrating a common address structure of a common protocol according to the present invention
  • Fig. 2 is a view for describing a domain address of a common address according to the present invention.
  • Fig. 3 is a view for describing a cluster address of a common address according to the present invention.
  • Fig. 4 is a table consisting of a device use address and a device type address
  • Fig. 5 is a view for describing an example of transferring data to another network according to the present invention
  • Fig. 6 is a structure chart illustrating an overall address table structure according to the present invention
  • Fig. 7 is a structure chart illustrating a partition structure of an address table
  • Fig. 8 is a structure chart illustrating a partition header structure
  • Fig. 9 is a flow chart illustrating a process of assigning a device ID
  • Fig. 10 is a view for describing an example of a device registration process
  • Figs. 11a and l ib are views for describing an example of a device registration packet
  • Fig. 12a and 12b are views for describing an example of a device registration process
  • Fig. 13 is a view for describing an example of a home station registration process
  • Figs. 14a through 4e are views for describing an example of a home station registration packet
  • Figs. 15a through 15d are views for describing an example of a practical use of HRSREQ, HRSRES, HRREQ, and HRRES packets.
  • Fig. 1 is a structure chart illustrating a common address structure of a common protocol according to the present invention.
  • Major features of a common address according to the present invention are that the common address can be understood only through a common protocol layer and that types of devices used in another network can be clearly identified through each field of the common address using a simple application program because the common protocol layer is positioned in or under an application layer. Another feature of the common address is that it distinguishes the same type of maximum fifteen devices.
  • the common address of the present invention is 3 bytes in size and comprises 6 fields such as a domain address (10), a cluster address (20), a device use address (30), a device type address (40), a device ID (50), and a reserved field (60).
  • Fig. 2 is a view for describing the domain address (10) of the common address according to the present invention.
  • the domain address first field of the common address, occupies 4 bits of [23:20] among the whole common address [23:0].
  • the domain means a network comprising a home station and, therefore, a home station is assigned one domain address.
  • all devices in a domain network have the same domain address. Fifteen home stations can be distinguished from values of the domain address from "0001" to "1111". Therefore, maximum 15 home stations can be installed in a home.
  • Fig. 3 is a view for describing the cluster address (20) of the common address according to the present invention.
  • the cluster address occupies 4 bits of [19:16] among the whole common address [23:0].
  • the cluster means a network that comprises devices using the same protocol and is connected to a home station, i.e., a domain network. Therefore, a domain network can comprise maximum 15 cluster networks (except "0000") that adopt different network protocols.
  • Fig. 4 is a table consisting of the device use address (30, category 1 address) and the device type address (40, category 2 address) in the common address according to the present invention. Referring to Fig.
  • the device use address (30) occupies 4 bits of [15:12] among the whole common address [23:0] and indicates a use of a device in a network.
  • the device type address (40) occupies 4 bits of [11 :8] among the whole common address [23 :0] and indicates a type of a device in a network. For example, a device use and type address of an electric meter reading system capable of telemetering is "0011 0000".
  • the device ID occupies 4 bits of [7:4] among the whole common address [23:0].
  • the device ID is a specific number assigned to each device in a home station supporting a common protocol. Based on combination of the 4 bits, 16 devices having the same use and type can be used in the same domain, but practically 15 devices (except “0000") are used. "0000" is used for address table management.
  • the reserved field occupies 4 bits of [3:0] among the whole common address [23:0]. The reserved field will be used for address extension hereafter.
  • Fig. 5 is a view for describing an example of transferring data to another network according to the present invention.
  • a device A A in a network A transfers data to a device BA in a network B.
  • data generated from an application layer of the device AA is passed through a common protocol layer where a common protocol header is attached to the data and a destination address in the header is set as a common address of the device BA.
  • the common protocol layer cannot understand a physical address of the device B A used in the network B because the common protocol layer uses only a common address.
  • a packet with the common protocol header is passed through lower layers.
  • the packet is set so as to have a physical address of a device AZ, an external interface of a home station chipset, in a data link layer and is passed through a physical layer to arrive at the device AZ.
  • the packet received is passed from lower layers to a common protocol layer in sequence.
  • the device AZ identifies a fact that the packet received has a preamble and transfers the packet to the home station chipset.
  • the home station chipset switches the packet to a corresponding port after identifying only the domain address in the destination address.
  • Fig. 6 is a stracture chart illustrating an overall address table structure according to the present invention.
  • the address table uses an external memory of a home station chipset (70).
  • One address space in the memory can store a physical address of 6 bytes.
  • the size of the address space is based on an MAC address of 6 bytes, a physical address used in Ethernet and Bluetooth.
  • the common address of 24 bits is entered into the address table memory as it is. In other words, if a common address is entered, a physical address corresponding to the common address is outputted through a data bus of the memory.
  • Fig. 7 is a structure chart illustrating a partition structure of the address table according to the present invention. Referring to Fig. 7, the external memory of the address table is naturally partitioned because an address inputted into the address table memory is a common address.
  • a partition means an area of upper 16 bits in the memory comprising the domain address, the cluster address, the device use address, and the device type address among the common address of 24 bits.
  • the partition and the device ID are defined as a partition ID (hereinafter referred to as "PID"). Therefore, one partition has 15 spaces capable of storing 15 physical addresses corresponding to device IDs.
  • device ID "0000” is used as a partition header to manage the 15 spaces. Therefore, one partition is filled with 15 device IDs (except “0000") each of which is 4 bits in size.
  • PID of "0001 0011 0000 0000” means a household refrigerator connected to Ethernet HS#1. As above-mentioned, "0000" is not allotted as a device ID.
  • the "0000" is used as a space to store information about the partition in the address table.
  • "XXXX XXXX XXXXXXXXXX" is PID.
  • Fig. 8 is a stracture chart illustrating a partition header stracture.
  • the partition header comprises a total number of devices part (80) of 2 bytes and an indication flags part (90) of 2 bytes.
  • the total number of devices part indicates the number of devices using the same PID.
  • the indication flags part indicates whether a device ID has been assigned or not.
  • the indication flags part is used to find out promptly a device ID for a new device when the new device is connected to a network.
  • Fig. 9 is a flow chart illustrating a process of assigning a device ID.
  • a home station assigns a device ID to the new device using information in a partition header according to the procedure in Fig. 9.
  • the home station finds PID and a physical address in the address table (S10), reads indication flags in the partition header (S20), and stores "1" in the indication flags pointer (S30).
  • the home station identifies whether a value of the indication flags is "0" or not (S40).
  • the home station gives a device ID to the new device (S50) and updates values of the total number of devices part and indication flags part in the partition header (S60). Then, the home station stores a physical address of the new device in an address space comprising the PID and the device ID and ends the process of assigning a new device ID to a new device (S70).
  • the home station adds "1" to the indication flags pointer (S80) and identifies whether a value of the indication flags pointer is equal to or less than 15 (S90). If the value of indication flags pointer is equal to or less than 15, the process returns to S40. If the value of indication flags pointer is more than 15, the home station indicates "Too many devices! (S 100).
  • a method of registering a device according to a device constitution change in a home network Among fields of a common address, a cluster address, a device use address, and a device type address are fixed according to features of a device.
  • a domain address and a device ID can change according to change of a home network structure, movement of devices, or movement of users. Whenever such changes occur, a new domain address and a device ID are assigned to the device and the network.
  • the device or the home station has to be able to assign or be assigned its own domain address, its own cluster address, and its own device ID automatically so that a PnP function can be provided.
  • management packets of a common protocol can support the PnP function.
  • a common protocol defines procedures of registering a device and a home station to set each device ID and domain address.
  • Fig. 10 is a view for describing an example of a device registration process.
  • a device if a device is turned on, an address table of the device is initialized (100).
  • the device sends a device registration request (hereinafter referred to as "DRREQ") packet to a home station (120) and waits for a predetermined time in order to receive a response (130). If the home station does not send a response, the device considers that the home station is turned off (140), and waits (150) until the home station is turned on, i.e., until a home station registration indication (hereinafter referred as to "HRIND”) packet is received (160).
  • DRREQ device registration request
  • HRIND home station registration indication
  • the device receives a device registration response (hereinafter referred to as "DRRES") packet (170), it sets its own domain address and device ID and stores an address table loaded on a payload (180). Then, the device works normally to inform the user of devices connected to the network (190). If the device receives the HRIND packet (200), it repeats the processes from 110 to 190.
  • DRRES device registration response
  • Figs. 11a and lib are views for describing an example of a device registration packet.
  • Each device adopting a common protocol is assigned a domain address and a device ID according to the procedure as shown in Fig. 10 and, in the procedure, a DRREQ packet (210) and a DRRES packet (220) as shown in Fig. 11 are used.
  • Fig. 12a and 12b are views for describing an example of a device registration process.
  • Case 1 is when a device sets a domain address and a device ID normally after receiving the DRRES packet as a response to the DRREQ packet.
  • Case 2 is when a device has not received the DRRES packet because power of a home station is turned off.
  • Registration of a home station means a series of processes where domain addresses for a new domain network are determined when a new home station logs on a home network or an existing home station is turned on.
  • the user needs not to set the domain address individually and the home station can determine its own domain address by itself through message exchange with other home stations.
  • Fig. 13 is a view for describing an example of a home station registration process.
  • an address table of the home station is initialized (300).
  • the home station sends a home station registration start request (hereinafter referred to as "HRSREQ”) packet (320) and waits for a predetermined time, preferably 3 seconds, to receive a response (320). If the home station receives a home station registration start response (hereinafter referred to as "HRSRES") packet (330), the procedure of registering a new home station is completed (350) after a predetermined time, preferably 5 seconds (340).
  • HRSREQ home station registration start request
  • HRSRES home station registration start response
  • the home station sends a home station registration request (hereinafter referred to as "HRREQ") packet (360) and waits for a predetermined time, preferably 5 seconds (370). If the home station receives a home station registration response (hereinafter referred to as "HRRES") packet within the 5 seconds (390), the home station sets its own address table (400). If the home station receives the HRSREQ packet while setting the address table (400), the home station sends the HRSRES packet (410) and returns to the step 370. If the home station receives the HRSREQ packet during the step 370, the home station sends the HRSRES packet (380).
  • HRREQ home station registration request
  • HRRES home station registration response
  • the home station After a predetermined time (420), the home station checks whether the HRRES packet is received or not (430). If the HRRES packet is not received, the home station sets "1" in a domain address (460). If the home station receives the HRSREQ packet while setting "1" in the domain address, the home station sends the HRSRES packet (470). After completing to set "1" in the domain address, the home station sends the HRIND packet (480) and works normally (530).
  • the home station If the home station receives the HRREQ packet while operating normally, the, it sends the HRRES packet (540). Also, if the home station receives the DRREQ packet (550) while operating normally (530), the home station assigns a device ID to a device, sets its own address table (560), and sends a DRRES packet to the device (570).
  • Figs. 14a through 14e are views for describing an example of a home station registration packet.
  • the HRSREQ packet (600) is a packet which a new home station sends to existing home stations already logged on to a home network when the new home station wants to log on to the home network. This packet is sent in order to identify whether another home station performs a registration procedure or not. This is for preventing more than one home station from being assigned the same domain address almost simultaneously. If the home station does not receive a response within a predetermined time after sending the
  • the HRSREQ packet the home station practically begins an actual registration procedure.
  • the HRSRES packet (610) is a response packet to the HRSREQ packet. If a first home station receives the HRSREQ packet from a second home station whiling performing the registration procedure, the first home station sends the HRSREQ packet.
  • the HRSRES packet to the second home station in order to request to start a registration procedure a little later.
  • the HRREQ packet (620) is used to inform other home stations that a home station will perform a registration procedure.
  • the HRRES packet (630) is a response packet to the HRREQ packet. If a home station receives the HRRES packet after sending the HRREQ packet, the home station sets its own address table using address information in a payload of the HRRES packet and, after a predetermined time, sets its own domain address using domain address information received from other home stations.
  • a home station receives an HRREQ packet while operating normally after completion of the registration procedure, the home station sends the HRRES packet (630) with a payload containing an address table for devices in its own domain network.
  • the HRIND packet (640) is used to inform devices in the same domain network of a domain address. For example, a home station collects the HRRES packets for a predetermined time, sets its own domain address, and sends the HRIND packet to devices in the domain network. The devices in the domain network can request its own device ID after receiving the HRIND packet.
  • Figs. 15a through 15d are views for describing an example of a practical use of HRSREQ, HRSRES, HRREQ, and HRRES packets.
  • Case 1 is when a home station sends the HRSREQ packet, receives the HRSRES packet within 3 seconds, waits for 5 seconds, and, then, sends again the HRSREQ packet.
  • Case 2 is when the home station sends the HRSREQ packet, waits for 3 seconds, and sends the HRREQ packet in order to begin a registration procedure because the home station has not received any HRSRES packet within 3 seconds.
  • Case 3 is when the home station sends the HRREQ packet, receives the HRRES packet within 5 seconds, sets its own address table, and, after 5 seconds, sets its own domain address.
  • Case 4 is when the home station sets its own domain address as "1" because it has not received any HRRES packet for 5 seconds.
  • a common address and an address table for transferring data between different network protocols can enhance compatibility between network protocols and enable communication of different networks with each other using only application programs without address conversion between existing protocol layers.
  • the present invention can identify whether devices in different networks are working and a new device is registered, identify types of protocols and devices used, and support rapid mapping between a physical address and a common address.
  • the present invention is applicable to various applications requiring communications between different protocols, protocols of home server and home gateway accepting various protocols, and a compatibilization method between protocols having different protocol layer architectures.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne une adresse commune utilisable dans un protocole pour réseaux interne et externe dans un réseau domestique, ou dans un protocole commun pour communications de données entre des protocoles variés, et une table d'adresse pour la conversion d'adresse entre une adresse commune et une adresse physique. Une structure d'adresse commune selon l'invention comprend une adresse de domaine, une adresse de groupe; une adresse d'utilisation du dispositif, une adresse du type de dispositif, un dispositif ID, et un champ réservé. L'invention améliore en conséquence la compatibilité entre des protocoles réseau et permet la communication de différents réseaux entre eux, uniquement au moyen de programmes d'application, sans conversion d'adresse entre des couches protocole existantes. En outre, l'invention permet d'identifier si des dispositifs fonctionnent dans différents réseaux et si un nouveau dispositif est enregistré, d'identifier des types de protocoles et de dispositifs utilisés et d'établir une correspondance rapide entre une adresse physique et une adresse commune.
PCT/KR2003/002543 2002-11-25 2003-11-25 Procede de construction d'une adresse commune et d'une table d'adresse pour le transfert de donnees entre differents protocoles de reseau, et architecture y relative WO2004049658A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003282428A AU2003282428A1 (en) 2002-11-25 2003-11-25 Method of constructing common address and address table for transferring data between different network protocols and architectures thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2002-0073649A KR100461698B1 (ko) 2002-11-25 2002-11-25 이기종 프로토콜간 상호 데이터 전송을 위한 공통 주소 및주소 테이블 방법과 그 구조
KR10-2002-0073649 2002-11-25

Publications (1)

Publication Number Publication Date
WO2004049658A1 true WO2004049658A1 (fr) 2004-06-10

Family

ID=32388211

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2003/002543 WO2004049658A1 (fr) 2002-11-25 2003-11-25 Procede de construction d'une adresse commune et d'une table d'adresse pour le transfert de donnees entre differents protocoles de reseau, et architecture y relative

Country Status (3)

Country Link
KR (1) KR100461698B1 (fr)
AU (1) AU2003282428A1 (fr)
WO (1) WO2004049658A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006083148A1 (fr) * 2005-02-07 2006-08-10 Lg Electronics Inc. Procede de gestion d'adresses et procede d'envoi et de reception de messages dans un systeme de commande de reseau
WO2006086914A1 (fr) * 2005-02-21 2006-08-24 Zte Corporation Système de communication et méthode d’interconnexion de celui-ci
CN108449392A (zh) * 2018-03-01 2018-08-24 深圳市创梦天地科技有限公司 设备识别装置、方法、电子设备以及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100767315B1 (ko) * 2005-12-08 2007-10-17 한국전자통신연구원 디바이스 집성화 장치 및 방법
KR100724950B1 (ko) * 2006-03-09 2007-06-04 삼성전자주식회사 Ｄｌｎａ 시스템에서 ｉｅｅｅ1394 인터페이스를 사용하는 장치 간의 콘텐츠 공유 방법
KR100789755B1 (ko) * 2006-07-12 2008-01-02 한국전자통신연구원 개인 영역 무선망에서 다수의 프로토콜이 수용된 공통플랫폼을 이용한 통신장치 및 그 방법
KR100805265B1 (ko) * 2006-12-28 2008-02-20 고려대학교 산학협력단 홈 네트워크 시스템 및 홈 네트워크 시스템의 제어 방법
KR101143510B1 (ko) * 2010-11-10 2012-05-09 숭실대학교산학협력단 통신 인프라를 이용한 지연 허용 네트워크의 메시지 전송장치 및 방법

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5568471A (en) * 1995-09-06 1996-10-22 International Business Machines Corporation System and method for a workstation monitoring and control of multiple networks having different protocols
US20020026528A1 (en) * 2000-08-24 2002-02-28 Lo Kwoktung B. System and method for selectively bridging and routing data packets between multiple networks
US20020085567A1 (en) * 2000-12-28 2002-07-04 Maple Optical Systems, Inc. Metro switch and method for transporting data configured according to multiple different formats
US20020167906A1 (en) * 2001-03-19 2002-11-14 La Porta Thomas F. Multiple-protocol home location register and method of use

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10322382A (ja) * 1997-05-20 1998-12-04 Furukawa Electric Co Ltd:The ネットワーク中継装置
KR100231705B1 (ko) * 1997-06-16 2000-01-15 정선종 하이브리드 게이트웨이 구조 및 그 운용 방법
DE19835668A1 (de) * 1997-08-07 1999-02-25 Matsushita Electric Ind Co Ltd Übertragungsmedienverbindungsvorrichtung, steuernde Vorrichtung, gesteuerte Vorrichtung und Speichermedium
US6577630B1 (en) * 2000-08-04 2003-06-10 Intellon Corporation Self-configuring source-aware bridging for noisy media
KR20020074914A (ko) * 2001-03-22 2002-10-04 주식회사 라오넷 네트워크상에서의 데이터 플로우 식별 방법 및 장치
KR100371328B1 (ko) * 2001-04-17 2003-02-07 엘지전자 주식회사 가전기기 네트워크 시스템 및 주소할당방법

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5568471A (en) * 1995-09-06 1996-10-22 International Business Machines Corporation System and method for a workstation monitoring and control of multiple networks having different protocols
US20020026528A1 (en) * 2000-08-24 2002-02-28 Lo Kwoktung B. System and method for selectively bridging and routing data packets between multiple networks
US20020085567A1 (en) * 2000-12-28 2002-07-04 Maple Optical Systems, Inc. Metro switch and method for transporting data configured according to multiple different formats
US20020167906A1 (en) * 2001-03-19 2002-11-14 La Porta Thomas F. Multiple-protocol home location register and method of use

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006083148A1 (fr) * 2005-02-07 2006-08-10 Lg Electronics Inc. Procede de gestion d'adresses et procede d'envoi et de reception de messages dans un systeme de commande de reseau
KR100789497B1 (ko) * 2005-02-07 2007-12-28 엘지전자 주식회사 네트워크 컨트롤 시스템에서의 번지 관리 및 메시지 송수신방법
WO2006086914A1 (fr) * 2005-02-21 2006-08-24 Zte Corporation Système de communication et méthode d’interconnexion de celui-ci
CN108449392A (zh) * 2018-03-01 2018-08-24 深圳市创梦天地科技有限公司 设备识别装置、方法、电子设备以及存储介质

Also Published As

Publication number Publication date
KR100461698B1 (ko) 2004-12-17
KR20040045791A (ko) 2004-06-02
AU2003282428A1 (en) 2004-06-18

Similar Documents

Publication Publication Date Title
US5737333A (en) Method and apparatus for interconnecting ATM-attached hosts with telephone-network attached hosts
US7831696B2 (en) Apparatus for providing device information via network and a method thereof
US7339895B2 (en) Gateway device and control method for communication with IP and IPV6 protocols
US7292859B2 (en) Apparatus and method for managing device information through networks
US5835725A (en) Dynamic address assignment and resolution technique
US5796736A (en) ATM network topology auto discovery method
US7411952B2 (en) Communication scheme with arbitration mechanism for cases of address initialization and server setting
US8165138B2 (en) Converged infiniband over ethernet network
US20030169728A1 (en) Apparatus for controlling devices in a sub-network of a home-network and a method thereof
US20020035624A1 (en) Gateway and a method for operating the same
US20020040397A1 (en) IP based network system and networking method thereof
US20070223494A1 (en) Method for the resolution of addresses in a communication system
US6741576B1 (en) Re-assignment method of re-assigning a connection identifier in a network operating in the connection mode
JPH10154995A (ja) ゲートウェイ装置及びパケット中継方法
US7187661B2 (en) Gathering of device discovery information
US20010025322A1 (en) Internet protocol interfacing apparatus for controlling non IP-based network device with IP-based network device and method therefor
CN101155146A (zh) 网络设备
JP2003204345A (ja) 通信システム、パケット中継装置、パケット中継方法、及び中継プログラム
JP3561107B2 (ja) ネットワーク接続装置
KR20020017135A (ko) 사설망의 네트워크 노드에 접속하기 위한 시스템과 방법
US6601127B1 (en) Communication control apparatus and method, communication system, and program storage medium
JP2000101589A (ja) ダイナミックドメインネームシステム
CN100359881C (zh) 用于通过透明网桥传输分组的地址分配方法和设备
WO2004049658A1 (fr) Procede de construction d'une adresse commune et d'une table d'adresse pour le transfert de donnees entre differents protocoles de reseau, et architecture y relative
CN108471440A (zh) 一种数字对讲方法及系统

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 KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL 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): BW GH GM KE LS MW MZ 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 IT LU MC NL 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
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP