MXPA06008348A - Communications system with context based addressing - Google Patents

Abstract

A communications system for a network of stations, is provided where stations identify themselves upon being informed of the desires of an inquisitor station. Additionally, techniques for"plug and play", self-healing and homogenizing the heterogeneous parts of a network, are provided.

Description

Published: For two-letter codes and other abbreviations, referto the "Guid¬ - with intemational search report ance Notes on Codes and Abbreviations "appearing at the beginning - before the expiration of the time limit for amending the no regular issue of the PCT Gazette.

SYSTEM. OF COMMUNICATIONS WITH DIRECTION BASED ON CONTEXT FIELD OF THE INVENTION This invention relates to communication systems for telemetry and related applications. BACKGROUND OF THE INVENTION For a message issuer in a network, the methods to identify and address that operate in a context devoid of emptiness have limitations. A method to identify and direct is based solely on "where" something exists (physically or logically), either by itself or relatively (in a logical or physical relationship with others), it is limited. A conventional addressing scheme where the network elements are addressed only by "where" they are, requires that the sender decides which elements of the network he wishes to contact and know their locations, all before sending a message to it. Having decided "where" to send the message is ineffective, especially if the sender does not know what is happening "out there" on a real-time basis in the operating environment and must first waste time and effort to find before sending the message. In addition, the addressing scheme that assigns (even temporarily) to a network element an address REF: 174413 One-dimensional for only one context, it is not powerful. A network in which the network element is assigned to fixed addresses (for example MAC address or even a static IP address temporarily under the TCP / IP or DHCP dynamic guest configuration protocol) and has no other addresses or means by which it can to be addressed, has limitations. Static schemes involve a rigid set of addressable elements which in turn imply that the communications system does not change over time and has no responsiveness to the operating environment that typically changes. As a result, conventional addressing schemes have become, in the best of cases, a general first-order approximation of a communications system that interacts with its operating environment. A realistic communication system is dynamic. It changes or is susceptible to change over time, often with response to stimuli (typically, but not exclusively from the operating environment) and sometimes needs to change itself (ie periodically or in case of maintenance or repair). - driven by some event). Consequently, the more variables (and resulting dimensions) of a network element are available to the sender to be considered when identifying the relevant elements (and not only in "where" the "element" is located), it is the potential and more "rich" identities will become more "rich" will be the communications network in its entirety. With such enrichment the concomitant efficiencies for desired complex actions (in terms of speed, granularity, specificity, for example) in the operating environment. SUMMARY OF THE INVENTION A method is provided for sending useful information from an interrogation station (inquirent) to a network of interrogated stations, comprising the steps of: (a) attributing to each interrogated station a set of contextual variables and their values contextual to them, to form what is called the contextual attributes of the interrogated station; (b) conforming the identity sought from a station interrogated to receive useful information, the identity sought is a function of the appropriate values for the contextual variables; (c) an interrogation station sends to all interrogated stations a CAS message that has: (i) useful information, and (ii) the identity sought; and (d) each station interrogated determines, upon receipt of the CAS message, if it has that identity sought, based on its contextual attributes, and on this basis it processes the useful information if it has said identity. A method is provided to obtain a desired complex action on an operating environment, which comprises: (a) establishing a communications network that has a base station and a plurality of endpoints (endpoints), each endpoint couples an interaction medium to interact with the operating environment and each endpoint has a medium of identity creation to create your identity; (b) develop a desired complex action in terms of individual actions by relevant means of interaction; (c) send to all the endpoints a message that is an expression of the desired complex action so that the identities of the relevant interaction means are derived (i) by each means of identity creation of the endpoints (ii) from the desired complex action expressed. BRIEF DESCRIPTION OF THE FIGURES The understanding of this invention can be obtained when considering the description of the preferred embodiment together with the following figures, in which: Figure 1 is an idealized traditional message format; Figure 2 is an idealized contextual addressing scheme message format; Figure 3 is an illustration of several networks of contextual addressing schemes; Figure 4 is an illustration of the contextual addressing scheme juxtaposed against the OSI; Figure 5 is an illustration of the base station-driven version of a "plug and play" procedure; and Figure 6 is an illustration of the endpoint driven version of the "plug and play" procedure. DETAILED DESCRIPTION OF THE INVENTION Before explaining the preferred modality (wireless electrical utility telemetry), some terminological guides and definitions are introduced for ease and economy of expression and comprehension, a general scheme is outlined where the role of the schemes is indicated of addressing, conceptual introductions are made for the user in the concepts of the invention, all with allusions to aspects of the preferred modality. The term "exemplary" herein refers to the provision of an example for illustrative purposes (as in "for example", ... ") and has no connotations of any notion indicating that it is" best "in any absolute sense and it can be conquered by the term "exemplary" because, what is "better" depends on a particular context.The present analogies are suggested from non-information technologies (for example, personnel, companies, of society and biomedical) solely to facilitate the perception of the concepts of the invention and a precise congruence with inventions must not be sought. As a first analogy, medical researchers ask "in what way (how well) does the human body interact with its environment?" If the mind develops desire, "if the temperature becomes too hot, get out now!" How (how well) is the realization of this desire accomplished? In what way can the mind better concatenate the senses and extremities to interact with the environment? For this invention, at the modalities level (preferred or otherwise), an analogous example may have the useful question "in what way (how well) the next wish is carried out" if the energy grid is now pulling too much energy, then they should be discontinued immediately certain seasons "? In what way can this desire be realized in the best way?" At a high conception level, a supersystem or a complex has: (I) a system of instructions and control (which includes a communications subsystem) that couples (II) interaction equipment that interacts with the operating environment. The operating environment is the dynamic matrix or the combination of physical conditions in which the supersystem or complex operates; and for the preferred modality is the electric power grid that operates in real time. An interaction equipment unit (an "interaction module" in the preferred embodiment) has and interacts with the operating environment by: (1) a sensor (which converts a physical property of the operating environment into electrical signals usable by an intelligence in a previous phase) or (2) an effector (which converts the electrical signals of the intelligence in a previous phase to a corresponding physical action in the operating environment, that is, that affects the operating environment). In a preferred embodiment, a typical sensor-interaction module is the combination of a conventional Watts / hour meter (for example General Electric I70S1) coupled with a conventional electromechanical-optical-electric converter (for example, US Patent # 5,874,732 and the technique referred to in it or the commercially available It'ron 40ER-1). Said combination provides electrical signals indicative of the consumption of electricity in a quantified energy line. In the preferred embodiment, a typical effector-interaction module is a remote disconnect switch which, based on the instructions, ends the supply of electricity in the power line to which it is attached. For economy of expression in the present, the terms (and the content of) "system of instructions and control "and" communications subsystem "are reduced and collectively referred to as" communications system ", with little loss of appreciable content for this invention.The communications system has: (1) a communications network that has (in the mode preferred): (a) a central intelligence, (b) a plurality of remote endpoints, and (c) communication channels between them, and (2) an addressing scheme by means of which messages are routed within the network Through the end points, the communication system couples the interconnection modules that interact with the operating environment, in this way, the endpoints represent (for the central intelligence) the "end" of the communication trajectories. otherwise, a supersystem or a complex has (with the preferred mode implementations "introduced in a parenthetical fashion"): (I) a communications system that has: (1) a network of communications that has: (a) a central intelligence < (base station >, (b) a plurality of remote endpoints < LAN devices > and (c) communication channels between them < communication representatives including WAN &LAN devices > and (2) a routing scheme < traditional &contextual addressing > by which messages are routed within the network, where each endpoint couples (II) its interaction equipment < interaction module > which interacts with the operating environment. The base station, the WAN and LAN devices are collectively the communications network devices or "network devices". In general, a communication channel includes all the communications infrastructure and means that are required to send / receive a message, excluding, but in accordance with, the applicable addressing scheme. In a preferred embodiment implementation, a channel includes physical elements (hardware) / programs (software) / firmware (firmware) such as transmitters, receivers, encoders / decoders and the like, and communication protocols that are necessary for the communication methods used. , exclusive of the addressing scheme. A part of the communication channel in the preferred embodiment is a "communication representative", which in the present is any functionality that serves to "lengthen" the communication path for a message without altering its substantive content. A transparent representative is typically a repeater (sometimes reinforcing or amplifying the signal or, in the case of a digital signal, which regenerates the signal, all to reduce errors due to deterioration with respect to distance). A non-transparent representative provides certain additional services (for example, packaging, a bridge or router for packaged messages, hidden storage, protocol conversion) but still retains the basic function of "lengthening" the communication path (for example by converting the message with a protocol that is more robust to the operating environment (for example a noisy RF) without altering the substantive content of the message) . In the present, the term "representative" includes the transparent and non-transparent types. In the preferred embodiment, a WAN device is an exemplary communication representative between the base station and the endpoints of the network. In addition, a LAN device is an exemplary communication representative between a WAN device and the endpoints of the network. In the preferred embodiment, an LA device? it is an exemplary endpoint of the communications network. It is the LAN device that couples the interaction module (sensor / effector). The communication system couples sensors and effectors but does not include them (in the same way that the nervous system of the human body, in a common vernacular manner, is considered to include the eyes and hands). The term "desired complex action" in the present is the desired action of the supersystem or complex that is to be obtained by the effect (collective or cumulative) of the communications system acting through its endpoints (LAN devices), each point The end device (LAN device) couples (in a concerted or individual way) its interaction module (sensor / effector) that interacts with the operating environment.

An objective principle of this invention is for the base station to obtain a desired complex action by efficient coupling of the interaction modules to interact with the operating environment. The desired complex actions evidently depend on the business objectives, the operating environment, the costs in the market, etc. The desired complex exemplary actions for a company that supplies electricity of the preferred embodiment, are related to the administration of electric power emission. The measurement of the quality of the electrical energy, the administration of load and the automation of the distribution. Effective couplings (of the interaction modules to interact with the operating environment) are obtained through the use of the invention of the communication network and an address of the invention. In the present two types of network addressing are explained: a conventional conventional addressing scheme (upstream and downstream) or TAS and in contrast to this a new downstream addressing scheme which is based on the "context", the Contextual addressing scheme or CAS. In particular, the CAS helps to "search" the endpoints and their interaction modules that are relevant to the desired complex action. Also explained here is a new procedure that uses these two schemes of addressing. The TAS (and the procedures based on it) and the CAS (and the procedures based on it) each can be self-sustaining. But, according to the preferred embodiment, a network advantageously uses both TAS and CAS. As a matter of terminology, a complex action is "desired" (by the central intelligence, the base station) and the expression and obtaining of that desire is carried out by means of effective couplings of the interaction modules that interact with the operating environment. . Consequently: (1) the interaction modules and (2) their respective endpoints (LAN devices in the preferred mode) that include endpoint components and the related CAS concepts of identity and contextual address are all "searched" and are considers relevant for a desired complex action and are synonyms for the purpose mentioned before "search" - all included in the epithet "sought". In a network of base stations and remote elements (whether they are endpoints or intermediate points such as communication representatives, and whether they are configured as LAN, WAN, or a WAN / LAN hybrid), an address to the base station or an intermediate element is therefore "upstream" and the opposite direction is "downstream". These guidance terms (upstream and downstream) apply to: (1) the address proposal of a message (and any component or implementation thereof, for example a packet) and (2) the location of an element in the network (for example, another station or device in the preferred mode), in particular, and intelligence of general way (no matter how it is distributed) in relation to a particular network element (station or device). The aspects, components, concepts and the like that are derived from the contextual addressing scheme (or CAS) and the traditional addressing scheme (or TAS) are referred to in the present in a formative way from them (for example a TAS message, a traditionally addressed message, a traditional address, a TAS network, TAS station, CAS message, contextually addressed message, contextual address, CAS network, CAS station, etc.). A CAS network is the subset of the communications network whose elements are routed using the CAS, in which, the CAS interrogation station sends a CAS message to all of the interrogated CAS stations (since such terms are explained in the following , although in the preferred embodiment, the CAS interrogation station is always the base station); and a TAS network is the subset of communications network whose elements are addressed using a TAS in which a TAS station The source sends a TAS message to one or more destination TAS stations. In contrast to the operating environment of the supersystem or complex, the term "network environment" refers to the relationship of a CAS station with other stations CAS of the same CAS network or of a TAS station with other TAS stations of the TAS network, as the case may be. The TAS is the "default" addressing scheme (upstream and downstream) in the preferred mode (and is used in many procedures such as "plug and play", AMR and PQM information and others that are explained in the following ). The exception is those messages downstream from the base station that are contextually addressed. The OSI is a theoretical reference model (and not a definition of a standard) for the analysis of communications within a network. When TAS or CAS is explained, references to one or more layers of OSI are useful only for economy of explanatory expression and are made at the expense of loss of explanatory precision because the CAS does not elaborate a mapping on the reference model OSI in the conventional use of said model. In the preferred mode, all messages (downstream and upstream) (either traditionally addressed or contextually addressed) are packaged, although for ease of explanation in the present, a message in the present is of a length that generally takes the form of a package in the idealized formats of Figures 1-2. It is important not to limit any connotation or denomination of the term "package" in the present to the transport layer 4 OSI. Splitting a message into smaller units, and the related procedures, are the result of design and implementation selections that favor certain aspects of network operation over other aspects, for a particular network implementation. The selection of the term "package" in the present refers to a unit that differs from the term "message" only at its conceptual level (where "package" refers to an implementation of a "message" that is, in an OSI layer smaller in comparison to the one where the message is implemented). In other words, a "package" and a "message" are often used interchangeably except where an implementation distinction is usefully highlighted. When useful information, for example, is large, obvious implementation modifications are necessary (for example, the message can be packaged in several packages). In the preferred embodiment, the reception of all messages traditionally addressed (downstream and upstream) by the destination station (immediate or final) are recognized in a packet by a packet base at a source station, by any conventional methodology not explained in the present by economy of expression. When an acknowledgment is not received for a packet (for example after a pre-set number of failed retries or perhaps when a "negative acknowledgment" is received indicative of a received packet integrity failure), the source station considers that it has lost the message (and proceeds to handle it according to the "lost messages" explained later). Scheme of traditional addressing (or TAS). Traditional routing schemes assign to each station a unique address that is also static. Traditionally, an address is assigned to a station by a controller / network administrator, according to a preconceived addressing plan and retained by the station until it is changed by the controller / network administrator; or it is assigned when a station joins the network (according to a specific protocol procedure for that network) and is held while it is attached. Said address is used by the TAS source station to send a TAS message to the proposed TAS destination station. In a TAS network, a TAS station is addressable by its TAS address and therefore, by definition, can not have a "null" TAS address. Also, because a TAS, the address of a station corresponds Directly or indirectly to a physical location, a TAS address must be unique (since two different places in space can not be identified by the same identifier). The TAS network (and in particular, when a central intelligence or a distributed intelligence) know one or more addresses - by analogy, the "where" - of one or more destination stations to which you wish to send and use the knowledge of " where "for the shipment. In particular, in a TAS network of a base station that addresses addressable stations, the base station (or its communication representatives such as bridges, routers and the like, depending on the implementation) knows and uses the addresses of all addressable stations for send messages to them (where their knowledge of these addresses exists at least when they send messages from them and is typically maintained in a central database or in distributed tables). This aspect of "knowing and using" a traditional addressing scheme is going to contrast with the agnostic concept of a contextual addressing scheme that is explained in the following, which "does not know" (and "does not use" and therefore so much "it does not matter" in which way it is sent or arrives said message). Common example TAS networks include: a network whose elements each have a MAC address (which has a hierarchical format of <manufacturerx serial #>), either the network is wired or operates under a wireless protocol such as IEEE 802.11; a wired network where an element address is implicitly equivalent to the physical location of the element; and a network that operates in a hierarchical addressing scheme, the common examples of which are IP addresses, with decimal point classes. Another TAS network example (which is explained in the following as part of the preferred mode) assigns a unique network ID to each network device (LAN and WAN). It is important to note that what appears to be a "dynamic" addressing scheme in reality, for the purposes of this invention, is a traditional static addressing scheme. For example, TCP / IP DHCP is only superficially dynamic and is actually a static TAS. DHCP allows a server or similar server to dynamically assign IP addresses in real time to particular network interconnections. DHCP supports a manual, automatic and / or dynamic address assignment to temporarily assign or "lend" an IP address to a network interconnection for a particular period of time and then reclaim it for reassignment when the "loan" expires. But once an IP address is "lent" by DHCP to a network interconnection (however, temporarily, that network interconnection is statically identified by that IP address and its address is equivalent to its "logical" location (that is, the "where" is its topological position in the hierarchical IP addressing scheme) and that location will not change during the duration of the "loan" or "session". Therefore, it is observed that a DHCP is only a way to establish a traditional addressing scheme for certain periods of time. A traditionally addressed point-to-point message can take the conventional idealized generic package format of Figure 1. For the ADDRESS fields (ADRESS) (SOURCE / DESTINATION (SOURCE / DESTINATION)) and USEFUL INFORMATION (PAYLOAD) the format conventionally prefix and suffice administration control information (for example # of package sequence, package type, priority, detection codes, error correction, seeds for encryption procedures, delimiters and others - selections of conventional design) which, for economy of expression, are labeled simply as PREAMBLE (PREAMBLE) and CORRECTION OF ERROR (ERROR CORRECTION). The traditionally addressed message format of Figure 1 can efficiently have an upstream / downstream indicator (not shown) so that for an upstream message, only the address of the message source station is provided in the ADDRESS field; and conversely, for a downstream message, only the destination station is provided in the ADDRESS field. In the TAS network of the preferred embodiment, the aforementioned source address and destination address are, respectively, the network ID of the source network device and the network ID of the destination network device. Contextual addressing scheme (CAS) Before explaining the CAS itself, some introductory, non-technical observations are useful. Identity is not monolithic and does not exist in a vacuum. Identity is a fluid creature of context depends both on the person who wants to know (in particular, depends on their point of view on what things are interested) as well as on one or more of the people who ask the question (in particular, it depends of their 'personal attributes'. The questions "who are you?" or "who am I?" they make sense (that is, they can be answered in a meaningful way) only in context. For example, an individual may be "the lady of the house" or the "credit department administrator," but their identity depends on the context - depending on whether they are at home or at work and whether the person asking is a traveling salesman whose interest is to sell a vacuum cleaner to the housewife or is a customer sales department whose interest is to increase their credit limit. Similarly, in a family setting, an individual may have multiple identities such as father, husband, son or some combinations thereof, depending on the context. Even some business advertisements claim "you are not just a policy number for us ...". An important aspect of context (and therefore of identity) is observed in relation to time. For example, as time goes on and events take place, a person's marital status can change (from "single" to "married" and then "married to Juan" to "married to Enrique"). Similarly, an employer can promote and thus "add new identities" and "annul old identities." The person is promoted to an executive position with a compensation package that makes him or her an employer's partner. Now it has gained new identities for two different contexts - a proprietary party for the context of filing taxes, personal and an "internal" executive person in the context of security laws. Similarly, a person ages and the photograph on the driver's license loses legal validity unless it is updated with a current photo. In this way it is observed that the "identity" changes realistically with the passage of time because the "contexts" change realistically with the passage of time. Not only do new variables come into play or come out, they also change their values. For example, the "background / credit risk" variable is generated when a person enters a trade with credit and subsequently the values of said variable change according to their participation. The identities are dynamic. Another temporal aspect of the context (and therefore of identity) is the rapid acquisition and dissolution of identities in a very short time. This aspect can be seen in the example of a general annual partners meeting of the company. A person walks in the meeting with his "personal accumulated" personal attributes (for example in relation to sex, marital status, income, address, societies, employment status, citizenship, etc.). Whoever holds the meeting prepares the partners to raise their hands. After reviewing the raised hands and physically excluding those who are not qualified to remain (ie, those who are not members), the person conducting the meeting presents the others with a first motion (change the name of the company) and indicates that only their Class A partners are trained to vote on this. After the vote, he submits a second motion (to modify the lending powers of the company) and indicates that only Class B members without debt conversion rights are qualified to vote on it. And so on . Each person at the meeting determines if they have the capacity to vote or on each motion that is presented, and vote or remain silent, as a result. A person may find that within a short period of time, he or she qualifies and votes twice while another person who is In the same short period of time you are able to vote only one motion or none at all. For each context (attendance at the meeting, first motion, second motion) several people may have the same identity sought or none may have the identity that is sought. For each context, a person "assumes" and "presents" their respective identity (partner, class A partner, class B partner or not) of their "accumulated" personal attributes and then continues with their "accumulated" until they are faced with the following context (maybe when you get home and being congratulated by your family).

This "rapid" acquisition and presentation of identities (from an "accumulated" of potential identities) as different contexts develop, suggests that identities are dynamically multidimensional and episodic. Other analogies are equally suggestive. In a chemistry lab, a solution of chemicals will precipitate (or not precipitate) according to the introduction of other chemicals selected by a chemical and not otherwise. As the hypothesis is established by the same theorists, it is the act of observation by an interested party that collapses a wave function within the observable particle and not an instant before or after. The proteome is the complete set of proteins that are expressed by the genome of a cell at any time. What is expressed or not and when it is expressed is the result of a complex set of factors and procedures that operate at any point in time (ie genes that are "inert" and that require, for their expression, interaction of higher order cells, complex biochemistry (protein-protein / nucleic acid)). The network version of the "identity" of the above analogies in relation to an individual is (in a vernacular network) the "address" of a network element (or of a station or a network device in the preferred embodiment). Next, "identity" and "contextual direction" are often used interchangeably, differing only in their level of abstraction, the former being more conceptual than the latter being a particular modality or example of the former in the explanation of the contextual addressing scheme. The SAS describes that for network addressing, instead of asking "where" is something, it is more advantageous to ask "what" is that something (for effective links for interaction with the operating environment). This invention recognizes that in some situations (to slightly modify what Gertrude Stein said) (there really is no "where" there). Instead, the questioner (inquirers such as the itinerant vacuum cleaner, the customer service department at the store that is looking for the most credit, the person conducting the partner meeting) asks "who?" of this hearing (the interrogated), that is, "are you the lady of the house?", "... the administrator of the credit department?", "... a class A member?". Although the "who" part may include an "where" aspect for some contexts, the point of this invention is not limited to "who" or "where" (as traditional routing schemes do) but "enrich" the "who" in the context of enabling a xed element so that it becomes a more useful participant in the life of the network and in this way facilitates efficient links to obtain the desired complex actions. In the previous analogy of the company meeting, the person conducting the meeting is not interested in "where" any of the partners is in the meeting room (after determining ownership that is present), but in "who" are (for purposes of ownership to vote in the various motions). The analogy between the contextual targeting scheme of the invention and the body's immune system, in its similar (initial) emphasis when asking "who?" ("Are you a dangerous substance or is it friendly?") Instead of asking "where" ("are you in the body?"), It suggests itself. The analogy of "chemocommunication" is then amplified after the CAS is explained. The identity (and therefore any particular example in a "network address" or a network element "addressable") advantageously does not exoutside the context. Properly and therefore advantageously understood, the identity - and therefore the network direction - are joint elements of the context - that crystallize continuously and dissolve with the changing contexts. To the extent that contexts "come" and "go" for a particular example, the same happens with identities (and their "network addresses"). Within a very short period of time, a station can "take" and "remove" several identities / network addresses. No CAS station in the CAS network has a static address or identity. In addition, a CAS station can not have a unique address in general - it will generate its contextual address that is unique if, and only if, for a given context, there is no other CAS station that generates the same contextual address. The CAS contemplates that several CAS stations will create, from themselves, the same address / network address for a given context. In the network of the electricity dibution company, for a context, a station is one (or perhaps several) in a certain geographical area. In another context, the same station is one (or perhaps several) (whose client is) billed according to a certain billing plan. In another additional context, the same station is one (or perhaps several) units that draw excessive energy at a certain point in time from a certain feeder line. energy In this way, all CAS addresses are episodic (ie, time-dependent), in particular, and more generally, all are contextual (ie, informed by the context provided by those who ask and those who respond, in the time to formulate the question or to establish the answer). The static addressing schemes involve a rigid set of addressable entities, which in turn implies that the particular communications system and the supersystem or the complex, in general, do not change with respect to time in response to their operating environment. that typically changes with respect to time. Because, CAS is "granular with respect to time", it provides a dynamic and realc communication system that changes over time, often in response to stimuli. (typically, though not exclusively from the operating environment) and sometimes needs to change itself (for example, periodically or when performing maintenance or repair driven by an event). In accordance with this invention, efficient identification and addressing stations in a network are based on the recognition that addresses follow identities (the "who") on a one-to-one basis and that identities do not exoutside of contexts. particular.

Put simply, a CAS station address - its identity or its contextual address - is a multidimensional element of context that in many areas changes realcally over time. The contextual addressing scheme or CAS is an addressing scheme that is based on the contexts that are defined by an "inquirer" and (ie with) an "interrogated" (CAS interrogation station and interrogated station CAS, respectively). Specifically, the contextual directions are generated "in the course" not by the "inquirer" but by the stations to which they are asked by the "inquirer", such directions depend on the point of view of the "inquirer" (to whom he is searching ) and the "constitution" or context of the "interrogated". A "CAS network" is a plurality of network elements (CAS stations) which are therefore communicated: a station (the CAS interrogation station) has the functionality of sending a particular message type (the CAS message) and other stations (interrogated stations CAS) each have the functionality to receive the CAS message and to identify themselves, accordingly (when creating contextual directions for themselves). See figure 2 for an idealized format of the CAS message. There are similarities and identities between portions of the message CAS (of figure 2) and those of the message TAS (of figure 1), especially the management control portions. But the CAS counterpart to the TAS ADDRESS field is crucially different, and is explained below. Unlike a TAS message that has an address that identifies (explicitly or implicitly the location - the "where" by analogy - of the proposed destination of the message) a CAS message is sent without that address. Instead, a typical CAS message has a contextual function (which has at least contextual variables that are related in a relevant way to the identity search) useful information. A interrogated station CAS has its contextual attributes (which are those contextual variables that maintain their contextual values for them). When the CAS message finds the contextual attributes of the interrogated invention (in particular, when the contextual function of the CAS message is processed by the station on its contextual attributes), said station is contextually addressed, accordingly. The concepts and foundations derived from the previous contextual scope are explained below. Until then it is enough to think that the "inquirer" is a CAS interrogation station whose "point of view" (in which thing is interested) is encapsulated in the CAS message it sends and in particular, its contextual function represents part of the context for which interrogated station CAS is identify itself The identity is the result of the meeting of said message CAS ("point of view" of the inquirer) with the contextual attributes of the interrogated station CAS (its "constitution"). When the CAS interrogation station sends a CAS message, a station having the functionality to "listen" to said CAS message (ie, has the functionality to decode it at the appropriate level of decoding so that the contextual function of said CAS message is applied to the contextual attributes of the station to determine, typically, whether said CAS message for which it is designed as a station that is searched for to carry out (a part) of a desired complex action) is a interrogated station CAS. If communications (ie, sending and receiving CAS messages) is implemented by wireless technologies, the CAS interrogation station can be considered to "broadcast" (to use the RF terminology) the CAS message, and each station that receives and it processes the CAS message to decide if that CAS message is for that station, it is a station interrogated CAS. In the preferred embodiment, the term "broadcast" means multiple point-to-point physical transmission of RF signals via communication representatives), and is referred to as "RF broadcast." This is to distinguish from "IP broadcast" which refers to a message sent to all stations in a network operating in an IP addressing system or other types of broadcasts (for example, under IEEE 802.11) which are referenced in the schemas of traditional addressing. Following are observations with examples about the nature of CAS. For example, consider Figure 3 and the following example, where the notation [frequency (s)] refers to one or more frequencies that a station synchronizes for transception. Consider station A [frequencies # 1 and # 2] and stations B [frequencies # 1 and # 2], C [frequency # 1], D [frequency # 1] and E [frequency # 2]. Base station A broadcasts a first message by RF (on frequency # 1) and stations B, C and D receive it and process it (station E is not tuned to receive a frequency # 1). In this way, the CAS network consists of station A of interrogation CAS and stations interrogated CAS B, C and D. Station E is "omitted" from the first message and thus is not a station interrogated CAS and is not part of the CAS network for the purposes of message # 1. Continuing the example, when station B (which is a station interrogated CAS in the preceding Example of message # 1) subsequently broadcasts by RF a second message (at frequency # 2) that is received by stations A and E (but not by stations C and D), the which are not tuned to receive a frequency # 2), then the CAS network for the second message consists of station B as the interrogation station CAS and stations A and E interrogated CAS. An analogy with the preceding example, can be found in the United Nations, where some speakers are multilingual and some speak a single language and participate in a plurality of interactions (written or verbal) - in the present "conversations" for simplicity purposes expression. On a given day, various conversations take place. What determines the participation of an individual in a given conversation is not the means of communication (oral or written) but the ability to preserve in the relevant language. Those who speak more languages evidently participate in more conversations. A Swiss diplomat can listen to a conversation. (for example in French) for a particular statement made by the speaker in that place and can be a speaker (for this particular statement) in another conversation (for example in German). Those who speak only English do not participate in either of the two previous conversations. The "omission" mentioned above of a station with respect to a CAS message (which disqualifies it from being included as a CAS interrogated station for said CAS message) may be the result of any designed incompatibility with a CAS interrogation station (which includes that related to frequency tuning (the example explained above with figure 3), a modulation scheme, a communications protocol or simply because it is located too far away for wireless communications of said CAS message). In this, with respect to CAS, the "omission" has a purpose (by design or as a consequence of the design) so that the "omission" does not include the ability to hear that results from equipment failure, accidental damage or the transport of communication channels (for example due to foliage moving) or similar. All stations in a network are CAS stations with respect to a CAS message, except for those that are "omitted" for this. A station that can not receive a CAS message, by definition, is not a CAS interrogated station and is not part of the CAS network for the purposes of that CAS message. That is, this invention does not leave the "omitted" stations because they are part of a web of a more general and concrete reality of hybrid networks. Although CAS can not include "omitted" stations, they are ways of the invention to adapt them by including their efforts in the life of the network (discussed in the following as "custodians"). It is indicated in the foregoing, that in contrast to TAS, the CAS "does not know" (and "does not care") "in which place" any of the searched CAS stations is found and evidently does not use its ignorance to send a CAS message. The CAS, regardless of which OSI layers are being implemented, simply bases on the proper functioning of all the OSI layer protocols below one or more of the respective layers of its implementation that are related to sending and receiving a message CAS between a CAS interrogation station and the interrogated CAS stations. The CAS does not suppose or require anything else. This assumption frees CAS from having to "know and use" traditional addresses when sending a CAS message. Even after a searched CAS interrogated station responds to a CAS message by communicating with the CAS interrogation station, the CAS interrogation station, in particular, and the CAS network in general still "do not know", necessarily, "where" find the interrogated station CAS that responds. For example, and continuing with Figure 3, consider that base station A and stations B, C and E communicate in the TCP / IP protocol and their traditional hierarchical addressing scheme (where each station has its fixed IP address). and only) . Assume that the base station A sends a CAS message in a multicast format (based on an IP addressing scheme) addressed to a designated subset of IP addresses of which stations C and E are members. After the CAS network, for the purposes of said CAS message (multicast) consists of the interrogation station A CAS, and the interrogated stations CAS and E. It may be that the base station (or one or several communication representatives) "know" "where" is each station interrogated CAS (physically or logically) and may even that knowledge (that is, a traditional management scheme) as part of its procedure (lower OSI protocol layering) send the CAS message to the interrogated CAS stations (as the previous multicast sample shows). But said base station network device, which is a CAS interrogation station, does not know "where" any of the stations interrogated CAS is. Consider the analogy of two OSI application layer programs, each on its own computer, communicating in a TCP / IP protocol with each other. Although it is conceivable that these two programs know and use the IP address of the network interconnection with each other in order to communicate with each other, more likely, the knowledge and use is transparent to the programs themselves, such as the OSI application layer, although such knowledge and use are part of the communication procedure between them. Generally, the two application programs that operate on their respective computers, application programs, do not know and do not "where" interest is the other and. they simply assume that lower layer protocols are managed to carry out communications with each other. To return to the analogy of the company meeting, whoever holds the meeting can use various techniques to present their voting instructions for the motion. The person can simply speak loudly if the acoustics of the meeting room is sufficient, or use a microphone / speaker system for a large room, or they can be manual instructions written manually (one or several copies) where they are asked to the closest person (your assistants or part of the audience) that you pass on to the rest of the audience (with or without your instructions for a specific method of moving from making such a transfer or a reference to meeting hosting topologies or other implementation details) . The person is not interested in how the voting instructions are conveyed and received by the audience as far as the person is concerned to the extent that the hearing understands the instructions. The CAS is agnostic or neutral with respect to the topology (physics and logic) regarding the stations which can be organized as a brush, a bus, a star, a ring or a tree topology with branches (physical or logical) or some combination thereof, or without a stable topology any. The CAS interrogation station can be at the root of the topology tree (the analogue can be a base station in a telemetry network of a power distribution company) or at the root of a branch of a tree (the analog would be the controller of a subnet of a large factory). The CAS interrogation station can be the station that has the witness and the expertise of a ring network. Nothing in the definition of a "CAS network", "CAS interrogation station" and "interrogated station CAS" prevents a station from being a CAS interrogation station at one instant and a CAS interrogating station at another time (as explained above). previous with figure 3). The CAS is not interested in how the CAS message is sent by the CAS interrogation station to the interrogated CAS stations. The examples below show the CAS's agnostic attitude regarding "how" the CAS message is sent and received - it simply assumes that the mechanical infrastructure is present and functioning so that the CAS message is received by all interrogated CAS stations. For example, the CAS message is broadcast by RF through the CAS interrogation station and finally arrives at a physically remote interrogated CAS station through one or more communication representatives. In particular, the station CAS may use a direct way to send a CAS message to a CAS interrogation station (such as an RF broadcast without repeaters) and may use another, indirect way of sending the CAS message to another interrogated station physically CAS further away. For example, the CAS interrogation station is a base station on a WAN that operates on a first communications protocol and one or more interrogated stations CAS is an LA? that operates in a second communications protocol, and is there a gate converter between the WA? and the? wherein the first communication protocol is a hierarchical TCP / IP and the second communication protocol is a non-hierarchical protocol. For example, the CAS network is agnostic with respect to communication protocols that are connection oriented (for example, circuit-switched wiring, X.25, TCP / IP) or connectionless (for example, TCP / UDP). The routing, if any, can take any conventional form. For example: routing by directory (where each station / element maintains a table for each possible destination), hierarchical routing, static or dynamic routing, routing directed by centralized base station, isolated ad-hoc routing between particular stations , routing d / hybrid, distributed routing, routing per session, routing by broadcast. The CAS is not interested in the Routing in particular - generally assumes that the communication channels are operational to transport the CAS message from the CAS interrogation station to the CAS interrogated stations. At present, the CAS in general and the CAS message of the CAS interrogation station in particular, do not provide assistance with respect to routing or the formation of bridges or connections (if they are performed). A hierarchical TAS address is one that provides information about "where" the station is (ie, its approximate topological location), so that the network analyzes or otherwise uses' routing from the source to the destination. In a very opposite way, the contextual address is a creation for each interrogated station CAS for itself, in response to a CAS message that is received at the end of the communication path from the interrogation station CAS, and therefore not yet has (in a topological, physical or otherwise) meaningful information to send said CAS message. Definitions . In the above, the concept of identity is introduced with exemplary references to individuals (for example, the lady of the house and the partner). The concept is then transplanted to a situation in a network, where individuals are replaced with "stations". The term "station" is used mainly in the conceptual explanation of a traditional addressing scheme and a contextual addressing scheme for networks. The term "device" is used primarily in the preferred mode of a telemetry network of a wireless power distribution company, where it refers to network devices that function as: (1) a central intelligence, the base station , (2) a communication end point, or (3) a communication representative operating between the base station and a communication end point. There is an approximate functional equivalence of a station (of interrogation TAS or CAS) (in the explanation of TAS and previous CAS) and the network device (LAN or WAN) of the preferred modality, where the latter is the implementation of the modality preferred from the previous conceptual (with the different ones explained in the following). In this way, both terminologies, "device" and "station" are used interchangeably to the present, with exceptions. An exception to the approximate equivalence (in the preferred mode) is a network device that (by design) can not receive any message (and in particular, a CAS message) because it only has RF transmission capability - it is denominates a LAN device [deaf to RF], explained in the following. Another exception is when the Use of the term "device" is to clarify distinctions in the implementation of the preferred embodiment that are not evident in the terminology "station". A terminological exception is the term "base station" which is used both in the CAS explanation and in the preferred modality to refer to the central intelligence that sends messages in a multiple point-to-point transmission or that receives messages from the endpoints . This element retains its "station" terminology when coupled to other network devices in the preferred embodiment. Each CAS or TAS station (and in the preferred mode, each network device) is "time conscious" which means in the present that it has the functionality to measure the passage of time. The time awareness of the entire network is generated by the base station, as the time metric "network time". If a station can and does actually calculate the passage of time in coordination with other parts of the network (for example with other network intelligence, which includes in particular the network time of the base station), its time awareness consider as "full" and its "time" in effect, it is network time; and if the station can not calculate in this way in coordination with the others, its consciousness of time is considered "limited" and its "time" is simply internal and is called relative time. A station completely Conscious of time, before the resumption of energy after an alteration of energy, temporarily maintain a relative time until it is re-coordinated with the time of the network. Consistent with the "context" theme, the terminology of "contextual variable", "contextual value" and "contextual attributes" are used both in the previous CAS explanation and in the wireless telemetry utility network of the preferred modalities. The terms "business" and "manufacturer" herein are understood as follows. The manufacturer produces the network devices and provides position or control of them (by sale, rent or other suitable legal arrangement) to a business that operates them for customers (in the preferred mode, the business is the electric power distribution company). that supplies energy to its commercial, industrial and residential customers). Although almost all of the operational management of the network is normally performed by the business, a certain fundamental waste of network administration will be retained by the manufacturer. Typically, the manufacturer is involved in maintaining the underlying integrity of the network, administrative functions, and the like related to the infrastructure of the network operated by the business. The term "business-motivated" means, for economy of expression, motivated by a business and manipulated by it. A business is typically interested in organizing its customers and their services in accordance with business models and procedures (for example, billing plans, "accumulation" of physically close customers in groups, etc.). The business performs "business-driven" manipulation by sending the instructions of the base station message (by traditional addressing or conceptual addressing) or by using portable technologies in the field of network devices of interest. The term "motivated by the manufacturer" means, by economy of expression, motivated by the manufacturer and exclusively manipulated by it (that is, it can not be manipulated by a business). The manufacturer typically performs manufacturer-driven manipulation at its factory or service center before the business takes ownership of the network device, but can also manipulate it later (for example on network devices of interest, by portable technologies used in the countryside) . In practice, the manufacturer (or some other party, perhaps the business under certain legal arrangements) must and can retain the implicit and absolute capacity throughout the network as a "system administrator" to manipulate everything, including everything that can be done. manipulate a business (that is, you can manipulate it as if it were a business). In this sense, "motivated by business" is a subset of "motivated by the manufacturer". The terms "motivated by a business" and "motivated by a manufacturer" are used here mainly with the contextual addressing scheme (for example, contextual variables) and the traditional addressing scheme (for example, network ID). Consequently, concepts and terms derived as "attributes / variables / context values of business" and "properties of the manufacturer" are used (as explained in the following). The term "business-driven" is also used with parameters (thresholds, time periods, etc.) used in procedures such as PQM, "plug and play" (as explained in the following). The manipulation includes the change of a contextual variable and the change of the contextual value for it. A specific case of the latter is to "attribute" contextual values to contextual variables to form contextual attributes and they are explained in the following. If the encounter mentioned before a contextual function with the contextual attributes of a station interrogated CAS that results in the creation of this contextual address of the station, the creation continues after the meeting that continues as a result of the latest implementation technologies. In this way, it can be said in general, the contextual address is generated when the CAS message is received. But as explained in the following, creation can be deliberately postponed beyond that encounter (for example as part of a desired complex action). The CAS does not require the creation of the contextual address in a completely simultaneous way through the CAS network. A measure of simultaneity is obtained insofar as it is facilitated by the implementation technologies. For example, in the telemetry network of wireless distribution companies of the preferred embodiment, the nature of some RF technologies provides very fast communications and it can be expected that the contextual addresses of all stations interrogated CAS in a CAS network for a given CAS message , they are created "approximately" at the same time. But even in the RF implementation of the preferred mode, factors such as the level of network traffic, bottlenecks in certain places, the amount of "daisy chaining" or the use of communications representatives will be simultaneously degraded. the physical location away from a particular CAS station, the header of the traditional addressing protocols used (if any), and other familiar factors that affect the latency. That is, the degree of simultaneity required (that is, the degree of granularity of response time to a CAS message), depends on the desired complex action. For example, for a CAS message, "all stations on line # 7 powered by energy now report their energy consumption", a delay greater than 5 minutes may be intolerable for a report to be made of all the stations searched for . In contrast, for a CAS message of "all stations in billing plan # 2, should be inactivated", a delay of one hour may be tolerable. The point is that the CAS does not impose an absolute simultaneity of crystallization of all the contextual directions (and of any processing of useful information of consequence by the CAS stations searched) through the CAS network. Similarly, the CAS does not require the CAS interrogation station to send the CAS message to all interrogated CAS stations at the same time. For example, you can send the CAS message to some interrogated CAS stations, wait and then send the same CAS message to the rest of the interrogated CAS stations. Contextualization produces identities / directions. In particular, according to this invention, the contextual address of each station interrogated CAS of the CAS network, is the encounter of: (a) a contextual function sent by the interrogation station CAS, where the contextual function is a relationship (typically mathematical) that involves contextual variables, with (b) each of the contextual attributes of the interrogated station (which are contextual variables with their contextual values for them). The contextual function is analogous to the inquiring point of view - it is part of the context within (or for) which the station can answer the question "who am I?". The contextual attributes of the station are analogous to the individual personal attributes (or its constitution or contexture). Once the point of view of who the inquirer is applied to the "constitution" of the individual, said individual has an identity that has meaning for the inquirer - the individual to whom it is asked is "addressed" in this way with meaning. Once the context is presented to a station, it identifies itself by creating its contextual address, based on its contextual attributes - its contextual direction "becomes" or crystallizes in existence. In formulas, the contextual function processed by a station on its contextual attributes will create the contextual address for said station. The formation of the "context" starts when the contextual function is sent and is partially informed by said contextual function and partially by the contextual attributes of the interrogated station CAS at the time of said processing. The main CAS components of the functions Contextual and contextual attributes (which are contextual variables and contextual values) are discussed later, followed by an explanation about the useful information. Contextual functions. A contextual function is the analogue (mathematical, network) from the point of view of a person who wants to know (for example "how the president of this meeting of the company wished to know of those class B partners who have the capacity to vote regarding the pending motion "). This point of view (that is, what is of interest to the president), informs part of the context for each person questioned so that he identifies himself (with the other part that comes from his personal attributes). In the context of the network, the contextual function partially informs the context for which the interrogated CAS stations identify themselves and are searched (as part of effective interactions for a complex action desired by the base station in the preferred mode) . The analog CAS of a traditional addressing message format is shown in the idealized format of Figure 2, where the CF contextual function can be found in conventional preambular and similar components (as in the TAS format of Figure 1) .

Next, there are four exemplary contextual functions CF1 to CF4 that are received by the interrogated CAS stations. Each station interrogated CAS has contextual variables (CVarl, CVar2, CVar3) with their respective contextual values (CValor 1, CValor 2, CValor3) that form their contextual attributes. { X,?, O). The contextual function CF has the same contextual variables (CVarl, CVar2, CVar3) and relates them (in exemplary ways described later). In addition to the first type CF1 of contextual function explained below, a contextual function also has the respective values for those contextual variables. { X,?,? } in such a way that the contextual function CF (X,?,?) represents the identity of the interrogated CAS stations that are searched. The words "turns" and "creates" are italicized in the following to emphasize that the contextual address is first brought into existence only by the interrogated station CAS when its resident intelligence receives the CAS message and processes the CAS message (in particular , the contextual function) about its contextual attributes - the contextual address does not exist before or after. I. Contextual function CF1 = (CVarl LOGIC1 CVar2) L0GIC2 CVar3 where LOGIC (i) is any traditional Boolean operator. { for example Y (AND), 0 (OR), XOR (XOR),? O (? OT),? Y (? AND),? O (? OR), X? O (X? OR)} .

When a interrogated station CAS receives CFl from the interrogation station CAS and processes it over its context attributes. { X,?, O.}. , its contextual address becomes < (X L0GIC1?) L0GIC2 O > for the context whose formation was initiated and partially informed by said particular CFl and for partially informed by its contextual attributes at the time of processing and only for that context. Yes { CVarl, CVar2, CVar3} represents contextual variables of. { height, weight, sex} , then CFl is. { (height OR weight) AND sex} . If two stations interrogated CAS have context attributes of. { 1.8 meters, 68 kg, male} , then the contextual address of those two stations becomes < (1.8 meters or 68 kg) And male > . In colloquial terms, CFl asks all stations to identify themselves with their respective specified physical attributes of. { (height OR weight) AND sex} . It is observed that the contextual function CFl of a CAS interrogation station is used by a interrogated station CAS on its contextual attributes to create its contextual address for (and only for) the context informed by said CFl and its contextual attributes at the time of creation . At another time, the context may be different (for example, weight gain) and the resulting contextual address may be different. Although CFl results in the creation of an address context, the following exemplary contextual function CF2 advantageously goes further by providing information related to what the CAS interrogation station is looking for (for the desired complex action), and that it has to ask the interrogated station CAS if the contextual address created by the interrogated station CAS is one of the searched. II. The contextual function CF2 is. { CVarl L0GIC1 (CVar2 L0GIC2 CVar3)} and has . { X,?,? } where LOGIC (i) is any traditional Boolean operator and. { X,?,? } is such that CF2 (X,?,?) represents the identity sought (from the point of view of the CAS interrogation station for a desired complex action). Upon receipt of CF2, the interrogated station CAS COMPARA CF2 (X,?, O.}. WITH CF2 (X,?,?) The result for the context whose signing is initiated and partially reported by said particular CF2 and partially informed by the context attributes at the time of execution and only for that context, is the station contextual address.If the comparisons do not match, the contextual address of the questioned station CAS becomes "null" for that context. context of the interrogated station CAS is returned for that context: <X LOGIC 1 (? L0GIC2 O)> which is identical to <x L0GIC1 (? L0GIC2?)> and the interrogated station CAS will consider itself What is it that which is sought by the CAS interrogation station (the base station for efficient links for the desired complex action). For example, . { CVarl, CVar2, CVar3} It represents . { location, type of customer and measured item} Y . { ?,?,? } =. { northwest, factory, electricity} and CF2 is. { Location Y (factory AND NO electricity)} . The interrogated station CAS COMPARA. { northwest Y (factory AND NO electricity)} WITH its contextual attributes. In colloquial terms, the contextual function CF2 asks all the stations to identify themselves which ones, at this moment, are in a factory in the northwest and do not measure the electricity (that is, measure the gas or water) of consumption) . For that context, these stations will have created their contextual addresses of: < "Northwest" AND ("factory" AND NOT "electricity") > and the other stations will have created a contextual address "null" (that is, "null" identities) for themselves. In short, although the CFl contextual function and the CF2 contextual function require that all interrogated CAS stations generate context identities / addresses for themselves, CFl does not do more, but CF2 does more when transporting information. { ?,?,? } for the interrogated station CAS to use it, to determine if it has an identity / contextual address searched by the station interrogation CAS. The preferred embodiment is described below with exemplary CF2 type context functions. The operational advantage of CF2 for efficient links is that useful information (explained later) can be processed by those stations who have determined that they have the identity / contextual address searched, immediately after determining it. In an analogy at the entrance of an airport, when an agent in that place announces "those with small children or those who need help, please advance to the entrance now ...", the identification of the individuals sought and their - Operation in the desired action, is carried out by the passengers immediately, without further action or communication with the agent. Note that simply by comparing the contextual attributes. { X,?, O), with. { ?,?,?) is not inherently useful because such a comparison can be the lost part of the context (ie, the part provided by the contextual function). For example, depending on the contextual function, the logical instruction of CF (LOGIC), a contextual function processed on a set of operands that can coincide with said contextual function executed on a different set of operands, and in this way a simple comparison is I would have "lost" something. That is, a Simple comparison (which is really an extremely simple contextual function) can be of some use for some complex actions desired in operating environments, as follows. The previous "compare and match" mechanism that identifies the searched stations does this on a "either / or" basis. In one variation, relevance can be based on "compare and set within a prescribed difference" (or "within a prescribed Hamming distance" to use an analogy) to create "generally granular" slides. For example, a contextual CF function requires the matching of at least any four or five contextual attributes and that is within a prescribed derivation for which it does not match, in order that a station is the searched station. This variation leads to the following exemplary contextual function.

III. Contextual function CF3 = a contextual function "confusing logic". While the logic instruction LOGIC (i) the context functions CFl and CF2, where there are simple boléano operators, a confused logical function recognizes more than the true and false simple values. Confusing logical propositions can be represented as degrees of "truth" and "falsehood", to make them coincide with the "real world" that lacks said "defining condition" in some metric environments.

For example, when there is an excessive load on the electric power grid, it is desired to identify user customers who are not at a good credit risk and who are also using an abnormally high amount of energy at this time. Assume that a station has contextual values such as a history of energy consumption and a history of paying bills. With operators such as: AOB = Max ((eA (x), e (B (x)) AYB = Min ((eA (x), e (B (x)) and the limits or modifiers of confusing values are as "manyqs" A (x) = A (x)? 2 and "more or less" A (x) = - "A (X), e is the function of presence, and 6A (x) = energy consumption = 1.0 where x is 50% more over the last values of period 1/6 where x is between 5% and 50% over 0.25 where x is between 5% and 1% over 0.0 otherwise and eB (x) = bad credit risk = 1.0 where the unpaid bills are 180 days 0.5 where the unpaid invoices are 90 days can be developed a contextual function CF3 which questions colloquially, for example, to stations whose Energy extraction is now "unexpectedly very high" (that is, in relation to their consumption history) and (whose users) are "more or less" of bad credit risk, to identify themselves. Those identified in this way can then process the associated useful information (for example, instructions to suspend the power supply).

IV. The contextual function CF4 is a combination of p, J, 2--, logarithms and other sophisticated mathematical functions with contextual variables, all selected for model physical situations presented by the operating environment, helping the artificial intelligence / expert decision systems in business aspects of operation of the network that interacts with the operating environment and the like. Observe the contextual functions CF I to IV above, which is the contextual function received (that is, the point of view of the CAS interrogation station or, in the preferred mode, the base station), which recognizes and creates the multidimensional nature of the identity / contextual address of the station. For example, if a contextual function CF considers three contextual variables of the station. { CVar, CVar2, CFar3} , the direction The resulting contextual can be one-dimensional (CF = numerical average of {textual attribute 1, contextual attribute 2, contextual attribute 3.}., two-dimensional, three-dimensional (for example, previous CFl) or greater.It is also observed from the previous examples , that the dimensions of an identity / contextual address of a interrogated station CAS is related by the received CF contextual function The dimensions can be related to each other without limitations: in a linear, non-linear way (by polynomials, rational, exponential, trigonometric functions ), orthogonally, by boléano operators or by confusing logical instructions.Therefore, it is observed that the CAS interrogation station (that is, its operator, either the business or the manufacturer) through its selection of the contextual function , controls all aspects of the dimensionality of the contextual direction of the stations interrogated CAS (but without each of the atri contextual but of the interrogated station CAS, the context is not complete). There are no inherent limitations regarding the dimensionality of the contextual directions because there are no limitations inherent in the CF contextual function. The implementation of this invention for the sophistication of contextual management is limited only by the limits of the technologies that are implemented (for example, the capacity and data storage capacities of the stations, the processing capacity of the stations, etc.). A simple exemplary implementation of CF2 is found below together with Table 1 below. Contextual variables, contextual values and contextual attributes A contextual variable is a variable related to a interrogated CAS station and its identity or contextual address. A contextual variable and its contextual value exist independently of the traditional direction of the station (assuming it has any). In the preferred modality, the contextual variables are selected (in cooperation with the interaction modules) for their assistance in the modeling and formulation of the desired complex actions with the operating environment. Generally, for a given CAS network (for example any of the three shown in Figure 3), all CAS stations in the network (the interrogation and interrogation stations together) must share the same semantic infrastructure scheme, which includes in particular the same set of contextual variables. For a given CAS network and its shared set of context variables, (1) each interrogated station CAS has its context values for that shared set of contextual variables, to form its contextual attributes; and (2) a function contextual- CF. has the same set of contextual variables. By delving into the nature of the contextual variables and their role in addressing for effective links, four exemplary types of contextual variables are provided when considering the following: (with references to implementations of preferred embodiment). Contextual variables type A. These relate to attributes of "infrastructure" of the station (for example, the version of the microprograms and physical elements (hardware) of the resident intelligence or the "device type", such as a LAN device [RF deaf]). Contextual variables type B. These are related to a physical metric or aspect (for example quantity or quality) that is' perceptible (directly or indirectly), observable, detectable or measurable (collectively, by expression economics in the present is used the term "detected" or "measured") in "real time" (immediately) by the interrogated station CAS. For an interaction module that is a sensor, what is typically measured is the operating environment (for example, the energy measured by a watt / hour meter or inadequate misuse by a misuse detector). The contextual variable of exemplary energy measurement is a good example of the dynamic effect of the operating environment in the context and therefore of the identity potential - in many areas, the value of said contextual variable changes (increases) daily, in case of not doing it every hour, or even per minute. Contextual variables type C. These relate to the use of the client of the station interrogated CAS (for example your credit classification, your billing plan, your legal rights to the interaction module, the background of energy use, the background of the invoice payment history) or with the business of the distribution company that operates the CAS network (for example, the interconnection meter module identification of the interrogating station CAS as a # serial meter, or the line # of energy to which the measured line is connected). Contextual variables type D. These relate to things "beyond" the type A-C such as the network environment of the interrogated station CAS. Regarding the example of the first type D of the influence of, and interaction with, the network environment, consider a station interrogated CAS that is fully aware of time. Consequently, a contextual variable can be related to the time in which the contextual value derives (directly or indirectly) from other CAS stations, either "globally", ie, base station network time) or "regionally" . For the latter, assume that the CAS network is within the limit of the time zone between the time of the Pacific and the time of the mountain. Said time of the time-conscious CAS station can be completely coordinated with those of its physically close neighbors (for example those in the same time zone) and will be advanced or delayed with the CAS stations in another part of the CAS network ( that are in another time zone and consequently are coordinated in that way). Regarding a second example of type D of the network environment, a contextual variable is related to "where" a conventional interrogated CAS station is, for example its location (physical or logical) in relation to interrogated stations CAS "neighbor" (physically or logically) For example, in "where" is your location in a routing topology similar to a related list or as part of an IP addressed network. Before explaining the useful information, below are observations and explanations about the contextual variables. Although the exemplary contextual variables are identified in the above with high-level symbolic pseudonyms (for example # of billing plan, power line #), the symbolic level can be very low. For example . { CVarl, CVar2, CVar3} can be the addresses in a station memory (for example, intermediate memories and registers of physical elements (hardware)) that store physical aspects of "low level" measured (for example voltage). Attribution of contextual values to contextual variables of the station to form their contextual attributes Contextual values (together with the contextual variables to form contextual attributes) can come from any source and method; the CAS does not impose limitations. In the present, the general procedures of contextual value and a contextual variable (that is, providing a value) are called "attribute". Some of the contextual values are attributed by contextual variables by programming. For example, the meter serial number, the customer credit risk rating and the power supply line # (contextual variable type C) are attributable and programmed by the business. For another example, the version of microprograms and physical elements (contextual variable type A) are programmed / attributed by the manufacturer. In contrast, for attribution by programming, some contextual values are attributed by the interaction of the station with the operating environment (for example, by means of its sensor-interconnection module-type B contextual variable) or coordination with its environment. network (for example, when obtaining network time-variable type D).

Environment Although the "network environment" (of a CAS station) and the "operating environment" (of a supersystem or complex) exist in different conceptual regimes,. they are not necessarily disconnected. Both are environments in the sense that both are exogenous to the subject CAS station and contribute to its contextual direction / identity. In addition, if a CAS station receives information from a neighboring CAS station (ie, from the network environment), that information can be derived from the contextual attributes of the neighboring CAS station which are attributed by detection from the operating environment ( see "inheritance" below or "receipt of information" from others). Time A conceptual distinction must be observed between: (i) time as a contextual variable of a station CAS, and (ii) the time when the CAS station creates / crystallizes its contextual address. There is a difference between "those who are large (ie, over 65 years of age), please come to the front of the" and "line, please take 5 minutes to consider if you are a person or older and those whoever they are, please go to the front of the line.) This invention considers that "65 years" is a contextual attribute but does not consider the postponement with the purpose of "5 minutes" is related to a variable contextual (although at the implementation level, said postponement is at some time in the future instead of waiting for the passage of a certain duration after the reception of the message, it can be an insignificant difference between them). See the following in "contextual address deferral" for amplification of when a contextual address is generated. Persistence / flow Some contextual variables will retain relatively persistent contextual values (for example, the microprogram version type A, which will not change except for manipulation motivated by the manufacturer). Other contextual variables will retain contextual values that typically fluctuate (type D - time and type B - measured power, for example) because the operating environment is dynamic over time. Therefore, if the contextual attributes of a station have a fluctuating type of contextual variable, the "potential" identity of the station / contextual address changes constantly. To use an analogy, the "genome" of the station changes constantly and therefore is expressible with a constant change, regardless of whether there is interest in expressing it at any given time. Endogenous / exogenous Contextual variables type A can be consider the interrogated station CAS "endogenous" whereas the BD type contextual variables can be considered "exogenous" to the station interrogated CAS in the sense that they are a product of their environment (ie, information of the operating environment or information of a logical instruction (which includes a logical instruction that includes information from its network neighbors) that resides at a higher level where the logical instruction resides exclusively in the interrogated station CAS). The hosts of a party who ask "those who have drunk a lot do not need a designated driver ..." refers to "exogenous" information (of alcohol consumption or having an independent means to go home, respectively). The line of division between "exogenous" and "endogenous" is sometimes porous, due to the true nature of any identity that evidently does not follow a rigidly clear caste system of "exogenous" and "endogenous" (similar to the elusive if a particular personal attribute of an individual is the product of food, nature or both). Without the point of view that the personal attributes of this individual are partly reported exogenously and in a similar way the contextual attributes of the station are reported in part of the environment (physical and network environment, in the preferred modality) and consequently , the environment is part of the context for which the identity. Relationship with OSI As indicated in the above, the CAS does not perform a mapping on the OSI reference model - see Figure 4 for an idealized visualization of the CAS in relation to the OSI. An implementation of a CAS network can reside exclusively in one OSI layer, but it can also reside partially in one layer and partially in another layer. Nothing about the context functions, values, variables and attributes as well as created contextual directions prints its residence to only one OSI layer. Although Figure 2 shows a CAS message in a format that may appear to reside in only one OSI layer, note that the format in Figure 2 is idealized. A CAS message does not necessarily map over a single OSI layer - it can span (or transcend) several OSI layers and in this way the contextual function can be a mathematical relationship of context variables, one of which resides in the OSI network and one in the OSI application layer. The analogy with personal identity is a message that seeks individuals based on two personal attributes - "those who are engineers of the male gender ..." for example - who exist at different levels - gender and profession - and who analogously correspond with the application OSI physical layers, respectively.

Relationship to a traditional addressing scheme The CAS network can be seen as an "overlay" on underlying addressing schemes (if any) and in fact, it does not care which underlying addressing scheme exists (if any), or which methods of communications are used. between the network elements, insofar as the sent CAS message is received by each station interrogated CAS. As an overlay on the underlying addressing schemes (if any) the CAS network can also be used "in parallel" or "in addition" to "other addressing schemes" (for example, traditional IP addressing schemes or one, such as in the preferred mode, based on network ID, for traditional messages). In this way, because the CAS can be (and in some modalities and implementations is) an overlay in a TAS network or is "in addition" to a TAS network, a station can be a CAS station for contextual addressing purposes but also it can be a TAS station for traditional addressing purposes (and therefore it can have its network IDs, explained later). All that said, it is worth noting the additional emphasis that CAS does not inherently require an underlying addressing scheme - a CAS network can be built on top of or "in addition to", in a "shape-fit" way whatever the architecture provides. of the network.

Above all, it is established that there is no CAS station in the CAS network that has a unique or static address or identity. This must be understood properly. First of all, there is no CAS station, a CAS station that has that unique address or identity. The LAN device, for example, the TAS station, which is traditionally addressed, has a unique TAS address (over network ID) but said LAN device, which CAS station, for a received CAS message, does not necessarily have a unique address or identity . Second, the CAS (unlike TAS, for example, does not impose a unique address requirement for each CAS network element (ie, if it transpires that a CAS station generates a contextual address that is unique to a given CAS message) (ie, it becomes the only station searched), which may be the result of context at the time of creation and not the consequence of an inherent characteristic of CAS.) Type A is motivated by the manufacturer, type C is motivated type B is motivated by the business, subject to limitations of the interaction module, type D is motivated by the business subject to limitations in the rest of the network, type B interacts with the operating environment and the type D interacts with the network environment, type A does not interact with any environment and type C is related to the client-user of the station.

As the previous observations and explanations show, the four exemplary types of contextual variables are not mutually exclusive, canonical or exhaustive of what is permissible under CAS. In fact, they suggest an advantageously broad and rich range of contextual variables that CAS invites to model the environment (operation and network) and are limited only by implementation technologies. For example, the data background of a station may be of a significant contextual value for maintenance but may be limited by memory restrictions that a LAN device may have implemented. Naturally, contextual functions are advantageously used to provide useful information for efficient couplings, as explained below. Useful information In the human body, when an antibody identifies its target antigen ("you are an unfriendly substance"), it then successfully initiates to unleash a range of defense mechanisms against the antigen. Consequently, by analogy, useful information advantageously accompanies a contextual function CF sent to the searched interrogated CAS stations that immediately processes the useful information as part of the desired complex action.

The term "useful information" herein refers to information that the interrogation station CAS, in order to carry out the desired complex action, wants the searched interrogated station CAS to perform or perform. Useful information may be data that is to be processed or a function for data processing, or both, in the present are referred to as "instructions" for economy of expression. To illustrate the flexibility and capacity of . CAS answer, three different exemplary types of useful information for a searched interrogated CAS station are explained below. Useful information type A. Useful information are instructions for the sensor-interaction module, to measure a specified physical aspect of the operating environment and to send the measurement back to the base station. Useful information type B. Useful information is instructions for the effector module of an interaction to perform a specified act to stop the performance or of a specified act. Regarding the CF3 contextual function, the confusing logical instruction of the previous example shown, in a message with a useful information to determine power, all the stations that unexpectedly extract too much energy and whose clients are in risky credit, will have a suspension of energy righ now. This can be useful for managing emergency power situations where instantaneous response capability is required. Useful information type C. Useful information are instructions for manipulating context attributes with a conventional action (such as "place, remove, view and change") with respect to: (a) the contextual value of a contextual variable and (b) the contextual variable itself. An example action on the contextual value of a station's contextual variable is the instructions to replace the contextual value of the "billing plan" contextual variable (for example, from plan # 3 for a customer credited to plan # 9 for one with risky credit). In this way, the contextual attribute of "billing plan" is changed accordingly. An exemplary action on the contextual variable of a station is the instructions to insert a new contextual variable of "information related to measured voltage phase" or to delete the existing contextual variable of "client with risky credit" or replace the existing variable with a new one. For some physical aspects of the operating environment, a simple mathematical transformation of an electrical signal from the sensor will represent the new desired metric. In general, the implementation of instructions to change a contextual variable depends on the intelligence resident involved (that is, the platform of microprograms / resident physical elements and the implementation of the contextual variables subject to them). An exemplary case below simple, complex and intermediate illustrate the types and scope of implementations. In a simple case, if the contextual variables represent addresses in the memory of the stations that store or represent various measured physical aspects of the operating environment (ie, derived from the interaction module), the useful information is a new location in the memory of the station. Depending on the routing scheme of the station memory, the useful information is a new absolute address, or a new deviation base for indirect and similar addressing, which can be accessed with the new measured physical aspect. In a complex case, the useful information is a new subroutine code to be accepted by the station to overwrite the existing code. In an intermediate case, the useful information is new branch instructions for the subroutines residing in the station (or a new key for a function search table, or a new operand value for a subroutine, or a new parameter value that changes the functionality of the resident microprogram or its relation with the physical elements). In addition, useful information can be a routine self-contained that is simply executed by the interrogated station CAS (on a one-time operation basis), on its contextual attributes without requiring anything else from the interrogated station. CAS. Therefore, it is observed that a CAS message, in addition to having a contextual CF function, can also carry useful information that is a function (complete or in part). Of course, the useful information can simply be data and / or functions that are not related to contextual attributes - for example the desired complex action can be a patch to a program control (software) or software improvement for user interconnection of the station interrogated CAS searched. In this way it is observed that CAS a complex action desired (for example "all stations in the power supply # 7 whose clients are risky credit, the power supply is interrupted") all the stations in the NE area of a city , please send your latest information regarding ... "," we are sending the information signal (new microprogram) to all the stations that ... "), is effectively carried out by an efficient addressing scheme where the complex action desired is expressed in such a way that the relevant portions of the network (the "searched" stations identify themselves as relevant and act accordingly for the useful information received. Postponement - contextual direction To return to the analogy of the company meeting, the chairman of the meeting says "this is a complex motion, even if they decide who has the right to vote is not easy - please listen to my explanation and ask questions, then we will take a short break of 5 minutes to be considered and we will return to vote. " In other words, the identification of those qualified to vote purposely postpones a defined duration. As in the language of humans, which has time (past, present, future), when they ask "who ...?" the analog of the CAS network can similarly be "displaced in time". Although the interrogated station CAS normally generates its contextual address upon receipt of the CAS message (and in particular, immediately before the contextual function of the contextual attributes of the CAS station encounters), another variation takes advantage of the time perception of each CAS station . The useful information of the CAS message in collaboration with the resident intelligence of the CAS station uses the time of the CAS station to postpone the crystallization of the contextual address. For example, useful information is related to the time by crystallization instruction to occur at a particular network time in the future (for a time-aware station complemented) or for it to occur at the end of a particular delay after receipt of the CAS message (for a full or limited time-aware station). Following are several concluding observations about CAS before it moves to the preferred modality. The first observation observes that "identity" (which depends on a plurality of contextual variables, values and functions) resides in a multidimensional address space. There is a recognition that the plurality of dimensions (in contextual variables and values) and the relationship of these dimensions (using contextual functions, typically mathematical functions), as part of the definition of the point of view of (that is, what is interest for) the CAS interrogation station, and that eventually leads to the context for which the identity or contextual address is created by each interrogated station CAS by itself. The second observation is based on a continuation of the analogy of the company's meeting. Who presides the meeting can have a corporate "minutes book" (or summary equivalent) where is the list of all partners and the details of their partnership. Although you can read and determine and announce the names of those with the capacity to vote on a particular motion, etc., it is more if you ask, for example in a question "all those who are class B members, please stand up, etc.". It is conventional that a base station or other (sub) central intelligence in a TAS network maintain complete information about each element of the (sub) network and its relationships in a central database (or distributed tables) and use conventional programs on said database to identify stations of interest and to send messages to them. The patent publication of E.U.A. # 2002/0019725 Al (submitted by StatSIGNAL Systems, Inc.) is typical. Such a program uses SQL statements or boolean-derived operations applied to a database and other conventional techniques used in the database search or in obtaining data information. But although these conventional methods inefficiently use the bandwidth where, for example, communications are carried out through the implementation of technologies that must be abundant in processing resources. For example, in a conventional TAS network of a single RF transmitter that transmits to a plurality of receivers, the base station must first determine which stations it wishes to disconnect energy in (eg, investigate the operating environment) and then determine those 30 stations , then it must send the instructions to disconnect the power and said instructions must be sent (in sequence, in some implementations) to each of said stations, resulting in 30 units of useful message information 'separated (although identical). Using the CAS and only a CAS message (with useful information) which is sent because (1) the identification of the searched stations and (2) the processing of useful information is done all downstream in each station before reception of the (same, unique) CAS message. The third observation relates similarities with an IP-based TAS network. In such a network, each network interconnection is identified by a fixed and unique IP address (typically shown in a decimal format with a dot), either statically or dynamically assigned and organized in a hierarchical topology. Through a mosaic of masking, filters, routing tables and related mechanisms, a message (either single broadcast or multicast) finds its way to one or more of the proposed stations. The similarity of the CAS with the IP diffusion (or the diffusion of a marking witness) is only apparent. IP multicasting is defined (in RFC 1112) as the transmission of an IP diagram to a host group. Each IP multicast group has a unique class D address, which is used to identify it. Class D addresses vary from 224.0 (reserved) to 239.255.255.255. Multicasting is based on the concept of a group. Each station must express interest in receiving a particular data stream (when subscribing to be in a multicast group according to the internet group administration protocol). The subscription is made by specifying the class ID address used for a particular multicast (similar to tuning to a particular TV channel). The group is arbitrary in the sense that there are no predefined physical or logical connections between group members except for the demonstration of interest. But a multicast IP address is really a hierarchical routing address that expresses information to help the message "find" the way to reach its proposed destinations. In contrast, the CAS does not have similar subscription procedures and the contextual address does not have routing information or equivalent useful information because, among other differences, it is created by the CAS interrogation station upon receipt of the CAS message. The fourth of the observations indicates that TAS and CAS are better contrasted when comparing the analogy of "where?" of the TAS with the "who?" of CAS. The answer to "where?" (a "location question"), is and can not be other than (direct or indirectly), "there is" (a "location response"). The TAS address is similar to the location of an inventory item in a warehouse. The warehouse itself can be moved and the items within the warehouse can be moved relative to each other, but finally the storage and retrieval management of the items is in code, directly or indirectly based on their physical locations. The industry has worked hard to improve the TAS techniques but fundamentally, the improvement can not escape its nature because they are reductions in the stages ("superiors" that (directly or indirectly) recognize that the source station (by its communication representative) must know (at least some part of) "where" an article is (physically or logically, in relation to other physical or logical items.) In contrast, CAS's "who?" answer requires (at least) Two people conversing Identity depends on the person who wants to know (in particular, depends on their point of view or interest) and on one or more of the people to whom the question is asked (in particular, it depends on their personal attributes) (endogenous and exogenous) to form the context together.) Although "where" can be part of some conversations, a conversation (ie, a "dialogue" between two participants) is inherently more powerful than a reading unilateral of a static map of locations. By asking "who?" as explained in the present, the supersystem or the complex is advantageously the peak of expression and content where the expression of the desired complex action is "part and parcel" with "who". Very effectively, the message and content are "1" and in this way the conventional concept of "network address" is subsumed. As a final observation before the main explanation of the preferred modality, it should be noted that if only the implementation technologies - and not the CAS - limit the contextually driven sophistication of the contextual functions, variables, values, attributes to model (so physical, logical and otherwise), the identities will be advantageously searched for from CAS interrogated stations. Preferred mode for a supply installation telemetry wireless communication network The traditional and contextual addressing schemes - TAS and CAS - are conceptually explained mainly with the terminology of "stations" with some references to network devices. For the preferred modality, the terminology that is formative of "device" is used primarily. One reason is the following. The concept of "listening" requires attention, especially in a wireless environment. When solving, explaining conceptually the previous schemes, the "deafness" is defined as follows. A station that can not hear a CAS message (regardless of the reason, to the extent that the deafness is intentional) is not a CAS station (that is, it is not part of the CAS network) for the purposes of that CAS message, by definition. In contrast, a station is still a CAS station (that is, part of the CAS network) in a common technical vernacular, even if it does not listen (and can not hear in some versions and implementations of TAS), and a TAS message is not directed to her. A station needs only to be addressable TAS to be a TAS station and part of the TAS network. For example, if the TAS is a hierarchical IP addressing scheme implemented with routers, then the message for a branch of the hierarchy may mean that it will never be "heard" by stations in another branch. But all of such subsequent stations will still be considered as part of the TAS network. The previous contrast is derived from the different natures of TAS (where the sender knows "where" the message will be sent and CAS (where the sender does not know and does not care, "where" and asks each station to determine if In addition, the "deafness" of a station is implemented in the preferred mode because of the lack of a means to receive RF messages (that is, it only has RF transmission functionality). only recognizes realities in concrete implementations (such as cost considerations) but simplifies the explanation of the procedure of "homogenization" of networks (under "hybrid / inheritance" below) where the explanation based on "RF deafness" is applicable without modification to the CAS and TAS networks. In the recognition of the above and to better carry out the explanation of the preferred modality, with economy of expression and ease of understanding, the formative terminology of the "devices" is used in the preferred modality, with the use of subscripts [. ..] so that relevant distinctions can be made. Definitions: Base station, WAN device and LAN device the three main network devices - were introduced in the above. Below are amplifications and continuations of them. A base station in principle is not different from any other network device and so, for example, in itself it can function as a portal / representative of communication with another network (for example a base station of another network). But typically it is too "big" in its central intelligence and in its logical processing instruction, with its special responsibilities in the network, its own energy resources, etc., so that it is uncomfortable in a technical vernacular to call it as if it were a Typical network device such as a WAN and LAN device. And for this reason it is called "base station". Each network device has persistent memory (eg non-volatile memory) such as EEPROM, flash memory, hard drives) which store information such as routing set, application set, routing depth, PQM messages, power outage account , LAN and WA? parameters, etc., as these terms have been explained in the above. In the same way, a network device has some non-persistent memory (that is, it requires energy to maintain its content). The term "memory" herein includes in its generality both persistent and non-persistent types of memory, unless explicit reference is made to "persistent memory". Each network device has logical processing functionality (constituted as ASIC, FPGA, PLD, microprocessor, for example), which typically collaborates with its memory, to collectively form its "resident intelligence". The network device in the preferred mode usually receives power from a socket on the power line with which it interacts in the interaction module. See, the implementation example of the E.U.A. Copendent # 10 / 164,394 filed on June 10, 2002 entitled "Adapter for a meter", which is incorporated in the present in its entirety as a reference. The suffix [battery support] for a network device means that there is an emergency power source that is automatically activated in case of an alteration in the power line. The suffix [without battery support] means that there is no emergency power if the source of the normal power line fails. Finally some functionality is lost by a network device [without battery support] during an energy alteration. As indicated in the above, each network device is time conscious (that is, it has functionality to calculate the passage of time), but it is done in this way only if its logical relay instruction is activated. During a power interruption, only one network device [battery holder] remains aware of the time. In addition, each of the messages (packets) of timestamps of the network device sends, based on its time consciousness (complete or limited, as the case may be). Each network device has at least one functionality for RF transmission and some have transceiver functionality. The suffix [RF full] for a network device means that it has the functionality of an RF transceiver, while the suffix [RF deaf] means that it only has the transmission functionality RF (that is, can not receive). An exemplary endpoint in the preferred mode is the LAN device. In general, it is the combination of: (a) communication functionality in connection with at least (b) an interconnection of a single data source or with a single data receiver (the latter is a sensor or effector of the data module). interaction). Bearing in mind that an aspect of a "unique" source or data receiver is that which is also the "final" source or receiver of the same (and hence the term "end point") and having in mind (as observed John von Neumann) that there are no real differences between the data that is going to be processed and the instructions that process it (whether the processing is doing something or not doing something), that is, an instruction is a type of data particular), then the preceding definition becomes: the combination of: (a) communications functionally in coupling with (b) an interconnection with a final data source or with a final control point. The LAN device in the preferred mode for utility telemetry, is the combination of (a) RF communications functionality in coupling with at least (b) an interconnection with its interaction module which is a watt / hour meter that provides in a unique way data on the consumption of electricity on the energy line to which it is attached. In summary, a LAN device is coupled with its interaction module. The interaction module interacts with the operating environment of an energy grid through its sensor or effector linked to an energy line of the same. In the preferred embodiment, the principal examples of a sensor and an effector are, derogatorily, a voltage sensor and a remote power disconnect switch. Other interaction modules useful in the telemetry adjustment of distribution companies include damping sensors (for detecting inclinations or detecting inappropriate alterations of the electric fields, magnetic fields, temperature, sound, inversion of rotation of a mobile element); and effectors such as load shear devices, distribution equipment of distribution companies (eg, reservoirs, capacitor blanks), load control devices, fault indicators and a variety of other utility equipment that needs (de) activation of according to a desired complex action. The LAN is an RF local area network that has a plurality of endpoints, LA devices? Who communicates with a WA device? which operates as a portal for the WAN and the base station. Are there several types of LA devices? classified by its functionality. For its simplicity of expression in the present, a reference to a "LA device?" is simpler and implicit (that is, without a suffix between brackets [...]) is generally a LAN device, that is, without distinction to any particular functionality but with distinction to non-LAN devices. The suffixes { [battery holder] and [without battery holder]} They were explained in the above. When a LAN device has a suffix (with { [RF full], [RF deaf], [dull and mute RF], [WAN / LAN portal mode], [application custodian].}.), they want to indicate the following particular functionalities (or limits). A LAN device [RF full] has a complete RF transceiver functionality and "is" a "CAS station" for CAS purposes. A particular type of LAN device [RF full] can have the functionality to collaborate with a WAN device to form with it a portal connection between the WA? and the LAN. The combination is called "WA? / LAN device", for economy of expression in the present, although reference will be made to the WA device? and LA device? as required in the explanation. Such a LAN device [RF full] when said portal functionality is activated, it is stated that it is in portal mode and then it is referred to as a LAN device [RF full], [portal mode WA? / LAN]. The combination of the WAN device and the LA device? [Full RF] [WAN / LA portal mode?] Is sometimes referred to herein, for simplicity of expression as a "portal" WAN / LAN. "An implementation of a WA? / LA? Portal (with an optical portal between the WA device? And the LA device?) Is provided in the US application # 10 / 164,394 copendiente mentioned above. application "is the set of one or more LAN devices [deaf to RF]" less workable "which are immediately downstream of an LA device [full RF] [application custodian]" fully functional "(sometimes in this called "application custodian" for economy of expression) that has an "application software" to provide "intelligence" to it.Indeed, a "fully functional" application custodian "takes care" of minor stations when providing "Application custodian services" to them For example, the application custodian has the functionality to temporarily store messages received from one or more LA devices [deaf to RF] in its application set and to send said messages upstream, to improve the quality of time awareness of the LAN device [deaf to RF] under its "care"; "extending" the CAS to cover stations that are not "CAS (which is explained in the following, which include" hybrid / inheritance "). The LA device [RF full] [application custodian] maintains the traditional address (ie , Network ID) of each LAN device [deaf to RF] in its set of application. A LAN device [RF deaf] only has the functionality to transmit RF - can not listen to RF communications and is not a CAS station (subject to "participate" in the network explained in the following together with a LAN device [RF full] [custodian of application] and "inherited"). A LAN device [RF deaf] can be equipped to receive communications by a different means of RF (for example a wire or an optical port for attribution). A LAN device [dull and mute to RF] has no RF functionality and communicates with another network device by a different RF method. The WAN is a wide area network of RF WAN devices which act as representatives of communication between a base station and one or more LAN devices. For the preferred mode, each WAN device is [RF full] [battery support], but the suffixes - [RF full] [battery support] - are not expressed in the present by economy of expression. In other modalities, there may be certain WAN devices which are not as functional (for example a WA? Device [without battery support] or a WAN device [RF deaf]), but in the preferred mode, the WAN wants to indicate operation as a communication representative between a base station and the LANs, and in this way each WAN device has Completed communications and other functionality. A hybrid network is described that involves a base station that is coupled to a LAN through a communication representative of an intermediate WAN between them (see Figures 4 and 5). The implementations of each WAN and LA? they depend on the subject commercial market and the physical field factors, but selections (and different consequences) include: the frequency band, communications protocols, government regulations, encryption and compression schemes, modulation techniques, standard bodies, etc. A preferred embodiment has the WAN operating in the 220 MHz band with a technology that is agile-frequency ultra-narrow-band GFSK (whose channels are collectively referred to herein as "WA communication channels?") And the LAN operates in the 433 MHz ISM band with narrowband technology (the channels are collectively referred to herein as "LAN communication channels"). An LA device? (either [RF full] or [RF deaf]) and a WAN device operate, respectively on the communication channel LA? in operation and the WA communication channel? in operation. All of these communication channels are motivated by the manufacturer. A "business ID" identifies the business with a business interest in a portion of the network (ie, one or more than LAN devices, WAN devices and base station). In the preferred modality, the first (business relationship) is the business of a power distribution company that supplies electricity to its customers, whose sensor-interaction module is the combination of meter-electro-mechanical-optical-electrical converter. watt / conventional hour mentioned above (with occasional reference to a (second) business of a gas distribution company that supplies gas to its customers, whose sensor-interaction module is a meter for conventional electromechanical gas measurement). A business ID may seem to be (and obviously can be) "motivated by business", but for the preferred modality, it is motivated by the manufacturer, for simplicity of explanation. In other words, in the preferred mode, even after the first business takes ownership (and even ownership) of the network devices (for example the base station, a LAN device to deploy for a client), the manufacturer still controls exclusively who can operate in the network (in this case, the first business). The alternative modalities contemplate the sale, rent or delegation of some other type of control by the manufacturer of the contextual attributes "Business ID" to the first business as a lesson of the business model used by them. Once the attribute control Context of business ID becomes motivated by business in the hands of the first business, then in turn, the first business can rent or make some other business arrangement with a second business to manage the respective business interests in their network devices. For example, the first business may decide to "share" the RF communications functionality with the second business and to do this each one may have their respective business interest, which is explained below. As indicated above, in the preferred embodiment, a LAN device is the combination of: (a) an RF transmission communications functionality in coupling with at least (b) an interaction module (which is a watt / hour). The first business (involved with an electricity distribution company) and the second business (a gas distribution company) who share a customer can each have a legal and business interest in the same RF communications functionality as illustrated in the next example. Suppose that the first business (involved) is owned by your LAN device (with RF communications functionality) and the right to manipulate the contextual variable of business ID.

Subsequently, the second business arrives, equipped with its interaction module to measure its gas consumption of the client that is adapted to be coupled with the functionality of RF communications and want to share it. The first business leases the use of RF communications functionality to the second business. The business may share the use of RF communications functionality in an arbitrated array or share / schedule time. For conceptual consistency, a network ID can be uniquely assigned to each # 1 and # 2 LAN device for TAS purposes since, according to the general definition of the LAN device, each LA device? it is coupled to a final data source. The LA device? # 1 is the sensor / interaction module connected for electricity and the LA device? # 2 couples the sensor / interaction module for gas. • Imposing limits on the nature of business interests. They can be distributed so that any use (single or double) of the RF communications functionality is under rent by the manufacturer (with the concomitant rent charges for time or services provided in the network) or the businesses involved rent from the manufacturing and in turn sublet to second businesses. The alternatives include sales instead of rent. The modalities mentioned above that contemplate two businesses that share the RF functionality will have corresponding effects on the base station functionality, the management of the ID scheme of multiple businesses and the like (explained in the following).

No limits are imposed on the type of business - for example, a provision of meter and a management company (ie, one that provides the measurement and not the installation that is measured). As mentioned in the above, there are adjustments without distribution companies. For example, a business can be a security alarm company or a vending machine operating company (self-service). No limits are imposed on distributions between businesses. For example, businesses, in themselves or in collaboration with others, can operate on several base stations, one or more WAN devices, or one or more LAN devices (for example, the businesses of electricity and gas distribution companies on the scene). previous). Then the explanations and quantities are expressed in tabular form only for simplicity of expression of the same. There is no relationship between CAS and the rows, columns, tables and associated concepts based on the same found in database systems, database techniques, etc. Any apparent similarity between CAS and databases is misinterpreted due to the concepts of basic databases which are foreign to CAS. For example, as is clear from the previous review of the contextual variables, there is nothing in CAS that understands the concepts of normalizing data to facilitate updating and denormalizing data to facilitate recovery.

A CAS message from an inquiring base station has a contextual function CF that presents the "point of view" of the inquirer with the exemplary implementation in a tabular 8x8 bit format: TABLE 1 where . { I} , it is coded. { 0/1 } , Is NOT coded as 1 and otherwise ignored, and PB =. { 1/0} as expressed in the following in relation to the propagation bit. The above is idealized for ease of understanding (for example, some expressions require XOR in the implementation). A field . { I} It is white to express implicitly the [Y] (in recognition that the business ID of the base station and the station must match), so that the previous contextual function is a Boolean function of "Business ID And contextual variable 2 Y / 0 variable contextual 3 Y / 0 contextual variable 4". This is a CF2 type of contextual function • with the values. { ?,?,? } in the previous fields for the contextual variables 2, 3 and 4, in such a way that the contextual function (?,?,?) represents the identity sought. The contextual function is implemented by the resident intelligence of the interrogated station (CAS), which interprets part of the received CAS message so that they are boléano operators to process in the contextual interrogation attributes of CAS and in. { ?,?,? } . In other words, the implementation of TABLE 1 of a contextual function contemplates the collaborative finding of the CAS message received (in particular its contextual function) and the interrogated station CAS (in particular its resident intelligence). The implementations and alternatives of a contextual function are obviously possible. As mentioned in the above, the contextual function can be completely constituted by the CAS message (CF and useful information) in which it is simply executed by the interrogated station CAS. As another example, the contextual function can also be implemented by having the interrogated station CAS stored a set of predefined functions and the contextual function of the CAS message, stores a set of predefined functions and the contextual function of CAS message is simply a function selection. Regardless of the implementation, the end result is that the interrogated station CAS executes the selected function or is provided by the interrogation station CAS, in its context attributes to determine the CAS address / identity. A typical network device (LAN or WAN) has a plurality of contextual attributes based on contextual variables and contextual values for them. The number and variety of contextual variables obviously depend on design selections for potential desired complex actions. Different types of seasonal contextual attributes will be discussed below, in "an exemplary manner, with reference to a tabular format of contextual variables: CVar 1 identifies the manufacturer and the context variables CVar2-CVar4 are the contextual variables motivated by the manufacturer or the "manufacturer's properties" of the station, the exemplary manufacturer's properties include a device type, microprogram version, version of physical elements. The manufacturer's properties are attributable in a scheduled manner. In contrast to the manufacturer's properties, CVar6-CVar8 are context variables driven by business and are called the "seasonal business variables" of the station. Exemplary business context variables include Meter Serial #, customer billing plan #, power supply line The attribution of contextual values to business contextual variables is done by programming (by instructions or manual handling of the base station) or detection (interaction module sensor). All the contextual variables (whether the manufacturer's properties or variables / values / contextual business attributes) are subject to be addressed contextually, although, as indicated in the above, they can be manipulated by different parties. The contextual attributes of a typical station can assign the first line to the manufacturer's properties, the second to the business context variables (maintaining context values to form contextual business attributes). Thus, represented with exemplary contextual and symbolic variables: Contextual variables of a CAS station are initially allocated in a programmed manner with context values so that the properties of the station manufacturer and the business context attributes of a CAS station can begin as: The previous implementation (TABLE 1) of the Boolean function of the contextual function can "process" in at least three entries of a row of the station's contextual attributes, the first entry is reserved for what are effective administrative security purposes . Then there are three exemplary desired complex actions. These are, respectively, detection, realization and change of a contextual attribute (when providing a value new contextual for a contextual variable). The first desired complex action of the power distribution company DEF is "ask the voltage levels of all the stations in the power line feeder # 75A". This can be implemented by the base station that sends a CAS message with the following contextual function CF, where. { ?,?,? } is . { 0.0,75A} that is (0.0, 75A) represents the identity sought, and the useful information is instructions to read and send back the measured voltage levels of all the stations searched.

The second of the desired complex action is "turn off All stations in the billing plan # 7"of the XYZ electricity distribution company can be implemented by the base station that sends a CAS message with the following CF contextual function where {?,?,?} is { 0,7,0.}., that is, CF (0,7,0) represents the identity sought and useful information is instructions for changing the remote power disconnect switch. logic The third complex action is "all the stations which are in the billing plan #A, also in the billing plan #B", of the electricity distribution company PQR. This can be implemented by the base station that sends a CAS message with the following function contextual CF, where. { ?,?,? } is . { 0, A, 0.}. , ie CF (0, A, 0) represents the identity sought and useful information are instructions to change the contextual attribute of "billing plan" (from #A) to #B.

The result can be that those stations (one or more than one or none) that have identities searched in the three previous examples can, respectively, detect, carry out and have a changed contextual attribute, as described in the above. For simplicity of explanation, the concept and terminology of the CAS stations are used in these examples - in the implementation, these stations can be LAN devices (of the communications network) that they couple their interaction modules that have the appropriate sensor or effector and other required infrastructure, as the case may be. The above is exemplary and evidently the CAS can be enriched with more contextual variables (motivated by the business or by the manufacturer). More examples are given below.

To adapt the additional contextual variables to CVar5-CVar8, it will require obvious changes to the previous implementation of the CF contextual function and the CAS message format. The above is for a typical network device (for example a LAN device). The nature and proposed role of a network device will suggest the appropriate "richness" of its contextual variables. A network device that operates purely as a communication representative (for example, a WAN device) may have few contextual variables (for example those related to manufacturer properties for fundamental network infrastructure management purposes). To continue with the previous example of the Double business interests in RF communications functionality, one network device can have context variables which are "motivated by business # 1" and others which are "motivated by business # 2". For example, there may be an RF communications functionality in a residential customer site that is coupled with an interaction module of a meter that measures the electricity consumption and an interaction module of a meter that measures gas consumption. The business of the gas distribution company and the business of the power distribution company "shares" the RF communications functionality as a communication portal for their respective meter interaction modules, but for the purposes of network TAS addressing, each one has its own LAN device [RF deaf] to couple its respective interaction module. Therefore, in context attributes, the additional lines are completed for the second business: with obvious corresponding changes in the CF contextual function. Corresponding to the technical and business situation in a customer's place, the base station has a list of business IDs (electric company DEF and gas company GHI) that it supports. Therefore, the CAS (and the business contextual attributes) can support two or more business IDs to fit two clients / owners / tenants. To avoid "avalanches" in an RF communications network where all messages are broadcast by RF, mechanisms are provided to limit the "avalanches" of CAS messages (which would be endlessly repetitive and useless RF retransmissions). Two examples of limitation mechanisms are explained below, the propagation bit and the routing depth. Bit of propagation. A PB is a bit of propagation whose use is explained with exemplary fact situations. The situations where the PB is clarified, includes the following. • When a base station sends CAS messages on the WAN, it means only for WAN endpoints (ie, messages will not be retransmitted by RF to the LANs), for example, sending network time to devices WAN or instruct a WA device? to broadcast RF from its current time to the respective LANs. • When the WA device? first discover a LAN device (in the "plug and play" procedure explained below), they broadcast an instruction by RF (since they do not know the LA device?), asking if it switches [portal mode WA? / LA]. When a LAN device knows that it is attached to a WAN device as part of a WAN / LAN device, will it send everything to the WA? through the interconnection of the optical port in the patent application mentioned above exemplary (instead of broadcasting by RF by air). This instruction may not be broadcast by RF to other devices that are not attached to the WAN devices. Situations are where PB is established, include the following. • When an instruction is broadcast by RF to all devices on the LAN and WAN. Depth of routing The "depth of routing" is a measure of the "separation" between a LAN device and its WA? / LAN portal with the WA ?. For a CAS message, the routing depth is the number of separation "levels". For an upstream TAS message, is the number of LAN devices that the message must "jump" to reach the WA? / LA ?. Each LA device? It has a depth of routed (determined by its topological position in the routing path in its LAN, which is the "topological proximity" to the WA device, counted in the number of intermediate stations). Each message will be identified with the routing depth of the station that is transmitted to it. When a LA device? receives a downstream message (TAS or CAS), it will only redistribute by RF if the routing depth of the message is less than its own, since these messages only propagate adequately downstream (away from the base station / portal). For example, if a first station whose routing depth = 6, broadcasts a message by RF and a second station whose routing depth = 7 takes and retransmits the RF, the first station will receive the redisclosed RF message but will be inert to it due to that the redisplayed RF message originates from the second station that is downstream (i.e., the routing depth of the second station is greater than its routing depth). When a station receives an upstream message, the depth of dynamic relationship routing is obviously inverted. Each downstream message, whether addressed in a traditional or contextual way, will be recognized or passed along (by an RF broadcaster) by a station whose routing depth is greater than that of a message downstream. Each message traditionally directed upstream will be recognized or recognized or passed from one to the other upstream (by an RF broadcast) by a station whose routing depth is less than that of the upstream message. "Plug and play" The term "plug and play" colloquially describes the automatic association procedure by means of which new LAN devices and WAN devices are deployed and become network participants by automatic detection and auto-configuration and with manual effort minimum. In essence, the network, through a "plug and play" procedure, monitors itself and automatically attempts to establish new communication links and "repair" broken communication links. A LAN device or a WA device? new ones are deployed (either in the name of the business) when they are connected by the installer to the relevant interaction module in the field - an electric energy meter / receptacle in the preferred mode - and are activated in this way. An example of implementation is the application of E.U.A. # 10 / 164,394 copendiente mentioned before. With respect to the concept and the terminology, a network device (a device LA? Or WA?) Is "associated" to the network when it is a functioning participant of it, as recognized by the base station. Sometimes in the present, as a matter of terminology, a network device becomes associated with a component of the network when it assists in understanding in a particular way. In particular, the "plug and play" procedure attempts to associate a WAN device not associated with the base station; an attempt to associate an unaffiliated LAN device (either [RF full] or [RF deaf]) to a LAN device [RF full] (already associated) (whether the device is already associated and part of a portal WAN / LAN operating as a communication representative for the WAN, or not) and finally through the base station, so that the base station recognizes the non-associated network device as a network participant. In addition, there are two major exemplary versions of "plug and play" distinguished by the "residence" of significant portions of intelligence used to carry out important aspects of association: (A) "driven by the base station" (where the intelligence significant resides upstream of a non-associated network device, mainly in the base station) and (B) "driven by the endpoint" (where, in relation to the modality driven by the base station, more than the intelligence resides current below the base station, mainly in the non-associated network device). These two versions are not absolute opposites and differ as subject of degree depending on which aspects of association are considered more important than others and where the intelligence for it is distributed in the network. An important aspect of exemplary association is the determination of the routing path - who selects for a LAN device not associated with the LAN device [RF full] (associated in advance) as its immediate upstream communication representative or link (or finally the portal) WAN / LAN), with which to associate. If the base station is selected, the "plug and play" is considered as "driven by the base station" and if it is selected from the non-associated LAN device, the "plug and play" is considered "driven by the end point" . The selection is based on physical communications, topological and criteria related to resources (the examples of which are provided in the following). The selection of "driven by the base station" or "driven by the end point" or some intermediate version between them presents obvious compensations. For example, the advantage of "driven by the end point" is that it is the essence of a local decision, and is best decided locally, instead of moving and filling the base station through other traffic. But a local decision, if it is parameterized too closely, it may be unable (through ignorance) to anticipate an upstream "bottleneck" and thus a local decision may worsen the functioning of the regional network (which in turn reduces the effectiveness of that local decision). The routing path and other concepts mentioned above are explained in the following. After introducing definitions common to both versions of association of "base station driven" and "end point driven", each version will be explained in a manner associated or not associated with (1) a WAN device, (2) a LAN device [ Complete RF] and (3) a LAN device [deaf or omitted to RF]. Definitions "Network ID" is the unique identifier of an interconnection of the different aspects of CAS of the network - it is the address used for the traditional addressed messages (ie SOURCE), or DESTINATION in Figure 1) . A network ID is motivated by the manufacturer and is uniquely assigned to each network device (either a LAN or WAN device or a base station) and resides in its persistent memory. The network ID assigned to the base station is called "base station ID" for ease of understanding. A WAN device leaves the factory with its ID of single network, the business ID it supports and a list of WAN communication channels for scanning and other WAN parameters. A LAN device leaves the manufacturer with its unique network ID, the business ID it supports and a list of LA communication channels? for exploration and other parameters LA ?. In the case where two are supported (or more) Business ID, there may be a single physical device in implementation but for the purposes of the network of this invention, this conceptually will be two (or more) LA devices ?. An "association beacon" is a message broadcast with the aim of "finding" non-associated network devices to initiate the "plug and play" procedure. The base station periodically broadcasts a WAN association beacon to "find" non-associated WAN devices and a LAN device [of complete RF] periodically broadcasts an association beacon LA? to "find" LA devices? not associated The association beacon WA? from a WAN device it includes the following information: one or more of its supported business IDs and its WAN communication channel in operation, with a list of time intervals during which a WA association request can be sent? for a WA device? not associated in response to the WAN association beacon. The number and duration of the time interval can be adjusted dynamically (locally, regionally or by the base station on a broad network basis) based, for example, on past experience as a function of traffic levels, communications interrupted and similar. The LAN association beacon of a LAN device [RF full] (regardless of whether or not it has the functionality to collaborate with a WAN device to form a WAN / LAN portal) includes the following information: Network ID, LAN communication channel operation, one or more supported business IDs, resource indicator, routing depth, base station ID and network time. The response of an ns LAN device associated with a LAN association beacon is a LAN association request, which has the device network ID, the manufacturer properties, and the business context attributes. The "signal quality" received from a communication channel is a metric of one or several messages received through it that depends on the bit force indicator (BSI), the received signal strength indicator (RSSI), and / or other physical communication aspects of the message. The quality of the received signal is measured, calculated and maintained by the network device that receives the message. The "acceptable signal quality" (and the components such as "acceptable RSSI" and "acceptable BSI") of each of the thresholds motivated by the manufacturer against which the signal quality of the message is compared in a "plug and play" decision-making procedure. The "resource indicator" is a measurement system maintained by a network device, about how busy it is (for example, a function of the size of its application set, routing set, traffic (background), etc.) or equivalent, for the purpose of "plug and play", what amount of communications and processing traffic can be handled. The "acceptable resource indicator" is a threshold motivated by the manufacturer for a network device. The "depth of routing" is introduced above, it is the # of devices (or levels, "jumps" or equivalents) from a LAN device to your WAN / LAN portal. A LAN device [RF deaf] has its routing depth set in a large number (for example 15) to represent its inherent inability to receive messages. An unattached LAN device [RF full] has its routing path initially set to be and then changes during the "plug and play" procedure, which is explained later. But, in particular, a LAN device that is part of a WAN / LAN portal starts, and remains fixed with a routing depth of zero.

The "routing set" of a network device (typically a WAN device or an LA device? [Full RF]) is the set of all LA devices? downstream (either immediately downstream or not) to which the traditional message received will be sent. Such a LA device? Downstream can be [Deaf to RF or omitted] in the following situation. If it is a member of the LAN device application set [Full RF] [custody application], then it is also a member of the previous routing set for the following reason.

Although the LA device? [Deaf to RF] in itself can not receive any message, your LA device? [Full RF] [custody application] can receive "in your name" (as explained in "hybrid / inherit" in the following). There is usually no necessary identity between the routing set of an LA device? [Full RF] [custody application] and its application set. The "routing path" of an LA device? [Full RF] (or a WA device or base station) is the sequence constructed from one or more downstream network devices to which a traditional message will be sent. A downstream network device can be identified with a business-driven identifier (for example, a business contextual attribute or a measured serial number) or an identifier motivated by the manufacturer (for example, network ID) but regardless of the identification means, the routing path is used only for sending traditional messages and is not part of the CAS. As elaborated in the following, the sequence is constructed for a downstream LAN device given by identifying the "best" LA device? immediately upstream [RF full], where "best" is determined by exemplary criteria such as physical communication qualities (such as signal quality), topological perform characteristics (such as depth of routing) and other criteria to minimize the load in the network in a general or regional manner (LA? upstream [RF full] devices (immediate or otherwise) as reflected in their resource indicators), such criteria are based on prior experience or projected values, or in both, limited only by the implementation technologies. In the following exemplary explanations, the term "best" sometimes, for ease of explanation only, is simplified to involve one or two of the preceding criteria. A typical routing path is < base station, WA device ?, LA device? [Full RF] [portal mode WA? / LA?], LA device? [Full RF] (better), LA device? [Full RF] (best)], LA device? [Deaf to RF] > .

The base station maintains a copy of all the routing paths constructed (i.e., the routing path of each applicable network device) or the information necessary to create them (e.g., maintains the routing sets of each network device and the Routing depth of each device in it). This information is used to update the routing set of the device, to perform diagnostics, etc. The base station also maintains the candidate_routes for a self-healing version (which is explained later). The "power cut" is an alteration to the energy that lasts more than one period (motivated by the business), a "period of power cut" and that drives the object device to send a "power cut message" to the base station. A power cut can obviously only be detected by a LAN device (battery backup) because the clock logic instruction of the network device needs to be activated to measure. A LAN device [without battery backup] can not calculate the. the passage of time during an alteration of energy. Power outages are discussed primarily in PQM / AMR in the following, but are introduced here for their role in the "self-healing" aspects of "plug and play" (ie, after a power outage).

Exemplary LAN parameters include: a) beaconing interval (the period of periodic diffusion of the LAN device of a LAN association beacon, between 1 and 255 minutes, with 0 to disable) b) installation closing time (maximum time in which an unattached LAN device will wait after you send your LAN association request, for an appropriate response, between 1 and 255 minutes, with 0 to disable) c) ordinary annealing close time (if a cut message is not detected) energy, maximum time that elapses for reassociation, between 1 and 255 hours, with 0 to disable) d) closing time of serious re-association (in case of a serious problem, that is, if a power cut message is detected, the maximum time that elapses to re-associate, in hours, with 0 to disable and the duration will be much greater than a closing time of ordinary reassociation). e) acceptable signal quality and acceptable resource indicator Exemplary WAN parameters include: a) WAN communication channels to scan; and b) related parameters (for example the period of) base station maintenance protocol to adjust the RF frequencies in case of drift (if they meet with the regulatory considerations of RF). The WAN and LAN parameters are typically motivated by the manufacturer but can be motivated by the business (with proper distribution with a sophisticated business). Through a sequence of expected links (they operate from the physical layer OSI upwards, which include those related to the modulation scheme, the frequency band, timing and other conventional techniques), each message sent on the network is in effect, "signed" by the conventional means with a "monogram" or a "signature" that identifies it that originates from said network, so that the stations belonging to said network will recognize it as one of the "own" and will continue in the process. For the preferred embodiment, this "signature" is referred to herein as "signed network packets" (to distinguish them from other network operation protocols or different communication protocols). I. Base station powered by "plug and play" This version has three main processes: (1) deploy a WA? / LAN device, (2) deploy an LA device? [RF full], and (3) deploy a LAN device [Deaf to RF]. In turn this will be explained, followed by an example. (1) Deploy a WAN / LAN device 1. The network of the WA device? is enroled in ID at the base station by the business. 2. The base station periodically broadcasts a WA ?. 3. When the WAN / LA? Device is deployed, the WA device? it will explore its list of WAN communication channels in search of signals that have an RSSI at least acceptable and among those channels, the presence of signed network packages. In the first of said channels, the WA device? not associated, for a while (programmable) will listen for a WAN association beacon that has its business ID (from the WAN device). If you do not listen to this WAN association beacon in a timely manner, try the next one of those channels. If there are no more such channels, restart the scan mentioned above. When the WA device? listen to a WA association beacon ?, send a WA association request message? to the base station (in one of the time intervals offered in said WA association beacon?). 4. In parallel with the procedure of stage 3, the device WA? ask your LAN device to determine if it is in [portal mode] (the LAN device always leaves that mode after a power interruption). If the LAN device is not in [portal mode], the device WAN sends a "set portal mode" instruction, and the LAN device in response moves to [portal mode] (ie, it becomes a LAN device [RF full] [WAN / LAN portal mode]) and returns a message from association request LA? to the WAN device, which in turn relays it to the base station. 5. When the base station receives a WA association request? of a WA device? enrolled but not yet associated, it will request the owners of the WAN device manufacturers and then add the base station ID to the contextual attributes of the WAN device. 6. When the base station becomes aware of the LA device? (through the LAN association application), you will: a) ask a question about obtaining your manufacturer's properties; b) add the base station ID to its context attributes; c) establish other business attributes; d) establish its parameters to AMR and PQM (explained later); e) set its routing depth to zero. The device WA? / LA? (until then) not associated now is associated with the network, and can be considered as an operational WAN / LAN portal. The LA device? [Full RF] [WAN / LA? portal mode] (new associate), in its communication channel LA? in operation, periodically broadcast its LA association beacon? in "search" for LAN devices not associated in the field, inviting them to a "plug and play" procedure so that they start again from it. Yes the LA device? [RF full] [WA? / LAN portal mode] is unable to send upstream messages received, to the WA device? after exhausting the attempts (a programmed number of them), it will stop sending LAN association beacons and will no longer recognize message / package that it receives. (2) Deployment of the LA device? [RF full] (by itself and not as part of a WA device? / LA?) 1. Is the LA device deployed? [RF full] and it is determined if previously it has not been associated (for example if it does not have a base station ID value in its contextual attributes that have been the result of a previous association). 2. If the LAN device [RF full] has not been previously associated, listens for its beacon interval and registers in a list those association beacons LA? who hears that they meet the following criteria (the list is considered complete when at least one qualifying message and the beacon interval has expired): a) the received signal quality is greater than the acceptable signal quality; and b) the business ID of the LAN device [RF full] is between the list of LA association beacons? of business IDs supported. 3. If the LAN device [RF full] has been previously associated and is in the list of association beacons, the LA device? [Full RF] which is previously your immediate predecessor (ie, is immediately upstream) of the communication representative, will be selected to maintain it and continue normal operation, and will advance to the subsequent "plug-and-run" procedures. . The LA device? [Full RF] selects the best candidate from the list of LA association beacons? which has received, based on the following sequential factors: a) the lowest depth of routing; and b) if the routing depth is the same, the best received signal quality; 5. The LA device? [RF full] sends a message of Immediate_Proxy_Found (immediate representative found) (after changing the ADDRESS the source of the upstream TAS message that is the network ID of the selected candidate) over the communication LAN communication channel selected candidate. 6. The selected candidate, on receiving the Immediate_Proxy_Found message, increases it by adding its received signal quality to it and sends it to the base station (ie, the received Immediate_Proxy_Found message is modified to include signal quality measurements received by the selected candidate and the LAN device [RF full]). Once the LAN device [RF full] has selected a candidate, you can learn the network time from the candidate association beacons and can coordinate your time awareness accordingly. 7. When the base station receives an enhanced Immediate_Proxy_Found message for a LAN device [RF full], it will determine the routing path according to its criteria, which may include factors that exceed those considered in stage 2 above. It is considered that the message Immediate_Proxy_Found increased and the information contained in it but that it is not compelled to accept the selected candidate. When determining the routing path, it will then send a Routing Set_Add message (set, add routing) to each device in the routing path to establish a routing path with the LAN device [RF full] (these messages will be sent one at a time , waiting for each device to respond, working from the top of the trajectory of routed, down). If the LAN device [full RF [is already known for the base station (due to a previous association), the base station will first perform certain "internal cleaning" as follows. It will suppress the previous routing path when sending a Routing Set_Delete message (delete routing establishment) to each device in it, before establishing a new routing path (deletions are made upwards from the bottom of the routing path, waiting for each device to respond in turn). After a message is sent Routing Set_Add (add routing establishment) empty to the LAN device [RF full] to clear its routing set, effectively cutting out any sub-trees, forcing each subordinate device to re-associate when starting its respective individual "plug and play" procedure. 8. The base station performs the following with the LAN device [RF full]: a) add the base station ID to its context attributes b) ask its context attributes to obtain its manufacturer properties c) set its other context attributes d) establish AMR parameters and PQM parameters (explained later) e) set its routing depth to zero f) verify / set its correct routing depth for its location inserted in the routing path. The LAN device [RF full] is now associated. 9. If the LAN device [RF full] does not receive a base station ID or any other appropriate response within the closing time of installation since its Immediate_Proxy_Found message is sent, it will delete the selected candidate from the list, and continue with the stage 4 previous. If the list is empty, it will continue with stage 2 above. Once the LA device? [RF full] has received the base station ID, and if its routing depth is less than 15, will it periodically start broadcasting its LA association beacon? (devices with a maximum routing depth can not route messages), "searching" for LA devices not associated in the field. Yes an LA device? [RF full] [portal mode WA? / LA?] Is unable to send messages upstream or direct messages upstream, receive, after exhausting (a programmed number of) retries, will stop sending the LA association beacons? and it will no longer recognize any package that it receives. The LA device? [Full RF] will continue to forward the message until the ordinary annealing close time elapses, by which time it will be considered likewise it is no longer associated and will initiate the association procedure in stage 2. If the LAN device [RF full] returns to try to send its upstream packet and succeeds before the ordinary annealing close time has expired, it will continue operating as normal. Any failed message is held by the LAN device [RF full] (and is handled accordingly as "lost messages" later). When the LAN device is weakened by the reacquisition of energy, it is assumed that it is still associated. When you realize that this is not the case, if you weaken in a power supply after a power outage, then you will perform the "plug and play" procedure using the close time of serious annealing. (3) Deployment of a LAN device [RF Deaf] The routing depth of a LAN device [Deaf to RF] is motivated by the manufacturer to be with a large number (for example 15) which means that it will not attempt to relay messages as a communication representative because it is too far from the WAN / LAN portal. 1. The LAN device [RF Deaf] is displayed. 2. The LAN device [RF Deaf] sends a Reporting_In (report) message, which includes your network ID, properties of manufacturer and business ID, and is repeated as follows ("Reporting_In Schedule"): a) immediately at the start; b) every 5 minutes during the first hour; c) every hour during the first day; d) once a day later. 3. Each associated LAN device [RF full] that listens to a Reporting_In message with a business ID that is the same as its business ID, will send a Routing_Candidate message (route candidate) to the base station that includes: a) its Network ID, business ID and manufacturer properties; b) the RSSI observed while the Reporting_In message is received; c) the BSI observed while the Reporting_In message is received. 4. When the base station is a Routing__Candidate message from a LAN device [RF full] for a LAN device [RF deaf], it will wait for a period (programmable) to see if any of the messages from Routing__Candidate are received for the same LAN device (deaf) After this wait, the base station will select among the candidate LAN devices [RF full] the one that best "allocates" the LAN device [RF Deaf] and that is immediately upstream of the communication representative, according to the ordered criteria: a) better RSSI over acceptable RSSI (if there is none, an error will be presented and the device will not be associated); b) RSSIs are the same, select one with better BSI; c) the precedent is the same, select one with a lower routing depth; d) if the precedent is the same, select one with the smallest routing set. 5. Once selected, the base station builds the routing path with the LAN device [RF deaf] and instructs each LAN device [RF full] in the routing path to the LAN device [RF deaf] to add it to its routing set to the network ID of the LAN device [RF deaf]. 6. The selected LAN device [RF full] is instructed by the base station to add it to its application set, the network ID of the LAN device [RF deaf], that is, it performs the selected LAN device [RF full] to the application custodian of the LAN device [Deaf to RF]. 7. The LAN device [Deaf to RF] will send an AMR information report according to the "Reporting_In Schedule" which will be passed upstream by your custodian of application. The LAN device [RF deaf] is now associated. The base station is built to create sufficient density of interactive communications (that is, the number of messages it sends over a period of time, for which it waits for responses) that will be detected when something goes wrong with any LAN device [Full RF ] particular or WAN device. Consequently, there is no need for such devices to "report" to the base station. In contrast, the Reporting_In message and the Reporting_In program are required for the LAN device [RF deaf] because the base station needs to know if it is still participating in the network. It is noted that stage 4 is based solely on the performance of RF communications. Alternatively, there may be hybrid criteria, for example after an acceptable RSSI, the base station decides, based on factors other than pure RF performance. Example of a base station powered by "plug and play" An example will be explained along with figure 5. Each network device (WAN device, LAN device) has context attributes which, in tabular format, have a first row of properties of manufacturer and a second row of business contextual attributes.

The LAN / WAN device starts with a set of blank routing device-LAN. [RF full] starts with a blank application set The LAN device [RF deaf] does not have an application set For a WAN device with network ID = # 99, its business context attributes and manufacturer properties are initialized with values for: For a (first) LAN device attached (physically) to the WAN device # 99: LAN device [RF full] (network ID = # 21) starts with context attributes of: Your routing depth will be set to zero (that is, it is at the same level as the WAN device # 99) Your routing set and application set start in white Before a LAN device # 21 (through an optical interconnect with the WAN device # 99) it identifies itself with the base station with its contextual attributes and upon being authenticated by the base station, then: The base station adds an additional line to the contextual attributes of the LAN device # 21: The WAN # 99 routing set has # 21 entered by the base station.

For (another) LAN device [RF full] communicating with the LAN device # 21: The LAN device [RF full] (Network ID = # 31) starts with the context attributes of the LAN device # 31 for: Its routing depth is set to be one (that is, one level below the WAN device # 99) Your routing set and your application set start blank On the LAN device # 31 (to the LAN device # 21 and then via the WAN device # 99) it identifies this way same with the base station with its contextual attributes and is authenticated by the base station, then the base station adds an additional line to the contextual attributes: The routing set of the LAN device # 21 and # 99 have both # 31 introduced by the base station. The LAN device # 31 is a LAN device [RF full] [application custody]. ********* For the LAN device [RF deaf] # 91 The routing depth set to 15 starts with business context attributes for: The LAN device application set # 31 has # 91 entered by the base station The WAN device routing set # 99 has # 91 entered by the base station The device routing set LAN # 31 has # 91 entered by the base station From (another) LAN device [deaf to RF] # 41: start with contextual attributes for: Its routing depth is set to 2 (that is, two levels below the WAN device) It does not have a routing set or application set (it is a LAN device [RF deaf]) Before a LAN device # 41 that sends a message to the base station (via LAN and then WAN) and by identifying itself with its contextual attributes, and being authenticated by the base station, the base station adds an additional line to the contextual attributes: The base station decides (based on criteria physical and logical) link the LAN device # 41 to the LAN device # 31 (instead of the LAN device # 21). The routing set of the LA device? [application custodian] # 31, the LA device? # 21 and the WAN device # 99 have, each # 41 introduced in them by the base station. II. Endpoint driven by "plug and play" This version has three main procedures: (1) deploy a WAN / LA device ?, (2) deploy the LAN device [RF full], and (3) deploy a LAN device [Deaf to RF]. In turn this will be explained, followed by an example (with figure 6) as indicated in the above.

The main exemplary difference between the "endpoint driven" version and the "base station driven" version above is the location of the intelligence that decides the routing path. Because the remnant aspects and mechanisms are the same, the following is an abbreviated summary of the three main procedures because of their close identity with the "plug-and-run" procedures "driven by base station". The base station periodically sends a WAN association beacon that "searches" for non-associated WAN devices. (1) Deployment of the WA? / LA device? 1. When the WA? Device is deployed, it scans its WAN communication channels in the list for a message which is (or has) signed network packets, displays a short list of said channels, selects a channel based on the best received signal quality (and other criteria) and returns a WAN association request message. 2. Does the WAN device determine (through its optical port, in the application of E. U: A: # 10 / 164,394 mentioned above, exemplary) its LA device? and upon receipt of an appropriate response, place the LAN device in portal mode, that is, it becomes an LA device? [RF full] [WAN / LAN portal mode]. After the LA device? send a LAN association request message to the WA device? which is retransmitted to the base station. 3. After association with the base station, the LA device? periodically send a LA association beacon? and listen for a network response to the - LAN association request from any non-associated LAN device. (2) Deploy the LAN device [RF full] (by itself and not as part of a WA device? / LA?) During its beacon interval, the LA device? listen in search of LA association beacons? have a matching business ID, and those that have at least acceptable signal quality and an acceptable resource indicator. Among such candidates, the LA device? selects the best one (regarding the function of received signal quality, resource indicator, routing depth minor) to be your immediate upstream representative and send your LAN association request. in the LAN communication channel in operation of said selected LAN device. That network ID of the selected LAN device will be the source address of the LAN association request. (3) Deployment of the LAN device [RF deaf] The procedure may be the same as for the base station driven by "plug and play" indicated above. Example of an endpoint driven by "plug and play" An example will be explained along with figure 6. Each network device (device WA ?, LA device?) Has context attributes which, in tabular format, have a first row of manufacturer properties and a second row of business contextual attributes. The LA? / WAN device starts with a set of blank routed LA device? [RF full] starts with a blank application set The LAN device [RF deaf] has no application set The base station has a list of supported business IDs and periodically broadcasts a beacon of WAN association with a list of empty time slots. For a WAN device it leaves the manufacturer with a network ID = # 100, a list of WAN communication channels and their contextual attributes initialized with context values for: Your routing set starts blank When the WAN # 100 device is deployed, it scans its WAN communication channels in the list for those that have WAN association beacon messages and then selects the best container for signal quality (and others). factors) to return a WAN association request. The base station, WAN device # 100, is associated with reception For the (first) LAN device that is part of a WAN / LAN device: The LAN device [Full RF] [WAN / LAN portal mode] (Network ID = # 43) starts with the business' contextual attributes of the LAN device # 43 Its routing depth starts at zero (that is, it is at the same level as the WAN device) Its routing set and its application set start in white Before the LAN device # 43 (through an optical interconnection with the WAN device) identifies itself with the base station and with its context attributes and is authenticated by the base station, the base station adds an additional line to the context attributes of the LAN device # 43: Base station ID 0 0 The routed set of WAN device # 100 has # 43 entered by the base station. The LAN device periodically sends a LAN association beacon for non-associated LAN devices.

For (other) LAN device [RF full] # 95 LAN device [RF full] (Network ID = # 95; begins with the business environment attributes of the LAN device # 95 Its routing depth is set to one (that is, one level below the WAN device) Its routing set and its application set are set to white Upon receipt of a LAN association beacon, it responds with a request message from LAN association, where you have inserted the ADDRESS field of an upstream TAS message, the traditional address of the LAN device # 43 of the LAN association request, note that the LAN association request network ID and places it in the routing set, and passes the LAN association request to the WAN device # 100 which updates the routing set to include the LAN device # 95, and then upstream, to the base station. When the base station receives it, it notes that the network ID is new, and in this way updates its routing set to include the LAN device # 95. Before the LAN device # 95 (via the LAN device # 43 and then the WAN device # 100), it is identified as such same to the base station with its contextual attributes and is authenticated by the base station, the base station adds an additional line to those contextual attributes: Base station ID 0 0 As indicated in the above, the difference between the two previous versions of "plug and play" is one degree. For example, in the "base station-driven" version for a LAN device [full RF] (by itself and not as part of a WAN / LAN device), additional criteria can be added to the local selection procedure that can return it more aware of factors that go beyond the simple qualities of immediate physical communication. For example, additionally 2 c) "the resource indicator greater than the acceptable resource indicator", and additionally 4 c) "if the signal quality received is the same, select one with the best indicator of resources", You can further differentiate between several LAN association beacons. These additional criteria may allow the base station to "relax" decision-making responsibilities because the new LAN device can perform more "regional" selections on topological and other factors beyond (of its immediate) quality of communications. physical For another example, although the base station-driven procedure explained above for a non-associated LAN device [RF deaf] (ie, candidates are provided to the base station to select from), this procedure is also you can use for an unaffiliated LAN device [Full RF]. Lost messages When a LAN device [RF full] considers that its message (downstream or upstream) has been lost, it will send a Failed_Message report to the base station. The report has the following information regarding the message / lost packet that includes: address (upstream / downstream), sequence number, type, size, source or destination ID, followed by message (encapsulated) complete (lost) of which the lost packet is part. If the complete (missing) message can not be attached to a single Failed_Message report, then a sequence of the Failed_Message reports is sent to the base station, each with a part of the lost message. The base station, upon receipt of one or more reports from Failes_Message, will reconstruct the original lost message, register it in an RF packet record and write down the error in its system record. If the message is lost when going upstream, it will be routed to the appropriate base station application as a normal message for processing. If the message is lost downstream, it is routed as a lost message to the appropriate base station application. If the device is not included as one that has been sent as a power interruption message, or is marked as "lost in action" (or any of the devices in its routing path), the base station will verify the path of the device. routed to the proposed receiver by confirming the routing information at each stage (for example by asking each station for its status and waiting for its response). If a LAN device can not be reached, it is marked as "lost in action" and the base station is simply stopped for a close and annealing time (or re-establishment of the power supply after a light interruption). As soon as any message is received from that LAN device, its status "lost in action" is removed. The base station application will not allow messages downstream to network devices that are "lost in action" or that are experiencing a power outage (ie, a power interruption message has been sent which has not been cancelled) . This will also be extended to each routing path (ie, if an upstream LAN device is the routing path of the target device which is "lost in action "or an energy interruption is experienced." The preceding explanation applies to, but is not limited to, traditionally addressed messages.The loss of messages addressed in contextuality can also be recognized., the base station knows the total number of interrogated CAS stations (ie, the total number of LAN devices [RF full]) and, depending on the total number of responses of the LA device? received, you can infer that one or more CAS messages have been lost. Autosamed As an example of the desired complex action in response to a dynamic operating environment, the network heals itself when a communication link is interrupted, as follows. (A) Base station driven The base station keeps a list of all Routing_Candidate messages (routing candidate) as alternative routing possibilities. When you determine that a LAN device [RF deaf] is no longer reporting (for example, a Reporting_In message is not received from a LAN device [RF deaf]), the current routing path is deleted so that the LA device ? [deaf to RF] that no longer reports and tries to establish a new routing path using the best communication of said list. As indicated in the above, the base station is constructed in a manner that generates sufficient density of interactive communications that will be detected at which time there is an error with a particular LAN device [RF full] or with a WAN device. As indicated in the above, the LAN device [RF full] can be associated by a procedure of Routing_Candidate (routing candidate). When the base station detects a problem with an LA device? [RF full] in particular, you can revisit your list of routed candidate messages and try to establish a new routing path using the best combination for that list. If a new routing path can not be established, an error message is generated that requires manual intervention. (B) End point driven When a LA device? or a WA device? they become non-associated (that is, the communication link with their upstream entities is lost due to a lack of recognition of the messages they send) restarts the "plug and play" procedure explained earlier, where the concepts of a device "new" are "deployed" and replaced with a device that is no longer associated. Unlike the failure in the link upstream communications which is due to causes not related to the communication capacity, there is no difference (from the point of view of a network device and of the base station with respect to the potential network participation) between said device new non-associated network and a non-associated network device that had previously been associated but is not currently associated. For such non-associated network device, the self-sanitizing and the "plug and play" procedure are synonymous. Common causes of lack of association include a degradation of the quality of RF communications to the point of "orphaning" a network device due to changes in the operating environment (eg foliage growth or transient adverse weather conditions) or failures transient or intermittent technologies and similar implementations. A loss of association that drives self-healing in the present does not include interruptions in communications links due to causes unrelated to the communications capability such as, for example, a severe mechanical or electrical failure in a network device rendering it useless without manual intervention and repair. Therefore, the lack of association in the presence of energy interruption messages is not considered by the simple fact of an interruption of energy, which is a situation that requires self-healing. So that when a device The network "wakes up" after an alteration of energy, will suppose that it is still associated until it is determined in another sense. Recovery In the case of a serious energy disturbance, it is advantageous to recover from the energy resupply in a manner very similar to the state of the network as possible. As explained in the above, the timestamps of the network device are messages that are to be sent, with their relative time or with the time of the network, as the case may be, with a. indicator of it. As the messages are sent, they are labeled as "sent" but a copy is retained in the persistent memory of the device (subject to physical limits). Upon replenishment of energy after an alteration, the LAN or WAN device restarts its clock with the value that is the time it has when the alteration began. If the device is fully aware of the time (ie, it is [RF full]), it continues to work with its clock until the network time is received from somewhere else in the network and coordinated with it. Upon replenishment of power after an alteration, the LAN or WAN device sends its unsent messages stored to the base station. The base station has the intelligence to recreate the lost messages due to the alteration of energy and if it has been lost Someone will ask the device for their "sent" messages which may have been sent but lost on the way to the base station due to the power alteration. To support the physical limits of persistent memory, they can be organized as a circular buffer (so that the oldest sent messages are deleted by the most recent sent messages) or messages can be prioritized with a classification algorithm (which suppresses to less critical messages so that more critical messages are stored). But evidently the physical limits (ie the amount) of persistent memory will determine how many messages are stored and recoverable, regardless of the organization of the persistent memory. Power Quality Management and Automated Meter Reading Definitions A "momentary interruption" is an alteration of energy that does not extend beyond a period of power outage. The power cutoff period is motivated by businesses but due to energy alterations are measured by physical elements, there is an inherent limit in the sensitivity of the physical elements used. A "momentary interruption" can evidently only be registered by a LAN device [battery support].

An "AMR" is an abbreviation for "automated meter reading". "AMR information" for a meter includes the serial # sign of the meter (or other business-driven sign) plus information about the amount of energy measured and energy consumption. In this way, an AMR information report may include, for example, the end time of the AMR interval, several consumption readings (ie, taken at the beginning, at the midpoint and at the end of the AMR interval), factor Kh, reading of current kWh). An AMR information report is sent at the end of the AMR interval when requested (by TAS or CAS messages). See the AMR parameters in the following for a more detailed explanation. The term "PQM" is the abbreviation for "energy quality management". The information "PQM" is information about energy quality and energy consumption. In this way, the PQM information report can include, for example, the end time of the PQM interval and the maximum voltages recorded during the PQM interval, the average voltage recorded during the PQM interval and several momentary interruption accounts (for example at the beginning or at the end of the PQM interval). A PQM information report is sent at the end of the PQM interval or when requested (by the TAS or CAS methods). See the PQM parameters in the following for a further explanation. PQM parameters and AMR parameters that are used to establish: • PQM interval (a duration motivated by business, typically in hours, with an implicit value in the order of several hours, if it is zero, the device will not generate PQM information reports) • AMR interval (a duration motivated by business, typically in minutes with an implicit value of the order of 15 minutes, if it is zero, the device will not generate information report to AMR) • momentary interruptions • period of power cut (interval of 1 to 10 seconds) • delay alarm interval voltage (15 seconds to 15 minutes in 15 second increments, with 0 to disable) • voltage delay alarm level (generates a voltage delay alarm message if the measured voltage remains below this level for a period of time longer than the voltage delay alarm interval) • voltage expansion alarm interval (15 seconds to 15 minutes in 15-second increments, with 0 to disable) • voltage expansion alarm level (generates a voltage expansion alarm message yes the voltage measured remains above this level for a period longer than the voltage expansion alarm interval) • the voltage expansion alarm message includes' the measured voltage level, the current time and the momentary current interruption account • the voltage delay alarm message includes the measured voltage level, the current time and the momentary current interruption account • delayed power cut notification delay (1 to 60 seconds, with 0 to disable) The PQM parameters and the AMR parameters are business-driven and therefore are initially set and subsequently manipulated with instructions (for example instruction to synchronize AMR interval, instruction to synchronize PQM interval, etc.). ). In particular, they can be adjusted and disabled to reduce traffic congestion in the network, for example, as desired (as indicated above in the implicit values for disabling in the above). The PQM and AMR parameters for each network device can be manipulated by the base station (either through traditional addressing on a device basis by device or by contextual addressing) or manually (interacting with each subject device) directly in the place). Of course, the exception is a LAN device [RF deaf], where manual programming is obviously necessary. Cut-off time report when replenishing energy (for version without battery support) The start of a delayed power cut and the power replenishment time is reported to the base station by all LAN devices [RF deaf] and the LAN device [RF full, but without battery support]. When energy replenishment is experienced by the LAN device [without battery support] a message will be sent to the base station containing the time at which the power disturbance was initiated and the moment when the power supply was summarized. The sending of this message will be delayed for a period (motivated by business) in such a way that momentary interruptions experienced by a LAN device [without battery support] will not saturate the network with power recovery messages. Voltage delay / expansion alarms The LAN device sends a voltage expansion alarm message and a voltage delay alarm message, as the case may be, when it considers it appropriate acing to the above definition, and also restoration messages appropriate when the voltage returns to be within the established range.

The AMR interval synchronization instruction and the PQM interval synchronization instruction, respectively, are used to coordinate the AMR intervals and the PQM intervals between the LAN devices. These instructions do in fact contain the times for the next AMR interval and PQM interval to start. Synchronization can occur through the entire network or in desired portions of the network (by elaboration of contextual address messages) or on the basis of an individual LAN device, one by one (by a traditional single broadcast message) ). In the implementation, these synchronization instructions contain the "base time" in which the LAN devices are to be coordinated, for the following PQM / AMR intervals for their start. A LAN device [RF deaf] can not be coordinated as a LAN device [RF full] but its LAN device [RF full] [application custodian] can be coordinated like any other LAN device [RF full], and in this way , in effect, the LAN device [RF deaf] is indirectly coordinated. At the end of the PQM interval (or before a request for a PQM information report (TAS or CAS)), a PQM information report is generated and sent to the base station. The AMR configuration can include parameters such as: a) AMR interval b) power cut reporting status (on / off to generate reports or not) c) power cutoff period - send a power cut report (if the cut report status is SWITCHED ON) . The AMR configuration may be the subject of a base station request of a LAN device or the contents of a base station instruction to a LAN device to change. The PQM configuration can include parameters such as: a) voltage delay alarm interval b) voltage expansion alarm interval c) voltage delay alarm level d) voltage expansion alarm level e) PQM interval f ) delayed power cut notification delay. The PQM configuration may be the subject of a base station request of a LAN device or the content of a base station instruction to a LAN device to change. When the LAN device [RF full] receives an AMR interval synchronization instruction or a PQM interval synchronization instruction, will recalculate its clock "countdown" value for the next PQM information report or AMR information report so that the messages will be coordinated acing to the time contained in the instruction. Each LAN device [RF deaf] periodically generates a time synchronization message, as explained in the above. When this time synchronization message is received by your LAN device [RF full] [application custodian], is the time synchronization message updated with the current network time stamp of the LA device? [RF full] and routed to the base station. This allows the base station to calculate from the "timestamps" reported by any LA device? [deaf to RF], an equivalent in network time. Hybrid / inheritance In a large family, not every individual is "equal" or "the same". For example, a child inherits part (but not all) of the parents' attributes. As another example, a more competent parent helps a less competent child to perform actions in the family. The respective analogies to this invention can be: an addressing scheme (CAS or TAS or both) that is used for the "partial inheritance" of a station next to some "attributes" of the upstream station and a fully functional station "help " to less functional stations. The issue of creating a more cohesive family unit from a heterogeneous set of individuals, or by analogy with the present, the issue of creating a more homogenized network performance from a heterogeneous network, is explained below with examples. In realistic network implementations in the field (perhaps due to regulatory, economic, technological, physical or other, particular factors) not all parts of a network have identical functionality. Some devices are "smarter" or full functionality compared to those "minor functionality" that have a reduced set of features. The "less functional" in relation to the "fully functional" may have, for example less memory and processing capacity, only transmit instead of transceiver capacity and without battery support. The heterogeneous nature of realistic networks makes it difficult to obtain certain management functions. For example, if all the network elements do not have functionality to be synchronized with the network time, then it is difficult to accurately observe the state of the entire network (that is, all the elements) at a given point (motivated by business) over time (for example, the voltage level in all the customer's places at a certain moment).

Two examples of heterogeneity and the attempt of this invention to "homogenize" them are explained in the following: (1) capacity only of transmission in the network where the other elements have transitory capacity, which affects time awareness messages (upstream) ) and addressing (downstream); and (2) that it does not have battery support in a network where the other elements do, which affects the reporting of power supply outages. (1) Ability to transmit only Two examples are provided to make "deaf" stations "listen" as if they were. The ability of a station to "listen" affects the quality of its time consciousness. In particular, if it is "deaf" (that is, it can only transmit RF), the aforementioned exemplary difficulty before accurately observing the state of the complete network presents itself. A LAN device [RF full] that has the complete communications transceiver functionality in this way can learn (or can be made to know from the base station another network device) the time of the network and calculate its time in coordination with the same. In this way, in the absence of energy or other alterations itself and its network environment, the time awareness of a LAN device [RF full] is "complete" and its "time" of internal clock is the time of the network. In contrast, a LAN device [RF deaf] can not receive information from its network environment and therefore its internal clock can not learn (or can not be) that it knows the time of the network and can not calculate the time of time in coordination with it. The LAN device [RF deaf] will never know the time of the network and its time consciousness is limited so that its time will always be that of its internal clock or relative time. But this does not mean that you can not approach a full-time awareness of a LAN device [Full RF] The internal clock of a LAN device [deaf to RF] can calculate the relative time since the last time that relative time information was turned on and sent (upstream). By providing upstream intelligence to translate the relative time into information coordinated with the time of the network, the message is reported as a "deaf" device having a certain relative time stamp, it can be roughly coordinated with the time of the net. For example, the message may have the voltage measured by the LAN device [deaf to RF] at a certain relative time. The intelligence upstream can be constituted in a LAN device [RF full] [application custodian] or another network device coordinated with the time of the network. So, from the point of view of the rest of the network, said particular information comes from "deaf" device is coordinated with the time of the network. Thus, from that point of view, the apparent quality of the time awareness of the "deaf" device does not differ from the LAN device [RF full] although the "deaf" device itself does not know the time of the network or anything else, besides himself. Said proverbially, this invention asks the network to judge an individual by their actions (the value of their actions create, through the work of their hands together with others) and not by their nominal appearance. Take the example of a contextual CF function that asks for a report of electricity consumption to all stations connected to line # 7 power feeder in a network time = 17:00. The answer for LA devices? Conscious of time completely [RF full] is easy to implement. Although a LAN device [RF deaf] can not precisely coordinate network time, coordination can be approximate, as follows. Periodically send to your LA device [RF full] [application custodian] a time synchronization message consisting of your relative time then and your power supply cut off account. The energy supply cutoff account is the counter maintained by each network device in its persistent memory and its current value represents the total number of times, minus one, which has been reactivated to date (it is say, the # of power supply cut to date, minus one). The LAN device [RF full] [application custodian] increases the time synchronization message with its network time and sends the increased message to the base station. This increased message (which has the relative time of the device LA? [RF deaf] with the network time of the device LA? [RF full]) allows the base station (or other intelligence upstream of the LA device? RF-deaf]) translate the relative time of the LAN device [deaf to RF] into the approximate network time. These augmented messages are maintained and the total number of times of activations can be used as an index to calculate the approximate network time equivalent to the relative time-stamping formation of the LA device? [deaf to RF]. In this way, the LA device? [deaf to RF] approaches full-time consciousness. Send information to the network (and in particular typically to the base station) in a way that is approximately coordinated with the time of the network as if the information had been sent by an LA device? [Full RF] The preceding example relates to a TAS message that is sent upstream by a "less-functional" LAN device [deaf to RF]. In other words, although a LAN device [RF deaf] can not be routed downstream directly by a base station, it can be addressed "indirectly" through your LAN device [full RF] [application custodian]. The following examples relate to the base station addressing of a LAN device [deaf to RF] in a traditional and contextual manner, respectively. An application custodian service is stored messages temporarily received from the LAN devices [deaf to RF] in its application set, and sends those messages upstream when they request it. Each application custodian knows the traditional address / network ID of each LAN device for which application custodian services are provided. In turn, the base station in this way has this information (either known indirectly by this means or by keeping a master copy of it) of each application custodian and of each LAN device [deaf to RF] . By having the application custodian act as a hidden memory or a mirror for information for which a base station TAS message might be of interest, the questions of the application custodian's base station that is temporarily storing a message received from the same, to send this information. Returning to the CAS, because only a LAN device [RF full] can "listen" and react with a contextual function CF. the LAN device [deaf to RF] by definition, is not a station interrogated CAS and is "orphaned" outside of CAS. Consequently, it is advantageous that the business environment attributes of a LAN device [RF full] [application custodian] be "shared" or "inherited" in the sensitive degree (commercially) by LA devices? [RF deaf] of your application set. In this way, an LA device? [RF deaf] can be addressed contextually, as explained below. For example, an LA device? [Full RF] [application custodian] has the business contextual attributes of "geographic area = south west" and "power feeder line = # 7"). A LAN device [RF deaf] that is physically proximal to it or is attached to power feeder line # 7 advantageously has its business attributes appropriately attributed. The LAN device [RF full] [application custodian], during the "plug and play" procedure, increases its application set information with the contextual attributes of its LAN devices [RF deaf] and therefore knows which of its LA devices? [deaf to RF] "shares" (or "have inherited") which of the contextual attributes of the application custodian business. This LA device? [deaf to RF] does not exist in the CAS and is not addressable under TAS but, nevertheless, can participate in the following exemplary manner. In operation, the LAN device [RF deaf] measures its voltage levels and sends the measurements to your LAN device [RF full] [application custodian] for temporary storage. The base station sends a CAS message whose CF contextual function is "all CAS stations whose geographical area is the southwest and which are attached to the power supply line # 7, send their information of voltage levels", in which case , the application custodian for the LAN device [RF deaf] will send information about its voltage levels and its application LAN (deaf to RF) device (stored), whose geographic area is the southwest and which is attached to a # 7 power line. Just like a collect call for "all MacGregors "will induce a response from parents who have the MacGregor name of themselves and their minor children who have inherited their father's name, a LAN device [deaf to RF] "inherits" part of the contextual attributes of its environment, and in particular, those of its LAN device [Full RF] [application custodian] and can be addressed contextually. In the limited manner described above, the LAN device [RF deaf] can be "contextually addressed". Of course, the inheritance has limits as well as families or individuals, and no less with the direction of this invention. Since the respective credit ratings of the father and the son are independent of each other, some contextual attributes, by their very nature, are not likely to be shared with others. For example, the business contextual attribute of "customer credit risk rating" of a LAN device [RF deaf] is independent of the "customer credit rating" of your LAN device [RF full] [custodians] of application] . (2) Without battery support This example will be explained together with the power supply cut messages. When a LAN device [battery holder] (either [RF full] or [RF deaf]), at the time of a power cut, it will send a power cut message to the base station. For a LAN device [RF full] [battery support] (that is, it has transceiver capability to be coordinated with network time), your power supply cut message will be marked on network time accordingly . For a LAN device [RF deaf] [with battery support], all your messages are sent upstream (and in particular your power supply cut message) and the relative time will be marked. Together with your LAN device [RF full] [application custodian], the base station translates the relative timestamp of the power supply cut message, into network time. In contrast to the above, the LAN device [without battery support] requires more stages because during an energy alteration, it obviously can not measure the power cut. When a LA device? [without battery support] experiencing a disturbance in energy for the first time and if a previous power supply cut has been reported, it is recorded in persistent memory: (a) your power supply cut off account, and ( b) its time (which can be relative time for an LA device? [RF deaf] and a network time for a LAN device [RF full]). This recorded information is focused as an upstream TAS message and is placed in the memory in advance for transmission but that depends on the specific conditions of the persistent memory, the alteration of energy and other factors, as it is known a priori that message will indeed be sent by the LA device? or if it is sent, it will be received by the base station. In any case, this message is kept in the persistent memory and will be (re) sent later (before the energy resupply, in accordance with the procedures of messages lost in the following) . Before the power supply is resumed, the LAN device [RF full] [without battery support] will increase its energy output account and wait until it is coordinated again with the network time (it can not be established that it is operating in coordination with network time because their upstream devices may still not have recovered from the power / power supply disruption and may not be in a position to provide network time to this LAN device [full RF ] [support without battery] When it is going to re-coordinate, a power supply cutoff message will be sent with the power supply cutoff account, with proper time dialing in the network. power, the LAN device [RF deaf] [without battery backup] will increase your power supply cutoff account (for the present of the next power disturbance and possibly the l cut off power supply) and reset your clock and send a power cut message marked in time, with the power cut count. One or more power supply cut messages will then be in the persistent memory (sent or not sent) and may be present. The intelligence of the base station is sufficient to filter one or more messages power supply cutoff, if any, created by the above procedure and to recreate the energy supply cutoff messages marked in time (of a network and relative), the network status (to the extent possible, of according to the procedures of lost messages and other intelligence, limited only by implementation technology). Therefore it is observed that, according to this invention, the "less functional" stations (those of the application set of a LAN device [RF full] [application custodian]) are associated (logically) with a fully functional upstream station that provides part of the total lost functionality of the "minor" functional stations, so that they form the point of view of the base station or the intermediate portions of the network, and the network approaches a homogenous network in the operation of concrete actions. By organizing and equipping stations in accordance with this invention, the "less" functional stations can be elaborated to approach the fully functional ones via application custodians, and in this way the network actions become more homogeneous. Similarities between CAS and the immune system The difference between the CAS and the body's immune system is that they are many and obvious and their expression. In other words, some similarities between them are not worth noting to clarify the advantageous aspects of CAS. Unlike the nervous system (where the neural signals are sent in a "connection-oriented" manner), the vascular system is a network of "lack of connection". Within the vessels and the tissue that transports or circulates fluids such as blood or lymph or travels through the body, the cells and molecules "float freely" in the blood or lymph. Antibodies are produced in the body and are "sent" to the vascular system to search for and destroy "antigens (ie, biological substances that are" foreign "to the body) An antibody is a molecule that is produced in response to an antigen and that it has the physical property of being able to combine or bind with the antigen that induces its production in its respective binding sites.The epitope part of the antigen and the paratope of the antibody "recognize" each other by "matching" and binding between yes (to mark for destruction, to coat or to initiate an activity of "useful information" type as part of the defense mechanism.) The paratope of the antibody and the epitope of the antigen that induces the production of said antibody are the respective molecular shapes or contours of them that are mutually attractive (which they include physically complementary) and that they interact in a manner very similar to a bolt and key designed for said bolt. An antibody and an antigen that is not related to said antibody are ignored to each other, in a manner very similar to the "interaction" between an erroneous key for a lock, or which will not produce any event. The complementary epitope-paratope interaction is similar to a CAS station that receives a CAS message that decodes and determines what it means for the station. Antibodies do not know in advance at what point an antigen is in the body, in the same way that the CAS interrogation station does not know where the searched stations are located. The union is made as a function of electric charge attractions-the greater the complementarity exists in three-dimensional epitope and paratope forms, the greater the attraction between antigen and antibody. Of course, the digital equivalent of the information technology of that complementary union is more definite - the complementarity is binary and opposite, so that "11101" joins "00010", as an analogous example. The immunogenicity of antigen is its ability to induce a specific immune response. The greater the chemical complexity (ie, more epitope diversity), the greater the degree of immunogenicity. By way of Similar the greater the number of contextual attributes that take into consideration a CAS station, the more enriched the network will be. The endocrine glands secrete hormones. Because there is no direct connection between the glands and the target tissue and there is usually some difference between them, the endocrine glands are often referred to as "no duct". Once secreted, the hormones find their way and identify the objective tissues by themselves, without the help of the gland. Similarly, the CAS interrogation station does not know "where" the interrogated CAS stations are searched-it simply sends a CAS message. Therefore it is observed that some systems of the body do not know, at least initially, "where" the target is but they are very sensitive to "who" (that is, they are very sensitive to "strange" substances). The similarities between the immune and hormonal systems of the body, the design of drugs to direct them to specific three-dimensional receptors and more generally the chemocommunications between organisms are just a crude analogy. Such biological analogies are obviously not prior art for this invention but indirectly illuminate some of the issues and advantages. It is interesting to observe that the human body has nervous and vascular systems (without connections and oriented to connection) that works side by side and that in the preferred modality are both, "connection-oriented system" (the communications network that operates with TAS for some messages, where the source knows where to "send") and a "system without connection" (the network and communications, which operates with CAS for other messages, where the person who wants to know does not know in "where" are the others that interest him). The preferred modality advantageously combines, in a system, "who?" and where?". Some of the communication representations mentioned in the above can "transport in blocks" in an existing land line and cellular systems used by businesses. The selection depends on exemplary frs (existing and desired) of communications coverage, cost, control and capacity. Although the physical means of communication in the preferred embodiment is wireless, wired or optical means are possible. For example, although a sensor and an effector are defined in terms of electrical signals, an obvious equivalent would be optical signals. For example, messages in accordance with this invention can be modulated and transported over power lines (e.g., power line carrier technologies from Hunt Technologies, Inc. and Distribution Control Systems, Inc., with patent descriptions representative of patents of USA # ,262,755, # 5,5581,229, # 6,154,488 and # 6,177,884 and publication of E. U. A. # 2003/0006884). Other embodiments of this invention can be carried out through a cable television system, for example, and the term "RF broadcasting" herein is not to be understood as some regulatory regimes that can uniquely define the policy reasons (in which "broadcast" does not include the transmission of a point to multiple points, for example, under FCC, parts 73 and 74). As explained in the preferred embodiment, some procedures (such as "plug and play") use a traditional addressing scheme. But it is not • necessary in other modalities. A CAS network can be established through "plug and play" without traditional addressing so that the new element communicates with the base station. The CAS is described in the preferred embodiment as a downstream addressing scheme, which radiates from a base station. There is no limitation of CAS to addressing with work. The CAS can be used for upstream addressing (in part or in its entirety) as suggested by Figure 3, where several CAS networks can coexist as a subset of the communications system that couples the interconnection modules, each with a station question mark and a schema semantic shared with their interrogated stations (for example, their contextual variables and the frequency of RF operation). The preferred modality is mainly related to telemetry of electricity distribution companies. This invention is advantageously applied to other telemetry businesses of distribution companies (such as gas and water distribution companies) and to many situations different from those of the distribution companies. Exemplary sensory interon modules include security in buildings and environmental alarms, sensors (for example to monitor equipment and inventory in a home environment, the water level in a dike system, the temperature of a road and the number of items sold or that remain in a vending machine), accelerometers, pressure transducers and voltage calibrators. Exemplary effector interon modules include ators on a robotic fry assembly line, thermostats, gauges and valves (e.g. for pressurized vessels). Other operating environments are those of office, home and business. For example, in a network of office printers, fax machines and other office type, the sensors take care of the level of paper or other consumable material, the date of the last complete maintenance review and the effectors can finalize the access or the power supply and a The desired complex action is "all equipment that has not undergone a maintenance check during the last 100 days or the last 1000 impressions, whichever comes first, please disconnect". In electrical appliances in a home environment (eg freezers, heaters) can be coordinated with this invention. In a home environment or in a factory, this invention can advantageously be used to interact with HVAC systems, lighting systems, motors, interruption mechanisms, pumps, etc. In the preferred modality, reception of all messages traditionally addressed (downstream and upstream) are recognized in a base package per package, by a conventional method not explained herein by economy of expression.

Obviously, recognition can be carried out (direct or indirect) on a different basis (for example greater than at the package level). In addition, recognition in the preferred embodiment was mentioned only with respect to the TAS messages for economy of explanation. Wireless LAN, as suggested in the above preferred embodiment, can be implemented in a narrow band of 433 MHz. Of course, other implementations are possible. A broad spectrum of frequency hopping technology implemented in its band of LAN communication channels to 900 Mhz is possible, for example. Of course, depending on the selection of implementation. Certain features need to be redesigned and will require conventional modification to reflect where the intelligence and processing power is distributed on the network, as a design matter for those skilled in the art. As mentioned in the above, the topology of a CAS network does not need to be stable. For example, the network can operate on a mobile Internet protocol (for trains that travel in a maneuvering yard or a fleet of transport trucks, as examples). As indicated in the above in the preferred embodiment, all messages (downstream and upstream) are traditionally addressed except those messages downstream from the base station which are contextually addressed. This distribution of communication addressing scheme is reflected by the analogy of the company and the respective roles of the president and the audience. The "president-vaudience" relationship is similar to the downstream aspects of a base station-endpoint communications network. During the course of the meeting, the president can recognize and communicate with a particular person or can address the entire audience. The relation "president * -audience" is similar to the upstream aspects of the network. The official communication by listening normally goes to the president and not directly to other listeners. That is, there is no inherent reason why an upstream message can not make a CAS message. But for economy of explanation and expression in the preferred embodiment, the CAS is a downstream addressing scheme. Although the preferred embodiment has been described with the combination of both the traditional addressing scheme and the contextual addressing scheme, as indicated in the foregoing, each can be a unique addressing scheme in a network that is utilized by the method of the invention (for example the "plug and play" procedure based solely on CAS). Although the preferred embodiment concentrates on assisting the base station to obtain a desired complex action through efficient coupling of the interaction modules to interact with the operating environment, obviously an exemplary desired complex action is the module conditions report. interconnection-based sensors on an event-driven basis (for example, an alarm condition) instead of being administered by the base station (in the exemplary PQM and AMR reporting procedures). In the preferred mode, all the devices of network have transmission communications functionality. In principle, a network device may have only reception communications functionality. WAN devices are considered in the preferred mode as communication representatives of the base station and the LAN. Of course, they can be equipped with additional functionality (for example, it can also be a final data source receiver, such as LAN devices). A WAN device by itself (that is, without an interaction module) does not make sense in the preferred mode because it means that it is a communication representative in it. In the preferred mode, the field installer starts with a non-associated WAN device that has a LAN device [RF full] attached, that is, each new WAN device is deployed as part of a WAN / LAN device (see the US application) mentioned before # 10 / 164,394). In other modalities (not explained in the present by economy of explanation), or may be attached to a non-associated WAN device, other types of network devices, such as a LAN device [deaf to RF], a LAN device [dull and mute RF] a remote power disconnect switch, a modem SCADA / DNP a keyboard or any other device useful for a desired complex action. In. the preferred modality, there is a relation one to one between a LAN device and an interaction module, for simplicity of explanation and expression. In principle, other types of relationships may exist, for example a LAN device with multiple interaction modules. For the preferred mode in your CAS network, the exemplary station that is "deaf" to a CAS message is the LAN device [RF deaf]. But in general, a station is "deaf" for CAS purposes but can process the currently pending CAS message, without being limited to any particular "deafness" basis. A LAN device may have RF transceiver capacity but still be "deaf" to a CAS message because the CAS message was formed with a communications protocol that differs from one that can be understood (go back to the United Nations analogy, where all individuals are individuals who "listen" but not all speak the same dialect). In general, "deafness" for purposes of CAS can be elaborated "contextual" and can not be limited to the fact of "not having ears" of the [deaf to RF]. The use of "plug-and-operate" beacons of the preferred embodiment has obvious alternatives for those skilled in the art (e.g., accumulation). Different alternatives have different advantages and disadvantages for different aspects of the functioning of the network, all within the point of view of those experts in The technique. There is no mention in the present of peer-to-peer communications (eg communications between LAN devices) to avoid the clutter of the economy and the simplicity of the explanation for the centric network of the base station. Many of the principles of this invention explained in the above will be readily applicable for peer-to-peer communications with appropriate modifications made readily by those skilled in the art. As an obvious example, the concepts of "downstream" and "upstream" can obviously be inapplicable (at least partially) accordingly the message format for a peer-to-peer message may be similar to a traditionally addressed message (see Figure 1) except that the address is for the peer source as for the peer destination. be provided. In addition, the "points of convergence" where the LAN device [RF full] keeps track of the routing sets, can be used so that each peer does not need to keep track of the TAS address of every other peer. Although this invention has been described in relation to the preferred embodiment and another embodiment, it is not intended to be limited thereto, but rather to cover such alternatives, modifications and equivalents as may be reasonably included within the spirit and scope of the invention. invention as defined in the claims. Also, although analogies have been used in the preceding descriptions, they should not unreasonably lead to the extreme, beyond the point where they cease to be useful in clarifying certain aspects of the concepts of the invention. It is noted that in relation to this date, the best method known to the applicant to carry out the aforementioned invention is that which is clear from the present description of the invention.

Claims (10)

2. Having described the invention as above, the content of the following claims is claimed as property: 1. A method for sending useful information from an interrogation station to a network of interrogated stations, characterized in that it comprises the steps of: (a) attributing to each of the interrogated stations a set of contextual variables and their contextual values for them, to form contextual attributes of said interrogated stations; (b) forming the searched identity of a interrogated station to receive useful information, the identity sought is a function of the appropriate values for the contextual variables; (c) the interrogation station sends to all interrogated stations a CAS message that has: (i) the useful information and (ii) the identity sought; and (d) each interrogated station determines, upon receipt of the CAS message, that it has, based on its contextual attributes, the identity sought, and before that, processing of the useful information does have that identity. 2. The method of compliance with the claim 1, characterized in that the interrogation station is agnc about the logical links, if any, between it and the interrogated stations having the searched identity, for the purposes of the CAS message.
3. 3. The method according to claims 1-2, characterized in that the station interrogated, when performing "the determination stage (d)", uses said function on its contextual attributes and compares the result with the identity sought.
4. 4. The method according to claims 1-3, characterized in that the "function stage (b)" uses: (i) the C values sought for said context variables, and (ii) a logic instruction of. { boleana, linear, non-linear and confused} .
5. 5. The method according to claims 1-4, characterized in that the "attribution step (a)" is motivated by business.
6. 6. The method according to claims 1-5, characterized in that the "attribution step (a)" is motivated by the manufacturer.
7. 7. The method according to claims 1-6, characterized in that the "attribution step (a)" is implemented by interaction with the environment of the interrogated station.
8. 8. The method of compliance with the claim 7, characterized in that the environment includes an aspect of the physical environment, and the interrogated station is equipped to measure the appearance of the physical environment and the interaction includes measuring said aspect.
9. 9. The method according to claim 7, characterized in that the environment includes information related to another interrogated station and the interaction includes coordination (of time) with it.
10. 10. The method according to claims 1-9, characterized in that the "stage (b) of identity development sought" is motivated by business.