Method for authorizing couplings between devices in a capability addressable network

Description: TECHNICAL FIELD [Detailed description of the invention]

Capability Addressable method for authorizing connections between devices in a network Cross-reference for related applications This application is the same as the one filed on October 15, 1996, which was assigned to the same assignee as this case. Time continuation application No. 08 / 729,207; Simultaneous continuation of application on December 9, 1996 Application No. 08 / 762,127; Simultaneous Continuation Application No. 0 filed on December 16, 1996 8 / 766,652; Simultaneous Continuation Application No. 08/7, filed December 26, 1996 No. 74,977; and Simultaneous Continuation Application No. 08/794 filed February 3, 1997 , 312; related. Technical field of invention The present invention generally relates to a data communication network. More specifically, the present invention is a node. · For peer-to-peer networks where addressing can be dynamically configured .. More specifically, the present invention is installed in a network in which capability addresses can be specified. Allow connection between on-premises services and / or access to services on the device Regarding the method to allow To. Background of the invention Capability Addressable network devices perform meaningful communication between peers Finally, a personal area network is formed. Networking Naturally when the device enters proximity, without any explicit action by the user Is done. Networking occurs between unpredictable devices. That is, any device It is not possible to predict which device will be networked at a particular moment .. Capability Addressable Many network functions can be carried by humans Can be incorporated into electronic devices, people may travel all day long. For example, pa -The person who carries the first device connected to the Sonal Area Network is the second Once within the range of unconnected devices, the second device is the personal personal area network. When connected to the network and the person leaves the range of the second device, the second device separates again Will be done. Such highly fluid network connections open many times in a day And separated. Capability Addressable network equipment has a wide range of requirements in terms of confidentiality Have. In some cases, it may be necessary to limit the use of the device to authorized bodies. Also, in some cases, the resources provided by the device can be transferred between any devices in close proximity. It is free to share and in some cases should be shared. For example, one Fiss usually has a single printer intended to be shared by any passerby. Have. Printers and other devices have little or no clear action by the user. This sharing should be dealt with without causing any problems. On the other hand, an individual is digital We may carry out financial processing from the wallet, and for that purpose, we will deal with the resources. Access must be certified as private. The connection mechanism is Fully sensitive system at one end of the spectrum, at the other end of the spectrum It must support a system that can be easily shared. The difficult thing is that spec To prepare a low-interactive mechanism for position-fixing to any point in the torr And. The problem is that the structure of the personal area network is not static. It gets complicated when you know what you are doing. That is, as the device moves in and out of range The structure changes fluidly. Outline of the invention Capability Addressable Equipment that provides capability before the network device is connected The device confirms that the connection is authorized. That the connection is authorized between devices The bond is activated through the key to allow. Authorized connections between devices Bonding the process to open The devices that have passed through this process are said to have been combined. That is, it is connected The device is combined. The bond is the pre-approval step for the connection stored by the device. It is a rule. One device may request service from another. Such a device Called the requester. One device servicing another There is. Such a device is called a provider. Providing equipment requires Provide services as requested by the side device. The requesting device is given to the providing device Use the service. One device can be the requesting device or the providing device for the service .. However, some devices can only be provided side devices, and request side devices. In some cases, it can only be placed. On the providing device as a result of the coupling being opened between the requesting device and the providing device Will unlock certain abilities. The requesting device is unlocked by the join key. Restricted on the use of services on the provider device that is excluded. The connection authorization between the requesting device and the providing device is the bond key that was successfully decrypted. Given based on a comparison of key). In one embodiment the binding key is a single entity Logically explained as, but multiple such as RSA public key encryption system Some have parts. Well-known to those skilled in the art of computer-based encryption and decryption Key combining many different technologies Can be used to express and decipher. Each capability network address can be specified at the time of manufacture. Device identifier or device for device A unique identifier called an ID is encoded. In reality, this name has a given length It is a unique string of bits that it has. The device name is the device's own serial number It may be the manufacturer's unique identifier linked to the member. This is Isane It is called the "address", but it is the format in which the Ethernet board is named. .. A brief description of the drawing More complete of the invention by reference to the detailed description and claims in connection with the drawings. You will get a good understanding. Similar reference numbers refer to similar items throughout the drawing. FIG. 1 shows the wireless peer-to-peer data communication network constructed by the present invention. It is a layout diagram which illustrates the relationship between various peers. Figure 2 is a block diagram of the hardware contained in the peer. Figure 3 is a list of equipment circuits included in the hardware shown in Figure 2. .. Figure 4 shows the list of gateways included in the hardware shown in Figure 2. is there. Figure 5 is included in the hardware shown in Figure 2. A list of I / O devices. Figure 6 is included in the capability addressable connection process performed by the peer. It is a flow chart of a task example. Figure 7 shows the need / ability to communicate from the peer to initiate a setup connection. It is a data format diagram of a power message example. Figure 8 identifies potential network services at the peer An example of the need table is shown. Figure 9 shows the ability to identify network capabilities that may be provided by peers. An example of a force table is shown. Figure 10 shows an example of the flow of process / service connection procedures executed at the peer. Is shown. Figure 11 shows personal area networks, telecommunications equipment and external ins. It is a block diagram which shows the relationship of a fragment. FIG. 12 is a block diagram of an example of peer communication and a control device. FIG. 13 is a diagram showing a sequence of data exchange messages between the devices of FIG. Is. FIG. 14 shows the data communication sequence of FIG. 13 with respect to the device of FIG. It is a flow chart that outlines the steps to be taken. FIG. 15 shows a sequence of data exchange messages between devices in another set. Is. FIG. 16 shows the data exchange sequence of FIG. It is a flow chart which outlines a stage. FIG. 17 is a diagram showing a data exchange sequence between devices in yet another set. .. Figure 18 shows a new device in a personal area network that has already been opened. It is a flow chart which outlines the procedure to introduce. Figure 19 shows polling / arranging used within a personal area network. It is a flow chart which outlines the process procedure. FIG. 20 shows a remote controller for a video cassette recorder according to the doctrine of the present invention. It is a simple plan view example of a controller. Figure 21 shows the sequence of data exchange messages between the controller and the controlled object. It is a figure which shows the operation. Figure 22 shows a sequence of steps in the process of selecting an address. This is the figure. Figure 23 shows the sequence of steps in the process of downloading a set of commands. It is a flow chart which shows the operation. Figure 24 shows a sequence of steps in the process of personalizing menu selections. It is a flow chart which shows. Figure 25 shows the process for enforcing instructions from a remote controller. It is a flow chart which shows the sequence of the steps. Figures 26 to 29 show mobile phones for storing data and streamlining operations. It is a series of sketches of a digital device. Figure 30 shows a sequence of data exchange messages between organizations involved in financial processing. It is a flow chart which shows. Figure 31 is a block diagram of an example of communication between organizations involved in financial processing. Figure 32 is another block diagram of an example of communication between organizations involved in financial processing. Fig. 33 shows a barcode reading pen and an electric machine on one side of a personal storage business device. This is a structural example of the talk function. Figure 34 shows a message format with an implicit action barcode. It is a figure which shows the example. Figure 35 shows a product using a barcode reading pen and a personal storage business device. A flow chart showing a sequence of steps in the process of reading barcode information. is there. Figure 36 shows the exchange of financial processing information between personal storage equipment and store equipment / terminals. It is a flow chart which shows the sequence of steps in the process of conversion. Figure 37 shows the access transmitted between the personal storage business equipment and the equipment of other organizations. A flow diagram showing a sequence of steps in the process of checking the level To. Figure 38 shows the access transmitted between the personal storage business equipment and the equipment of other organizations. Another stream showing another sequence of steps in the process of checking the level This is the figure. FIG. 39 is a diagram showing an example of components of a coupling key. FIG. 40 is a diagram showing an outline of the binding process. FIG. 41 shows an example of a message communicated between devices in a preferred embodiment. FIG. 42 shows yet another message communicated between the devices in a preferred embodiment. An example is shown. FIG. 43 cites the needs and capabilities adopted in the preferred embodiments. An example of data structure explanation is shown. FIG. 44 shows the request-side device and the provider-side device adopted in the preferred embodiment. An example of explaining the data structure to be quoted is shown. FIG. 45 illustrates how the elements of the requesting device data structure are related. .. FIG. 46 illustrates how the elements of the provider device data structure are related. .. FIG. 47 is a data structure quoting the connection tracking adopted in the preferred embodiment. An explanation example is shown. FIG. 48 cites yet another connection tracking adopted in a preferred embodiment. An example of explaining the data structure is shown. Figure 49 illustrates how the elements of the chat data structure are related. .. Figure 50 illustrates where various pre-ambling and post-ambling instructions are executed. It is a figure to do. Figure 51 shows the messages and messages exchanged between the two devices that open the connection. It is a message sequence diagram which shows the sequence of sage. Figure 52 is a matrix that lists the types of join keys, which is good. Its use in suitable embodiments will be described. FIG. 53 is an example of a flow diagram outlining the main control loop of the device. FIG. 54 is an example of a flow chart outlining the processing of the capacity notification message of the device. FIG. 55 is an example of a flow chart outlining the ping message processing of the device. FIG. 56 is an example of a flow chart outlining the Jing message processing of the device. FIG. 57 is an example of a flow chart that outlines the connection execution status message processing of the devices. Fig. 58 is an example of a flow chart that outlines the capacity execution message processing of the device. FIG. 59 is an example of a flow chart that outlines the processing of the join execution message of the devices. FIG. 60 is an example of a flow chart that outlines the capacity question message processing of the device. FIG. 61 is an example of a flow diagram outlining the beacon message processing of the device. Fig. 62 outlines the processing when the time of the internal timer elapses in the device. It is a figure example. Figure 63 shows when one device loses communication from another connected device and chooses to separate. This is an example of a flow chart that outlines the processing of. Figure 64 shows the case where the providing side device is separated from the requesting side device. This is an example of a flow chart that outlines the processing of. FIG. 65 outlines the process when the requesting device is separated from the providing device. It is a figure example. Detailed description of the drawing FIG. 1 shows the capability addressable wireless constructed by the doctrine of the present invention. -Various peers (P) 20, 20', 2 in the inter-peer data communication network 22 It is a layout diagram showing the relationship between 0 .... In Fig. 1, there are only a few peers 20. Computer or microprocessor control around the world, not shown Any electronic device that receives can function as a peer 20. Therefore, the net Network 22 supports an infinite number of possible connections between peers 20. The term "peer-to-peer" as used herein is at least a communication pro. Defined to mean having an intersection of tocol and / or ability, Physical dimensions, functionality, data processing capacity or transmitter / receiver range and power equivalent Gender does not matter. Each peer of communication network 22 or communication node 20 is a personal area Network 22 can be opened. For example, 1st and 2nd nodes 20 first discovers or determines that the nodes are compatible with each other. next As a result of the self-starting process, the first and second nodes 20 are personalized. Rear network Form a The first and second nodes 20 are in a specific proximity to each other. Must be detected, and if so, a communication link is opened. This phosphorus Can be conducted by known RF, IR, optical or acoustic techniques, or through living organisms. More realized. Once the link is opened, the first and second nodes 20 are needed And exchange abilities. If the needs and abilities are not satisfied or can be matched If not, one of the first and second nodes 20 communicates with the third communication node 20. A link may be arranged. In other words, at least with overlapping communication areas Communication platforms that also include two nodes form a communication network 22 at least Will also have a means of exchanging need and capability information between the two nodes. .. Network 22 is preferably built within a peer-to-peer architecture and is minimal Requires fixed infrastructure with limited network-specific components Try not to. In a preferred embodiment, each peer 20 is to manage the connection. You can start connecting with other peers 20 without the need for a server. Furthermore In addition, peer 20 can be rebuilt, set up and also without affecting the network structure. Can move freely without requiring the performance of the boot procedure. Free movement of peer 20 connects wireless communication link 26 to network 22 It is further supported by using it as a physical transport layer. In a suitable embodiment By the way Earless communication link 26 is an RF link that operates in the higher microwave band region. Therefore, a compact, lightweight, and inexpensive omnidirectional antenna can be used. But, For other RF frequencies, optical links and other wireless communication links well known to those skilled in the art Can be Specific devices used to realize wireless communication link 26 Rotocol is not important to the present invention. Various TDMA, FDMA and / known to those skilled in the art Alternatively, CDMA technology can be adopted. But all peers in network 22 20 can communicate using the protocol regardless of the capabilities and needs of peer 20 It is desirable to be able to. FIG. 1 shows a detection zone 28 surrounding each peer 20. In a preferred embodiment The wireless communication link 26 of most peers 20 operates at sufficiently low power The wireless coverage of a particular peer 20 is preferably less than 5 meters. Is. However, for regular peer 20, this range is much larger. Recently By using low power transmission each time, the wireless spectrum can be shared in different places. Interference between independent connections that have is limited. Furthermore, transmission with such low power Using is comparable to building a significant portion of peer 20 as a mobile device To. As those skilled in the art will understand, portable electronic devices are physically small and lightweight, and have batteries. It has the characteristic of having a built-in power supply such as. Extremely low power transmission, so portable devices Small battery commonly used in Does not consume much spare. Peer 20 connects to a potentially huge number of peers 20 via network 22 However, with the low power wireless communication link 26, each other at a specific time The number of potential connections to 20 physically adjacent peers is limited. In other words, the first 1 peer 20 is in the detection zone 28 of the 2nd peer 20, and the 2nd peer 20 is the 1st Contact over network 22 only when in peer 20's detection zone 28 You can continue. Instead of specifying a network-specific address to initiate a connection, Network22 uses physical proximity with need and capacity assessment (discussed below) And set the goal of peer 20 who wants to connect. Network Germany to initiate a connection By not specifying your own address, you can reduce user involvement when making connections. Network addressing can be dynamically constructed. Such addressing The scheme is when exchanging data between devices that the user carries and has daily contact with. It is useful for. It is also possible to relay information between peers instead of direct communication. For example, peer 20 opens a communication link with peer 20' via peer 20 Sometimes. In this case, peer 20 is a relay interface between the other two peers. It becomes. Note that all peers 20 need to be mobile devices. Figure 1 shows communication The ink 30 is illustrated, but this is a peer 20'to the public switched telecommunication network (PSTN) ) 32 may not include a wired link connecting peer 20'. PSTN Through 32, peer 20'can communicate with a huge variety of remote devices 34. .. Only one remote device 34 is shown in FIG. Peer 20'is the public power grid Power is supplied from (not shown), so it is important to minimize power consumption. It does not pose a design problem. Figure 1 shows the PS linking peer 20 to remote device 34. Only TN32 is shown, but other premises networks (LAN), wide area networks well known to those skilled in the art. A network (WAN) or communication link connects peer 20 to remote device 34. There is also. The remote device 34 itself may or may not be peer 20. Ne Task 22 requires proximity in setting goals for peer 20 trying to connect Used as a cause, but by using distribution, gateway or peer 20'relay , It is possible to make a long-distance connection using another network. FIG. 2 is a block diagram of the hardware 21 included in the peer 20. Peer 2 0 features antenna 36 built to support wireless communication link 26 To. Antenna 36 connects to transmit and receive section 38. Send and receive Communication section 38 is compatible with the protocol used by peer 20 to communicate with each other. Have sex. The transmit and receive section 38 connects to the processor 40. Pu Rose The 40 is memory 42, optional gateway 44, communication link 30, o Option I / O section 46, transmit and receive section 38 and options Connect to the equipment circuit 48 of the device. Processor 40 uses computer program 50 stored in memory 42. Execute. Computer program 50 is on processor 40 and peer 20 Therefore, the process to be executed is defined. Memory 42 is even more personalized (persona) Conversion) Stores data 52 and application data 54. Individual The humanized data 52 characterizes the user or owner of peer 20, and for each user, Rui changes over time. ID code, password and PIN Radio or TV channel preset, selected language and fast dial phone number It is an example of personalized data, as is the case with issues. Application data 54 is provided by running a peer application and every time Change. Fax, phone numbers received via pager, barcodes Data scanned using a reader and received from a microphone or other source A piece of sound is an example of application data. In certain embodiments, the present invention uses one or more communication nodes in a common network. It is realized as an integrated circuit that connects interactively. Input data is stored in this integrated circuit. Receive receive The machine, the transmitter that transmits the output data, and the processor are integrated and included. Process The receiver is connected to the receiver and transmitter, and the first common node is paired with the second common node. Connect to talk. In the processor, the first and second common nodes are at a predetermined distance from each other. If the needs and capabilities of the 1st and 2nd common nodes overlap, then It is equipped with a device that activates a communication link between the 1st and 2nd common nodes. FIG. 3 is a non-exhaustive list of examples of equipment circuits 48 included in peer 20. No. With reference to FIGS. 2 and 3, the equipment circuit 48 is present in a wide range of everyday and usually present. As any kind of electronically controlled fixed or portable device Can be built. Thus, peer 20 is, in addition to being peer 20, Personal Digital Assistant (PDA), TV, Radio, CD Player, Te Loop player, copier, facsimile machine, telephone, cellular telephone, cordless Telephone, pager, wristwatch, computer, POS (point of sale) terminal, own It can be a dynamic payment machine or other electronic device. FIG. 4 is a non-exhaustive list of gateways 44 contained in peer 20. No. Refer to Figures 2 and 4, the gateway 44 can be of any type known to those of skill in the art. Can be constructed as a relay, distribution or protocol conversion device. For example , Peer 20, in addition to being Peer 20, brings Peer 20 to PSTN32 (Figure 1) The modem to connect to Can be done. The other gateway 44 connects peer 20 to a LAN or WAN There is. Yet another gateway 44, for example, a peer 20 modem as a satellite, Connect Peer 20 Cell Phone to PSTN32, Older Phone (POT) Peer 20 to PSTN32 Can be FIG. 5 is a non-exhaustive list of I / O devices 46 included in peer 20. Fig. 2 And with reference to FIG. 5, the I / O device 46 is classified into an input device and an output device. Input devices include keyboards, indicators, optical scanners, microphones and others. There are well-known input devices. Output devices include printers, monitors, speakers and others There is a well-known output device. Thus, in addition to being peer 20, peer 20 is It can also be an I / O device 46. As those skilled in the art will understand, inevitably Gateway 44, I / O Section 46 And equipment circuits 48 are not mutually exclusive categories. For example, many outfits Places belong to multiple categories. For example, a computer that is considered a device is an I / May have both an O section and a gateway. Similarly, the gateway May also play the role of I / O. Figure 6 shows the ability addressable connection process performed by peer 20 56. It is a flow chart of the task included in. Process 56 is performed in a format well known to those skilled in the art. A Computer program stored in the memory 42 of 20 (Fig. 2) Defined by 50. In a preferred embodiment, all peers 20 are process 56 Performs a process similar to. Process 56 includes query task 58, during which peer 20 is set up. Determine if a setup coupling is attempted. In general, task 5 According to 8, does the first peer 20 have the second peer 20 physically close to the first peer 20? It is possible to judge whether or not. Task 58 includes send and receive section 38 ( Let network 22 monitor the wireless communication link (Fig. 1) Determine if you can receive a signal that is compatible with the protocol you are using To do. Due to the above low transmit power levels used by most peers 20, the signal When the issue is detected, the peer 20 sending the signal is placed near the receiving peer 20. To. Task 58 cannot determine if a setup connection is being attempted In that case, query task 60 causes a coupling-seeking event. Judge whether or not it has come. Due to the connection search event, peer 20 is in contact with another peer 20. Find the continuation. Connection search events can be triggered using a periodic schedule .. For example, you can look for a connection every few seconds. In this example, the schedule is public Seek more frequent periodic connection attempts from peer 20 powered by the public power grid , Battery-powered peers 20 seek less frequent connection attempts. Connection Search event is constant Receiving interval or random interval timers when the timer expires or other external information It can also be activated from time to time. Other external information includes equipment circuit 48, gateway 4 Information obtained through I / O Section 46 (Figure 2) containing 4 or user input Is included. Program control if task 60 cannot determine that a connection search event has occurred Return to task 58. Task 60 determines that a connection search event has occurred Process 56 then executes task 62. Task 62 is a voluntary setup Start the connection. The setup connection is to a specific peer 20 on network 22. No dress is specified. Rather, it's publicized by peer 20 trying to do it. By all peers 20 in detection zone 28 (Fig. 1) of public relations peer 20 Is received. As explained below, the public relations signal is detected by another peer 20. There is no need for another peer 20 to respond even if you are in the 28. At this point, public relations Peer 20 needs to know when other peers 20 can receive publicity signals No, even if the public relations peer 20 is close enough that the other peer 20 can form a connection, You may or may not know the specific needs or abilities of your peer 20. Task 62 is set up by publicizing the need / capability message 64. Start the connection. Figure 7 shows an example of the format of this message. Figure 7 Please refer to Sage 64 has ID 66 of peer 20 publicizing message 64 and authorization key 68. Includes Necessity Spec 70 and Capability Spec 72, and may include other data elements To. Peer ID 66 is preferably sufficiently unique within the domain of network 22 And if the setup connection is successful, the service connection will be addressed Used. Authorization key 68 contains one or more data codes and this data The code is used by the receiving peer 20 in performing the authorization process. necessity Specification 70 is a list of network needs that currently exist for public relations peer 20. Capability specification 72 is provided by Public Relations Peer 20 to Peer 20 on Network 22. A list of possible network capabilities. Necessity specification 70 is determined by collating the need table 74. Figure 8 shows an example of a non-exhaustive block diagram of this table. As shown in Figure 8 , The data code requires a wide range of services owned by the service requesting peer 20 Related to sex. One of the necessary examples is the personalization of equipment. In the example of the need for device personalization, PD A may need to personalize nearby equipment. To meet this need Program personalized data 52 (Figure 2) to nearby devices without user intervention I have to go. As a result, the user whenever the user is nearby A constant machine, regardless of the person who used the device before, without the need for side action In a bowl Is always programmed with personalized data for a particular user. Another example of the need is printing application data 54 (Figure 2), Display of application data 54, application data on speaker 54 Announcements, Wiring to the Internet or Other Network Resources , POS transactions, passing through protected areas or tollhouses, etc. Capability specification 72 (Figure 7) is determined by collating capability table 76. Is done. Figure 9 shows an example of a non-exhaustive block diagram of this table. Shown in Figure 9 As such, the data code is extensive provided by peer 20 on the service provider side. Related to the service capacity of. For example, the capacity of the service providing peer 20 is the capacity of each device. It can be a humanization ability. For this reason, peer 20 is personalized data 52 (Fig. 2). ) Can be personalized. Another example is printing, to name a few. , Display, speaker announcement, internet or other network or POS There are relaying of connections via terminals and cancellation of confidential passages. In general, potential Is comparable to the potential need. Returning to Figure 7, the need / capability message 64 currently applies to Table 7 Includes code for 4,76 (Figures 8 and 9). Peer 20 at some point 2 May have more than one need 70 or ability 75, but peer 20 You are not required to have multiple needs or abilities. In addition, peer 20 Does not have to have both network needs and network capabilities. message 64 indicates the need for a peer 70, whether or not the peer's ability 75 is specified. If determined, will it act as a need message and specify a peer need 70? If the peer's ability 75 is specified, whether or not it functions as an ability message .. Going back to Figure 6, when Task 62 publicizes Message 64 (Figure 7), the pro Gram control returns to task 58. Task 58 actually receives message 64 When it detects that a setup connection is being attempted by 78 runs the authorization process. Task 78 is from message 64 to authorization key 6 When the receiver uses 8 (Figure 7) to the peer 20 trying to set up the connection Determine if you are authorized to connect to peer 20. Task 78 is for peer 20 Owner restricts access to owned peer 20 over network 22 Make it possible. The authorization process for Task 78 is, for example, a small family glue. It is used to limit the personalization ability of the device to the device. Alternatively, POS capability Peer 20 with has an extensive authorization process before it can be traded can do. Peer 20 with need is also an authorization pro provided by Task 78 Depending on your access, you will be eligible to receive the services provided. After task 78, query task 80 is the set in which authorization process 78 was attempted. Determine if you have authorized the up connection. Program control if authorization is denied Returns to task 60. Receiving peer 20 does not need to respond, otherwise Acknowledge the attempted setup connection. Once the authorization is accepted, task 82 will determine the need for the peer and the capabilities of the peer. Is evaluated. In other words, task 82 causes the message receiving peer to do so. Spontaneous need / ability message 64 (if any) received for available abilities Compare the needs listed in Figure 7) and see the available needs (if any). Compare with the abilities listed in Sage 64. After task 82, query task 84 However, it works after receiving the evaluation result of task 82. Marked in Spontaneous Message 64 If there is no internal capability that matches the need to be, and also marked in the voluntary message 64 If there is no internal need to match the ability to be done, either peer 20 will sir to the other We cannot provide bis. Program control returns to task 60 and the receiver A20 does not need to respond, otherwise it will be the attempted setup connection Respond affirmatively. At this point, the majority of potential connections that peer 20 makes in network 22 are , The range is greatly reduced without using network-specific addressing. The low power transmission scheme currently has many peers 20 in network 22 Exclude from those that can be connected with. This is because many peers 20 are not close to each other For the sake of. Potential of the few peers 20 in each other's detection zone 28 (Figure 1) The scope of the target connection is the authorization process of task 78 (Fig. 6) and the necessity of task 82. And further constrained through ability assessment. Service requester peer 20 and service Negotiation process (negotiatio) performed with the provider peer 20 n Further exclusion is performed for the remaining potential connections through process). If task 84 determines that the capabilities and needs match, the query task 86 determines if this negotiation process has ended .. If the negotiation process is not finished, task 88 will call it A ID66 (Figure 7) is included in the need / capability message 64 just received Addressed negotiation message for peer 20 (not shown) ) To open a setup connection or continue to negotiate Facilitate the situation process. Negotiation message is necessary / May have a format similar to capability message 64, but especially for other peers 20 And the address is specified. After task 88, program control returns to task 60. Subsequent negotiation You may receive a message, but you do not have to. like this Subsequent negoshi A situation message negotiates both peers 20 for the expected connection Query task 90 negotiates when it is marked that the session has been completed. Determine if the operation was successful / finished. If the negotiation is unsuccessful , Program control returns to task 58 and no service connection is made. But ne If the gossip is successful, process service connection step 92 is performed. During step 92, a one-to-one addressed connection was opened between peers 20 and the net Run the work service. When the service connection is finished, the program flow Return to task 58. Capability addressing connection process 56 is set up during the connection process of the user There is nothing to prevent you from relying on intervention, but no user intervention is required. User Whether intervention is required depends on confidentiality, empirical knowledge, and the peer 20 involved. It depends on other considerations that are tied to the nature. For example, peer 2 involved in financial processing 0 is better to intervene with the user to confirm confidentiality. But the user is You need to rely on user intervention for personalization of your device and many other connection situations Absent. FIG. 10 is a flow chart of the process / service connection procedure 92 of FIG. procedure 92 is to be executed by the service provider peer 20 to make a service connection. Shows a set of tasks that can be done. All peers 20 are all tasks shown in Figure 10. Keep in mind that you don't have to be able to do I want to be. Similarly, many peers 20 are other suitable for the nature of those particular peers 20. Have a task. Step 92 is to receive the service of network 22 through the opened service connection. Network relay, router or gateway capabilities for believer peer 20 Perform task 94 to provide. Service provider peer during task 94 20 relays data communication between the connected peer 20 and the remote device 34 (Fig. 1). To do. After task 94, the program flow returns to process 56 (Figure 6). Task 94 extends the service connection to the Internet or other networks Can be used to lengthen. Step 92 performs tasks 96,98 through an established service connection. Provides user input capability for service receiver peer 20 on network 22 .. During task 96, the service provider peer 20 has its I / O section 46 (second). Collect user input from (Figure). During task 98, the service provider peer 20 , Send the collected user input data to the connected service receiving peer 20 .. After task 98, the program flow returns. Using tasks 96,98, Control or program equipment from PDAs and other devices with enhanced input capabilities Can be ramming. Step 92 is to perform task 100 and connect through the established service connection. Network22 service receiver peer Provides user output capability for 20. Service provider during task 100 Peer 20 sends the data generated from the service receiver peer 20 over the service connection. And receive the data at the output device in I / O section 46 (Fig. 2). To know. This data is in an audibly and / or visually recognizable form or person Announced in any other form recognizable by the sensation between. After completing task 100 , The program flow returns. Task 100 was collected at mobile peer 20 The data can be used to announce in a non-portable notification device. is there Or generated by a stationary device with limited I / O capability using Task 100 The data can be announced by the mobile notification device. Step 92 executes the device control process 102 to assist in controlling the device. Professional Tasks 104,106,108 of Seth 102 are personalized data 5 to device peer 20 Executed to program 2 (Fig. 2). During task 104 The service provider peer 20 is a service receiver peer connected using a service connection. Get personalized data 52 from 20. Then in task 106, a network compatible individual Personalized data 52 is suitable for the specific device in which the personalized data 52 is programmed. Convert to an expression. All 52 personalized data available on the service receiver peer 20 Those skilled in the art will understand that it is not necessary to make it adaptable to all devices. This Therefore, task 106 is an individual that only adapts to a specific device. Humanized data 52 can be used. After task 106, by task 108 Therefore, the converted personalized data 52 is programmed into the device. Task 10 After the end of 8, the program flow returns. Tasks 110,112,114,116 are performed and the user can easily get the device Can be controlled. These tasks are, for example, on the display and on the device. Run on a PDA with user input capabilities that exceed the user I / O capabilities normally found on Can be In this case, the device becomes the service receiving peer 20 and the PDA is the service. -Become 20 peers on the service provider side. During task 110, the service receiving peer 20 A device control computer on the service provider peer that is joined using a service connection -Upload the program. Then during task 112, the service provider A20 runs the computer program that was just uploaded. Ta The desk 112 is a desirable user interface for a particular device to be controlled. Have the service provider peer 20 specifically built to provide. Then task 1 During 14, control data is sent to the service receiving peer 20 over the service connection. Is received. Control data generated from user input is on the service provider peer 20 Supplied through a control computer program that runs on. Task 114 After the end of, task 116 is the target machine according to the control data received by task 114. Control the vessel. End of task 116 After completion, the program flow will return. Example 1 Figure 11 shows the personal area network 120, the communication device 127 and It is a block diagram showing the relationship between the external infrastructure 120 and the external infrastructure 120. Person The null area network 120 is, for example, an RF represented as link 123. It is composed of personal devices 121 that are linked to each other via an interconnect. Pa -Sonal area network 120 is a communication device 1 via RF link 125. Linked to 27, and external infrastructure 13 via link 129 Linked to 1. External infrastructure 131, in this example, is an individual unit -The taste, location and / or number (IUPLS134) or roaming user One of the preferences, location, regional phone number and / or number (RPLS133) Consists of personal records describing. Of personal equipment 121 and telephone 127 Each is equipped with a bidirectional RF link device, such as the RF link device 135 in Figure 12. To. FIG. 12 shows an example of peer communication and controller 135 similar to that of FIG. It is a figure. This device is an antenna 137 connected to the T / R module 139. , Processor 143, Memory 147, Optional I / O device 159 and And an optional equipment circuit 155. These are shown in Fig. 2 respectively. Antenna 36, transmit and receive section 38, processor 40, memory 42 , Similar to optional I / O section 46 and optional equipment circuit 48 To. The optional gateway interface 44 in Figure 2 is shown in Figure 2. As in separate elements, or in the system shown in Figure 12. As such, it may be included in any I / O device 159. Optional I / O device 159 If present, it is linked to processor 143 via link 157 and opci The equipment circuit 155 is linked to the processor 143 via the link 153. .. Processor 143 is relocated to T / R module 139 via link 141. Connect to memory 147 via link 145. Memory 147 is a computer Personal data 149 including programs 148, IUPLS133, RUPLS134 and a It includes application data 151. Application data 151 Includes device structural preferences, network structure, etc. Instrument circuit 155 or 48 (Figure 2) controls the system associated with a particular instrument. Interfaceed for. It is or is installed in the equipment at the time of manufacture Or the equipment circuit 155 or 48 is manufactured without personal networking capabilities Adapted to modify the equipment. In either case, the memory 147 is internal Command, ability, inter Data and / or interface related to device control such as face protocol Access command and equipment circuit 155 or 48 via antenna 36 or 137 Through commands generated by processor 143 in response to the information connected to At least you can program and assert the control means of the device Contains information about what to do. Memory 147 rewrites or updates the data in it in response to changes in the environment. It is built so that it can be used. An example of work in which such changes occur is the 13th It will be explained by the figure and the related text. T / R module 139 (similar to transmit and receive module 38 in Figure 2) is Rad DTR-9000 manufactured by io Design Group (3810 Almar Road, Grants Pass OR97527-4550) Is useful, processor 143, memory 147 and optional I / O Equipment 159 is from Motorola (Phoenix AZ, Austin Tx, Schaumburg IL). It is useful to have the MPC821 sold. FIG. 13 shows the sequence 160 of data exchange messages between the devices of FIG. It is a figure which shows. The personal device 121 in FIG. 11 (similar to device 20 in FIG. 1) Speaking of which, the exchange of data with the dialogue request 161 addressed to the telephone 127 is started. Den Story 127 acknowledges dialogue request 161 with message 162 and message 162 Polls the personal device 121 regarding preferences. Personal equipment 121 Is Next, the preference response 164 is provided to the telephone 127. Phone 127 then net Included in preference response 164 for work or infrastructure 131 Location and / or IUPLS133 and / or R, depending on the nature of the data Send message 166 containing UPLS134. This kind of exchange has an individual A device that enters the rear and is relatively fixed within the environment in which the individual's personal communication device is located It can happen when you start a dialogue with the network. For example, walking to a doctor's office Personal digital reed where a patient interacts with a device in the doctor's office Have a stunt and where the person is for that infrastructure Tell the doctor all calls to your personal home and / or office phone It can be delivered to the office phone. About this kind of work, 14 Explained below with reference to figures and related texts. Figure 14 shows the data communication sequence for devices 121,127 (Figure 11). It is a flow chart of process 170 which outlines the steps in 160 (Fig. 13). Pu Rothes 170 was opened by telephone system dialogue 171 with telephone 127 (Fig. 11). Be started. Process 170 brings personal equipment 121 within range of telephone 127 When it is determined that (block 172), the telephone 127 has its personal device 121 Acknowledge that it is within range (block 173). Next, the personal device 121 is Send the preference (block 17) Four). The personal device 121 allows the line connected to the telephone 127 to transmit data Mark not to be used, or personal device 121 is in the range of telephone 127 If it is determined that it is not inside (block 172), control returns to block 172. The line on which the personal device 121 is connected to the telephone 127 is used to send or receive data. Marking that it will be used for (block 175), telephone 127 will give location information Send to infrastructure 131 (block 176). Location information is by phone 12 Describe the location of 7 and the telephone number. This means that the user is within the range of phone 127 Therefore, the user's position is included. Using this information, the telephone 127 is the user's telephone RUPLS 134 when not talking or when not in the user's normal location RUPLS134 and IUPLS13 when updated or when the user returns to home or office Update 3. If you don't use this phone line, no matter what the reason, professionals Gram control returns to block 172. Also, when the personal device 121 is physically moved, , Or personal device 121 through which a connection to the network is established. If another personal device 121 moves out of range, the program will make a decision. Go to CK180 and update your preferences to default (block 182) or Sets it to preference from another personal device 121 within the range of the television. When a call is made to the user's home or office phone (block 178), the system If the user determines that the user is still within the range of telephone 127 (block) 180), the call is delivered to the user's current location (block 181). You If it is determined that The is no longer within range of Phone 127 (Block 180), Phone 1 27 sets the phone line preference to the default value (plus phone 127 interacts with other users) Update to the value derived from). Process 170 ends (block 183). Example 2 Figure 15 shows the sequence of data exchange messages between devices 121 and 191 in separate sets. It is a figure which shows the operation 190. In this example, the personal device 121 is, for example, personal. Device 121 (Fig. 11), 135 (Fig. 12) or Peer 20 (Fig. 1) 21 (Fig. 1) 2) Approaching Rent-A-Car 191 with Similar Peers and Controlled by It Carried by one user. Personal device 121 sends a dialogue request 192 To. Vehicle 191 affirms personal device 121 via hardware 135,21 Reply the reply. The personal device 121 is a car key (electronic unique to vehicle 191). Send code) to hardware 135 or 21 in vehicle 191 (car key) -Is for personal use according to the procedure when renting the vehicle 191 Preloaded in device 121). Vehicle 191 then hardware 135, Check the validity of the car key through 21 and unlock the door, in this case Also acknowledges the receipt of the car key via hardware 135,21. Reply from hardware 135,21 of vehicle 191 to personal device 121 The constant response message 198 coincides with the user opening the vehicle door. Personal clothing Place 121 in message 200 to vehicle 191 hardware 135,211 In response, the vehicle structure preference is transmitted. Vehicle 191 is then seated, height, and Mira -Adjustment, lighting level and personal equipment adjustment (ie radio to the desired station) By setting (such as), it corresponds to as many tastes as possible. this These operations will be explained in more detail with reference to Fig. 16 and related texts. To. FIG. 16 outlines the steps in the data exchange sequence 190 of FIG. It is a flow chart of process 210. In process 210, personal device 121 is hard Beginning when forming a personal network with vehicle 191 via ware 135,21 Maru (block 211). By stage 212, personal device 121 is hardware 1 If it is determined that it is within the door range of 35,21, an acknowledgment signal will be given to vehicle 191. Sent from hardware 135,21 (block 213), personal device 121 -Send the key (block 214). Vehicle 191 / Hardware 135,21 Next, Kah Ki -Determine if is valid (block 215). Where the personal device 121 is not within the hardware 135,21 of vehicle 191 If, or if the car key is determined to be invalid for this vehicle 191 (Block 215), program control returns to block 212. Car key is valid When determined to be (block 215), vehicle 191 unlocks and opens the door. And send an acknowledgment to personal device 121 via hardware 135,21 (Block 216). Next, the personal device 121 sets the structural preference of the vehicle 191. Send to Doware 135,21 (block 217). Vehicle 191 is shown in Fig. 15. Corresponding to these preferences as explained above in relation to the relevant text, Rothes 210 exits (block 219). Example 3 Figure 17 shows the steps in the data exchange sequence between devices in yet another set. It is a flow chart of the process 220 to be outlined. Process 220 is personal equipment 121 Is determined to be within the television range (block 222) (eg, stated separately) Initiated (by a periodic "pinging" process) (block 221). Tele Bi responds affirmatively to the presence of personal device 121 (block 223). Personal device 1 21, channel or network, volume level, control Send preferences such as last (block 224). Choices or tastes on this TV If it is not a valid option for, or the personal device 121 is within the range of the TV If not, control returns to block 222. If not, this is the TV Corresponding to their tastes (block 226), changing the transmitted cable network Set (block 227). System in response to messages sent in connection with the task in block 227 Delivers the desired station to the television receiver (block 228). In addition, personal equipment The physical movement of 121 goes out of range of the television, or the personal device 121 Another personal device 121 that opens a connection to the network through this is the net When moving out of work / television range, the program goes to decision block 230 Go ahead and update your TV preferences to system defaults (block 232), or This is set to the preference of another personal device 121 within the range of the television. This is the origin If not, the selected TV signal will be delivered to the TV (block 231) and displayed. To. This ends process 220 (block 233). Example 4 FIG. 18 is a flow chart outlining the procedure 250 for setting the confidentiality standard of device A. To. Step 250 is as follows: (i) Device A Those who lograming have the right to do it (owner code, password, etc.) As a basis), (ii) Those who program each of the member devices have the right to do so It is assumed that there is (based on the owner code, password, etc.). men A bar is a device in which device A is expected to be in close proximity. Member devices are close Otherwise, device A will be missing. The principle that determines proximity is It can be decided by the individual who has the right to do so. For example, the proximity relationship is the number of communication relays or the member device is separated from device A. One or both of the rational distances can be limited. How to do this As an example, the tag of the number of relays for each communication, that is, whether it can be executed A count that increments each time a message is transmitted from one device 121 to another 121 It is done by adding. When devices 121 are in close proximity, they detect each other (Figure 1 and related texts). See). At this point, the device can potentially be networked But I haven't done so yet. After a short negotiation, each device 121 is the other Decide if you want device 121 and a network. Both devices 121 are die Upon agreeing to participate in the alog, device 121 connects (joins). That's right After that, it becomes a data communication state. Two devices beyond this first negotiation 12 Note that the one-to-one dialog never happens. But the devices are each other Recognizing the existence of A mechanism for communication has been established and you can participate in the dialog. It is believed that you will be connected because you have agreed to. On the other hand, adjacent devices 121 do not participate in dialogue with each other. May be selected and networked even if they can detect each other Not combined. This situation is owned by two devices 121 by two different individuals. Each device 121 may be owned by the same person It is ordered to interact only with the device 121 of. In this way, peering Placement 121 may selectively ignore other devices 121 even if they are in close proximity. this To be carried out by a unique ownership identification code or other method well known to those skilled in the art. Can be done. In this method, the first individual has equipment 121 in the apartment, these are the other apartments Corresponds to the case of being close to another person's device 121. These devices 121 connect each other Can be detected, but net only with other devices 121 owned by the same person Networking with each other when programmed to work There is no such thing. Of course, there are other authorization schemes that can be used by those skilled in the art. it can. For example, network devices 121 together and secret subgroups It can also be divided into disjointed sets called. Step 250 is for a particular device 121 (Device A). Triggered when a confidentiality standard is programmed into device A (block 251). If device 121 does not have input capability by nature, this programming is RF link, Effective via wired or optical links. At the opposite end of the link, a key Programming device A, such as a board, speech recognition system or similar device There is an interface device for this. In the first stage, all equipment of a specific confidential group It is determined whether 121 is close to device A, that is, in a data communication state. Lock 253). If this is not yes, the program is available on the internet Trying to enable communication with (dashed line) or missing member device network Wait until close to and / or data communication (block 255) .. In either case, the connection stage (block 257) takes place first, followed by the device. Information that should include confidentiality needs related to other devices in A's confidential group Programmed in device A (blocks 259-265). For more information, the member device is selected (block 259) and becomes member device 121. Confidential information about device A is programmed into device A (block 261) and is involved with device A. Confidential information is programmed into member device 121 (block 263). Sa In addition, device A is programmed to be recognized by one or more of the following: : Confidential group unit serial number, unique machine to identify owner Dense group identifiers, physical addresses and / or phone numbers of places of use, etc. The confidentiality standards of member devices include inclusive and exclusive specifications. For example, the inclusive specification is "when device B disappears, this is missing (" It is missing) ". What is the exclusive specification? "If you can see device D, click here. Is missing. " Desirably, all these member devices 121 in the confidential group are defeated by each other. Confidential information for device A contains multiple interactions when the data is programmed Program 250 ends (block 26) 7). For example, if the confidential group of device A contains three devices, B, C, and D. To do. In block 267, the confidentiality criteria contained in device A are "devices B, C, If any two of D are missing for more than 2 hours, this is missing. " It can be specified by an inclusive statement. This standard is "more than 3 minutes each other If you can always see devices C and D inside, this is missing. " It can also be specified by a toment. Control if data for each other is not programmed into all member devices 121 Returned to block 259, another member device 121 was selected, and a nominally confidential group Block 2 until all member devices 121 that make up the loop are programmed The steps 59 to 265 are repeated. If a sensitive group is set up for device A, that sensitive group will be on device A. Note that it only exists for. For example, device A is its confidential glue It is assumed that there is one member device B in the device. Device B, on the other hand, is its own secret Define the loop with device C as a member. But this is implicit from B to A Neither the target relationship nor the relationship between A and C is set. B is A's confidential glue A is a member of B's confidential group just because he is a member of Nor does C belong to A's confidential group. This scheme Provides great flexibility in the realization of the present invention. Figure 19 shows the polling / alarm procedure 270 used in connection with a sensitive group. It is a flow chart which outlines. Step 270 is between device A's pre-specified polling. It starts by waiting for the interval (block 273) (block 271). Between polling The septum is unique to the nature of device A, and in some cases very short pollin. Relatively long polling intervals for other types of equipment from the interval (eg 5 minutes) May vary up to (for example, 1 day). After waiting for the polling interval, device A pops all 121 members in the sensitive group. -Ling to determine if the members are in close proximity. When this is done , Device A does not predict when member 121 is missing from the sensitive group Determine when it exists in (block 277). There is no member 121 missing from the sensitive group and there is an unexpected device 121 If there is nothing to do, program control returns to block 271/273 and blows The steps outlined in 273-277 are repeated at appropriate intervals. Member 121 is missing or unpredictable from a sensitive group When it is determined that -121 exists (block 277), device A is in the specified period. For a short time, wait for the missing device to return or for the unexpectedly existing device to disappear. Lock 279), then poll for missing or unexpectedly existing equipment (bu) Lock 281). If it is determined that member 121 is not actually missing (block) 283), control returns to block 271/273, roughly to blocks 273-277 The stage to be explained is repeated. Member 121 is actually missing or unexpectedly present When it is determined (block 283), the device is disabled (block). 285) and / or activate the alarm (block 287), take steps, etc. It performs a polar action, after which step 270 ends (block 289). The alarm condition is that device A is (i) stopped (block 285), (ii) ask for help. Attempting to call the police (Block 287), (iii) Asking for help, Or try to make a call to the central equipment authorization body for an invalidation code (block) 287) or (iv) interact with a neighboring device to make a call for (ii) or (iii) The case of trying is included. After that, process 270 ends. When making a call using a normal telephone line The physical address is usually easily determined from the identifier of the line on which the call is made. To. Example 5 Figures 20 to 25 show the above concept of setting up a remote controller for a device. Apply to constant. FIG. 20 is used for a video cassette recorder in accordance with the doctrine of the present invention. It is a simplified plan view example of the 1st preferred embodiment of the remote controller 300. Tale Roller 300 has three displays 303,307,309 and displays Ray 303 provides address notification, display 307 uses controller 300 The display 309 is available for commands to be sent to the controlled device. Display the icon 311 corresponding to the window. Which icon 3 is the cursor 312 11 indicates whether it has been selected, and display 307 shows the text of the selected command. Provide a description or identifier. The trackball 301 allows the operator to -Move Sol 312 between different icons 311 to move a specific icon 311 You can choose. Button 305 is an ad displayed on display 303. Allows switching of less. FIG. 21 shows the controller 300 and the controlled object 324. It is a figure which shows the sequence 320 of the data exchange message between. Process 320 Address search request 326 is from controller 300 to controller 300 And peer communication and control device 135 (Fig. 12) in each of the controlled objects 324. Or it is started when it enters the controlled target 324 via a device such as hardware 21. .. Address acknowledgment 328 causes 324 to be controlled with controller 300. The controller 300 is notified that it is in a communication state. Controller 300 Sends request 330 to download the command set for controlled 324 To do. The controlled object 324 is then a set of these commands for the controller 324. Download (Download "Control Command Set" 332). at this point, The control target 324 is a frame that can be executed by an instruction of the controller 300. Sending a set of operations / actions. Selected by the user of controller 300 The command to be selected is sent to the controlled object 324 (the command selected to be controlled). 334), the controlled object 324 receives at least a command or a command group. Provides command feedback 336, including an acknowledgment. Control target In both 324 and controller 300, the user downloads a "set of control commands". If you set a preference that is selected from a previously sent list in de 332, it Send and receive commands and feedback 338 according to, this is the last, sand Wachi i-th command (command_i 340) and feedback (command_i Continue until feedback 342). Figure 22 shows a sequence of steps in process 350 of address selection. It is a flow chart which shows. Process 350 initiates an address where the user searches for a device Then it starts (block 325). Controller 300 (Figs. 20 and 21) ) Is allowed to interact with the controller 300's personal area network Launched within the area (block 354), controller 300 is its personality "Ping" to the controlled object 324 in the Ruellia network. That's right Send a question message (block 356). Unknown control pair to controller 300 Elephant 324 is in communication with or part of a personal area network When the response indicates that there is (block 358), the controller 300 is new. Add the controlled object 324 to the internal list (block 360) (ie, in Figure 2). Store data in memory 42 or memory 147 in Figure 12). Controller 30 0 corresponds to the new controlled object 324 on display 303 (Fig. 20) View the address (block 362) and enter the personal area network Repeat steps 358-362 until there are no new controls. Controller 300 selects whether the user has pressed an address button (Block 364), Controller 300 increments the internal list of addresses (ie sequentially enumerated) (Display the address) (block 366). If not, process 350 Ends (block 370). Incremented sequentially listed addresses (block 366) ) After that, the controller 300 is addressed on display 303 (Fig. 20). Display (block 368). The steps outlined in blocks 364-368 are: Repeated until the user stops incrementing and displaying addresses. Figure 23 shows the steps in process 375 that download the command set. It is a flow chart which shows a sequence. Controller 300 (Figs. 20 and 21) When stabilized to address the controlled object 324 (block 378), for example you The address increments at steps 364-368 of process 350 (Figure 22) When stopped, process 375 starts (block 376). Controller 30 0 then sends a download request to controlled 324 (block 380) (block 380) See also Download 332 of "Control Command Set" in Fig. 21 and related texts. Teru). Controlled 324 downloads a set of control commands to controller 300 Do (block 382). The command set is downloaded by the controller 300. If it is determined that the file has been executed (for example, a file end instruction or timer expiration date, etc. ), Process 375 ends (block 384). Figure 24 shows the command menu that controls the controlled object 324. Sequence of steps in the process for personalizing choices in the process 38 It is a flow chart which shows 5. Controller 300 active for command selection When it becomes (block 389) (that is, items 332 to 342 in Fig. 21, Fig. 23) After exiting process 375 in the figure, process 385 begins (block 387). Ko The controller 300 determines that all commands have been processed (block 39). 1). In that case, control goes to block 399, otherwise control The La 300 then displays the appropriate icon 311 (Figure 20) on Display 309. Also, display the command text on display 307 (block 393). , Allows the user to remove a command from the command set. When the controller 300 determines that the user wants to delete the command (Block 395), controller 300 updates the internal list of commands (bro) 397), stages 391 to 397 until it is determined that all commands have been processed Repeated (block 391). Controller 300 allows the user to command If it is determined that you do not want to delete (block 395), control is block 3 Return to 91 and repeat steps 391-397 until it is determined that all commands have been processed. Returned (block 391). When controller 200 determines that all commands have been processed (block 39) 1), controller 300 is diss Show updated command list on play 307/309 (block 39) 9) Internal user preferences (eg memory 42 in Figure 2 or memo in Figure 12) Store in 147) (block 401). After this, the controller 300 is framed. Activated for processing (block 403), process 385 internally It ends when the stored command set is personalized according to the user's taste. Lock 405). Figure 25 shows when commands are supplied from the remote controller 300 (Figure 20). , Fig. 21), Process 42 for executing the command by the controlled object 324 It is a flow chart which shows the sequence of the stage at 0. User controller 300 When the command transmission (block 426) to the controlled target 324 is started from (bro) 424), process 420 begins (block 422). The control target 324 is The command is preferably processed immediately (block 428). Control and instruction professionals When it is determined that the session is complete (block 430), process 420 is terminated (block 430). Lock 432), if it is determined that the control and instruction process has not ended (bro) 430), process 420 returns to block 424, blocks 424 ~ 43 The steps outlined in 0 are repeated. Example 6 Personal data such as information that people put in wallets and wallets has been digitized (Ah) Rui is its functional equivalent (expressed in digital format), similar to a wallet, etc. Carried in a device with formal elements. There are various formal elements, but this device is subordinate If it is useful or desirable, it will be carried instead of the next wallet. It does not matter if it takes a physical form such as. That is, men's pockets and women's It is preferably suitable for a wallet. This device is in close proximity according to the same protocol You can interact and trade with other short-range wireless devices. For example Corresponding to this device in business, "Network Match Digital Wire" There is a "less cache register". For personal data storage devices and business devices As an example, this device is used as an activity base for personal area networks. Is a personal database carried by the company, and is a function collectively called "electronic wallet". To execute. The present invention is composed of at least some of the following components: 1) Basic peer communication detailed in Figures 1 and 12 and related texts Shin module. Personal transaction and storage devic e) Options for unique peer-to-peer communication nodes in 407 (Figures 26-29) The parts are listed below. 2) (i) Data entry and (ii) User interface capable of displaying data Soo. Data entries are physical keyboard, handwriting recognition, character recognition, voice And / or word recognition and / or point-and-click mouse interaction Achieved through some well-known methods such as virtual keyboards with faces Can be done. Data display is virtual display or graphic display It can be achieved through several well-known methods, including a unit. 3) Memory for database function. In addition to the hardware features listed above, the following features are available for personal business storage. Convenient to be present in Place 407: 1) Data storage, data placement, data retrieval and navigation within data General-purpose database function including the system. Such a function is a personal business storage device 40 Data stored locally in 7 or remotely stored in another device However, the data is accessed via the personal storage business device 407. 2) Select specific data from the database and connect it via wireless link Ability to send to one or more third parties. 3) Receive data sent by a third party and store the data for personal business Save to the database of device 407 Ability to do. 4) Stores identifiers or indicators that indicate the existence or location of people involved in data operations And the ability to publicize. For example, the owner of this device is currently with the device Ability to store and publicize information. 5) Command over a wireless link (eg Link 26 in Figure 1) Receive the card and locally place it on the unit (eg 324, vehicle 390, etc.) Ability to execute program / command code. 6) Other peer-to-peer communication device 135/121/21 (Fig. 12, Fig. 11, Fig. 2) ) And the ability to use the downloaded control code Ability to remotely control the device. In certain embodiments, a portion of the invention is one or more communications within a common network. It is realized as an integrated circuit that connects nodes interactively. Input to this integrated circuit A receiver that receives data and a transmitter that transmits output data (What are receivers and transmitters? In FIG. 2, it is collectively referred to as 38) and the processor 40 are collectively provided. Pu The Rossessa 40 is connected to the receiver / transmitter 38 and is the first common node 135/121. / 21 is the second common node 135/121/21 (Fig. 12, Fig. 11, Fig. 2) Connected interactively to (see related text). Processor 40 is the first and first 2 Common nodes 135/121/21 exist within a predetermined distance from each other, and the first node And when the needs and capabilities of the second common node 135/121/21 overlap , Activate communication link 26 between 1st and 2nd common nodes 135/121/21 It is equipped with a device. In this way, the personal business storage device 407 is a barcode reading pen 490 (33rd). (Figure) and can interact with other devices that assist in communication or dialogue. Ta Speaking of communication between buyer 452 (Fig. 30) and store 456, this kind of communication It can be done via a link. The present invention digitizes information and puts it in a device with formal elements in the wallet. To pay. The present invention further transfers peer-to-peer wiring from such a device to another. A machine that easily moves information via short-distance links (for example, link 26 in Fig. 1). Equipped with Noh. The present invention provides command code that adapts its actions to the environment. Can be accepted. For example, an automated teller machine (ATM) When interacting with achine), the display drawn on the personal business storage device 407 It can be a user interface with ATM. This is also when the action is manufactured Is not hard-coded in the personal business storage device 407 at the time of sale Actions are dynamically loaded into the personal business storage device 407 according to the situation, and the individual When the application stored in the business storage device 407 is canceled or completed It is a function that is erased at the same time. Figures 26 to 29 show portable hands for storing data and streamlining operations. It is a series of sketches of a portable digital device. Figures 26 and 27 show two aspects of the personal business storage device 407. It is a schematic diagram which shows the core function. Personal business storage device 407 is optional Display / Output Unit Panel 408, with some folding or hinged hierarchies 409 and softkey input unit panel 410,411,412,413,4 Has 14. As a result, the personal business storage device 407 can be expanded in multiple directions. Can display / output unit panel 408,409 and softkey input uni Each set of panels 410,411,412,413,414 is one domain Provides the function of 2 Domain foldout example It is shown in FIGS. 28 and 29. In FIG. 26, the upper panel, that is, the foldout 408, is the output display. Or a hardware compliant output unit, for example used as a speaker. Lower panel The 418 is a touch screen display or hardware compliant input unit. Knit eg button 410, trackball or microphone (the latter two) Is not shown). Below the bottom panel 418 is a row of options Button 410 controls the structure of the single-sided device functional domain. For example , Place the physical button 410 on the bottom, Launch or select to display different softkey input units on bottom panel 418 can do. The distinction between the top panel 408 and the bottom panel 418 is extremely simple This is an example, especially for personal business storage equipment with foldouts that are divided into upper and lower parts. Can be adapted to 407. Depending on the execution example, instead of up and down, or In addition, some have left and right sides. Top panel 408 also includes optional slide-out unit 416 Extend this to create a third panel 416 that works within a particular functional domain You can also do it. For example, extend the third panel 416 through handwriting recognition, etc. It can also be another input pad used to enter notes or notes. Wear. In a preferred embodiment, panels 408,409,410,411,412, 413,414,415,416,417,418 button selection and / also Is a touch type that enables handwriting input. For personal business storage device 407, A. Intercommunication nodes 21, 121 and / or 135 (Fig. 2, Fig. 11, Fig. 12) The wireless communication link 26 (see Figure and related text) is shown in Figure 1 and Figure 2. ), Barcode reader 490 (see Figure 33 below and related text) It is connected to (Te), which also has an inter-peer communication node 135/121/21. It functions as a point-touch panel writing element. By this connection Enables rapid, automated financial / data operations via personal operations storage 407 become. Of these barcode pens 490 for personal business storage 407 An example will be described in detail below. FIGS. 26 to 29 are different from the preferred embodiments of the personal business storage device 407. The drawing is shown. Examples of this configuration include Personal Digital Organizer and Electric There are two functional domains that work as a story. Figure 26 shows the persona of the two faces. Flip-up di on one surface that acts as a digital organizer A personal business storage device 407 equipped with a spray 408 is schematically illustrated. For personal use The personal digital organizer of the business storage device 407 is on the panel 408. Top panel 408 with output display 417 and touch softkey input Lower panel 415 with panel 418, one row of control / setting buttons 410, Slide-out panel 416 that acts as a mo-pad and reads barcodes With a pen 490 that can act as a touch panel writing element (No. 1 below) 33). FIG. 27 is another aspect of a preferred embodiment covering another functional domain acting as a telephone. Is schematically illustrated. This side is a flip-up panel that includes speaker 419 Has 409. The lower panel 413 is a softkey input that functions as a telephone button. Includes 421. Below the lower touch panel 413 There is a bottom row button 414 with some settings / control buttons and voice or its Includes microphones that receive other auditory inputs. FIG. 28 shows the top side view, which has two interpretations of the personal business storage device 407. Emphasize that it has a face and two functional domains. Fig. 28 mainly shows the telephone side Shown that flip-up sections 408,409 are placed on different faces To emphasize. Fig. 29 is the opposite side of Fig. 28, mainly personal digital. Shows the Tal Organizer side. Example 7 Figure 30 shows organizations 452 to 460 involved in financial processing, such as personal business storage. Between device 407 (Figs. 26-29) and some objects involved in financial processing Data exchange message example 462 ~ 476 sequence 450 and a specific financial office It is a figure which shows the data transfer which is related to the science. Personal business storage device 407 is for all With long-distance wireless connectivity, users interact with the device throughout the store It can be performed. Because of this enhanced communication function, the buyer is a good. It is possible to carry out business processing and agree to exchange confidential information. The following methodology preaches a store-assisted self-closing business system I will reveal. Retail items are purchased by the implicit actions of three organizations: Chi (1) buyers, (2) shops and (3) one or more financial institutions. Self-closing The business may be (i) electronic three-way transactions, including buyer, store and banking systems. Alternatively, (ii) it can be easily carried out in an electronic cash transaction between the buyer and the store. The system is either mode of electronic financial processing, ie (i) three-way trading. Or (ii) for simplified transactions between buyers and shops that enable cash exchange transactions Based on. The current system is implicitly defined and agreed upon for a particular purchase It is necessary to use a financial system. For example, the current credit card Users can get information from their credit card between the credit card institution and the store. Has an implicit agreement to read the information and carry out the business for purchase. With a recent invention Also implicitly defined infrastructure access, such as confidential electronic retrieval A paging system with a pull will continue to be used. The next step, shown in Figure 30, shows an example of financial processing used for three-way electronic purchases. Su. Process 450 is where buyer 452 barcodes on the product It begins with scanning at da 490 (Fig. 33) (block 462). This is magnetic information It can be an information or a common UPC barcode line. The buyer is in the scanning stage ( After executing block 462), financial processing begins (block 464). The financial process is a collection of buyers, shops and bank sources (in this case simply with the bank of the shop). It consists of a three-way mechanism that includes the buyer's bank). User 452 You must provide your bank account or credit card number, and bank source 45 8,460 help determine prices, store 456 controls inventory and confidentiality It is necessary to relay product information so that it can be done. After the store 456 explained the price and product information along with the buyer's bank information, the quotient Store 456 initiates banking request to store bank 458 (block 466) .. Bank 458 of the store then initiates proper financial processing with Bank 460 of the buyer (Block 468), but this is just a transfer that covers the required shopping price It is a request. Bank 458 of the store receives an acknowledgment of financial processing from the buyer's bank 460 Upon receipt (block 470), the information is processed for that store's account. Store Bank 458 sends an acknowledgment to store 456 (block 472). Store 456 Received a remittance acknowledgment (block 472) and adjusted for buyer 452 Send back information (block 474). Along with this acknowledgment, preferably the product code , Receipts and comprehensive product tags related to purchase transactions are sent to buyer 452 .. Buyer 452 is able to record financial processing information and a comprehensive product tag of the product Yes (block 476). Process 450 improves the financial processing system and buys Buyer 452 transfers information directly to the store with perfect control of information transfer in hand 452 To send and assists in banking as needed. Or , "Stored value electronic cash transactions" Electronic cash without interaction with the banking system at the time of purchase in a format commonly known as You can make a deal. The present invention improves the current method of confidential electronic services to provide an implicit financial system and Go away from the infrastructure and through the connection between buyer 452 and store 456 Move to a flexible financial system structure. Figure 31 shows a third party where buyer 452 and store 456 monitor or guarantee the transaction. The current method 480 using the financial institution 459 implicitly defined as is shown. No. Figure 32 by buyer 452 with the cooperation of store 456 and financial institution 458,460 Shows a new way 482 that transactions are started, controlled and completed. Buyer 452 To financial institution 459 composed of financial institution 458,460 Note that there is a subsidy for the program. In this case, the buyer 452 is the store 4 Using direct cash transfer to 56 (eg as illustrated in Figure 31) Absent. Figures 33 and 34 show examples of modified or enhanced business operations. Main departure Ming has two main parts: (i) the device and its dialogue (Fig. 33) and (ii) the bar. Code (3rd It can be explained as (Fig. 4). Fig. 33 is one of the personal business storage devices 407 (Fig. 27 and Fig. 28 above). Barcode reader 490 and telephone function 492 located on surface 409/413 This is an example of the structure of the pen 490 and the telephone function 492, respectively. , The function shown in Figure 12 and related texts, ie Device 21/121/1 Including 35. In Figure 33, the barcode reader 490 is in the shape of a regular pen. It is drawn and is simply called "Pen 490" below. Low power short range RF link 491 is phone 4 It exists between the 92 and the pen 490. All information read by the pen 490 is straightforward It will later be publicized to the telephone (or other device) 492. Phone 492 is pen 490 It can interpret the information received from and works on that information. Figure 34 is an example of message format 495, an implicit action. Some include barcodes. The most common form of barcoded information is UPC (Universal product code). UPC is block 49 Identify the product by giving it a unique identifier as shown in 6. .. However, UPCs usually do not have linguistic or action information encoded. I. The systems of the present invention provide additional information, especially blocks 497 (dial) and 4 Action commands as shown in 98 ("Dial" and "Wait for response") To the barcode Need to get. The information bar coded in blocks 497-498 is It is a sequence of pairs of verbs and objects called "implicit action barcodes"). Example 8 How to build implicit action barcodes such as 497,498 The example includes a barcode that describes: That is, (i) with respect to specific information "Start a purchase transaction" including a specific request); (ii) "Which product is the transaction?" "Name, "Transaction request" including implicit request such as "credit card number, address"; (iii) "required" A collection of information that describes a product or service with information that identifies the job offer and the payment method. Collection "; or (iv)" Add to Organizer List "ie, add this information to other a. A database that describes an action, service or product (eg Figure 2, Figure 1) 2 Put it in the memory 42,247 in the figure). For example, a wide range of discounted airfares where the user includes an implicit action barcode Suppose you see the announcement. The user uses this information as personal data storage business device 407 (No. 26). Scan and capture in Fig. 29). Different barcodes available Contains information about lights, dates, etc. and displays these data to the user Prompt and request to make one or more selections and send with other data Toga Included, as well as user identification information by name, photo, etc., and explanation of payment method Information (eg credit card number, bank account information, address, etc.) The request is included. A personal business storage device 407 contacts a travel agency on the barcode. Enough information to touch, such as phone or fax numbers, emails Address etc. are also included. The personal business storage device 407 displays flight information and allows the user to make a selection. In addition, travel agency, user and payment method information is included in the message. Incorporate. Personal business storage device 407 then or later phone or other (For example, 34 in Fig. 1; 21 in Fig. 11; 159 in Fig. 12) Upon touch, a message tailored to use the medium will be sent to the travel agent. Be done. The message includes the selected flight, number of people, their ID and payment. And / or contains billing information. Travel agency when these data are received It will be processed by the store to process flight reservations and payments. Financial institution Is confirmed by the travel agency or both. Example 9 Table 1 shows the access level corresponding to the data structure in the personal business storage device 407. This is a table of examples. The present invention can carry out various operations, and the financial processing is the same. It is one. With all these enhanced business possibilities, data structures are becoming more complex. To. It is necessary to specify and consider various levels of protection of personal information. Equipment and Yu Knits can "talk to each other", but exchange and modify only certain information There is a need or desire to be able to. Table 1 Access levels and meanings Level Access Level Examples and Meanings 0 Anonymous 1 Business abbreviation 2 social 3 intimacy 4 Confidential (don't just read and write) 5 Confidential (only tell, do not read or write) For these reasons, there are at least 6 levels of data protection: (i) Level 0-Anonymous, users exchange only information that leaves the identifier anonymous; (ii) Level 1-Business abbreviations, data exchanges are about business, not too much It's not human. For example, business card information. (iii) Level 2-Social, more information (at the "social" level) is exchanged. For example, a calendar for social work. (iv) Level 3-Intimacy, information has a more intimate nature, eg clothes size and home The date and time of the tribe's event. (v) Level 4-Confidential, data is protected as "confidential" and information cannot be read You can, but you must not write. Therefore, the person is certified to be approved by a third party Can convey information, such as authorized and critically protected financial records .. (vi) Level 5-Critical Confidential, Another Group of "Confidential Data", Information Authorized and Critical Built for items such as medical records and testimonials protected by. Also, the user Can communicate without being able to manipulate data values or read information. Fig. 35 shows the barcode reading pen 490 (Fig. 33) and personal business storage equipment. Barco from product 454 (Fig. 30) using the 407 (Figs. 26-29) It is a flow chart which shows the sequence example of the stage of process 500 which reads the information. Pu Rothes barcodes user 452 (Figure 30) on product 454 Started when reading with the reading pen 490 (block 503) (block 5) 01). This barcode is an implicit action barcode (Fig. 34 and Seki). (See continuous text) and implicit action Is to make a purchase on behalf of buyer 452. Personal business storage device 407 Draw the action code (block 505) and product information (block 507) put out. It is determined that the barcode information is not correctly received by the personal business storage device 407. If rejected (block 509), a signal is sent to the user (block 513) and it is already A warning is given to scan once, and it is restarted by scanning the barcode again. The process is stopped until it is done (block 503) (block 521). Barco If it is determined that the information has been received correctly (block 509), the personal business storage device Place 407 confirms the validity of the action code (block 515) and Axis Make sure that the Yong code is in an understandable word leaf. If the action code is valid, the personal business storage device 407 is a store device. Initiate a connection with (block 517) and send all required product and financial information Believe (block 519). This ends process 500 (block 521). If the action code is determined to be invalid (block 515), again Process 500 terminates (block 521). Fig. 36 shows the personal business storage device 407 (Figs. 26 to 29) and the store 4 A process for exchanging financial processing information with 56 (Fig. 30) or a store device / terminal. It is a flow chart which shows the sequence of the steps in 525. This algorithm Zum provides an improved way of exchanging financial treatment through stores as shown in Figure 32. Shown. In process 525, the personal business storage device 407 is a store terminal 456 (Fig. 30). Connect to (block 529) and start (block 529), Figure 31-Fig. 35 Send product and financial information as described in the text on the diagram (block) 531). The store terminal 546 is used for financial information, that is, the bank account of the store, the section of the store. Add gold address, store address, etc. (block 533). Purchase account information, product Collective information including code and store account information from store 456 to third party financial institution Sent to the terminal 458,460 to which it belongs (block 535). The store terminal 456 is Wait until you receive an acknowledgment from financial institution 458,460. Acknowledged If determined to have been made (block 537), store 456 is involved in the approved purchase Extract information (block 539). Purchase approved by financial institution 458,460 If determined to have been done (block 541), store 456 will receive a receipt and product code. Send back to the user, execute the purchase (block 543), process 525 ends Finish (block 545). Is it determined that no acknowledgment is received (block 537) or the purchase is gold If it is determined not to be approved by the intermediary (block 541), financial processing will be suspended. Process 525 terminates (block 545). Store 456 You can make a decision to seek another financial treatment. Fig. 37 shows the personal business storage device 407 (Figs. 26 to 29) and another organization. In process 550 to check the access level sent to and from the device It is a flow chart which shows the sequence of the steps. Shown in Table 1 and related text (above) As you can see, there are various access levels for the personal business storage device 407. That makes the data structure more complex. These various access levels correspond It is used to control the release of information in the data business. For example, first name When exchanging stabs, the owner of the personal business storage device 407 checks the access level. You need to click. Process 550 is started (block 554) and connected to another device Start with (block 556) (block 552). Process 550 of information Incorporation into transmit block (block 558) and access level check (Block 560) and is included. Determining appropriate, data access If it is determined that the level is not Level 1-Business Abbreviation-- Information is sent (block 564) and affected data is removed from the transmission (Block 562). When it is determined that further transmission is desirable (block 566), Control returns to block 558, otherwise process 550 terminates. Lock 568). Fig. 38 shows the personal business storage device 407 (Figs. 26 to 29) and another organization. In process 2600 to check the access level sent to and from the device It is still another flow diagram which shows still another sequence example of the stage. As the first example The various access levels in the personal business storage device 407 (see Table 1 above). Use to control the release of information about the corresponding data business. As a second example, When exchanging recommendations, the owner of the personal business storage device 407 checks the access level. You need to click. Process 2600 is started (block) with the start of business (block 572) 570), connection to another device (block 574), incorporation into the information transmission block Only (block 576), access level check (block 578) and de Sending information to connector 901/902 when the data access level is appropriate Proceed to the stage including (block 582). Data access level level 5- If not -Critical Confidential--, transmission is omitted (block 580). Further de Process 2600 blocks when it is determined that there is a data transmission (block 584) Go back to 576 and include data from another block, blocks 578-58 Perform the steps outlined in 4. It is determined that further data transmission is not desired Process 2600 ends (block 585). Personal business storage device 407 has many network interactions, Allows interaction with other elements in the capability addressable network, among others It is a versatile tool. The above examples 1 to 9 of the capacity addressable network As an example of another device is shown, it is intended to interact with the personal business storage device 407. Can be explained. The personal business storage device 407 is the telephone or data access described in Example 1. Personalized data about services can be maintained. This allows the individual User preferences, locations or numbers (Figs. 11-13, IUPLS134) Or roaming user preferences, locations, phone numbers and / or numbers (RUPLS1) Maintaining and storing personalized records describing any of 34) in a convenient way Can be done. For example, in Rent-A-Car 191 (Figs. 15 and 16), as shown in Example 2. Personalized information by the personal business storage device 407 carried by the approaching user Can be sent to vehicle 191. Alternatively, as shown in Example 3, entertainment Maintained in personal storage business equipment for media, such as television program verification preferences Send personal information to a nearby television set or system (Figure 17) I can trust you. Example 4 illustrates a more complex situation. Personal business storage device 407 is explained here Either a client or a service device in a confidential system that is revealed Can be done. For example, as a client of the confidential system in Example 4, the personal business storage device 40 7 Monitor and protect against theft or misplacement and misuse after theft or misplacement Can be done. Personal business storage device 407 as a server for the confidential system in Example 4 It can be used to set confidential information to other devices in the confidential system (Figs. 18 and 19). Wear. Example 5 shows the use of an interactive remote controller (Figs. 20-24). Is a functional domain that can be built in the personal business storage device 407. Individual The human business storage device 407 includes multiple functional domains (Figs. 26 to 29). Personal organizer and telephone are shown in Example 6, but remote controller Functions can also be added or replaced with the personal business storage device 407. FIG. 39 is a diagram showing a partial example of the binding key 2840. Join key 2480 Treated as a logical entity, its components distinguish it from untrained observers It can't be done, but it actually contains many parts. Device ID 2481 is the join key Coded for requesting device 901 (Figure 40) on which the 2480 is about to enter .. The best-by date 2482 is the coded date when the binding key 2480 becomes ineffective. Attached field. Key type 2483 is intended for use with join key 2480 This is the field to explain. See Figure 52 for more information on how the keys are used. I want to be. Other cryptographic information in the join key 2480 is stored in the cipher 2484 Will be done. FIG. 40 is a diagram showing a brief overview of the coupling process 900. This figure is essential Requesting device 901 (device for requesting capacity) and providing side device 902 (for requesting requesting device) A device that provides the ability to be performed accordingly). Request side device 901 and provider side equipment When the device 902 is in close proximity to each other, the requesting device 901 becomes the providing device 902. Be aware of its existence; this process is described with respect to the other figures below. Requesting device 901 Sends one or more binding keys 903,2480 to the provider device 902. Provider Device 902 is the join key 903,2480 sent by requesting device 901. Compare with one or more join keys 904,2480 stored in the donor device 902 To do. Binding key 903,2480 and provider sent by requesting device 901 If a match 905 is found between the join keys 904,2480 in device 902, it is suggested. Capability 911 related to the coupling key 915,2480 of the side device 902 is the requesting device 9 Unlocked for 01. Provided in connection with this binding key 904,2480 One or more capacities 911 stored in side device 902 (for example, 912,913) , 914). Upon successful join attempt 905, requesting device 901 unlocks capacity 911. And related to the join key 903,2480 in the requesting device 901 907 Need 90 Try to meet 6. 907 related to a specific join key 903,2480 There may be one or more needs 906 (eg 908,909,910). Need 906 on requesting device 901 matching capacity 911 on providing device 902 Each time, a call to capacity 911 on the providing device 902 is initiated by the requesting device 901. Will be done. FIG. 41 shows a message communicated between devices 901 and 902 in a preferred embodiment. Includes example 2499. Beacon Message 2500 is a device 901,90 For other devices 901,902 in detection zone 28 (Figure 1) by 2 It is a message sent regularly to announce its existence. In fact, -All devices 901,902 that send con messages say, "I'm here. I declare. Devices 901,902 send Beacon Message 2500 In a preferred embodiment, the device 901,902 is the requesting device 901. Is it, the provider device 902 (Fig. 38), or both? , Devices 901,902 are battery powered or public power grid Supplied from a less consuming power source such as, or the device 901,902 is portable Device or quiescent, frequency of other message traffic, device 9 Feedback received by 01,902 from instrument circuit 155 (Fig. 12), device Depends on the intended use of 901,902 and any measures of equipment 901,902 However, it may be variable due to multiple factors. Beacon Message 2500 contains opcode 2501. this is , Fixed to uniquely identify this message as Beacon Message 2500 Rui is an arbitrary pattern. ID2502 sends Beacon Message 2500 Identify the attached devices 901 and 902. Equipment that wants to communicate with this device 901,902 Places 901 and 902 must use this ID 2502. ID type 2503 is a device that sends Beacon message 2500 901, It is a pattern that identifies the characteristics of 902. ID address 2504 is optional A space placed in Beacon Message 2500 to describe the device address It is This is because devices 901,902 go through the gateway or Via Leh (eg Gateway 44 and related texts in Figures 2 and 12) This is convenient when communicating. Common message header 2510 is not a message, but another message An ingredient, something that is also included in the other messages below. Common message -Header 2510 contains opcode 2511. This is a common message Contains a fixed or arbitrary pattern that uniquely identifies the header 2510 To. This pattern is a message that includes the common message header 2510. It is variable depending on the The sender ID 2512 is the message header 2510 Identifies the sender of Beacon Message 2500 that incorporates. Sender ad Less 2513 is placed in the message to describe the optional device address It is a space to be taken. This is because devices 901,902 go through the gateway Or via a relay (eg gateway 44 in Figures 2, 12 and (See related text) Useful for communication. Sender device type 2514 Identifies the characteristics of devices 901,902 that send Beacon message 2500 It is a pattern to do. The target ID 2515 is which device 901,902 to which the message is addressed. To identify. The target address 2516 is the device to which the message is addressed 901, Beacon message 25 to describe the optional device address of 902 It is a space placed in 00. This is because devices 901,902 are gateways Through or through a relay (for example, the gateway shown in Fig. 2 and Fig. 12) (See 44 and related texts) Useful for communication. Device 901,902 identifies ping message 2520 Device when nothing is received from other devices 901,902 that communicate during the time period of This is the message sent by 901,902 (for example, Fig. 18 and Fig. 19). And related texts). This time period is in the preferred embodiment. Varies by devices 901,902 due to several factors. actually, This me The device 901,902 that sends the message to another device 901,902 is "still there. Are you in? " Ping message 2520 pings that message 252 Fixed or optional in opcode field 2511 that uniquely identifies 0 Common message header 2521 containing the pattern of (message header 251 (Similar to 0). Zing message 2525 , After device 901,902 receives ping message 2520, device 90 This is a message sent by 1,902. In other words, Jing Me Sage 2525 replies to Ping Message 2520. In fact, this message Device 901,902, which sends sage to other devices 901,902, says "Yes, not yet. I'm here. " Jing Message 2525 gin the message Opcode field 251 uniquely identified as message 2525 Common message header 2526 (contains a fixed or arbitrary pattern within 1) Consists of message header 2510). FIG. 42 further communicates between devices 901,902 in a preferred embodiment. Here are many example messages. Make bond message 253 0 means that the requesting device 901 (Fig. 38) is combined with the potential providing device 902 905. Sent by requesting device 901 when attempting Message. The first part 2531 of the join execution message 2530 joins the message. Opcode field 2511 uniquely identified as line message 2530 By common message header 2510 containing fixed or arbitrary patterns within It is composed of. The requesting device key 2532 is provided by the requesting device 901. The binding key 903 provided in Place 902. Join execution status message (make b ond status message) 2540 is sent to requesting device 901 by providing device 902. Join attempt initiated by join execution message 2530 sent to This is a message indicating the situation. Part 1 of join execution status message 2540 25 41 uniquely identifies the message as a join execution status message 2540. Contains fixed or arbitrary patterns in the opcode field 2511 Consists of common message header 2510. The requesting device key 2532 is the provider that the provider device 902 is currently reporting. The coupling key 903 provided to device 902 by requesting device 901. Result The mode 2543 indicates the status of the join attempt. In this situation, the join attempt was successful Whether or not it is included. Ability question message (ask capability message) 2550 illuminates ability 911 A message sent by requesting device 901 to providing device 902 to meet It is. Noh The first part 2551 of the power question message 2550 asks the message the ability question. In opcode field 2511 uniquely identified as sage 2550 By common message header 2510 containing fixed or arbitrary patterns It is composed. The requesting device key 2552 is the join key 904 to which the join is made. To. Ability number 2553 is a fixed or arbitrary that uniquely identifies the ability 911. It has a pattern. The tell capability message 2560 is a capability question message. A message sent by the providing device 902 to the requesting device 901 in response to the sage 2550. It's sage. The first part 2561 of the ability notification message 2560 is the message An opcode fee that uniquely identifies the page as the capability notification message 2560 Common message headers containing fixed or arbitrary patterns within the Ludo 2511 Equipped with 2510. The requesting device key 2562 is the join key 90 from which the join 905 is made. It is 3. Ability number 2563 is a fixed or fixed that uniquely identifies ability 911. It has an arbitrary pattern. Result code 2564, need 906 to capacity 911 Whether it corresponds (and / or is currently available on the providing device 902) Mark. Ability description 2565 is an optional description of ability 911. Ability real Line The sage (execute capability message) 2570 is capable on the provider device 902. A message sent by the requesting device 901 to the providing device 902 to activate the force 911. It's sage. The first part of the ability execution message 2570, 2571, puts the message into the ability. Opcode field 2511 uniquely identified as line message 2570 Equipped with a common message header 2510 containing fixed or arbitrary patterns within Eh. The requesting device key 2527 is the join key 90 from which the join 905 is made. It is 3. Ability number 2573 is a fixed or fixed that uniquely identifies the ability 911. With any pattern, ability parameter 2574 is given to these abilities 911 It has operating parameters that can be used. Ability Preamble 2575 gives instructions to be executed before Ability 911 is activated. Including. Using this, the equipment circuit in which the capability is before it goes into operation (eg Figure 2 Figure 4) 8; (Fig. 12, 155, etc.) state can also be set to a known state. ability For a further description of the preamble function, see the detailed description in Figure 50. I. Ability Post Amble 2576 gives instructions to be executed after the end of Ability 911 Including. Using this, the state of the equipment circuit at the end of capacity 911 is known. It can also be set to. For a further description of the ability post-amble feature, Please refer to the detailed explanation in Fig. 50. FIG. 43 is a diagram showing an example of data structure elements. Need table element 2580 Is a data item that stores information about one need 906 of requesting device 901. The need table element 2580 is stored on the requesting device 901. ability Code 2581 is a fixed or arbitrary pattern that uniquely identifies need 906. Equipped with Ability name 2582 has the original name of necessity 906. Enable / Able Flag 2583 is a must at this point for users of this device 901 Requirement Indicates whether 906 is enabled or disabled. passive / Active flag 2584, need 906 is active or not That is, it is automatically searched and executed without user interaction, or it is passive. Is there, i.e. the user must explicitly activate ability 911 on his own? To describe. The requesting device preamble 2585 has a need 906 capacity execution message Satisfied through sage (execute capability message) 848 (Fig. 51) Contains instructions to be previously executed on requesting device 901. Further information in this field For information, refer to the detailed explanation in Fig. 50. The requesting device Post Amble 2586 is provided by the requesting device 901 to the providing device 902. Contains instructions to be executed on requesting device 901 after separation from. This field For more information on, see the detailed description in Figure 50. Provider device Reamble 2587 is capable of the provider device 902 Contains a set of instructions that are executed on the providing device 902 before activating 911. this See the detailed description in Figure 50 for more information on the fields. Proposal In the side device post amble 2588, the provider side device 902 is from the request side device 901. Includes instructions to be executed on the providing device 902 after separation. This field For the information, refer to the detailed explanation in Fig. 50. Capacity table element 2590 relates to one capacity 911 of donor device 902. It has a data item to store information. Ability code 2591 uniquely identifies ability 911 It has a fixed or arbitrary pattern that identifies the object. Ability name 2583 is ability 9 It has 11 original names. Enable / Able Flag 2584 Indicates whether force 911 is enabled or disabled at this point. Physical constraint 2594 hard for requesting device 901 to use capacity 911 This field describes the restrictions on the wear. Logical constraint 2595 refers to the logical constraint imposed on the user of this ability 911. It is a field to be determined. For example, a particular file or feature is out of range (See, for example, Figure 37, Figure 38, Table 1 and related text). Capability Preamble 2596 runs on donor device 902 before activating the capability. Includes instructions to be. For more information on this field, see Figure 50 for more information. Ming Please refer. Capability Post Amble 2597 is divided by the provider device 902 from the requester device 901. Includes instructions to be executed on the providing device 902 after release. Further in this field For the information, refer to the detailed explanation in Fig. 50. Provider device Prean Bull 2598 is a donor device 90 before the donor device 902 activates capability 911. 2 Contains instructions executed on. For more information on this field, see # 5. 0 Please refer to the detailed explanation of the figure. Provider device Post Amble 2599 is the provider Performed on the providing device 902 after the device 902 has separated from the requesting device 901 Includes instructions. For more information on this field, see Figure 50 for more information. Please refer to. Ability command 2600 is a command about ability 911 itself Please refer to this. The need table 610 is a data structure that stores the need table element 2580. To be equipped. In this case, need table 610 is the line of need table element 2580. Shown as a form array, but with other table methods such as tree type, hashing , Coordination list and well-known to experts in software engineering The data structure of can also be adopted. The capacity table 620 has a data structure that stores the capacity table element 2590. Eh. In this case, capacity table 620 is a linear array of capacity table elements 2590. Shown as But other table methods, such as tree type, hashing, linkage list and so Adopt other data structures well known to experts in software engineering You can also do it. FIG. 44 is a diagram showing an example of data structure elements. Requester device table element 63 0 is a data item that stores information related to one join key 903,2480 Be prepared. This data structure is stored in the requesting device 901. Join key 631 , Join key 903,2480. Enable / Able Flag 6 32 enables the user of this device 901 to enable join key 631 at this point Mark whether it was disabled or disabled. Point to need table 633 Refer to the need table 610. The provider device table element 640 ranks the information associated with one join key 904. It has data items to be delivered. This data structure is stored in the provider device 901. .. The join key 641 is the join key 904. Enable / Able F The rug 642 allows the user of this device to enable join key 641 at this point. Mark whether it was disabled or disabled. Point to ability table 643 Refer to the capability table 620. The donor device table 650 is a stored provider device table element 651 ... A data structure that stores the provider device table element 640 as one of the 655. .. The requesting device table 660 is a stored requesting device table element 6. Data structure that stores the requesting device table element 630 as one of 51 ... 655 It is a structure. In this case, the donor device table 650 is the donor device table element 6. Shown as a linear array of 51 ... 655, but with other table methods, such as In Lee type, hashing, linkage list and software engineering Other data structures well known to those skilled in the art can also be adopted. Figure 45 shows the requesting device table 671 and the need table 672,673. Show the relationship. As mentioned above, the requesting device table 671 is in 661 ... 655. Needs table 67, including the corresponding requesting device table elements 676 ... 680 2 contains the need table elements 681 ... 685 corresponding to 611 ... 615 .. Need to correspond to 611 ... 615 Table element 686 ... 690 The need table 673 made is also illustrated. Requesting device table element 676 , Includes reference 674 for need table 672. This is the need table 6 It is done via a pointer to 33. In addition, requesting device table element 68 References to need table 673 from 0 are also illustrated. Other requesting device table It is illustrated that elements 677 ... 680 also refer to need table 674/5. Absent. FIG. 46 shows the donor device table 701 (FIG. 44 shows the donor device table 65. Similar to 0) and ability table 702,703 (similar to ability table 620 in Figure 43) Relationship with It is a figure which shows. As mentioned above, the donor device table 701 is the provider device table. The ability table 702 has the ability table element 711 with the elements 706 ... 710. ... with 715. In addition, it consists of capability table elements 716 ... 720 The ability table 703 to be used is also illustrated. The provider device table element 706 is capable. Contains reference 704 for force table 702. This is against capacity table 643 It is done via a pointer to. In addition, from the provider device table element 710 A reference to capacity table 703 is also illustrated. Other donor device table element 7 07 ... 710 is also not shown to refer to the capability table. FIG. 47 is a diagram showing an example of a data structure. Chat table element 730 , Stores information related to one device 901,902 in the chat space Includes data items. Chat space is all nearby devices 901,902 Defined as, devices 901,902 are in meaningful communication at that time. Gateway (Figure 44; Figure 12 159) or relay, with or without All devices capable of communicating via (Fig. 1 46; Fig. 12 159) 9 Defined as 01,902. This data structure is required by devices 901,902 A device even if it is composed of a side device 901, a provider device 902, or both. Stored in 901,902. Device ID 731 is device 901, in the chat space. It is an identifier of 902. Chat state 732 is a communication with devices 901 and 902. Define the situation. Valid chat states include (i) ignore and (ii) join. Combined The pointer to the table 733 is the join table 770 (explained in Figure 48 below). Is a reference to. The number of bonds 734 indicates the number of bonds currently active in this device. Describe. Timestamp 735 was communicated from this device 901,902 The clock value of the last time. Residual ping 736 is Jing Message 25 If 25 (Fig. 44) is not received from device 901,902, this device 90 Stores an integer that specifies how many times to try 1,902 awakenings. Join table element 740 stores information related to one device 901,902 Includes data items to do. Key 741 is a bond key to which bond 905 was made under it. -. Device ID 742 is the device knowledge of devices 901,902 indicated by coupling 905. Besshi. Bonded state 743 defines the status of bond 905. Valid join state There are (i) requesting equipment, (ii) providing equipment and (iii) pending. Mate Te A pointer to Bull 744 points to Mate Table 780 (explained below). Is a reference. The number of mates 745 is the need 906 and ability in this bond 905. An integer that specifies the number of matches with 911 (Fig. 51, Fig. 53, Fig. 57). .. Mate table element 750 is the source of this join 905 One match between the need for requesting device 901 and the capacity of providing device 902 in Contains data items that store information about. Providing device / requesting device table required The pointer to the element 751 is the provider device table element 640,651 (44th). Figure), 706 (Figure 46) or Requesting Device Table Elements 630,661 (Figure 44) (Fig.), 676 (Fig. 48). For necessity / ability table element 752 The pointer to the need table element 2580,611, depending on the join state 743 (Fig. 43), 681 (Fig. 45) or capability table elements 2590, 621 (Fig. 43) It is one of the references to (Fig. 43) and 711 (Fig. 46). Figure 48 shows table elements 761 ... 765,771 ... 775,781 ... Three data structures as one of 785 (i) chat table 760, (ii) join It is a figure which shows the table 770 and (iii) mate table 780 (Fig. 47). To. The chat table 760 stores the chat table element 730. Includes data structure. In this case, the chat table 760 is the chat table. Shown as a linear array of elements 761 ... 765, but with other table methods, even For example, tree type, hashing, linkage list and software engineering Other data structures well known to those skilled in the art can also be adopted. Join table 770 joins as one of join table elements 771 ... 775 Table element 740 (Fig. 47) Contains data structures to store. In this case, the join table 770 requires a join table Shown as a linear array of elements 771 ... 775, but with other table methods, such as For tree type, hashing, linkage list and software engineering Other data structures well known to the expert in the field can also be adopted. The mate table 780 is one of the mate table elements 781 ... 785. Contains a data structure that stores the mate table element 750 (Figure 47). this If the mate table 780 is a line of mate table elements 781 ... 785 Shown as a form array, but with other table methods such as tree type, hashing , Coordination list and well-known to experts in software engineering The data structure of can also be adopted. Figure 49 shows the chat table 791, the join table 792 and the mate table. The relationships in Table 793 are shown. Chat table 791 is a chat table Includes element 796 ... 801 (similar to Figure 47 chat table element 730) Only join table 792 is a join table element 802 ... 806 (join table) (Similar to element 740). In addition, the mate table element 807 ... 811 ( Mate table 79 composed of (similar to mate table element 750) 3 is illustrated. Chat table element 796 is join table 733 (4th) 7) via a pointer to Contains a reference 794 to the join table 792. Join table element 806 Contains reference 795 for mate table 793. This reference is a join table This is done via a pointer to 744. FIG. 50 is a diagram showing an outline of the pre-ambling and post-ambling instructions 820. is there. Figure 50 shows the need 823 on the requesting device 901 (the need 90 in Figure 40). 6) and capacity 824 on donor device 902 (similar to capacity 911 in Figure 40) Consistency with 825 is shown. Requesting device 901 has capacity execution message 2570 (4th) Before sending (Fig. 2) to satisfy the need 823, the requesting device 901 must first be required. Executes the instruction contained in the side-seeking device Preamble 827. The requesting device 901 Send capacity execution message 2570 to provider device 902. Ability execution message The 2570 includes the donor device pre-ambling 829 and the provider device post-ambling. It contains two sets of instructions called 830. When the provider device 902 receives the capacity execution message 2570, the capacity is first generated. Executes the instructions contained in Reamble 831. Second, the provider device 902 is provided. Executes the instructions contained in the side device preamble 829. Third, the provider device 9 02 activates capacity 824 itself. The providing side device 902 is the coupling 90 between the requesting side device 901 and the providing side device 902. Upon noticing that 5 was destroyed, the provider device 902 first had the capacity 911/824. To end. Second, the donor device 902 executes the instructions in the donor device post amble 830. To do. Third, the provider device 902 executes the instructions in the capability post amble 832. To do. The requesting device 901 couples between the requesting device 901 and the providing device 902. Upon noticing that the 905 has been destroyed, the requesting device 901 will post the requesting device post. Execute the instruction in the table 828. Figure 51 is provided with the requesting device 901 when opening the coupling 905 (Figure 40). The sequence of messages exchanged with the side device 902 (see also Figure 42). Shown is a message sequence chart 840. This sequence is a request The side device 901 is the beacon message 2501 of the provider device 902 (Fig. 41). ) Recognizes the provider device 902 to start. Existence of provider device 902 Upon recognizing, the requesting device 901 issues a join execution message 844 to the providing device 9 Attempts to open Bond 905 by sending to 02. The provider device 902 responds to the join execution status message 845 with this join key. -Indicates whether join 905 was performed via 2480 (see also Figure 39). Whether the join attempt succeeds or fails, the requesting device 901 connects to the providing device 902. The execution message 844 is repeatedly sent, and the requesting device 901 is the requesting device 9 Once for each enable binding key 2480 contained in 01 (ie acte) Eve Do this once for each of the bonds 905). Provider device 902 requires Corresponds to each of the join execution messages 844 sent by the requesting device 901. Respond with join execution status message 845. One or more couplings 905 are opened between the requesting device 901 and the providing device 902. Then, the requesting side device 901 requires the providing side device 902 to be the requesting side device 901. Determine if you have the ability 911 (see also Figure 40) to meet any of the 906s Refuse. For each of the combined needs 906 of the required enable The requesting device 901 sends the capability question message 846 to the providing device 902. .. The provider device 902 responds with the capability notification message 847/2560 and asks for it. Indicates whether the need to be 906 can be met by this donor device 902. Words In other words, each of the ability question message 846 and the ability notification message 847 is 1. In pairs, this is placed on the requesting device 901 in each of the active couplings 905. Repeat within the sequence once for each of the active needs of 906. The requesting device 901 is the requesting side achieved by the capability 911 of the providing device 902. For each need 906 of device 901, the provider device provides capacity execution message 848. Send to 902. Need for part of requesting device 901 906 and providing device 902 Ability execution message frame once every time the ability 911 and the ability of 911 are actively matched 848 will be sent. FIG. 52 shows the types of binding keys and illustrates their use in preferred embodiments. Includes the Matrix 850 to be revealed. First row of matrix 850 (block 851) Indicates the title of the column. The key type column (block 852) is a concatenation of each type. Identify the key 2480 and the intended use. The column of number of providers (block 853) is Indicates how many donor devices 902 accommodate this type of join key 2480. In the column of the number of requesting devices (block 854), how many requesting devices 901 are of this type. Indicates whether to accommodate the binding key 2480 (see also Figure 39). Column of meaning ( Block 855) describes the use of the join key 2480 in text. Matrix 850 row 2 (block 860) has only one donor device 902 Type device key 870 used to bind 905 to (block 871) The join key 2480 will be described. Device key 870 requires many (block 872) The requesting device 901 can have it, but all requesting devices 901 use it. And joins one and only (block 871) donor device 902. Row 3 (block 861) of matrix 860 offers many (block 875) Within the side device 902, but by one (block 876) requesting device 901 The join key 2480 of the type personal key 874 that is held only is described. Personal key -874 is used to identify individual users. Row 4 (block 862) of the matrix 850 provides many (block 879) proposals. Held by the side device 902, each device is owned by a person or entity (eg, a meeting). A type owned by the same owner, regardless of whether it is a company or synagogue) The join key 2480 of the owner key 878 is described. Required to have owner key 878 The number of seeking devices 901 is one or several (block 880). Usually the owner Key 878 has administrative priority, so the number of owner keys 878 is the highest It can be suppressed to a small limit. Row 5 (block 863) of matrix 850 provides many (block 883) More (block 884) requesting device 9 held by side device 902 Preaching the join key 2480 of type group key 882 held by 01 I will reveal. Group key 882 is a key for sharing the device. Row 6 of Matrix 850 (block 864) is of type hat key 886. The join key 2480 will be described. Hat Key offers many (Block 887) Held by side device 902, but the hat key 886 is one (block 8) 88) It is held only by the requesting device 888, and this device is an individual (personal key 874). Similarly). This access is for individuals using the Hat Key 886 Divide the priority into multiple categories according to the different roles they perform. Row 7 of matrix 850 (block 865) joins type role key 890 Key 2480 will be described. Role key 890 is a lot of (block 891) providing side equipment It is held in place 901 and also in many (block 892) requesting devices 902. Role The split key 890 is assigned to individuals who collectively play roles simultaneously or alternately. Be done. Similar to Group Key 882, but for a different purpose. Role key 890 The difference from the hat key 886 is that the hat key 886 divides the roles. Role key 890 shares one role, whereas it is used by only one person To deal with many individuals. Row 8 (block 866) of the matrix 850 is the type system key 894. The join key 2480 of is described. System key 894 has many (block 89) 5) Secured by the provider device 902 and many (block 896) requester devices 901. Be held. The system key 894 is a set of devices 901 and 902, both in one system. Used to logically group into stems. This system is a logical system Called mu. System key 894 is similar to, but identical to, group key 882. All donor devices 902 containing the system key 894 of the system have a special synergism. The case is different in the application having. Figure 53 shows the flow of process 999 for the main control loop of equipment 901,902. This is an example. Smell of preferred embodiments All peer devices 901,902 run a process similar to process 999. .. Process 999 begins by activating the internal timer of equipment 901,902. (Block 1001). Control then enters a non-terminating loop (block 1002). Loop 1002 polls the event to be processed (see Figures 42 and 43). , Process each event sequentially and repeat it. Control determines if Beacon Message 2500 is pending (blocks) 1003), when pending, control proceeds through branch point 1004, of the message Perform processing (block 1006; see Figure 61). Control then at branch point 1007 Return to the beginning of the loop through. If there are no pending Beacon Messages 2500 (1003), processing proceeds through branch point 1005, join execution status message 2 Determine if 540 is pending (block 1008). Control determines if join execution status message 2540 is pending (block) 1008) If pending, control will process the message via branch point 1009. Do the reason (block 1011; see Figure 57). Then control is via branch point 1012 And return to the beginning of the loop. Determined that there is no pending join execution status message 2540 When it is done (block 1008), the process proceeds through the fork 1010 and the ability notification message is displayed. Determine if Sage 2560 is pending (block 1013). Control determines if capability notification message 2560 is pending (block 1) 013) When pending, control processes the message via branch point 1014. Do (block 1016; see Figure 54). Then control is done via branch point 1017 Return to the beginning of the loop. If it is determined that there is no pending ability notification message 2560 (Block 1013), the process proceeds through the branch point 1015, and the internal timer has elapsed. Determine if (block 1018). Control determines if the internal timer has elapsed (block 1018) and if so Control handles events via branch point 1019 (block 1021; 6th 2 See Figure). Control then returns to the beginning of the loop via branch point 1022. The timer If it is determined that it has not passed (block 1018), processing is via branch point 1020. To determine if ping message 2520 is pending (block) 1023). Control determines if ping message 2520 is pending (block 1) 023) If pending, control will ping message through branch point 1024 Process 2520 (block 1026; see Figure 56). Next control is branch point 1 Return to the beginning of the loop via 027. Pending ping message 2520 If it is determined (block 1023), the process proceeds through the branch point 1025, and the process proceeds. Determine if message 2525 is pending Lock 1028). Control determines if Jing Message 2525 is pending (block 1) 028) When pending, control is Jing message via branch point 1029 Process 2525 (block 1031; see Figure 56). Next control is branch point 1 Return to the beginning of the loop via 032. Pending Jing Message 2525 If it is determined (block 1028), the process proceeds through the branch point 1030 and concludes. Determine if execute message 2530 is pending (block 1033). Control determines if join execution message 2530 is pending (block 1) 033) When pending, control joins message 25 via branch point 1034 Perform 30 operations (block 1036; see Figure 59). Next control is branch point 103 Return to the beginning of the loop via 7. Without pending join execution message 2530 Once determined (block 1033), processing proceeds through branch point 1035 and competence. Q Determine if message 2550 is pending (block 1038). Control determines if capability question message 2550 is pending (block 1) 038) When pending, control is capable question message via branch point 1039 Process 2550 (block 1041; see Figure 60). Next control is branch point 1 Return to the beginning of the loop via 042. Pending If it is determined that there is no ability question message 2550 (block 1038), the process is Proceed through branch point 1040 to see if capacity execution message 2570 is pending Judge (block 1043). Control determines if capability execution message 2570 is pending (block 1) 043) When pending, control has a capability execution message via branch point 1044 Process 2570 (block 1046; see Figure 58). Next control is branch point 1 Return to the beginning of the loop via 047. Pending ability execution message 2570 If it is determined to be (block 1043), the process is looped through branch point 1045. Go back to the beginning. FIG. 54 is an example of a flow chart showing the processing 1048 of the capacity notification message 2560. To. As for the ability notification message, the requesting device 901 sends the ability question message 2550. It is sent to the providing device 902 and arrives after the requesting device 902 responds. Process 1048 begins (block 1100), capability notification message 2560 Read the result code 2564 from (block 1102), and the provider device 902 is capable. Determine if force 911 can be supplied (block 1102). Need table element 2 580 is also checked for this need 906 and process 1048 needs It also determines if 906 is an active need (block 1102). these If both conditions are met, control is at branch point 110. Move through 3 and run the requesting device preamble 827 (block 110) Four). Capability execution message 2570 is sent to provider device 902 (block 1) 105). Process 1048 reverts (block 1106). Figure 55 shows process 1049 processing ping message 2520. This is an example of a flow chart. Ping messages have not been communicated by the target for a period of time , Is sent to the target device 901/902 by another connected device 901/902. When target device 901/902 receives ping message 2520, Jing Must respond with message 2525. The procedure begins (block 1200), sender of ping message 2520 9 01/902 is locked to chat table 760 (block 1201). Search results are queried (block 1202). Sender 901/902 chats When found in table 760, this device 901/902 is already sender 901 Recognizes / 902, and the time stamp of this device 901/902 is Updated in table 760 (block 1025) with the number of residual pings 736 Set to 2 (block 1207). In this example, the number of residual pings 736 is 2. Although set, any other number can be used in preferred embodiments. Target device 901/902 is considered isolated by the number of residual pings 736 Need to happen before The number of timeouts for an internal clock is determined. Determine the total time interval before separation Not only the number of ping messages 2520, but also the time set in the internal timer Note that the threshold is also involved. If sender 901/902 is not found in chat table 760 ( Block 1202), the first communication this is received from sender 901/902 Is. In other words, this message is as Beacon Message 2500 Handled (block 1206) and process related to beacon messages is invoked (block 1206) Block 1800). In either case, Jing Message 2525 is ping · Sent to sender 901/902 in response to message 2520 Lock 1208). After this, process 1049 reverts (block 1209). Figure 56 shows target device 901/902 in response to ping message 2520. This is an example of a flow chart showing the processing 1050 of the Jing message 2525 sent to. .. Process 1050 was sent by ping message 2520 sender 901/902 Begins when locked in chat table 760 (block 1300). Search Results are queried (block 1302), sender 901/902 chat table If found in Le 760, this device 901/902 is already the sender 901/9 Recognizing 02, control proceeds to block 1305 via branch point 1303. Timestamp of this device 901/902 is updated in chat table 760 New (block 1307). In this example, the number of residual pings 736 is set to 2 (block 1207), In a preferred embodiment, a constant or arbitrary number can be used. Remaining The number of retaining pings 736 considers the target device 901/902 to be separated. Determines the number of internal clock timeouts that must occur before Before separation It is not only the number of ping messages 2520 that determines the total time interval, but also the internal tie Note that the time threshold set in the machine is also involved. The sender is chat te If not found in the Bull 760 (block 1302), this is the sender 901 / This is the first communication received from 902. In other words, this is Beacon Me Treat as Sage 2500 (block 1306). After this, process 104 9 goes back (block 1308). Figure 57 shows the process involved in receiving join execution status message 2540 105. It is an example of a flow chart showing 1. The join execution status message is usually the requesting device 901. Sent by provider device 902 in response to join execution message 2530 from Is done. The join 905 described in the join execution status message 2540 is the join table. When locked in 740 (block 1401), process 1051 begins (block 1401) Block 1400). Search results are queried (block 140) 2), join 905 found in join table 740 (block 1402), join Required when execution status message 2530 indicates that join 905 was successful The seeking side device 901 connects with the providing side device 902. The difference between the specified conditions If not satisfied (block 1402), control proceeds through branch point 1404, Process 1051 reverts (block 1415). The state of bond 743 is the request side Changes in join table 740 for position 901 (block 1405), that is The connection 905 is the active connection, and this device 901 is connected as the requesting device 901. Participate in the continuation. Each need 906 by first selecting the first need 908 A loop is set to process under the current join key 2480 (block 140) 6). If there is no need 906 left to handle, control will take branch point 1408. Proceed through (block 1407), step back (block 1415) or Or block 1407 determines if the current need is enabled ( Block 1410) Transfer control. If not enabled, then need 90 9 ... is selected (block 1414). Where the current need 906 is enabled If so (block 1410), control proceeds through the fork 1412 and the ability question message Send the 2550 to the provider device 902. The next need 909 ... is selected ( At block 1414), control moves to the beginning of the loop (block 1407). Figure 58 shows the process 1052 for capacity execution message 2570. This is an example. Capability execution message combined with need 906 of requesting device 901 Under 905, each time the requesting device 902 matches capacity 911, the requesting device It is sent by 901 to the provider device 902. Process 1052 is preferably , Occurs within the donor device 902 and is initiated by the sender device 901/902 ( Block 1500). Join 905 described in ability execution message 2570 Locked on chat table 760 and join table 770 (block 1) 501). The search results are queried (block 1502), which is the requesting device 901. With a valid coupling of 905, control proceeds through branch point 1503 and the requesting device Corresponding key that decrypts the binding key 903 of 901 and accommodates it in the providing device 902 Compare with 904 (block 1505). If there are unsatisfied conditions (block 1) 052), control proceeds through branch point 1504 and process 1052 reverts. Lock 1516). If it is determined that the binding key 903 has been successfully decrypted (block 1) 506), the location of the specified ability 911 is identified (block 1509). Join If it is determined that the decryption of key 903 is unsuccessful, the ability execution message 2570 Is ignored and process 1052 reverts (block 1516). Ability 911 exists As soon as it is determined to be present and enabled (block 1510), capability 911 It will be started. ability Preamble 2596 is activated (block 1513) and the provider device preamble 2587 is launched (block 1514). Finally, the ability 911 itself is activated (Block 1515). If these conditions are not met, or ability 911 Process 1052 reverts after it is started (block 1516). Figure 59 shows the flow showing process 1053 for join execution message 2530. This is an example. The join execution message is the rice contained by the requesting device 901. For each lockable binding key 905, the requesting device 901 provides the providing device 902. Will be sent to. Process 1053 preferably occurs within the donor device 902. , Sender device 901/902 is locked to chat table 760 (bro It is started with the click 1601) (block 1600). Search results are queried (block) If the search is successful, this is the known device 901/902. If the search is unsuccessful, the state is set to "No ID found" (block 1611), Placed in the result code of join execution status message 2540 (block 1613) .. The join status message 2540 is then sent to requesting device 901 for the process. 1053 reverts (block 1614). If the search is successful (block 160) 2), the binding key 903 of the requesting device 901 is decrypted (block 1605) and provided. Compared to the corresponding key 904 contained in the side device 902. If it is determined that the binding key 903 has been successfully decrypted (block 1606), this new Join table element 740 created in join table 770 for new join 905 (Block 1609) and the state of process 1053 is set to "join successful" (Block 1610). If it is determined that the decryption of the binding key 903 is unsuccessful (B) Lock 1606), the state of process 1053 is set to "key not decrypted" (lock 1606) Block 1612). In either case, process 1053 has a join execution status message. Send sage 2540 to requesting device 901 (block 1613) and back (block 1613) Block 1614). Figure 60 shows the process 1054 for capability question message 2550. This is an example. The ability question message 2550 is the rice requested by the requesting device 901. Send to provider device 902 by requesting device 901 for each need Will be done. The moat described here is performed within the donor device 902. Process 1054 is started (block 1700) and senders 901/902 are selected. Matched within chat table 760 (block 1701). Search results are queried If the search is successful (block 1702), this is the provider device 902 previously The device 901/902 that communicated with the process 1054 proceeded to join Decrypt key 903 (block 1705). If the search is determined to be unsuccessful (block 1702), control is at branch point 170. Proceed through 4 and set the status to "ID not found" (block 1714). Status Is included in the result code of the ability notification message 2560 (block 1716). Capability notification message 2560 is sent to requesting device 901 (block 171) 6). Then process 1054 reverts (block 1717). If the search is determined to be successful (block 1702), control is at branch point 1703. Go through and decrypt the join key 903 of the requesting device 901 (block 170) Five). If the decryption of binding key 903 is determined to be unsuccessful (block 1706) , The state of process 1054 is set to "key not decrypted" (block 1715) After the process sent the capability notification message 2560 (block 1716) Go back with (block 1717). If it is determined that the binding key 903 has been successfully decrypted (block 1706), control Proceeds through branch point 1708 and finds the specified ability 911 (block) 1709). If the search result is tried (block 1718) and the search is unsuccessful, the state Is set to "No ability found" (block 1712) or the search is successful If, the state is set to "valid match" (block 1713). Ability notification Messe The page 2560 is sent back to the requesting device 901 (block 1716). afterwards, Process 1054 reverts Lock 1614). Figure 61 shows process 1055 for Beacon Message 2500. This is an example of a flow chart. Beacon messages are regularly sent by device 901/902 It will be sent to announce its existence. Process 1055 has potential requesting device 901 When the beacon message 2500 is received from the provider device 902, the requester device 9 It is preferably executed within 01. Process 1055 is started (block 1800) and sender (provider device 902) ) Is matched in chat table 760 (block 1801). Search results are If queried (block 1802) and the search was successful, this is the provider device 902. Is supposed to be the device 901/902 that is already aware of, and the control is at branch point 1804. Go through and update the time stamp of this device in chat table 760 And set the number of residual pings to 2. However, in a preferred embodiment, it is fixed. Rui can also use any integer. Process 1055 reverts (block) 1821). If the search does not provide a record of previous communication with this device 902 (block) 1803), device 901 does not recognize this device. Control is branching Proceed through point 1803 and for this device 902, chat table 760 A new chat table element 730 is created within (block 1805). Outfit Place 901,902 ties The stamp is set (block 1806). The number of residual pings is then set to 2 (block 1808). In this example, the pin The number is set to 2, but in preferred embodiments it is a fixed or arbitrary integer. Can be used. First binding key housed by this requesting device 901 903 is selected (block 1810) and accommodated by requesting device 901. Every 903 key is ready to loop. Next, the requesting device coupling to be processed It is determined if the key 903 is still present (block 1811). If not left , Control proceeds through branch point 1812 and process 1055 reverts (blocks) 1814). If not, the join key 903 is processed (block 1814). ). Branch point 181 if the current requesting device join key 903 is not enabled 5 allows you to select the next requesting device join key 903 (block 18) 17), control returns to the beginning of the loop (block 1811). Current requesting device coupling If key 903 is enabled (block 1814), control will take branch point 1816. Proceed through and create a new join table element 740 (block 1818). The join key state is set to "pending" (block 1819), then "join execution" The message is sent to the provider device 902 (block 1820). Then next The requesting device join key is selected (block 1817). Figure 62 shows the process that occurs when the internal timer has elapsed. This is an example of a flow chart showing the 1056. When this happens, the connected device 901,9 Check if any of 02 was separated. The procedure begins (block 1900) and is used first in chat table 760 The entry to be selected is selected (block 1901). Chat table to handle It is determined if there are still entries left (block 1903). No place If so, proceed to branch point 1904, reset the internal timer (block 1909), and Process 1056 reverts (block 1918). Chat table to handle If it is determined that there are still entries (block 1903), control is at branch point 19. Go through 05 and the timestamp of the current chat table element is the threshold Determine if it is too old (block 1906). In a preferred embodiment, the threshold is solid It may be a fixed value or an arbitrary value. If this threshold is exceeded, the access to try to revive the connection / bond 905 I have to wake up. If the threshold is not exceeded, control will reach branch point 1908. Proceed through, where the next chat table entry 740 is selected and processed (Block 1902). Exceeded the number of ping trials for this device 901/902 It is judged whether or not it was obtained (block 1910). If there is no residual ping, Is executed (block 1917, 63rd) See figure). If there is residual ping (block 1910), control is at branch point 1911 Proceed through and have a dialog with the desired device 901/902, or not Is simply determined to be in the chat space (block 1912). If you do not have a dialog with the desired device 901/902, at branch point 1913 Proceed to select the next chat table element 730 (block 1902). So If not, it has a meaningful dialog with the target device 901/902. , So control proceeds through branch point 1914 and ping message 2520 Sent to the desired device (block 1915). The number of residual pings is reduced (block) 1916), the next chat table entry is selected (block 190) 2). Figure 63 is an example flow diagram showing the process 1917 for separation. process Beginning in 1917 (block 2000), the coupling te for this device 901/902 The first join table element 740 in the table 760 is selected (block 2001) .. Determines if there are still join table elements 740 to process. Lock 2003). If not, proceed to branch point 2004 and process 1917 is original Return to (Block 2012). Determined that there are still join table elements 740 to process When broken (block 2003), control proceeds through branch point 2005 and joins 90. Whether the relationship in 5 is that of the provider device 902 or that of the requester device 901 Judge (Block 2006). For donor device 902, proceed to branch point 2007 to provide provider device separation process. (Figure 64) is executed (Block 2010). Minutes for requesting device 901 Proceeding to crossroads 2008, the requesting device separation process (Fig. 65) is executed (broth). 2011). Finally, both processes free the join table element 740. Lock 2009), the next join table element 740 is selected (block 2002) ). FIG. 64 is a flow diagram showing the process 1058 related to the separation of the provider device 902. This is an example. Process 1058 begins (block 2100) and the first of this join 905 1-mate table element 750 is selected (block 2101). Me to process Determines if table element 750 remains (block 2103) .. If not, proceed to branch point 2104 and process 1058 reverts (blocks) 2110). If it is determined that there are still mate table elements 750 to process ( Block 2103), control proceeds through branch point 2105, providing equipment post-a. Run amble 2588 (block 2106) and the ability post amble 2576 is real Will be done (block 2107). Mate table element 750 released (block 2108), the next mate table entry is selected (block 2109) ). Mate table element 750 to process is already If it is determined that there are no remaining processes, process 1058 reverts (block 2110). .. FIG. 65 is a flow chart showing the process 1059 related to the separation of the requesting device 901. This is an example. Process 1059 begins (block 2200) and the message about this join The first entry in the table is selected (block 2109). Should be processed Determines if mate table element 750 remains (block 220) 3). If not, proceed to branch point 2204 and process 1059 reverts (block) 2208). Determined that there are still mate table elements 750 to process And (block 2203), control proceeds through branch point 2205 and the requesting device post Run Amble 2586 (block 2206). Mate table element 750 Is released (block 2207). Mate table element 750 to process If it is determined that there is no remaining (block 2203), process 1059 is reverted. (Block 2208). In short, the present invention is networked with other data storage business devices and networked. With improved personal storage business equipment that can interact with it through the Provide a corresponding method. This network is a huge and diverse service To interconnect multiple everyday electronic devices, including mobile and portable devices Suitable for. Network ads for network-specific devices to make connections response No empirical boot and set-up in this network No up procedure is required. You don't need a device address to open a connection, but you open a meaningful communication The device name must be known before the information can be exchanged. this For the device or peer name, one device or peer 20 to another device or peer 2 It may be a unique identifier that can be uniquely distinguished from 0. As a result Minimal user involvement is required to connect to a, and peers routinely Can connect to a new peer. By connecting such devices, you can physically give and receive money, and you can use it as a card. Electronic transactions can be executed without the need to charge. User preference Depending on the situation, you may or may not exchange the information as it appears on your business card. Network connections are formed based on proximity, and unique network-wide ads Network because it is based on evaluation of necessity and ability, not less coding -Node addressing can be dynamically constructed. Although preferred embodiments of the present invention have been illustrated and described in detail, the spirit or appendix of the present invention has been described. It will be apparent to those skilled in the art that various modifications can be made without departing from the scope of the attached claims. It will be white.