Electronic unit-based status management system, management method, and service delivery system

Abstract

In this embodiment, the electronic unit acquires information from the surrounding equipment in which it is located. The system controller collects the information acquired by the electronic unit and provides an electronic unit management method and management system that estimates the surrounding environment of the electronic unit. [Solution] In one embodiment, the first system controller and / or the second system controller collect sensor information and / or current setting status information from the electronic units registered in their respective address information. The first system controller and the second system controller each manage multiple electronic units that exist within the area they manage, check the attribute information sent from the multiple electronic units, and notify a predetermined organization if an impossible combination of attribute information exists.

Description

Technical Field

[0001] Embodiments of the present invention relate to a situation management system, a management method, and a service providing system using an electronic unit, and more particularly to an M2M (Machine to Machine) application technology or an IoT (Internet of Things) application technology that can collect information using various sensors installed in, for example, public facilities or homes and perform control based on the information.

Background Art

[0002] Regarding the field of M2M or IoT application technologies, as shown in Non-Patent Document 1, global standardization work is in progress. Here, it aims to establish a general standard for comprehensively integrating and managing information obtained from all kinds of diverse sensors and adapting the results to various services.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As Non-Patent Document 1 shows, previous standardization activities have been based on the premise of collecting information from "sensor-embedded devices" and using that information comprehensively to provide services. Furthermore, due to the requirement for versatility in standardization, it is necessary to be able to comprehensively handle information obtained from a wide variety of sensors. Moreover, in order to maintain the usefulness of the established standard over the long term, it is necessary to be able to accommodate future technological advancements in sensor-embedded devices and the expandability of the types of sensors that can be incorporated into the devices. Thus, ensuring consistency between the diversity (of sensors) and the versatility (of the standard) which are mutually contradictory is not only extremely difficult, but the inherent contradiction in standardization activities lies in guaranteeing versatility, flexibility (to accommodate sensor diversity), and expandability even for devices that incorporate sensors.

[0005] The current specific technical challenges can be summarized in the following four points. Firstly, the accuracy of information gathering for service provision largely depends on whether each sensor-embedded device is powered on or off. In other words, in order to select the optimal service content, it is necessary to integrate information obtained from various sensors to estimate / determine the state within a given system or the user's behavior and state. However, if the power to most of the devices in the above network system is turned off, the amount of information to be collected becomes too small, resulting in a significant decrease in the accuracy of the aforementioned estimation / determination.

[0006] Next, there is the difficulty of adapting to future changes in the functionality of sensor-embedded devices. For example, television functionality was previously limited to receiving broadcast waves and displaying images, so consider a scenario where a communication standard was developed that could only grasp the television display status. In contrast, high-end televisions in Japan now have built-in recording functions. Furthermore, there are high-end televisions that have data communication functions using network lines. And although not yet widespread, glasses-free 3D TVs (3-Dimensional Television) can detect the viewer's location information. Furthermore, in the future, there is a possibility that light sensors will be built into televisions (to optimally control the brightness of the display screen). In this way, if the standard is updated every time television functionality improves, there is a problem that the standard review process takes too much time, leading to delays in adaptation. Conversely, if the number of items to be supported within the standard is increased in advance in anticipation of future expansion of television functionality, the standard itself becomes redundant, and the control of support within the device becomes complicated.

[0007] The third technical challenge is that current communication standards, which aim for versatility and scalability, are finely layered (see Figure 32 for details), resulting in duplication and redundancy in communication information. While layering communication standards allows for support of diverse technical domains by replacing specific layers, it leads to an increase in the amount of communication information and increased processing complexity. As long as communication is conducted using PCs or smartphones equipped with high-performance processors, the increase in communication information and processing complexity were not a problem. However, these are not suitable for the demands of power saving and simplified processing.

[0008] The final technical challenge is that making communication information versatile requires significant processing power, leading to higher costs and higher power consumption. For example, there is a communication method that uses XML (Extensible Markup Language) to describe communication information, providing flexibility and extensibility. However, in this case, the receiving side requires XML parser functionality, complicating the receiving side's operations. On the other hand, there is a communication method that uses different standard tables for each type of device to accommodate the diversity of devices. However, even in this case, the standard table that can handle high-end devices of the same type becomes complex, increasing the burden of communication processing on single-function devices.

[0009] The objective of this embodiment is to provide a status management system, a management method, and a service provision system that utilize information from an electronic unit, which acquires information from surrounding equipment at its new location and performs operations according to the acquired information. [Means for solving the problem]

[0010] According to one embodiment, a first system controller and a second system controller are located in a first local network and a second local network, respectively. Servers located on a wide-area network, The first local network, the second local network and the wide area network The server, the first system controller, and the second system controller are connected via network. A status management system using an electronic unit that can communicate with a controller, The first system controller and the second system controller are, Each local area network sets up multiple sections, It manages the electronic units within each section. The server, the first system controller, and the second system controller are: Each unit is equipped with a memory section, and each memory section is configured to communicate with the electronic unit. It contains shared address information for use, The address information includes at least the sender's IP address, the receiver's IP address, and the receiver's IP address. Identification information of the section in which the transmitting electronic unit is located, including the receiving electronic unit. This includes the equipment type code of the equipment and the equipment identification code within the same type. The first system controller and / or the second system controller are Means for collecting sensor information and / or current setting status information from each of the aforementioned address information electronic units, The system comprises means for estimating / determining the state of the electronic unit within the system based on the collected information and / or current setting state information, The first and second system controllers each manage multiple electronic units located within their respective areas, check attribute information sent from each of the multiple electronic units, and provide a means for notifying a designated organization if an impossible combination of attribute information exists.

[0011] The aforementioned electronic unit is defined as a unit that generalizes a composite module, equipment, or a combination thereof, and can be managed and controlled on a unit basis.

[0012] The above-mentioned unit and system controller constitute a network system, and the system controller controls this entire network system. Furthermore, the system controller is capable of communicating with the outside world of this network system. [Brief explanation of the drawing]

[0013] [Figure 1] Diagram illustrating the wide-area network structure within this embodiment of the system. [Figure 2]Explanation diagram of the local network structure within the system of this embodiment. [Figure 3A] Explanation diagram (1) of the embodiment of the unit. [Figure 3B] Explanation diagram (2) of the embodiment of the unit. [Figure 4A] Explanation diagram (1) of the embodiment of the composite module. [Figure 4B] Explanation diagram (2) of the embodiment of the composite module. [Figure 4C] Explanation diagram (3) of the embodiment of the composite module. [Figure 4D] Explanation diagram (4) of the embodiment of the composite module. [Figure 4E] Explanation diagram (5) of the embodiment of the composite module. [Figure 4F] Explanation diagram (6) of the embodiment of the composite module. [Figure 5] Explanation diagram of the specific structure within the sensor / communication module. [Figure 6A] The first embodiment showing the specific structure within the drive / communication module. [Figure 6B] The second embodiment showing the specific structure within the drive / communication module. [Figure 6C] The third embodiment showing the specific structure within the drive / communication module. [Figure 6D] The fourth embodiment showing the specific structure within the drive / communication module. [Figure 7A] Explanation diagram of the specific structure within the communication module. [Figure 7B] Explanation diagram of another example of the specific structure within the communication module. [Figure 8A] Explanation diagram of another example regarding the local network structure. [Figure 8B] Explanation diagram of another alternative example regarding the local network structure. [Figure 9] Application example regarding the local network structure. [Figure 10A] Explanation diagram of the basic app / communication layer structure of the system of this embodiment. [Figure 10B] Explanation diagram of the overview of the information communicated in the communication middleware layer. [Figure 11] Diagram illustrating the data structure transmitted within a network line in this embodiment. [Figure 12A] Diagram illustrating the data structure within the physical layer header and MAC layer header. [Figure 12B] Detailed diagram illustrating IEEE extended addresses in this embodiment. [Figure 13] Diagram illustrating the data structure within the IPv6 header. [Figure 14] Diagram illustrating the data structure of communication middleware in C-format. [Figure 15A] Diagram illustrating the data structure of communication middleware in E-format. [Figure 15B] Diagram illustrating the data structure of communication middleware in A-format. [Figure 16] An illustrative diagram showing an application example of the basic application / communication layer structure. [Figure 17A] Diagram illustrating another example of the application / communication layer structure (1). [Figure 17B] Diagram illustrating another example (2) of the application / communication layer structure. [Figure 18A] A diagram illustrating the peripherals of device drivers in a computer system. [Figure 18B] A diagram illustrating the area surrounding the management / control zone of a unit within the system. [Figure 19A] Diagram illustrating another example of the management / control relationship between units within the system. [Figure 19B] A diagram illustrating the management / control methods of units within a system from a software perspective. [Figure 20] A comparison diagram of the existing file system and the unit management method in this embodiment. [Figure 21A] An illustrative diagram showing an example of the internal structure of a simulated drive managed by a unit. [Figure 21B] An example diagram illustrating the internal structure of a folder that supports composite modules. [Figure 21C] An example diagram illustrating the internal structure of a folder for sensor / communication modules. [Figure 21D]An illustrative diagram showing an example of how sensor information is displayed in a sensor / communication module. [Figure 22] A diagram illustrating the position management routines within sections for equipment and various modules. [Figure 23] An explanatory diagram of an example address table managed by the system of this embodiment. [Figure 24] Diagram illustrating an example of section division. [Figure 25] A diagram illustrating spatial unit sections related to sensing and services. [Figure 26A] A diagram illustrating the basic processing flow within the system controller. [Figure 26B] A diagram illustrating methods for collecting, estimating, and determining information from fixedly positioned equipment and complex modules within a section. [Figure 27] Diagram illustrating the estimation / determination method in this embodiment. [Figure 28] An illustrative diagram showing an example of how communication information changes over time. [Figure 29] An explanatory diagram illustrating an example of service delivery methods on a section-by-section basis. [Figure 30] A diagram illustrating methods for collecting, estimating, and determining information from movable equipment and complex modules between sections. [Figure 31] Diagram illustrating the method for monitoring the location of equipment and various modules. [Figure 32] A diagram illustrating the structure of the radio wave source direction detection unit in this embodiment. [Figure 33] A diagram illustrating the structure of the stealth plate in this embodiment. [Figure 34] Diagram illustrating the principle of direction detection of the radio wave source in this embodiment. [Figure 35] An explanatory diagram illustrating an example of section division in the social infrastructure sector. [Figure 36A] An explanatory diagram illustrating an example of applying a composite module across different middleware layers. [Figure 36B] An explanatory diagram showing an example of applying composite modules across different systems. [Figure 37A] An explanatory diagram showing an example of the application of a composite module. [Figure 37B]An explanatory diagram showing another example where a composite module is applied. [Figure 37C] An explanatory diagram showing yet another example where a composite module is applied. [Figure 37D] An explanatory diagram showing yet another example where a composite module is applied. [Figure 37E] An explanatory diagram showing yet another example where a composite module is applied. [Figure 37F] An explanatory diagram showing yet another example where a composite module is applied. [Figure 37G] An explanatory diagram showing yet another example where a composite module is applied. [Figure 37H] An explanatory diagram showing yet another example where a composite module is applied. [Figure 38] A diagram illustrating network connectivity within a home client system. [Figure 39] Diagram illustrating the control method for smart home appliances that support automatic control. [Figure 40] Example of the robot cleaner control condition settings screen. [Figure 41] Diagram illustrating the content of exchange information between air conditioners based on the E-format. [Figure 42] Diagram illustrating the content of information exchanged between a television and a television based on the E-format. [Figure 43] A diagram illustrating the relationship between the status information of each related device and the user's actions and status. [Figure 44] Detailed control diagrams illustrating the operation of each component related to robotic vacuum cleaners. [Figure 45] Another explanatory diagram illustrating a method for automatically determining the optimal operating state of a robot cleaner based on collected information. [Modes for carrying out the invention]

[0014] The embodiments will be described below with reference to the drawings. First, the structure of the chapters and sections related to the description of these embodiments is shown in the table of contents below.

[0015] Chapter 1 Overall System Overview in this Embodiment Section 1.1 Overview of the entire system in this embodiment Section 1.2 Description of unit configuration Section 1.3 Description of the configuration within the composite module Section 1.4 Description of the structure within the sensor / communication module Section 1.5 Description of the structure within the drive / communication module Section 1.6 Section 1.7 Description of an example structure within a communication module Section 1.8 Description of the overall structure of the wide-area network system in this embodiment Section 1.9 Description of the local network system structure in this embodiment Chapter 2 Examples of the use of composite modules within a local network system Chapter 3: Overview of the Hierarchical Structure and Data Structure of Communication Information Section 2.1 Hierarchical Structure of Network Communication-Related Functions in This Embodiment Section 2.2 Relationship between the Hierarchical Structure of Communication-Related Functions and Communication Information on Network Lines Section 2.3 Z-Format Data Structure in the Physical Layer and Media Access Layer Section 2.4 Data Structure of the Internet Protocol Version 6 Layer Section 2.5 C-Format Data Structure in the Communication Middleware Layer Section 2.6 E-Format Data Structure in the Communication Middleware Layer Section 2.7 A-Format Data Structure in the Communication Middleware Layer Section 2.8 Address Table Used in This Embodiment System and Examples of Its Use Chapter 3: Management / Display Methods for Each Unit Section 3.1 Overview of Basic Unit Management Methods Section 3.2 3.3 Specific examples of unit management and display examples Chapter 4 Section 4 Overview of sections within this embodiment system 4.1 Positioning of sections within this embodiment system 4.2 Management method for the placement of various modules and equipment within sections 4.3 Processing method from information collection to service provision for each section 4.4 Tracking method for inter-section movement of various modules and equipment 4.5 Compatibility of units (composite modules and equipment) between different systems Chapter 5 Application examples for each application field 5.1 Application examples for the consumer sector 5.1.1 Examples of applications of wide-area network systems to the consumer sector 5.1.2 Section Examples of applications of composite modules to the consumer sector 5.1.3 Section Examples of applications of section division methods to the consumer sector 5.2 Section Examples of applications to social infrastructure 5.2.1 Section Examples of applications of wide-area network systems to social infrastructure 5.2.2 Section Examples of applications of composite modules to social infrastructure 5.2.3 Section Examples of applications of section division methods to social infrastructure 5.3 Section Examples of applications to healthcare 5.3.1 Section Examples of applications of wide-area network systems to healthcare 5.3.2 Section Examples of applications of composite modules to healthcare 5.3.3 Section Examples of applications of section division methods to healthcare Chapter 6 Smart Home Appliance Automatic Control Methods 6.1 Section Relationship between Automatic Control-Compatible Smart Home Appliances and Smart Home Appliance Related Devices 6.2 Section Overview of Control Methods for Automatic Control-Compatible Smart Home Appliances 6.3 Section Communication Information with Smart Home Appliance Related Devices 6.4 Section Methods for Estimating / Determining User Behavior and State 6.5 Section Other embodiments of automatic control between smart home appliances Next, following the table of contents above, the following will be a description of each chapter / section.

[0016] Chapter 1 Overall System Overview in this Embodiment 1.1 Overview of the System in this Embodiment First, we will provide an overview of the system in this embodiment using Figures 1 and 2. Figure 1 shows the overall structure of the wide-area network system within this embodiment, and Figure 2 shows the structure of the local network system that constitutes a part of that wide-area network system. Furthermore, the embodiments, service contents, and newly arising effects described in Figure 1 are applied exactly to the embodiment system shown in Figure 2. Similarly, the embodiments, service contents, and newly arising effects described using Figure 2 (or later using Figures 8A to 8B and Figure 9) are also applied to the entire wide-area network system in Figure 1.

[0017] In Figure 1, the central organization or institution handling the specified goods or information is referred to as wholesaler A_1102, B1 / 2_1104-1 / 2. The organization or group providing the specified service is referred to as service provider A~C_1112-1~3. Each service provider A~C_1112-1~3 possesses one or more servers 1~n_1116-1~n. In this embodiment of the system, the servers 1~n_1116-1~n are also referred to as cloud servers or clouds. These service providers A~C_1112-1~3 obtain goods (or information) from wholesaler B1_1104-1 and / or wholesaler B2_1104-2, which handle similar goods (or information), and provide services to each domain 1~3_1122-1~3. Here, domains 1-3_1122-1-3 represent predetermined network spaces, and one domain 2_1122-2 consists of one or more systems α_1132 and β_1134. In the following explanation, the above systems α_1132 and β_1134 may also be referred to as a network system or a client system. Therefore, the terms "network system" or "client system" used in the following explanation are synonymous with the above "systems α_1132 and β_1134". As mentioned above, one domain 2_1122-2 may be composed of multiple different systems α_1132 and β_1134. Therefore, in the following explanation, the above domain 2_1122-2 may be referred to as a composite client system. Thus, the term "composite client" used in the following explanation is synonymous with "domain 2_1122-2".

[0018] In addition, wholesalers A_1102 and B1 / 2_1104-1 / 2 and service providers A~C_1112-1~3 and domains 1~3_1122-1~3 are each connected via a network. Furthermore, each of the service providers A~C_1112-1~3 is also connected via a network, enabling them to share information and exchange resources with one another.

[0019] The system α_1132 shown in Figure 1 represents the smallest network system unit whose internal systems are interconnected via a network. Within this system α_1132, there is often one system controller α_1126. This system controller α_1126 manages or operates the (network) system. However, the smallest network system unit, a single system β_1134, may consist of only one system controller β_1128. Furthermore, systems α_1132 and β_1134, which constitute the same domain 2_1122-2, may be physically separated from each other. Moreover, collaborative processing between different systems α_1132 and β_1134 within the same domain 2_1122-2 is also possible.

[0020] In this embodiment of the system, a predetermined service unit provided to a user within the same system α_1132 is defined as section 1~m_1142-1~m. However, it is not limited to this, and a unit related to the integration, management, or control of information collected within the same system α_1132 may also be defined as section 1~m_1142-1~m. Naturally, the same section 1~m_1142-1~m may serve both as a service unit for the user and as an information integration / management / control unit. By providing services and collecting / managing information in this section 1~m_1142-1~m unit, the efficiency of service provision and information collection / management is increased, and user convenience is improved.

[0021] Figure 2 shows the structure of the local network system formed by system α_1132 in Figure 1. The system controller α_1126 contains a processor 1230 and a memory unit 1232, and network communication within system α_1132 is performed via the communication module 1202-3. In parallel, system controller α_1126 is also capable of network communication with the outside world via the same communication module 1202-3.

[0022] In this embodiment, basic units having network communication functions other than the system controller α_1126 within the network system α_1132 are defined as units 1-7_1290-1-7. In this embodiment, various predetermined functions scattered within the network system α_1132 are managed or controlled on a unit basis. This facilitates integrated management / control of various functions within the same network system α_1132, regardless of the physical form of the units. Figure 2 shows an example in which each unit 1-7_1290-1-7 incorporates a communication module 1202-4-10 as a means of realizing the network communication function. However, this is not the only means of realizing the network communication function; for example, a part of a predetermined module or a part of a device may have the network communication function. Alternatively, the network communication function may be realized as part of the functions within specific software.

[0023] In this embodiment of the system, the system controller α_1126 is basically responsible for managing, operating, and controlling network communication within the network system α_1132. As shown in Figure 2, the system controller α_1126 is often physically installed within the network system α_1132. In this case, each unit 1-7_1290-1-7 in Figure 2 can individually communicate directly with the system controller α_1126. However, as will be described later in Figure 9, a system controller β_1128, physically installed outside the network system α_1132, may also manage, operate, and control network communication within the network system α_1132. Furthermore, independent information communication between different units 1-7_1290-1-7 is also possible under the management of either system controller α_1126 or system controller β_1128.

[0024] Section 1.2 Description of Unit Configuration As explained in the previous section, the system controller α_1126 manages or controls various predetermined functions scattered within system α_1132 on a unit basis. In other words, as shown in Figure 2, many different means of realizing various functions are scattered within the same network system α_1132, and conventionally, their integrated management and control have been extremely complicated. Furthermore, the physical forms of the units that realize various functions are diverse, including equipment 1250, composite modules 1295 (this composite module will be described later in Section 1.3), sensor modules 1260, and drive modules 1270. Therefore, integrated management and control become even more complex.

[0025] To address this increasing complexity, this embodiment of the system is characterized by managing and controlling the diverse functional implementation means scattered within the network system α_1132 as units based on network communication functions (with each individual network communication function implementation means serving as the basic unit). In other words, a single function or a collection of multiple functions that can be implemented in conjunction with a minimum network communication function are grouped under the common, generalized concept of a unit. Furthermore, as mentioned above, individual units can take on diverse physical forms, but management, control, or information gathering is performed using a common, generalized unit that is independent of specific physical forms as the basic unit. By defining units that are independent of individual functions and physical forms as management units (or control / information gathering units) within the network system α_1132 in this way, the management or control / information gathering within the network system α_1132 by system controller α_1126 or system controller β_1128 can be significantly simplified. (Specific examples of management / control using units will be described later in Chapter 3.) As an example of a specific physical form of a unit, as shown in Figure 2, the entire device 1_1250-1 may correspond to unit 4_1290-4, or the entire composite modules 1_1295-1 and 7_1295-7, which exist independently, may correspond to units 1_1290-1 and 7_1290-7. Furthermore, it is not limited to these, composite modules 6_1295-6, 2_1295-2, and 3_1295-3, which constitute parts of device 2_1250-2 and device 5_1250-5, may correspond to units 6_1290-6, 2_1290-2, and 3_1290-3, respectively. Incidentally, in Figure 2, units 2_1290-2 and 3_1290-3 overlap at the communication module 1202-10. Thus, in this embodiment, partial overlap between different units 2_1290-2 and 3_1290-3 is permitted. Furthermore, there may be inclusion relationships between different units (a state in which one unit is completely contained within another unit).

[0026] Figure 2 shows a specific example, but Figure 3A will explain the general forms that a unit can take. In the unit configuration shown in Figure 3A(a), the entire device 1250 with network communication capabilities corresponds to a single unit 1290. If this device 1250 has complex multi-functions, the unit 1290 also has similarly complex multi-functions and is managed or controlled / information collected within the network system α_1132 as a basic unit.

[0027] On the other hand, as shown in Figure 3A(b), a composite module 1295 (specific details of which will be described later in Section 1.3) existing independently within the network system α_1132 may be associated with a single unit 1290. Furthermore, as another management configuration (or control / information collection unit configuration), a specific device 1250 (which may or may not have its own network communication function) may be expanded by adding or connecting a predetermined composite module 1295, and the entire resulting expanded device may be considered as a single unit 1290, as shown in Figure 3A(c).

[0028] The unit configuration defined within device 5_1250-5 shown in Figure 2 will be explained more clearly using Figure 3B. As shown in Figure 3B, device 5_1250-5 contains one sensor module 1260-9 with sensor functionality and two drive modules 1_1270-5 and 2_1270-6, each with different drive or operating functions. Furthermore, a communication module 1202-10 is incorporated, which has network communication functionality with the system controller α_1126 within the network system α_1132. Device 5_1250-5 also has a device controller 1240-3 that comprehensively controls the operation of these modules and comprehensively collects and manages their state information and the sensor information obtained therefrom. Information acquired or independently generated by the device controller 1240-3 can be stored in the memory unit 1246.

[0029] As mentioned above, the system controller α_1126 or system controller β_1128 can be appropriately configured (defined) as the standard unit for optimal management or control / information collection within the network system α_1132. For example, if the system controller α_1126 or system controller β_1128 wants to control / collect information in detail on the individual sensor functions and drive (operation) functions within device 5_1250-5 via the network (i.e., via the communication module 1202-10), then unit 2_1290-2 is configured as shown in Figure 3B(a). In this case, unit 2_1290-2 consists of sensor module 1260-9, two drive modules 1_1270-5 and 2_1270-6, and communication module 1202-10. Then, the system controller α_1126 (or system controller β_1128) can perform fine-grained control over the individual modules within unit 2_1290-2.

[0030] In contrast, as shown in Figure 3B(b), unit 3_1290-3 consists only of the communication module 1202-10 and the device controller 1240-3. Therefore, when system controller α_1126 (or system controller β_1128) communicates information with unit 3_1290-3, it becomes possible to integrate advanced control or integrated information collection for the entire device 5_1250-5. Furthermore, information communication with unit 3_1290-3 does not require the detailed information communication processing for each module that is required when communicating with unit 2_1290-2. Therefore, when unit 3_1290-3 is set (defined), the processing within system controller α_1126 (or system controller β_1128) is greatly simplified and processing efficiency is improved. As described above, when the form (configuration) of unit 1290 changes, the content of the communication information between system controller α_1126 (system controller β_1128) and unit 1290 changes.

[0031] As mentioned above, the unit takes the form of a predetermined function realized in conjunction with a minimum network communication function. Therefore, the unit has a minimum network communication function. As an example of how this network communication function is realized, if the communication module 1202-10 is configured as shown in Figure 3B, the unit will include the communication module 1202-10. As a result, as shown in Figure 3B(c), the communication module 1202-10 is a common part and overlaps between unit 2_1290-2 and unit 3_1290-3.

[0032] As described above, by making it possible to configure multiple different units with overlapping functionality within the same functional area, and by allowing flexible configuration of the specific form of unit 1290 within the network system α_1132, the degree of freedom in the management (or control / information gathering) of system controller α_1126 (or system controller β_1128) is improved.

[0033] Section 1.3 Description of the Configuration within the Composite Module As one form of the composite module 1295, Figure 3A(b) shows the configuration of the composite module 1295. In this embodiment, the composite module is defined as a functional module capable of realizing communication functions and other functions besides communication functions. A particular feature is that the communication function is involved in realizing the aforementioned other functions. Information communication with the outside (outside the composite module 1295) regarding the aforementioned other functions is carried out via this communication function. That is, by using the communication function within the composite module 1295, it is possible to collect information obtained as a result of performing a specific function of the composite module 1295 from the outside (outside the composite module 1295). On the other hand, the communication function within the composite module 1295 may also be used to control a specific function of the composite module 1295 from the outside (outside the composite module 1295).

[0034] Here, specific examples of the aforementioned other functions include sensor functions, drive (or operation) functions, control (process) functions, memory functions, and display functions. However, the composite module is not limited to these, and may have any function other than communication functions. In particular, a composite module with sensor functions is called a sensor / communication module 1460, and a composite module with drive (or operation) functions is called a drive / communication module 1470. Furthermore, a composite module with control (process) functions is called a processor / communication module 1465, a composite module with memory functions is called a memory / communication module 1475, and a composite module with display functions is called a display / communication module 1478.

[0035] Next, we will explain the difference between the composite module described here and the unit described in Section 1.2. The composite module 1295 can constitute a part of the device 1290 as a predetermined module. Furthermore, the composite module 1295 may exist independently within the network system. In contrast, the unit 1290 represents a basic unit for management, control, and information gathering within the network system, common and generalized for various forms such as the device 1290, the composite module 1295, or combinations thereof. Therefore, as shown in Figure 3A(b), there is an inclusion relationship where one or more composite modules 1295 can be included within a single unit 1290. For example, while the device 1290 corresponds to one form of the unit 1290, the composite module 1295 merely constitutes a part of the device 1290. In this inclusion relationship, the means for realizing the communication function described above are commonly possessed both within the unit 1290 and within the composite module 1295. Incidentally, in Section 1.2, it was explained that the system controller α_1126 is not included in the unit 1290. In contrast, a major difference from unit 1290 is that a portion of the system controller α_1126 can be configured in the composite module 1295.

[0036] The means of implementing communication functions and other functions within a composite module may be either software (program) or hardware (circuit), or they may be implemented using a combination of software and hardware (partially implemented in hardware and the rest in software). Furthermore, the above-mentioned communication functions and other functions do not need to be separated in either software or hardware; the means of implementing both functions may coexist in either software or hardware, or there may be some overlap or inclusion relationships. Moreover, the means of implementing both functions do not necessarily need to be directly linked in either software or hardware. In other words, the means of implementing communication functions and the means of implementing other functions may be separated and located far apart in hardware or program, and a configuration in which the means of implementing both functions can cooperate using some kind of linking mechanism is also acceptable.

[0037] For the sake of explanation, the configuration within the composite module is shown as a block structure in Figures 4A to 4F. These blocks may be predetermined circuits (hardware) or predetermined programs (software). Furthermore, each block does not necessarily need to be separated in terms of software or hardware; as mentioned above, there may be mixed / distributed / partially overlapping (shared) / inclusion relationships between blocks.

[0038] Figure 4A shows the basic configuration of the composite module 1295. The composite module 1295 has a communication module 1660 as a means of realizing the communication function within the module. In Figure 4A(a), the antenna 1480 for transmitting and receiving wireless signals is located separately and connected to the communication module 1660. On the other hand, in Figure 4A(b), the antenna for transmitting and receiving wireless signals is built into the communication module, forming an antenna-integrated communication module 1666. Furthermore, this antenna-integrated communication module 1666 has a structure that allows it to be functionally connected (they work together) to a multi-function module (functions other than communication) 1440 that realizes functions other than communication. However, as shown in Figure 4A(b), it is not necessarily required that the antenna-integrated communication module 1666 and the multi-function module 1440 be directly connected; it is sufficient if some kind of link is formed between the functions of the two. As an example of link formation, as shown in Figure 4A(a), a communication module 1660 and a multi-function module (functions other than communication) 1440, which are located far apart from each other, can be connected by a long-distance cable or the like, and the two may remotely cooperate 1444. (For example, if a composite module is configured with software, and the program that constitutes the communication module 1660 and the program that constitutes the multi-function module 1440 are located on servers in remote locations, the two programs may cooperate in processing via link data (such as a URL (Uniform Resource Locator)) corresponding to the remote cooperation 1444.) For example, if it is desired to operate the multi-function module (functions other than communication) 1440 in a special environment where wireless transmission and reception (realization of communication function by the communication module 1660 using the antenna 1480) is impossible, such as underground, deep underwater, or in a secluded place inside a steel-frame building, the above-mentioned remote cooperation 1444 has the effect of allowing the composite module 1295 to function stably even in a special environment. Furthermore, the configuration of the composite module does not prohibit any configuration other than that shown in Figure 4A. For example, the antenna-integrated communication module 1666 and the other-function module (functions other than communication) 1440 may be located remotely, and the two may be remotely connected by long-distance cables 1444.

[0039] Figure 4B shows an example configuration of the composite module 1295 using the sensor / communication module 1460. In Figure 4A, the part of the multi-function module (functions other than communication) 1440 is the sensor module 1260. This sensor module 1260 refers to a sensor function unit that has a quantitative or qualitative information acquisition function or a signal detection function within a predetermined system α_1132. This sensor module 1260 has the attribute of being installable or movable (portable) within the predetermined system α_1132 and can contribute to state measurement and observation within the corresponding system α_1132.

[0040] Specific examples of objects to be sensed include common human information such as body temperature, pulse, heart rate, and respiratory rate; identifiable information such as facial expressions, individual face shapes and appearances, and size information such as height and width; physical information such as illuminance (brightness), acceleration, temperature, humidity, power / current / voltage, and flow rate (of water, gas, etc.); the number of people present in a designated section 1142, congestion levels, or human presence detection information; movement information such as the movement of people and vehicles; and structural information such as the temperature, strain, shape, number of cracks, and internal cavity volume of structures. However, it is not limited to these, and any senseable object may be used.

[0041] Figure 4C shows an example configuration using the drive / communication module 1470 as the next example of the composite module 1295. In Figure 4A, the part of the multi-function module (functions other than communication) 1440 is the drive module 1670. Alternatively, the external antenna 1480 and the communication module 1660 may be connected (Figure 4C(b)), or it may be composed of an antenna-integrated communication module 1666 that includes an antenna for transmitting and receiving wireless signals (Figure 4C(a)). In the embodiment of Figure 4C(a), the antenna-integrated communication module 1666 and the drive module 1670 are located in different locations, and the two can remotely cooperate 1444 via a remote cable or the like. However, it is not limited to this, and it is also possible to have a configuration in which the communication module 1660, which can be connected to the external antenna 1480, and the drive module 1670 remotely cooperate 1444.

[0042] The drive module 1670 as defined herein refers to a service provision-related function unit for providing a specific service, or a state change control function unit used to control predetermined state changes within system α_1132. The term "actuator" used in the term drive module here is easily misunderstood as being limited only to movable or operating parts that actually move, but it does not necessarily have to involve movement. Therefore, specific examples of the functions of the above drive module may include display functions such as sound and images, functions to maintain or change the brightness of lights or the intensity of smells, predetermined information transmission functions (such as remote control functions) or information communication relay functions that form part of the information transmission path for controlling these functions, or remote control functions (of predetermined equipment 1250).

[0043] The sensor / communication module 1460 and the drive / communication module 1470 described so far often communicate information relatively passively in response to control from the system controller α_1126 (or system controller β_1128). In contrast, the processor / communication module 1465 shown in Figure 4D exhibits relatively spontaneous or active functions. In this embodiment, the means of realizing the control (process) function within the processor / communication module 1465 may include not only the device controller 1240 in the device 1250, but also the processor 1230 in the system controller α_1126 (Figure 2) and the processor 1734 in the system controller β_1128 (Figure 17A / B). In particular, the communication modules 1202-3 in the system controller α_1126 and system controller β_1128 enable information communication with devices installed outside of the system α_1132 and system β_1134 (e.g., server α_1116-n). Here, the composite module 1295 is at least required to have information communication functionality within system α_1132 (or system β_1134). Therefore, in Figure 4D, the communication module 1202-3 is functionally separated into an in-system communication module 1752 and an out-of-system communication module 1758, and only the in-system communication module 1752 constitutes the processor / communication module 1465. However, it is not limited to this, and the out-of-system communication module 1758 may also be included within the processor / communication module 1465. Also, when the configured (defined) processor / communication module 1465 exists within device 1250, the out-of-system communication module 1758 is often not originally included within device 1250.

[0044] When the processor / communication module 1465 performs relatively spontaneous or active functions within the network system α_1132 (or β_1134), it often utilizes the information recorded in the management information (table) related information recording area 1740, which will be described later using Figure 10A / B. Therefore, when the processor / communication module 1465 is required to perform spontaneous / active functions, the processor / communication module 1465 may include parts of the memory sections 1242 and 1246 in the device 1250, parts of the memory section 1232 in the system controller α_1126 (Figure 2), or parts of the memory section 1248 in the system controller β_1128 (Figure 17A / B).

[0045] For example, when the system controller α_1126 reads information recorded in the memory section 1242 of device 1_1250-1 in Figure 2, it is generally necessary to exchange sophisticated communication information between the processor 1230 in the system controller α_1126 and the device controller 1240-1 in device 1_1250-1. In contrast, as shown in Figure 4E, by having a memory / communication module 1475 consisting only of a recording area 1740 for management information (tables) related to memory sections 1242, 1246, 1232, and 1248 and a corresponding in-system communication module 1752, the system controller α_1126 (or system controller β_1128) can directly communicate information with the memory / communication module 1475 using a very simplified communication protocol. Therefore, the memory / communication module 1475 has the effect of simplifying the communication of information recorded in the recording area 1740 for management information (tables) related to memory.

[0046] Figures 4B to 4E only describe single-function examples of the functions implemented by the multi-function module 1440 in Figure 4A. However, as shown in Figure 4F, multiple different functions may be implemented within a single composite module 1295. For example, multiple different sensing functions (sensor modules 1_1260-1 and 2_1260-2), multiple different driving (operation) functions (driving modules 1_1670-1 and 21670-2), control (process) functions (processors 1230 and 1734 or device controller 1240), memory functions (memory units 1232 and 1248), and display functions (display module 1226) may be implemented simultaneously within the composite module 1295. Alternatively, as shown in the embodiment in Figure 4F, the sensor module 1_1260-1 and the drive module 1670-2 may be individually positioned far away from the location where the antenna 1480 and the communication module 1660 are connected, and a structure may be adopted that allows for remote communication 1444 using long-distance cables or the like.

[0047] In Figure 4F, each of the multi-function modules, which have functions other than communication, is individually wired and connected to the communication module 1660. However, instead of connecting each multi-function module individually, the communication module 1660 and a number of multi-function modules may be connected to a common bus line. In this case, the multi-function module directly connected to the communication module 1660 will switch over time based on a selector action or addressing.

[0048] Section 1.4 Explanation of the Structure within the Sensor / Communication Module Figure 5 shows a more specific and detailed example of the structure within the sensor / communication module 1460, which was outlined in Figure 4B. In its basic structure, the sensor signal or detection information obtained by the sensor module 1260 is transferred to the communication module 1660. This sensor signal or detection information is transmitted via the communication module 1660 to the communication module 1202-3 (Figure 2) in the system controller α_1126. Here, the processing of information communicated by the communication middleware layer APL02, which conforms to the C-format and other standards described later in Chapter 2 using Figures 10A and 10B, is also performed within the communication module 1660 in Figure 5.

[0049] On the other hand, the power supplied to the sensor module 1260 and the communication module 1660 is obtained from the energy storage module (battery) 1554. Furthermore, the sensor / communication module 1460 in Figure 5 has a built-in (solar) power generation module (solar cell) 1552 with a photoelectric conversion function, and the power generated in this (solar) power generation module (solar cell) 1552 with a photoelectric conversion function is stored in the energy storage module (battery) 1554. In Figure 5, a (solar) power generation module (solar cell) 1552 with a photoelectric conversion function is shown as the means of generating power, but any other energy conversion means may be used instead. As an energy conversion means other than the above-mentioned photoelectric conversion element, a thermoelectric conversion means such as a thermocouple may be used. An end user may wear the sensor / communication module 1460 with such a built-in thermoelectric conversion means, and operate the sensor / communication module 1460 by generating power using the end user's body temperature. In further embodiments, the communication module 1660 may convert the wireless energy received from the communication module 1202-3 in the system controller α_1126 in Figure 2 into electrical power and store it, or the near-field communication module 1560, described later, may convert the near-field energy received from an external source into electrical power and store it. By incorporating energy conversion means such as a (solar) power generation module 1552 and a power storage module (battery) 1554 into the sensor / communication module 1460 in this way, the sensor / communication module 1460 can operate for a long period of time without external power supply.

[0050] When the sensor module 1260 is used to measure light, ambient temperature, or ambient humidity, or when the sensor module 1260 corresponds to a human presence sensor, the sensor module 1260 is mounted in a way that exposes it to the surface of the devices 1_1250-1, 2_1250-2, and 5_1250-5 (Figure 2). At the same time, the (solar) power generation module (solar cell) 1552 is also mounted in a way that exposes it to the surface of the devices 1_1250-1, 2_1250-2, and 5_1250-5.

[0051] If the sensor / communication module 1460 is left in a dark place for a long period of time, the amount of charge stored in the power storage module (battery) 1554 will decrease, and there is a risk that it will not be able to supply sufficient power to the sensor module 1260 and the communication module 1660. To address this, if the output voltage of the power storage module (battery) 1554 or the amount of charge stored in the power storage module (battery) 1554 falls below a predetermined reference value, the system controller α_1126 in Figure 2 is notified via the communication module 1660 as appropriate. Specifically, as will be explained in detail in Chapter 2 using Figure 14, the information that "battery level is low" is notified to the system controller α_1126 in the form of an "alarm notification" from a specific sensor / communication module 1460. When the processor 1230 in the system controller α_1126 detects a decrease in the amount of charge stored in the power storage module (battery) 1554 built into the specific sensor / communication module 1460, it notifies the end user via the user I / F unit 1234. In this way, the output voltage or amount of charge stored in the energy storage module (battery) 1554 is appropriately notified to the system controller α_1126, which prevents the operation of a specific sensor / communication module 1460 from stopping due to a decrease in the amount of charge stored, and thus ensures the operational stability of the entire system in this embodiment.

[0052] The sensor / communication module 1460 shown in Figure 5 also incorporates a near-field communication module 1560 capable of near-field wireless communication. For the near-field wireless transfer technology used here, for example, TransferJet or the contactless IC card standard FeliCa® (a portmanteau of Felicity and Card) may be applied. In addition to the external power supply mentioned above, the near-field communication module 1560 may also be used for detecting the installation location of the sensor / communication module 1460 during initial setup, as described below. Specifically, when the composite module 7_1295-7 corresponding to the sensor / communication module is installed alone in the system of this embodiment shown in Figure 2 (or when the device 2_1250-2 containing the composite module 6_1295-6 corresponding to the sensor / communication module is installed), a portable external device (not shown) with a built-in GPS (Global Positioning System) function is brought close to communicate with the near-field communication module 1560 during initial setup. The GPS location information at this time is then notified to the system controller α_1126 via the communication module 1202-3. As a result, location information of the composite module 7_1295-7 (or the device 2_1250-2, which incorporates the composite module 6_1295-6 compatible with the sensor / communication module) is registered in the system controller α_1126. This registration information is stored in the memory section 1232 (Figure 2) of the system controller α_1126, for example, as information in the format shown in Figure 23, which is explained in Chapter 2. By incorporating GPS functionality and performing initial setup via near-field communication using a portable external device, the installation location of the sensor / communication module 1460 can be determined, resulting in the ability to provide detailed services to end users.

[0053] Section 1.5 Explanation of the Structure of the Drive / Communication Module Figures 6A to 6D show more specific and detailed structural examples of the drive / communication module 1470 outlined in Figure 4C. When the externally controllable drive / communication module 1470 is used as part of the circuit (internal circuit component) within the device 1250, the circuit component functions most often utilized are those of an "ON / OFF switch," a "predetermined voltage output," or a "variable resistance value." In this embodiment, the above standard (most frequently used in circuits) functions are provided as modules within the specific device 1250. This is characterized by the reduction in cost and ease of assembly of the corresponding device 1250. As an example, Figure 6A shows the internal structure of the drive / communication module 1470 that provides the "variable resistance value" function, Figure 6B shows the internal structure of the drive / communication module 1470 that provides the "ON / OFF switch" function, and Figure 6C shows the internal structure of the drive / communication module 1470 that provides the "predetermined voltage output" function. In order to provide both the "variable resistance value" function and the "ON / OFF switch" function, input terminal 1602 and output terminal 1604 are required. Figure 6A shows a structure in which a variable resistor unit 1610 is placed between these two terminals, allowing the variable resistance value between them to be set. On the other hand, in Figure 6B, a conduction / disconnection switching unit 1614 is placed between the two terminals to form an ON / OFF switch between them. CMOS (Complementary Metal-oxide-Semiconductor) type FET (Field-effect Transistor) elements may be used as the specific circuit elements for the variable resistor unit 1610 and the conduction / disconnection switching unit 1614. Here, an element with a smooth gamma characteristic (resistance value characteristic between input terminal 1602 and output terminal 1604 in response to the input voltage applied to the variable resistor section 1610 or the conduction / disconnection switching section 1614) (an element whose resistance value changes slowly even when the applied input voltage value is changed significantly) can be used in the variable resistor section 1610, and an element with a steep gamma characteristic (an element whose resistance value changes rapidly from a conduction state where the resistance value is close to "0" to a disconnection state where the resistance value is "very large" with only a slight change in input voltage around a predetermined threshold) can be used in the conduction / disconnection switching section 1614.However, in this embodiment, the circuit is not limited to the CMOS type FET element described above, but any circuit element that provides a variable resistance value through some control or an ON / OFF switch function may be used. On the other hand, the terminal that outputs the "predetermined voltage" may be a single terminal of the voltage output terminal 1606, as shown in Figure 6C. The output voltage output by this terminal is connected to the output of the predetermined voltage generation unit 1618 in the drive module 1670. As a specific example of the circuit in this predetermined voltage generation unit 1618, in this embodiment, an intermediate voltage is extracted from a variable resistor connected between a constant voltage source generated inside the drive / communication module 1470 or a constant voltage supplied from the outside (e.g., power supply voltage) and the ground line (earth line), and this extracted voltage is maintained by a current supply buffer circuit (an electronic circuit that can supply a relatively large external current to maintain the output voltage even when the external impedance is low). However, the circuit is not limited to this, and any method or circuit that can generate and maintain the predetermined voltage may be used.

[0054] In all of Figures 6A to 6C, the set value is provided by the communication module 1660, which is located outside the drive module 1670. A feature of this embodiment is that it has an internal storage section for the set value so that the set value does not change even if the power to the drive / communication module 1470 is cut off. The parts corresponding to this storage section are the set resistance value storage unit 1620 in Figure 6A, the set state storage unit 1624 in Figure 6B, and the set voltage storage unit 1628 in Figure 6C. These are all composed of non-volatile semiconductor memory such as NAND (Not And) memory as an example. However, they are not limited to this, and the above storage section may be composed of any non-volatile memory. That is, in all of Figures 6A to 6C, the set value notified from the communication module 1660 is once transmitted to the set resistance value storage unit 1620, the set state storage unit 1624, or the set voltage storage unit 1628, and is stored non-volatilely in those storage sections. Simultaneously, the stored setting values ​​are output from these memory sections to control the operation of the variable resistor section 1610, the conduction / disconnection switching section 1614, or the predetermined voltage generation section 1618.

[0055] If drive modules 1270-1 and 1270-6 are used to control or change the settings of devices 1_1250-1 and 5_1250-5 in Figure 2, then an extended form of an existing infrared communication-based remote control may be adopted as the specific form of these drive modules 1270-1 and 1270-6. That is, the drive module 1270-1 and communication module 1202-4 within device 1_1250-1 constitute a drive / communication module 1470 (a type of composite module 1295), allowing it to be placed at a separate location outside device 1_1250-1 as a "new type of remote control". Similarly, the drive module 1270-5 within device 5_1250-5 and a part of the communication module 1202-10 may constitute a drive / communication module 1470 (a type of composite module 1295), allowing it to be placed at a separate location outside device 5_1250-5 as a "new type of remote control". As a concrete example, this "new type of remote control" could be used as an extension (replacement) for conventional infrared communication-based remote controls that come with air conditioners, televisions, lighting equipment, etc.

[0056] Figure 6D shows the internal structure of the drive / communication module 1470 adapted to this usage method. In the embodiment shown in Figure 6D, it is possible to handle both control of transitions between binary states such as "ON / OFF switching" (change of state settings) and control related to "fine-grained changes in state settings using multi-level information". Furthermore, control of transitions between binary states (change of state settings) from the communication module 1660, which receives communication information exchanged within the network system α_1132, is stored or updated in the setting state storage unit 1624. On the other hand, control information related to "fine-grained changes in state settings using multi-level information" sent from the communication module 1660 is stored or updated in the setting voltage storage unit 1628.

[0057] The information stored or updated in the setting state memory unit 1624 and the setting voltage memory unit 1628 is then format-converted by the format conversion unit 1644, modulated by the infrared light-emitting element 1608 via the infrared light-emitting drive circuit 1648, and reaches the remote-controlled infrared receiver in the device 1_1250-1 or 5_1250-5. This allows many existing devices such as air conditioners, televisions, and lighting equipment 1_1250-1 or 5_1250-5 to be incorporated into the network system α_1132 inexpensively and easily by simply replacing the existing infrared communication remote control with the drive / communication module 1470 shown in Figure 6D, without having to replace the main unit of the existing device 1250.

[0058] Here, the minimum required functions of an existing remote control do not necessarily need to store the state when the device 1250 is controlled. However, since the setting state storage unit 1624 and the setting voltage storage unit 1628 are built into the drive module 1670 within the drive / communication module 1460, the system controller α_1126 can later check the control history via the communication module 1660. Note that the setting state storage unit 1624 and the setting voltage storage unit 1628 may use NAND (Not And) memory or other non-volatile memory as described above.

[0059] Here, the C-format, which will be described in detail in Chapter 2, may be used as the communication information transmitted between the system controller α_1126 and the drive / communication module 1470. Below, the method of transferring the communication information exchanged with the system controller α_1126 in Figure 2 within the drive / communication module 1470 based on the C-format will be explained. However, information communication processing with the system controller α_1126 may be performed using A-format, E-format, or any other arbitrary format.

[0060] First, when the system controller α_1126 issues a command to start operation (turn on the power) for the existing device 1250, the communication access control information 1830 in the communication information (Figure 14(d)) from the system controller α_1126 to the corresponding drive / communication module 1470 is set to

[0111] (reset instruction), the multi-level transmission data section CTMDT is set to

[0000] , and the value of the binary transmission data section CT2DT is set to [1] (ON). When the communication module 1660 receives this information, the information [1] (power ON) is transferred / stored in the setting state storage unit 1624 in the drive module 1670. This information also passes through the setting state storage unit 1624 and is notified to the format conversion unit 1644, where it is converted into information indicating power ON for the existing remote control. This converted information is then transferred to the infrared light emission drive circuit 1648, and the emission of the infrared light-emitting element 1608 is controlled. The converted information is then transmitted to the existing device 1250, and the device 1250 is powered on.

[0061] In the C-format shown in Figure 14(d), it is also possible to change (reset) multi-level information corresponding to, for example, a change in the set temperature of an air conditioner or a change in the illuminance of lighting equipment. In this case, the communication access control information 1830 in the communication information from the system controller α_1126 to the drive / communication module 1470 (Figure 14(d)) is set to

[0111] (reset instruction), and the multi-level transmission data section CTMDT is set to something other than

[0000] . In this case, in the 5-bit information combining the multi-level transmission data section CTMDT and the binary transmission data section CT2DT, values ​​from

[0010] to

[11111] are assigned to the range from 0% to 100%, respectively. Next, when the communication module 1660 receives this information, the changed setting value is converted to a percentage. This percentage-converted information is then transferred / stored in the setting voltage storage unit 1628. This information is then passed through the setting voltage storage unit 1628 and notified to the format conversion unit 1644, where it is converted into information indicating the state setting change value for the existing remote control. This converted information then activates the infrared light emission drive circuit 1648, which controls the emission of the infrared light-emitting element 1608, thereby changing the setting state of the existing device 1250.

[0062] Next, we will explain how the system controller α_1126 can check the state already set in the drive / communication module 1470. In this case, the system controller α_1126 first communicates communication information to the drive / communication module 1470 with the communication access control information 1830 set to

[0011] (response (data) request). When the communication module 1660 in Figure 6D receives the response (data) request from the system controller α_1126, it reads the information already stored in the setting state storage unit 1624 and the setting voltage storage unit 1628. The result is then set in the binary transmission data unit CT2DT or the multi-level transmission data unit CTMDT in Figure 14(d). Here, the communication access control information 1830 in the communication information communicated from the drive / communication module 1470 to the system controller α_1126 is set to

[0010] (response answer).

[0063] With the aim of simplifying the explanation of the operation of the drive / communication module 1470 in this embodiment, the operation of the drive / communication module 1470 has been disclosed in hardware (electrical circuit) form until now. However, it is not limited to this, and in this embodiment, the drive / communication module 1470 may also be formed as a software module. However, even when the drive / communication module 1470 is formed as a software module in this way, input / output terminals 1602, 1604 or voltage output terminal 1606 or infrared light-emitting element 1608 as shown in Figures 6A to 6D are installed. The following is an explanation of the case using a software module. In the communication modules 1202-4 to 10 in Figure 2 and the communication module 1660 in Figures 6A to 6D, processors 1960 and 1736 are built in, as shown in Figures 7A and 7B, and perform communication control processing according to a predetermined communication control program. This communication control program can be any programming language that can be executed within the above-mentioned processors 1960 and 1736.

[0064] From this point forward, the entire communication control program will be referred to as the "main program," and a block of specific small programs called from this main program will be called a "subprogram module" in the explanation. However, the explanation will not be limited to these, and will also include Java® scripts that are OS (Operating System) independent or Java applets that support HTML / HTML5, and will include terminology used in Java. Within the main program (Class) that causes the processor built into the communication module 1660 in Figures 6A to 6D, processing is performed according to the subprogram module (Specific Method) corresponding to the drive module 1670. Within this subprogram module (Specific Method), corresponding processing for input / output terminals 1602, 1604 or voltage output terminal 1606 is performed based on the settings values ​​set in advance within the subprogram module (Specific Method). Then, when a setting change command is sent from the system controller α_1126 in Figure 2 to the drive / communication module 1470 (command issued), the main program (class) calls another subprogram module (another method) that handles the "setting value change" process to perform the setting value change. After that, corresponding processing is performed for the input / output terminals 1602, 1604 or the voltage output terminal 1606 based on the changed setting value.

[0065] In the above explanation, the drive / communication module 1470, which is included in one type of composite module 1295, was used as an example. However, it is not limited to this; any composite module 1295, such as the sensor / communication module 1460, processor / communication module 1465, or memory / communication module 1475, may be implemented using the aforementioned software modules.

[0066] Furthermore, for the sake of simplicity, the descriptions in Figures 6A to 6D have been omitted, but the drive / communication module 1470 shown in Figures 6A to 6D may also incorporate energy conversion means such as a (solar) power generation module 1552, a battery storage module 1554, and a near-field communication module 1560, similar to Figure 5.

[0067] Section 1.6 Explanation of Examples of Structure within Communication Modules Figures 7A and 7B show examples of the structure within the external antenna 1480 type communication module 1660, which constitutes the composite module shown in Figures 4A to 4F. Note that in the examples of the antenna-integrated communication module 1666 and the communication module 1752 for communication within the same system shown in Figures 4A to 4E, the antenna 1480 for communication within the same system is built into the communication module 1660 shown in Figure 7A or Figure 7B.

[0068] A key feature of this embodiment is that it is designed so that the same communication module 1660 can be used in common among the system controller α_1126 (or system controller β_1128) in Figure 2, the device controllers 1240-1 and 1240-3 within equipment 1_1250-1 or equipment 5_1250-5, and the standalone composite modules 1_1295-1 and 7_1295-7. By sharing the same communication module 1660 among many component members within the same network system α_1132 (system controller α_1126 (or system controller β_1128) and unit 1290), the cost of the communication module 1660 can be reduced through economies of scale.

[0069] As a concrete method for realizing the above features, the communication module 1660 is provided with functions common to all composite modules 1295 shown in Figures 4B to 4F. The functions common to all composite modules 1295 shown in Figures 4B to 4F are: 1) support for a common communication protocol used within the same network system α_1132, and 2) support for information communication of all information related to functions other than communication. As explained in Sections 1.2 and 1.3, in the unit 1290 and composite module 1295, the communication module 1660 is always connected to other functional modules that have functions other than communication, so function [2] is particularly important.

[0070] The communication module 1660 is equipped with functions to realize [1] and [2] above. Specifically, the communication control unit 1700 in Figure 7A mainly realizes the function of [1] above. Also, the interface unit 1710 in Figure 7A mainly realizes the function of [2] above. In Figure 7A, for clarity, the communication control unit 1700 and the interface unit 1710 are shown as separate areas for each function. However, it is not limited to this, and circuits that implement the above two points may be mixed, or some functions may be shared in the same circuit.

[0071] Furthermore, in order to make the communication module 1660 more versatile and shareable among many composite modules 1295, this embodiment also features a distinctive structure for the interface section (I / F section) between it and the other functional module 1440. Specifically, the connection section between it and the other functional module 1440 is separated into a content information I / F section 1950 and an address information I / F section 1940, and the connection method is made variable depending on the type of other functional module 1440 to which it is connected. This improves versatility with various types of other functional modules 1440, resulting in the effect of being applicable to multi-purpose (diverse) composite modules 1295.

[0072] The above features will be explained in detail below. When the composite module 1295 takes the form of a single-function sensor / communication module 1460 as shown in Figures 4B and 5, or a single-function drive / communication module 1670 as shown in Figures 4C and 6A to 6D, information communication within the network system α_1132 can be established by storing only the address information specific to the composite module 1295 and the address information of the system controller α_1126 (or system controller β_1128). Therefore, when connecting to only one sensor module 1260 (Figure 4B) or only one drive module 1670 (Figure 4C) as the multi-function module 1440 (Figure 4A), the address information I / F section 1940 in Figure 7A is not used.

[0073] On the other hand, when used as part of the processor / communication module 1465 in the configuration shown in Figure 4D, within the system controller α_1126 (or system controller β_1128), the address information differs for each unit 1290 (or composite module 1295) that communicates with the network system α_1132. Therefore, the address information of the communication partner is notified from the processors 1230 and 1734 in Figure 4D to the corresponding communication module 1752 within the same system via the bus line 1490. In this case, the address information I / F unit 1940 is used as the address information transmission means (information transmission input / output terminal).

[0074] Furthermore, when used within the memory / communication module 1475 as shown in Figure 4E, the address range in which the recording area 1740 for management information (table) related information is stored within the memory sections 1242, 1246, 1232, and 1248 must be specified from the corresponding communication module 1752 within the same system via the bus line 1490. Thus, within the processor / communication module 1465 shown in Figure 4D and the memory / communication module 1475 shown in Figure 4E, both the content information I / F section 1950 and the address information I / F section 1940 shown in Figure 7A are connected to the bus line 1490.

[0075] On the other hand, at the end of Section 1.3, a method of connecting to multiple other functional modules using a common bus line instead of Figure 4F was described. In this case, the corresponding addresses of the other functional modules directly connected to the communication module 1660 are specified in a part of the address information I / F section 1940. This makes it possible to switch the other functional modules directly connected to the communication module 1660 over time.

[0076] When using wireless as the communication medium for network communication within the network system α_1132, the transmitting side transmits radio waves by supplying current to the antenna 1480, and the receiving side detects the signal by detecting the weak current flowing through the antenna 1480. Both the current supply corresponding to the antenna 1480 and the signal detection are performed within the information communication execution unit 3016.

[0077] On the other hand, the communication information exchanged between the information and communication execution unit 3016 and other communication modules 1660 via the antenna 1480 has the structure shown in Figure 11(a). (A detailed explanation of the communication information shown in Figure 11 will be described later in Section 2.2.) The communication middleware data APLDT (and extended data EXDT) shown in Figure 11(b) is processed within the interface unit 1710 in Figure 7A. That is, the communication middleware data APLDT (and extended data EXDT) is analyzed within the content extraction unit 1938, and the necessary information is transmitted to other functional modules 1440 via the content information I / F unit 1950. As a specific example, if the communication middleware data APLDT (and extended data EXDT) in Figure 11(b) contains status setting change information (control information) for the device 1250 or the drive / communication module 1470, the specific contents are decoded in the content extraction unit 1938, and the decoded result is notified to the drive module 1670 via the content information I / F unit 1950. Then, the operation (or status setting change) of the drive module 1670 is started in response to the content of that notification.

[0078] Furthermore, information input from the other function module 1440 via the content information I / F unit 1950 is formatted within the content setting unit 1934 to generate communication middleware data APLDT (and extended data EXDT). As a specific example, if the content information I / F 1950 is connected to the sensor module 1260, the sensor information obtained within the sensor module 1260 is converted into communication middleware data APLDT (and extended data EXDT) within the content setting unit 1934. This communication information is then communicated to the system controller α_1126 (or system controller β_1128) via the information communication execution unit 3016 and the antenna 1480.

[0079] The information from Figures 11(c) to 11(f) within the structure of Figure 11(a) is processed within the communication control unit 1700 of Figure 7A. Specifically, the physical layer frame generation unit 1914 generates the information from Figures 11(c) to 11(f), combines it with the information in Figure 11(b) generated in the content setting unit 1934, and transfers it to the information communication execution unit 3016 to transmit the communication information. On the other hand, when receiving communication information, the physical layer frame analysis unit 1918 analyzes the communication information having the structure of Figure 11(a), and the extracted information in Figure 11(b) is sent to the content extraction unit 1938.

[0080] Furthermore, if the address information interface unit 1940 is connected during transmission, the recipient's address information is notified via the address information interface unit 1940. Then, address information conforming to the format shown in Figure 11(a) is generated in the address information generation unit 1924, and the communication information shown in Figure 11(a) is generated in the physical layer frame generation unit 1914.

[0081] If the address information interface unit 1940 is connected upon reception, the physical layer frame analysis unit 1918 selects the information shown in Figures 11(c) to 11(f) and transfers it to the address information extraction unit 1928. The address information extraction unit 1928 then extracts only the specified address information and passes it to the address information interface unit 1940.

[0082] When this communication module 1660 is used within a single-function sensor / communication module 1460, instead of using the address information I / F unit 1940, the address information generation unit 1924 pre-stores the address information of the recipient system controller α_1126 (system controller β_1128). As a result, sense information can be automatically communicated to system controller α_1126 (system controller β_1128).

[0083] Furthermore, when this communication module 1660 is used within a single-function drive / communication module 1470, instead of using the address information interface unit 1940, it pre-stores its own address information in the address information extraction unit 1928. That is, all wireless information detected within the information communication execution unit 3016 is forwarded to the content extraction unit 1938 and the address information extraction unit 1928 via the physical layer frame analysis unit 1918, with corresponding information being transferred. The address information extraction unit 1928 then sequentially determines whether the extracted receiver address information matches its own address information. If the receiver address information does not match its own address information, the information temporarily stored in the content extraction unit 1938 is discarded accordingly. Only when the receiver address information matches its own address information is the information determined to be communication information for the corresponding composite module 1295, and the information temporarily stored in the content extraction unit 1938 is transferred to the content information interface 1950.

[0084] The series of processes described above are controlled by processor 1960. Although the connection lines for processor 1960 are omitted in Figure 7A, the wiring shown in Figure 7B, where processor 1736 is directly connected to a bus line such as BUS, is also acceptable, or processor 1960 may be directly connected to each component individually.

[0085] Another embodiment of the communication module 1660 is shown in Figure 7B. A key feature of Figure 7B is that the memory unit 1790 is built into the communication module 1660. This makes it easier to seamlessly adapt the unit 1290 containing the communication module 1660 to another system (for example, from system α_1132 to system β_1134).

[0086] Incidentally, the external module connection section 1778 in Figure 7B corresponds to the content information I / F section 1950 and the address information I / F section 1940 in Figure 7A. Also, the signal processing section 1780 in Figure 7B corresponds to the content extraction section 1938 and the content setting section 1934 in Figure 7A. Furthermore, the signal processing section 1780 in Figure 7B may also correspond to the address information extraction section 1928 and the address information generation section 1924 in Figure 7A, or even further to the information communication execution section 3016, the physical layer frame analysis section 1918, and the physical layer frame generation section 1914.

[0087] As shown in Figure 7B, the communication module 1660 is used by being attached, embedded, bonded, or mounted to a multi-function module 1440 that has functions other than communication, as shown in Figure 4A. The attachment, embedding, bonding, or mounting of the communication module 1660 constitutes a composite module 1295. Then, as shown in Figure 3A(b) or (c), a unit 1290 including this composite module 1295 is formed. This unit 1290 can take various forms such as parts, products, goods, devices, materials, and other items. Therefore, the communication module 1660 is used by being attached, embedded, bonded, or mounted to any object to which it is integrated, such as any part, product, goods, device, material, or other item (unit 1290).

[0088] The communication module 1660 described above specifically has various functional blocks constructed on an insulating substrate 1660-1 using integration technology. The communication module 1660 includes an antenna connection section 1774 for connecting an antenna ANT_1772 for transmitting and receiving wireless signals 1770. Here, the antenna ANT_1772 may be configured on the insulating substrate 1660-1 of the communication module 1660. The communication module 1660 also includes an external module connection section 1778, through which it can be connected to, for example, multiple other functional modules 1766-1, 1766-2, ... 1766-n. Examples of other functional modules 1766-1, 1766-2, ... 1766-n include a sensor module 1260 and / or a drive module 1670, a processor module 1680, a memory module 1680, a display module 1226, and the like.

[0089] Various types of sensors can be used as the sensor module 1260 in the multi-function module 1766-1-1766-n. These sensors perform functions such as temperature detection, humidity detection, pressure detection, strain detection, water quality detection (including those utilizing chemical reactions and filtration), gas detection (including those utilizing chemical reactions), light / dark detection, ultrasonic detection, color detection, and pulse detection. One or more of these sensors are selectively configured depending on the operating environment of the communication module 1660. Furthermore, different types of sensors may be combined and provided according to the order. Some sensors are connected to the external module connection section 1778 via wireless communication (radio waves, infrared, ultrasound, etc.).

[0090] Furthermore, the specific form of the drive module 1670 used in the other functional modules 1766-1-1766-n can be arbitrarily selected according to the purpose of use, such as an electrical switch, a mechanical switch, a light-emitting element, a heating element, a displacement object (shape memory medium), or an expandable / contractible body (rubber).

[0091] Here, one or more of the multi-function modules 1766-1, 1766-2, ... 1766-n may be configured on the insulating substrate 1660-1. Additionally, some of the multi-function modules may be optionally connected via the external module connection section 1778.

[0092] The communication module 1660 also has a power supply unit 1776, and can be connected to a power supply via the power supply unit 1776. The power supply may be located at a distance from the communication module 1660. Alternatively, the power supply mounting section may be provided on the insulating substrate 1660-1, and the power supply may be integrated with the communication module 1660.

[0093] Incidentally, various methods are possible for storing power in the power source (not shown), as described below. One example of such a method is one in which current from a power generation element that generates electricity using sunlight is charged to the storage unit. This method corresponds to the combination of the (solar) power generation module 1552 and the energy storage module (battery) 1554 in Figure 5. Another method is one in which current induced in a coil due to the influence of electromagnetic waves is charged to the energy storage unit. This method corresponds to the combination of the near-field communication module 1560 and the energy storage module (battery) 1554 in Figure 5. Furthermore, there is a method in which the voltage generated in a piezoelectric element is converted into current and charged to the energy storage unit when mechanical vibration is applied to the piezoelectric element. Mechanical vibrations can be selectively used, for example, pressure and vibration due to sound, pressure and vibration due to gas (wind, gas, etc.), pressure and vibration due to liquid (water, oil, etc.), etc. Depending on the operating environment of the communication module 1660, one method or a combination of multiple methods can be selected.

[0094] The antenna connection section 1774, the external module connection section 1778, and the power supply section are connected to the signal processing section 1780. Inside the communication module 1660, the processor 1736, the memory section 1790, and the signal processing section 1780 are connected via a bus to enable mutual communication. Based on the application stored in the application storage section 1792 of the memory section 1790, the processor 1736 controls the overall operation of the communication module 1660.

[0095] The processor 1736 and signal processing unit 1780 operate according to the application, performing tasks such as acquiring output from the sensor module 1260, outputting control signals to the drive module 1670 and display module 1226, coordinating control processing with the processor module 1666, inputting and outputting recording information to the memory module 1690, supplying transmission signals to the antenna ANT_1772, acquiring received signals from the antenna ANT_, writing data to the memory unit 1790, or reading data from the memory unit 1790.

[0096] The memory unit 1790 contains an application change software storage unit 1791 and a security target data storage unit 1799. Furthermore, the memory unit 1790 also contains a drive module management data storage unit 1792, a sensor module management data storage unit 1796, a self-attribute data storage unit 1793, a lifespan management data storage unit 1794, and an operating period management data storage unit 1795.

[0097] The drive module management data storage unit 1792 inside the memory unit 1790 stores management data for the drive module 1670, which is connected via the external module connection unit 1778. The sensor module management data storage unit 1796 stores management data for the sensor module 1260, which is connected via the external module connection unit 1778.

[0098] For example, the communication module 1660 may be inspected during maintenance or before factory shipment. When an inspection device (not shown) issues a predetermined command to the communication module 1660 via the antenna ANT_1772 during inspection, the management data for the drive module 1670 stored in the drive module management data storage unit 1792 and / or the management data for the sensor module 1260 stored in the sensor module management data storage unit 1796 are read out. The read management data is transmitted to the inspection device via the antenna ANT_1772. This allows the inspection device to determine the sensing capability and driving capability of the communication module 1660.

[0099] Although not shown in Figure 7B, a processor module management data storage unit for storing management data for the processor module 1680, a memory module management data storage unit for storing management data for the memory module 1690, or a display module management data storage unit for storing management data for the display module 1226 may be provided inside the memory unit 1790.

[0100] In this embodiment, as shown in Figure 1, multiple different systems (system α_1132 and system β_1134) are formed within the same domain 2_1122-2. Similarly, one or more systems (often multiple systems) are formed within domains 1_1122-1 and 3_1122-3. Furthermore, differences in the target application fields and intended use of each system are permitted, such as for consumer goods, social infrastructure, and healthcare. Even when the composite module 1295 or unit 1290, which incorporates the communication module 1660 shown in Figure 7B, moves across multiple systems with different target application fields and intended uses, optimal operation according to each system is possible. In other words, a major feature of this embodiment is that when the composite module 1295 or unit 1290 moves between different systems α_1132 and β_1134 within the same domain 2_1122-2, or between different systems within different domains 1_1122-1, 2_1122-2, and 3_1122-3, the operation of the composite module 1295 or unit 1290 is appropriately switched to optimize it according to the applicable field and purpose of use of the system α_1132 (or system β_1134) to which it belongs. To enable this feature, the memory unit 1790 includes at least one of the following: an application storage unit 1792, an application change software storage unit (application change software) 1791, a security target data storage unit 1799 or a self-attribute data storage unit 1793, a lifespan management data storage unit 1794, and an operating period management data storage unit 1795. This also has the effect of ensuring flexible system compatibility and general-purpose use of the composite module 1295 or unit 1290 in this embodiment.

[0101] As previously explained, the communication modules 1660 and 1202 shown in Figure 7B are incorporated to form a composite module 1295 (see Figure 4) or a device 1250 (see Figure 2) to create unit 1290 (Figure 3A). At this stage of unit 1290, information may be pre-recorded in at least one of the application storage unit 1792, security target data storage unit 1799, self-attribute data storage unit 1793, lifespan management data storage unit 1794, and operating period management data storage unit 1795 using external radio waves. Alternatively, the system controller α_1126 may write the above information during a check-in process or plug-in process (described later in Section 4.2) that is performed after the user purchases unit 1290.

[0102] The application modification software storage unit 1791 described above is used when there are any modifications or changes to the application that controls the operation of the communication module 1660. For example, if the composite module 1295 or unit 1290 that incorporates this communication module 1660 is moved to a different system (for example, from system β_1134 to system α_1132), a "plug-in process" is performed each time the system to which it belongs is changed, as described later in Section 4.2. If the application field or purpose of use differs significantly between system β_1134 before the move and system α_1132 after the move, software to execute the new application is sent from system controller α_1126 (or system controller β_1128) that manages / controls / operates system α_1132 after the move, via the communication module 1202-3 in Figure 2. This software to execute the new application is then appropriately saved in the application modification software storage unit (application modification software) 1791 described above. Since the processor 1736 processes based on the software that runs the new application, when the composite module 1295 or unit 1290 is moved to system α_1132, which has a completely different application field or purpose of use, it can operate optimally in system α_1132.

[0103] Here, the communication module 1660 may request a new application, or an application change command may be given from an external source (e.g., system controller α_1126). There are many possible timings for application changes, such as when the communication module 1660 is manufactured and shipped from the factory, when it becomes necessary to switch the operating mode during use, when the operating environment of the communication module 1660 changes (e.g., moving between systems α_1132 and β_1134), or when the service period of the communication module 1660 expires. By providing an application change software storage unit (application change software) 1791 inside the memory unit 1790, the communication module 1660 can freely change, add, or update its application in accordance with the above changes in the operating environment and purpose of use.

[0104] On the other hand, the application storage unit 1792 within the memory unit 1790 (Figure 7B) contains common application software that is independent of system changes. Therefore, even if the composite module 1295 or unit 1290, which incorporates the communication module 1660, is moved between different systems, the common application software pre-stored in the application storage unit 1792 remains unchanged and is saved / continued to be used.

[0105] The application software stored in the application modification software storage unit (application modification software) 1791 and the application storage unit 1792 is written in a predetermined programming language or scripting language (including machine language). The application software 3050 may also include an API command 3045 corresponding to a predetermined OS_3030 (or a predetermined API command) as described later using Figure 18B. However, it is not limited to that, and may also be written in Javascript, or in machine language and similar languages, as described later using Figures 19A and 19B. Furthermore, it may also be written in web-related languages ​​such as HTML (Hyper-text Markup Language) or XML (Extensible Markup Language).

[0106] The secure data storage section 1799 can be used to store highly sensitive data, such as personal information. Alternatively, the secure data storage section 1799 may be used to store any data that the user wishes to store.

[0107] For example, one scenario in which the communication module 1660 is used is when it is embedded in an individual patient's medical record holder in a hospital. In such cases, personal information (name, age, diagnosis, medical history, etc.) may be stored in the secure data storage unit 1799. However, the medical record holder is not necessarily used permanently and may be discarded. Moreover, it may be replaced with a new medical record holder. In such cases, the secure data in the communication module of the old medical record holder must be erased.

[0108] There are various methods for determining the timing of the deletion of secure data. For example, if the communication module 1660 has not communicated with the system controller α_1126 for a certain period of time, the system controller α_1126 may determine that the communication module 1660 has been discarded or replaced and execute the data deletion process. The system controller α_1126 may also proactively request the communication module 1660 to delete the secure data. Furthermore, the data deletion process may be executed when the sensor module 1260 connected to the communication module 1660 detects a specific atmosphere and / or a detection element (e.g., pressure, heat, humidity, liquid, etc.). In other words, when the sensor module 1260 detects a specific atmosphere and / or a detection element (e.g., pressure, heat, humidity, liquid, etc.), the processor 1736 automatically determines that the environment has changed from its normal operating environment and executes the data deletion process. However, the data deletion process may also be executed when various predetermined conditions are met.

[0109] On the other hand, if, for example, an old medical record holder is replaced with a new one and it becomes necessary to move the secure data from the old medical record holder to the new one, the system controller α_1126 may perform control such as succession or transfer of the secure data.

[0110] The self-attribute data storage unit 1793 stores attribute data related to the handling of the unit (product, part, material, item, etc.) to which the communication module 1660 is attached, bonded, mounted, or embedded. This specific attribute data may include identification data of the corresponding unit (product name, part name, product name, etc.) as well as identification data such as its place of manufacture and manufacturer.

[0111] For example, a composite module 1295 (or unit 1290) containing a communication module 1660 may be bonded to or embedded in an aluminum beverage can. After use, the aluminum beverage can is discarded and transported to a recycling plant. If attribute data indicating that "the bonded or embedded object is made of aluminum" is stored, the beverage can be automatically classified into the aluminum processing unit within the recycling plant. In this case, the entire recycling plant corresponds to system α_1132, and the classification device within the recycling plant corresponds to system controller α_1126. The classification device corresponding to system controller α_1126 then sends a specific command to the communication module 1660 to read its own attribute data. Based on this self-attribute data, it can then determine what the beverage can is made of.

[0112] On the other hand, the composite module 1295 (or unit 1290) containing the communication module 1660 may be embedded in a plastic beverage bottle. In this case, the classification device sends a specific command to the communication module 1660 to read its own attribute data and detect that the beverage can is made of plastic. This allows the classification device to easily and automatically classify the beverage can to the plastic processing unit. However, the above example is not the only one; the own attribute data may be used for any integrated object (parts, products, goods, devices, materials, etc.) to which the composite module 1295 (or unit 1290) containing the communication module 1660 is attached, embedded, bonded, or mounted.

[0113] Incidentally, if the composite module 1295 (or unit 1290) containing the above communication module 1660 is moved between different systems, the environment in which it is deployed may change. In response to this change in environment, the content of the self-attribute data may progressively change. For example, if the beverage can is displayed in a store, the selling price of the beverage can, its display location in the store, or its product category may be stored in the memory unit 1790 as the self-attribute data. In this case, the system controller α_1126 that manages the store may use the self-attribute data to perform inventory management and settlement processing for customers.

[0114] Another example describes the use of composite module 1295 (or unit 1290) as a tag attached to a fish. Fish caught in the sea are transported by fishing boat to the port, bought by dealers at the port's auction market, transported by car, displayed in supermarkets, and purchased by consumers.

[0115] This section describes a case where a temperature sensor and a humidity sensor for quality control are installed as a sensor module 1260 within the tag (composite module 1295 / unit 1290) integrated with the fish mentioned above. In this case, the self-attribute data stored includes appropriate temperature range data, appropriate humidity range data, and best-before date data. The fishing vessel crew or market manager then inputs this self-attribute data.

[0116] If the ambient temperature or humidity exceeds an appropriate range during transport or storage of fish, the communication module 1660 can output a first warning signal to the system controller α_1126 installed inside the fishing vessel or transport truck. Furthermore, if the expiration date is approaching or has passed, a second and third warning signal can be output via the antenna 1772.

[0117] Furthermore, when products are displayed in stores, self-attribute data such as the selling price, display location within the store, and product category are added. In this case, the above self-attribute data is automatically saved in the memory unit 1790 from another system controller α_1126 installed in the store. This self-attribute data can then be used for inventory management and settlement processing for customers.

[0118] As described above, a key feature of this embodiment of the system is that, in response to the movement of the system to which the composite module 1295 / unit 1290 is located (belongs), the system controller α_1126, which manages / controls / operates system α_1132, can automatically add or update the self-attribute data 1793. This significantly improves the flexibility and versatility of utilizing the corresponding composite module 1295 and unit 1290. In other words, by utilizing the added / updated self-attribute data, the system controller α_1126 can execute the most optimal processing for system α_1132.

[0119] Furthermore, the self-attribute data may also be used as data for the communication module 1660 to respond to a specific command (request signal) and output a response signal indicating the presence of the communication module 1660. For example, the communication module 1660 may be embedded in surgical instruments or inspection tools in aircraft or trains. In this case, the work site is considered a specific system α_1132, and a system controller α_1126 installed at the work site requests a response from the communication module 1660. The presence or absence of a response at the work site (system α_1132) determines whether or not surgical instruments, inspection tools, or other items have been left behind at the work site. In this way, information communication processing regarding self-attribute data makes it possible to determine whether or not items have been left behind after surgery or inspection.

[0120] As an example of using self-attribute data 1793 other than those mentioned above, owner information of the corresponding unit 1290 (or composite module 1295 or device 1250) may be recorded in this area. When the unit 1290 (or composite module 1295 or device 1250) on which this self-attribute data 1793 is recorded is put on sale, it is displayed in a store as described above. At this time, the store where it is displayed corresponds to one system β_1134. When a user purchases the unit 1290 (or composite module 1295 or device 1250), they move it to their home. Then the user's home corresponds to system α_1132 (see Figure 1). Therefore, the system in which the unit 1290 is located changes before and after the purchase of the unit 1290 (or composite module 1295 or device 1250). When the unit 1290 is placed in the user's home, the system controller α_1126, which manages / operates / collects information within the new system α_1132, performs the check-in process described later in Section 4.2. At this time, the system controller α_1126 records user information about the owner in part of the self-attribute data 1793. This user information is not limited to the owner's name; it can also be the user's ID, address, telephone number, email address, etc. Recording user information in part of the self-attribute data 1793 in this way makes it easier to find the corresponding unit 1290 if it is left outside.

[0121] The above-mentioned owner is not limited to the direct owner of unit 1290. That is, it also includes any person, organization, or company involved in the use of unit 1290 (or composite module 1295 or equipment 1250). It may also include any person, organization, or company involved in the use of goods, parts, or materials in which composite module 1295 on which this self-attribute data 1793 is recorded is installed, inserted, or mixed.

[0122] As an example, let's describe a tablet or powdered medicine into which a composite module 1295 containing this self-attribute data 1793 has been inserted or mixed. For example, when the above medicine is taken at a hospital, facility, or at home, the system controller α_1126 records the name of the person who took the medicine and the date and time it was taken in the self-attribute data 1793. The name of the medicine is also pre-recorded in this self-attribute data 1793. Then, even when the user who took the medicine is away from home, the system controller β_1134 installed at the location can manage "who took what medicine and when?" For people with chronic illnesses, regular medication is very important but easy to forget. If the system controller β_1134 constantly manages the medication status as described above, it becomes less likely that medication will be missed.

[0123] As described above, by recording multiple pieces of information that are related to each other as self-attribute data 1793, it becomes easier to manage the usage status of the composite module 1295 (unit 1290) on which the self-attribute data 1793 is recorded with high accuracy.

[0124] Life management data for managing the lifespan of the composite module 1295 (or unit 1290) containing the communication module 1660 can be stored in the life management data storage unit 1794. This life management data indicates the lifespan period during which the composite module 1295 (or unit 1290) containing the communication module 1660 becomes obsolete. When this lifespan period has elapsed, the communication module 1660 automatically ceases operation and stops. This prevents the emission of unnecessary radio waves after the lifespan period.

[0125] For example, in the case of discarded beverage cans or cooked fish as described above, the use of corresponding tags (composite module 1295 / unit 1290) is unnecessary. As described above, the memory unit 1790 has a life management data storage unit 1794, and by automatically shutting down its activity after the life period, unnecessary radio wave generation within system α_1132 can be prevented. And by preventing unnecessary radio wave generation, the efficiency of information communication within system α_1132 is improved.

[0126] Data for setting the operating period of the communication module 1660 can be stored in the operating period management data storage unit 1795. Setting the operating period and sleep period of the communication module 1660 according to the usage environment and conditions improves power saving and prevents interference with surrounding devices. As the above operating period management data, for example, the operating period and sleep period can be set in hours, or the operating period and sleep period can be set according to the sensor output.

[0127] Section 1.7 Description of the Overall Structure of the Wide Area Network System in This Embodiment An overview of the system in this embodiment has already been given in Section 1.1. In contrast, this section will describe in detail the overall structure of the wide area network system in this embodiment using Figure 1. As shown in Figure 1, service provider B_1112-2 obtains goods (or information) from wholesalers B1_1104-1 and / or wholesalers B2_1104-2, which handle similar goods (or information), and provides services.

[0128] Here, wholesalers A_1102 and B1 / 2_1104-1 / 2 refer to the main body or organization that handles the specified goods or information. Specific examples of such organizations are not limited to private for-profit organizations such as foundations or business corporations, but may also include public organizations such as national and local governments, public corporations, and public interest corporations. Therefore, from the perspective of service providers A~C_1112-1~3, the wholesalers may be positioned not only as "trading partners," but also as "contractors for specified services" or "partners for guidance and licensing of specified services." For example, if the aforementioned wholesaler is a trading partner of service providers A-C_1112-1-3, the goods handled by the wholesaler may not be limited to public consumer goods such as electricity, gas, water, and gasoline, but may also include general consumer goods, liquid assets such as money, bonds, and precious metals, and fixed assets such as real estate. Furthermore, the goods may also include valuable information that is difficult to obtain through the regular internet (market research information, information specific to specific individuals or regions (such as weather and traffic information limited to very narrow areas)).

[0129] Next, in this embodiment of the system, service providers A to C_1112-1 to 3 refer to organizations or groups that provide predetermined services. In particular, these service providers A to C_1112-1 to 3 also have the characteristic of performing "integrated management related to predetermined services." Furthermore, the services provided by the service providers may correspond to all kinds of services that utilize information obtained from the sensor module 1260, which will be described later. In particular, a feature of this embodiment is that some of the information obtained via the network from the sensor modules in domains 1 to 3_1122-1 to 3, and related information, is transmitted to the server n_1116-n in this service provider B_1112-2, and based on that, service provider B_1112-2 can provide predetermined services. Thus, in this embodiment of the system, service providers A to C_1112-1 to 3 can retrieve goods and information from within domains 1 to 3_1122-1 to 3. Furthermore, service provider B_1112-2 owns multiple servers 1~n_1116-1~n, and manages database 1118-1~n for each server 1~n_1116-1~n. In addition, coordinated distributed processing is performed among servers 1~n_1116-1~n to speed up processing. Although omitted in Figure 1, similar servers and corresponding databases are also installed within service provider A_1112-1 and service provider C_1112-3.

[0130] One specific task of the service provider is to distribute (both inflow and outflow) goods and information wholesaled from wholesaler A_1102 or wholesaler B1 / 2_1104-1 / 2 within domains 1~3_1122-1~3. A specific example of this service is shown below.

[0131] α) Retail service to end users of goods and information handled by wholesalers A_1102 and B1 / 2_1104-1 / 2 β) A service that independently processes the goods and information handled by wholesalers A_1102 and B1 / 2_1104-1 / 2 and provides the results of that processing to end users γ) A service that is deemed optimal based on information obtained from the sensor module δ) A combination of the above [α] to [γ] Here, the goods handled by the service provider are not limited to the retail of public consumer goods such as electricity, gas, water, and gasoline, but may also include the retail of general consumer goods, current assets and fixed assets, etc. Furthermore, the information (goods) handled may also include information with commercial value that is difficult to obtain through the normal internet (market research information, information specific to specific individuals or regions (such as weather information or traffic information limited to a very narrow area)).

[0132] On the other hand, service provider A_1112-1 obtains different goods (or information) from wholesaler A_1102 than wholesaler B1 / 2_1104-1 / 2 and provides a different type of service. Here, service provider A_1112-1 and service provider B_1112-2, or service provider B_1112-2 and service provider C_1112-3, share information or exchange resources 1114 to improve the efficiency and sophistication of services. Service provider A_1112-1 also has a designated goods storage unit 1154 for storing goods obtained from wholesaler A_1102. Then, in the designated goods generation unit 1152 within service provider A_1112-1 shown in Figure 1, new products are manufactured using goods obtained from wholesaler A_1102 as materials, or new products (or new information) are created by processing goods (or information) obtained from wholesaler A_1102. Although not shown in Figure 1, designated product storage units 1154 and designated product generation units 1152 are also installed within service providers B_1112-2 and C_1112-3.

[0133] The predetermined product generation unit 1152 shown in Figure 1 refers to a place that generates unique products to which unique added value has been added. A specific example of the form of this unique product generation is the processing of raw materials purchased from wholesaler A_1102. For example, in the manufacturing industry, a product manufacturing plant would correspond to the predetermined product generation unit 1152. However, this embodiment is not limited to that, and could also correspond to a power plant that owns solar cells, wind turbines, thermal power plants, geothermal power plants, etc., or related peripheral equipment such as substations and transmission stations. Furthermore, this embodiment's system is not limited to the above, and production sites of other public consumer goods such as gasoline refineries and water storage facilities could also correspond to the predetermined product generation unit 1152 as an example of the form of the predetermined product generation unit 1152. In addition, as another form of product, a place that generates "unique information created within service provider A" could also correspond to the predetermined product generation unit 1152. For example, analytical information newly obtained as a result of analyzing various information published on the internet, such as market trend information or weather forecast information, could also correspond to one form of the above product.

[0134] In the designated product storage unit 1154 shown in Figure 1, temporary storage of any of the following products (including information) is performed.

[0135] α) Goods and information wholesaled from wholesaler A_1102 or wholesaler B1 / 2_1104-1 / 2 β) Goods and information generated by the above-mentioned predetermined product generation unit 1152 γ) Goods and information extracted from domains 1~3_1122-1~3 δ) A combination of the above-mentioned [α] to [γ] For example, if the product to be temporarily stored is electricity, the above-mentioned predetermined product storage unit 1154 consists of a storage battery, a charge / discharge amount monitor unit (corresponding to the smart meter 1124 in system α_1132), and a charge / discharge amount control unit. On the other hand, if the product to be temporarily stored is tap water or city gas, it consists of a water or gas tank, a storage / discharge amount monitor unit, and a storage / discharge amount control unit.

[0136] The recipients of services from the aforementioned service providers A-C_1112-1-3 are the domain 2_1122-2 or its system α_1132 (details below). The system pays the service providers A-C_1112-1-3 directly for the services provided. As shown in Figure 1, the server n_1116-n within service provider B_1112-2 and the designated product storage unit 1154 within service provider A_1112-1 are directly network-connected to the smart meter 1124 and the system controller α_1126 (details below) installed in domain 2_1122-2 and system α_1132. Furthermore, as indicated by the dashed line in Figure 1, the smart meter 1124 is also network-connected to wholesaler A_1102, enabling direct information communication. In Figure 1, the recipients of the smart meter 1124's measurement data are server n_1116-n within service provider B_1112-2, system controller α_1126 within the same system α_1132, or wholesaler A_1102. However, the smart meter 1124's measurement data may also be transmitted to system controller β_1134, which belongs to a different system β_1134, even though it is within the same domain 2_1122-2, or to other devices within the same domain 2_1122-2.

[0137] The smart meter 1124 refers to a device that measures the amount of (similar) goods entering and leaving the inside and outside of Domain 2_1122-2 (or System α_1126) at predetermined time intervals. It mainly refers to measuring the amount of public consumer goods such as electricity meters, gas meters, water meters, and sewage meters entering and leaving the system, and has the characteristic of being able to collect measurements of both the amount flowing in from the outside to the inside (or consumed inside) and the amount flowing out from the inside to the outside (for example, sold to the outside). However, in this embodiment of the system, the smart meter 1124 may also measure the amount of general consumer goods purchased through mail order, liquid assets, or specific information entering and leaving the system, and transmit the results via communication.

[0138] In particular, in this embodiment of the system, a communication module 1202-1 is built into the smart meter 1124 (Figure 8A), and has the function of transmitting the smart meter's measurement values ​​via communication at predetermined intervals. Furthermore, the time interval for communication transmission can be changed as appropriate by the server n_1116-n, system controller α_1126, or wholesaler A_1102. Moreover, the timing of communication transmission of the measurement values ​​obtained from the smart meter 1124 is not limited to the predetermined intervals, but may be transmitted as appropriate in response to requests from the system controller α_1126, server n_1116-n, or wholesaler A_1102. In addition, communication may be transmitted when the smart meter 1124 spontaneously determines that communication transmission to an external party is necessary.

[0139] An example of a service model provided by service provider A1102 using the smart meter 1124 is described below. In this example, predetermined goods and information that have been previously stored in a predetermined goods storage unit 1154 within service provider A1102 are supplied to domain 2_1122-2 (or system α_1132) via system controller α_1126 or smart meter 1124. Conversely, any surplus goods remaining in domain 2_1122-2 (or system α_1132) may be returned to the predetermined goods storage unit 1154 via smart meter 1124. In this case, the difference between the amount of goods supplied from the predetermined goods storage unit 1154 to domain 2_1122-2 (or system α_1132) and the amount of goods returned to the predetermined goods storage unit 1154 via smart meter 1124 is billed by service provider A1102-1 as the amount of goods used.

[0140] In parallel with this, goods (or information) may also be received directly using infrastructure and distribution systems owned or managed by wholesalers A_1102 or B1 / 2_1104-1 / 2. That is, following the dashed line in Figure 1 connecting wholesaler A_1102 to smart meter 1124, goods (or information) handled by wholesaler A_1102 may be directly received via smart meter 1124 within domain 2_1122-2 or within system α_1132. In this case, information regarding the content and quantity of goods (or information) received within domain 2_1122-2 is simultaneously notified from smart meter 1124 to server n_1116-n in service provider B_1112-2, and based on this notification information, service provider B_1112-2 periodically bills the user. Here, the characteristic of this embodiment of the system shown in Figure 1 lies in the fact that there are multiple supply routes from wholesaler A_1102 to smart meter 1124, which serves as a window for supplying predetermined goods within domain 2_1122-2 or system α_1132 (a direct route indicated by a dashed line from wholesaler A_1102 to smart meter 1124, and a route via service provider A_1112-1). This allows service provider A_1112-1 to provide new and unique services. The unique effects resulting from utilizing this characteristic will be explained in detail in Section 5.2.1.

[0141] Next, we will describe domain 2_1122-2 or system α_1132 within it, which can receive services via a wide-area network from the above service providers A~C_1112-1~3. As shown in Figure 1, one domain 2_1122-2 consists of one or more systems α / β_1132 / 1134, and each system α / β_1132 / 1134 has a system controller α / β_1126 / 1128 installed. Furthermore, system controllers α / β_1126 / 1128 or smart meters 1124 are connected via a network either directly or through servers n_1116-n, enabling information communication between them. Within system α_1132, division into multiple sections 1~m_1142-1~m is permitted (sections will be explained in detail in Chapter 4).

[0142] As described above, a key feature of this embodiment of the system is that it allows for the simultaneous coexistence of multiple different systems (client systems). In other words, taking into account the contents described in Figure 2, a composite client system (corresponding to domain 2_1122-2 in Figure 1) includes multiple client systems α_1132 (and β_1134) (multiple client systems α_1126 and β_1134), each comprising a unit 1290 having the function of acquiring or creating information and communicating it, and a system controller α_1126 (and β_1128) that acquires and manages the information from the unit 1290. The system controller α_1126 that manages the client systems α_1132 included in the composite client system (domain 2_1122-2) divides the multiple existing units 1295-1 to -7 into sections to be managed (sections 1_1142-1, 2_1142-1, and m_1142-m in Figure 2), and holds information about the section to which each unit belongs (section information in Figure 23).

[0143] In this context, the domains 1-3_1122-1-3 refer to a network space composed of one or more interconnected systems. In particular, in this embodiment of the system, a domain corresponds to a "network space that is the subject of various state observations" or a "network space that is the subject of predetermined operations or executions or (related to a specific service) operational executions." In order to participate in and operate within a specific domain, it may be necessary to have domain-specific identification information (ID) and a unique password. If one system α / β_1132 / 1134 corresponds to a specific area that is physically or geographically close, then one domain 1-3_1122-1-3 corresponds to a predetermined area on the network managed / used by members of a specific group that transcends the aforementioned physical or geographical space.

[0144] Next, the system α_1132 described above refers to the smallest network system unit in which the internals are connected to each other via a network and one system controller α_1126 is installed inside. This network system is managed or operated by the aforementioned system controller α_1126. In particular, the physical or geographical range of one system α_1132 may be positioned as a specific area that is physically or geographically close to one or more specific users (for example, an area defined within the range of activity of one or more specific users within a predetermined time). Furthermore, one system α_1132 in this embodiment can be specifically associated with a network unit identified by predetermined identification information, such as a PAN (Personal Area Network), LAN (Local Area Network), MAN (Metropolitan Area Network), or WAN (Wide Area Network). For example, IEEE (Institute of Electrical and Electronic Engineers) 802.15.4 specifies the setting of individual identification information, PANID (Personal Area Network Identifier), for each PAN, and one PAN defined by this specific PANID may be associated with one system in this embodiment. Another concrete example would be to associate one system with one home, one car interior, one mobile terminal surrounding space, or one work environment (Work Station Area).

[0145] The system controllers α / β_1126 / 1128 mentioned above refer to devices that are deployed in one or more units within a system and perform communication control, management, and operation of communication status within the network system corresponding to the systems α / β_1132 / 1134. As also mentioned above, the system controllers α / β_1126 / 1128 are connected to a wide-area network outside of the systems α / β_1132 / 1134 (the network used for information communication with service providers A~C_1112-1~3). Furthermore, the system controllers α / β_1126 / 1128 incorporate a processor for collecting signals and information obtained from one or more sensor modules (sensor module 1260, which will be described later using Figures 8A and 9) within the same system α / β_1132 / 1134 and performing appropriate processing. Specific examples of a system controller include a single PC (Personal Computer), a mobile device such as a smartphone, tablet, or cell phone, a distribution board or refrigerator with a built-in processor, or a television, a recorder capable of recording, or a recording device that only records audio. Alternatively, a processor may be built into the smart meter 1124, giving the smart meter 1124 the functionality of the system controller α_1126, or a processor and communication module (communication module 1202, described later using Figures 8A and 9) may be built into a remote control for an air conditioner, television, or lighting fixture and used as a system controller. However, in this embodiment, any processor-equipped device with a program set to collect signals and information obtained from sensor modules in the system and provide appropriate services to the user may be used as a system controller. Furthermore, a single system controller may be configured by combining / cooperating multiple physical devices.

[0146] In particular, a remote control with a built-in processor and communication module, used as a system controller, can be temporarily placed on a wall or shelf in a fixed or movable manner, either by screwing it in or otherwise. This allows for unique uses (and the resulting effects). However, in this case, it is necessary to fix or place it in a location where infrared communication with the main unit equipment, such as air conditioners, televisions, and lighting fixtures, is possible. Furthermore, sensors / communication modules (described later using Figure 8B) related to temperature sensors, wind speed sensors, or short-range motion sensors can be installed throughout the room, enabling internal communication between the remote control (system controller α_1126) and the system α_1132. This allows for efficient service to users, such as prioritizing and accurately controlling the temperature only in areas where multiple users are present in the room, or controlling the display method of a glasses-free television so that it can be viewed in 3D simultaneously in the locations of multiple users. As a result, simply replacing existing remote controls with the system controller-equipped remote controls allows for more efficient operation than before, without replacing the main unit equipment (such as air conditioners, televisions, and lighting fixtures) that has already been installed.

[0147] In conventional technologies known as M2M (Machine to Machine) or IoT (Internet of Things), a cloud server (corresponding to server n_1116-n in Figure 1) collected all signals and information obtained from in-home sensor modules in each household, and services were often provided directly to end users from the cloud server. In this case, the system controller α_1126 only functioned as a gateway or router, as shown in Figure 9, relaying the transmission of signals and information on the network. Such conventional technologies had the following problems: (1) Users' personal information was easily transmitted to the relatively public server n_1116-n, which was problematic from the perspective of protecting users' personal information; and (2) If there was a problem with the communication line between the system controller α_1126 or smart meter 1124 and server n_1116-n, the service to end users would be interrupted, creating a vulnerability in the entire system. In this embodiment, the system controller α_1126 is not limited to the function of transmitting and relaying signals and information on the network as a gateway or router, but is characterized by the fact that it performs specific processing, including judgment, integration, processing, or unique services to the user based on signals and information collected from sensor modules by its built-in processor. Therefore, in this embodiment (1) (2) The system controller α_1126 independently determines whether or not to transmit individual signals or information to server n_1116-n, thus protecting the user's personal information. Based on the signals and information collected from the sensor module, the system controller α_1126 can make decisions to provide unique services to the user. Moreover, since this service can be executed regardless of whether or not there are communication line problems with server n_1116-n, the overall robustness of the system is improved. These effects occur. In particular, the system controller α_1126 in this embodiment is characterized by its ability to integrate information obtained from the sensor module 1260 to determine / estimate user behavior (such as the presence or absence of a user, and behavior such as sleep / wake) and situation (for example, whether the user is a child or an adult), and even to estimate user requests. As a result, even without the server n_1116-n, it becomes possible to provide comfortable services to the user within domain 2_1122-2 independently.

[0148] Furthermore, a key feature of this embodiment of the system is the ability for multiple system controllers α / β_1126 / 8 to work together within the same domain 2_1122-2. Therefore, a single system controller α_1126 can collect signals and information from all sensor modules located within the same domain 2_1122-2 (including sensor modules located within system β_1134, although not shown in the diagram). As a result, system controller α_1126 can integrate and utilize information within the same domain 2_1122-2 to provide the user with the most optimal service within system α_1132.

[0149] In this embodiment of the system, as a coordinated work mode between multiple system controllers α / β_1126 / 8 within the same domain 2_1122-2, there are two types of network paths, as shown in Figure 1: one where system controllers α / β_1126 / 8 directly exchange information using, for example, wireless communication, and another where system controllers α / β_1126 / 8 indirectly exchange information via, for example, the Internet, through server n_1116-n. This results in the ability for users to receive a variety of services. For example, if system controller α_1126, which is a home PC, and system controller β_1128, which corresponds to a mobile terminal such as a smartphone or tablet, are physically close to each other, they can exchange information at high speed via WLAN (Wireless Local Area Network) or WPAN (Wireless Personal Local Area Network). On the other hand, by using an internet connection, including a wired connection, information exchange between the two is guaranteed regardless of how far apart they are physically. On the other hand, by directly exchanging information, the two parties can obtain private services independently without involving server n_1116-n, thus preventing the risk of personal confidential information leaking to server n_1116-n, which has a relatively public nature. Meanwhile, server n_1116-n can use a different network path to obtain information that cannot be obtained within domain 2_1122-2, such as local weather forecasts and traffic congestion information. Therefore, by indirectly exchanging information between system controllers α / β_1126 / 8 via server n_1116-n, a variety of services can be provided to users that utilize information owned by server n_1116-n itself. By switching network communication paths as appropriate in this way, it is possible to provide a wider variety of services that users desire. As mentioned above, system controller α_1126 itself can estimate the user's behavior and state or estimate the user's desires / requests, so system controller α_1126 can switch the connection path between system controllers α / β_1126 / 8 based on its own judgment.

[0150] Section 1.8 Description of the Local Network System Structure in This Embodiment Section 1.1 already outlined an example of the structure within a local network system configured within system α_1132, which is included in domain 2_1122-2 as shown in Figure 1, using Figure 2. In this Section 1.8, we will describe application examples of other embodiment systems other than those shown in Figure 2, using Figures 8A to 9.

[0151] In the embodiment shown in Figure 8A, each device (Device) 1250-1 to 3 has a built-in communication module 1202-4 to 6, enabling information communication within the same system α_1132. Furthermore, each device (Device) 1250-1 to 3 has a built-in sensor module 1260-1 to 5 or an actuator module 1270-1. In contrast, in Figure 8B, the relationship between communication modules 1202-4 to 6 and sensor modules 1260-1 to 5 is understood or managed using the concept of sensor / communication module 1460-1 to 5. Similarly, the relationship between communication module 1202 and actuator module 1270 is understood or managed using the concept of actuator / communication module 1470-1 to 2. Moreover, as explained in Section 1.3, concepts such as processor / communication module 1465, memory / communication module 1475, and display / communication module 1478 are also comprehensively managed using the concept of a composite module 1295. Incidentally, a single composite module may exist as a standalone unit, as shown in the sensor / communication module 1460-5 in Figure 8B.

[0152] In this embodiment of the system, a smart meter 1124 is installed that automatically measures the amount (or cumulative amount) of public consumption goods such as electricity, gas, and water / sewage used in total within one system (for example, within system α_1132) at predetermined intervals, and automatically transmits the measurement data periodically. In reality, a different smart meter 1124 is installed for each public consumption good such as electricity, gas, and water / sewage, but in Figure 8A / B, only one smart meter 1124 is shown as a representative example. Furthermore, the system may also automatically measure and transmit the amount (or cumulative amount) of the above public consumption goods for each of the sections 1_1142-1 and 2_1142-2 described later.

[0153] As shown in Figures 8A and 9, the detailed structure of the smart meter 1124 is that, in addition to the inflow monitoring unit 1208 (e.g., the electricity purchase meter), there is also an outflow monitoring unit 1206 (e.g., the electricity sales meter). This outflow monitoring unit 1206 is used to measure the amount of surplus public consumption materials released (sold) to wholesaler A_1102 within system α_1132. The individual metered values ​​(or cumulative values) obtained within the smart meter 1124 are periodically reported to server n_1116-n via communication module 1202-1. In parallel, they are also reported to wholesaler A_1102.

[0154] The communication module 1202 shown in Figure 8A or Figure 9 refers to a communication function unit capable of transmitting information using wired or wireless methods. The wired communication supported by this communication function unit may include any communication method, from local video signal transmission lines and audio signal transmission lines to telephone lines and Ethernet (registered trademark) communication related to the Internet. The wireless communication supported by the above communication function unit may include any wireless communication method, such as short-range wireless methods like ZigBee (registered trademark), Bluetooth (registered trademark), UWB (Ultra Wide Band), and Z-Wave; medium-range wireless methods like Wi-Fi (Wireless Fidelity) and EnOcean; and long-range wireless methods like 2G / PDC, GSM (registered trademark) (Second Generation / Personal Digital Cellular, Global System for Mobile Communications), 3G / CDMA (Third Generation / Code Division Multiple Access), and WiMAX (World wide Interoperability for Microwave Access).

[0155] In particular, this embodiment of the system has the functionality to execute the minimum necessary process processing within the communication modules 1202 and 1660, as will be described later using Figure 10A. As a result, the processing and execution of communication protocols (communication information) having the structure shown in Figures 11 to 15B, as will be described later in Chapter 2, are processed within the communication modules 1202 and 1660. This process processing may, for example, be based on a general-purpose basic (standard) application such as a Java script that does not require a specific OS. However, it is not limited to that, and may also be based on process processing compatible with ECMA Script, or on HTML (Hyper-text Markup Language) or HTML5 decoding functions and the execution of corresponding Java applets. Furthermore, it may be based not only on the existing general-purpose scripts mentioned above, but also on a proprietary process method.

[0156] In Figures 8A and 9, the communication module 1202 is built into the system controller α_1126, the smart meter 1124, and the various devices 1250, enabling them to communicate with each other. On the other hand, as shown in Figures 8A and 9, the various devices 1250 have either a sensor module 1260 or an actuator module 1270 built into them.

[0157] In the embodiment of the system shown in Figure 8A, multiple devices 1250-1 to 3 installed within the same system α_1132 communicate information with the system controller α_1126 via their respective built-in communication modules 1202-4 to 6 and communication module 1202-3. Here, as shown in Figure 8A, it is permissible to have devices 1250-2 to 3 that contain only one or more sensor modules 1260-3 to 5, devices 1250-1 that contain both one or more sensor modules 1260-1 to 2 and a drive module 1270-1, and devices 1250 that contain only a drive module 1270 (not shown). On the other hand, in the embodiment shown in Figure 8A, it is possible to arrange a mix of devices 1250-1, which has a built-in device controller 1240-1 and a memory unit 1242 that can sequentially store and manage historical information related to sensor modules 1260-1 to 1260-2 and drive module 1270-1, and devices 1250-2 to 3, which do not have these components.

[0158] By having a function equivalent to a predetermined product generation unit 1152 or a predetermined product storage unit 1154 within system α_1132, similar to the service provider A_1112-1 described in Section 1.7 using Figure 1, it becomes possible to secure and temporarily store surplus public consumer goods. Figures 8A / B show an example of the use of a (car) battery 1220 as an example of a function equivalent to a predetermined product storage unit 1154. However, this embodiment is not limited to this, and any device having the function of a predetermined product generation unit 1152 or a predetermined product storage unit 1154 may be installed within system α_1132. For example, a battery center or water tank (or other storage equipment) may be installed on a building-by-building or regional basis to temporarily store surplus public consumer goods generated within the building or region.

[0159] Figures 8A / B illustrate a specific example of the use of the (car) battery 1220 for convenience. Here, the interior space of one vehicle corresponds to one section 1_1142-1, which will be described later. Therefore, all information detected inside the vehicle (for example, gasoline consumption, engine speed, interior temperature, and individual body information of occupants) is detected by the sensor module 1222, and the results are transmitted to the system controller α_1126 via the communication module 1202-2. Similarly, within this section 1_1142-1 (interior), an inflow rate monitor unit 1218 for measuring the amount of charge to the (car) battery 1220 and an outflow rate monitor unit 1216 for measuring the amount of electricity released (sold) from the (car) battery 1220 to the outside are installed, and each measured value is transmitted to the system controller α_1126 via the communication module 1202-2. In particular, this embodiment of the system includes a discharge control unit 1212 that can accurately control the amount of electricity discharged (sold) to the outside from the (car) battery 1220, and an inflow control unit 1214 that can accurately control the amount of electricity charged to the (car) battery 1220. Both are connected to the system controller α_1126 via communication modules 1202-2 and 1202-3. Therefore, the system controller α_1126 can accurately control the amount of electricity discharged (sold) to the outside by feeding back the amount of electricity discharged (sold) measured sequentially by the discharge monitor unit 1216 to the discharge control unit 1212. Similarly, the system controller feeds back the amount of electricity inflow (purchased) measured sequentially by the inflow monitor unit 1218 to the inflow control unit 1214 to accurately control the amount of electricity charged to the (car) battery 1220.

[0160] Section 1.7 already explained that the system controller α_1126 performs communication control, communication status management, and operation within the corresponding system α_1132 (network system). As shown in Figure 8A, this system controller α_1126 incorporates a processor 1230. This processor 1230 collects information from all sensor modules 1222, 1260-1~5 within the same domain 2_1122-2 and stores it sequentially as history information in the memory unit 1232. Similarly, command information for the drive module 1270-1 is also stored as history information. Furthermore, this system controller α_1126 has a user interface unit 1234, which allows for direct input of requests from the user and display of the current progress status to the user. However, it is not limited to this, and the user interface unit 1234 may be installed outside the system controller α_1126 and connected via the communication module 1202-3.

[0161] In particular, a key feature of this embodiment of the system is that, instead of automatically transferring all information regarding sensor modules 1222, 1260-1~5 and drive module 1270-1 within domain 2_1122-2 to server n_1116-n, the system controller α_1126 (specifically its processor 1230) autonomously selects and sends only the necessary information to server n_1116-n. This effectively protects the user's personal information. Furthermore, in addition to the above-mentioned selection of information, some processing and analysis may be performed on the above information, and only the results may be notified to server n_1116-n. This allows server n_1116-n to collect only the minimum necessary information, thus improving the efficiency of integrated management processing performed within service provider B_1116-1.

[0162] Furthermore, in this embodiment of the system, the system controller α_1126 (specifically the processor 1230) can collect proprietary information from the server n_1116-n via the communication module 1202-3 and store it in the memory unit 1232. This proprietary information refers to information that cannot be obtained from within domain 2_1122-2, such as traffic congestion information, local weather forecast information, and time-varying price information for public consumer goods. The system controller α_1126 (specifically the processor 1230) analyzes the information accumulated in the memory unit 1232 to estimate and judge the end user's behavior, state, or requests. Based on this estimation and judgment, the system controller α_1126 (specifically the processor 1230) controls the system α_1132 (or domain 2_1122-1) to provide the end user with the optimal service. As an example of this service provision method, the drive module 1270-1 in Figure 8A may be remotely controlled. In this way, the system controller α_1126 (specifically its processor 1230) independently analyzes and interprets information collected from sensor modules 1222, 1260-1~5 and server n_1116-n, along with the command history to drive module 1270-1. This enables the provision of unique services, such as detailed user support within domain 2_1122-2, which was previously difficult. Furthermore, these unique services within domain 2_1122-2 can be provided stably even in the event of communication failure with server n_1116-n due to system trouble, thus ensuring the robustness of services provided to end users.

[0163] An example of the application of the embodiment system shown in Figure 8A is shown in Figure 9. In Figure 9, all devices 1250-1 and 4 within domain 2_1122-2, excluding the smart meter 1124 and the router (gateway) 1300, have a processor 1330 or device controllers 1240-1 to 1240-2 built in, and direct information exchange with the server n_1116-n is possible via the router (gateway) 1300, which has a built-in battery.

[0164] Here, the processor 1330 built into section 1_1142-1 (inside a single vehicle) controls not only the amount of power charged / discharged from the (car) battery 1220, but also all kinds of controls such as air conditioning management inside the vehicle and combustion control for fuel-efficient engines, and this related information can be transmitted to the server n_1116-n via the router (gateway) 1300 (or directly). In addition, all communication modules 1202-1 to 1202-7 are network-connected to the server n_1116-n via the router (gateway) 1300. In the application example shown in Figure 9, the router (gateway) 1300 does not perform any discrimination or selection and automatically transfers all information from devices 1250-1 / 4 to the server n_1116-n, which is a major functional difference from the system controller α_1126 in Figure 8A.

[0165] On the other hand, in the application example shown in Figure 9, memory units 1244 and 1246 are built into all devices 1250-1 / 4 within domain 2_1122-2. Signals and information detected moment by sensor modules 1260-1 to 7 are sequentially stored in memory units 1244 and 1246 in a time-series manner. Instruction information issued from device controllers 1240-1 to 2 to drive modules 1270-1 to 3 is also sequentially stored in memory units 1244 and 1246. Using the information stored in these memory units 1244 and 1246, device controllers 1240-1 to 2 can provide unique services to end users on a device-by-device basis (1250-1 to 4). When providing this service, the device controllers 1240-1 / 2 use the history of detection signals and measurement information from the sensor modules 1260-1 to 1260-7, which are stored in memory units 1244 and 1246 and change moment by moment, to estimate / determine the end user's actions, state, or requests, and to control the drive modules 1270-1 to 1270-3 (details will be described later in sections 4.2 to 4.4).

[0166] The key feature of the application example shown in Figure 9 is that "the entire network communication system α_1132 (and the physical space area it forms) is managed or controlled from outside the network communication system α_1132" or "there is no system controller α_1126 located within the network communication system α_1132 (and the physical space area it forms) that manages or controls the entire network communication system α_1132." From this perspective, the management and operation of information communication within the same intra-system network line 1782 formed between devices 1250-1 and 4 within system α_1132 via a battery-powered router (gateway) 1300 may be performed by a system controller β_1128 located physically separate from system α_1132, instead of servers n_1116-n.

[0167] As a further application example, a "hybrid form" between the embodiment system shown in Figure 2 or Figure 8A / B and the embodiment system in Figure 9 may be adopted. In this case, the system α_1132 may have both a system controller α_1126 and a battery-powered router (gateway) 1300 as relay means inside and outside the system α_1132. Furthermore, the management, operation, or control of the entire network communication system α_1132 may be performed in cooperation between the system controller α_1126 and the system controller β_1128, or it may normally be performed by the system controller α_1126 alone. The system controllers α_1126 and β_1128 frequently exchange information, and all information necessary for information collection for each section 1_1142-1 to m_1142-m and for providing services to users is shared between the two. In this case, the relevant files stored in the memory section 1232 of the system controller α_1126 are mirrored and appropriately copied to the corresponding memory section 1248 of the system controller β_1128. The address table in Figure 23, the estimation / judgment matching table in Figure 27, and the time-series information tracking table in Figure 28, which are examples of information necessary for collecting information for each section 1_1142-1 to m_1142-m and providing services to users, will be explained later. By sharing information between system controllers α_1126 and β_1128 as appropriate, processing within the stable system α_1132 can continue without interference, even if the main body of management / operation or control changes (or is mixed) along the way. Furthermore, system controller α_1126 and server n_1116-n may cooperate to manage, operate, or control the entire network communication system α_1132. In this case, as described above (using mirroring, etc.), all information necessary for collecting information for each section 1_1142-1 to m_1142-m and providing services to users may be shared between system controller α_1126 and server n_1116-n. By managing, operating, and controlling the entire network communication system α_1132 using multiple devices located in different positions, it becomes possible to respond flexibly to emergencies, thus improving the stability and reliability of the network communication system α_1132.For example, if the system controller α_1126 shuts down due to some unforeseen event, or if all the information stored in the memory unit 1232 is destroyed due to a head crash, the system will automatically switch to the system controller β_1128 or server n_1116-n as an emergency measure, allowing the system α_1132 to continue processing stably without causing any stress to the user. Furthermore, the user can remotely operate the system controller β_1128 to collect information from the network communication system α_1132 or control the network communication system α_1132, thus improving user convenience. In this case, the system α_1132 may contain a mix of devices 1250-1 and 4 that have a built-in device controller 1240 and memory unit 1242, devices 1250-2 and 3 that do not have a device controller 1240 or memory unit 1242, or composite modules such as the sensor / communication module 1460 or the drive / communication module 1470, as described later.

[0168] Let me provide some supplementary explanation regarding the "mixed configuration" mentioned above. As shown in Figure 5, the composite module 1295 (or unit 1290) located within the network system α_1132 often possesses a power storage module (battery) 1554. Therefore, even if a power outage occurs within system α_1132, most of the composite modules 1295 (or unit 1290) will continue to operate unaffected. Furthermore, in the embodiment system shown in Figure 9, the router (gateway) 1300 that relays information communication inside and outside system α_1132 has a built-in battery and is therefore unaffected by power outages within the network system α_1132. Consequently, by setting up a means to back up management / control within the network system α_1132 in the event of unforeseen circumstances such as power outages or failures, information communication within system α_1132 will continue without interruption, unaffected by such unforeseen circumstances.

[0169] As explained in Section 1.1, "the sole system controller α_1126 manages, controls, operates, and collects information communications within the network system α_1132." Under normal circumstances, the system controller α_1126 handles the management, control, operation, and collection of information communications within the network system α_1132. However, in the event of unforeseen circumstances such as a power outage or malfunction, the system controller β_1128 temporarily takes over the management, control, operation, and collection of information communications within the network system α_1132. Incidentally, under normal circumstances, the system controller β_1128 may be treated as a single unit 1290 belonging to the network system α_1132.

[0170] As already explained in Section 1.1 using Figures 1 and 2, the system controller α_1126, which manages, controls, operates, and collects information communication within the network system α_1132, communicates information within the network system with each unit 1290 within the network system α_1132, and also communicates information outside the system with servers n_1116-n (cloud or cloud servers) that exist outside the network system α_1132. When system controller β_1128 takes over the role of system controller α_1126 in the event of an unforeseen incident such as a power outage or failure, it is desirable that information communication between each unit 1290 and server n_1116-n be conducted using the same communication information format as before the temporary takeover. This is because using the same communication information format allows for smooth and seamless temporary takeover processing.

[0171] As will be described later in Section 2.1 using Figure 10A, the communication information in the communication middleware layer APL02 between system controller α_1126 and composite module 1295 can use the C-format. On the other hand, the communication information in the communication middleware layer APL06 between system controller α_1126 and server n_1116-n (cloud or cloud server) may use the A-format, E-format, W-format, etc. Therefore, when system controller β_1128 performs processing on behalf of system controller α_1126, it is desirable to perform similar information communication. That is, the communication information in the communication middleware layer APL02 between system controller β_1128 and composite module 1295 uses the C-format, and the communication information with server n_1116-n (cloud or cloud server) uses the A-format, E-format, W-format, etc.

[0172] Thus, using Figures 10A and 17A, the characteristics of the client system resulting from combining the contents described later in Section 2.1 with the embodiment system described above are summarized below. That is, this client system (system α_1132) can connect to an external cloud (server n_1116-1 in Figure 1) (via the system controller α_1126 in Figure 10A or the router (gateway) 1300 or system controller β_1128 in Figure 17A), and furthermore, this client system (system α_1132) includes a first system controller α_1126 that acquires and manages the information from a unit 1290 (or composite module 1295) which has the function of communicating information that it has independently acquired or created, and a second system controller β_1128 which is different from the first system controller α_1126 that acquires and manages the information from the unit 1290 (or composite module 1295), The first system controller α_1126 divides and manages multiple units 1290 (or composite modules 1295) into sections 1142 (Figure 1), and maintains information about the section to which each unit belongs (the address table in Figure 23 or the time-series information tracking table in Figure 28, which will be described later in Section 4.3). The communication between the second system controller β_1128 and the multiple units 1290 (or composite modules 1295) uses a first data format (C-format in Figure 17A), and the communication between the second system controller β_1128 and the cloud (server n_1116-1 in Figure 1) uses a second data format (A / E / W-format in Figure 17B).

[0173] As previously explained, under normal circumstances, system controller β_1134 may be treated as a single unit 1290 belonging to network system α_1132, which is managed / controlled / operated / information collected by system controller α_1126. Furthermore, in this embodiment of the system, information communication between different units 1290 within the same network system α_1132 is possible via (through) network system α_1132. As mentioned above, when information is communicated between system controller α_1126 and unit 1290, the communication information in communication middleware layer APL02 can use the C-format. Therefore, when information is communicated between system controller α_1126 and system controller β_1128, using the C-format for the communication information in communication middleware layer APL02 also has the effect of making it easier for system controller α_1126 to manage / control / operate / collect information.

[0174] On the other hand, even when the system controller β_1134 communicates information with the server n_1116-n (cloud or cloud server) under normal circumstances, it is desirable to use A-format, E-format, or W-format for communication information in the communication middleware layer APL06. This has the effect of enabling smooth and seamless temporary backup processing for the management / control / operation / information collection of the network system α_1132 in the event that the system controller α_1126 becomes unusable due to a power outage or failure.

[0175] This can be rephrased as follows: This client system (system α_1132) can connect to an external cloud (server n_1116-1 in Figure 1) (via system controller α_1126 in Figure 10A or router (gateway) 1300 or system controller β_1128 in Figure 17A), and a first system controller α_1126 acquires and manages the information from a unit 1290 (or composite module 1295) which has the function of communicating information that it has independently acquired or created. The system includes a second system controller β_1128, which is different from the first system controller α_1126 that acquires and manages the system. The second system controller β_1128 communicates with the plurality of units 1290 via the first system controller α_1126 using a first data format (such as C-format), and uses a second data format (A / E / W-format in Figure 17B) for communication between the second system controller β_1128 and the cloud (servers n_1116-n in Figure 1).

[0176] Incidentally, the paraphrasing up to this point has mostly focused on the coordinated processing and alternative processing of system controllers α_1126 and β_1128. However, it is not limited to that; the characteristics of the standalone system embodiment shown in Figure 9, in which system controller α_1126 does not exist from the beginning, can also be described as follows. In other words, this client system (system α_1132) can connect to an external cloud (server n_1116-1 in Figure 1) (via system controller α_1126 in Figure 10A or router (gateway) 1300 or system controller β_1128 in Figure 17A), and further comprises a unit 1290 (or composite module 1295) that has the function of communicating information that it has independently acquired or created, a system controller β_1128 that acquires and manages the said information from the unit 1290 (device 1250 in Figure 9), and a gateway 1300 that has the function of communicating between the unit 1290 (device 1250 in Figure 9) and the system controller β_1128, and the system controller β_1128 has the function of communicating between multiple units This electronic device system manages 1290 (device 1250 in Figure 9) by dividing it into sections 1_1142-1 and 2_1142-2, and maintains information (address table in Figure 23 or time-series information tracking table in Figure 28, described later in Section 4.3) related to the sections 1_1142-1 and 2_1142-2 to which each unit 1290 (device 1250 in Figure 9) belongs. The system is characterized by using a first data format (such as C-format) for communication between the system controller β_1128 and the multiple units 1290 (device 1250 in Figure 9), and using a second data format (A / E / W-format in Figure 17B) for communication between the system controller β_1128 and the cloud (server n_1116-n in Figure 1).

[0177] Section 1.9 Examples of the Use of Composite Modules within a Local Network System In the embodiment shown in Figure 8A or Figure 9, the basic communication partners of the system controller α_1126 in Figure 8A or the server n_1116-n in Figure 9 are devices 1250-1 to 4. Traditionally, the basic functions of each device were predetermined, so the content of network communication information (communication protocol or exchange information 1810 in the communication middleware layer APL, explained in Chapter 2) that was compatible with the basic functions of each device was predetermined in the standard specifications. However, as devices evolve and diversify with the passage of time, it becomes difficult to quickly adapt the standard specifications to the ever-changing equipment functions of each device. For example, the basic function of a television is to "receive broadcast waves and display the content to the user." However, current high-end Japanese televisions have built-in functions such as data communication using network lines or recording functions, in addition to the above basic function. Also, although not yet widespread, glasses-free 3D TVs (3-Dimensional Television) have a built-in function to detect the location information of the viewer. Furthermore, in the future, televisions may incorporate light sensors (to optimally control the brightness of the display screen). If the communication information format (exchange information 1810) or communication protocol between the devices 1250-1 to 4 is made general-purpose to accommodate this diversification and expandability of each device, it will lead to the drawback of increasing the price of devices 1250-1 to 4, which incorporate high-performance device controllers 1240-1 to 2 for decoding the communication information. In other words, it is difficult for devices 1250-2 or 1250-3 in Figure 8A to decode complex, general-purpose communication information, and it becomes necessary to incorporate a device controller 1240 for decoding and performing various controls within the device according to the decoding results.

[0178] As a countermeasure, Figure 8B allows for the installation of sensor / communication modules 1460-1 to 5 or drive / communication modules 1470-1 to 2 belonging to the composite module 1295, either inside or outside the equipment 1450-1 to 4.

[0179] For the sake of explanation, all the devices 1450-1 to 1450-4 in Figure 8B are shown to have a structure that incorporates sensor / communication modules 1460-1 to 1460-4 and drive / communication modules 1470-1 to 1470-2, which belong to the composite module 1295. However, the embodiment shown in Figure 3A(c) may also be used. That is, for example, the above-mentioned composite module 1295 (sensor / communication module 1460 or drive / communication module 1470) may be additionally incorporated into the devices 1250-1 to 14 shown in Figures 8A and 9. In this case, information communication regarding the basic functions of each device (for example, the function of "receiving broadcast waves and displaying their content to the user" in the previous example) is handled within the devices 1250-1 to 14 shown in Figures 8A and 9. Information communication regarding newly developed, diversified, and added functions is directly handled by the newly added composite modules 1295, 1460, and 1470. Furthermore, the entire set of functions possessed by the highly diversified and evolved device 1250 is comprehensively managed, understood, and controlled within the system controller α_1126. This creates a new effect that facilitates expandability (expandability of embedded sensors / drive types) when adding new functions to existing devices. Moreover, since the functions of each of the above-mentioned composite modules 1295, 1460, and 1470 are greatly limited and simplified, a further effect is created in which the communication information exchanged between these composite modules 1295, 1460, and 1470 and the outside world can be greatly simplified. With the communication information exchanged with the outside world greatly simplified in this way, the need to incorporate high-performance device controllers 1240-1~2 to decode / control complex communication information is eliminated, making it easier to reduce the cost and miniaturize the above-mentioned composite modules 1295, 1460, and 1470.

[0180] In the example shown in Figure 8B, equipment 1450-1 and 1450-2 are located in section 2_1142-2, and equipment 1450-3 to 1450-4 are located in section m_1142-m. However, the installation locations of each piece of equipment 1450-1 to 1450-4 do not necessarily have to be fixed; an end user may transport any of the specific pieces of equipment 1450-1 to 1450-4 and move them to a different section.

[0181] Similarly, in the embodiment system shown in Figure 8B, sensor modules and drive modules are individually integrated with communication modules within the smart meter 1124 and within section 1_1142-1 (corresponding to, for example, the entire interior of a single vehicle). As a result, as shown within the smart meter 1124 in Figure 8B, discharge volume monitor / communication module 1406 and inflow volume monitor / communication module 1408 are configured and individually network-connected to the system controller α_1126 and server n_1116-n. Similarly, section 1_1142-1 consists of discharge volume monitor / communication module 1416, inflow volume monitor / communication module 1418, discharge volume control / communication module 1412, and inflow volume control / communication module 1414, each individually network-connected to the system controller α_1126 (specifically, its processor 1230) via communication module 1202-3. Here, the discharge rate monitor / communication module 1406, the inflow rate monitor / communication module 1408, the discharge rate monitor / communication module 1416, and the inflow rate monitor / communication module 1418 correspond to the sensor / communication module 1460. Also, the discharge rate control / communication module 1412 and the inflow rate control / communication module 1414 correspond to the drive / communication module 1470. In this case, the system controller α_1126 collects all detection signals and measurement information obtained from the sensor / communication modules 1460-1~5 or the discharge rate monitor / communication modules 1406, 1416 and the inflow rate monitor / communication modules 1408, 1418 within system α_1132 (and stores it in the memory unit 1232). Furthermore, the system controller α_1126 controls (issues commands to) all the drive / communication modules 1470-1~2 and the discharge rate control / communication module 1412 and the inflow rate control / communication module 1414 within system α_1132. As a result, a single system controller α_1126 enables efficient and integrated management and control of all devices 1450-1~5 within system α_1132, as well as the provision of high-quality services to end users.

[0182] Furthermore, the embodiment system example shown in Figure 8B has the effect of being able to manufacture devices 1450-1 to 1470 at a very low cost. That is, by mass-producing a large quantity of general-purpose standard composite modules 1460 and 1470, these composite modules 1460 and 1470 can be manufactured at a significantly lower cost. Moreover, there is no need for any new interface section to connect these composite modules 1295, 1460, and 1470, and they can be incorporated into the corresponding devices 1450-1 to 1450-5 very easily and inexpensively at the level of simple physical arrangement. Furthermore, if the drive / communication modules 1470-1 to 2 become available at a low cost, the number of drive / communication modules 1470-1 to 2 incorporated into devices 1450-1 to 5 can be increased compared to the example in Figure 8B. In addition, the method of incorporating the composite modules 1295, 1460, and 1470 into devices 1450-1 to 5 is not limited to screw fastening; for example, temporary fastening using double-sided tape or adhesive tape by the end user is also acceptable. In other words, in the example shown in Figure 8B, one sensor / communication module 1460-4 to 1460-5 is built into each of devices 1450-1 and 1450-3, while multiple sensor / communication modules 1460-2 to 1460-3 are built into device 1450-2. However, using the method described above, it becomes easy for an end user to reattach a specific sensor / communication module 1460-2 to 1460-5 to another device 1450.

[0183] In the embodiment of the system shown in Figure 8B, the sensor / communication module 1460-5 is not built into the device 1450, but is instead installed independently at any location within the specific section 1142 (or domain 1122). As a method for installing such a sensor / communication module 1460-5 (or composite modules 1295, 1460, 1470) independently, for example, the user may fix the sensor / communication module 1460 (or composite modules 1295, 1460, 1470) to a wall, roof, or floor using fixing materials such as tape, adhesive, or thumbtacks, or it may be mixed with paint and painted onto the wall, roof, or floor. Furthermore, although not shown, the drive / communication module 1470 may also be installed independently at any location within the specific section 1142 (or domain 1122) (for example, in the form of a remote control for controlling an air conditioner, television, or lighting equipment).

[0184] Furthermore, in another embodiment of this system, the composite modules 1295, 1460, and 1470 may be made movable with the user, and the user's behavior history information may be collected by measuring the position change history of the composite modules 1295, 1460, and 1470. In addition (though not shown in the figures), the drive / communication module 1470 may be made movable with the user, and control of state changes within section 1142 (for example, changes in air conditioning or brightness) may be performed from any location within section 1142 (or domain 1122) where the user is located. As a method for making the composite modules 1295, 1460, and 1470 movable with the user, for example, they may be temporarily fixed or attached with tape or adhesive to personal belongings that the user wears regularly, such as glasses, tie clips, shoes, or wallets. Alternatively, they may be firmly fixed with screws, or they may be incorporated inside the personal belongings.

[0185] Chapter 2 Overview of Hierarchical and Data Structures of Communication Information In Chapter 1, the overall structure of this embodiment system was explained using Figures 1 to 9. In this Chapter 2, we will explain the characteristics and details of the data structure (communication protocol content) of the communication information communicated between systems within this embodiment as described in Chapter 1.

[0186] Section 2.1 Hierarchical Structure of Network Communication-Related Functions in This Embodiment A key feature of the network communication used in this embodiment is its hierarchical structure for each function, as shown in Figures 10A / B and 16-17B. Within this hierarchical structure, the physical layers PHY02 and PHY06, corresponding to the lowest-level physical functions shown in Figures 10A / B and 16-17B, specify the physical communication media necessary for network communication. When using wired Ethernet as a specific example of this physical communication media, cables and connectors with the shape and characteristics specified in the PHY06 standard are used. On the other hand, when using wireless as this physical communication media, the frequency, channel, modulation scheme, basic communication frame configuration, etc., are adapted to the PHY02 and PHY06 standard.

[0187] The media access layers MAC02 and MAC06, located above the physical layers PHY02 and PHY06, which support access functions on the communication media, define the information necessary to correctly transmit communication information between the network-connected nodes (device 1250 in Figure 8A or composite modules 1460 and 1470 in Figure 8B). Furthermore, the top-level extended application layer EXL06 and communication middleware layers APL06 and APL02 define the provision of various services using network communication (corresponding to various service provision functions using communication).

[0188] By providing a hierarchical structure corresponding to each function in this way, it becomes possible to select / combine the optimal format for each layer according to the characteristics and performance of the communication partner. As a result, the entire system of this embodiment achieves both lower costs (for the composite modules 1460 and 1470 shown in Figure 8B) and higher functionality of communication information (between the device 1250 shown in Figure 8A). A specific example of this effect is explained below. First, the physical layer PHY02 and the media access layer MAC02 can adopt the Z-format (details described later in Section 2.3), which is compatible with short-range wireless communication and is optimal for the "power saving" required for the composite modules 1460 and 1470. Furthermore, in order to optimize for the "low cost" required for the composite modules 1460 and 1470, the C-format (details described later in Section 2.5), in which "communication information is simplified," may be adopted for the communication middleware layer APL02. On the other hand, in order to accommodate the increased functionality required for communication between the server n_1116-n and the device 1250-1, the communication middleware layer APL06 may use the A-format (details described later in Section 2.7), E-format (details described later in Section 2.6), or W-format, which are capable of simultaneously communicating multiple pieces of information, and may also utilize the communication information of the extended application layer EXL06.

[0189] Furthermore, the following characteristic of this embodiment lies in the fact that, as an intermediate layer of communication information with the above-described hierarchical structure (a layer higher than the media access layer MAC02 and MAC06, and lower than the communication middleware layer APL02 and APL06), it is possible to "commonly" communicate information defined by Internet Protocol version 6 layer IPv6, which corresponds to Internet communication (Internet Protocol) functionality. Here, "commonly communicateable" means that when communicating with all nodes connected to the network within all of the embodiment systems shown in Figures 1 to 8B (meaning communication targets corresponding to the source and destination of network communication; specific examples in this embodiment include device 1250 in Figure 8A, server n_1116-n, wholesaler A_1102, or composite modules 1460 and 1470 in Figure 8B), it is permissible to communicate communication information defined by Internet Protocol version 6 layer IPv6 (details will be described later in Section 2.4). This situation can be explained in another way as follows. In other words, as shown in Figure 10A, the communication information used (transmitted) on the external network line 1788 and the internal network line 1782 (details to be described later) may include information defined by the same standard specification corresponding to Internet Protocol version 6 IPv6. Here, Internet Protocol version 6 IPv6 defines the communication protocol on the Internet and manages addresses and communication routes on the Internet. Therefore, the standard specification defined by Internet Protocol version 6 IPv6 allows for the setting of unique IP addresses (Internet Protocol Addresses) for any node (communication target), regardless of the type of node, such as wholesaler A_1102, server n_1116-n, system controller α_1126, device 1250-1, composite module 1460, 1470, etc. Thus, when communicating between different systems within the same domain 2_1122-2 in this embodiment (for example, when communicating between system α_1132 and system β_1134 in Figure 1), using the above IP address significantly simplifies the management of communication partners (details will be described later in Section 2.8).As a concrete example of its effects, for instance, it becomes possible to collect necessary information from the sensor / communication module 1460 at home (corresponding to the location of system α_1132 in Figure 1) or operate the drive / communication module 1470 from a mobile device such as a smartphone or tablet (corresponding to the system controller β_1128 in Figure 1) while on a business trip abroad (corresponding to the location of system β_1134 in Figure 1), significantly improving user convenience. Furthermore, in this case, both the business trip location (system β_1134) and the home (system α_1132) are protected within the same domain 2_1122-2, which prevents intrusion from other external sources, thus providing sufficiently robust security protection.

[0190] First, using the embodiment system model shown in Figure 8B, Figure 10A shows the hierarchical structure (architecture) for each function related to network communication. Note that in Figures 10A and 10B, the embodiment system model shown in Figure 8B was taken into consideration, and therefore, composite modules 1460 and 1470 are shown as the network nodes on the far right. Furthermore, instead of composite modules 1460 and 1470, the communication modules 1202-5 and 6 (and sensor modules 1260-3 to 1260-5) within devices 1250-2 and 3, which do not contain the device controller 1240-1 shown in Figure 8A, may be used as the network nodes on the far right within the same system network line 1782.

[0191] Here, the left side of Figure 10A shows the hierarchical structure (architecture) for each function related to communication between the servers n_1116-n and the system controller α_1126 in Figure 8B. The right side of Figure 10A shows the hierarchical structure (architecture) for each function related to communication between the system controller α_1126 and each composite module 1460, 1470 in Figure 8B.

[0192] As shown in Figure 1, in this embodiment of the system, the server n_1116-n can be installed in a location physically outside the area where system α_1132, to which system controller α_1126 belongs, resides. Therefore, as shown on the left side of Figure 10A, communication between server n_1116-n and system controller α_1126 utilizes the external network line 1788. This external network line 1788 may use an internet connection via wired or wireless. However, it is not limited to these; it is also possible to use network lines used within a relatively narrow area, such as a LAN (Local Area Network).

[0193] Furthermore, fiber optic cables may be used as the physical communication medium utilizing the wired connection described above. However, other signal transmission methods such as electric cords, telephone wires, or power lines may be used as the physical medium compatible with the wired connection described above. In addition, either analog or digital signals may be used as the transmitted signal format. Not only do the physical form of the communication medium and the signal format transmitted within it differ, but the communication standards at the physical layer PHY06 also differ depending on the communication line management company and the country or region that manages / supervises the communication. Therefore, in this embodiment of the system, all communication standards at the physical layer PHY06 via existing lines are collectively referred to as "L-format". On the other hand, if wireless communication is used at the physical layer PHY06 as the external network line 1788, communication standards such as 2G (Second Generation), 3G (Third Generation), or WiMAX (World Wide Interoperability for Microwave Access) may be used. Furthermore, this embodiment of the system is not limited to that; it can use communication information compliant with all wireless communication standards, including medium-range wireless systems. All of these wireless communication standards, from long-range to medium-range wireless systems, are collectively referred to here as "G-format."

[0194] In contrast, all composite modules 1460 and 1470 shown in Figure 8B are commonly located within system α_1132, which is managed by system controller α_1126. The physical extent of system α_1132 is limited to a relatively narrow area. Therefore, information communication between system controller α_1126 and composite modules 1460 and 1470 is performed using the intra-system network line 1782 shown in Figure 10A. To distinguish it from the "G-format" and "L-format" communication standards used in the external network line 1788 mentioned above, the communication standards used in the physical layer PHY02 of information communicated within the intra-system network line 1782 are collectively called "Z-format". In this embodiment of the system, either wireless or wired (or a combination thereof) may be used as the intra-system network line 1782.

[0195] On the other hand, the standards used in the media access layer MAC02 / 06 shown in Figure 10A are often considered / proposed by the same standards-setting organization as those used in the physical layer PHY02 / 06. Therefore, within the media access layer MAC06 transmitted over the external network line 1788 between server n_1116-2 and system controller α_1126, the "L-format" or "G-format" can be used in accordance with the physical layer PHY06. Similarly, within the media access layer MAC02 transmitted over the same internal network line 1782 between system controller α_1126 and composite modules 1460 and 1470, the "Z-format" can be used. However, this is not limited to these cases; for example, the Z-format may be used in the physical layer PHY02, and the L-format or G-format may be used in the media access layer MAC02. Alternatively, the L-format or G-format may be used in the physical layer PHY06, and the Z-format may be used in the media access layer MAC06.

[0196] The processing of information related to each function from the physical layer PHY06 to the Internet Protocol version 6 layer IPv6 (mainly communication control processing) is performed by communication modules 1768 and 1202-3 within the server n_1116-n and system controller α_1126. The communication module 1660 within the composite modules 1460 and 1470, whose internal structure is explained in Figures 5 and 66, can be functionally divided into a communication control unit 1700 and an interface unit 1710. The processing of information related to each function from the physical layer PHY02 to the Internet Protocol version 6 layer IPv6 (mainly communication control processing) is performed within this communication control unit 1700.

[0197] Up until now, information related to each function from the physical layer PHY06 to the Internet Protocol version 6 layer IPv6 has mainly been related to communication control and has little relation to the functions, operation, or performance of, for example, device 1450. In contrast, the communication middleware layers APL02 and APL06 and the extended application layer EXL06 in Figure 10A are related to various service provision functions that utilize network communication. The processing of communication information related to the functions of the communication middleware layer APL06 and the extended application layer EXL06 (mainly processing related to service provision to the user) is executed by processors 1738 and 1230 within the server n_1116-n and system controller α_1126. In contrast, information related to the functions of the communication middleware layer APL02, which is communicated via the same system network line 1782, is processed within the interface section 1710 of the communication module 1660 within the composite modules 1460 and 1470. Thus, a key feature of this embodiment of the system is that the composite modules 1460 and 1470 do not require expensive processors, and all communication information transmitted via the same system network line 1782 can be processed within the communication module 1660. By eliminating the need for an expensive processor, the composite modules 1460 and 1470 can be provided at a low cost.

[0198] A key feature of this embodiment of the system is that, among the information communicated via the external network line 1788, unique information usable only on specific application software installed on both the server n_1116-n and the system controller α_1126 can be stored and communicated within the extended application layer EXL06. This enables differentiation between application software installed on both the server n_1116-n and the system controller α_1126. As a result, competitive development based on the principle of competition is promoted among application software from various companies, accelerating the progress of application software technology and improving user convenience. Furthermore, by utilizing the unique information stored within the extended application layer EXL06, the quality of services provided by the application software to the user can be improved. As the performance and additional expansion capabilities of devices 1250-1 and 1250-2, shown in Figures 8A and 9, improve and develop in the future, it will be necessary to successively update the A-, E-, and W- formats used in the communication middleware layer APL06. However, updating the standard specifications is a very complicated process, which creates a problem as it is difficult for these standard updates to keep pace with the performance improvements and additional expansions of devices 1250-1 and 1250-2. In contrast, by utilizing the extended application layer EXL06, application software vendors can easily respond to performance improvements and additional expansions of devices 1250-1 and 1250-2 without waiting for standard updates. In this way, the information stored and communicated within the extended application layer EXL06 can be freely configured by a specific software vendor, so there is no need to pre-define the description format of the communication information here as a global standard.

[0199] In contrast, communication information related to the service provision functions of the communication middleware layer APL02 / APL06 may use information conforming to a standardized format, such as the A-, E-, W-, or C- formats. When communication information related to the service provision functions of the communication middleware layer APL02 / APL06 conforms to a predetermined standard format, it becomes easier to achieve interoperability between servers 1116 and system controllers 1126 / 1128, and between composite modules 1460 and 1470.

[0200] As shown in Figure 25, both the server n_1116-n and the system controller α_1126 have large-capacity memory units 1232 (and database 1118-n) and can have high-speed, powerful processors 1738 / 1230. Therefore, a wide variety of communication information corresponding to diverse service provision can be set within the communication middleware layer APL06 transmitted between them. In contrast, it is difficult to incorporate a processor capable of handling diverse service provision within the composite modules 1460 and 1470. Therefore, in response to the above situation, in this embodiment of the system, a format different from the format used within the communication middleware layer APL06 (such as A-format, E-format, or W-format) (such as C-format) may be used within the communication middleware layer APL02 for information communication with the composite modules 1460 and 1470. In particular, by relatively simplifying the C-format used within the communication middleware layer APL02 (details will be described later in Section 2.5), it is possible to reduce the processing burden within the composite modules 1460 and 1470, thereby lowering the cost. Furthermore, by improving the relative processing speed and shortening the processing time, it is possible to reduce the power consumption of the built-in energy storage module (battery) 1554. However, this embodiment of the system is not limited to this, and A-format, E-format, or W-format may also be used for information communication with the composite modules 1460 and 1470.

[0201] Here, the switching (conversion) process between information used within the communication middleware layer APL02 contained in communication information using the same internal network line 1782 and information used within the communication middleware layer APL06 contained in communication information using the external network line 1788 is processed within the system controller α_1126. However, within the communication middleware layers APL02 and APL06 of this embodiment, the communication information used within the same internal network line 1782 and the communication information used within the external network line 1788 do not necessarily have to be exactly the same; there may be some differences between the two sets of communication information. This processing method will be explained below. As already explained in sections 1.1 and 1.7, and as shown in Figure 8B, the system controller α_1126 manages and operates network communication within the network system α_1132. Then, all the information detected by all the sensors / communication modules 1460 and all the status information controlled (set) by the drive / communication module 1470, which are obtained sequentially in real time via the same system network line 1782, are appropriately stored as management information 1744 in the memory section 1232 of the system controller α_1126. Here, the above management information 1744 may be stored in table format as a management table. Furthermore, if the configuration of Figure 8A and Figure 8B is combined, the system controller α_1126 simultaneously stores information of all devices 1250 (such as detection information and current status information) as part of the above management information 1744. Then, the system controller α_1126 extracts only the specific information within the scope where the user's personal information is protected from the above management information 1744 and communicates this information to the server n_1116-n via the system network line 1788. The information communicated to server n_1116-n is then stored in database 1118-n as management information 1748 (which may be in table format) managed by server n_1116.In this way, the system controller α_1126 performs conversion (information switching) between communication information used within the communication middleware layer APL02 and communication information used within APL06. This not only protects user security but also simplifies the processing of servers n_1116-n by pre-selecting and receiving only the minimum necessary information.

[0202] Combining the above description with the overall system overview of this embodiment already explained in Section 1.1, the client system has the following characteristics. Specifically, it is connectable to an external cloud (server n_1116-n in Figure 1) and comprises a system controller α_1126 that manages information, and units (units 1_1290-1 to 7_1290-7 in Figure 2) that have the function of acquiring, creating and transmitting information to be provided to the system controller α_1126. The system controller α_1126 divides the multiple existing units into sections to be managed (sections 1_1142-1 to m_1142-m in Figure 1), and each unit belongs to the section... An electronic device system that holds information relating to a cloud, wherein communication between the system controller and the plurality of units (a composite module 1295, 1460, 1470, which is a type of unit) uses a first data format (corresponding to the C-format or Z-format in Figure 10A), and communication between the system controller α_1126 and the cloud (server n_1116-n in Figure 10A) uses a second data format (corresponding to the A / E / W-format or L / G format). In particular, the first data format and the second data format are different data formats.

[0203] As will be described later in Section 2.2, the first data format consists of a header (corresponding to the physical layer header PHYHD in Figure 11), first data (data from the MAC layer header MACHD to the TCP header TCPHD in Figure 11), and second data (communication middleware data APLDT) in addition to the first data.

[0204] Furthermore, when performing communication processing of communication information having the above characteristics via the system controller α_1126 described above, the following characteristics apply. Specifically, the system controller α_1126 converts the communication information obtained from the unit (a type of composite module 1295, 1460, 1470) into the second data format (A / E / W-format or L / G format in Figure 10A) and transmits it to the cloud (server n_1116-n), and also converts the information communicated from the cloud (server n_1116-n) into the first data format (C-format or Z-format) and transmits it to the unit (a type of composite module 1295, 1460, 1470).

[0205] Here, the unit includes a function to transmit information to the system controller (handled by the communication module 1660 shown in Figure 4A), a function to detect external environmental information such as temperature and illuminance (handled by the sensor module 1260 in Figure 4B), or a state change function to change the state of the unit itself, which is the basis for the transmitted information (handled by the drive module 1670 in Figure 4C). Therefore, as part of the communication function, the unit acquires or creates information in the first data format.

[0206] For the sake of clarity, Figures 4A to 4C show the communication module 1660, sensor module 1260, and drive module 1670 separately. However, in this embodiment, they may share functions or some functions may overlap. In such cases, the detection function or state change function within the unit will share the communication function.

[0207] Furthermore, if the structure shown in Figure 7A is adopted within the communication module 1660, the functions of the communication module 1660 may be realized entirely by a combination of functional circuits without using the processor 1960 shown in Figure 7A. In this case, the unit will not have a CPU (Central Processing Unit) to process the information.

[0208] Next, Figure 10B will be used to explain the comparison of the characteristics of each communication information used (transmitted) within the same system network line 1782 and system network line 1788 within the same communication middleware layers APL02 and APL06. Communication information conforming to A-format or E-format may be used for communication between system controller α_1126 and server n_1116-n via system network circuit 1788. In this embodiment of the system, A-format includes all formats that are "described in a broad sense as communication information related to the communication middleware layer APL in a text format." On the other hand, as will be described later in Section 2.6, E-format includes all formats that utilize a format in which "setting codes are stored in a predetermined area defined in advance" within the area of ​​the communication middleware data APLDT (see Section 2.2). In particular, A-format and E-format have the characteristic that "multiple pieces of information (information including plural items) can be communicated (transmitted) at once." However, the external network circuit 1788 used for this information communication is at risk of temporary network congestion due to the usage status of other users. Therefore, if a method is adopted in which communication is repeated very frequently between the system controller α_1126 and the server n_1116-n, there is a risk that communication between the two will stagnate only during periods when the network line is abnormally congested. In contrast, as shown in this embodiment, by adopting a format that allows multiple pieces of information to be communicated at once, the frequency of communication between the two can be reduced, thereby reducing the risk of communication stagnation. However, this embodiment of the system is not limited to this, and communication information compliant with C-format or W-format may also be used for communication between the system controller α_1126 and the server n_1116-n.

[0209] In the above A-format or E-format, multiple tables in a predetermined template format are defined according to the type of exchange information 1810 communicated between the system controller α_1126 and the server n_1116-n. Information indicating which type of table to adopt as a template is included in the exchange information 1810 as exchange information type identification information 1840. By sharing the communicated exchange information (table) 1810 between the system controller α_1126 and the server n_1116-n in this way, the efficiency of information processing between the two companies is improved. In other words, by installing application software that includes the processing routine for the above exchange information (table) 1810 on both the system controller α_1126 and the server n_1116-n, it becomes possible to provide advanced services to users.

[0210] On the other hand, information indicating the purpose of use of the exchange information (table) 1810 to be notified to the recipient is included in the exchange information (table) 1810 as communication access control information 1830. For example, in the E-format, the communication access control information 1830 has codes set for "write request," "read request," "notification request," "write / read request," as well as "write response," "notification," "read response," "notification response," and "write / read response." In the A-format, the communication access control information 1830 can also be described in XML (Extensible Markup Language) format within the exchange information (table) 1810, such as "WRITEONLY" (meaning a status setting instruction to the recipient or notification of the sender's status to the recipient), "READONLY" (meaning a request for a response regarding the recipient's current status), or "READWRITE."

[0211] Although not shown in Figure 10B, another method of communicating information via the external network line 1788 is to use the World Wide Web. This method corresponds to the W-format in Figure 10A, and either server n_1116-n or system controller α_1126 also functions as a web server. In this case, the sender of the communication information (either server n_1116-n or system controller α_1126) specifies the recipient (the other side of server n_1116-n or system controller α_1126) based on the URL (Uniform Resource Location), and automatically writes the communication information into the input field specified in the form format on the homepage. Once the information communication is complete, the receiving side saves the received information (or its processing result) to management information 1744 or 1748 according to a program pre-configured in PHP (a recursive abbreviation for Hypertext Preprocessor) or a Java applet. By providing multiple input fields in a form format within the same homepage, it becomes possible to configure the system to allow for the simultaneous communication (transmission) of information containing multiple types of content, thus achieving the aforementioned effects even with the W-format. Therefore, the W-format in this embodiment of the system includes any format in which the sender fills in input fields designated in advance by the receiver to communicate information. Furthermore, it is not limited to this; any format containing HTML or HTML5-specific "tags" may also be classified as the W-format.

[0212] As described above, in the information communication between servers n_1116-n and system controller α_1126 via the external network line 1788, measures have been taken to reduce the frequency of communication. In contrast, with the internal network line 1782, the system controller α_1126 manages and operates the communication lines within the network system, so there is no risk of communication stagnation due to network line congestion. More importantly, in order to reduce the cost and size of the composite modules 1460 and 1470, the communication information in the communication middleware layer APL02 for the composite modules 1460 and 1470 has been simplified. As a specific example, information communication can be performed in any of the cases 1 to 3 shown in Figure 10B. In this case 1, for example, the system controller α_1126 issues a command (command issuance) 1852 to change the setting state (state control) to the drive / communication module, and the drive / communication module responds with the result of executing the command 1852. In Case 2, for the purpose of collecting sense information (detection information) from the sensor / communication module 1460, the system controller α_1126 issues a response request 1872, and the sensor / communication module 1460 responds with sense information (detection information) as a response 1874. If the sensor / communication module 1460 notifies the system controller α_1126 of sense information (detection information) at any time (or at a pre-set periodic time), it may also perform periodic / irregular reporting 1894 as in Case 3.

[0213] In this embodiment, the information communication method is not limited to the above; other communication methods may be used. For example, as shown in Figure 8A, if a device 1250-1 containing a device controller 1240-1 and a memory unit 1242 is installed within the system α_1132, information communication between this device 1250-1 and the system controller α_1126 over the same system network line 1782 may utilize a communication middleware layer APL06 or an extended application layer EXL06 compliant with A-format, E-format, or W-format, as shown in Figure 16. In this embodiment, application software that can utilize the extended application layer EXL06 may be pre-installed in the server n_1116-n. After obtaining user permission via the user I / F unit 1234 (shown in Figure 8A), the system controller α_1126 may automatically install the application software on both the system controller α_1126 itself and the corresponding device 1250. At this time, the system controller α_1126 accesses the server n_1116-n and transfers the application software that has been pre-stored in the database 1118-n. In this way, the system controller α_1126 acts as an intermediary, connecting the external network circuit 1788 and the internal network circuit 1782, enabling the automatic installation of the application software up to the corresponding device 1250. This allows for the automatic construction of an environment where the extended application layer EXL06 can be utilized without burdening the user, thus ensuring the ease of use and flexibility of the newly functionally enhanced latest device 1250 within the network system. However, the system in this embodiment is not limited to the above; for example, communication information compliant with the C-format may be used for information communication in the communication middleware layer APL06 between the system controller α_1126 and the device 1250 as shown in Figure 16.

[0214] As shown in Figure 9, if devices 1250-1 and 1250-4 and server n_1116-n are directly connected via router (gateway) 1300, router (gateway) 1300 is placed between device 1250 and server n_1116-n instead of system controller α_1126 in Figure 16. In this case, the same communication information is used in both the external network circuit 1788 and the internal network circuit 1782 within the same system in the extended application layer EXL06 and the communication middleware layer APL06. Furthermore, since each device 1250 and server n_1116-n has its own IP address set, direct information communication can be performed between device 1250 and server n_1116-n using the transmitting IP address information SIPADRS and receiving IP address information DIPADRS (details will be described later in Section 2.4 using Figure 13) set in the Internet Protocol version 6 layer. Furthermore, in this case, the information communication between device 1250 and server n_1116-n at the communication middleware layer APL06 mainly uses communication information compliant with E-format or A-format. However, in this embodiment of the system, it is not limited to these, and C-format or W-format may also be used. By using the same communication information both within the external network circuit 1788 and the internal network circuit 1782 of the same system, the burden on the relay processing of the router (gateway) 1300 can be significantly reduced. However, different formats may be used for the physical layer PHY02, PHY06 and the media access layer MAC02, MAC06 (in the example in Figure 16, Z-format is used for the internal network line 1782 of the same system, and L-format or G-format is used for the external network line 1788). In this case, format conversion is performed within the router (gateway) 1300.

[0215] On the other hand, as shown in Figure 1, when communicating information between system controllers α_1126 and β_1128, which belong to different systems α_1132 and β_1134 but are within the same domain 2_1122-2, the same communication method as between system controller α_1126 and servers n_1116-n shown on the left side of Figure 10A may be used. In this case, the same communication information as on the external network line 1688 may be used in all layers from the physical layer PHY06 to the extended application layer EXL06. In this case, as described above, application software may also be automatically installed on system controller β_1128. Therefore, in this case, communication information in the communication middleware layer APL06 mainly uses communication information compliant with E-format or A-format. However, in this embodiment, the system is not limited to these, and C-format or W-format may also be used. In this case, the format used by the physical layer PHY06 and the media access layer MAC06 can be either the L-format or G-format if the distance between systems α_1132 and β_1134 is large, or the Z-format if the distance between systems α_1132 and β_1134 is small. Here, the L-format and G-format allow information communication anywhere in the world, but the communication time is relatively long, while the Z-format has a limited communication range but the communication time is relatively short. Therefore, by switching the format used according to the distance between the two, it is possible to appropriately utilize the advantages of both formats.

[0216] Furthermore, as an application example of this embodiment system, consider the case where Figure 1 and Figure 8B are mixed. In this case, the system controller β_1128 (Figure 1) in a different system β_1134 may directly access the composite modules 1460 and 1470 in system α_1132. In this case, the communication method is the same as replacing the server n_1116-n in Figure 10A with the system controller β_1128 shown in Figure 1, and replacing the external network line in Figure 10A with an intra-domain network line. Therefore, in this case, L-format, G-format, A-format, E-format, or W-format may be used as communication information within the intra-domain network line 2082. Moreover, this embodiment system is not limited to these, and for example, Z-format or C-format may also be used. Also, similarly to the above, the format may be automatically switched between Z-format and L / G-format depending on the distance between the composite module (in system α_1132) and the system controller β_1128. The detailed method for using Internet Protocol version 6, IPv6, in this case will be described in detail in Section 2.8.

[0217] Section 2.2 Relationship between the Hierarchical Structure of Communication-Related Functions and Communication Information on Network Lines Figure 11 shows the relationship between the functional hierarchical structure shown in Figures 10A and 16-17B and the specific communication information content actually communicated within the network line. Whether the network communication medium is wired or wireless, communication information is transmitted intermittently on these physical communication mediums in units of one block. This block corresponds to the physical layer frame PPDU in Figure 11(f). In the case of a single channel (single responder), other communication information cannot be transmitted on the network communication medium when the above block (physical layer frame PPDU) is transmitted. Therefore, if the size of the above block (physical layer frame PPDU) is too large, the time occupied by the network communication medium will increase, and there is a risk of hindering other communications. To solve the above problem, in this embodiment of the system, the data size of one physical layer frame PPDU is set to 127 bytes or less. This has the effect of reducing the harmful effect of one physical layer frame PPDU communication hindering other information communications within the network system. Furthermore, as shown in Figure 11(a), within this single physical layer frame PPDU, the data is composed in the order of transmission from the sender to the receiver (from front to back or in order of the earliest timing of sending information): physical layer header PHYHD, MAC layer header MACHD, IPv6 header IPv6HD, TCP header TCPHD, communication middleware data APLDT, extension data EXDT, and false check CRC. On the other hand, looking at this data arrangement from the perspective of Figure 11(f), it can also be said that "the physical layer header PHYHD is placed at the beginning of the physical layer frame PPDU, followed by the physical layer data or physical layer payload PSDU, and then the MAC layer header MACHD, IPv6 header IPv6HD, TCP header TCPHD, communication middleware data APLDT, extension data EXDT, and false check CRC are sequentially stored within this physical layer data / payload PSDU."

[0218] In the physical layer PHY02 and PHY06 shown in Figures 10A and 16-17B, the processing of the entire physical layer frame PPDU is performed. Here, the physical layer PHY02 and PHY06 represent an abstract concept of "functions that deal with physical communication media." In contrast, the actual processing corresponding to each function from the physical layer PHY02 and PHY06 to the Internet Protocol version 6 layer IPv6 is performed inside the communication modules 1768, 1202-3 and the communication control unit 1700 (Figure 10A). In this Section 2.2, in order to make it easier to explain the relationship between the functions of each layer and the communication information transmitted over the network line, the information transfer procedures for each layer are explained in detail. However, it is not necessary to omit some of the information transfer procedures for each layer when creating the communication information. For example, during transmission, the communication modules 1768, 1202-3 and the communication control unit 1700 (Figure 10A) may directly create the information (data structure) shown in Figure 11(a) from the communication middleware data APLDT and extended data EXDT (or just the communication middleware data APLDT) provided from the communication middleware layers APL02 and APL06 (in practice, provided from the interface section within the processors 1230 and 1738 in Figure 10A or the communication module 1660), and then transmit (transmit) it from the network lines 1782 and 1788. Furthermore, upon reception, the communication modules 1768, 1202-3 and the communication control unit 1700 (Figure 10A) may selectively extract only the necessary physical layer frame PPDU from the network lines 1782 and 1788, extract the communication middleware data APLDT and extended data EXDT (or just the communication middleware data APLDT), and pass them to the communication middleware layers APL02 and APL06 (effectively the processors 1230 and 1738 in Figure 10A or the interface section within the communication module 1660).

[0219] The detailed receiving functions of the physical layer PHY02 and PHY06 include identifying the contents of the physical layer header PHYHD located at the beginning of the received physical layer frame PPDU, and passing the entire physical layer data or physical layer payload PSDU located immediately after it to the media access layer MAC02 and MAC06. Therefore, from the perspective of the media access layer MAC02 and MAC06, this entire physical layer data or physical layer payload PSDU corresponds to the MAC layer frame MPDU. On the other hand, the detailed transmitting functions of the physical layer PHY02 and PHY06 include storing the MAC layer frame MPDU received from the media access layer MAC02 and MAC06 in the physical layer data or physical layer payload PSDU, and transmitting the physical layer frame PPDU, which is constructed by adding the physical layer header PHYHD to the beginning, over network lines 1782 and 1788.

[0220] As shown in Figure 11(e), the MAC layer frame MPDU consists of, from the beginning, the MAC layer header MACHD, the MAC layer data / payload MSDU, and the false check CRC. When the media access layer MAC02 and MAC06 receive data, they use the communication information stored in the MAC layer header MACHD within the MAC layer frame MPDU passed from the physical layer PHY02 and PHY06 to perform access control on the communication medium. Specifically, they extract only the MAC layer data / payload MSDU related to the corresponding device 1250, composite modules 1460 and 1470, or system controller α_1126, and pass it to Internet Protocol version 6 layer_IPv6. On the other hand, when transmitting data, they store the information passed from Internet Protocol version 6 layer_IPv6 within the MAC layer data / payload MSDU, add the MAC layer header MACHD to form a MAC layer frame MPDU, and pass it to the MAC layer frame MPDU side.

[0221] By using the false check CRC (Figure 11(e)) attached to the last position within the MAC layer frame MPDU, it becomes possible to check for data errors within the MAC layer frame MPDU (or to extract the location of data errors). Specifically, the false check CRC in this embodiment uses the CRC (Cyclic Redundancy Checksum) code. This is calculated as the remainder in the binary representation when the MAC layer header MACHD (a sequence of "1"s or "0"s) within the MAC layer frame MPDU is divided by a predetermined code. When transmitting, the false check CRC calculated using the above method is attached to the last position within the MAC layer frame MPDU. When receiving, the remainder obtained when the MAC layer header MACHD and the MAC layer data / payload MSDU are divided by the aforementioned code is compared with the false check CRC obtained at reception. If the two match, it is considered "error-free". If there is an "error", the error location can be extracted by performing an inverse operation on the false check CRC obtained at reception. Here, the error correction capability (i.e., the size of the error-correctable area within the entire error-correctable data including this false check CRC (in this case, the entire MAC layer frame MPDU)) is determined by the data size of the false check CRC. Therefore, if the data size of the false check CRC is fixed, a smaller overall data size of the error-correctable data including this false check CRC (MAC layer frame MPDU) increases the relative error correction capability, thus improving the data reliability of the MAC layer frame MPDU (when error correction is taken into consideration).

[0222] Taking the above situation into consideration, a key feature of this embodiment is the placement of the error-checking CRC at the very end of the MAC layer frame, as shown in Figure 11(e). As explained in Section 2.3 using Figure 12A, the physical layer header PHYHD contains a large amount of relatively robust information. That is, even if some error bits are mixed into the physical layer header PHYHD, it is possible to automatically correct them by some means. In contrast, the data accuracy required for the information in the MAC layer frame MPDU handled by the media access layer MAC02, MAC06 and above is very high. Therefore, by removing the relatively robust physical layer header PHYHD and adding an error correction function to the entire MAC layer frame, the relative error correction capability can be improved, thereby relatively improving the reliability of the entire communication information (physical layer frame PPDU).

[0223] Next, as shown in Figure 11(d), the information consisting of the IPv6 header IPv6HD placed at the beginning, followed immediately by the IPv6 data / payload IPv6DU, is stored within the MAC layer data / payload MSDU. In Internet Protocol version 6 layer IPv6, during transmission, the TCP header TCPHD, communication middleware data APLDT, and extension data EXDT are stored within the IPv6 data / payload IPv6DU, and the IPv6 header IPv6HD is added before passing it to the media access layer MAC02 and MAC06. During reception, the IPv6 header IPv6HD is extracted from the MAC layer data / payload MSDU received from the media access layer MAC02 and MAC06, processed independently, and finally the communication middleware data APLDT and extension data EXDT (or communication middleware data APLDT only) are passed to the communication middleware layer APL02 and APL06.

[0224] The communication middleware data APLDT and extended data EXDT (or communication middleware data APLDT only) shown in Figure 11(b) are processed within the communication middleware layers APL02 and APL06. The various service provision functions using network communication, which are handled by the communication middleware layers APL02 and APL06, are realized by various processes performed by the processors 1230, 1738, and 2030, the device controller 1240, or the interface section within the communication module 1660, as shown in Figures 10A and 16 to 17B.

[0225] Section 2.3 Z-Format Data Structure in the Physical and Media Access Layers Figure 12A shows a specific example of the data structure in the physical header PHYHD and MAC layer header MACHD, based on the Z-format (see Figures 10A and 16) usable by the physical layer PHY02 and media access layer MAC02 corresponding to the intra-system network circuit 1782. However, the Z-format described below is merely one example used in this embodiment of the system, and other formats corresponding to the intra-system network circuit 1782 may be used. Furthermore, the hierarchical structure is not limited to the physical layer PHY02 and media access layer MAC02 described above; information without a hierarchical structure or information corresponding to a different hierarchical structure may be used as information communicated on the intra-system network circuit 1782.

[0226] First, the data structure in Figure 12A(c) is a direct copy of the content in Figure 11(a). Then, as shown in Figure 12A(b), the physical layer header PHYHD consists of a synchronization header SYNC, which is placed in the first 5 bytes, and the physical layer data / payload length information LPSDU, which is placed immediately after it in a 1-byte section. Therefore, the data size of this physical layer header PHYHD is 6 bytes (5+1). This physical layer data / payload length information LPSDU represents the data size of the physical layer data / payload PSDU in Figure 11(f) and is set in bytes. As explained at the beginning of Section 2.2, the maximum data size of the entire physical layer frame PPDU is set to 127 bytes. Therefore, a value of 121 bytes (127-6) or less is set in this physical layer data / payload length information LPSDU.

[0227] Next, as shown in Figure 12A(a), the synchronization header SYNC consists of a 5-byte preamble PRM placed first, followed by a 1-byte physical layer frame start information SFD. The preamble PRM is set to [00000000h] (where "h" represents a hexadecimal value). Since the signal modulation uses a direct sequence spread spectrum method, the synchronization signal is obtained from the above preamble PRM section, which consists entirely of "0". Within the area of ​​the physical layer frame start information SFD, [A7h] is set. Converting the hexadecimal value [A7h] to binary results in "10100111".

[0228] The method of using the communication information within the physical layer header PHYHD in the communication control unit 1700 within the communication module 1660 in Figure 10A, or in communication modules 1768, 1202-3, or in communication modules 1202-4, 2002 in Figures 16 to 17B will be explained. The communication information within the physical layer header PHYHD is mainly used for chip synchronization and bit synchronization on the receiving side. That is, the above communication module has a built-in oscillator (PLL circuit: Phase Lock Loop Circuit) that can automatically synchronize frequency and phase. This oscillator (PLL circuit) then automatically synchronizes frequency and phase in accordance with the preamble PRM (chip synchronization). Next, the position of the physical layer frame start information SFD is detected by a method such as pattern matching, and (1) it is recognized that the physical layer PHY02 is using the Z format, and the starting bit position of the MAC layer header MACHD is detected from a sequence of binary bits 1 / 0 (bit synchronization).

[0229] As shown in Figure 12A(d), the MAC layer header MACHD consists of areas that store the MAC layer frame control information MACNTL, the MAC layer sequence number MASQNM, and the address information MADRS, in the order of transmission from the sender to the receiver (from the beginning to the end or in the order in which the information is sent).

[0230] Within the MACNTL area of ​​the first MAC layer frame, two bytes of information controlling the entire MAC layer frame MPDU (Figure 11(f)) are stored. Further details within the MACNTL include the first three bits, which store information indicating the type of the MAC layer frame MPDU. Specific types include identifiers such as "beacon," "data," "ACK (Acknowledgement)," and "command frame type." The next bit stores information about the presence or absence of security. The following bit stores information about the presence or absence of pending data, and the bit immediately following stores information about the presence or absence of the aforementioned Acknowledgement message request.

[0231] The next bit then stores information indicating whether the relevant information communication is limited to communication within a PAN (Private Area Network) or whether it spans multiple PANs. As already explained using Figure 1 or Figure 8A, in this embodiment of the system, one PAN may correspond to one system α_1132 or to one section 1142. Therefore, the method of setting the above information may be changed depending on which one is used. However, when using the Z-format for information communication within the same domain network line 2082, this information area may store information corresponding to "communication spanning multiple PANs". This is because, as shown in Figure 1, this embodiment of the system allows for a situation where the distance between system controller α_1126 and system controller β_1128 is large (exceeding one PAN) within the same domain 2_1122-2. Therefore, in this case, the storage area stores information corresponding to "communication spanning multiple PANs". On the other hand, if the portable system controller β_1128 is moved closer to the system controller α_1126 (i.e., moved within the same PAN), the storage area will contain information corresponding to "communication within the PAN".

[0232] The two bits immediately following and the last two bits within the MACNTL (2 bytes) control information of the MAC layer frame store the address and mode information of the receiving and transmitting sides, respectively. Here, the Z-format can specify either the IEEE extended addresses DEXADRS and SEXADRS, or a shortened address. Incidentally, a feature of this embodiment of the system is that both the receiving and transmitting sides use the IEEE extended addresses DEXADRS and SEXADRS as the address and mode information, as shown in Figure 12A(e). In this embodiment of the system, network communication is not only possible via the system controller α_1126 and the communication modules 1202-3~6 built into the devices 1250-1~3, as shown in Figure 8A, but also via composite modules such as the sensor / communication modules 1460-1~5 and the drive / communication modules 1470-1, 2, as shown in Figure 8B. Therefore, in this embodiment system, by using the IEEE extended addresses DEXADRS and SEXADRS in this address mode, it is possible to easily identify whether it is communication module 1202-3~4 or composite module 1460-1~5, 1470-1, 2 at the media access layer MAC02 level (details will be described later using Figure 12B(e)), which has the effect of (1) enabling high-speed switching of the communication middleware layer APL02 on the receiving side (C-format or other format), and (2) making it easier to detect any errors on the transmitting side that may occur (recognition of whether it is communication module 1202-3~4 or composite module 1460-1~5, 1470-1, 2).

[0233] Next, we will explain the information storage area for the MAC layer sequence number MASQNM, which has a data size of 1 byte, as shown in Figure 12A(d). As mentioned above, in this embodiment of the system, the total data size of the physical layer frame PPDU is set to 127 bytes or less. Therefore, if the combined data size of the communication middleware data APLDT and the extended data EXDT (see Figure 11(b)) becomes large, one physical layer frame PPDU alone will not be sufficient to communicate (transmit) this information. This risk is particularly high when using A-format or E-format as the communication middleware layer APL06. As a countermeasure, in this embodiment of the system, the above-mentioned communication middleware data APLDT and extended data EXDT are divided into 256 (2 to the power of 8) physical layer frame PPDUs, making them available for transmission (communication). Specifically, the communication middleware data APLDT and extended data EXDT are divided into multiple parts and transmitted (communicated) sequentially over the network line. In this case, the physical layer header PHYHD and IPv6 header IPv6HD (and TCP header TCP) shown in Figure 11(a) all contain the same information. Then, in accordance with the transmission (communication) order on the network line, a value starting from "0" and incremented by 1 is stored in the area of ​​the MAC layer sequence number MASQNM. As a result, the transmission order of the communication middleware data APLDT and the extended data EXDT is determined, which has the effect of enabling stable information communication even if the reception order of the physical layer frame PPDU is changed due to a network problem.

[0234] The data structure shown in Figure 12B(c) is exactly the same as that in Figure 12A(e), so we will use Figure 12B to explain the address information MADRS within the MAC header MACHD. In this embodiment of the system shown in Figure 1, one system α_1132 may be formed by a single PAN (Private Area Network), or by a combination of multiple PANs. Furthermore, each section 1142-1~m within the same system α_1132 may be formed by one or more PANs. When one system α_1132 is composed of multiple PANs in this way, the system controller α_1126 needs to manage the above multiple PANs. Information communication takes place across different PANs within the same system α_1132. To accommodate this situation, the system controller α_1126 assigns PAN-specific identification information to each PAN, and as shown in Figure 12B(c), it sets up areas within the address information MADRS storage area to store PAN-specific identification information DPANID and SPANID related to the PAN containing the receiving and transmitting nodes.

[0235] Both the receiving and transmitting sides have IEEE extended addresses DEXADRS and SEXADRS, each containing a storage area for a 1-byte extended IEEE extended address EXEXADRS and an 8-byte chip-specific configuration address ADRSIEEE compliant with IEEE 802.15.4. Here, the chip-specific configuration address ADRSIEEE compliant with IEEE 802.15.4 refers to a unique number pre-assigned to each composite module, such as all communication modules 1202-3~6, sensor / communication modules 1460-1~5, and drive / communication modules 1470-1, 2, etc., that comply with the IEEE 802.15.4 standard worldwide. This unique number does not overlap globally between different communication modules or composite modules. This unique number is assigned before shipment of the aforementioned communication modules 1202-3~6 and composite modules, but it is also possible to obtain a unique number by directly applying to the IEEE. When the IEEE or a designated official organization issues this unique number, the issuing organization obtains information, particularly regarding the performance and functions of the composite module, as well as the type of communication information (category and template type used for information communication) when communicating in the corresponding C-format. Therefore, not only can the functions and performance of each target composite module be determined from the ADRSIEEE information of the chip-specific configuration address compliant with IEEE 802.15.4, but the type of communication information using the C-format can also be officially predicted, which has the effect of enabling fast and easy preparation of the corresponding processing in the communication middleware layer APL02.

[0236] Next, an example of the data structure within the Expanded IEEE Extension Address (EXEXADRS) in the system of this embodiment is shown in FIG. 12B(e). The first 1 bit in this is an area where module structure information MST can be stored. When this 1 bit is [0], it represents the communication modules 1202-3 to 6 built into the system controller α_1126 or devices 1250-1 to 3. On the other hand, when this bit is [1], it indicates that the corresponding node has a composite module structure. Further, the information stored in the next 1-bit area means composite module structure information CMST. When this bit is [0], the corresponding node indicates a sensor / communication module, and when this bit is [1], the corresponding node indicates a drive / communication module.

[0237] The sense information transmitted from the sensor / communication module starts from binary optical levels (whether the illumination is ON or OFF) or multi-valued optical levels (corresponding to illuminance), and extends to various types such as human presence and temperature. Also, as described in Section 1.5 using FIGS. 6A to 6D, the information for controlling the drive / communication module also extends to various types such as binary values of ON / OFF, multi-values, or remote control information of devices. Therefore, in the system of this embodiment, an area is provided where information for identifying the types of the above-mentioned sensor / communication module 1460 and drive / communication module 1470 corresponding as nodes can be recorded as 6-bit composite module type identification information CMTID. Regarding the method of setting information CNTID for identifying the type of each of these composite modules 1460 and 1470, in the A-format as a method of identifying the type of device 1250

[0238]

[0239]

[0240]

[0241]

[0242]

[0243]

[0244]

[0245]

[0246]

[0247]

[0248]

[0249]

[0250]

[0251]

[0252]

[0253]

[0254]

[0255]

[0256]

[0257] The E-format utilizes the number attribute within the Element (see explanation in Section 2.7 using Figure 15B) and employs the exchange information type identification information EPC (see explanation in Section 2.6 using Figure 15A(f)). Therefore, this composite module type identification information CMTID may also be used as the exchange information type identification information 1840 shown in Figure 10B. This has the effect of making it easier to interpret the meaning of the data stored in the multi-level / binary transmission data section CTMDT and CT2DT (described later in Section 2.5 using Figure 14(d)), which conform to the C-format, by using this composite module type identification information CMTID, similar to the A-format and E-format. Furthermore, by comparing this module structure information MST, composite module structure information CMST, and composite module type identification information CMTID with the target node function expected from the chip-specific setting address ADRSIEEE conforming to IEEE802.15.4, the reading accuracy and reliability of the address information MADRS are improved. In other words, if the transmitting side mistakenly records different information in the storage area for the module structure information MST, composite module structure information CMST, and composite module type identification information CMTID, or if the receiving side mistakenly causes a bit shift (misplayback) of the playback information during playback, the error can be easily detected by the above comparison. (In this case, the receiving side sends an alarm notification to the transmitting side. As an example, in the communication access control information 1830 in Figure 14(d), set to

[0000] , and set the multi-level transmission data section CTMDT and the binary transmission data section CT2DT together to

[0011] . Details will be described later in Section 2.5.) Section 2.4 Internet Protocol Version 6 Layer Data Structure Section 2.4 of this book explains the data structure within communication information corresponding to Internet Protocol Version 6 Layer IPv6 using Figure 13. A major feature here is that it has areas for storing the IP address information SIPADRS and DIPADRS of the transmitting and receiving sides, each described in 16 bytes as shown in Figure 13(b). This IP address is assigned separately to every single communication module and composite module worldwide. Furthermore, the IP addresses assigned to each communication module and composite module worldwide will never overlap.Therefore, by enabling the communication of information including the IPv6 header IPv6HD (Figure 13(a)) within this embodiment of the system, if placed within the same domain 2_1122-2 (Figure 1), it becomes possible to communicate information with specific communication modules or specific composite modules from anywhere in the world. Within the IPv6 header IPv6HD, IP packet-related information IPPKT is stored in the first 8-byte area shown in Figure 13(b). Furthermore, as shown in Figure 13(c), this area consists of areas where the leading information SIPHD, IPv6 data / payload length information LIPv6DU, header type identification information NXHD that follows immediately after the IPv6 header, and remaining traversable node information HPLMT are stored, and they are arranged in the order described above. This IPv6 data / payload length information LIPv6DU indicates the data size of the IPv6 data / payload IPv6DU shown in Figure 11(d), and the area for storing this information has a size of 2 bytes. Next, the header type identification information NXHD that follows immediately after the IPv6 header will be explained. As shown in Figure 11(a), various headers are sequentially stored within a single physical layer frame PPDU. The header type identifier NXHD that follows immediately after the IPv6 header specifies the header type that follows immediately after the IPv6 header IPv6HD. Therefore, in the example shown in Figure 11(a), "TCP header TCPHD" is specified as the header type identifier NXHD that follows immediately after the IPv6 header. This header type identifier NXHD that follows immediately after the IPv6 header makes it possible to specify the method of setting the communication path on the communication network (on the internet). However, in this embodiment of the system, the information stored in the physical layer frame PPDU is not limited to that shown in Figure 11(a), and other information may be stored. For example, as another application example, another type of header information may be placed immediately after the IPv6 header IPv6HD. As a specific example, instead of TCP (Transmission Control Protocol) as shown in Figure 13, UDP (User Datagram Protocol) may be used, and a UDP header may be placed immediately after the IPv6 header IPv6HD. Furthermore, as a further application example, communication middleware data APLDT may be placed / stored directly immediately after the IPv6 header IPv6HD.For example, when using the E-format as the communication middleware data APLDT, the E-format header E-HD information is placed / stored at the beginning of the communication middleware data APLDT, as will be described later in Section 2.6 using Figure 15A(b). Therefore, in this case, the header type identification information NXHD that follows immediately after the IPv6 header specifies the information that identifies the "E-format header E-HD". In the information communication between servers n_1116-n and system controller α_1126 using the external network line 1788 shown in Figure 10A, and between system controller α_1126 and system controller β_1128 using the intra-domain network line 2082, direct information communication between the two is rare, as described in Figure 10A. In most cases, information is communicated via multiple relay points (relay nodes) along the external network line 1788 or the intra-domain network line 2082. The maximum number of relay points (relay nodes) allowed in the communication circuit between the transmitting node and the receiving node is indicated by the remaining number of passable nodes information HPLMT in Figure 13(c), which is a positive integer including zero. For example, when communicating information between the two, the transmitting node first sets the value of the remaining number of passable nodes information HPLMT. Then, each time this communication information passes through a relay point (relay node) in the communication circuit, the value of the remaining number of passable nodes information HPLMT is decremented by "1" (i.e., after passing through a relay point (relay node) once, the value of the remaining number of passable nodes information HPLMT after passing is updated by subtracting "1" from the value of the remaining number of passable nodes information HPLMT before passing). When the value of the remaining number of passable nodes information HPLMT becomes "0", information communication on the network is discarded. Incidentally, since the HPLMT information, which indicates the number of remaining traversable nodes, is written in 1 byte, it is possible to traverse up to 256 relay points (relay nodes). However, the more relay points (relay nodes) there are, the longer the communication time (time required for information transmission) from the sender to the receiver becomes. In contrast, for urgent information transmission, such as "alarm notifications," it is necessary to shorten the communication time.Considering the information transfer time at these relay points (relay nodes), the number of relay points (relay nodes) must be set to 100 or less, preferably 10 or less. Therefore, a characteristic of this embodiment of the system is that when using the external network line 1788 or the intra-domain network line 2082 for information communication, the setting value of the remaining number of traversable nodes information HPLMT on the transmitting side is set to 100 or less, preferably 10 or less. Naturally, the value of the remaining number of traversable nodes information HPLMT, which is reset (updated) at the relay points (relay nodes) that pass through the external network line 1788 or the intra-domain network line 2082 applied to this embodiment of the system, will also be 100 or less, preferably 10 or less. When the value of the remaining number of traversable nodes information HPLMT becomes small in this way, the routers placed at the relay points (relay nodes) along the external network line 1788 or the intra-domain network line 2082 automatically search for the shortest path to the receiving node, preventing interruption of information communication along the way. As a result of the above, the communication time between servers n_1116-n and system controller α_1126, or between system controller α_1126 and system controller β_1128, can be shortened, which has the effect of enabling rapid communication of urgent information such as "alarm notifications". On the other hand, as information communication forms using the same system network line 1782 in this embodiment system, information communication between system controller α_1126 and composite modules 1460 and 1470 as shown in Figure 10A, and information communication between system controller α_1126 and equipment 1260 as shown in Figure 16 are possible. Furthermore, if multiple sections 1142 constitute one system as shown in Figure 1, and for example, different PANs (Personal Area Networks) are used for each section 1142, network communication across multiple PANs becomes necessary. In this case, each time communication information crosses an adjacent different PAN, information transfer processing at a relay point (relay node) is required. Therefore, in this embodiment of the system, even when communicating information using the same network line 1782 within the same system, it is necessary to define the upper limit of relay points (relay nodes) that relay between the transmitting node and the receiving node.As shown in Figure 5, the composite module used in this embodiment of the system receives power from a built-in energy storage module (battery) 1554. Each time it performs a transfer of communication information as a relay point (relay node), the power stored in the energy storage module (battery) 1554 is consumed. Therefore, in information communication using the same system network line 1782, it is necessary to reduce the number of communication information transfers at relay points (relay nodes) as much as possible. Considering the relationship between the amount of power consumed for one transfer of communication information and the amount of energy stored in the energy storage module (battery) 1554, it is appropriate to set the number of intermediate relay points (relay nodes) to 30 or less, preferably 10 or less. Therefore, a key feature of this embodiment of the system is that when performing information communication on the same system network line 1782, the value of the HPLMT information (remaining number of traversable nodes) is set to 30 or less, preferably 10 or less, within the transmitting node. This prevents unnecessary waste of the energy stored in the energy storage module 1554 built into the composite module, and has the effect of maintaining stable network communication within the system of this embodiment over a long period of time. As shown in Figure 13(d), the SIPHD area of ​​the leading information within the IPv6 header IPv6HD consists of areas where the version information IPVRS, the communication class information IPCLS, and the communication type label information IPLBL are stored, and they are arranged in the order described above from the beginning. Here, the area where the version information IPVRS is stored consists of 4 bits and stores the value "6" (0110 in binary notation) as the Internet Protocol version number. Then, the communication type label information IPLBL is stored in an area consisting of 2.5 bytes, which is set immediately before the area where the IPv6 data / payload length information LIPv6DU is stored. Incidentally, when the combined data size of the communication middleware data APLDT and the extended data EXDT (Figure 11(b)) becomes large, a method of dividing them and distributing (storing) them within multiple physical layer frames PPDU for communication was explained in Section 2.3. At this point, we explained a method for storing sequentially incremented values ​​within the MAC layer sequence number MASQNM area of ​​the MAC layer header MACHD, so that the transmission order between multiple physical layer frames PPDU can be determined.In parallel with this, the system of this embodiment uses the above-mentioned communication type label information IPLBL to identify the entire communication middleware data APLDT (and extended data EXDT) when it is distributed and stored within multiple different IPv6 data / payload IPv6DU (see Figure 11(d)). The contents of this communication type label information IPLBL are initially set within the transmitting node (before network communication). Therefore, when a set of communication information contents of communication middleware data APLDT (and extended data EXDT) related to the same service provision is distributed (stored) within multiple IPv6 data / payload IPv6DU and communicated, the same label information is commonly stored in the storage area of ​​all corresponding communication type label information IPLBLs and communicated accordingly. In this embodiment of the system, information communication is possible between servers n_1116-n and system controller α_1126 using the external network line 1788 shown in Figure 10A, between system controller α_1126 and device 1250 using the internal network line 1782 shown in Figure 16, or between system controller α_1126 and system controller β_1128 using the internal network line 2082. By changing the content of the "communication type label information IPLBL" for each communication middleware data APLDT (and extended data EXDT) related to different service provision, it becomes possible to simultaneously communicate between multiple different communication middleware data APLDT (and extended data EXDT) related to different service provision. As a result, information regarding the provision of multiple different services can be communicated simultaneously between servers n_1116-n and system controller α_1126 (or between system controller α_1126 and device 1250, or between system controller α_1126 and system controller β_1128), enabling the simultaneous provision of a wide range of services to users. Furthermore, combining this "communication type label information IPLBL" with the MAC layer sequence number MASQNM information in the MAC layer header MACHD mentioned above produces another effect: the accuracy of verifying the reliability of communication information upon reception is further improved.Another application example is that the same information commonly stored in the "communication type label information IPLBL" for communication middleware data APLDT (and extension data EXDT) related to the provision of the same service may be used as the "encryption key". Incidentally, the communication class information IPCLS shown in Figure 13(d) is used to indicate the communication class during network communication. In particular, this communication class information IPCLS is intended to be used mainly in layers above the Internet Protocol Version 6 layer IPv6 shown in Figure 10A (i.e., communication middleware layers APL02, APL06 and extension application layer EXL06). The extended IEEE extension address EXEXADRS has already been explained in Section 2.3 using Figures 12B(d) and (e). As an example of applying this embodiment of the system, the following may be performed: ○ Eliminate the storage area for the extended IEEE extended address EXEXADRS within the IEEE extended addresses DEXADRS and SEXADRS on the receiving and transmitting sides. ○ Store only the information of the IEEE 802.15.4 compliant chip-specific setting address ADRSIEEE in the storage areas for the IEEE extended addresses DEXADRS and SEXADRS on the receiving and transmitting sides, respectively (i.e., the IEEE extended addresses DEXADRS and SEXADRS on the receiving and transmitting sides are matched to the IEEE 802.15.4 compliant chip-specific setting address ADRSIEEE, respectively). ○ Store the information of the IEEE 802.15.4 compliant chip-specific setting address ADRSIEEE in the storage area for the above-mentioned communication class information IPCLS (i.e., match the above-mentioned communication class information IPCLS to the IEEE 802.15.4 compliant chip-specific setting address ADRSIEEE). As already explained in Section 2.2 using Figure 10A, the functionality of Internet Protocol Layer 6 IPv6 is handled by the communication control unit 1700 within communication modules 1768, 1202-3, or 1660. The service provision functions corresponding to the communication middleware layers APL02 and APL06 and the extended application layer EXL06 are handled by the processors 1738 and 1230, or the interface unit 1710 within communication module 1660.Therefore, the TCP header prior to the IPv6 header (IPv6HD) in Figure 11, including the IPv6 header (IPv6HD), is processed within the communication control unit 1700 in communication modules 1768, 1202-3, or 1660. Similarly, the communication middleware data APLDT (and extended data EXDT) is processed within the interface unit 1710 in processors 1738, 1230, or 1660. When a physical layer frame PPDU is received, the communication class information IPCLS is processed first within the communication control unit 1700 in communication modules 1768, 1202-3, or 1660, and then the communication middleware data APLDT (and extended data EXDT) is passed to the interface unit 1710 in processors 1738, 1230, or 1660. Therefore, by storing the extended IEEE extended address EXEXADRS, as explained in Figure 12B(d)(e), within the IPv6 header IPv6HD (specifically in the communication class information IPCLS storage area), it becomes possible to prepare for the composite module in advance within processors 1738, 1230, or communication module 1660 before receiving the communication middleware data APLDT (and extended data EXDT). This results in an improvement in the processing speed of the system controller α_1126 for communication information transmitted from the composite module. Section 2.5 C-format data structure in the communication middleware layer The "C-format" used in this embodiment of the system is primarily intended for use within the communication middleware layer APL02, which communicates information to the composite modules 1460 and 1470 over the same system network line 1782, as explained in Section 2.1 using Figure 10A. Furthermore, as explained at the end of Section 2.1, this C-format may also be used for information communication between the system controller β_1128 in a different system β_1134 and the communication modules 1460 and 1470 in system α_1132. It may also be used for information communication with device 1250. Here, this C-format does not define the extended application layer EXL06 (see Figure 10A) and is used only within the communication middleware layer APL02.Furthermore, a key feature is the simplification of the C-format data structure to the greatest extent possible in order to minimize the processing burden on communication modules 1460 and 1470. Specifically, the data structure avoids information duplication as much as possible in the area from the physical layer header PHYHD to the TCP header TCPHD shown in Figure 11(a). (Details and their effects will be described later.) As a concrete example, instead of having the size information of the communication middleware data APLDT within the communication middleware data APLDT itself, the IPv6 data / payload length information LIPv6DU in the IPv6 header IPv6HD is used for this purpose. Here, this IPv6 data / payload length information LIPv6DU indicates the data size of the IPv6 data / payload IPv6DU in Figure 11(d). Since the data size of the TCP header TCPHD is predetermined, the data size of the communication middleware data APLDT is automatically determined from this IPv6 data / payload length information LIPv6DU, as shown in Figures 14(c) and 14(d). The basic data size of the communication middleware data APLDT in the C-format is specified as 1 byte. However, depending on the content of the communication information between the composite modules 1460 and 1470, the data size of the communication middleware data APLDT may be extended beyond 1 byte by adding extended transmission data CEDT to the end, as shown in Figure 14(d). As already explained in Section 2.1 using Figure 10B, in the A-format or E-format, the exchange access control information 1830 is included in the exchange information (table) 1810 used for information communication. In the C-format, this exchange access control information 1830 can also be stored in a "3-bit format". In particular, describing it in 3 bits (= describing 8 types of control information) has the effect of enabling the identification of various types of exchange access control information 1830. As a specific control method, when issuing a command 1852 as described in Case 1 of Figure 10B, the reset instruction

[0111] is set as the exchange access control information 1830.When responding with a result report (status) 1854, the exchange access control information 1830 is set to either a response response or report notification

[0010] or an acknowledgment notification

[0001] . In this embodiment of the system, the threshold (reference level when converting to a binary signal) used when converting a signal detected analogously by the sensor unit in the sensor / communication module 1460 into binary information for information communication can be set externally. When setting this threshold, the exchange access control information 1830 is set to the threshold level setting instruction

[0110] , corresponding to the command (command issuance) 1852 in Case 1 of Figure 10B. On the other hand, the exchange access control information 1830 is set to the response (data) request

[0011] , corresponding to the response request (request) 1872 in Case 2 of Figure 10B. Then, in the response 1874, the exchange access control information 1830 is set to the response response / report notification

[0010] . Furthermore, in response to the periodic / irregular reports 1894 that are voluntarily made from the composite modules 1460 and 1470 in Case 3 of Figure 10B, the response answer / report notification

[0010] is set as the exchange access control information 1830. When an abnormality is detected by the composite modules 1460 and 1470, an alarm notification is issued by setting

[0000] to the exchange access control information 1830 as the irregular report mentioned above. In addition, when the composite modules 1460 and 1470 voluntarily make periodic reports, the time interval (interval) for periodic reporting can be set from the system controller α_1126. In this case, the exchange access control information 1830 is set to

[0101] to give instructions regarding the report interval. For example, consider the smart meter 1124 in Figure 8A, which reports the amount of electricity used (public consumption) to the system controller α_1126, server n_1116-n, or wholesaler A_1102 at the specified time intervals. In this case, there are two methods: reporting the instantaneous value of the instantaneous amount of electricity used (public consumption) and reporting the accumulated value at predetermined intervals. To address this situation, the system in this embodiment sets the exchange access control information 1830 to

[0100] to give instructions regarding the data storage interval.Here, if

[0000] is specified in the area for storing transmission data, which is set immediately after the storage area for the exchange access control information 1830, the composite module reports instantaneous usage (usage of public consumption materials such as electricity) at specified time intervals. As shown in Figure 14(d), binary or multi-level transmission data is transmitted using the storage area for the 4-bit multi-level transmission data section CTMDT and the 1-bit binary transmission data section CT2DT, which are set immediately after the storage area for the exchange access control information 1830. A distinctive feature here is that there is no special information storage area to indicate whether the transmission data is binary or multi-level; binary / multi-level identification is performed by the transmission data itself. That is, if the transmission data is binary, all values ​​in the 4-bit multi-level transmission data section CTMDT are set to "0" (i.e.,

[0000] ). Here, if the ON state or OK state is indicated, [1] is set in the binary transmission data section CT2DT. Furthermore, if the state is OFF or NG (No), set the binary transmission data section CT2DT to [0]. On the other hand, the method for setting the transmission data when an abnormal situation occurs in the composite modules 1460 and 1470 and an alarm is notified to the system controller α_1126 (this exchange access control information 1830 is set to

[0000] ) will be explained. In this case, set the multi-level transmission data section CTMDT to

[0000] . If the abnormal situation in the composite modules 1460 and 1470 is a sensor detection abnormality or a drive system abnormality in the drive unit (uncontrollable / difficult to control), set the binary transmission data section CT2DT to [1]. Incidentally, as shown in Figure 5, since the sensor / communication module 1460 or the drive / communication module has a built-in energy storage module (battery) 1554, there is always a risk of depletion of the stored energy (running out of charge). Therefore, when the remaining charge in this energy storage module (battery) 1554 becomes low, the binary transmission data unit CT2DT is set to [0] to notify the system controller α_1126 of the decrease in battery charge. On the other hand, when transmitting information as multi-value data, the multi-value is represented by a 5-bit signal that combines the multi-value transmission data unit CTMDT and the binary transmission data unit CT2DT.For example, when storing multi-level information ranging from 0% to 100% as transmission data, the multi-level information from 0% to 100% is converted into 30 divided values ​​and represented as values ​​from

[0010] (=0%) to

[11111] (=100%). However, this embodiment of the system is not limited to this, and multi-level information may be represented in other ways by combining the multi-level transmission data section CTMDT and the binary transmission data section CT2DT. Furthermore, for example, in the communication of high-precision sense information such as temperature and humidity detection or illuminance changes of lighting equipment, where the 30 divided values ​​are insufficient for representation, or in the high-precision setting of thresholds or control values, an area for storing extended transmission data CEDT can be added immediately after the area for storing the binary transmission data section CT2DT to improve the accuracy of representing multi-level information. The number of bits used to represent the multi-level information in this case is indicated by the IPv6 data / payload length information LIPv6DU in the IPv6 header IPv6HD, as described above. In this way, by not having a specific binary / multi-value identifier and instead relying on the content of the transmitted data for binary / multi-value identification, the data size of the communication middleware data APLDT can be reduced. As a result, information communication congestion on the same system network line 1782 is alleviated, and processing within the composite modules 1460 and 1470 (particularly within the interface section 1710 shown in Figure 10A) is simplified, and the cost of the composite modules 1460 and 1470 can be reduced. Furthermore, there is no area to store information indicating the meaning of the multi-value transmitted data within the C-format compliant communication middleware data APLDT. Instead, a characteristic feature of this embodiment of the system is that it utilizes the chip-specific setting address ADRSIEEE information compliant with IEEE802.15.4 shown in Figure 12B(d) as information indicating the meaning of the multi-value transmitted data. As explained in Section 2.3, the issuing authority for the IEEE 802.15.4-compliant chip-specific configuration address ADRSIEEE is aware of the functions and performance of the composite modules 1460 and 1470 that correspond to the above address. By making this information public on the internet, the meaning of the transmitted data corresponding to the composite modules that correspond to the IEEE 802.15.4-compliant chip-specific configuration address ADRSIEEE can be understood.Furthermore, from the explanation in Section 2.3 using Figure 12B(e) and the explanation in Section 2.4 using Figure 13(d), it can be seen that the composite module type identification information CMTID can be stored in the IEEE extended addresses DEXADRS and SEXADRS on the receiving and transmitting sides within the MAC layer header MACHD, or in the communication class information IPCLS within the IPv6 header IPv6HD. Therefore, by combining the aforementioned IEEE 802.15.4 compliant chip-specific configuration address ADRSIEEE with this composite module type identification information CMTID, the meaning and interpretation method of the transmitted data CTMDT, CT2DT, and CEDT (which are, for example, expressed in multi-level notation) communicated between composite modules 1460 and 1470 can be accurately understood. In this way, the composite module type identification information CMTID can be used to understand the meaning and interpretation of the transmitted data CTMDT, CT2DT, and CEDT, and is related to the type identification information 1840 (see Figure 10B) of the exchange information corresponding to each composite module 1460 and 1470. In other words, the above composite module type identification information CMTID is used in the A-format described later in Section 2.7.

[0258]

[0259]

[0260]

[0261]

[0262]

[0263]

[0264]

[0265]

[0266]

[0267]

[0268]

[0269]

[0270]

[0271]

[0272]

[0273] It can be used for the same purpose as the number attribute within Element (see Figure 15B(b)). On the other hand, this exchange information type identification information 1840 corresponds to the exchange information type identification information EPC (see the explanation in Section 2.6 using Figure 15A(f)) in the E-format. Thus, in both the E-format and A-format, the exchange information type identification information 1840 in Figure 10B is included in the communication middleware data APLDT. Compared to the E-format and A-format described above, the C-format has a major feature in that it can use information in the MAC layer header MACHD (composite module type identification information CMTID in Figure 12B(e)) or information in the IPv6 header IPv6HD (information in the communication class information in Figure 13(d) as explained in Section 2.4) as information related to the exchange information type identification information 1840 in Figure 10B. As already explained in Section 2.2, when receiving, communication information is processed sequentially from the layers located on the lower side of Figure 10A. Therefore, if the type of composite module can be known in advance, not only at the functional level of the Media Access Layer MAC02 or the Internet Protocol Version 6 Layer IPv6, which are located relatively low in the network, it becomes possible to prepare for C-format compatibility within the interface unit 1710 before the communication middleware data APLDT is passed from the communication control unit 1700 in the communication module 1660 (shown in Figure 10A) to the interface unit 1710. This allows for faster processing of communication information on the receiving side. Furthermore, as mentioned above, the C-format utilizes information defined at other layers to minimize the data size of the communication middleware data APLDT. This reduces information communication congestion on the same system network line 1782, simplifies processing within the composite modules 1460 and 1470 (especially within the interface unit 1710 shown in Figure 10A), and reduces the cost of the composite modules 1460 and 1470. Next, we will show a specific example of communication middleware data APLDT in C-format according to the method described above.For example, when the system controller α_1126 issues a "stop operation" command (issue) 1852 (Figure 10B) to the drive / communication module 1470, the above communication access control information 1830 is set to "

[0111] Reset instruction," the multi-level transmission data section CTMDT is set to "

[0000] Binary data specification," and the binary transmission data section CT2DT is set to "[0] OFF specification." Also, when the sensor / communication module 1460 notifies (reports) the system controller α_1126 that, for example, the current usage amount of public consumer goods is 50%, the above communication access control information 1830 is set to "

[0010] Report notification," and the 5-bit area combining the multi-level transmission data section CTMDT and the binary transmission data section CT2DT is set to "

[10001] 50%." Another specific data example is shown below. As described later in Section 4.3, while large adults with thick fingers can achieve stable user input even with low sensitivity on touchpads and capacitive buttons, children and women with thin fingers may not respond unless the sensitivity of the touchpad or capacitive buttons is increased. To address this, an example is shown in which the system controller α_1126 sets the sensitivity of the sensor / communication module 1460 corresponding to the touchpad or capacitive button after estimating / determining the user state (finger thickness) according to Section 4.3. In this case, the above communication access control information 1830 is set to "

[0110] Threshold level setting instruction". Let's consider the case where the sensitivity of the touchpad or capacitive button is increased from 25% to 73%. Then, in the 5-bit area combining the multi-level transmission data section CTMDT and the binary transmission data section CT2DT,

[11000] corresponding to 73% is specified. In the above embodiment, the timing of communication for binary information such as ON / OFF and the timing of communication for multi-value information such as state settings are separated, and the presence or absence of

[0000] in the multi-value transmission data section CTMDT is used to distinguish between binary and multi-value communication information. However, in other embodiments, binary data such as ON / OFF and multi-value data such as state settings may be communicated together at the same time. In this case, one bit of binary information may be set in the binary transmission data section CT2DT, and four bits of multi-value information may be set in the multi-value transmission data section CTMDT.In this way, by communicating binary data and multi-value data such as state settings at the same time, for example, by specifying a state setting value (such as a set temperature) at the same time as starting operation, the frequency of information communication between the system controller α_1126 and the composite modules 1460 and 1470 can be reduced, resulting in the effect of alleviating communication congestion within the same system network line 1782 (Figure 10A). Incidentally, it has already been explained that the communication accuracy and communication stability can be improved by combining the IEEE802.15.4 compliant chip-specific setting address ADRSIEEE with this composite module type identification information CMTID. Furthermore, if an error occurs in the system controller α_1126 and it mistakes the function of the composite modules 1460 and 1470 it is communicating with, this error can be detected by comparing the information between the two. If the composite modules 1460 and 1470 detect this error in the system controller α_1126, this embodiment of the system supports a function that allows the composite modules 1460 and 1470 to notify the system controller α_1126 of the error. In this case, the communication access control information 1830 in Figure 14(d) is set to "

[0000] Alarm notification". Then, "

[0011] " is set in the 5-bit area combining the multi-level transmission data section CTMDT and the binary transmission data section CT2DT to notify of the misrecognition of the target. In this way, the system of this embodiment supports the function of notifying errors that occur in the system controller α_1126 from the composite modules 1460, 1470 or the device 1250, which has the effect of improving the stability and reliability of information communication on the network line 1782 within the same system. Section 2.6 Data structure of E-format in the communication middleware layer The "E-format" used in the system of this embodiment is mainly intended for use in the communication middleware layer APL06 that communicates information to the device 1250 and the server n_1116-n, as explained in Section 2.1 using Figure 16. Furthermore, it may also be used for information communication between different system controllers α_1126 and β_1128, or for information communication with composite modules 1460 and 1470.As already explained in Section 2.1 using Figure 10B, the E-format basically performs information communication through the exchange of exchange information (table) 1810 between the transmitting node and the receiving node. Therefore, this exchange information (table) 1810 (or a part thereof) is stored in the IPv6 data / payload IPv6DU as part of the communication middleware data APLDT shown in Figure 11(a). As will be described later in Section 2.7, the A-format is characterized by being written in a broad text format. In comparison, the E-format is characterized by storing corresponding information in a predetermined area using a configuration code. Therefore, the E-format is defined as a format that "stores configuration codes in a predetermined area within the area of ​​the communication middleware data APLDT". Accordingly, in this embodiment of the system, any format that sequentially stores configuration codes in a predetermined area is included in the E-format. At the beginning of the communication middleware layer data APLDT based on the E-format, the E-format header E-HD shown in Figure 15A(b) is stored in a 2-byte area. The value of this E-format header E-HD is set to [1081h] ("h" represents the hexadecimal value, which in binary representation is [0001000010000001]). The next two-byte area stores the identification information TID for associating the request transmission and the response reception. This identification information TID for associating the request transmission and the response reception is a parameter used by the request sender to associate the response request and the received response when the response is received. (The sequence of response 1874 to this request 1872 corresponds to the sequence shown in Case 2 of Figure 10B.) The code stored in this area can be arbitrarily specified by the request sender node. When the receiving node of the request sends its response, it stores the same code in this area as the code set by the previous request sender node.Then, based on the degree of agreement of the identification information TID used to associate the request transmission and the response reception, it is determined whether the received information indicates a response to the previous response request. The E-format data E-DT stored in the next area shown in Figure 15A(b) corresponds to the exchange information 1810 explained in Section 2.1 using Figure 10B. As shown in Figure 15A(c), the E-format data E-DT consists of 3 bytes of transmitting device identification information SEOJ, 3 bytes of receiving device identification information DEOJ, 1 byte of communication access control information ESV, and control / processing related information CM1, arranged in the order described above. Here, the 1 byte of communication access control information ESV corresponds to the communication access control information 1830 explained in Section 2.1 using Figure 10B. As shown in Figure 15A(d), both the transmitting device identification information SEOJ and the receiving device identification information DEOJ consist of a 1-byte device type group code DTGC, a 1-byte device type code DTC, and a 1-byte device identification code within the same type DIDC, arranged in the order described above. The device type group code DTGC represents a group of device types, indicating which group the target device belongs to, for example, a sensor-related device group, an air conditioning-related device group, a housing / equipment-related device group, a cooking / household appliance-related device group, etc. The next device type code DTC represents a device type, for example, a television or an air conditioner. When multiple different devices 1250 belonging to the same device type are installed within the same system α_1132 (for example, when multiple air conditioners are installed in one house), the aforementioned device identification code within the same type DIDC is set to identify each device 1250. For example, if we consider an air conditioner as an example of device 1250, there are setting states for multiple items such as "set temperature," "set airflow," "set airflow direction," and "set timer duration (automatic ON / automatic OFF)," and it is possible to change the settings (state change control) for multiple items simultaneously. Therefore, in the exchange information (table) 1810 shown in Figure 10B, even for a single device, "states related to multiple items" or "instructions for simultaneous setting changes related to multiple items (state change control information)" are defined, and this information can be described in a list format.Therefore, as shown in Figure 15A(e), the control / processing related information in Figure 15A(c) allows for simultaneous collection of status information and status change control for multiple items. The number of status information items to be collected simultaneously, or the number of items for which status change control (setting change) is performed simultaneously, is described in one byte as the control / processing number NCM. The number of items set in the control / processing number NCM corresponds to the number of control / processing information CM-1 to n from the first to the nth time, which are arranged in the order described above. Each control / processing information CM-1 to n consists of a one-byte exchange information type identification information EPC, a one-byte individual exchange information data size PDC, and individual exchange information EDT, as shown in Figure 15A(f), and is arranged in the order described above. The "status information to be collected," "status information to be answered," or "status change (setting change) control information" corresponding to each item of each device 1250 is stored as the individual exchange information EDT. The data size information for each individual exchange information EDT is stored as the individual exchange information data size PDC. Furthermore, depending on the type of equipment 1250 (i.e., according to the contents of the equipment type code DTC mentioned above), the contents of the items representing the status and the contents of the items subject to status change control (setting change) differ. Therefore, in the E-format, the items of information to be collected for status and the information representation format, or the items to be controlled for status change (setting change) and the representation format of the control information are predetermined for each type of equipment 1250 (content of the equipment type code DTC), and templates and item codes (template codes) according to the representation format for each item are prepared in advance. The item codes set for each type of equipment 1250 (content of the equipment type code DTC) are stored as the exchange information type identification information EPC. This exchange information type identification information EPC corresponds to the exchange information type identification information 1840 shown in Figure 10B. Here, taking the case of changing the settings (status change control) of a household air conditioner controlled from the system controller α_1126 as an example, we will explain the information in the E-format data E-DT corresponding to the exchange information (table) 1810. By the way, the command (issuance of a command) for changing settings (state change control) in E-format corresponds to the "write request" explained in Section 2.1.Therefore, the communication access control information ESV(1830) in Figure 15A(c) is set to [60h] (=no response required) or [61h] (=response required). (For reference, the setting codes for the communication access control information ESV(1830) are [62h] for "read request", [73h] for "notification", and [72h] for "read response".) The equipment type group code DTGC for the household air conditioner is [01h], which means the air conditioning related equipment group. The equipment type code DTC is [30h]. When this is assigned to the first air conditioner in system α_1132, the same model type equipment identification code DIDC is [01h]. Therefore, when the system controller α_1126 issues a state change control command 1852 (corresponding to case 1 in Figure 10B) to this household air conditioner, the identification information for the receiving equipment in Figure 15A(c) is [013001h]. When the system controller α_1126 controls the corresponding air conditioner to change its operating state, the exchange information type identification information EPC is [80h], the data size of the individual exchange information is [01h] (=1 byte), and the individual exchange information EDT is [30h]. Therefore, the initial control / processing information CM-1, which combines these pieces of information, can be represented as [800130h]. Next, when the nth control / processing is to change the set temperature to 26°C, the exchange information type identification information EPC is [B3h], the data size of the individual exchange information is [01h] (=1 byte), and the individual exchange information EDT is [1Ah], which means 26°C. Therefore, the nth control / processing information CM-n, which combines these pieces of information, can be represented as [B3011A]. Section 2.7 Data Structure of A-Format in Communication Middleware Layer The "A-Format" used in this embodiment of the system, as explained in Section 2.1 with reference to Figure 16, is primarily intended for use within the communication middleware layer APL06, which is used for information communication with devices 1250 and servers n_1116-n. However, it may also be used for information communication between different system controllers α_1126 and β_1128, or for information communication with composite modules 1460 and 1470.As already explained in Section 2.1 using Figure 10B, the A-format basically communicates information through the exchange of exchange information (table) 1810 between the sending node and the receiving node. Therefore, this exchange information (table) 1810 (or a part thereof) is stored in the IPv6 data / payload IPv6DU as part of the communication middleware data APLDT shown in Figure 11(a). In the A-format, the communication middleware data APLDT may be written in XML (Extensible Markup Language) format, as shown in Figure 15B as an example. In this specification, methods of describing content in text-based formats such as XML and HTML (Hypertext Markup Language) are referred to as "broad text formats." For example, HTML always contains tags in its description. However, in the context of "broad text formats," the above tag descriptions are not necessarily required; any description in a broad text format is included. Therefore, for example, Java applets, Java scripts, or programs in C language are also included in the broad text formats. By describing the communication middleware data APLDT in a broad text format in this way, it is possible to ensure the versatility and extensibility of the communication middleware data APLDT. Therefore, the A-format in this embodiment of the system is defined as "a format described in a broad text format as communication information related to the communication middleware layer APL." And all formats described in the broad text format are included in this A-format. And the exchange information (table) 1810, which is composed in the table format of Figure 10B, is " in Figure 15B(b). Element area”( from (Up to this range) may be considered appropriate.

[0274] Furthermore, in A-format, the above <tdl>Element may be set here. (The above <tdl>This refers to the transferring data language. Also, as shown in Figure 15B(b), <tdl>The creation date of the table can also be described using the `date` attribute as an attribute of the Element. In the description in Figure 15B(b), the creation date of the table is "December 25, 2014".

[0275] And as shown in Figure 15B(b), the above< / tdl> < / tdl> < / tdl> The Root Element is the parent element of the Element. The number attribute or name attribute within an Element corresponds to the exchange information type identification information 1840 shown in Figure 10B. However, in the communication middleware data APLDT written in A-format, there is no place to display information corresponding to the device type group code DTGC or device type code DTC, as explained in Section 2.6 for the E-format. Instead, a table template that pre-defines the items of information to be collected and the information representation format, or the items to be controlled (settings changed) for device 1250 status changes and the representation format of the control information, is set up in detail for each corresponding device type. And for each of these table templates set up in detail for each device type, a table number and its table name are specified. As an example, as written in Figure 15B(b) as 'number="02"', the corresponding table template number can also be directly specified by the number specified in the number attribute.

[0276]

[0277] By describing it within Element, it becomes possible to automatically describe the communication middleware data APLDT in accordance with the table template. Furthermore, in this embodiment of the system, other descriptive statements may be associated with the above-mentioned exchange information type identification information 1840, which can be used to select the standard template used for the information exchange table. Also, similar to the method of associating a table template according to the type of device 1250 by specifying a numerical value with the above-mentioned number attribute, the composite module type identification information CMTID in Figure 12B(e) may be used to call the standard information exchange template according to the type of composite module 1460, 1470 (see Section 2.5 for details). Incidentally, as an example of describing communication information in the communication middleware data APLDT compliant with A-format, Figure 15B(b) shows an example of a description that notifies the service provider B_1112-2 (server n_1116-n) that provides the power supply service of the amount of power used that is periodically accumulated in the smart meter 1124 in Figure 1 as the "accumulated current value (Ampere)". As shown in Figure 1, this smart meter 1124 is also connected to the system controller α_1126 and wholesaler A1102 via a network connection, so it may also transmit the above communication information to the system controller α_1126 and wholesaler A1102. On the other hand, since the voltage value supplied is predetermined depending on the location where this smart meter 1124 is installed (i.e., corresponding to general households, buildings, or factories), it notifies the cumulative current value instead of the cumulative power amount. Furthermore, not limited to the description example in Figure 15B(b), information written in "broad text format" may be used for information communication with any device 1250 or any composite module 1460, 1470. As an example of notifying the cumulative current value shown in Figure 15B(b), in A-format, a standard table (table template) with "table number 2" and table template name "Device Nameplate Table" may be used as a template. Also, in A-format, Table may be abbreviated as "TBL".

[0278] <packedrecord>The same word is used in the number attribute within an Element, written as 'name="E_ELECTRIC_DEVICE_RCD"'.

[0279] As already explained in Section 2.1 using Figure 10B, both the A-format and the E-format described in Section 2.6 include communication access control information 1830 within the exchange information (table) 1810. This communication access control information 1830 is then used as follows:< / packedrecord> The number attribute within the Element is written as 'number="02"', and the name attribute is written as 'name="DEVICE_NAMEPLATE_TBL'. As already explained in Section 1.7, there are smart meters 1124 that notify the usage status of various public consumption goods, not limited to "electricity usage", but also "gas usage", "water usage", "sewage discharge", etc. In contrast, the example description in Figure 15B(b) means "measuring electricity usage", and the type attribute is written as 'type="E_ELECTRIC_DEVICE_RCD"'. By the way, the above "RCD" is the Record of packedRecord. This means that, as already explained in Section 2.2, the communication middleware layer data APDLT (or a portion thereof) described in Figure 15B(b) is packed into the MAC layer data / payload MSDU and communicated. Therefore, the expression "packedRecord" is used to mean "packing (or a portion thereof) of the above communication middleware layer data APDLT into the physical layer frame PPDU and communicating it." <set>The accessibility attribute within the Element can be used to specify the following: READWRITE, READONLY, or WRITEONLY. Here, READ means an instruction to read the state of the receiving node (e.g., device 1250 or composite modules 1460, 1470, etc.) and have it respond with the read information (or notify sense information), corresponding to a "read request" in E-format. WRITE means an instruction to the receiving node to provide information or change its state, corresponding to a "notification," "read response," or "write request" in E-format. READWRITE is used to instruct the receiving node to follow the sequence correspondence of response request 1872 / response 1874 as shown in Figure 10B Case 2. However, in this embodiment, other descriptive statements may also be used to correspond to the above communication access control information 1830. In the example shown in Figure 15B(b), the smart meter 1124 measures "cumulative current value (Ampere)" and notifies the receiving node (for example, server n_1116-n, controller α_1126, or wholesaler A1102), so accessibility="WRITEONLY" is specified.

[0280] Furthermore, in the embodiment shown in Figure 15B(b), the element refers to "individual items such as sense target information, detection target state information, or state information that is subject to control (setting change)." Therefore, the information content specified in the exchange information type identification information 1840 in Figure 10B (< / set> Within the Element or as described later <element>The settings are described within the Element.

[0281] By the way, in the table template that is pre-configured with "table number 2", the table template defined as "type="E_ELECTRIC_DEVICE_RCD"" is <packedrecord>Within Element, individual items such as "E_KH" (periodically accumulated power), "E_KT" (test pulse output), "E_INPUT_SCALAR" (defines the unit of communication information and indicates how much the value input from the sensor is compressed to), "E_ELEMENT" (smart meter local number), "E_VOLTS" (instantaneous voltage value / allows real-time monitoring of voltage fluctuations in the power transmission system), and "E_AMPS" (periodically accumulated current value) are pre-configured. In the example shown in Figure 15B(b), only "E_KH" and "E_AMPS" are used. <element>Defined using Element.

[0282] First, specify "E_KH" in the name attribute. <element>Element declares that "this communication information will notify the amount of power that has been periodically accumulated." According to the standard, <element name="E_KH">The meaning of "E_KH" can be understood from this information alone. However, the contents of exchange information (table) 1810 can be understood without referring to the standard. <description>An Element is set. One of the characteristics of the A-format is that it has the "function of being able to provide supplementary explanations using broad text" within the A-format, which can be written in a broad text format. As a result, the content can be understood without referring to the standard document, which has the effect of making it easier for the receiving node to understand the exchange information (table) 1810.

[0283] As an example of A-format, <set>Numerical values ​​are set using Element. However, numerical values ​​can be set using other methods as well. <set>Before using the Element, specify "E_KH" in the name attribute. <element>Specify the type of "E_AMPS_RCD" within the element (<element name="E_AMPS" type="E_AMPS_RCD"), and clarify that "the item of 'periodically integrated current value' is packed and recorded in the MAC layer data / payload MSDU and notified". Then, using the same name of "E_AMPS_RCD" <set>This defines an Element.

[0284] The "periodic cumulative current value" measured by smart meter 1124 is, <enum>This is set in the value attribute within the Element (enum stands for Electrical numerator). (Here, smart meter 1124 automatically substitutes the measured value into the $$$$ part of value="$$$$".) Also, the variable name "E_AMPS" that represents the value set here is <enumerator>It is specified in the `name` attribute within the Element.

[0285] By the way, as a "supplementary explanation function" within the A-format, <description>I explained the Element. However, you can also use the label attribute or text attribute to provide supplementary explanations, not limited to the above.

[0286] Section 2.8 Address Table Used in This Embodiment System and Examples of Its Application From the explanations in Sections 2.3 to 2.7 above, it can be seen that different addresses are duplicated and set for the same module at each hierarchical level. For example, Figure 23 shows an example of the data structure in the address table that lists the various addresses that can be set for the sensor module 1260-1 and drive module 1270-1 in Figure 8A, or the drive / communication module 1470-2 and sensor / communication module 1460-5 in Figure 8B. In addition to the methods described in Section 2.8, this address table may also be used in the way described in Section 4.2.

[0287] In Figure 23, the various addresses that are duplicated in the drive / communication module 1470-2 and the sensor / communication module 1460-5 in Figure 8B are grouped together in the same vertical column. Similarly, the various addresses that are duplicated in the sensor module 1260-1 and the drive module 1270-1 built into the device 1250-1 in Figure 8A are also grouped together in the same vertical column. The IEEE extended address EXADRS, which is included in one of the address items in the address table in Figure 23, is assigned to the communication module chip 1202-4 (see Section 2.3). Therefore, the IEEE extended address EXADRS corresponding to the sensor module 1260-1 and the drive module 1270-1 in Figure 23 is set to the address related to the communication module chip 1202-4 built into the same device 1250-1.

[0288] In the address table shown in Figure 23, the Media Access Layer MAC02 has the IEEE Extended Address EXADRS individually configured, as explained in Section 2.3. Next, the Internet Protocol Version 6 Layer IPv6 has the IP Address IPADRS (Sender IP Address Information SIPADRS / Receiver IP Address Information DIPADRS) individually configured, as explained in Section 2.4. Meanwhile, the Communication Middleware Layer APL06 has the Device Type Code DIDC configured in accordance with ...

Claims

1. A first system controller and a second system controller are located in the first local network and the second local network, respectively. Servers located on a wide-area network, The first local network, the second local network and the wide area network The server, the first system controller, and the second system controller are connected via the network. A status management system using an electronic unit that can communicate with a controller, The first system controller and the second system controller are, Each local area network sets up multiple sections, It manages the electronic units within each section. The server, the first system controller, and the second system controller are: Each unit is equipped with a memory section, and each memory section contains shared address information for specifying the electronic unit and communicating with it. The address information includes at least the sender's IP address, the receiver's IP address, identification information of the section where the receiver electronic unit is located, the equipment type code of the equipment including the receiver electronic unit, and the equipment identification code within the same type. The first system controller and / or the second system controller are Means for collecting sensor information and / or current setting status information from each of the aforementioned address information electronic units, The system comprises means for estimating / determining the state of the electronic unit within the system based on the collected information and / or current setting state information, A status management system using electronic units, wherein the first system controller and the second system controller each manage multiple electronic units located within the area they manage, check the attribute information sent from each of the multiple electronic units, and provide means for notifying a predetermined organization if an impossible combination of attribute information exists.

2. The first system controller or the second system controller is installed in the patient's room, and the condition management system uses the electronic unit according to claim 1.

3. A status management system using electronic units according to claim 1, wherein the plurality of electronic units include those that can be moved from under the control of the first system controller to under the control of the second system controller.

4. A first system controller and a second system controller are located in the first local network and the second local network, respectively. Servers located on a wide-area network, The first local network, the second local network and the wide area network The server, the first system controller, and the second system controller are connected via the network. A status management method using an electronic unit that can communicate with a controller, The first system controller and the second system controller are, Each local area network sets up multiple sections, It manages the electronic units within each section. The server, the first system controller, and the second system controller are: Each unit is equipped with a memory section, and each memory section is configured to communicate with the electronic unit. It contains shared address information for use, The address information includes at least the sender's IP address, the receiver's IP address, and the receiver's IP address. Identification information of the section in which the transmitting electronic unit is located, including the receiving electronic unit. This includes the equipment type code of the equipment and the equipment identification code within the same type. The first system controller and / or the second system controller are Sensor information and / or current setting status information are collected from the electronic units registered in each of the aforementioned address information. Based on the collected information and / or current setting status information, the state of the electronic unit within the system is estimated / determined. Furthermore, the first and second system controllers each manage multiple electronic units located within the area they control, check the attribute information sent from each of the multiple electronic units, and notify a designated organization if an impossible combination of attribute information exists, in a method of managing the status using electronic units.

5. A first system controller and a second system controller are located in the first local network and the second local network, respectively. Servers located on a wide-area network, A service provision system using electronic units that enables communication between the server, the first system controller, and the second system controller via the first local network, the second local network, and the wide area network, The first system controller and the second system controller are, Each local area network sets up multiple sections, It manages the electronic units within each section. The server, the first system controller, and the second system controller are: Each unit is equipped with a memory section, and each memory section contains shared address information for specifying the electronic unit and communicating with it. The address information includes at least the sender's IP address, the receiver's IP address, identification information of the section where the receiver electronic unit is located, and the receiver electronic unit itself. This includes the equipment type code of the equipment and the equipment identification code within the same type. The first system controller and / or the second system controller are Means for collecting sensor information and / or current setting status information from each of the aforementioned address information electronic units, Means for estimating / determining the state within the system in which the electronic unit is located, based on the collected information and / or current setting status information, Equipped with, A service provision system using electronic units, wherein the first system controller and the second system controller each manage multiple electronic units located within the area they manage, check the attribute information sent from each of the multiple electronic units, and provide means for notifying a predetermined organization if an impossible combination of attribute information exists.

Images