TW200841668A - Method and system of providing network addresses to in-premise devices in a utility network - Google Patents
Method and system of providing network addresses to in-premise devices in a utility network Download PDFInfo
- Publication number
- TW200841668A TW200841668A TW097103660A TW97103660A TW200841668A TW 200841668 A TW200841668 A TW 200841668A TW 097103660 A TW097103660 A TW 097103660A TW 97103660 A TW97103660 A TW 97103660A TW 200841668 A TW200841668 A TW 200841668A
- Authority
- TW
- Taiwan
- Prior art keywords
- network
- node
- address
- access point
- indoor
- Prior art date
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]
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D4/00—Tariff metering apparatus
- G01D4/002—Remote reading of utility meters
- G01D4/004—Remote reading of utility meters to a fixed location
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D21/00—Measuring or testing not otherwise provided for
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/163—Interprocessor communication
- G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
- G06F15/17306—Intercommunication techniques
-
- 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/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/741—Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6
-
- 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/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/251—Translation of Internet protocol [IP] addresses between different IP versions
-
- 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
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
-
- 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/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- 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/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- 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/50—Address allocation
- H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
-
- 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/50—Address allocation
- H04L61/5061—Pools of addresses
-
- 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/14—Multichannel or multilink 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
-
- 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/618—Details of network addresses
- H04L2101/659—Internet protocol version 6 [IPv6] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/33—Services specially adapted for particular environments, situations or purposes for indoor environments, e.g. buildings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/005—Data network PoA devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/02—Inter-networking arrangements
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02B—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
- Y02B90/00—Enabling technologies or technologies with a potential or indirect contribution to GHG emissions mitigation
- Y02B90/20—Smart grids as enabling technology in buildings sector
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S20/00—Management or operation of end-user stationary applications or the last stages of power distribution; Controlling, monitoring or operating thereof
- Y04S20/30—Smart metering, e.g. specially adapted for remote reading
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S40/00—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
- Y04S40/18—Network protocols supporting networked applications, e.g. including control of end-device applications over a network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mathematical Physics (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
200841668 九、發明說明: 【發明所屬之技術領域】 本發明的領域大體上關於控制及傳遞有價資源 (commodity)的系統,且更明確地說,係關於監視、控制、 以及傳遞有價資源的以IP為基礎的封包通訊系統。 相關申請案 本申請案主張2007年2月2曰提申的美國臨時專利申 請案序號第60/899,328號的優先權,其標題為「SYSTEM & METHOD OF COMMUNICATIONS FOR UTILITY & HOME NETWORK SERVICES USING IPV6 AND IP PROTOCOL SUITE ,。 【先前技術】 自動抄表(AMR)系統及自動抄表基礎建設(AMI)提供監 視及/或回報有價資源(例如水、電力、瓦斯、…等)之用量(或 消耗量)的服務與功能。此等系統係在一有價資源計量表 (commodity meter)以及用以回報、計費(billing)、…等的一 或多個系統之間提供通訊。有價資源計量資訊以及其它資 訊通常係從與該等計量表相關聯的網路裝置處回報給該等 回報與計費系統。 本發明試圖克服習知公用網路的限制。 【發明内容】 本發明提供一種用於以IP為基礎之通訊的系統與方 5 200841668 法其中,IPv6公用網路中的公用節點能夠指派ιρν6位 址、、°透過不以IP為基礎的室内通訊網路與該公用節點進行 通桌的至内装置。存取點係指派IPv6位址區塊給公用節 點:用以指派給該等室内裝置。,亥等經指派的區塊可能係 連、貝的並且可旎係該給定公用節點特有的。雖然該室内 衣置並不在一 Π>網路上,但是該公用節點可能會將已指派 給至内奴置的位址代理傳送給其它節點(其包含存取點), 以允許該公用網路中的其它節點定址該室内裝置。 【實施方式】 本文將在特定實施例的内文中說明本發明。如此作法 有助於瞭解本發明的特點與原理,且本發明並不受限於此 貝Μ例明確地說,本發明所述的係一種用於遠端讀取、 控制、以及管理一公用網路中之電子裝置的系統。本發明 可應用於以網路為基礎來管理電子裝置及有價資源計量表 的其它系統。 本範例實施例提供一種用以在一公用網路中監視與控 制一公用計量表的以網路為基礎的系統與方法。 圖1所不的係可用來實施本發明實施例的一公用網路 100的整體方塊圖。公用網路1〇〇可能包含一或多個電子 裝置101。於一較佳的實施例中,該等電子裝置101可能 會在一無線區域網路(LAN)102上被連接。於一公用網路的 靶例中,該LAN可能係一對應於該公用設施的鄰里或服務 區域的鄰里區域網路(neighb〇rh〇〇d area netw〇rk,Nan)。 6 200841668 如該範例實施例中所示,可以使用多冑LAN(它們可处合 或可能不會重疊),俾使一給定的電子裝置可被連接至;二 的無線LAN(或是該唯-的無線LAN的—部分)或是多個無 線LAN。該等電子裝置可能係任何類型的電子裝置。電; 裝置的範例包含公用節,點’其可能包含—公用計量表=是 可連接至H計量表。—公料量表係—能夠測量 量數量(通常係有價資源’例如電力、水、天然瓦斯 的裝置。連接至一公用計量表的公用節點可能包含一用於 在-網路上進行通訊的網路介面卡(Nlc),並且可能包含用 :在一或多個無線LAN上進行通訊的一或多個灯傳收 益。電子裝置的其它範例包含通訊裝置,例如:機上盒(可 用j有線電視或衛星電視傳送中)、家用設施(舉例來:, 水相’’、、水态、電燈、炊煮設施、…等)、電腦或計算裝置 (舉例來說’遊戲機、儲存裝置、pc、伺服器、…等)、網 路連接裝置(例如中繼器、閘道器、存取點、路由器、或是 其它網路連接裝置)、電話或蜂巢式電話、電池儲存裝置、 運輸裝置、運輪目,斑/ t + 一一 I具(舉例來說,電力車或混合動力車 ,八匕又通工具)、娛樂裝置(舉例來說,TV、DVD播放 :、機上盒、遊戲機、·等)、或是可在家中、公司、路上、 不壯或疋八匕地方找到的其它裝置。中繼器可處置電 繼t置1〇1與無線L· 102之間的通訊。舉例來說,一中 繼為可在一命早壯 二 衣置及該無線網路的基礎建設之間提供通 非㈣提及’否則’該網路中的其它裝置(例如計量 "子衣置、間道器、.··等)均同樣可實施中繼器的功能, 7 200841668 v200841668 IX. INSTRUCTIONS OF THE INVENTION: FIELD OF THE INVENTION The field of the invention relates generally to systems for controlling and communicating valuables, and more specifically to monitoring, controlling, and transmitting valuable resources. Based on the packet communication system. RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application Serial No. 60/899,328, filed on Feb. 2, 2007, entitled "SYSTEM & METHOD OF COMMUNICATIONS FOR UTILITY & HOME NETWORK SERVICES USING IPV6 AND IP PROTOCOL SUITE , [Prior Art] Automatic Meter Reading (AMR) systems and Automatic Meter Reading Infrastructure (AMI) provide monitoring and/or reporting of the amount of valuable resources (eg water, electricity, gas, etc.) (or consumption) Services and functions. These systems provide communication between a valuable resource meter and one or more systems for reporting, billing, etc. Valuable resource measurement information and Other information is typically reported back to the reward and billing systems from the network devices associated with the meters. The present invention seeks to overcome the limitations of conventional public networks. SUMMARY OF THE INVENTION IP-based communication system and party 5 200841668 method, in which the public node in the IPv6 public network can assign the ιρν6 address, and the The internal communication network communicates with the common node to the internal device. The access point assigns an IPv6 address block to the common node for assigning to the indoor device. The assigned block may be Connected, and can be unique to the given public node. Although the indoor device is not on the network, the public node may transmit the address agent assigned to the inner slave to the other A node (which includes an access point) to allow other nodes in the public network to address the indoor device. [Embodiment] The present invention will be described in the context of a particular embodiment. Such an approach helps to understand the present invention. Features and principles, and the present invention is not limited to this. Specifically, the present invention is a system for remotely reading, controlling, and managing electronic devices in a public network. The invention is applicable to other systems that manage electronic devices and valuable resource meters on a network basis. This exemplary embodiment provides a method for monitoring and controlling a common meter in a public network. Network-based system and method. Figure 1 is an overall block diagram of a public network 100 that may be used to implement an embodiment of the present invention. The public network 1 may include one or more electronic devices 101. In a preferred embodiment, the electronic devices 101 may be connected to a wireless local area network (LAN) 102. In a target of a public network, the LAN may correspond to the public. Neighborhood neighborhood of the facility or neighborhood area of the service area (neighb〇rh〇〇d area netw〇rk, Nan). 6 200841668 As shown in this exemplary embodiment, multiple LANs (which may or may not overlap) may be used to enable a given electronic device to be connected to; a wireless LAN (or the only one) - part of the wireless LAN or multiple wireless LANs. These electronic devices may be any type of electronic device. An example of a device contains a common section, which may contain - a common meter = is connectable to an H meter. - the public meter system - the ability to measure the quantity (usually a valuable resource 'such as electricity, water, natural gas. The public node connected to a common meter may contain a network for communication on the network - Interface card (Nlc), and may include one or more light transmissions for communication over one or more wireless LANs. Other examples of electronic devices include communication devices such as set-top boxes (available with j cable or Satellite TV transmission), household facilities (for example: water phase '', water state, electric light, cooking facilities, etc.), computer or computing device (for example, 'game console, storage device, pc, servo Device, etc.), network connection device (such as repeater, gateway, access point, router, or other network connection device), telephone or cellular phone, battery storage device, transportation device, transport wheel Eye, spot / t + one I (for example, electric car or hybrid car, gossip and tools), entertainment devices (for example, TV, DVD playback:, set-top box, game console, Etc.) or Other devices found at home, on the company, on the road, in the hustle or in the hustle and bustle. The repeater can handle the communication between the electric relay and the wireless L. 102. For example, a relay is available. Providing communication between the first life and the infrastructure of the wireless network (four) refers to 'otherwise' other devices in the network (such as metering "sub-clothing, inter-channel, ..... And so on) can also implement the function of the repeater, 7 200841668 v
且中繼器亦可實施該網路上其它裝置或軟體的功能。 該無線LAN 1 02可能係任何類型的無線網路,並且可 能使用任何的頻率、通訊頻道、或通訊協定。 該等LAN 1 02通常會被連接至一或多個存取點(Ap) 103。一給定LAN可能會被連接至單一個Ap,或者可能會 被連接至二或多個存取點。該等存取點1〇3可能會被連接 至一或多個廣域網路(WAN) 104。該等WAN 104可能會被 連接至一或多個後勤系統(B〇s)1〇5。該後勤系統可以處置 各種的商業或管理任務,其包含參與計量資訊的收集、管 理計量裝置、保護該網路、或是在一 AMI網路中可能所希 的其它功能。後勤系統的範例包含計費與會計系統、代理 伺服器、供應中斷偵測系統(可用在一公用網路之中)、資 料儲存系統、…等。 ' 該通訊網路(其可能係LAN或WAN或兩者之組合)内 :節點可使用-或多個協定來進行通訊。節點可能包含一 迅子裝置、一中繼器、一存取點、一路由器、或是一則。 特定的節點可能能_用IPv6來進行通訊,特定的節點可 能能夠以1Pv4來進行通訊,而㈣的節點可能能夠以IPv4 或IPv6纟進订通訊。特定的節點可能能夠將複數個ιρν6 ^包封裝在叫Pv4封包内。除此之外,料的節點還可能 由-IPv6網路來建立一 ιρν4隧道。下面將更完整 地祝明節點之間的通訊。 在通訊網路中分配與登錄網路位址 8 200841668 圖2所示的係一通訊網路的整體方塊圖,其包含一 LAN 200與LAN 206。該等LAN會連接節點202與存取點201。 如圖所示,LAN 200具有兩個存取點,而LAN 206具有一 個存取點。一網域名稱伺服器(DNS)203會經由存取點201 被連接至LAN 200與LAN 206並且會被連接至一通訊網 路204。於此目前較佳的實施例中,DNS伺服器203能夠 接收且處理動態更新,從而提供動態DNS服務。DNS的 動態更新係根據IETF RFC 2136。通訊網路204可能係任 何類型的通訊網路,其包含,但並不受限於:LAN、WAN、 無線網路、固定線路網路、私有網路、虛擬私有網路、... 等。於此目前較佳的實施例中,該通訊網路204係一廣域 網路,並且可能使用一或多個通訊協定,例如IPv4或IPv6。 一或多個計算裝置205會連接至該通訊網路204。接著便 可以使用一節點202的網路位址來將一訊息從該計算裝置 205發送至該節點。計算裝置205可能係任何裝置、裝置 之組合、網路管理系統、伺服器、後勤系統(BOS)、電腦、 網路裝置、通訊裝置、應用軟體、或是能夠透過該通訊網 路204來與一存取點或節點進行通訊的組件。一第二LAN 206亦可能會被連接至該DNS伺服器203及該通訊網路 2〇4。一 DNS伺服器可能係專屬於單一 LAN,或者二或多 個LAN可分享一 DNS伺服器。如圖所示,LAN 200與LAN 206並未重疊,因為圖中所示的節點與存取點中沒有任何 一個係同時為LAN 200與LAN 206成員。替代實施例可 9 200841668 能具有會重疊的一或多個LAN,其中,會有一或多個節點 及/或存取點係一或多個LAN所共有的。替代實施例可能 具有額外的LAN,它們可能會或可能不會彼此重疊。於此 目前較佳的實施例中,係根據下面配合圖3所述的方法來 取得一節點的網路位址。 DNS伺服器203會保留與其相關聯的LAN網路的節 點的網路位址。如上面的討論,一 DNS伺服器可能會與一 或多個LAN相關聯並且會保留一或多個LAN内的節點的 網路位址。於一較佳的實施例中,一已登錄在數個存取點 之中的節點可能會具有至少一樣多的網路位址。該等節點 的網路位址可能會被納入該DNS伺服器或是節點路由登錄 冊之中。除此之外,該DNS伺服器還可能會保留位址指派 資訊,例如節點位址指派表示符(或是節點優先表示符)。 下面表1顯示的係可被納入用以保留一 LAN中的節點的網 路位址的部分資訊。被保留在該DNS伺服器之中的資源記 錄可能包含: 表1 資源記錄類型 節點網路位址 節點名稱 節點位址優先 表示符 AAAA ADDR1 MAC1 50 ADDR2 30 ADDR2 10 AAAA ADDR4 MAC2 80 AAAA ADDR5 MAC3 44 ADDR6 20 10 200841668 如表1中所示,於此目前較佳的實施例中,該節點名 稱為該節點的MAC位址。然而,其它實施例可能使用該 節點的其它名稱,其可能包含或可能不包含或是可能係以 MAC位址為基礎。進一步言之,表!中的資源記錄(RR)類 型可能係IPv6類型。 路由登錄冊中的資訊可根據多項準則來更新,其包含 定期更新或是在符合一或多項準則時才進行更新。And the repeater can also implement the functions of other devices or software on the network. The wireless LAN 102 may be any type of wireless network and may use any frequency, communication channel, or communication protocol. These LANs 102 are typically connected to one or more access points (Ap) 103. A given LAN may be connected to a single Ap or may be connected to two or more access points. These access points 1〇3 may be connected to one or more wide area networks (WANs) 104. The WANs 104 may be connected to one or more logistics systems (B〇s) 1〇5. The logistics system can handle a variety of commercial or administrative tasks, including the collection of metering information, managing metering devices, protecting the network, or other functions that may be desirable in an AMI network. Examples of logistics systems include billing and accounting systems, proxy servers, supply disruption detection systems (available in a public network), data storage systems, ... and the like. 'The communication network (which may be a LAN or WAN or a combination of both): Nodes can communicate using - or multiple protocols. A node may contain a device, a repeater, an access point, a router, or a router. A particular node may be able to communicate using IPv6, a particular node may be able to communicate with 1Pv4, and (4) a node may be able to subscribe to IPv4 or IPv6. A particular node may be able to encapsulate a plurality of ιρν6^ packets in a Pv4 packet. In addition, the node of the material may also establish a ιρν4 tunnel by the -IPv6 network. The communication between the nodes will be more fully described below. Assigning and Logging Network Addresses in a Communication Network 8 200841668 FIG. 2 is an overall block diagram of a communication network including a LAN 200 and a LAN 206. These LANs will connect node 202 with access point 201. As shown, the LAN 200 has two access points and the LAN 206 has one access point. A Domain Name Server (DNS) 203 is connected to the LAN 200 and LAN 206 via the access point 201 and is connected to a communication network 204. In this presently preferred embodiment, DNS server 203 is capable of receiving and processing dynamic updates to provide dynamic DNS services. The dynamic update of DNS is based on IETF RFC 2136. Communication network 204 may be any type of communication network that includes, but is not limited to, LAN, WAN, wireless network, fixed line network, private network, virtual private network, ... and the like. In the presently preferred embodiment, the communication network 204 is a wide area network and may use one or more communication protocols, such as IPv4 or IPv6. One or more computing devices 205 are coupled to the communication network 204. A network address of a node 202 can then be used to send a message from the computing device 205 to the node. The computing device 205 may be any device, combination of devices, network management system, server, logistics system (BOS), computer, network device, communication device, application software, or capable of being stored through the communication network 204. A component that takes a point or node to communicate. A second LAN 206 may also be connected to the DNS server 203 and the communication network 2〇4. A DNS server may be dedicated to a single LAN, or two or more LANs may share a DNS server. As shown, the LAN 200 does not overlap with the LAN 206 because none of the nodes and access points shown in the figure are members of the LAN 200 and LAN 206 at the same time. Alternate Embodiments 9 200841668 can have one or more LANs that overlap, where one or more nodes and/or access points are common to one or more LANs. Alternate embodiments may have additional LANs that may or may not overlap each other. In the presently preferred embodiment, the network address of a node is obtained according to the method described below in conjunction with FIG. The DNS server 203 will retain the network address of the node of the LAN network associated with it. As discussed above, a DNS server may be associated with one or more LANs and will retain the network addresses of nodes within one or more LANs. In a preferred embodiment, a node that has been logged into several access points may have at least as many network addresses. The network addresses of these nodes may be included in the DNS server or node routing register. In addition, the DNS server may also retain address assignment information, such as node address assignment indicators (or node priority indicators). The information shown in Table 1 below can be incorporated into a portion of the information used to reserve the network address of a node in a LAN. The resource records retained in the DNS server may contain: Table 1 Resource Record Type Node Network Address Node Name Node Address Priority Indicator AAAA ADDR1 MAC1 50 ADDR2 30 ADDR2 10 AAAA ADDR4 MAC2 80 AAAA ADDR5 MAC3 44 ADDR6 20 10 200841668 As shown in Table 1, in the presently preferred embodiment, the node name is the MAC address of the node. However, other embodiments may use other names for the node, which may or may not contain or may be based on the MAC address. Further, the table! The resource record (RR) type in the middle may be an IPv6 type. The information in the routing book can be updated based on a number of criteria, including periodic updates or updates when one or more criteria are met.
為達解釋目的,圖中僅顯示且下文僅討論一個DNS伺 服裔。不過’替代實施例可能會使用多個Dns伺服器。 该等DNS貧源記錄的替代實施例可能包含額外資訊或 者可能排除表1中所包含的特定資訊。除此之外,雖然表 1僅包含三個節點的資訊;不過,路由登錄冊的替代實施 例亦可忐具有更多或較少節點的資訊。雖然表1包含一給 定節點的三個網路位从· χ+六μ抓 J給徂址,不過,路由登錄冊的替代實施例 中的每一_節點'亦可能具有任何數量的位址。 圖3所不的係用以取得一節點的網路位址的方法3 〇〇For the purpose of explanation, only the one shown in the figure is shown below and only one DNS server is discussed below. However, alternative embodiments may use multiple Dns servers. Alternative embodiments of such DNS poor source records may contain additional information or may exclude specific information contained in Table 1. In addition, although Table 1 contains only three nodes of information; however, alternative embodiments of routing books can also have more or fewer nodes of information. Although Table 1 contains three network bits for a given node from · 六 六 六 六 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , . Figure 3 is not a method for obtaining the network address of a node.
的整體流程圖。名q Λ ^ A 在步驟301處,一希望發送-封包或-訊 Γ-_的節點會產生—画解析要求给—刪 益。該則解析要求包含―節點辨㈣,其” μ 稱。該節點辨識符可為$ ^ . 也人“品 為子母、數子、符號、或字元的任何 組合。如上面配人闰 4 σ圖1所述,於一目前較佳的每 該節點辨識符係哕4 Μ 灵e U中, 取灯你鑌預期節點的MAC位址。如 該來源或要求節點包含用以…〜表1中所示’ 的網路位址、網路二…亥即點之辨識符、該節點 、.罔路位址優先權、…等的資訊 11 200841668The overall flow chart. Name q Λ ^ A At step 301, a node wishing to send-packet or - Γ-_ will generate a drawing resolution request to delete. The parsing requirement includes "node" (four), which is "μ". The node identifier can be $ ^ . Also "product" is a child, a number, a symbol, or any combination of characters. As described above, in Figure 1, the currently preferred per-node identifier system 哕4 Μ 灵 e U, take the MAC address of the node you are expecting. If the source or request node contains the information of the network address, the network 2, the identifier of the network, the node, the address of the network address, etc., as shown in Table 1 200841668
處,該DNS伺服器會接收該預期節點的DNS解析要求。 j步驟303處,該DNS飼服器會以—網路位址來回應與該 節點辨識符相關聯的節點。於此目前較佳的實施例中,該 網路位址係一 IP <立址。於一目前較佳的實施例中,該資源 。己錄AAAA與一 iPv6位址有關。π"資源記錄(rr)可能 係A類型、PTR類型、CNAME類型。該DNS伺服器可能 具有一給定節點的一個以上網路位址。舉例來說,多個i p V 6 位址可能會與一給定節點(或是存取點、或是B〇s、或是一 網路上的任何其它裝置)相關聯。倘若多個位址與一給定節 點相關聯的話,那麼在步驟3〇2處,該DNS伺服器便可能 冒提供一特殊RR的所有可用網路位址。或者,該伺 服器可能會選擇與該預期節點相關聯的一網路位址子集。 舉例來說,該DNS伺服器可能會選擇一網路位址以便響應 於該電子裝置來納人。偏若選擇與該預期節點相關聯的一 網路位址子集的話,該選擇可能係以連接成本為基礎、以 禪設的選擇準則為基礎、以政策(舉例來說,希望與該節點 父換訊息的電子裝4 ’該訊息的類型、大小、或優先權, 該節點所使用的訊息的特定樣態、或是該網路裝置(舉例來 說,伺服器、網路管理系統、計費系统、供應中斷管理系 統、公用管理系統、...等)的本質)為基礎、或是以特定其 它準則為基礎。倘若在該麵解析要求中提供多個網路位 址的話’那麼該響應便可能還包含對應的節點位址優先指 不符。在步驟304處,該節點會從該DNS伺服器處接收該 DNS解析要求。 12 200841668 用來將該訊息從該節點及/或—電子裝置處發送至該預 ,月蜻點或電子裝置的 、 ^ ,,,.各 θ对應於一或多個存取點。 :例末:,在1PV6…’該網路位址通常會係… / :有—個以上的存取點的話,那麼,該網路位址 白、IPv6則置碼便可能會與一給定存取點相關聯。依此方 式’該IPv6網路位址便可以允許使用—給^存取點來將一 訊息傳达至該網路目的地。倘若一節點位於—具有多個存 取點的LAN之中的話,那麼,該節點便可能會具有與該節 點相關聯的一個以上IPv6位址。 範例1—使用IPv6網路定址的多重進入 本範例具有一節點名稱為節點丨的給定節點。節點工 具有與其相關聯的兩個IPv6網路位址。節點i的路由登錄 冊項目可被讀取如下:At this point, the DNS server will receive the DNS resolution request of the prospective node. At step 303, the DNS feeder responds to the node associated with the node identifier with a network address. In the presently preferred embodiment, the network address is an IP < In a presently preferred embodiment, the resource. The recorded AAAA is related to an iPv6 address. The π"resource record (rr) may be of type A, PTR type, or CNAME type. The DNS server may have more than one network address for a given node. For example, multiple i p V 6 addresses may be associated with a given node (either an access point, or B〇s, or any other device on the network). In the event that multiple addresses are associated with a given node, then at step 3〇2, the DNS server may assume all available network addresses for a particular RR. Alternatively, the server may select a subset of network addresses associated with the intended node. For example, the DNS server may select a network address to respond to the electronic device. If a subset of network addresses associated with the intended node is selected, the selection may be based on the cost of the connection, based on the selection criteria of the meditation, and by policy (for example, wishing to be associated with the node parent) The electronic device of the message 4 'the type, size, or priority of the message, the specific aspect of the message used by the node, or the network device (for example, server, network management system, billing) Based on the nature of the system, supply disruption management system, public management system, etc.), or based on specific other criteria. If multiple network addresses are provided in the face resolution request, then the response may also include the corresponding node address priority mismatch. At step 304, the node receives the DNS resolution request from the DNS server. 12 200841668 The θ used to transmit the message from the node and/or the electronic device to the pre-, month, or electronic device corresponds to one or more access points. : End of the example: In 1PV6...'The network address will usually be... / : If there are more than one access point, then the network address is white, and the IPv6 address will be given with a given address. The access point is associated. In this way, the IPv6 network address can be used to the ^ access point to communicate a message to the network destination. If a node is located in a LAN with multiple access points, then the node may have more than one IPv6 address associated with the node. Example 1 - Multiple Entry Using IPv6 Network Addressing This example has a given node with a node name of Node 丨. The node worker has two IPv6 network addresses associated with it. The routing entry for node i can be read as follows:
節點1會經由兩個存取點AP1與AP2連接至一通訊網 13 200841668 路。API 與 IPv6 前置碼 2001:2i05:20ae:1::/64 相關聯,而 AP2 與 IPv6 前置碼 2001:2105:2〇ae:2::/64 相關聯。一希望 發送一 ‘息給卽點1的網路裝置(舉例來說,管理供應中斷 偵測的後勤系統)可能會從該DNS伺服器的路由登錄冊處 接收與節點1相關聯的網路位址(或者可能會接收兩個網路 位址)。k该供應中所债測系統被發送至使用具有前置碼 2〇01:2105:20ae:2::/64之網路位址的節點1的訊息會經由 φ AP2被路由。從該供應中斷偵測系統被發送至使用具有前 置碼2001:2105:20ae:l::/64之網路位址的節點i的訊息則 會經由API被路由。 圖4所示的係將一有節點裝置登錄在一存取點之中的 方法400的整體通訊流程圖。登錄一有節點裝置以取得一 網路位址可以套用至任何袼式或協定的網路位址。於一目 前較佳的實施例中,該LAN可能正在使用lpv6協定(單獨 • 使用或是連同IPV4協定一起使用)。為達討論的目的,方 法400將會說明使用ΙΡν6網路位址的一無線lan的節點。 於-目前較佳的實施例中,㈣M會啟動一探索過程並且 會辨識其鄰近節點以及提供外出與進入的一或多個lan的 :取,。節點Μ可能會進一步啟動一路由分析,用以辨識 會以最低路徑成本透過一或多個存取點來提供外出的一較 佳的單跳鄰居(one_h〇p neighb〇r)集。接著,便會利用一或 多個AP以及附屬@ DNS伺服器來開始進行登錄過程。在 4〇1處,節點Μ會發送一層2登錄訊息給一存取點Ap。 14 200841668 在402處,該ap會以一層2承認訊息來回應,該訊息包 含與該AP相關聯的一 IPv6前置碼。除此之外,該承認訊 息還可能包含組態資訊。於一目前較佳的實施例中,該組 怨育訊包含允許節點Μ登錄在一 DNS伺服器之中的資訊。 於另一實施例中,該ΑΡ可能會代表節點Μ來代理傳送該 DNS要求。在4〇3處,節點Μ會接收該層2承認訊息並且 會發送一層3 IPv6登錄訊息給該DNS。於一目前較佳的實 Φ 施例中,送往該DNS的1登錄訊息包含節點乂的ΙΡν6 位址’其會運用接收自該AP的ΙΡν6前置碼以及一特有的 IPV6「後置碼」,以便完成節點Μ的IPv6位址。這會連 同RFC 2462的無狀態自動組態步驟一起完成。於一較佳 的實施例中,該IPv6後置碼係以該節點汹的mac位址為 基礎。替代實施例可能會使用不以該MAC位址為基礎的 j它後置碼來創造該節點Μ的一特有的IPv6位址。請注 意,節點Μ的IPv6位址未必係全域特有的。 鲁在404處,一層3承認訊息會從該DNS被發送至節點 Μ並且會在405處被該節點接收。該層3承認訊息可能包 含節點Μ登錄該DNS伺服器之中的登錄確認訊息, 可能包含額外資訊。 雖然方法400僅顯示出一節點登錄在一存取點之中· 不過,於此目前較佳的實施例中,所有節點會登錄在至少 存取點之中。除此之外’於—目前較佳的實施例中,倘 若在與該節點相關聯的LAN上有—個以上存取點的話,^ 點便會登錄在它們的LAN上的—個以上存取點之中。 15 200841668 點甚至可以登錄在該LAN上與該節點相關聯的所有存取點 之中。 於此目前較佳的實施例中,一給定節點可能會具有與 該節點相關聯的一個以上特有IPv6位址。倘若,如上所述, 從一存取點的IPv6前置碼及一特有分量(舉例來說,該節 點的MAC位址)來決定一節點的1?¥6位址的話,那麼倘若 該節點登錄在多個存取點之中的話,那麼,該節點將會與 多個特有IPv6位址相關聯。依此方式,節點可能會具有多 ^ 條連接路徑(multihomed)。 節點Μ可能會在406處發送一層3 SNMP TRAP或 INFORM訊息給一後勤系統BOS。或者,該DNS伺服器可 能會透過SNMP發信給該BOS。較佳的係,該SNMP TRAP 或INFORM訊息包含該節點Μ的至少一 IPv6位址(並且可 能包含與節點Μ相關聯的多個網路位址)。在407處,該 BOS會接收該SNMP TRAP或INFORM訊息並且會回覆一 ^ 層3訊息,例如GMI(通用管理資訊)資料查詢。GMI資料 查詢訊息可能會要求與節點Μ有關的資訊。舉例來說,倘 若節點Μ係公用網路中的一計量表的話,那麼,該GMI 資料查詢訊息便可能會要求與該計量表的組態設定值有關 的資訊、該計量表的狀態、與該被計量的有價資源有關的 資訊、…等。在408處,節點Μ會接收該資料查詢訊息並 且會發送一資料響應訊息。在409處,該BOS會從節點Μ 處接收該資料響應訊息。 該BOS可能會在任何時間處要求一給定節點的網路位 16 200841668 址。舉例來說,當預期一訊息時,倘若該BOS尚未從節點 Μ處收到一訊息的話,那麼,該B0S便可能會查詢節點M。 倘若該B0S尚未具有節點Μ的網路位址的話,或者於_ 目别較佳的貫施例中,除非該Β 0 S正在回應一已收到的訊 息,否則倘若該網路被配置成用以要求一網路位址的話, 該B0S便可能會利用該DNS伺服器來實施查找(也就是, 一 DNS解析要求)。在410處,該B0S會發送節點Μ的一 IPv6網路位址查找訊息給該DNS伺服器。在4〗丨處,該 DNS伺服斋會以該節點M的IPv6位址回應該B〇s(倘若該 DNS伺服器具有該節點M的網路位址的話,否則該 伺服了此會回應其不具有該節點Μ的網路位址)。在4 12 處會接收節點Μ的IPv6位址。 倘若该節點並未被登錄的話,或者倘若該B〇s並未接 收忒節點的網路位址的話,那麼,該B〇s便可能會試圖以 私式化的方式來推知該][P位址或者可能會產生一 位址。 "亥B〇S可旎會使用該AP的IPv6位址及該節點的MAC位 址(如上面所述)來創造一獨特的IPv6位址。該B〇S可能 k曰^送IPv6讯息給該AP,用以要求該AP根據該節 -占的扣有MAC辨識符以該節點為基礎來將一訊息前傳至 該節點。或者,該B0S可能會要求該Ap呼叫(ping)該節 •占用以决疋该點的網路位址及/或調查該登錄過程的結 果。 入倘若節點Μ遇到問題的話,舉例來說,電力損耗、安 事件其硬體或軟體的問題、網路問題、…等,節點Μ 17 200841668 便可能會發送一用以表示一問題的訊息(例如SNMP TRAP 或INFORM訊息)給該BOS(或者發送給節點μ可以抵達的 任何裝置)。倘若為電力損耗的話,該節點Μ便可能會發 送一「最後喘息(last gasp)」訊息。在413處,節點μ會 送一最後喘息訊息給該ΑΡ。一般來說,層2最後喘息訊息 非常短,僅具有用以保存節點的資源及網路的資源的基本 資訊’俾使該訊息會被其它鄰近節點及對應的ΑΡ可靠地 φ 收到。在414處,該ΑΡ會從節點Μ處接收該最後喘息訊 息,且於此目鈾較佳的貫施例中會將一 SNMP 1TRAP或 INFORM PDU(協定資料單元或SNMP封包)與L2「最後喘 息」訊息包封在一起並且將它們前傳至表示該Ap已經從 節點Μ處接收到一最後喘息訊息的B0S。 範例2—用於運輸節點的網路定址Node 1 is connected to a communication network 13 200841668 via two access points AP1 and AP2. The API is associated with the IPv6 preamble 2001:2i05:20ae:1::/64, and AP2 is associated with the IPv6 preamble 2001:2105:2〇ae:2::/64. A network device wishing to send a message to node 1 (for example, a logistics system that manages supply interruption detection) may receive network bits associated with node 1 from the routing register of the DNS server. Address (or may receive two network addresses). The message sent by the debt measurement system in the supply to node 1 using the network address with preamble 2〇01:2105:20ae:2::/64 will be routed via φ AP2. Messages sent from the provisioning interruption detection system to node i using the network address with preamble 2001:2105:20ae:l::/64 are routed via the API. The overall communication flow diagram of method 400 for registering a node device with an access point is shown in FIG. Logging in to a node device to obtain a network address can be applied to any type or protocol network address. In a preferred embodiment, the LAN may be using the lpv6 protocol (either alone or in conjunction with the IPV4 protocol). For purposes of discussion, the method 400 will illustrate a wireless lan node using the ΙΡν6 network address. In the presently preferred embodiment, (4) M initiates a discovery process and identifies its neighboring nodes and one or more lans that provide outgoing and incoming: fetch. The node may further initiate a route analysis to identify a better one-hop neighbor (one_h〇p neighb〇r) set that will provide out-of-office through one or more access points at the lowest path cost. The login process is then initiated using one or more APs and an affiliate @DNS server. At 4〇1, the node will send a layer 2 login message to an access point Ap. 14 200841668 At 402, the ap responds with a layer 2 acknowledgement message containing an IPv6 preamble associated with the AP. In addition to this, the acknowledgement message may also contain configuration information. In a presently preferred embodiment, the set of complaints includes information that allows the node to log into a DNS server. In another embodiment, the UI may proxy the transmission of the DNS request on behalf of the node. At 4〇3, the node will receive the layer 2 acknowledgement message and send a layer 3 IPv6 login message to the DNS. In a currently preferred embodiment, the 1 login message sent to the DNS includes the node 乂 ν6 address 'which uses the ΙΡv6 preamble received from the AP and a unique IPV6 "post code". In order to complete the IPv6 address of the node. This is done in conjunction with the stateless automatic configuration steps of RFC 2462. In a preferred embodiment, the IPv6 post code is based on the mac address of the node. Alternate embodiments may use a post-code that is not based on the MAC address to create a unique IPv6 address for the node. Note that the IPv6 address of a node is not necessarily domain-specific. At 404, a layer 3 acknowledgement message is sent from the DNS to the node and is received by the node at 405. This layer 3 acknowledgement message may contain a login confirmation message from the node to the DNS server, which may contain additional information. Although method 400 only shows that a node is logged into an access point, however, in the presently preferred embodiment, all nodes will be logged into at least the access point. In addition, in the presently preferred embodiment, if there are more than one access point on the LAN associated with the node, then more than one access will be registered on their LAN. Among the points. 15 200841668 Point can even log in to all access points on the LAN associated with this node. In the presently preferred embodiment, a given node may have more than one unique IPv6 address associated with the node. If, as described above, the IPv6 preamble of an access point and a unique component (for example, the MAC address of the node) determine the address of a node of 1?¥6, then if the node logs in Within a plurality of access points, then the node will be associated with multiple unique IPv6 addresses. In this way, a node may have multiple ^multihomed paths. Node Μ may send a layer 3 SNMP TRAP or INFORM message to a logistics system BOS at 406. Alternatively, the DNS server may send a message to the BOS via SNMP. Preferably, the SNMP TRAP or INFORM message contains at least one IPv6 address of the node (and may include multiple network addresses associated with the node )). At 407, the BOS will receive the SNMP TRAP or INFORM message and will reply with a Layer 3 message, such as a GMI (General Management Information) data query. GMI Information Query messages may require information about node Μ. For example, if the node is a meter in the public network, then the GMI data query message may require information related to the configuration settings of the meter, the status of the meter, and the Information about the valuable resources being measured, ...etc. At 408, the node will receive the data inquiry message and send a data response message. At 409, the BOS receives the data response message from the node Μ. The BOS may request a given node's network bit at any time 16 200841668. For example, when a message is expected, if the BOS has not received a message from the node, then the BOS may query the node M. If the B0S does not already have a node's network address, or in a preferred embodiment, unless the S 0 S is responding to a received message, the network is configured to use In order to require a network address, the BOS may use the DNS server to perform the lookup (ie, a DNS resolution request). At 410, the POS sends an IPv6 network address lookup message for the node to the DNS server. At 4 丨, the DNS server will respond with the IPv6 address of the node M to B〇s (if the DNS server has the network address of the node M, otherwise the servo will respond to it. The network address with this node). At 4 12, the IPv6 address of the node is received. If the node is not logged in, or if the B s does not receive the network address of the 忒 node, then the B s s may attempt to privately infer the] [P bit The address may or may not be a single address. "Hai B〇S can use the AP's IPv6 address and the node's MAC address (as described above) to create a unique IPv6 address. The B〇S may send an IPv6 message to the AP to request the AP to forward a message to the node based on the node-based MAC identifier. Alternatively, the BOS may ask the Ap to ping the section • Occupy to determine the network address at that point and/or investigate the results of the login process. If the node encounters a problem, for example, power loss, hardware or software problems, network problems, etc., node Μ 17 200841668 may send a message to indicate a problem ( For example, the SNMP TRAP or INFORM message is given to the BOS (or to any device that the node μ can reach). In the event of power loss, the node may send a "last gasp" message. At 413, node μ will send a final wheezing message to the UI. In general, Layer 2 finally has a very short wheezing message, and has only basic information to save the resources of the node and the resources of the network, so that the message will be reliably received by other neighboring nodes and corresponding ports. At 414, the 接收 will receive the last wheeze message from the node ,, and in this preferred embodiment of the uranium, an SNMP 1 TRAP or INFORM PDU (a protocol data unit or SNMP packet) and L2 "last breather" The messages are encapsulated and forwarded to a POS indicating that the Ap has received a final respite message from the node. Example 2 - Network Addressing for Transport Nodes
本範例中的一給疋節點係一如圖5中所示的運輸裝 置。明確地說,節點Η係一混合動力車,其電池會從一電 柵極(electric grid)處獲得充電。當將節點Η插入一電力插 座時,節,點Η便會試圖與電力公用言十f B〇s(稱為B〇s_HB) 建立通訊。於本範例中,節點Η係位於LAn_7(其係一使 用IPv6協定的無線通訊網路)的覆蓋區域内。節點η會發 =一層2登錄要求訊息給副_7内的至少—存取點。配 =LAN-7的—存取點)會回應其ιρν6前置碼,其為私心。 節點H會使用接收自AP1的前置碼來創造-特有的IPv6 位址1點Η會使㈣點时的—網路卡的Μ。位址, 18 200841668 連同來自API的IPv6前置碼,來創造該特有的IPv6位址。 節點Η會發送一層3登錄訊息給與LAN-7相關聯的一 DNS 伺服器並且會從該DNS伺服器處接收一承認訊息。節點Η 還會登錄在LAN-7上的一第二存取點(稱為ΑΡ-2)之中。API 與AP2兩者均能夠經由一通訊網路與BOS-HB進行通訊。 AP2會將其IPv6前置碼21 ff發送給節點Η,節點Η會使 用該前置碼來創造一與ΑΡ2相關聯的第二特有IPv6位址。 接著,節點Η便會發送一 SNMP TRAP或INFORM訊息給 表示其位在LAN-7上的BOS-HB。除此之外,發送至BOS-HB 的訊息還包含用以警示BOS-HB使其知道節點Η目前被連 接至該電柵極並且正在接收電力用以對節點Η的電池進行 再充電的資訊。BOS-ΗΒ會發送訊息給節點Η,用以調查 節點Η的電力用量並且還會發送訊息以檢查節點Η是否仍 位於該網路上。在發送一訊息給節點Η之前,BOS-HB會 配合該DNS伺服器來對節點Η的網路位址實施查找。回 應對應於節點Η之查找要求的DNS伺服器可以決定與節 點Η相關聯的哪兩個特有IP位址要提供給BOS-HB。於本 範例實施例中,該DNS伺服器的路由登錄冊包含與對應於 節點Η的IPv6位址相關聯的一特有優先表示符。該優先 表示符會規定ΑΡ2優於ΑΡ1,因為ΑΡ2和ΑΡ2的連接可 靠性優於和ΑΡ1的連接可靠性。因此,該DNS伺服器會 以和ΑΡ2相關聯的網路位址來回覆BOS-HB。BOS-HB接 著會使用和AP2相關聯的網路位址,其接著會經由AP2將 訊息路由送至節點Η。倘若經由AP2從BOS-HB傳送訊息 19 200841668 至節點Η失敗的話,BOS-HB(或是該網路中的另一裝置)便 可月b θ要求且接收與節點H相關聯的次佳網路位址,並且 使用即點Η的該次佳網路位址來重新發送該已失敗訊息。 因為節點Η的該次佳網路位址對應於Αρι,所以,該已失 敗4息的重新發送會經由Αρι路由送至節點響應於將 。亥已失敗傳遞訊息送往和Ap2相關聯的網路位址,該圓$ ^艮抑可此冒改變與節點H相關聯的一或多個網路位址相 Μ的優先表示符’並且可能還會根據一或多項準則(舉例 和節點^鄰近性、和他的相依性、和節^ 的相依性、···等)來改變其它節點的優先 DDNS登鉾·由文又欠 N 、支先表不符可能會由節點H、BOS-HB、 AP-1、ap_2中的任一者發出。 ::Η會發送一含有節點U網路位 =自-來自卿_ΗΒ的要求。倘若所包含 : 包含ΑΡ1的前罟说4 』吩世址 至BOS-HB,從=¥^能會經由AP1路由送 用哪—個存取點從LAN_7外出。節點 = 點Η相關聯的哪幾個網 要 一擇與即 的標頭。藉由依據節點Η中所要二::自…的封包 封包,便可以選擇該LAN的外‘ J取=置碼來,由 例中進行外出控制。 ‘ k *多重外出實施 因為節點Η係一能夠從—位 能會造成不會與一給定^ ^動至另一位置(其可 行動節點,所以,…能會解XLAN_^^ 9浒陈登錄一仃動節點。舉 20 200841668 例來說,倘若行動節點已經在一段預設或可設定的時間週 期中未與該AP進行通訊的話,它們便可能會被解除登錄。 除此之外,或者,行動節點可能會發送資訊給一或多個A?, 用以避免解除登錄它們;或者,Ap4的政策可能會依據一 或多項特徵來決定不要解除登錄一給定的行動節點。A given node in this example is a transport device as shown in FIG. Specifically, a node is a hybrid vehicle whose battery is charged from an electric grid. When a node is inserted into a power outlet, the node will attempt to establish communication with the power utility (called B〇s_HB). In this example, the node is located in the coverage area of LAn_7, which is a wireless communication network using IPv6 protocol. Node η will send a layer 2 login request message to at least the access point in sub_7. With the =LAN-7 access point, it will respond to its ιρν6 preamble, which is selfish. Node H will use the preamble received from AP1 to create - the unique IPv6 address 1 point will make the (four) point - the network card. Address, 18 200841668 Together with the IPv6 preamble from the API, to create this unique IPv6 address. The node will send a layer 3 login message to a DNS server associated with LAN-7 and will receive an acknowledgement message from the DNS server. The node 还会 is also registered in a second access point (called ΑΡ-2) on the LAN-7. Both API and AP2 can communicate with BOS-HB via a communication network. AP2 will send its IPv6 preamble 21 ff to the node, which will use the preamble to create a second unique IPv6 address associated with ΑΡ2. The node then sends an SNMP TRAP or INFORM message to the BOS-HB indicating its location on LAN-7. In addition, the message sent to the BOS-HB also contains information to alert the BOS-HB that it knows that the node is currently connected to the electrical gate and is receiving power to recharge the node's battery. BOS-ΗΒ will send a message to the node to investigate the power usage of the node and also send a message to check if the node is still on the network. Before sending a message to the node, the BOS-HB cooperates with the DNS server to perform a lookup on the node's network address. The DNS server that responds to the node's lookup request can determine which two unique IP addresses associated with the node are to be provided to the BOS-HB. In this exemplary embodiment, the DNS server's routing entry contains a unique priority identifier associated with the IPv6 address corresponding to the node. This priority indicator specifies that ΑΡ2 is better than ΑΡ1 because the connection reliability of ΑΡ2 and ΑΡ2 is better than the connection reliability of ΑΡ1. Therefore, the DNS server will echo the BOS-HB with the network address associated with ΑΡ2. The BOS-HB will then use the network address associated with AP2, which will then route the message to the node via AP2. If the message is sent from BOS-HB via the AP2 to the node 21 200841668, the BOS-HB (or another device in the network) can request the monthly b θ and receive the second best network associated with the node H. The address is, and the failed network message is used to resend the failed message. Since the second best network address of the node 对应 corresponds to Αρι, the resend of the failed 4 message is sent to the node via Αρι to respond. Hai has failed to send a message to the network address associated with Ap2, which may change the priority identifier associated with one or more network addresses associated with node H' and possibly It will also change the priority DDNS of other nodes according to one or more criteria (for example, node ^ proximity, and his dependencies, and the dependency of the section ^, etc.). The first table mismatch may be issued by any of the nodes H, BOS-HB, AP-1, and ap_2. ::Η will send a request containing the node U network bit = from - from __. If it contains: The front-end ΑΡ ΑΡ 吩 吩 吩 吩 吩 吩 吩 B B B B B B B B B 吩 吩 吩 吩 吩 吩 吩 吩 B 吩 B B B 吩 B B B B B B B B B B B 。 。 。 。 。 Node = Which of the associated networks is to be selected. By relying on the packet of the second:: from ... in the node, you can select the outer _J of the LAN = the code is set, and the outgoing control is performed by the example. 'k *Multiple outbound implementation because the node can be driven from the - position can not be moved to another location with a given ^ (its actionable node, so... can solve XLAN_^^ 9浒For example, if the mobile node has not communicated with the AP for a preset or configurable period of time, they may be logged out. Otherwise, or The mobile node may send information to one or more A? to avoid un-entering them; or, Ap4's policy may decide not to deactivate a given action node based on one or more characteristics.
支援IPv6公用網路的系統組件 八能夠使用IPv6定址與協定來支援通訊的公用網路可能 日使用此夠進灯通訊(較佳的係,使用ιρν6)的各種裝置。 於此目別車父佳的貫施例中,I统組件(例如公用節點、存取 .、、、占以及後勤系統)會具有被整合至該個別系統組件之中的 IPv6功能性支援。本文會配合圖6、7 '以及8來顯示與說 明具有功能的系統組件的範例較佳實施例。 欣圖所不的係可在上面所述的通訊網路600中發現的 ^ 600的整體方塊圖。於一較佳的實施例中,節點6⑼System Components Supporting IPv6 Public Networks Eight public networks that can use IPv6 addressing and protocols to support communications may use various devices that are capable of communicating (preferably, using ιρν6). In this case, the I system components (such as public nodes, access, , , and logistics systems) will have IPv6 functional support integrated into the individual system components. Exemplary embodiments of the system components having functions are shown and described herein in conjunction with Figures 6, 7' and 8. What is not shown is the overall block diagram of ^ 600 found in the communication network 600 described above. In a preferred embodiment, node 6 (9)
:匕a · I置貧訊控制器6〇1、一記憶體002、LAN :線電控制器與介面6G3、私有無線電控制器與介面6〇4、 ^表與外部資料介面_、以及ιρν6協定控制器6〇9。 =表與外部資料介面咖可能會連接至一從屬裝置輸出 區域計量表資料介面6°7、及/或-外部感測器 封勺。出’丨面ΙΡν6協定控制器_可以接收與發送IPv6 谁一於必要枯’可能還會創造或保留IPv6隧道以及 進仃封包的封裝/解除封裝。 雖然該範例節點 600不包含一用於計量有價資源的計 21 200841668 量表;不過’替代實施例卻可能包含計旦 里功能。 雖然該範例節點600不包含無線曾 , ’例如私有網路鉦 線電或LAN無線電;不過,該節點的替 ”、 含一或多個無線電。 P 了此匕 雖然本文所述的範例節點600係單_壯 、 一衣置;不過,替 代實施例卻可能會使用多部電腦、多個泰 卜 ㈡包子叙置或是無線 电來貫施範例節點600。 • ® 7所示的係可在上面所述的通訊網路_中發現的 存取點700的整體方塊圖。存取點7〇〇(其亦可充當一網路 (例如一無線LAN)中的節點的閘道器)可 j旎包含:一存取點 資訊控制器701、記憶體702、一 WA ”、 卜 介面703、一私有 然線電網路控制器704、一益後LAN a μ ^ …、深LAN热線電控制器與介面 7〇5、以及網路IDsIPv6協定控制器7〇6。該網路取㈣ 協定控制器可能還包含一隨道代理器(tunnei), =者,在運用-隧道代理器的實施例中,可能會包含一與 _ -亥路由器及‘6加14(6-in-14)格式化器分離的隨道代理器。 雖然該範例存取點700不包含無線電,例如私有網路 讀電、WAN或LAN無線電;不過,該存取點的替代實 轭例部可能包含一或多個無線電。 雖然該範例存取點與該網路中的計量表或其它裝 置(舉例來說,中繼器…等)不同;不過,替代實施例亦可 ° 口 :亥網路中卽點、計量表、中繼器、或是任何其它裝置 的功能。 雖然本文所述的存取點7〇〇係單一裝置;不過,替代 22 200841668 實施例卻可能會使用多部電腦、多個電子裝置或是無線電 來實施存取點700。 圖8所示的係可在上面所述的 k δ孔網路5〇〇中發現的 後勤系統800的整體方塊圖。後勤系统_可能包含:一 通訊伺服器801、一無線私有網路通訊控制器8〇2、一路 由器及6加14格式化器803、一應用軟體伺服器8〇4、以 及一資料庫伺服器805。無線私有網路通訊控制器8〇2可 能會與一私有無線網路進行通訊。路由器及6加Μ柊式 化器_可能會與該WAN進行通訊。路由器及6加】^各 式化器803可能還包含一隨道代S|§,或者,在運用一隧 道代理器的實施例中,可能會包含_與該路由器及6加Μ 格式化器分離的随道代理器。該WAN可能係—網際網路、 一企業内部網路、或是任何其它類型的廣域網路。應用軟 體伺服器可能係使用在-公用網路之中的任何類^應用軟 體。其範例包含,但並不受限於:計f應用軟體;會計^ 用軟體;供應中斷偵測及/或管理應用軟體;組態及/或供 應應用軟體;網路應用軟體(例如代理伺服器、dns或 伺服器);儲存、備份、及/或復原應用軟體;客戶介面應 用軟體(舉例來說,-用以讓客戶控制與—節點相關聯的樣 態或是用以控制一節點的各種樣態的介面應用軟體節點 官理器、内容管理或傳送系統、通訊管理器或通訊供應應 用軟體、…等。或者,該格式化器可能係一用於ιρν6封包 封裝的6轉4(6 to 4)格式化器。 雖然本文所述的後勤系統800係單一實體;不過,亦 23 200841668 一資料中心 的組件可能 部電腦來實 個位置中或 還可能會聚 系統可能會 另一範例來 伺服器。在 軟體的額外 可實施在一或多部電腦中,與 r 舉例來說,實施在 中的多部伺服器上。本文所述 人、 4的後勤糸統800 冒被貫施在不同的電腦上,戋 可旎會跨越多 :。除此之外,後勤系、统800亦可能會跨越多 夕個網路上的多部電腦來實施。後勤系統_ 集或是包含多個應用軟體。舉例來說,一後勤 同時包含一會計系統以 _ 各戶计費系統。以 §兄’後勤系統可能包含—計費系統以及一代理 額外的替代實施例中亦可能包含任何數量應用 組合。 公用節點子網路 圖9所不的係-公用節點子網路_的整體方塊圖。 網路_可能包含-公用節.點州。該公用節點可能包含 有W源計量表’或者可能會介接一有價資源計量表。 公料點9(Π能約與-通訊網路9〇2進行通訊。於一較佳 的貫施例中,公用節K 4 P』901包含一能夠使用IP協定(IPv4 IPv6)來與一無線LAN進行通訊的無線電。公用節點9〇1 :包含-室内裝置介面903。室内裝置介自9〇3會連接至 至内衣置904 ’用以在該公用節點及該等室内裝置之間提 七、通砒鏈路。除此之外,該公用節點還可在室内裝置9〇4 及被連接至該公用節點的通訊網路9〇2之間提供一通訊鍵 路。 於—目前較佳的實施例中,該公用節點室内裝置介面 24 200841668 〇3 a刀配網路位址給其能夠與之進行通訊的室内裝 置於可此的貫施例中,由該室内裝置介面903所分配 的、、周路位址係一 Ip位址。較佳的係,被分配給一室内裝置 的網路位址係通訊網路9〇2内獨一無二的。該室内裝置介 面903可此還會分享,或是允許分享,被分配給房屋裡面 的子、、罔(subnet)外面的一室内裝置的網路位址。因此,可從 房屋的子網路外面直接定址室内裝置。該公用節點會代表 φ 該對應至内裝置來代理傳送該已分配IP位址,從而允許該 通訊網路中的其它節點使用該已分配IP位址來與該室内裝 置進行通成。範例3利用一可能的實施例來解釋此情形。 範例3—使用IPv6網路定址的室内通訊 本範例係一具有節點名稱為節點3 1 cedar Ave的公用 即點。即點31 Cedar Ave係被部署在一住宅單元(或是住 豕)之中並且能夠經由多重協定及通訊技術來與室内裝置 _ (住豕裡面的裝置)進行通訊。舉例來說,節點3i Cedar Ave 可以利用無線個人區域網路(WPAN)來與裝置進行通訊, 或疋利用PLC(電力線載波)來與被連接至該住家的電栅極 之〃有PLC功此的裝置進行通訊。該範例住家包含〔五個 室内裝置,一透過WPAN來進行通訊的自動調溫器 (therm〇stat),一透過wpAN來進行通訊的泳池泵(ρ〇〇ι p mp) 透過PLC來進行通訊的冷藏箱(freezer),以及 一透過WPAN來進行通訊的家庭娛樂系統。 該WPAN可能係各種網路技術或標準中任何一者或是 25 200841668:匕a · I set the poor controller 6〇1, a memory 002, LAN: line controller and interface 6G3, private radio controller and interface 6〇4, ^ table and external data interface _, and ιρν6 agreement Controller 6〇9. The = table and external data interface may be connected to a slave output area meter interface 6°7, and/or - external sensor seal. The 丨 6 6 6 6 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定 协定Although the example node 600 does not include a meter for measuring valuable resources, the 2008 41668 668 scale; however, the alternative embodiment may include a function in the calendar. Although the example node 600 does not include wireless, 'for example, private network radio or LAN radio; however, the node is replaced with one or more radios. P. Although the example node 600 described herein is Single_strong, one-piece; however, alternative embodiments may use multiple computers, multiple tabs, or radios to apply the example node 600. An overall block diagram of the access point 700 found in the communication network _. The access point 7 〇〇 (which can also act as a gateway for a node in a network (eg, a wireless LAN)) can include : an access point information controller 701, a memory 702, a WA ”, a interface 703, a private line grid controller 704, a post-LAN a μ ^ ..., a deep LAN hot line controller and interface 7〇5, and the network IDsIPv6 protocol controller 7〇6. The network fetch (four) protocol controller may also include a tunnie, and in the embodiment of the application-tunnel agent, it may include a _-Hai router and a '6 plus 14 (6) -in-14) A separate proxy for the formatter. Although the example access point 700 does not include a radio, such as a private network read, WAN or LAN radio; however, an alternate semaphore portion of the access point may contain one or more radios. Although the example access point is different from a meter or other device (for example, a repeater, etc.) in the network; however, an alternative embodiment may also be used in the network: a point in the network, a meter, The function of a repeater, or any other device. Although the access point 7 described herein is a single device; however, instead of the 22 200841668 embodiment, the access point 700 may be implemented using multiple computers, multiple electronic devices, or a radio. The overall block diagram of the logistics system 800 found in the k δ hole network 5〇〇 described above is shown in FIG. The logistics system_ may include: a communication server 801, a wireless private network communication controller 8, 2, a router and 6 plus 14 formatter 803, an application software server 8〇4, and a database server 805. The wireless private network communication controller 8〇2 may communicate with a private wireless network. The router and the 6 Μ柊 Μ柊 _ may communicate with the WAN. Routers and 6 Plus 803 may also include a suffix S|§, or, in embodiments employing a tunneling agent, may include _ separate from the router and the 6-plus formatter Companion agent. The WAN may be an internet network, an intranet, or any other type of wide area network. The application software server may use any class of application software in the public network. Examples include, but are not limited to: application software; accounting software; supply interruption detection and / or management application software; configuration and / or supply application software; network application software (such as proxy server , dns or server); store, backup, and/or restore application software; client interface application software (for example, to allow customers to control the state associated with the node or to control a node's various The interface interface application software node manager, content management or transmission system, communication manager or communication provision application software, etc. Alternatively, the formatter may be a 6 to 4 (6 to for ιρν6 packet encapsulation 4) Formatter. Although the logistics system 800 described herein is a single entity; however, 23 200841668 a component of a data center may be part of a computer or may also be a convergence system may have another example to the server. The software can be implemented in one or more computers, and r is, for example, implemented on multiple servers. The logistics system 800 of the person, 4 described in this article On different computers, there will be more than one: In addition, the logistics department and system 800 may also be implemented across multiple computers on multiple networks. Logistics system _ set or multiple application software For example, a logistics includes both an accounting system and a billing system for each household. Any number of application combinations may also be included in the alternative system that may include the billing system and an agent. The overall block diagram of the node subnet Figure 9 - Common Node Subnet _ Network _ may contain - common section. Point state. The common node may contain a W source meter ' or may interface A valuable resource meter. The material point 9 (communication can communicate with the communication network 9〇2. In a preferred embodiment, the common section K 4 P 901 includes an IP protocol (IPv4 IPv6). a radio to communicate with a wireless LAN. The common node 9〇1 includes an indoor device interface 903. The indoor device is connected from the ninth to the undergarment 904' for the common node and the indoor devices. Between seven, the chain In addition, the common node can also provide a communication link between the indoor unit 9〇4 and the communication network 9〇2 connected to the common node. In the presently preferred embodiment, Common node indoor device interface 24 200841668 〇 3 a knives with a network address for the indoor device with which it can communicate, in the embodiment, the peripheral device address assigned by the indoor device interface 903 It is an Ip address. Preferably, the network address assigned to an indoor device is unique within the communication network 9〇2. The indoor device interface 903 can also be shared, or allowed to share, be assigned. The network address of an indoor device outside the subnet and subnet inside the house. Therefore, the indoor unit can be directly located outside the subnet of the house. The common node will proxy the assigned IP address on behalf of the corresponding internal device, thereby allowing other nodes in the communication network to communicate with the indoor device using the assigned IP address. Example 3 uses a possible embodiment to explain this situation. Example 3 - Indoor Communication Using IPv6 Network Addressing This example is a public point with a node name of node 3 1 cedar Ave. The point 31 Cedar Ave is deployed in a residential unit (or residence) and is capable of communicating with the indoor unit _ (the device inside the residence) via multiple protocols and communication technologies. For example, node 3i Cedar Ave can communicate with the device using a wireless personal area network (WPAN), or use a PLC (power line carrier) to connect to the electrical gate of the home. The device communicates. The example home contains [five indoor devices, a thermostat (therm〇stat) that communicates via WPAN, and a pool pump (ρ〇〇ι p mp) that communicates via wpAN to communicate via PLC. A freezer and a home entertainment system that communicates via WPAN. The WPAN may be any of a variety of network technologies or standards or 25 200841668
任何組合,其包含,但並不受限於:藍芽、zigBee(iEEE 802.15.4) > irDA . UWB(IEEE 802.15.3) ^ Dust TSMP >Any combination, including, but not limited to: Bluetooth, zigBee (iEEE 802.15.4) > irDA . UWB (IEEE 802.15.3) ^ Dust TSMP >
Insteon、以IEEE 8〇215為基礎的其它技術、…等。 公用節點31 Cedar Ave會使用ιΡν6通訊協定以無線 的方式來與一公用網路進行通訊。該公用網路包含其它的 公用節點與至少一存取點,以及一用於管理節點31 Cedar Ave 的 BOS。 公用節點3 1 Cedar Ave包含一電力用量計量表,其會 監視與回報該住家的電力用量。除此之外,節點3丨。以訂Insteon, other technologies based on IEEE 8〇215, etc. The public node 31 Cedar Ave will communicate wirelessly with a public network using the ιΡν6 protocol. The public network includes other common nodes and at least one access point, and a BOS for managing node 31 Cedar Ave. Common Node 3 1 Cedar Ave includes a power usage meter that monitors and reports the amount of electricity used by the home. In addition to this, node 3丨. Order
Ave迺包含一用於其它有價資源計量表的介面,其會被連 接至一天然瓦斯計量表,該天然瓦斯計量表會監視與回報 該住家的天然瓦斯用量。 節’沾3 1 Cedar Ave會分配一 ιρν6位址給每一個該些 室内裝置。節點31 Cedar Ave會與通訊網路分享該自動調 溫器、泳池泵、冷藏箱、以及娛樂系統的已分配IPv6位址。 明確地說,該等室内裝置的網路位址會與一室内管理入口 -起分享,該室内管理入口會被連接至該公用網路並且允 許屋主監視與控制該等室内裝置。—或多個室内裝置的網 路位址亦可由通訊網路内的節點31⑽a來代理傳 送,或者可經由該通訊網路來與節點3l Cedar A”進行通 訊。 經由該室内管理人口 ’屋主(或是其它人)便可以使用 該已分配1Ρ位址來與該等室内裝置進行通訊。節點31Cedar Ave曰接收奴达彺至内裝置的封包,根據該已分配π位址 26 200841668 來辨識該預期駐恶 、, ^ 、J衣置,亚且在合宜的室内通訊系統(WPAN、 PLC、 ^ \ , ···、)上將該等封包的酬載前傳至該預期裝置。同樣 地在°亥至内通訊系統上從該室内裝置處被接收到的通訊 ° b曰被輸入至少一(或複數)封包的酬載之中並且會被發 C至σ亥至内笞理入口’其包含被分配給該室内裝置的網路 位址。 "亥專至内裝置的室内登錄冊項目可被讀取如下: 室内登錄冊 —----~ 室内裝置名稱 --- 已分配 IPv6 網路位址 室内通訊技術 原有位址 自動调溫器 位址1 ZigBee 冷藏箱 位址2 ZigBee ^ 1 PLC, 泳池泵 位址3 ZigBee __参樂系統 位址4 ZigBee __^ 2__ Z, • 節點31 Cdar Ave會使用該等已分配網路位址及該室 内通訊技術以允許在該等室内裝置及室内通訊網路外面之 間進行通訊。 於一較佳的實施例中,該公用節點可能還會保留室内 裝置的一存取控制清單(ACL)e使用該ACL,該公用節點 便允許根據該ACL來接取一室内裝置。舉例來說,該acl 可能會規定一家用保全系統可能僅允許從一安全入口處來 接取。試圖與該家用保全系統進行通訊的任何裝置或系統 27 200841668 均會被拒絕接取,除非其提供在該ACL之中所規定之對應 於該安全入口的合宜驗證資訊。 该公用節點ACL可能還會規定可用於内送資料運輸量 及外迗貪料運輸量中任一者或兩者的服務埠或是網路程序 名稱(network daemon name) 〇 於一目可較佳的實施例中,該公用節點可能會分配可 路由的網路位址給室内裝置。在可能無法使用該網路位址 ⑩ 的至内裝置中,如上面的範例3,WPAN與PLC裝置會使 用它們自己的網路位址並且具有一已分配Ip位址。因此, 被分配給該室内裝置的網路位址會由該公用節點來代理傳 送。於使用IPv6的實施例中,一存取點可能會分配其已指 派IPv6位址的一部分給該公用節點。接著,該公用節點便 可能會從被分配給該公用節點的IPv6位址中指派位址給室 内裝置。於一較佳的實施例中,該Ap可能會指派一連續 網路區塊給一或多個公用節點。接著,該等公用節點。便 • 可能會分配任何該等已指派位址,或是它們的一部分,給 室内裝置。 被分配給一裝置的網路位址可能部分或完全以和該裝 置、一存取點、或該裝置本身進行通訊的公用節點的Mac 位址為基礎。 除此之外,或者,可以使用規則或政策來決定要指派 給室内裝置的位址。規則可能係以下面為基礎:裝置類型; 裝置屬性;該裝置所使用的網路技術或網路協定;該裝置 的有價資源用量類型(舉例來說,電力、瓦斯、水、.·.等)· 28 200841668 ' 2裝置的:價資源用量歷史資料或特徵(舉例來說,高用 里中用里…等),§亥裝置實際所在的處所或所在處所的 區段;該裝置的已分配屬性(舉例來說,一裝置的重要性, -裝置的用途,例如醫療設備、滅火設備、保全設備、緊 急反應6又傷、…等);或是該裝置的使用者或該處所的擁有 者/經營者所分配的屬性。規則可能還會結合上面所列的多 項因素,舉例來說,可能會考量裳置的類型、實體處所、 籲電力消耗、以及該裝置是否與安全或緊急反應有關。 除此之外,或者,可能會為特殊的裝置、用途、使用 ::二預留特定的網路位址。舉例來說,可能會為緊急 人它們的設備預留特定的網路位址。因此,出現在 二至内子網中的—緊急反應器的-行動式室内裝置可 ㈣:此等緊急反應器裝置的一預留位址群中分配到一位 址。由一預留位址群所认 派,舉例來說,依據下: = 根據某項崎 ,刑r、二一 配網路位址址:反應器的 • ::「、火災、EMT、…等);它們的組合或組織(部門、 = 裝置類型―織、目的、或裝置的任 何其它屬性;…等。 4解# ^於指派位址給公用節點及分配該等 = 曰派位址給使用公用節點的室内裝置的—種可能的實施 範例4—分配室内IPv6網路位址 一具有節點名稱計量表Μ、 Τ衣ΗΜ的公用節點係被部署在 29 200841668 住宅單元(或是住家)之中並且能夠經由多重協定及通訊技 術來與室内裝置(該住家或鄰近住家裡面的裝置)進行通 訊。除此之外,計量表HM還包含一有價資源計量表,其 會計量該住家中所使用的電力。計量表HM可以利用WP AN 來與裝置進行通訊,或是利用PLC來與被連接至該住家的 電栅極之具有PLC功能的裝置進行通訊。該住家包含:六 個室内裝置,它們可與計量表HM進行通訊;一透過WP AN 來進行通訊的自動調溫器(thermostat); —透過PLC來進行 通訊的冷藏箱(freezer); —在WP AN上進行通訊的住家警 示系統;一視訊相機,其會監視該住家的一部分並且會在 WP AN上進行通訊;一健康監視系統,其可監視長輩的健 康並且其會在WP AN上進行通訊;以及一透過WP AN來 進行通訊的家庭娛樂系統。 計量表HM會使用IPv6通訊協定以無線的方式來與一 公用網路進行通訊。該公用網路包含其它的公用節點與至 少一存取點 AP214、AP137、以及AP8,以及一用於管理 計量表HM的B0S。該B0S還包含一客戶入口,其可允許 屋主來監視或控制或同時監視與控制該等室内裝置的一部 分或全部。 存取點AP214、API37、以及AP8每一者均具有一 IPv6 位址的/64指派值。存取點API 37會指派IPv6位址的/125 給公用節點計量表HM。計量表HM會從其IPv6位址的/125 指派值中選擇位址用以分配位址給要登錄在它之中的室内 裝置。計量表HM會分配位址給透過WP AN來進行通訊的 30 200841668 自動調溫器、透過PLC來進行通訊的冷藏箱、在wpAN 上進行通訊的住家警示系統、在WPAN上進行通訊的視訊 相機、在WPAN上進行通訊的健康監視系統、以及透過 WPAN來進行通訊的家庭娛樂系統。倘若一或多個室内裝 置被移除的話,或者從計量表HM處解除登錄的話,那麼, 計量表HM便會將被分配給該已移除或已解除登錄之室内 裝置的網路位址重新分配給另一室内裝置。 指派位址區塊給公用節點可以根據各種準則來隔離。 舉例來說,該公用網路中地理上或邏輯上不同的區2可能 會具有從一可用位址區塊子集中所指派的位址區塊。 雖然上面的範例實施例讓該等室内裝置與一公用節點 進行通訊,其中,該等室内裝置係被分配給(或是被安裝在) 該公用節點的室内某處;不過,替代實施例卻可讓室^裝 置透過鄰近屋子的公用節點來進行通訊。 雖然上面的範例使用根據CIDR(無類型域間路由)標記 法的-给定大小的連續區塊;不㉟,替代實施例卻可能會 使用任何大小的位址區塊,而且不論是連續或不連續。 經由IPv4網路從一 IPv6節點傳送封包 究竟經由IPv4網路來使用r 6轉4(6 t〇 /」取 6加 m 4)」通訊可由該存取點、該後勤系統、或是該系統 的另一組件來決定。根據節點的類型、網路的類型、選定 的存取點、後勤系統、訊息的類型、訊息 女王程度、…等,經由lpv4網路在該公用網路中的一 aw 31 200841668 節點之間的通訊可能係經由「6轉4」或「6加4」通訊。 舉例來說,針對高安全性來說,可以使用「6加4」通訊。 ο月注忍’「6加4」通§fl通常會被稱為隨道作用(tunneling), 而「6轉4」通訊則通常會被稱為網路位址轉換(NAT)或是 IPv6封包封裝。 圖10所示的係一網路1000的整體方塊圖,其中,— IPv4隧道會將一 IPv6 LAN連接至一 ιρν6後勤系統。網路 1000包含兩個區域網路1001與1002。LAN 1001與1002 包含節點1 003。於此目前較佳的實施例中,節點i 〇〇3為 公用節點。LAN 1002會被連接至存取點API 1004。LAN 1001會被連接至存取點AP2 1〇〇5與存取點AP3 1〇〇6。存 取點API 1004與存取點AP2 1005會連接至通訊網路 1007。存取點AP3 1006會連接至通訊網路1 〇〇8。於此目 前較佳的實施例中,通訊網路1〇07與1〇〇8為廣域網路。 後勤系統BOS-1 1009會連接至WAN 1007。後勤系統BOS-2 1010會連接至WAN 1008。後勤系統B〇S-3 1011會連接 至 WAN 1008。 於該範例實施例中,LAN 1001與1〇〇2係使用胸6來 進行通訊。同樣地,WAN 1008係運用IPv6通訊協定。存 取點AP3 1006(其會將LAN 1001連接至WAN 1008)係運 用 IPv6。後勤系統 bos] 1〇〇9、b〇s_2 1〇1〇、以及 b〇s_3 1011全部都係運用IPv6通訊協定。 WAN 1007係一 IPv4網路,並且不支援ιρν6。存取點 1004與1005(它們會分別將LAN 1〇〇2與1〇〇1連接至Wan 32 200841668 1007)能夠使用IPv6來進行通訊並且參與幫助經由WAN 1007來將IPv6封包傳送至BOS 1009與1010(反之亦然)的 機制之中。 LAN 1002上來自節點1003欲送往BOS-1 1009或 BOS-2 1010的訊息會使用一 IPv6位址與封包格式被發送 至存取點API 1004。API 1004會創造且使用一經由WAN 1007(動態或手動配置)的IPv6隧道。LAN 1001上來自節 點1003的一 IPv6封包可能會將該封包路由經過WAN 1007 或是經過WAN 1008。倘若該IPv6封包希望路由經過WAN 1008的話,便會使用AP3 1006,且因為WAN 1008係一 IPv6 網路,所以,不需要實施任何的隧道、轉換、或是封裝作 業。然而,倘若該IPv6封包路由經過WAN 1007的話,那 麼,便會使用AP2 1005,來自節點1003的該IPv6封包將 會通過一「6加4」隧道,如圖中所示,或者,可能會被 封裝在一 IPv4封包之中,用以在一 6轉4虛擬隧道中傳送 經過WAN 1007,如下面配合圖12所述。 如圖11中所示,介於和該IPv6 LAN相關聯的存取點 及該B0S之間的封包流係經由IPv4 WAN。 圖12所示的係根據一網路1200的整體方塊圖,其中, IPv6封包會通過一 IPv4 WAN。網路1200可能包含兩個區 域網路1201與1202。LAN 1201與1202包含節點1203。 於此目前較佳的實施例中,節點1203為公用節點。LAN 1201 與1202會使用IPv6協定及定址來與節點1203進行通訊。 LAN 1202會被連接至存取點API 1204。LAN 1201會被連 33 200841668 接至存取點AP2 1205與存取點ΑΡ3 ι2〇6。存取點Αρι 12〇4 與存取點AP2 1205會連接至通訊網路12〇7。存取點Ap3 1206會連接至通訊網路12〇8。於此目前較佳的實施例中, 通訊網路1207與1208為使用ipv4協定及位址的廣域網 路。後勤系統BOS-1 1209會連接至WAN 1207。後勤系統 BOS-2 1210 會連接至 WAN 12〇8。後勤系統 B〇s_3 ΐ2ΐι 會連接至WAN 1208。 在LAN 120 1或1202上要發送一訊息給該等後勤系統 BOS-卜BOS-2、以及BOS_3中其中一者或多者的節點12〇3 必須通過一或多個IPv4 WAN 1207或1208。 在LAN 1201或1202上的節點1203會將一使用IPv6 位址的IPv6封包發送給合宜的存取點,用以和預期的後勤 系統進行通訊。倘若BOS-1 1209為預期的後勤系統的話, 可以使用API 1204來連接至WAN 1207。API 1204會接 收來自節點1203的IPv6封包,並且可以將該已收到的lpv6 封包封裝在一 IPv4封包的酬載部分之中。為達此目的,Αρι 可能會具有或是會為自己取得一全域IPv4位準。具有協定 41的IPy4標頭會被附加在該ιρν6封包前面。與BOS-1相 關聯的一 IPv4位址會被使用在該IPv4封包之中,以該IPv6 封包作為酬載(該IPv6封包係該ipV4封包内的數據報 (datagram))。該前置封包標頭的Bos-i的巧“位址亦可 藉由抽出該IPv6目的地位址,2002::前置碼後面的32位位 元而從該已封裝封包的IPv6目的地位址中推知。於此實施 例中’該前置封包中的IPv4來源位址為AP1的ipv4位址。 34 200841668 接著,該封包IPv4封包便會經由WAN 1207被傳送至BOS-1 1209。BOS-1 1209會接收該IPv4封包,並且抽出該經封 裝的IPv6封包。該IPv6封包的酬載會被BOS-1 1209抽出。 依此方式,API 1204以及BOS-1 1209會經由IPv4 WAN 1207使用「6」轉「4」的隧道轉換,而不會建立一明確的 隨道。Ave迺 contains an interface for other valuable resource meters that will be connected to a natural gas meter that monitors and rewards the natural gas usage of the home. Section 沾 3 1 Cedar Ave will assign a ιρν6 address to each of these indoor units. Node 31 Cedar Ave shares the assigned IPv6 address of the auto-tuner, pool pump, reefer, and entertainment system with the communications network. Specifically, the network addresses of the indoor devices are shared with an indoor management portal that is connected to the public network and allows the homeowner to monitor and control the indoor devices. - or the network address of the plurality of indoor devices may also be transmitted by the node 31 (10) a in the communication network, or may communicate with the node 31 Cedar A" via the communication network. The other person can use the allocated address to communicate with the indoor devices. The node 31Cedar Ave receives the packet of the slave device, and identifies the expected host according to the allocated π address 26 200841668. , , ^ , J , , and in the appropriate indoor communication system (WPAN, PLC, ^ \ , ···,), the payload of the packets is forwarded to the intended device. Similarly within the ° Hai to The communication received from the indoor device on the communication system is entered into the payload of at least one (or plural) packets and will be sent C to the ig to the internal access port 'its inclusion is assigned to the The network address of the indoor unit. The internal register item of the "Hai-specific device" can be read as follows: Indoor register----~~ Indoor device name--- Allocated IPv6 network address indoor communication Original technology Thermostat address 1 ZigBee reefer address 2 ZigBee ^ 1 PLC, pool pump address 3 ZigBee __ 参乐系统 address 4 ZigBee __^ 2__ Z, • Node 31 Cdar Ave will use these allocated networks The location of the road and the indoor communication technology to allow communication between the indoor devices and the outside of the indoor communication network. In a preferred embodiment, the common node may also maintain an access control list of the indoor device ( ACL) e uses the ACL, and the public node allows access to an indoor device based on the ACL. For example, the acl may specify that a security system may only allow access from a secure entry. Any device or system that communicates with the home security system 27 200841668 will be denied access unless it provides appropriate verification information corresponding to the security entry as specified in the ACL. The common node ACL may also be specified for use. The service of either or both of the inbound data traffic and the external traffic, or the network daemon name is preferred. The public node may assign a routable network address to the indoor device. In an in-device that may not be able to use the network address 10, as in example 3 above, the WPAN and PLC devices use their own network. The path address also has an assigned IP address. Therefore, the network address assigned to the indoor device is forwarded by the common node. In the embodiment using IPv6, an access point may allocate it. A portion of the IPv6 address has been assigned to the public node. The public node may then assign an address to the indoor device from the IPv6 address assigned to the public node. In a preferred embodiment, the Ap may assign a continuous network block to one or more common nodes. Then, the common nodes. • Any of these assigned addresses, or a portion of them, may be assigned to an indoor unit. The network address assigned to a device may be based in part or in whole on the Mac address of the public node that communicates with the device, an access point, or the device itself. Alternatively, rules or policies may be used to determine the address to assign to the indoor device. The rules may be based on: device type; device properties; network technology or network protocol used by the device; type of valuable resource usage for the device (for example, electricity, gas, water, .., etc.) · 28 200841668 ' 2 device: historical data or characteristics of price resource usage (for example, in high-use use, etc.), where the physical location or location of the device is located; the assigned attribute of the device (for example, the importance of a device, - the use of the device, such as medical equipment, fire-fighting equipment, security equipment, emergency response, injury, etc.); or the user of the device or the owner of the premises / The attributes assigned by the operator. The rules may also incorporate a number of factors listed above, for example, may consider the type of skirt, the physical location, the power consumption, and whether the device is related to a safety or emergency response. In addition, or may be reserved for a specific device, use, use :: two reserved specific network address. For example, specific network addresses may be reserved for emergency devices for their devices. Therefore, the emergency reactor-operating indoor unit appearing in the second to inner subnet can be (4): a priority address group of such emergency reactor devices is assigned to a single address. Recognized by a reserved address group, for example, according to the following: = According to a certain item, the sentence r, the second one with the network address: the reactor's ::: ", fire, EMT, ..., etc. ); their combination or organization (department, = device type - weaving, purpose, or any other attribute of the device; ... etc. 4 solution # ^ in assigning addresses to the common node and assigning those = 曰 位 位 给A possible implementation example of an indoor device of a common node 4 - Allocating an indoor IPv6 network address - A common node having a node name meter and a Τ ΗΜ is deployed in 29 200841668 residential units (or homes) And communicating with the indoor device (the home or the device in the neighboring home) via multiple protocols and communication technologies. In addition, the meter HM also includes a valuable resource meter that measures the use of the home. The meter HM can communicate with the device using the WP AN or with a PLC to communicate with a PLC-enabled device connected to the electrical grid of the home. The home contains: six indoor devices. They can communicate with the meter HM; a thermostat that communicates via the WP AN; a freezer that communicates via the PLC; a home warning system that communicates on the WP AN; a video camera that monitors a portion of the home and communicates on the WP AN; a health monitoring system that monitors the health of the elders and communicates on the WP AN; and communicates via the WP AN Home entertainment system. The meter HM communicates wirelessly with a public network using an IPv6 protocol. The public network contains other common nodes and at least one access point AP214, AP137, and AP8, and one The BOS of the management meter HM. The BOS also includes a customer portal that allows the homeowner to monitor or control or simultaneously monitor and control some or all of the indoor devices. Access points AP214, API37, and AP8 each Each has an /64 assignment value of an IPv6 address. The access point API 37 assigns /125 of the IPv6 address to the common node meter HM. The meter HM will be /125 from its IPv6 address. The address of the assigned value is used to allocate the address to the indoor device to be registered in it. The meter HM assigns the address to the 30 200841668 thermostat that communicates through the WP AN, and communicates through the PLC. Refrigerator, home warning system for communication on wpAN, video camera for communication on WPAN, health monitoring system for communication on WPAN, and home entertainment system for communication via WPAN. One or more indoor devices If it is removed, or if the login is cancelled from the meter HM, then the meter HM will reallocate the network address assigned to the removed or deregistered indoor device to another indoor device. Assigning address blocks to common nodes can be isolated according to various criteria. For example, a geographically or logically distinct zone 2 in the public network may have addressable blocks assigned from a subset of available address blocks. Although the above exemplary embodiment allows the indoor devices to communicate with a common node, wherein the indoor devices are assigned (or installed) somewhere within the common node; however, alternative embodiments may Let the room device communicate through the common node in the adjacent room. Although the above example uses a contiguous block of a given size according to the CIDR (Typeless Inter-Domain Routing) notation; instead of 35, alternative embodiments may use any size of the address block, and whether it is continuous or not continuous. The transmission of packets from an IPv6 node via an IPv4 network is performed via an IPv4 network using r 6 to 4 (6 t〇/"takes 6 plus m 4). The communication may be by the access point, the logistics system, or the system. Another component to decide. Communication between an aw 31 200841668 node in the public network via the lpv4 network, depending on the type of node, the type of network, the selected access point, the logistics system, the type of message, the degree of message queen, etc... It may be via "6 to 4" or "6 plus 4" communication. For example, for high security, you can use "6 plus 4" communication. ο月注忍' "6 plus 4" §fl is usually called tunneling, and "6 to 4" communication is usually called network address translation (NAT) or IPv6 packet Package. Figure 10 is an overall block diagram of a network 1000 in which an IPv4 tunnel connects an IPv6 LAN to a ιρν6 logistics system. Network 1000 includes two regional networks 1001 and 1002. LANs 1001 and 1002 contain node 1 003. In the presently preferred embodiment, node i 〇〇 3 is a common node. LAN 1002 will be connected to access point API 1004. The LAN 1001 will be connected to the access point AP2 1〇〇5 and the access point AP3 1〇〇6. The access point API 1004 and the access point AP2 1005 are connected to the communication network 1007. The access point AP3 1006 is connected to the communication network 1 〇〇 8. In the presently preferred embodiment, the communication networks 1〇07 and 1〇〇8 are wide area networks. The logistics system BOS-1 1009 will connect to the WAN 1007. The logistics system BOS-2 1010 will connect to the WAN 1008. The logistics system B〇S-3 1011 will be connected to WAN 1008. In this exemplary embodiment, LANs 1001 and 1〇〇2 use chest 6 for communication. Similarly, WAN 1008 uses the IPv6 protocol. Access point AP3 1006 (which will connect LAN 1001 to WAN 1008) is IPv6. The logistics system bos] 1〇〇9, b〇s_2 1〇1〇, and b〇s_3 1011 all use the IPv6 protocol. WAN 1007 is an IPv4 network and does not support ιρν6. Access points 1004 and 1005 (which will connect LANs 1〇〇2 and 1〇〇1 to Wan 32 200841668 1007, respectively) can communicate using IPv6 and participate in helping to transfer IPv6 packets to BOS 1009 and 1010 via WAN 1007. Among the mechanisms (and vice versa). Messages from the node 1003 destined for the BOS-1 1009 or BOS-2 1010 on the LAN 1002 are sent to the Access Point API 1004 using an IPv6 address and packet format. API 1004 creates and uses an IPv6 tunnel via WAN 1007 (dynamic or manual configuration). An IPv6 packet from node 1003 on LAN 1001 may route the packet through WAN 1007 or through WAN 1008. If the IPv6 packet is intended to be routed through the WAN 1008, the AP3 1006 will be used, and since the WAN 1008 is an IPv6 network, no tunneling, conversion, or encapsulation is required. However, if the IPv6 packet is routed through WAN 1007, AP2 1005 will be used, and the IPv6 packet from node 1003 will pass through a "6 plus 4" tunnel, as shown in the figure, or it may be encapsulated. In an IPv4 packet, it is transmitted through the WAN 1007 in a 6 to 4 virtual tunnel, as described below in conjunction with FIG. As shown in Figure 11, the packet flow between the access point associated with the IPv6 LAN and the POS is via an IPv4 WAN. Figure 12 shows an overall block diagram of a network 1200 in which an IPv6 packet passes through an IPv4 WAN. Network 1200 may include two regional networks 1201 and 1202. LANs 1201 and 1202 contain nodes 1203. In the presently preferred embodiment, node 1203 is a common node. LANs 1201 and 1202 communicate with node 1203 using IPv6 protocols and addressing. LAN 1202 will be connected to access point API 1204. The LAN 1201 will be connected to the access point AP2 1205 and the access point ΑΡ3 ι2〇6 by the connection 33 200841668. The access point Αρι 12〇4 and the access point AP2 1205 are connected to the communication network 12〇7. The access point Ap3 1206 is connected to the communication network 12〇8. In the presently preferred embodiment, communication networks 1207 and 1208 are wide area networks that use ipv4 protocols and addresses. The logistics system BOS-1 1209 is connected to the WAN 1207. The logistics system BOS-2 1210 will connect to WAN 12〇8. The logistics system B〇s_3 ΐ2ΐι will connect to WAN 1208. A node 12 〇 3 to send a message on the LAN 120 1 or 1202 to one or more of the logistics systems BOS-B BOS-2, and BOS_3 must pass through one or more IPv4 WANs 1207 or 1208. Node 1203 on LAN 1201 or 1202 sends an IPv6 packet using the IPv6 address to the appropriate access point for communication with the intended logistics system. If the BOS-1 1209 is the intended logistics system, API 1204 can be used to connect to the WAN 1207. The API 1204 will receive the IPv6 packet from the node 1203 and may encapsulate the received lpv6 packet in the payload portion of the IPv4 packet. For this purpose, Αρι may or may acquire a global IPv4 level for itself. The IPy4 header with protocol 41 will be appended to the ιρν6 packet. An IPv4 address associated with BOS-1 is used in the IPv4 packet, with the IPv6 packet as a payload (the IPv6 packet is a datagram within the ipV4 packet). The Bos-i address of the pre-packet header can also be extracted from the IPv6 destination address of the encapsulated packet by extracting the IPv6 destination address, the 2002:: 32-bit bit following the preamble. It is inferred that in this embodiment, the IPv4 source address in the pre-packet is the ipv4 address of AP1. 34 200841668 Next, the packet IPv4 packet is transmitted to BOS-1 1209 via WAN 1207. BOS-1 1209 The IPv4 packet is received and the encapsulated IPv6 packet is extracted. The payload of the IPv6 packet is extracted by the BOS-1 1209. In this way, the API 1204 and the BOS-1 1209 are switched to "6" via the IPv4 WAN 1207. The "4" tunnel is converted without creating a clear track.
或者’用以接收來自節點1203之IPv6封包的AP1 1204 會將IPv6封包封裝在UDP封包内,用以使用WAN 12〇7 傳送至BOS-1 1209。如上,依此方式,AP1 12〇4以及B〇S-1 1209便能夠經由ipV4 WAN 1207來交換 希望經由IPv4 WAN及IPv6 LAN來發送一訊息至節 點1203的B0S-1 1209可能會經由WAN 1207來發送一 ιρν4 封包至API 1204。API 1204可能會將一 IPv6前置碼附加 在接收自BOS-1 1209且希望送往節點12〇3的封包的ιρν4 位址的前面,從而讓該IPv4位址會被有效地轉換,用以在 IPv6 LAN 1201上來傳送該已收到的封包。 於又一替代實施例中,可能會經由一或多個ipv4 wan 來創造一 IPv6「明確隧道」(或者可能會經由一給定的 WAN來創造-個以上的ιρν6隧道),同樣如上配合圖ι〇 的討論。舉例來說,LAN _或、2Ό2上的節點讓會 發送-使用Π>ν6位址的ΙΡν6封包至合宜的存取點,用以 和該預期的後勤系統進行通訊。倘若刪]12〇9係該預 期的後勤系統的話,可以使用AP1 12()4連接至WAN衝。、 AH觀會接收來自節點12〇3的ιρν6封包,並且可能會 35 200841668 經由IPv4 WAN 1207建立一 IPv6隧道(或者可能會接取一 已建立的)IPv6隧道。一隧道代理器(圖中並未顯示)可能會 經由IPv4 WAN 1207建立一 IPv6隧道。這係一經過組態 設定的隧道(稱為6加4隧道),其中,於一目前較佳的實 施例中,介於任一側預期BOS及AP節點之間的資料運輸 量一定會使用此隧道。一組態劇本(configuration script)可 能會在該公用網路的該存取點及一後勤系統之間被交換, 用以經由該廣域網路來建立該隧道。於一較佳的實施例 中,API 1204會建立通往B0S-1 1209的隧道。然而,替 代實施例可能會讓一或多個後勤系統經由一 WAN來建立 一「6加4」隧道通往一或多個存取點。6加4隨道係一經 過組態設定的隧道。於替代的實施例中,舉例來說,還可 能會使用IPv6封包的UDP封裝來防止經由WAN 1207傳 送的封包不會被可能出現在WAN 1207之中的任何NAT(網 路位址轉換)裝置阻隔。 API 1204所收到的IPv6封包IPv4會透過經由WAN 1207的「6加4」隧道被傳送至B0S-1 1209。BOS-1 1209 會接收且處理該IPv6封包。同樣地,BOS-1 1209可能會 使用經由WAN 1207的「6加4」隧道經由API 1204來發 送IPv6封包至節點1203。 經由一 IPv6公用網路傳送IPv4封包 圖13所示的係一網路1300的整體方塊圖,其中,IPv4 封包會通過一 IPv6 LAN。網路1300可能包含兩個區域網 36 200841668 路1301與1302。LAN 1301與1302包含節點1303。於此 目前較佳的實施例中,節點13〇3為公用節點。LAN 13〇2 曰被連接至存取點API 1304。LAN 1301會被連接至存取 二占AP2 1305與存取點AP3 1306。存取點1304與存取點1305 胃連接至通訊網路13〇7。存取點13〇6會連接至通訊網路 13 08於此目鈾較佳的實施例中,通訊網路13 〇7與1 308 為廣域網路。後勤系統BOS-1 1309會連接至WAN 1307。 φ 後勤系統1^8·2 U 1〇會連接至WAN 1307與WAN 1308。 後勤系統BOS-3 1311會連接至WAN 1308。 LAN 1301上的節點1312為使用ιΡν4來進行通訊的 IPv4節點,而LAN 13〇1則運用ιρν6。發送訊息給b〇s 131〇 的節點1312(其會經由IPv6 WAN連接至LAN 13〇1)可藉由 在LAN 13 01上發送IPv4封包的節點13 12來達成。 節點1312會發送其IPv4封包至AP2,用以前傳至 BOS-1 1309。於此情況中,AP2能夠讀取該lpv4封包中的 除目的地標頭,但是卻不會再格式化該封包;該封包會在ιρν4 WAN 1307 上橫越至 BOS-1 1309 或 BOS_2 1310;BOS-1 1309 與BOS-2 1310兩者均能夠分解該ιΡν4封包,讀取該來源 貪訊與該酬載;B0S-1 13〇9與B〇S-2 1310還會產生欲送 往1Pv4節點1312的IPv4封包,用以通過WAN 13 07,並 且藉由AP2 1305前傳至節點1312。 於可施的替代貫施例中,AP2 1305能夠將該等ιρν4 位址與標頭映射且轉換成ιρν6,並且還會讀取該酬載且映 射至1Pv6封包。之後,該IPv6封包便會如同所有其它的Ipv6 37 200841668 封包在一 6轉4或6加4隧道中通過WAN 13 07; BOS 1309 與BOS 1310會接收且處理該經過重新格式化的ιρν6封包 並且還會在針對節點1312的任何響應中或是與節點1312 所進行的任何通訊中產生一 ipv6封包。返回的I]pv6封包 冒在别傳至節點13 12之前被Ap2 13〇5轉換回Ipv4格式。 於又一可能的實施例中,透過IPv6 WAN從節點1312 奴岫往BOS 1310或B0S 1311的IPv4封包會被AP2 1305 _ 或AP3 1306轉換成IPv6袼式,並且會被前傳至b〇s 131〇 或BOS 1311(依此方式,便不需要涉及6加4或6轉4隧 道作業)。 本务明已經參考特殊實施例作過說明。不過,熟習本 技術的人士便很容易明白可以上面所述之較佳實施例中之 形式以外的扣疋形式來具現本發明。這可在不脫離本發明 的精神下來完成。 因此,本文的較佳實施例僅具解釋性而不應被視為具 • 有任何限制意義。本發明的範疇係由隨附的申請專利範圍 來給定,而並非係前面的說明,而且本文希望涵蓋落在該 等申請專利項之範圍内的所有變化例與等效例。 【圖式簡單說明】 圖1所不的係根據本發明一實施例可用來實施本發明 的一以電腦為基礎的系統的整體方塊圖。 圖2所示的係根據本發明一實施例可用來實施本發明 的一以電腦為基礎的系統的整體方塊圖。 38 200841668 圖3所不的係根據—可能實施例,用以提供一區域網 路中節點的網路位址的方法的整體流程圖。 、 固4所示的係根據本發明一實施例,用以將一有節點 一、彔在存取點之中的整體通訊流程圖。 圖5所示的係根據本發明一實施例,用以將一可充電 此合動力車登錄在一存取點之中的整體方塊圖。Alternatively, AP1 1204, which receives the IPv6 packet from node 1203, encapsulates the IPv6 packet in a UDP packet for transmission to BOS-1 1209 using WAN 12〇7. As above, in this manner, AP1 12〇4 and B〇S-1 1209 can exchange OBV-1 WAN 1207 via ipV4 WAN 1207 to send a message to node 1203 via IPv4 WAN and IPv6 LAN. 1209 may be via WAN 1207. Send a ιρν4 packet to API 1204. API 1204 may append an IPv6 preamble to the front of the ιρν4 address received from BOS-1 1209 and destined for the packet of node 12〇3, so that the IPv4 address is effectively translated for use in The IPv6 LAN 1201 is sent to transmit the received packet. In yet another alternative embodiment, an IPv6 "clear tunnel" may be created via one or more ipv4 wan (or more than one ιρν6 tunnel may be created via a given WAN), again as described above. Awkward discussion. For example, a node on LAN_OR, 2Ό2 will send a packet to the appropriate access point using the ΙΡv6 address of the Π>ν6 address to communicate with the intended logistics system. If you delete the 12/9 system for the expected logistics system, you can use AP1 12()4 to connect to the WAN. The AH view will receive the ιρν6 packet from the node 12〇3, and may establish an IPv6 tunnel (or possibly an established) IPv6 tunnel via the IPv4 WAN 1207. A tunneling agent (not shown) may establish an IPv6 tunnel via IPv4 WAN 1207. This is a configured tunnel (referred to as a 6 plus 4 tunnel), wherein in a presently preferred embodiment, the amount of data traffic between the expected BOS and AP nodes on either side must be used. tunnel. A configuration script may be exchanged between the access point of the public network and a logistics system for establishing the tunnel via the wide area network. In a preferred embodiment, API 1204 establishes a tunnel to BOS-1 1209. However, alternative embodiments may allow one or more logistics systems to establish a "6 plus 4" tunnel to one or more access points via a WAN. The 6 plus 4 channel is once configured through the tunnel. In an alternate embodiment, for example, UDP encapsulation of IPv6 packets may also be used to prevent packets transmitted via WAN 1207 from being blocked by any NAT (Network Address Translation) device that may be present in WAN 1207. . The IPv6 packet IPv4 received by the API 1204 is transmitted to the BOS-1 1209 through the "6 plus 4" tunnel via the WAN 1207. The BOS-1 1209 will receive and process the IPv6 packet. Similarly, BOS-1 1209 may use the "6 plus 4" tunnel via WAN 1207 to send IPv6 packets to node 1203 via API 1204. Transferring IPv4 Packets via an IPv6 Public Network Figure 13 shows an overall block diagram of a network 1300 in which an IPv4 packet passes through an IPv6 LAN. Network 1300 may include two regional networks 36 200841668, roads 1301 and 1302. LANs 1301 and 1302 include a node 1303. In the presently preferred embodiment, node 13〇3 is a common node. The LAN 13〇2 is connected to the Access Point API 1304. The LAN 1301 will be connected to access two AP2 1305 and access point AP3 1306. The access point 1304 and the access point 1305 are connected to the communication network 13〇7. The access point 13〇6 is connected to the communication network. In the preferred embodiment of the uranium, the communication networks 13 〇 7 and 1 308 are wide area networks. The logistics system BOS-1 1309 is connected to the WAN 1307. φ Logistics System 1^8·2 U 1〇 will connect to WAN 1307 and WAN 1308. The logistics system BOS-3 1311 will connect to the WAN 1308. The node 1312 on the LAN 1301 is an IPv4 node that communicates using ιΡν4, and the LAN 13〇1 uses ιρν6. Sending a message to node 1312 of b〇s 131〇 (which will connect to LAN 13〇1 via IPv6 WAN) can be achieved by transmitting IPv4 packetized node 13 12 on LAN 13 01. Node 1312 will send its IPv4 packet to AP2, which was previously passed to BOS-1 1309. In this case, AP2 can read the destination header in the lpv4 packet, but will not format the packet; the packet will traverse to BOS-1 1309 or BOS_2 1310 on ιρν4 WAN 1307; BOS- Both 1 1309 and BOS-2 1310 are capable of decomposing the ιΡν4 packet, reading the source of the message and the payload; B0S-1 13〇9 and B〇S-2 1310 are also generated to be sent to the 1Pv4 node 1312. The IPv4 packet is used to pass through WAN 13 07 and is forwarded to node 1312 by AP2 1305. In an alternative embodiment, AP2 1305 can map the ιρν4 address to the header and convert it to ιρν6, and also read the payload and map it to the 1Pv6 packet. After that, the IPv6 packet will pass through WAN 13 07 as all other IPv6 37 200841668 packets in a 6 to 4 or 6 plus 4 tunnel; BOS 1309 and BOS 1310 will receive and process the reformatted ιρν6 packet and also An ipv6 packet is generated in any response to node 1312 or in any communication with node 1312. The returned I]pv6 packet is converted back to the Ipv4 format by Ap2 13〇5 before being passed to node 13 12. In yet another possible embodiment, the IPv4 packet from the node 1312 to the BOS 1310 or the BOS 1311 via the IPv6 WAN is converted to the IPv6 format by the AP2 1305 _ or AP3 1306, and is forwarded to the b〇s 131〇. Or BOS 1311 (in this way, there is no need to involve 6 plus 4 or 6 to 4 tunneling operations). This service has been described with reference to the specific embodiments. However, it will be readily apparent to those skilled in the art that the present invention can be embodied in a form of a buckle other than that of the preferred embodiment described above. This can be done without departing from the spirit of the invention. Therefore, the preferred embodiments herein are merely illustrative and should not be considered as limiting. The scope of the present invention is defined by the scope of the appended claims, and is not intended to be BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is an overall block diagram of a computer-based system in accordance with one embodiment of the present invention that can be used to implement the present invention. 2 is an overall block diagram of a computer-based system in accordance with an embodiment of the present invention that can be used to implement the present invention. 38 200841668 Figure 3 is an overall flow diagram of a method for providing a network address of a node in a regional network, in accordance with a possible embodiment. The solid 4 shows an overall communication flow diagram for having a node and an access point in accordance with an embodiment of the present invention. Figure 5 is an overall block diagram of a rechargeable electric vehicle registered in an access point, in accordance with an embodiment of the present invention.
圖6所示的係根據本發明一實施例,可在一通訊網路 中發現的節點的整體方塊圖。 圖7所示的係根據本發明一實施例,可在一通訊網路 中發現的存取點的整體方塊圖。 圖8所示的係根據本發明一實施例,可在一通訊網路 中餐現的後勤糸統(back office system)的整體方塊圖。 圖9所示的係根據一可能實施例的一公用節點的子網 路的整體方塊圖。 圖1 〇所示的係根據本發明一實施例的一網路的整體方 塊圖,其中,一 IPv4隧道會將一 ipv6 LAN連接至一 ιρν6 後勤系統。 圖11所示的係根據本發明一實施例的一整體方塊圖, 其中,會在與該IPv6 LAN相關聯的存取點及經由該ιρν4 WAN的B0S之間產生封包流。 圖12所示的係根據一可能實施例的一網路的整體方塊 圖,其中,IPv6封包會通過一 ipv4 WAN。 圖13所示的係根據一可能實施例的一網路的整體方塊 圖,其中,IPv4封包會通過一 ipv6 LAN。 39 200841668 主要元件符號說明 100 公用網路 101 電子裝置 102 無線區域網路 103 存取點 104 廣域網路 105 後勤系統 200 區域網路 201 存取點 202 節點 203 網域名稱伺服器 204 通訊網路 205 計算裝置 206 區域網路 500 通訊網路 600 節點 601 裝置資訊控制器 602 記憶體 603 區域網路無線電控制器 604 私有無線電控制器與介 605 計量表與外部資料介面 606 從屬裝置輸出介面 607 區域計量表資料介面 40 200841668 608 外部感測器裝置輸出介面 609 IPv6協定控制器 700 存取點 701 存取點資訊控制器 702 記憶體 703 廣域網路介面 704 私有無線電網路控制器 705 無線區域網路無線電控制器與介面 706 網路IDs IPv6協定控制器 800 後勤系統 801 通訊伺服器 802 無線私有網路通訊控制器 803 路由器及6加14格式化器 804 應用軟體伺服器 805 資料庫伺服器 806 網域名稱伺服器介面 900 公用節點子網路 901 公用節點 902 通訊網路 903 室内裝置介面 904 室内裝置 1000 網路 1001 區域網路 1002 區域網路 41 200841668Figure 6 is an overall block diagram of a node that can be found in a communication network in accordance with an embodiment of the present invention. Figure 7 is an overall block diagram of an access point that can be found in a communication network in accordance with an embodiment of the present invention. Figure 8 is an overall block diagram of a back office system in a communication network in accordance with an embodiment of the present invention. Figure 9 is an overall block diagram of a subnet of a common node in accordance with a possible embodiment. Figure 1 is a block diagram of a network in accordance with an embodiment of the present invention, wherein an IPv4 tunnel connects an ipv6 LAN to a ιρν6 logistics system. 11 is an overall block diagram of an embodiment of the present invention in which a packet stream is generated between an access point associated with the IPv6 LAN and a BOS via the ιρν4 WAN. Figure 12 is an overall block diagram of a network in accordance with a possible embodiment in which an IPv6 packet passes through an ipv4 WAN. Figure 13 is an overall block diagram of a network in accordance with a possible embodiment in which an IPv4 packet passes through an ipv6 LAN. 39 200841668 Main component symbol description 100 Public network 101 Electronic device 102 Wireless area network 103 Access point 104 Wide area network 105 Logistics system 200 Area network 201 Access point 202 Node 203 Domain name server 204 Communication network 205 Computing device 206 Area Network 500 Communication Network 600 Node 601 Device Information Controller 602 Memory 603 Area Network Radio Controller 604 Private Radio Controller and Interface 605 Meter and External Data Interface 606 Slave Output Interface 607 Area Meter Data Interface 40 200841668 608 External Sensor Device Output Interface 609 IPv6 Protocol Controller 700 Access Point 701 Access Point Information Controller 702 Memory 703 WAN Interface 704 Private Radio Network Controller 705 Wireless Area Network Radio Controller and Interface 706 Network IDs IPv6 Protocol Controller 800 Logistics System 801 Communication Server 802 Wireless Private Network Communication Controller 803 Router and 6 Plus 14 Formatter 804 Application Software Server 805 Database Server 806 Domain Name Server Interface 900 Common Node Subnet 901 Common Node 902 Communication Network 903 Indoor Device Interface 904 Indoor Unit 1000 Network 1001 Area Network 1002 Area Network 41 200841668
1003 節點 1004 存取點 1005 存取點 1006 存取點 1007 通訊網路 1008 通訊網路 1009 後勤系統 1010 後勤系統 1011 後勤系統 1200 網路 1201 區域網路 1202 區域網路 1203 節點 1204 存取點 1205 存取點 1206 存取點 1207 通訊網路 1208 通訊網路 1209 後勤系統 1210 後勤系統 1211 後勤系統 1300 網路 13 01 區域網路 1302 區域網路 42 200841668 1303 節點 1304 存取點 1305 存取點 1306 存取點 1307 通訊網路 1308 通訊網路 1309 後勤系統 1310 後勤系統 1311 後勤系統 1312 節點 431003 Node 1004 Access Point 1005 Access Point 1006 Access Point 1007 Communication Network 1008 Communication Network 1009 Logistics System 1010 Logistics System 1011 Logistics System 1200 Network 1201 Area Network 1202 Area Network 1203 Node 1204 Access Point 1205 Access Point 1206 Access Point 1207 Communication Network 1208 Communication Network 1209 Logistics System 1210 Logistics System 1211 Logistics System 1300 Network 13 01 Area Network 1302 Area Network 42 200841668 1303 Node 1304 Access Point 1305 Access Point 1306 Access Point 1307 Communication Network 1308 Communication Network 1309 Logistics System 1310 Logistics System 1311 Logistics System 1312 Node 43
Claims (1)
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US89932807P | 2007-02-02 | 2007-02-02 | |
| US11/807,177 US8489716B2 (en) | 2007-02-02 | 2007-05-24 | Method and system of providing network addresses to in-premise devices in a utility network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| TW200841668A true TW200841668A (en) | 2008-10-16 |
| TWI372546B TWI372546B (en) | 2012-09-11 |
Family
ID=39675706
Family Applications (5)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW097103661A TWI369101B (en) | 2007-02-02 | 2008-01-31 | Method and system of providing ipv6 packet transit between two ipv6 nodes of a utility network connected via an ipv4 network using encapsulation technique |
| TW097103660A TWI372546B (en) | 2007-02-02 | 2008-01-31 | Method and system of providing network addresses to in-premise devices in a utility network |
| TW097103900A TWI376132B (en) | 2007-02-02 | 2008-02-01 | Method and system of providing ip-based packet communications with in-premise devices in a utility network |
| TW097103901A TWI369111B (en) | 2007-02-02 | 2008-02-01 | Method and system of providing ip-based packet communications in a utility network |
| TW097103898A TWI427991B (en) | 2007-02-02 | 2008-02-01 | Method and system for transmitting packet transmission of IPV6 node and common intra-gate area network through tunneling technology through IPV4 network |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW097103661A TWI369101B (en) | 2007-02-02 | 2008-01-31 | Method and system of providing ipv6 packet transit between two ipv6 nodes of a utility network connected via an ipv4 network using encapsulation technique |
Family Applications After (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW097103900A TWI376132B (en) | 2007-02-02 | 2008-02-01 | Method and system of providing ip-based packet communications with in-premise devices in a utility network |
| TW097103901A TWI369111B (en) | 2007-02-02 | 2008-02-01 | Method and system of providing ip-based packet communications in a utility network |
| TW097103898A TWI427991B (en) | 2007-02-02 | 2008-02-01 | Method and system for transmitting packet transmission of IPV6 node and common intra-gate area network through tunneling technology through IPV4 network |
Country Status (15)
| Country | Link |
|---|---|
| US (10) | US8364846B2 (en) |
| EP (1) | EP2127226B1 (en) |
| JP (1) | JP5329433B2 (en) |
| KR (1) | KR101434705B1 (en) |
| CN (2) | CN101641908B (en) |
| AU (1) | AU2008214466B2 (en) |
| BR (1) | BRPI0806837A2 (en) |
| CA (1) | CA2676656C (en) |
| DK (1) | DK2127226T3 (en) |
| MX (1) | MX2009008085A (en) |
| MY (1) | MY151825A (en) |
| RO (1) | RO126258A2 (en) |
| RU (1) | RU2479932C2 (en) |
| TW (5) | TWI369101B (en) |
| WO (5) | WO2008097447A1 (en) |
Families Citing this family (129)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9001645B2 (en) * | 2006-05-17 | 2015-04-07 | Rajant Corporation | System and method for packet delivery backtracking |
| US7532587B2 (en) * | 2006-09-06 | 2009-05-12 | Motorola, Inc. | Method and apparatus for performing anonymous source routing |
| US7957322B2 (en) | 2007-02-02 | 2011-06-07 | Silver Sring Networks, Inc. | Flow-through provisioning in utility AMR/AMI networks |
| US8364846B2 (en) * | 2007-02-02 | 2013-01-29 | Silver Spring Networks, Inc. | Method and system of providing IP-based packet communications with in-premisis devices in a utility network |
| AU2008212549A1 (en) * | 2007-02-09 | 2008-08-14 | Business Intelligent Processing Systems, Plc | System and method for performing payment transactions, verifying age, verifying identity, and managing taxes |
| US8339991B2 (en) | 2007-03-01 | 2012-12-25 | Meraki, Inc. | Node self-configuration and operation in a wireless network |
| US8072951B2 (en) | 2007-06-15 | 2011-12-06 | Silver Spring Networks, Inc. | Method and system for providing routing protocols in a frequency hopping spread spectrum network |
| US8233905B2 (en) | 2007-06-15 | 2012-07-31 | Silver Spring Networks, Inc. | Load management in wireless mesh communications networks |
| US7769888B2 (en) | 2007-06-15 | 2010-08-03 | Silver Spring Networks, Inc. | Method and system for providing network and routing protocols for utility services |
| US8130700B2 (en) | 2007-06-15 | 2012-03-06 | Silver Spring Networks, Inc. | Method and system for providing network and routing protocols for utility services |
| US8279870B2 (en) | 2007-08-01 | 2012-10-02 | Silver Spring Networks, Inc. | Method and system of routing in a utility smart-grid network |
| US9177323B2 (en) | 2007-08-28 | 2015-11-03 | Causam Energy, Inc. | Systems and methods for determining and utilizing customer energy profiles for load control for individual structures, devices, and aggregation of same |
| US9130402B2 (en) | 2007-08-28 | 2015-09-08 | Causam Energy, Inc. | System and method for generating and providing dispatchable operating reserve energy capacity through use of active load management |
| US8806239B2 (en) | 2007-08-28 | 2014-08-12 | Causam Energy, Inc. | System, method, and apparatus for actively managing consumption of electric power supplied by one or more electric power grid operators |
| US8805552B2 (en) | 2007-08-28 | 2014-08-12 | Causam Energy, Inc. | Method and apparatus for actively managing consumption of electric power over an electric power grid |
| US12438368B2 (en) | 2007-08-28 | 2025-10-07 | Causam Enterprises, Inc. | System and method for estimating and providing dispatchable operating reserve energy capacity through use of active load management |
| US8280057B2 (en) * | 2007-09-04 | 2012-10-02 | Honeywell International Inc. | Method and apparatus for providing security in wireless communication networks |
| CA2703546A1 (en) | 2007-10-25 | 2009-04-30 | Trilliant Networks, Inc. | Gas meter having ultra-sensitive magnetic material retrofitted onto meter dial and method for performing meter retrofit |
| WO2009067256A2 (en) | 2007-11-25 | 2009-05-28 | Trilliant Networks, Inc. | System and method for power outage and restoration notification in an advanced metering infrastructure network |
| EP2215550A1 (en) | 2007-11-25 | 2010-08-11 | Trilliant Networks, Inc. | Energy use control system and method |
| US8138934B2 (en) | 2007-11-25 | 2012-03-20 | Trilliant Networks, Inc. | System and method for false alert filtering of event messages within a network |
| EP2215616B1 (en) | 2007-11-25 | 2016-08-17 | Trilliant Networks, Inc. | Communication and message route optimization and messaging in a mesh network |
| US7940679B2 (en) * | 2008-05-08 | 2011-05-10 | Elster Electricity, Llc | Power outage management and power support restoration for devices in a wireless network |
| TWI392317B (en) * | 2008-05-27 | 2013-04-01 | Silver Spring Networks Inc | Multi-protocol network registration and address resolution |
| US8316136B2 (en) | 2009-05-22 | 2012-11-20 | Silver Spring Networks, Inc. | Multi-protocol network registration and address resolution |
| US7783764B2 (en) * | 2008-05-27 | 2010-08-24 | Silver Spring Networks, Inc. | Multi-protocol network registration and address resolution |
| WO2010022535A1 (en) | 2008-08-26 | 2010-03-04 | 上海贝尔股份有限公司 | Method and device for transferring packet in ipv6 access node |
| CA2734953A1 (en) | 2008-09-04 | 2010-03-11 | Trilliant Networks, Inc. | A system and method for implementing mesh network communications using a mesh network protocol |
| WO2010033244A1 (en) * | 2008-09-22 | 2010-03-25 | Silver Spring Networks, Inc. | Transparent routing in a power line carrier network |
| US9743337B2 (en) * | 2008-09-22 | 2017-08-22 | Silver Spring Networks, Inc. | Meshed networking of access points in a utility network |
| JP5651594B2 (en) * | 2008-10-01 | 2015-01-14 | シルバー スプリング ネットワークス インコーポレイテッドSilver Spring Networks, Inc. | Method and system for applying environmental incentives |
| US8782746B2 (en) * | 2008-10-17 | 2014-07-15 | Comcast Cable Communications, Llc | System and method for supporting multiple identities for a secure identity device |
| CN101447935B (en) * | 2008-11-20 | 2011-12-21 | 华为技术有限公司 | Data packet transmitting method, system and equipment thereof |
| US8289182B2 (en) | 2008-11-21 | 2012-10-16 | Trilliant Networks, Inc. | Methods and systems for virtual energy management display |
| CN102265562B (en) * | 2008-12-25 | 2014-11-26 | 三菱电机株式会社 | Communication management device, communication system, and data communication method |
| US9014832B2 (en) * | 2009-02-02 | 2015-04-21 | Eloy Technology, Llc | Augmenting media content in a media sharing group |
| US8781435B2 (en) | 2009-02-13 | 2014-07-15 | Qualcomm Incorporated | High rate packet data (HRPD) idle state handout from femto access point to macro access network |
| US8874693B2 (en) * | 2009-02-20 | 2014-10-28 | Microsoft Corporation | Service access using a service address |
| EP2224217B1 (en) * | 2009-02-27 | 2014-06-11 | Technische Universität Dresden | Device and method for a resource-generating and/or consuming device communicating with a central control unit |
| CA2753074A1 (en) | 2009-03-11 | 2010-09-16 | Trilliant Networks, Inc. | Process, device and system for mapping transformers to meters and locating non-technical line losses |
| EP2244066A1 (en) * | 2009-04-21 | 2010-10-27 | Alcatel Lucent | Method and system for transferring information, as well as a master device, a slave device and a central instance for such system |
| US8719337B1 (en) * | 2009-04-27 | 2014-05-06 | Junaid Islam | IPv6 to web architecture |
| WO2010131149A1 (en) * | 2009-05-13 | 2010-11-18 | Koninklijke Philips Electronics N.V. | A method for assigning a network address for communicating in a segmented network |
| TWI491300B (en) * | 2009-06-10 | 2015-07-01 | 皇家飛利浦電子股份有限公司 | Wireless network system, joining device for use in a wireless network system, method of commissioning awireless network system and computer program product |
| US8730057B2 (en) * | 2009-08-17 | 2014-05-20 | Tendril Networks, Inc. | AMR meter to ZigBee communications bridge |
| US8516141B2 (en) * | 2009-09-01 | 2013-08-20 | Konica Minolta Laboratory U.S.A., Inc. | Method and system for modifying and/or changing a MAC ID utilizing an IPv6 network connection |
| US8037343B2 (en) * | 2009-09-15 | 2011-10-11 | Verizon Patent And Licensing, Inc. | Trap-based configuration audit |
| CN102045244A (en) * | 2009-10-10 | 2011-05-04 | 中兴通讯股份有限公司 | IPV4 (Internet Protocol Version 4) network as well as implementation method and system for intercommunicating with new network |
| US8958400B2 (en) | 2009-10-16 | 2015-02-17 | Silver Spring Networks, Inc. | Wireless device with opportunistic band access |
| US11164672B2 (en) * | 2010-01-22 | 2021-11-02 | Deka Products Limited Partnership | System and apparatus for electronic patient care |
| US8605609B2 (en) * | 2010-03-11 | 2013-12-10 | Silver Spring Networks, Inc. | Simulation of multiple nodes in an internetwork |
| US20130024306A1 (en) * | 2010-04-07 | 2013-01-24 | Silver Spring Networks, Inc. | Systems and methods for charging electric vehicles |
| US9729516B2 (en) * | 2010-04-09 | 2017-08-08 | Gemalto Sa | Method of machine-to-machine communication |
| CN101830421A (en) * | 2010-04-26 | 2010-09-15 | 万迅电脑软件(深圳)有限公司 | Wireless oiling and gassing method and system based on RFID and GPS technologies |
| DE102010026174A1 (en) * | 2010-07-06 | 2012-01-12 | Siemens Aktiengesellschaft | System and method for storing network parameter data of a power supply network |
| KR101678494B1 (en) * | 2010-08-16 | 2016-11-22 | 삼성전자주식회사 | Method for Setupping Protection and Device for implementing thereof |
| US9084120B2 (en) | 2010-08-27 | 2015-07-14 | Trilliant Networks Inc. | System and method for interference free operation of co-located transceivers |
| CA2813534A1 (en) | 2010-09-13 | 2012-03-22 | Trilliant Networks, Inc. | Process for detecting energy theft |
| TWI450614B (en) * | 2010-10-27 | 2014-08-21 | Hon Hai Prec Ind Co Ltd | Femtocell and internet accessing method |
| EP2641137A2 (en) | 2010-11-15 | 2013-09-25 | Trilliant Holdings, Inc. | System and method for securely communicating across multiple networks using a single radio |
| WO2012097204A1 (en) | 2011-01-14 | 2012-07-19 | Trilliant Holdings, Inc. | Process, device and system for volt/var optimization |
| US8970394B2 (en) | 2011-01-25 | 2015-03-03 | Trilliant Holdings Inc. | Aggregated real-time power outages/restoration reporting (RTPOR) in a secure mesh network |
| EP3429163B1 (en) | 2011-02-10 | 2020-08-19 | Trilliant Holdings, Inc. | Device and method for facilitating secure communications over a cellular network |
| US9041349B2 (en) | 2011-03-08 | 2015-05-26 | Trilliant Networks, Inc. | System and method for managing load distribution across a power grid |
| US20120268291A1 (en) * | 2011-04-19 | 2012-10-25 | John Christopher Boot | Systems and method for transmitting data in an advanced metering infrastructure |
| US9936473B2 (en) * | 2011-05-03 | 2018-04-03 | Nokia Technologies Oy | Method and apparatus for managing radio interfaces |
| US20130002449A1 (en) * | 2011-06-28 | 2013-01-03 | General Electric Company | Systems, methods, and apparatus for utility meter configuration |
| US20130028306A1 (en) | 2011-07-26 | 2013-01-31 | Cristina Seibert | Systems and methods for multimode signal acquisition |
| US9001787B1 (en) | 2011-09-20 | 2015-04-07 | Trilliant Networks Inc. | System and method for implementing handover of a hybrid communications module |
| KR20130033869A (en) * | 2011-09-27 | 2013-04-04 | 삼성전기주식회사 | Method and system for association between controller and device in home network |
| CN103037459B (en) * | 2011-09-29 | 2015-08-19 | 中国移动通信集团江苏有限公司 | Method of data synchronization and device |
| US9065869B2 (en) | 2011-10-08 | 2015-06-23 | Broadcom Corporation | Social network device memberships and applications |
| US20130091212A1 (en) * | 2011-10-08 | 2013-04-11 | Broadcom Corporation | Social network device communication resource allocation |
| TWI454093B (en) * | 2011-10-18 | 2014-09-21 | Av Tech Corp | Network electronic device installation method and network electronic device installation setting system thereof |
| US9967235B2 (en) | 2011-11-14 | 2018-05-08 | Florida Power & Light Company | Systems and methods for managing advanced metering infrastructure |
| US9084091B2 (en) * | 2011-11-17 | 2015-07-14 | Silver Spring Networks, Inc. | Registration and data exchange using proxy gateway |
| US8887238B2 (en) * | 2011-12-07 | 2014-11-11 | Time Warner Cable Enterprises Llc | Mechanism for establishing reputation in a network environment |
| US8914170B2 (en) * | 2011-12-07 | 2014-12-16 | General Electric Company | System and method for communicating data in a vehicle system |
| CN102523272B (en) * | 2011-12-08 | 2014-07-16 | 北京航空航天大学 | Electric energy measuring, controlling and protecting system |
| KR101907933B1 (en) * | 2011-12-23 | 2018-10-17 | 한국전자통신연구원 | User-centric virtual network and building method thereof |
| US20130184878A1 (en) * | 2012-01-13 | 2013-07-18 | General Electric Company | Systems and Methods for Tracing Nodes in an Electrical Network |
| CN103327129B (en) * | 2012-03-21 | 2018-10-26 | 深圳市共进电子股份有限公司 | For the domain name analytic method of more WAN mouthfuls of gateway devices |
| US8902901B2 (en) * | 2012-03-23 | 2014-12-02 | Itron, Inc. | Communication packet conversion |
| CN102761440B (en) * | 2012-06-28 | 2015-01-28 | 华为终端有限公司 | Method for establishing channel for managing IPv4 terminal and network gateway |
| US10861112B2 (en) | 2012-07-31 | 2020-12-08 | Causam Energy, Inc. | Systems and methods for advanced energy settlements, network-based messaging, and applications supporting the same on a blockchain platform |
| US8983669B2 (en) | 2012-07-31 | 2015-03-17 | Causam Energy, Inc. | System, method, and data packets for messaging for electric power grid elements over a secure internet protocol network |
| US9513648B2 (en) | 2012-07-31 | 2016-12-06 | Causam Energy, Inc. | System, method, and apparatus for electric power grid and network management of grid elements |
| US10475138B2 (en) | 2015-09-23 | 2019-11-12 | Causam Energy, Inc. | Systems and methods for advanced energy network |
| US8849715B2 (en) | 2012-10-24 | 2014-09-30 | Causam Energy, Inc. | System, method, and apparatus for settlement for participation in an electric power grid |
| TWI477128B (en) * | 2012-09-10 | 2015-03-11 | Chunghwa Telecom Co Ltd | A system and method for automatically configuring different IPv6 network header codes and network traffic classes |
| TWI469605B (en) * | 2012-09-18 | 2015-01-11 | Hon Hai Prec Ind Co Ltd | Network address translation system and method |
| EP2725763B1 (en) * | 2012-10-24 | 2015-01-07 | Alcatel Lucent | Apparatus, method and computer program for relaying payload data between two network nodes |
| US9472093B2 (en) * | 2012-12-17 | 2016-10-18 | Itron, Inc. | Near field communications for utility meters |
| KR101548948B1 (en) * | 2013-03-08 | 2015-09-03 | 주식회사 케이티 | Method and system for providing electric vehicle in charging with contents |
| US9285790B2 (en) | 2013-03-15 | 2016-03-15 | Hayward Industries, Inc. | Modular pool/spa control system |
| US9182275B2 (en) * | 2013-04-01 | 2015-11-10 | Silver Spring Networks | Distributing light intensity readings in a wireless mesh |
| US10097503B2 (en) | 2013-09-27 | 2018-10-09 | Fastly, Inc. | Content node network address selection for content delivery |
| KR101539331B1 (en) * | 2014-02-04 | 2015-07-28 | 고려대학교 산학협력단 | Parking guidance and reservation system using in-vehicle navigator with bidirectional communication and method thereof |
| US9794355B2 (en) | 2014-04-08 | 2017-10-17 | Samsung Electronics Co., Ltd. | Systems and methods for adaptive notification networks |
| US9794218B2 (en) * | 2014-04-29 | 2017-10-17 | Trustiosity, Llc | Persistent network addressing system and method |
| EP3183868A1 (en) * | 2014-08-21 | 2017-06-28 | Nokia Technologies Oy | Ipv4 communications using 6lowpan header compression mechanisms |
| US20160135235A1 (en) * | 2014-11-06 | 2016-05-12 | David R. Elmaleh | System and method for information sharing based on wireless association |
| CN104468864B (en) * | 2014-12-24 | 2018-05-01 | 国家电网公司 | A kind of method for network address translation of IPv6-in-IPv4 tunnel packets |
| EP3059930B1 (en) * | 2015-02-18 | 2021-01-06 | Siemens Aktiengesellschaft | Method for configuring a communication device of an industrial automation system and communication device |
| EP3062490B1 (en) * | 2015-02-27 | 2018-07-18 | Siemens Aktiengesellschaft | Method for transmitting data within an industrial automation system and communication device |
| EP4293979A3 (en) * | 2015-04-07 | 2024-04-17 | Umbra Technologies Ltd. | System and method for virtual interfaces and advanced smart routing in a global virtual network |
| CN106302845B (en) * | 2015-05-29 | 2020-07-17 | 西安中兴新软件有限责任公司 | Domain name system address configuration method and device of data channel product |
| CN106340176B (en) * | 2015-07-09 | 2020-01-17 | 中国电力科学研究院 | Information sharing method of smart meter, smart meter and acquisition router |
| CN105162728B (en) | 2015-07-31 | 2018-07-31 | 小米科技有限责任公司 | Method for network access, equipment and system |
| US9678911B2 (en) * | 2015-11-12 | 2017-06-13 | Aupera Technologies, Inc. | System for distributed computing and storage |
| JP6580462B2 (en) * | 2015-11-02 | 2019-09-25 | PicoCELA株式会社 | Network system, node, frame communication method and program |
| US10250452B2 (en) | 2015-12-14 | 2019-04-02 | Microsoft Technology Licensing, Llc | Packaging tool for first and third party component deployment |
| US10356038B2 (en) * | 2015-12-14 | 2019-07-16 | Microsoft Technology Licensing, Llc | Shared multi-tenant domain name system (DNS) server for virtual networks |
| US10666517B2 (en) | 2015-12-15 | 2020-05-26 | Microsoft Technology Licensing, Llc | End-to-end automated servicing model for cloud computing platforms |
| US10272014B2 (en) | 2016-01-22 | 2019-04-30 | Hayward Industries, Inc. | Systems and methods for providing network connectivity and remote monitoring, optimization, and control of pool/spa equipment |
| US11720085B2 (en) | 2016-01-22 | 2023-08-08 | Hayward Industries, Inc. | Systems and methods for providing network connectivity and remote monitoring, optimization, and control of pool/spa equipment |
| US20190297655A1 (en) * | 2016-05-18 | 2019-09-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Local break-out in mobile ip networks |
| CN106016385A (en) * | 2016-05-26 | 2016-10-12 | 东莞市沁鑫热能科技有限公司 | An integrated control system for induction cooker based on Internet of Things |
| TWI628934B (en) * | 2016-11-11 | 2018-07-01 | 中華電信股份有限公司 | IPv6 interconnection control system and method thereof |
| CN108171957B (en) * | 2016-12-07 | 2021-11-30 | 中兴通讯股份有限公司 | Meter reading method, device and system and communication gateway |
| US10749692B2 (en) | 2017-05-05 | 2020-08-18 | Honeywell International Inc. | Automated certificate enrollment for devices in industrial control systems or other systems |
| CN108777849B (en) * | 2018-04-12 | 2020-06-19 | 北京邮电大学 | Indoor mirror virtual relay layout method and device |
| US11936629B2 (en) * | 2018-06-21 | 2024-03-19 | VMware LLC | System and method for creating a secure hybrid overlay network |
| US11290378B2 (en) * | 2018-08-21 | 2022-03-29 | Frontiir PTE Ltd | Network systems and architecture with multiple load balancers and network access controllers |
| US11555718B2 (en) * | 2019-01-18 | 2023-01-17 | Sensus Spectrum, Llc | Devices having communication circuitry decoupled from device circuitry and related meters and housings |
| US11245570B2 (en) * | 2019-03-01 | 2022-02-08 | Itron, Inc. | Remote data publishing |
| CN112258827B (en) * | 2020-10-16 | 2021-08-24 | 杭州百富电子技术有限公司 | Ammeter box convenient for meter reading and meter reading method |
| WO2022231747A1 (en) * | 2021-04-29 | 2022-11-03 | Arris Enterprises Llc | Enhanced docsis packet classification for tunneled traffic having ipv4 and ipv6 rules mixed in a single upstream (us) and/or downstream (ds) traffic classifier |
| US20240236717A9 (en) * | 2022-10-20 | 2024-07-11 | Verizon Patent And Licensing Inc. | Systems and methods for detecting fixed wireless access customer premise equipment coverage during a planned network outage |
Family Cites Families (72)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5425028A (en) * | 1992-07-16 | 1995-06-13 | International Business Machines Corporation | Protocol selection and address resolution for programs running in heterogeneous networks |
| JP3097525B2 (en) * | 1995-11-10 | 2000-10-10 | 株式会社日立製作所 | Data transmission method for performing information filtering |
| US6701361B1 (en) * | 1996-08-22 | 2004-03-02 | Intermec Ip Corp. | Enhanced mobility and address resolution in a wireless premises based network |
| CA2213984A1 (en) * | 1996-08-22 | 1998-02-22 | Norand Corporation | Enhanced mobility and address resolution in a wireless premises based network |
| US6012088A (en) | 1996-12-10 | 2000-01-04 | International Business Machines Corporation | Automatic configuration for internet access device |
| US7046682B2 (en) * | 1997-02-12 | 2006-05-16 | Elster Electricity, Llc. | Network-enabled, extensible metering system |
| US6396839B1 (en) * | 1997-02-12 | 2002-05-28 | Abb Automation Inc. | Remote access to electronic meters using a TCP/IP protocol suite |
| US20060062192A1 (en) * | 1998-06-26 | 2006-03-23 | Payne William A Iii | Method for wireless access system supporting multiple frame types |
| US6272540B1 (en) * | 1998-12-31 | 2001-08-07 | Intel Corporation | Arrangement and method for providing flexible management of a network |
| US6502158B1 (en) * | 1999-04-23 | 2002-12-31 | Sony Corporation | Method and system for address spaces |
| US6816706B1 (en) * | 1999-09-08 | 2004-11-09 | Qwest Communications International, Inc. | Wireless communication access point |
| EP1087575A1 (en) * | 1999-09-24 | 2001-03-28 | BRITISH TELECOMMUNICATIONS public limited company | Packet network interfacing |
| US6768743B1 (en) * | 1999-10-26 | 2004-07-27 | 3Com Corporation | Method and system for address server redirection for multiple address networks |
| US6885309B1 (en) | 2000-06-01 | 2005-04-26 | Cellnet Innovations, Inc. | Meter to internet pathway |
| US6836737B2 (en) * | 2000-08-09 | 2004-12-28 | Statsignal Systems, Inc. | Systems and methods for providing remote monitoring of consumption for a utility meter |
| AUPQ963100A0 (en) * | 2000-08-24 | 2000-09-14 | Tele-Ip Limited | Means for interfacing non-standard devices under snmp |
| JP2002084561A (en) * | 2000-09-06 | 2002-03-22 | Nec Corp | Connection system, connection method therefor, and recording medium in which connection program is recorded |
| JP2002095072A (en) * | 2000-09-14 | 2002-03-29 | Hitachi Ltd | Device control method |
| US7280540B2 (en) * | 2001-01-09 | 2007-10-09 | Stonesoft Oy | Processing of data packets within a network element cluster |
| WO2002073933A1 (en) * | 2001-03-08 | 2002-09-19 | British Telecommunications Public Limited Company | Address translator |
| US6546469B2 (en) * | 2001-03-12 | 2003-04-08 | International Business Machines Corporation | Multiprocessor system snoop scheduling mechanism for limited bandwidth snoopers |
| US20030050070A1 (en) * | 2001-03-14 | 2003-03-13 | Alex Mashinsky | Method and system for dynamic spectrum allocation and management |
| US7061924B1 (en) * | 2001-05-24 | 2006-06-13 | Intel Corporation | Methods and apparatus for remote metering |
| US7339895B2 (en) | 2001-08-21 | 2008-03-04 | Hitachi, Ltd. | Gateway device and control method for communication with IP and IPV6 protocols |
| JP2003224874A (en) * | 2002-01-29 | 2003-08-08 | Fujitsu Ltd | Mobile communication network router and mobile communication terminal |
| KR20040075962A (en) * | 2002-01-29 | 2004-08-30 | 코닌클리즈케 필립스 일렉트로닉스 엔.브이. | Internet protocol based wireless communication arrangements |
| US20030177174A1 (en) * | 2002-03-14 | 2003-09-18 | International Business Machines Corporation | Target resource allocation in an iSCSI network environment |
| US7284068B1 (en) * | 2002-06-20 | 2007-10-16 | Cisco Technology, Inc. | Technique for providing multi-homing capability in data networks |
| US20030236914A1 (en) * | 2002-06-25 | 2003-12-25 | Intel Corporation | Connection of next generation mobile nodes across previous generation networks to next generation networks |
| CA2393547A1 (en) * | 2002-07-15 | 2004-01-15 | Hexago Inc. | Method and apparatus for connecting ipv6 devices through an ipv4 network using a tunneling protocol |
| JP2004068700A (en) * | 2002-08-06 | 2004-03-04 | Toyota Motor Corp | Exhaust gas purification method |
| EP1420559A1 (en) * | 2002-11-13 | 2004-05-19 | Thomson Licensing S.A. | Method and device for supporting a 6to4 tunneling protocol across a network address translation mechanism |
| CN102611596B (en) * | 2002-11-29 | 2015-02-11 | 飞比特网络股份有限公司 | Networked appliance |
| US20040148428A1 (en) * | 2003-01-28 | 2004-07-29 | George Tsirtsis | Methods and apparatus for supporting an internet protocol (IP) version independent mobility management system |
| US7031328B2 (en) * | 2003-03-10 | 2006-04-18 | Cisco Technology, Inc. | Arrangement for traversing an IPv4 network by IPv6 mobile routers |
| JP4025674B2 (en) * | 2003-04-01 | 2007-12-26 | 富士通株式会社 | Detour communication route design method |
| US7490152B2 (en) * | 2003-04-11 | 2009-02-10 | Alcatel-Lucent Usa Inc. | Version caching mechanism |
| US20040210524A1 (en) * | 2003-04-15 | 2004-10-21 | David Benenati | Methods for unified billing across independent networks |
| KR100757860B1 (en) * | 2003-05-29 | 2007-09-11 | 삼성전자주식회사 | Complex wireless service device using wired and wireless communication system |
| US20040254999A1 (en) * | 2003-06-13 | 2004-12-16 | Bellsouth Intellectual Property Corporation | System for providing content to multiple users |
| WO2005008994A1 (en) | 2003-07-23 | 2005-01-27 | Samsung Electronics Co., Ltd. | Method and system for generating ip addresses of access terminals and transmitting messages for generation of ip addresses in an ip system |
| US20050055432A1 (en) | 2003-09-08 | 2005-03-10 | Smart Synch, Inc. | Systems and methods for remote power management using 802.11 wireless protocols |
| CN100579089C (en) * | 2003-09-26 | 2010-01-06 | 无极公司 | Device control system, method and apparatus |
| US7630323B2 (en) * | 2004-03-11 | 2009-12-08 | Symbol Technologies, Inc. | Self-configuring wireless personal area network |
| US20050251403A1 (en) * | 2004-05-10 | 2005-11-10 | Elster Electricity, Llc. | Mesh AMR network interconnecting to TCP/IP wireless mesh network |
| RU2247669C1 (en) * | 2004-05-27 | 2005-03-10 | Общество с ограниченной ответственностью "АЛЬТОНИКА" (ООО "АЛЬТОНИКА") | Vehicle data control system |
| KR100645440B1 (en) | 2004-06-14 | 2006-11-14 | 삼성전자주식회사 | ZigBee network device for determining network parameter separately and assigning address, and address assigning method thereof |
| WO2006004112A1 (en) * | 2004-07-05 | 2006-01-12 | Ip Power Systems Corp. | Power consumption measuring device and power control system |
| US11144995B2 (en) * | 2004-07-19 | 2021-10-12 | Fmh Ag Risk Insurance Company | Insurance product associated with risk management on the application of crop inputs |
| US7840217B2 (en) * | 2004-07-23 | 2010-11-23 | Cisco Technology, Inc. | Methods and apparatus for achieving route optimization and location privacy in an IPV6 network |
| US20060045105A1 (en) | 2004-08-25 | 2006-03-02 | Dobosz Paul J | System and method for using a utility meter |
| US8026830B2 (en) * | 2004-09-02 | 2011-09-27 | Boh Technology, L.L.C. | Methods and systems for meter reading and high speed data transfer |
| US20060083262A1 (en) * | 2004-10-14 | 2006-04-20 | Utstarcom, Inc. | Method and apparatus to facilitate use of a pool of internet protocol 6to4 address prefixes |
| WO2006046261A1 (en) * | 2004-10-29 | 2006-05-04 | Telecom Italia S.P.A. | Method for controlling routing operations in a network, related network and computer program product thereof |
| US7437470B2 (en) * | 2004-11-18 | 2008-10-14 | International Business Machines Corporation | Tunneling IPv6 packets |
| KR100738524B1 (en) * | 2004-11-24 | 2007-07-11 | 삼성전자주식회사 | Tunneling method and apparatus for multicasting |
| TWI267270B (en) | 2004-11-26 | 2006-11-21 | Univ Nat Central | Seamless multimedia stream system applying a dynamic multicast technique |
| JP4330520B2 (en) * | 2004-12-08 | 2009-09-16 | 富士通株式会社 | Communication device |
| KR100716163B1 (en) * | 2004-12-23 | 2007-05-10 | 삼성전자주식회사 | Tunneling method and apparatus for multicasting between IPv4 network and IPv6 network |
| KR20070106971A (en) * | 2005-01-11 | 2007-11-06 | 텔코디아 테크놀로지스, 인코포레이티드 | How to establish and configure an ad hoc wireless peer-to-peer network |
| US7363137B2 (en) * | 2005-02-03 | 2008-04-22 | Lincoln Global, Inc. | Construction equipment discovery on a network |
| JP4285420B2 (en) * | 2005-02-22 | 2009-06-24 | 株式会社日立製作所 | Sensor network management system |
| US7440405B2 (en) * | 2005-03-11 | 2008-10-21 | Reti Corporation | Apparatus and method for packet forwarding with quality of service and rate control |
| CN1842051A (en) * | 2005-03-30 | 2006-10-04 | 国际商业机器公司 | Flow equalization apparatus and process and network forwarding apparatus and method using same |
| EP3713264B1 (en) * | 2005-03-31 | 2025-08-20 | Sun Patent Trust | Communication control method, communication node, and mobile node |
| KR101265954B1 (en) * | 2005-07-11 | 2013-05-23 | 더 트러스티이스 오브 콜롬비아 유니버시티 인 더 시티 오브 뉴욕 | Method and apparatus of performing tunnel signaling over ip tunneling path |
| JP4190521B2 (en) * | 2005-07-14 | 2008-12-03 | 株式会社東芝 | Multiprotocol address registration method, multiprotocol address registration system, multiprotocol address registration server, and multiprotocol address communication terminal |
| US8477731B2 (en) * | 2005-07-25 | 2013-07-02 | Qualcomm Incorporated | Method and apparatus for locating a wireless local area network in a wide area network |
| RU52504U1 (en) * | 2005-08-30 | 2006-03-27 | Закрытое Акционерное Общество Российская Приборостроительная Корпорация "Системы Управления" | INTEGRATED SYSTEM OF INDIVIDUAL ACCOUNTING AND REGULATION OF ENERGY RESOURCES CONSUMPTION IN HOUSING AND COMMUNAL SERVICES |
| US7613914B2 (en) * | 2006-07-27 | 2009-11-03 | Intel Corporation | Wireless user device having integrated hotspotter technology |
| US8364846B2 (en) * | 2007-02-02 | 2013-01-29 | Silver Spring Networks, Inc. | Method and system of providing IP-based packet communications with in-premisis devices in a utility network |
| US7769888B2 (en) * | 2007-06-15 | 2010-08-03 | Silver Spring Networks, Inc. | Method and system for providing network and routing protocols for utility services |
-
2007
- 2007-05-24 US US11/807,176 patent/US8364846B2/en active Active
- 2007-05-24 US US11/807,173 patent/US8953610B2/en active Active
- 2007-05-24 US US11/807,177 patent/US8489716B2/en active Active
- 2007-05-24 US US11/807,185 patent/US8429295B2/en active Active
- 2007-05-24 US US11/807,184 patent/US20080186203A1/en not_active Abandoned
-
2008
- 2008-01-29 WO PCT/US2008/001110 patent/WO2008097447A1/en not_active Ceased
- 2008-01-29 WO PCT/US2008/001109 patent/WO2008097446A1/en not_active Ceased
- 2008-01-30 CA CA2676656A patent/CA2676656C/en active Active
- 2008-01-30 AU AU2008214466A patent/AU2008214466B2/en active Active
- 2008-01-30 JP JP2009548284A patent/JP5329433B2/en active Active
- 2008-01-30 DK DK08713336.9T patent/DK2127226T3/en active
- 2008-01-30 WO PCT/US2008/001166 patent/WO2008097454A2/en not_active Ceased
- 2008-01-30 MY MYPI20093179 patent/MY151825A/en unknown
- 2008-01-30 RO ROA200900608A patent/RO126258A2/en unknown
- 2008-01-30 CN CN2008800090710A patent/CN101641908B/en active Active
- 2008-01-30 CN CN201310556691.9A patent/CN103701944B/en active Active
- 2008-01-30 EP EP08713336.9A patent/EP2127226B1/en active Active
- 2008-01-30 RU RU2009132956/07A patent/RU2479932C2/en not_active IP Right Cessation
- 2008-01-30 WO PCT/US2008/001165 patent/WO2008097453A1/en not_active Ceased
- 2008-01-30 BR BRPI0806837A patent/BRPI0806837A2/en not_active Application Discontinuation
- 2008-01-30 KR KR1020097018182A patent/KR101434705B1/en active Active
- 2008-01-30 MX MX2009008085A patent/MX2009008085A/en active IP Right Grant
- 2008-01-31 TW TW097103661A patent/TWI369101B/en active
- 2008-01-31 WO PCT/US2008/001262 patent/WO2008097457A1/en not_active Ceased
- 2008-01-31 TW TW097103660A patent/TWI372546B/en active
- 2008-02-01 TW TW097103900A patent/TWI376132B/en active
- 2008-02-01 TW TW097103901A patent/TWI369111B/en active
- 2008-02-01 TW TW097103898A patent/TWI427991B/en active
-
2013
- 2013-03-15 US US13/834,727 patent/US8892774B2/en active Active
- 2013-07-02 US US13/933,943 patent/US9094458B2/en active Active
-
2014
- 2014-10-20 US US14/518,475 patent/US9178716B2/en active Active
-
2015
- 2015-01-20 US US14/600,427 patent/US9288181B2/en active Active
-
2016
- 2016-02-10 US US15/040,422 patent/US20160165564A1/en not_active Abandoned
Also Published As
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TW200841668A (en) | Method and system of providing network addresses to in-premise devices in a utility network | |
| CN110140415A (en) | Use the WLAN connection of wireless device | |
| HK1139530B (en) | Method and system of providing ip-based packet communications in a utility network |