Network systems and processing methods
Patent Information
- Application Number
- TW114151585
- Authority / Receiving Office
- TW · TW
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-04-19
- Filing Date
- 2020-04-17
- Publication Date
- 2026-11-01
- Estimated Expiration
- 2040-04-16
AI Technical Summary
Existing technologies struggle to accurately determine the location of devices connected to networks due to the limitations of assigning arbitrary IP addresses, making it difficult to provide precise location-based services.
A network system utilizing devices with authenticated IP addresses, each equipped with a communication unit, storage unit for electronic authentication, and a determination unit to verify IP addresses based on public keys, along with a certification authority to manage and sign electronic certificates, ensuring accurate location information.
Enables precise determination and management of device locations, facilitating secure and flexible connectivity for various services by using certified location information.
Smart Images

Figure TWG2TB001919263_001 
Figure TWG2TB001919263_002 
Figure TWG2TB001919263_003
Abstract
Description
Technical Field
[0001] This disclosure relates to a network system consisting of devices having authenticated IP addresses, the devices thereon, and processing methods within the network system. Prior Technology
[0002] Recent advancements in Information and Communication Technology (ICT) have been remarkable. Devices connected to networks such as the Internet are no longer limited to familiar information processing devices like personal computers or smartphones, but have expanded to a wide variety of things. This technological trend is known as the "Internet of Things (IoT)," with various technologies and services constantly being proposed and applied. In the future, it is conceivable that billions of people and tens or trillions of devices on Earth will be simultaneously connected. To realize such a networked world, solutions that enable simpler, more secure, and more flexible connectivity are essential.
[0003] Information such as the location of such devices is important when providing various services. For example, Japanese Patent Publication No. 2012-504285 (Patent Document 1) discloses a technology for identifying the actual physical location of computers, mobile devices, website visitors, or other entities connected to the network: physical location. In particular, Patent Document 1 discloses a technology that supports updating location information along with changes in the IP (Internet Protocol) address assigned to a typical home customer.
[0004] Patent Document 1: Japanese Patent Publication No. 2012-504285
[0005] As disclosed in the aforementioned Patent Document 1, due to the limitation of assigning arbitrary IP addresses to the software framework of the device, it is difficult to accurately determine the location information of the device.
[0006] This disclosure provides a solution that addresses such problems while offering a variety of services that utilize location information by employing a software framework that uses authenticated IP addresses. Summary of the Invention
[0007] According to the form disclosed herein, a network system comprising a plurality of devices is provided, each device including: a communication unit for data communication with other devices; a storage unit for storing electronic authentication including a public key used to determine the IP address of its own device; and a determination unit for determining the IP addresses of other devices based on the public key contained in the electronic authentication received from other devices. The electronic authentication includes location information associated with the corresponding device.
[0008] Location information can display any region resulting from the segmentation of regional hierarchies.
[0009] Location information can consist of codes that reflect the hierarchical structure of the area being the object. Any device among a plurality of devices may request other devices connected to a region of a higher hierarchy than the region indicated by the location information connected to itself, which should be set in the location information of its own device.
[0010] The network system may further include: a certification authority, which responds to a request from any of the plurality of devices and signs an electronic certificate that should be stored on the requester's side.
[0011] After any of the multiple devices exchanges electronic authentication with other devices to establish a meeting, it can send information generated or collected by its own device to the other devices.
[0012] A first device among a plurality of devices manages resources connected to it and can allocate at least a portion of the managed resources in response to requests from a second device among the plurality of devices. Information related to resource allocation can be shared between the first device and the second device.
[0013] Any of the plurality of devices can respond to a request for the current location from other devices by answering specific information used to identify the device associated with that current location.
[0014] Any one of the multiple devices can have the function of managing value, which becomes the consideration paid for goods and services.
[0015] According to other embodiments of this disclosure, an apparatus for constituting a network system is provided. The apparatus includes: a communication unit for data communication with other devices; a storage unit for storing an electronic authentication certificate including a public key used to determine the IP address of the device itself; and a determination unit for determining the IP addresses of other devices based on the public key contained in the electronic authentication certificate received from other devices. The electronic authentication certificate includes location information associated with the corresponding device.
[0016] According to another embodiment of this disclosure, a processing method for use in a network system including a first device and a second device is provided. The processing method includes: the first device sending a first electronic authentication, including a first public key used to determine the IP address of the first device, to the second device; the second device determining the IP address of the first device based on the first public key contained in the first electronic authentication received from the first device; the second device sending a second electronic authentication, including a second public key used to determine the IP address of the second device, to the first device; and the first device determining the IP address of the second device based on the second public key contained in the second electronic authentication received from the second device. The electronic authentication includes location information associated with the corresponding device.
[0017] According to this disclosure, it is possible to obtain the device's certified location information while providing a variety of services using the certified location information. Simple Explanation of the Diagram
[0018] Figure 1 is a schematic diagram showing an example of the overall architecture of a network system according to this embodiment. Figure 2 shows a schematic diagram of an example hardware architecture of a device included in a network system according to this embodiment. Figure 3 illustrates an example of IP address authentication processing in a network system according to this embodiment. Figure 4 shows an example of electronic authentication used in a network system according to this embodiment. Figure 5 is a schematic diagram illustrating the area ID used in the network system according to this embodiment. Figure 6 is a schematic diagram illustrating the coding system of area IDs used in the network system according to this embodiment. Figure 7 is a schematic diagram illustrating the processing related to setting the area ID in the network system according to this embodiment. Figure 8 shows a schematic diagram of an example of an application that uses location information provided by the network system according to this embodiment. Fig. 9 is a timing diagram showing processing steps for implementing the application shown in Fig. 8. Fig. 10 is a schematic diagram showing another example of an application using position information provided by the network system according to the present embodiment. Fig. 11 is a schematic diagram showing an example of a system architecture for implementing the application shown in Fig. 10. Fig. 12 is a schematic diagram for explaining resource management in the application shown in Fig. 10. Fig. 13 shows an example of ticket information used in the application shown in Fig. 10. Fig. 14 is a sequence diagram showing processing steps for implementing the application shown in Fig. 10. Fig. 15 is a schematic diagram showing still another example of an application using position information provided by the network system according to the present embodiment. Fig. 16 is a schematic diagram showing path selection using the application shown in Fig. 15. Fig. 17 is a timing diagram showing processing steps for implementing the application shown in Fig. 15. Embodiment
[0019] Embodiments of the present disclosure will be described in detail with reference to the drawings. In addition, the same or corresponding parts in the figures are denoted by the same reference numerals, and repeated descriptions are omitted.
[0020] <A. Overall Architecture of Network System 1> First, the overall architecture of the network system 1 according to the present embodiment will be described. The network system 1 has a function of managing and providing position information of one or more devices.
[0021] Fig. 1 is a schematic diagram showing an example of the overall architecture of the network system 1 according to the present embodiment. Referring to Fig. 1, the network system 1 includes a plurality of devices 10, and each device 10 is linked to a physical position or area. The position or area linked to each device 10 may be the position or area where each device 10 is actually located, or may be the position or area of the management or service provided by each device 10.
[0022] In the example shown in Fig. 1, linked to three areas A, B and C, there are devices 10A1, 10B1 and 10C1. Area A further has devices 10A2, 10A3 and 10A4; area B further has devices 10B2, 10B3, 10B4 and 10B5; area C further has devices 10C2, 10C3 and 10C4. In addition, each device may be simply collectively referred to as "device 10" sometimes.
[0023] In the network system 1 of this embodiment, the location information connected to each device 10 can be determined and provided.
[0024] Each device 10 has an authenticated IP address. In this specification, "authenticated IP address" refers to the state that guarantees the legitimacy of the IP address held by each device 10 to the communication partner or a third party. More specifically, "authenticated IP address" refers to an IP address generated by an irreversible cryptographic hash function and directly or indirectly authenticated by the authentication authority 2 (details will be described later). Using such "authenticated IP addresses" ensures that the IP addresses used by each device 10 for data communication are not spoofed.
[0025] As a result, any device 10 included in network system 1 will be uniquely identified based on the IP address of each device 10. That is, because the IP address of each device is itself identification information, location information and associated information can be determined and provided based on the identification information (i.e., IP address) of each device 10.
[0026] An IP address is assumed to be a public IP address that can be used for data communication between devices 10 connected to the network, but it can also be a private IP address used only within a specific network. The number of bits constituting an IP address varies depending on the version. The currently defined IPv4 (Internet Protocol Version 4) specifies a 32-bit address range, while the currently defined IPv6 (Internet Protocol Version 6) specifies a 128-bit address range. This embodiment will primarily describe IP addresses based on IPv6. However, this disclosure can also be applied to network addresses defined with more bits or fewer bits.
[0027] The term "device" in this specification includes any device that has the function of communicating data with other devices using its own IP address. Device 10 is sometimes configured as a standalone communication device, sometimes as part of an object, or sometimes assembled into an object.
[0028] More specifically, device 10 can be any of the following: a personal computer, a smartphone, a tablet computer, or a wearable device (such as a smartwatch or AR glasses) installed on the user's body (e.g., wrist or head). Alternatively, device 10 can be a smart home appliance, a connected car, a control machine installed in a factory, or a part thereof.
[0029] The network system 1 may further comprise one or more certification authorities 2. Each certification authority 2 may be a computer formed by one or more servers. The one or more certification authorities 2 may also be used to certify the IP address of each device 10. However, any device 10 may also be responsible for all or part of the functions provided by the certification authority 2.
[0030] In the network system 1 according to the present embodiment, between the devices 10, and between the devices 10 and the certification authority 2, are connected via any wired communication or wireless communication in a manner enabling data communication. A type of peer-to-peer connection is used for communication between the devices 10 and communication between the devices 10 and the certification authority 2. Any protocol including TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) can be adopted for this communication.
[0031] The devices 10 and the certification authority 2 connected to the network can each be regarded as "nodes" of the network, and in the following description, each device 10 and the certification authority 2 are sometimes referred to as "nodes".
[0032] <B. Example of Hardware Architecture of Device 10> Next, an example of the hardware architecture of the device 10 included in the network system 1 according to the present embodiment will be described.
[0033] Figure 2 is a schematic diagram showing an example of the hardware architecture of the device 10 included in the network system 1 according to the present embodiment. Referring to Figure 2, the main component of the device 10 includes processing circuitry, that is, the control unit 110.
[0034] The control unit 110 is a computing entity used to provide and process functions according to this embodiment. The control unit 110 can be an architecture using the processor and memory shown in Figure 2, where the processor executes computer-readable instructions stored in the memory. Alternatively, the control unit 110 can be implemented using hard-wired logic circuits such as an ASIC (Application Specific Integrated Circuit) in which circuitry equivalent to computer-readable instructions is assembled. Alternatively, the control unit 110 can be implemented on an FPGA (field-programmable gate array) to implement circuitry equivalent to computer-readable instructions. Furthermore, the control unit 110 can be implemented by appropriately combining processors and memory, ASICs, FPGAs, etc.
[0035] In the architecture using the processor and memory shown in Figure 2, the control unit 110 includes a processor 102, main memory 104, storage 106, and ROM (Read Only Memory) 108.
[0036] The processor 102 is a computing circuit that sequentially reads and executes computer-readable commands. The processor 102 may be configured as a CPU (Central Processing Unit), MPU (Micro Processing Unit), GPU (Graphics Processing Unit), etc. The control unit 110 (multi-processor architecture) may also be implemented using a plurality of processors 102, or the control unit 110 (multi-core architecture) may be implemented using a processor with a plurality of cores.
[0037] The main memory 104 is a volatile storage device such as DRAM (Dynamic Random Access Memory) or SRAM (Static Random Access Memory). The processor 102 expands the program specified in various programs stored in the memory 106 or ROM 108 on the main memory 104 and operates in conjunction with the main memory 104 to realize various processes according to this embodiment.
[0038] Storage 106 is a non-volatile storage device such as HDD (Hard Disk Drive), SSD (Solid State Drive), or flash memory. Storage 106 stores various programs executed by processor 102 or various data described later.
[0039] ROM 108 permanently stores various programs or data executed by processor 102.
[0040] The device 10 further includes a network interface 120 for connecting the device 10 to a network. The network interface 120 is equivalent to a communication unit for data communication with other devices 10 through a network.
[0041] Network interface 120 may include wired connection terminals such as Ethernet (trademarked) ports, USB (Universal Serial Bus) ports, IEEE 1394 serial ports, or traditional parallel ports. Alternatively, network interface 120 may also include processing circuitry and antennas for wireless communication with devices, routers, mobile base stations, etc. The wireless communication supported by network interface 120 may be, for example, any of Wi-Fi (trademarked), Bluetooth (trademarked), ZigBee (trademarked), LPWA (Low Power Wide Area), GSM (trademarked), W-CDMA, CDMA200, LTE (Long Term Evolution), or 5G mobile communication systems.
[0042] The device 10 may also include an internal interface 130, an input section 140, and an output section 150 as optional components.
[0043] The internal interface 130 enables data communication with the object when the device 10 is part of or assembled into an object. The internal interface 130 may include, for example, wired connection terminals such as a USB (Universal Serial Bus) port, an IEEE 1394 serial port, or a conventional parallel port. Alternatively, the internal interface 130 may also include circuitry for reading electrical signals, such as an analog-to-digital converter.
[0044] The input unit 140 is a component used to accept input operations from the user of the operating device 10. The input unit 140 may also be, for example, a keyboard, a mouse, a touch panel disposed on a display device, or operation buttons disposed on the frame of the device 10.
[0045] The output unit 150 is a component used to display the processing results of the processor 102 to the outside. The output unit 150 can also be, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display. Alternatively, the output unit 150 can be a head-mounted display worn on the user's head, or a projector that projects images onto a screen. Or, the output unit 150 can also be an indicator disposed within the frame of the device 10.
[0046] The input section 140 and the output section 150 are optional components, so they can also be connected from outside the device 10 via any interface such as USB.
[0047] Device 10 can also be used as a component to read various programs and / or data from non-transitory media that store various programs (computer-readable commands) and / or various data. The media can also be optical media such as DVD (Digital Versatile Disc), semiconductor media such as USB memory, etc.
[0048] Alternatively, various programs and / or data can be installed on device 10 without using media, and the necessary programs and data can be installed on device 10 from a distribution server on the network. In this case, the necessary programs and data are obtained through network interface 120.
[0049] The control unit 110 is responsible for providing and processing the functions according to this embodiment. The scope of this application includes at least the hardware and / or software used to implement the control unit 110. The hardware is not limited to the architecture composed of a processor and memory as described above, but may also include hard-wired circuitry using an ASIC or an architecture using an FPGA. That is, the control unit 110 can be implemented by installing a program into a general-purpose computer or as a dedicated chip.
[0050] Furthermore, the software executed by the processor can not only be distributed through media, but can also be appropriately downloaded through distribution servers.
[0051] Furthermore, the architecture used to implement the function provision and processing execution according to this embodiment is not limited to the control unit 110 shown in Figure 2, and any technology appropriate to the era in which it is to be implemented can be used.
[0052] <C·Authenticated IP Address>Next, an example of an implementation method of an authenticated IP address in the network system 1 according to the present embodiment will be described.
[0053] In the network system 1 according to the present embodiment, as an example, a public key infrastructure (PKI) is used to authenticate the IP address of each device 10.
[0054] Figure 3 is used to explain an example of IP address authentication processing in the network system 1 according to the present embodiment. Referring to Figure 3, the device 10 has a key pair consisting of a secret key 160 and a public key 162. A hash value 166 is calculated by inputting the public key 162 into a predetermined hash function 164, and all or part of this calculated hash value 166 is used as the IP address 168 of the device 10.
[0055] By sharing the predetermined hash function 164 among the devices 10, the unique transmission source of the public key 162, that is, the IP address 168 of the device 10 can be determined based on the public key 162 obtained from another device 10. The public key 162 is transmitted together with the electronic certificate 170 or incorporated into the electronic certificate 170, and the validity of the public key (that is, the IP address 168 to be determined) can be ensured based on the electronic certificate 170. That is, each device 10 has a logic that, by sharing the predetermined hash function 164 among the devices 10, determines the IP address of the other device based on the public key 162 included in the electronic certificate 170 received from the other device 10.
[0056] As described above, in the network system 1 according to the present embodiment, the IP address 168 itself can be authenticated, and by having such an authenticated IP address 168 retained in the device body, an independent network can be constructed without using statically or dynamically allocated IP addresses for each device.
[0057] As the key pair, the secret key 160 and the public key 162 may be generated by the device 10 itself, or may be provided from the outside and pre-stored in the device 10. When provided from the outside, the device 10 may also be configured to only obtain the secret key 160 and generate the public key 162 by itself.
[0058] As an example of a method for generating the secret key 160 and public key 162 of a key pair, a predetermined length of bit array (e.g., 512 bits) generated by a random number generator can be used as the secret key 160, and simultaneously, a predetermined length of bit array (e.g., 256 bits) can be generated from the secret key 160 using a known cryptographic algorithm (e.g., elliptic curve cryptography). Alternatively, if the device 10 itself generates the key pair, the random number generator can be implemented using functions provided by the OS, or it can be implemented using hard-wired circuitry such as an ASIC.
[0059] Hash function 164 can use known irreversible cryptographic hash functions (such as BLAKE). Hash function 164 calculates a hash value 166 composed of a given length of bits (such as 256 bits).
[0060] The hash function 164 can accept not only the public key 162, but also any keyword. As an arbitrary keyword, a message linking to an established organization can also be used. The message linking to an established organization can also include information containing the trademark name of that established organization. For example, a registered trademark name owned by an established organization (e.g., "connectFree") can be used as the keyword input to the hash function 164. By adopting this installation method, it is possible to prevent third parties outside the established organization from implementing the network system 1 and associated methods or programs according to this embodiment without the permission of the established organization.
[0061] All or part of the hash value 166 calculated by hash function 164 will be used as IP address 168. For example, if the hash value 166 is 256 bits (64 bits in hexadecimal representation), any 32 bits (e.g., the first 32 bits) of the 64-bit hash value 166 can be used as the corresponding IPv6 IP address 168 (128 bits). Alternatively, the first 8 bits of the 64-bit hash value 166 can be used as the corresponding IPv4 IP address 168 (32 bits).
[0062] Alternatively, one could consider mapping the IPv6 address 168 (128 bits) to the hash function 164 and calculating the 128-bit hash value 166. In this case, all calculated hash values 166 could be assigned to the corresponding IPv6 address 168 (128 bits).
[0063] In addition, the determined IP address may also contain pre-determined specific intrinsic values (intrinsic text).
[0064] As an example, the first two digits (the first and second digits counting from the beginning) of the hexadecimal IP address 168 can be fixed to a predetermined set of characters (e.g., "FC"). As another example, the type of the display device 10 (type-specific information) can be embedded in the third and fourth digits counting from the beginning of the hexadecimal IP address 168.
[0065] Typically, hash function 164 is a one-way function, so it cannot be used to derive public key 162 from IP address 168. Therefore, a random number generator can be used to repeatedly generate secret key 160 and public key 162 until the determined IP address 168 meets the given conditions (in which case, all or part of the first 4 bits become the predetermined value).
[0066] In this way, by including a predetermined, specific value (e.g., the first two bits are "FC") in the IP address 168, a third party can determine whether the IP address 168 of device 10 is determined by device 10 itself. Furthermore, by including a value indicating the type of display device 10 in the IP address 168, a third party can identify the type of device 10 from the determined IP address 168.
[0067] Figure 4 shows an example of the electronic authentication 170 used in the network system 1 according to this embodiment. Each device 10 holds the electronic authentication 170 shown in Figure 4 and sends it to other devices 10 as needed. The electronic authentication 170 is typically stored in the memory 106 or ROM 108 of the device 10 (refer to Figure 2). That is, the memory 106 or ROM 108 of the device 10 corresponds to the storage unit storing the electronic authentication 170.
[0068] The electronic certificate 170 shown in Figure 4 can be pre-generated by the certification authority 2 and provided to each device 10, or it can be generated by each device 10 itself (however, the certification authority signature will become the signature of the device 10 itself). When the certification authority 2 issues the electronic certificate 170, the device 10 issues its own public key 162 and also sends an electronic certificate issuance request (hereinafter also referred to as "certification signature request") to the certification authority 2. The certification authority 2 responds to the certification signature request received from the device 10, registers the public key 162, and issues the electronic certificate 170, which includes the certification authority signature 178 generated according to a predetermined algorithm. That is, the certification authority 2 responds to the certification signature request from a device and signs the electronic certificate 170 that should be stored on the requesting end.
[0069] Figure 4 shows, as an example, an electronic certificate 170 in accordance with the X.509v3 authentication format. More specifically, referring to Figure 4, the electronic certificate 170 held by each device 10 includes version information 171, serial number 172, signature algorithm 173, issuer identifier 174, validity period 175, subject identifier 176, public key 162, certification authority signature 178, and extension information 180.
[0070] Version information 171 displays the version information of the authentication format. Serial number 172 displays the serial number of the issuing entity (Certification Authority 2 or device 10) of electronic authentication 170. Signature algorithm 173 displays the algorithm used to generate the Certification Authority signature 178 included in electronic authentication 170. Issuer identifier 174 displays information about the issuing entity (Certification Authority 2 or device 10) of a specific electronic authentication 170. Validity period 175 displays the validity period of electronic authentication 170. Subject identifier 176 displays information about the recipient of a specific electronic authentication 170 (usually the device 10 holding electronic authentication 170). Public key 162 is the public key 162 possessed by the device 10 holding electronic authentication 170, used to determine the IP address of the device itself.
[0071] Certification Authority Signature 178 is a signature (hash value) generated by Certification Authority 2. Extended Information 180 can contain arbitrary information. In the network system 1 according to this embodiment, a region ID 182 (details will be described later) is included, displaying location information connected to each device 10. Region ID 182 contains location information connected to the device storing the electronic certificate 170 (i.e., the device corresponding to region ID 182). By referring to the region ID 182 included in the electronic certificate 170, the location or range of each device 10 can be easily identified.
[0072] <D·Area ID>Next, the details of the area ID used in the network system 1 according to the present embodiment will be described.
[0073] (d1: Determination and system of area ID) FIG. 5 is a schematic diagram for explaining the area ID used in the network system 1 according to the present embodiment. Referring to FIG. 5, in the present embodiment, a range is hierarchically divided according to requirements. FIG. 5 shows an example using quaternary spatial division, but the present invention is not limited thereto, and any division method can be used.
[0074] More specifically, the areas for which area IDs can be set can be divided into four areas A to D. That is, the uppermost area IDs in FIG. 5 are "A", "B", "C", and "D".
[0075] Each divided area can be further divided into 4 blocks. In the example shown in FIG. 5, the area with the area ID "A" is further divided into 4 blocks. The area IDs of the respective divided areas are "AA", "AB", "AC", and "AD".
[0076] The area with the area ID "AA" is further divided into 4 blocks. The area IDs of the respective divided areas are "AAA", "AAB", "AAC", and "AAD". The areas with the area IDs "AB" and "AC" are also further divided into 4 blocks respectively in the same manner. That is, the area IDs of the areas obtained by dividing the area with the area ID "AB" into 4 blocks are "ABA", "ABB", "ABC", and "ABD", and the area IDs of the areas obtained by dividing the area with the area ID "AC" into 4 blocks are "ACA", "ACB", "ACC", and "ACD".
[0077] The area with the area ID "D" is also divided into 4 blocks in the same manner, and a part of the divided areas are further divided into 4 blocks.
[0078] In this way, position information can be determined by repeatedly performing the operation of dividing all or part of the target area into 4 blocks until a required granularity is achieved. That is, the position information to be determined represents a certain area generated by hierarchically dividing areas.
[0079] FIG. 6 is a schematic diagram for explaining the coding system of area IDs used in the network system 1 according to the present embodiment. An example of the coding system shown in FIG. 6 corresponds to the area division shown in FIG. 5.
[0080] Referring to Figure 6, the first level is assigned four region IDs: "A", "B", "C", and "D". The second level uses region IDs that are further supplemented with identification text by appending the corresponding region IDs from the first level. For example, after dividing the region with region ID "A" into four regions, the regions with the identification text "A", "B", "C", and "D" appended to "A" are "AA", "AB", "AC", and "AD", respectively.
[0081] Similarly, in the third level, a region ID for identification is further appended to the region IDs of the corresponding second level region IDs. For example, in the four regions obtained after dividing the region ID "AA", the regions "AAA", "AAB", "AAC", and "AAD" are used, with the identification letters "A", "B", "C", and "D" appended to "AA" respectively.
[0082] The same rules apply to determining the region ID, even in cases involving deeper hierarchies. Thus, the region ID, as location information, is encoded to reflect the hierarchical structure of the region being targeted. In the network system 1 of this embodiment, region IDs that include all higher-level region IDs are used; therefore, for any region ID, a unique higher-level region ID can be identified. For example, it can be determined that a region with the region ID "AAA" is part of a region with the region ID "AA," and it can also be determined that it is part of a region with the region ID "A."
[0083] Figures 5 and 6 show an example of adding one English letter each time the hierarchy changes, but it is not limited to this. It can also be used to add identification information (text or numbers, etc.) of any length in sequence according to a predetermined rule.
[0084] In Figures 5 and 6, for ease of explanation, the state divided into 4 parts is taken as the top level (level 1), but the top level can also be any number of regions. Furthermore, for levels 2 and below, the number of divisions does not need to be limited to 4, and can be divided into any number of regions in sequence.
[0085] Figure 5 illustrates an example of sequentially dividing a square area for clarity, but this is merely a logical representation. Any unit can be assigned to different levels of the area depending on the application. In other words, the "area" shown in Figure 5 is not necessarily limited to a physical boundary and can encompass divisions of areas defined by human-determined rules. For example, the levels of the "area" can correspond to human-determined address designations (e.g., "prefecture," "city," "town," "address," "room number," etc.). Furthermore, the number of divisions and levels of the "area" shown in Figure 5 are not limited. For example, the area ID corresponding to the first store's address can be further subdivided, assigning an area ID to each seat.
[0086] The region ID is obtained from each communicating device and mapped onto the map, thereby specifying the location of each device 10.
[0087] (d2: Setting and Updating Region IDs) Next, an example of processing related to setting and updating the region IDs of each device 10 will be described. Alternatively, a predetermined region ID can be set for each device 10, and an electronic certificate 170 containing that set region ID can be issued from the certification authority 2. Alternatively, after connecting the device 10 to the network system 1, a region ID can be set for the connected device 10 according to the connection relationship on the network. The following describes an example of processing regarding the setting of region IDs and the issuance of electronic certificates 170 based on the connection relationship on the network.
[0088] Figure 7 is a schematic diagram illustrating the processing related to setting the area ID in the network system 1 according to this embodiment. In Figure 7, an example of processing is shown when device 10A2 (refer to Figure 1) is connected to the network of device 10A1 connected to area A.
[0089] Figure 7(A) shows an example of device 10A2 requesting a region ID from device 10A1 connected to the same network. In the example shown in Figure 7(A), device 10A2 requests a region ID from device 10A1 ((1) Region ID Request). Device 10A1 responds to the region ID request by adding identification information to the region ID assigned to its own device to determine the region ID, and responds to device 10A2 ((2) Region ID). Then, device 10A2 sends an authentication signature request to authentication authority 2, including the region ID assigned by device 10A1 and its own public key 162 ((3) Authentication Signature Request). Authentication authority 2 responds to the authentication signature request by generating an electronic certificate 170 to be given to device 10A2 and sending it to device 10A2 ((4) Electronic Certificate). Device 10A2 stores the electronic certificate 170 from authentication authority 2 and uses it for data communication with other devices.
[0090] In this way, the lower-level device 10 requires that the location information be set on its own device for other devices connected to a region of a higher level than the region shown in the region ID (location information) connected to its own device.
[0091] In Figure 7(B), there is an example of a request from display device 10A2 to device 10A1, which is connected to the same network, to issue an electronic certificate 170. In the example shown in Figure 7(B), device 10A2 requests device 10A1 to issue an electronic certificate 170 ((1) Authentication Issuance Request). This electronic certificate 170 issuance request includes device 10A2's public key 162. Device 10A1 responds to the electronic certificate 170 issuance request by adding identification information to the area ID assigned to its own device and determining the area ID of device 10A2 ((2) Area ID Determination). Then, device 10A1 sends an authentication signature request to authentication authority 2, including the area ID determined for device 10A1 and device 10A2's public key 162 ((3) Authentication Signature Request). Authentication authority 2 responds to the authentication signature request by generating an electronic certificate 170 to be given to device 10A2 and sending it to device 10A1, which then relays it to device 10A2 ((4) Electronic Authentication). Device 10A2 stores electronic certification 170 from certification authority 2 and uses it for data communication with other devices.
[0092] The area ID setting process shown in Figure 7 is one example; any other setting method can also be used. Furthermore, if device 10 is connected to another network, the area ID setting process shown in Figure 7 can be executed again. This re-execution allows the area ID to be updated.
[0093] Several application examples using the position information according to the present embodiment will be described below. In the applications described below, each device may also be installed with a function for managing currency or value for goods or services (including general currency and virtual currency). For example, by allocating a budget to each device, settlement processing without human intervention can be implemented.
[0094] <E·First Application Example>As a first application example, a configuration applied to fire alarms installed in a building will be described.
[0095] Figure 8 is a schematic diagram showing an example of an application using position information provided by the network system 1 according to the present embodiment. Referring to Figure 8, it is assumed that devices 10DT1 to 10DT6 serving as fire alarms are arranged on each floor of a building. In addition, a device 10HST, which is a main body that collects various information including fire sensing of the building, is also arranged. The device 10HST can perform data communication with each of the devices 10DT1 to 10DT6. Furthermore, the device 10HST can also perform data communication with a device 10MST, which is a main body arranged at a fire department or a main body that collects notifications to the fire department.
[0096] In the example shown in Figure 8, one building serves as the management unit of area IDs, and "AKPRMM" is allocated as the area ID. Furthermore, each floor of the building is respectively allocated an area ID ("AKPRMM1" to "AKPRMM6").
[0097] For example, when a fire alarm (device 10DT5) located on the 5th floor detects a fire, it notifies the main body (device 10HST) of the fire detection information. Between the device 10DT5 and the device 10HST, a session for data communication is established by exchanging electronic authentication 170 including an area ID. The exchanged electronic authentication 170 includes the area ID of the device 10DT5. In addition, the device 10DT5 specifies the area ID of the upper-level device 10 from its own area ID "AKPRMM5". In this example, "AKPRMM" obtained by removing the last character from the area ID "AKPRMM5" of the device 10DT5 can be specified as the notification destination.
[0098] When device 10HST receives fire detection information from device 10DT5, it refers to the electronic authentication 170 previously obtained from device 10DT5, specifies the area ID of device 10DT5, and notifies device 10MST of the area ID containing the fire detection information. Based on the notification information from device 10HST, device 10MST can pinpoint the location of the fire alarm (device 10DT5) that detected the fire. Then, it takes necessary actions according to the specific location.
[0099] In this way, by using the network system 1 according to this embodiment, it is possible to immediately obtain information such as which floor of the building has experienced an anomaly, such as a fire.
[0100] Figure 9 shows the timing diagram of the processing steps used to implement the application shown in Figure 8. Referring to Figure 9, the process of establishing a meeting is first performed between the devices. The main device 10HST sends its own electronic certificate 170 to the fire department's device 10MST (timing SQ10), and device 10MST also sends its own electronic authentication 170 to device 10HST (timing SQ11). By exchanging electronic authentication 170 between device 10HST and device 10MST, the meeting is established (timing SQ12).
[0101] Furthermore, device 10DT5, acting as a fire alarm, sends its own electronic authentication 170 to device 10HST (timing SQ13), and device 10HST also sends its own electronic authentication 170 to device 10DT5 (timing SQ14). A conference is established by exchanging electronic authentication 170 between device 10DT5 and device 10HST (timing SQ15). For ease of explanation, Figure 9 only shows the conference established between device 10DT5 and device 10HST, but other devices 10DT1~10DT4 and 10DT6 can also establish conferences in the same way as device 10HST.
[0102] Subsequently, when device 10DT5 detects a fire (timing SQ16), device 10DT5 sends the fire detection information to device 10HST (timing SQ17). Upon receiving the fire detection information from device 10DT5, device 10HST determines the area ID of device 10DT5 by referring to the electronic authentication 170 received from device 10DT5 (timing SQ18). Then, device 10DT5 sends the fire detection information from device 10DT5 and the determined area ID of device 10DT5 to device 10MST (timing SQ19).
[0103] In this way, after the device 10DT5 and the device 10HST constituting the network system 1 exchange an electronic certificate 170 to establish a session, the information generated or collected by the own device is transmitted to the device 10HST. The device 10DT5 can be reliably identified according to the content of the electronic certificate 170 used for establishing the session.
[0104] Through the processing steps as described above, the information detected by the fire alarm is transmitted to fire departments and the like together with the position of the detecting fire alarm, so position information necessary for fire fighting activities of the fire department can be provided.
[0105] In addition, in Fig. 8 and Fig. 9, as a typical example, an example in which notification is performed by a fire alarm is shown, but the present invention is not limited thereto, and can also be applied to any monitoring and detecting device (for example, an intrusion sensing device formed of an infrared sensor, a camera, or the like).
[0106] Furthermore, in devices such as fire alarms and sprinkler heads, a withheld payment that can cover the expenses for water required when a fire occurs may also be retained or managed in advance. By installing such a budget and payment function, when a device such as a fire alarm or a sprinkler head detects a fire, it can autonomously provide information to the fire department and even manage expenses without intervention of a manager or the like.
[0107] <F·Second Application Example> As a second application example, an architecture for managing service usage rights such as room reservation and usage in a hotel will be described.
[0108] Fig. 10 is a schematic diagram showing another example of application of position information provided by the network system 1 according to the present embodiment. In the application shown in Fig. 10, a user can use a mobile terminal owned by the user, i.e., the device 10TRM, as an electronic key (for usage authentication). A device 10KEY serving as an unlocking device is arranged in front of each room of an accommodation facility 40. When the user operates his or her own mobile terminal, that is, the device 10TRM, to make a reservation through a reservation website or the like, ticket information described later is provided to the mobile terminal and the target unlocking device. The same ticket information is shared between the mobile terminal and the target unlocking device. When the user approaches the reserved room, communication is performed between the user's mobile terminal and the target unlocking device to unlock the room. In addition, the communication between the mobile terminal and the unlocking device may be started automatically, or may be started only after the user performs an operation with a clear instruction.
[0109] Figure 11 shows a schematic diagram of a system architecture example for implementing the application shown in Figure 10. Referring to Figure 11, one or more unlocking devices, namely devices 10KEY1, 10KEY2, 10KEY3..., are configured to connect to each room in the hotel. Devices 10KEY1, 10KEY2, 10KEY3... can communicate with the server that manages hotel reservations, namely device 10SRV.
[0110] The 10SRV, acting as a server, can also communicate with the mobile terminal, namely the 10TRM.
[0111] The server device 10SRV manages the reservations for each room, and each room is managed by unlocking devices, namely devices 10KEY1, 10KEY2, 10KEY3, etc. If we consider the rooms managed by each unlocking device as "resources," we can also view it as the device 10SRV managing the resources to be provided in response to service requests. Information used to provide services determined according to the resource management described later is sent as ticket information 50 to the mobile terminal device 10TRM and the resource-providing device 10KEY.
[0112] Figure 12 is a summary diagram illustrating resource management in the application shown in Figure 10. Referring to Figure 12, the server device 10SRV manages time as a resource for each room connected to devices 10KEY1, 10KEY2, 10KEY3… Each hotel room only accepts one reservation (i.e., service) at any given time, thus services are allocated without overlap across timelines.
[0113] In the network system 1 according to this embodiment, each device 10 has an authenticated IP address, so even in resource management, the authenticated IP address of the device 10 requesting service can be used.
[0114] If resources can be secured for the service (reservation) requested as shown in Figure 12, ticket information 50 is sent to both the device requesting the service 10 and the device providing the secured resources 10.
[0115] Figure 13 shows an example of ticket information 50 used in the application shown in Figure 10. Referring to Figure 13, ticket information 50 includes resource allocation period 51, resource IP address 52, resource zone ID 53, and service delivery destination IP address 54.
[0116] The resource allocation period 51 displays the available room time. The resource IP address 52 displays the IP address of the unlocking device (device 10KEY) linked to the reserved room. The resource zone ID 53 displays the zone ID of the unlocking device (device 10KEY) linked to the reserved room. The service delivery destination IP address 54 displays the device 10TRM that reserved the room.
[0117] This ticket information 50 will be shared between device 10TRM and the target device 10KEY. As described above, the unlocking devices, namely devices 10KEY1, 10KEY2, 10KEY3…, can manage the resources connected to each device. Then, in response to requests from device 10TRM, at least a portion of the resources managed by devices 10KEY1, 10KEY2, 10KEY3… will be allocated. Furthermore, information regarding resource allocation will be shared between the device 10KEY that provides the resources and the device 10TRM that requests the resources.
[0118] Figure 14 shows a sequence diagram of the processing steps used to implement the application shown in Figure 10. Referring to Figure 14, the devices first perform a meeting establishment process. Device 10SRV, acting as a server, sends its own electronic authentication 170 to device 10KEY, acting as an unlocking device (timing SQ20), and device 10KEY also sends its own electronic authentication 170 to device 10SRV (timing SQ21). Device 10SRV and device 10KEY exchange electronic authentications 170, thereby establishing a meeting (timing SQ22). For ease of explanation, Figure 14 shows the process of device 10SRV establishing a meeting with only one device 10KEY, but even between one or multiple devices 10KEY1, 10KEY2, 10KEY3..., a meeting is established in the same way as between device 10SRV.
[0119] Furthermore, device 10TRM, acting as a mobile terminal, sends its own electronic authentication 170 to device 10SRV (timing SQ23), and device 10SRV also sends its own electronic authentication 170 to device 10KEY (timing SQ24). Devices 10DT5 and 10HST exchange electronic authentication 170, thereby establishing a conference (timing SQ25).
[0120] Subsequently, a user operation on device 10TRM is received (time sequence SQ26), and device 10TRM sends a reservation request to device 10SRV (time sequence SQ27). Device 10SRV receives the reservation request from device 10TRM, and ensures that the resources for the requested service can be provided (time sequence SQ28). Then, device 10TRM generates ticket information 50 corresponding to the guaranteed resources (time sequence SQ29), and device 10SRV sends the generated ticket information 50 to device 10TRM that sent the reservation request and device 10KEY that provides the guaranteed resources (time sequences SQ30 and SQ31).
[0121] When the user approaches the reserved room, device 10TRM sends the electronic certificate 170 of its own device to device 10KEY (time sequence SQ32), and device 10KEY also sends the electronic certificate 170 of its own device to device 10TRM (time sequence SQ33). Device 10TRM and device 10KEY exchange electronic certificates 170, thereby establishing a conference (time sequence SQ34). Then, the process of comparing ticket information 50 with each other is performed between device 10TRM and device 10KEY (time sequence SQ35). When the comparison process of ticket information 50 is successfully completed, device 10KEY unlocks the lock of the managed room (time sequence SQ36).
[0122] Through the above processing steps, a mechanism that allows users to reserve hotel rooms and use the mobile terminal body as a room key can be provided.
[0123] In the above description of the application, as a typical example, the architecture that uses a mobile terminal as the key for each room in accommodation facilities such as hotels is illustrated. However, the present invention is not limited thereto, and can be used as arbitrary usage authentication. For example, the mobile terminal itself can be used as an admission ticket for various facilities such as entertainment facilities, or for various events such as concerts. Also, the mobile terminal can be used as a ticket for railways or airplanes.
[0124] In addition, authentication terminals (such as gates or ticket vending machines, etc.) such as keys or tickets for each room of accommodation facilities as devices can have their own budgets. The budget can also be maintained in cooperation with withheld payment or settlement operators. Alternatively, the mobile terminal itself can also have its own budget. In this way, smooth money exchange can be performed between the authentication terminal and the mobile terminal, and a system that does not require intervention by managers or other personnel can be constructed.
[0125] <G·Third Application Example> As the third application example, an architecture for managing transportation resources will be described.
[0126] In this description, "transportation resources" refers to physical or human resources used in the movement of vehicles, railways, airplanes, ships, etc. Essentially, "transportation resources" are finite and will be appropriately scheduled and utilized according to demand. Hereinafter, it is assumed that the system is configured with a device 10 for managing these transportation resources.
[0127] Figure 15 shows a schematic diagram of yet another example of an application using location information provided by network system 1 according to this embodiment. Figure 15 shows a system assuming that the roads traveled by vehicles are traffic resources. More specifically, assuming four roads, traffic resources are defined for each section where roads 61, 62, 63, and 64 intersect, and devices 10 are configured to manage each traffic resource. It is assumed that each device 10 is configured to display the area ID of the traffic resource to be managed.
[0128] The device 10 connected to road 61 (area: avenue 001) has a resource comparison table 71 for managing traffic resources. Similarly, the device 10 connected to road 62 (area: avenue 002) has a resource comparison table 72 for managing traffic resources. Similarly, the device 10 connected to road 63 (area: street 001) has a resource comparison table 73 for managing traffic resources. Similarly, the device 10 connected to road 64 (area: street 002) has a resource comparison table 74 for managing traffic resources.
[0129] Resource lookup tables 71-74 register vehicles existing in the linked traffic resources. Each vehicle has an IP address and can communicate with the device 10 connected to each traffic resource. Each device 10 managing resource lookup tables 71-74 registers the vehicle's IP address and other information in the corresponding resource lookup table when a vehicle uses (or is scheduled to use) a linked traffic resource. Furthermore, each device 10 managing resource lookup tables 71-74 deletes the vehicle's IP address from the corresponding resource lookup table when the vehicle stops using the linked traffic resource. Additionally, additional information such as the vehicle's direction of travel can also be combined for registration.
[0130] By managing such traffic resources, congestion caused by traffic concentration can be avoided, and optimal route options can be provided for each vehicle.
[0131] Figure 16 shows a summary diagram of the route selection using the application shown in Figure 15. Referring to Figure 16, smooth travel is achieved by pre-allocating traffic resources for roads 61 and 63 to vehicles (IP address xx).
[0132] More specifically, for resource lookup table 71 connected to road 61 and resource lookup table 73 connected to road 63, the IP addresses of vehicles that are scheduled to use traffic resources are first registered, thereby ensuring a "right" for vehicles to pass.
[0133] In this way, the area IDs that are prepared to be linked to each transportation resource are managed by the device 10, which is assigned the area IDs for each transportation resource. The device 10 also manages the services that utilize each transportation resource. This architecture enables the optimal utilization of transportation resources.
[0134] As a mobile vehicle, the vehicle can use a region ID coding system to identify the device 10 that manages the available traffic resources.
[0135] Figure 17 shows a timing diagram of the processing steps used to implement the application shown in Figure 15. Figure 17 shows that the network system includes device 10M mounted on the vehicle and resource managers for managing roads 61, 62, 63, and 64, namely devices 10RM1, 10RM2, 10RM3, and 10RM4, as well as a higher-level area management server, namely device 10SRV, existing on devices 10RM1, 10RM2, 10RM3, and 10RM4.
[0136] Referring to Figure 17, the device 10M mounted on the vehicle obtains its current location by any method (timing SQ40). Typically, it obtains its current location based on information from GPS or mobile base stations.
[0137] Then, device 10M sends its own electronic authentication 170 to device 10SRV, which acts as a regional management server (timing SQ41), and device 10SRV also sends its own electronic authentication 170 to device 10M (timing SQ42). Device 10M and device 10SRV exchange electronic authentication 170 to establish a meeting (timing SQ43).
[0138] After the meeting is established, device 10M sends a connection node query, including the current location obtained in timing SQ40, to device 10SRV (timing SQ44). Device 10SRV responds to device 10M with a connection node query based on the current location included in the connection node query (timing SQ45). The connection node is used to specify information about device 10M that manages traffic resources, which will be used by device 10M. Additionally, multiple devices 10 can be included as connection nodes; in this example, it is assumed that device 10RM1, acting as the resource manager, is notified as a connection node.
[0139] In this way, device 10SRV responds to a request from device 10M regarding the current location, and answers the connection nodes (specific information) of devices 10RM1, 10RM2, 10RM3, and 10RM4 that are specifically connected to that current location.
[0140] Next, device 10M sends its own electronic authentication 170 to device 10RM1, which acts as the resource manager (timing SQ46), and device 10RM1 also sends its own electronic authentication 170 to device 10M (timing SQ47). Devices 10M and 10RM1 exchange electronic authentication 170, thereby establishing a meeting (timing SQ48).
[0141] After the meeting is established, device 10M sends a resource request to device 10RM1 (timing SQ49). Upon receiving the resource request from device 10M, device 10RM1 secures the resource as requested (timing SQ50). Then, device 10RM1 sends a response indicating that the resource has been secured back to device 10M (timing SQ51). Furthermore, device 10RM1 identifies the subsequent traffic resources managed by it and displays a response from the connection node of the resource manager managing the specific traffic resource back to device 10M (timing SQ52). In this example, device 10RM2, acting as the resource manager, is assumed to be notified as the connection node.
[0142] Next, device 10M sends its own electronic authentication 170 to device 10RM2, which acts as the resource manager (timing SQ53), and device 10RM2 also sends its own electronic authentication 170 to device 10M (timing SQ54). Devices 10M and 10RM2 exchange electronic authentication 170, thereby establishing a meeting (timing SQ55).
[0143] After the conference is established, the device 10M sends a resource request to the device 10RM2 (timing SQ56). The device 10RM2 receives the resource request from the device 10M and reserves resources in accordance with the request (timing SQ57). Then, the device 10RM2 sends a resource request response indicating that resources have been reserved to the device 10M (timing SQ58). Furthermore, after the device 10RM2 specifies the subsequent traffic resource following the traffic resource managed by the device 10RM2, it replies a connection node of the resource manager that manages the specified traffic resource to the device 10M (timing SQ59). Hereinafter, processing similar to that of timings SQ46 to SQ52 and timings SQ53 to SQ59 is repeated.
[0144] Through such processing steps, the allocation of traffic resources shown in FIG. 16 is completed. Thereby, efficient utilization of traffic resources can be achieved.
[0145] As described above, the devices 10RM1, 10RM2, 10RM3, and 10RM4 manage traffic resources connected to respective devices. Then, in response to a request from the device 10M, at least a part of the traffic resources managed by the devices 10RM1, 10RM2, 10RM3, and 10RM4 is allocated.
[0146] In the above description of the application, a typical example where roads are used as traffic resources is illustrated, but the present invention is not limited thereto, and can also be applied to any traffic resources. For example, each seat of each flight of railways, airplanes, ships and the like can also be treated as a traffic resource.
[0147] A budget can also be allocated for the above-mentioned traffic resources. In this case, when it is desired to guarantee arrival at the destination in the shortest time, a mechanism can be provided where road users are charged for traffic resources. On the other hand, even for an efficient route, for unblocked roads, traffic resources can also pay consideration for use to users and the like from the budget.
[0148] <H. Other Embodiments> In the above application example, processing of exchanging data between devices 10 is illustrated, but the present invention is not limited thereto, and commands (instructions) may also be exchanged between devices 10. By exchanging such commands, the function and the like of the device 10 can be dynamically changed.
[0149] By dynamically changing such functions, for example, the processing of a certain device 10 can also be entrusted or assigned to another device 10. For example, when an abnormality occurs in the device 10 responsible for managing traffic resources shown in FIG. 15, or when the processing related to traffic resource management increases, functional changes can be made; for example, the device 10 responsible for processing can be changed to another device 10, or another device 10 can be added in addition to the device 10 responsible for processing. As for such an entire network system, any method for optimal use of the devices 10 can be employed.
[0150] <I·Advantages>According to the network system 1 of the present embodiment, authenticated position information of devices can be obtained, and various services using the authenticated position information can be provided at the same time.
[0151] All contents of the embodiments disclosed herein are illustrative and not intended to limit the present invention. The scope of the present invention is defined by the claims, rather than the above description, and all modifications that fall within the meaning equivalent to the claims and the scope thereof are included in the present invention.
[0152] 1: Network system 2: Certification authority 10, 10A1~10A4, 10B1~10B5, 10C1~10C4, 10DT1~10DT6, 10HST, 10KEY, 10KEY1~10KEY3, 10M, 10MST, 10RM1~10RM4, 10SRV, 10TRM: Device 40: Accommodation facility 50: Ticket information 51: Resource allocation period 52, 54, 168: IP address 53, 182: Area ID 61, 62, 63, 64: Road 71, 72, 73, 74: Resource comparison table 102: Processor 104: Main memory 106: Storage 108: ROM 110: Controller 120: Network interface 130: Internal interface 140: Input unit 150: Output unit 160: Secret key 162: Public Key 164: Hash Function 166: Hash value 170: Electronic Authentication 171: Version Information 172: Serial Number 173: Signed Algorithm 174: Publisher Identifier 175: Validity period 176: Subject Identifier Name 178: Certification Authority Signature 180: Expansion Information 182: Region ID
Claims
1. A network system having at least one first device; The first device includes: means for managing resources associated with the first device; and means for allocating at least a portion of the resources associated with the first device in response to a resource allocation request from a second device; wherein information associated with the allocated resources is shared between the first device and the second device through a specific method of a cryptographic device.
2. The network system as described in request item 1, wherein, The first device includes means for generating a ticket; the ticket contains information indicating the content of the allocated resource and the network address of the second device to which the resource has been allocated.
3. The network system as described in request item 1, wherein, The network address of the second device is determined based on a public key, which is a key pair of the secret key of the second device.
4. The network system described in any of requests 1 to 3, wherein, This resource includes available space and available time.
5. The network system described in any of requests 1 to 3, wherein, The network system includes a plurality of the first devices and a third device capable of communicating with the plurality of first devices; and the third device, in response to a resource allocation request from the second device, identifies a corresponding first device and responds to the second device with the identified first device.
6. The network system described in any of requests 1 to 3, wherein, The second device includes: means for obtaining the current location of the second device; and means for making an inquiry including the current location of the second device and identifying the first device based on the response to the inquiry.
7. The network system described in any of requests 1 to 3, wherein, The resource is a transportation resource; moreover, the second device is a mobile body.
8. The network system as described in claim 7, wherein, This resource includes the right of passage of the second device.
9. A network system as described in any of claims 1 to 3, wherein, The specific method of this cryptographic device includes using cryptographic algorithms to uniquely determine the network address of each device.
10. A processing method, executed in a network system, comprising: Steps performed by the first device for managing resources associated with the first device; And the step performed by the first device to allocate at least a portion of the resources associated with the first device in response to a resource allocation request from the second device; wherein information associated with the allocated resources is shared between the first device and the second device through a specific method of the cryptographic device.
Citation Information
Patent Citations
Methods, Apparatus And Systems For Wireless Network Selection
TW201526676A
Network systems, information processing devices and processing methods
TWI879765B
Methods and systems for unilateral authentication of messages
US20020152384A1
Methods and Systems for Unilateral Authentication of Messages
US20070061574A1
Remote access to resouces
US20070088834A1
