WO2011099590A1 - Système de prestations de service ad hoc - Google Patents

Système de prestations de service ad hoc Download PDF

Info

Publication number
WO2011099590A1
WO2011099590A1 PCT/JP2011/052963 JP2011052963W WO2011099590A1 WO 2011099590 A1 WO2011099590 A1 WO 2011099590A1 JP 2011052963 W JP2011052963 W JP 2011052963W WO 2011099590 A1 WO2011099590 A1 WO 2011099590A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
client
secondary server
adjacency
generated
Prior art date
Application number
PCT/JP2011/052963
Other languages
English (en)
Japanese (ja)
Inventor
晋 原田
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to JP2011553906A priority Critical patent/JPWO2011099590A1/ja
Publication of WO2011099590A1 publication Critical patent/WO2011099590A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • the present invention relates to an ad hoc service providing system, an ad hoc service providing method, a main server, a sub server, a client, and a program recording medium, and in particular, an ad hoc service providing system for providing a service to a client device existing in the vicinity of a server device,
  • the present invention relates to an ad hoc service providing method, a main server, a secondary server, a client, and a program recording medium.
  • Non-Patent Document 2 discloses that when a user simultaneously presses a button on two terminals, each terminal transmits a pairing request to the server.
  • Non-Patent Document 3 discloses a method in which information when two terminals collide with each other is transmitted to the server, and the two terminals are associated with each other based on the information received by the server.
  • One object of the present invention is to provide an ad hoc service providing system, an ad hoc service providing method, a main server, a sub server, a client, and a program recording medium that solve the above-described problems.
  • the secondary server Third adjacency generation control means for generating the adjacency relationship between the sub-client list and the sub-client list received from the sub-server generated with the adjacency relationship, and the identifier of the client included in the sub-client list
  • Client list generating means for generating a client list including the client list, and the client
  • the main server having an access control means for permitting access from the client identified by the client identifier included in the cement list.
  • the ad hoc service providing method of the present invention uses proximity registration in which each of two devices within a predetermined range acquires an identifier of a counterpart device, and the proximity registration is performed between a client and a secondary server. If this happens, create an adjacency relationship with the secondary server, When the proximity registration is performed with the client, the secondary server generates the adjacency with the client, and the secondary server sets the identifier of the client with the adjacency generated.
  • the sub-client list is generated, and when the sub server performs the proximity registration with the main server, the sub server generates the adjacency relationship with the main server, and the main server When the proximity registration is performed with the sub server, the adjacency relationship is generated with the sub server, and the sub server transmits the sub client list to the main server with the adjacency relationship generated.
  • the main server receives the sub-client list from the sub-server in which the adjacency is generated, and the identifier of the client included in the sub-client list A client list including the server, and the secondary server transmits, as upper server information, the identifier of the main server in which the adjacency is generated, to the client in which the adjacency is generated.
  • the upper server information received from the generated secondary server is used to access the main server, and the main server permits access from the client identified by the client identifier included in the client list.
  • the main server of the present invention uses a sub-client including an identifier of a client whose adjacency is generated by proximity registration, in which each of two devices existing in a predetermined range acquires an identifier of a counterpart device,
  • the adjacent relationship generation control unit that generates the adjacent relationship with the secondary server, and the secondary server with which the adjacent relationship is generated
  • Access control means for permitting access for permitting access.
  • the adjacency generation control means for generating the adjacency relationship with the client the subclient list generation means for generating the subclient list including the identifier of the client in which the adjacency is generated, and the adjacency A sub-client list sender that sends the sub-client list to the main server for which a relationship has been generated
  • a host server information transmitting means for transmitting the adjacency said adjacency of the main server generated to the client generated identifier as the host server information.
  • each of two devices existing in a predetermined range obtains the identifier of the counterpart device as proximity registration, and the computer has the adjacent relationship generated by the proximity registration.
  • the adjacent relationship generation control unit that generates the adjacent relationship with the secondary server, and the adjacent relationship is
  • a client list generating means for receiving the sub client list from the generated sub server and generating a client list including an identifier of the client included in the sub client list; and an identifier of the client included in the client list.
  • each of two devices existing in a predetermined range obtains the identifier of the counterpart device as proximity registration, and the computer has generated the adjacent relationship by the proximity registration.
  • the proximity registration is performed with a secondary server that generates a sub-client list including an identifier of the client and transmits the adjacent relationship to the primary server generated by the proximity registration, Received from the secondary server in which the adjacency is generated, to an adjacency generation means for generating an adjacency, and to the primary server that permits access from the client identified by the identifier of the client included in the subclient list Program for client to function as server access means to access using the higher-level server information Record.
  • the effect of the present invention is that, in an ad hoc service providing system, even when there are a large number of client devices, the client devices can be registered smoothly.
  • both the two secondary servers 200 are representative secondary servers
  • the ad hoc service providing system includes a main server 100, a plurality of secondary servers 200, and a plurality of clients 300.
  • the main server 100, the sub server 200, and the client 300 are movable terminal devices such as smartphones and mobile phones.
  • the main server 100, the sub server 200, and the client 300 can communicate with each other via a network (not shown) using a mobile communication network, a wireless LAN, a short-range communication method, or the like.
  • the main server 100 provides services such as photo and file sharing and bulletin boards to registered clients 300.
  • the secondary server 200 performs registration of services of the client 300 in a distributed manner in the system.
  • the client 300 accesses a service provided by the main server 100.
  • proximity registration refers to acquiring the identifiers of partner devices and registering them as close terminals in a situation where two devices are guaranteed to be within a predetermined range.
  • an adjacency relationship that is a path for transferring the identifier of the client 300 to the main server 100 is generated between the two devices.
  • a dashed arrow indicates that proximity registration is performed between devices.
  • a solid line arrow indicates an adjacent relationship generated by proximity registration.
  • the direction of the arrow indicating the adjacency relationship indicates the direction in which the identifier of the client 300 is transferred toward the main server 100.
  • the main server 100 side of the arrow indicating the adjacency relationship is the upper level and the client 300 side is the lower level.
  • the secondary server 200 registers the client 300 with the primary server 100 that the secondary server 200 plans to generate an adjacent relationship (or has already generated an adjacent relationship). In this case, proximity registration is performed with the client 300. Further, when registering the client 300 registered in the secondary server 200 to the main server 100, the main server 100 performs proximity registration with the secondary server 200.
  • the secondary server 200 and the client 300 When proximity registration is performed between the secondary server 200 and the client 300, the secondary server 200 and the client 300 generate an adjacent relationship with each other.
  • the main server 100 and the secondary server 200 When proximity registration is performed between the main server 100 and the secondary server 200, the main server 100 and the secondary server 200 generate an adjacent relationship with each other.
  • Each of the plurality of secondary servers 200 registers the identifier of the client 300 that has generated the adjacency relationship with the main server 100 that has generated the adjacency relationship.
  • the proximity registration is performed between the secondary server 200 (SS1) and the client 300 (C1-3), so that the secondary server 200 (SS1) and the client 300 (C1-3) are adjacent to each other. Is generated.
  • the clients 300 (C1 to C3) are registered in the secondary server 200 (SS1).
  • the secondary server 200 (SS2) and the client 300 (C4 to 6) generate an adjacency relationship.
  • the client 300 (C4 to C6) is registered in the secondary server 200 (SS2).
  • the main server 100 (S0) and the sub server 200 (SS1, SS2) generate an adjacency relationship.
  • the clients 300 (C1 to 6) registered in the secondary server 200 (SS1, SS2) are registered in the main server 100 (S0).
  • the main server 100 (S0) provides services to these registered clients 300 (C1 to C6).
  • any method may be used as long as the identifiers of the partner devices can be acquired in a situation where it is guaranteed that the two devices are within a predetermined range.
  • the terminal device (device A) has only a terminal device whose device A identifier is in a limited range (predetermined range) from the device A, such as infrared communication, short-range wireless communication using weak radio waves, and barcodes.
  • the terminal device (device B) that outputs in a method that cannot be acquired and has acquired the identifier of the device A may access the device A using the identifier of the device A and transmit the identifier of the device B to the device A.
  • FIG. 2 is a block diagram showing the configuration of the ad hoc service providing system according to the first embodiment of the present invention.
  • the main server 100 includes an adjacent relationship generation control unit 110, a client list generation unit 120, an access control unit 130, a service providing unit 140, a client list storage unit 150, and a secondary server information storage unit 160.
  • the adjacency generation control unit 110 generates an adjacency relationship with the secondary server 200 when proximity registration is performed with the secondary server 200 existing in a predetermined range in the vicinity.
  • the adjacent relationship generation control unit 110 stores the identifier of the secondary server 200 in which the adjacent relationship is generated in the secondary server information storage unit 160 as the secondary server information 165.
  • FIG. 8 is a diagram illustrating an example of the secondary server information 165 according to the first embodiment of this invention.
  • the secondary server information 165 includes the secondary server identifier of the secondary server 200 in which the adjacency relationship is generated.
  • the client list generation unit 120 receives the sub client list 255 from the sub server 200 in which the adjacency is generated, generates the client list 155 including the identifier of the client 300 included in the sub client list 255, and the client list storage unit Save to 150.
  • FIG. 9 is a diagram illustrating an example of the client list 155 according to the first embodiment of this invention.
  • the client list 155 includes the client identifier of the client 300 registered in the secondary server 200 in which the adjacency relationship is generated.
  • the access control unit 130 permits access from the client 300 with the client identifier included in the client list 155 to the service providing unit 140.
  • the service providing unit 140 provides a service to the client 300.
  • the service providing unit 140 may be a web server.
  • the secondary server 200 is a terminal device for performing registration of the client 300 in a distributed manner in the system.
  • the secondary server 200 includes an adjacent relationship generation control unit 210, a sub client list generation unit 220, a sub client list transmission unit 230, an upper server information transmission unit 240, a sub client list storage unit 250, and a main server information storage unit 260.
  • the adjacency generation control unit 210 generates an adjacency relationship with the client 300 when proximity registration is performed with the client 300 existing in a predetermined peripheral range. Further, the adjacency generation control unit 210 generates an adjacency relationship with the main server 100 when proximity registration is performed with the main server 100 existing in a predetermined range in the vicinity.
  • the adjacency generation control unit 210 stores the identifier of the main server 100 in which the adjacency is generated in the main server information storage unit 260 as main server information 265.
  • 10 and 12 are diagrams illustrating examples of the main server information 265 according to the first embodiment of this invention.
  • the main server information 265 includes the main server identifier of the main server 100 in which the adjacency relationship is generated.
  • the subclient list generation unit 220 adds the identifier of the client 300 for which the adjacency relationship has been generated to the subclient list 255 and stores it in the subclient list storage unit 250.
  • 11 and 13 are diagrams illustrating examples of the sub client list 255 according to the first embodiment of this invention.
  • the sub-client list 255 includes the client identifier of the client 300 for which the adjacency relationship has been generated.
  • the sub client list transmission unit 230 transmits the generated sub client list 255 to the main server 100 in which the adjacency relationship is generated.
  • the upper server information transmission unit 240 transmits the identifier of the main server 100 to the client 300 for which the adjacency relationship has been generated.
  • the client 300 is a terminal device for accessing a service provided by the main server 100.
  • the client 300 includes an adjacent relationship generation control unit 310, a server access unit 320, and a secondary server information storage unit 330.
  • the adjacency generation control unit 310 generates an adjacency relationship with the secondary server 200 when proximity registration is performed with the secondary server 200 existing in a predetermined range in the vicinity.
  • the adjacent relationship generation control unit 310 stores the identifier of the secondary server 200 in which the adjacent relationship has been generated in the secondary server information storage unit 330 as the secondary server information 335.
  • FIG. 14 is a diagram illustrating an example of the secondary server information 335 according to the first embodiment of this invention.
  • the secondary server information 335 includes the secondary server identifier of the secondary server 200 in which the adjacency relationship is generated.
  • the server access unit 320 receives the identifier of the main server 100 from the secondary server 200 in which the adjacency relationship is generated, and accesses the main server 100.
  • the server access unit 320 may be a web browser.
  • the service providing unit 140 provides content data such as moving images, music, and documents
  • the server access unit 320 may be an application for reproducing or displaying these content data.
  • the main server 100, the secondary server 200, and the client 300 may be information processing devices that operate according to programs. In this case, an application that operates as the primary server 100, the secondary server 200, or the client 300 may be activated by an operation of the user of the information processing apparatus.
  • the main server 100 and the client 300 or both the sub server 200 and the client 300 may operate with one terminal device.
  • the operation of the first embodiment of the present invention will be described in detail with reference to the drawings.
  • the operation will be described taking as an example the case where the client 300 (C1 to 6) is registered to the primary server 100 (S0) using the secondary servers 200 (SS1, SS2).
  • SS1, SS2 secondary servers 200
  • FIG. 4 is a sequence diagram showing the registration operation from the client 300 to the secondary server 200 in the first embodiment of the present invention.
  • the adjacency generation control unit 210 of the secondary server 200 and the adjacency generation control unit 310 of the client 300 use the method as described above.
  • To perform proximity registration step S101).
  • the secondary server 200 and the client 300 mutually acquire the identifier of the counterpart device. For example, in FIG. 3, when the secondary server 200 (SS1) registers the identifier of the client 300 (C1) existing in the surroundings with the main server 100 (the user of the secondary server 200 (SS1) is started from the client 300 (C1).
  • the adjacency generation control unit 210 of the secondary server 200 responds to the user instruction of the secondary server 200 (SS1) and identifies the secondary server 200 (SS1). "Information for accessing the secondary server 200" is displayed on a display unit (not shown) as a two-dimensional barcode.
  • the adjacency generation control unit 310 of the client 300 (C1) that exists in a range where the contents of the display unit of the secondary server 200 can be read is transmitted by the imaging unit (not shown) in response to a user instruction of the client 300 (C1).
  • the two-dimensional barcode displayed on the display unit of the secondary server 200 (SS1) is read.
  • the adjacent relationship generation control unit 310 transmits the identifier of the client 300 (C1) to the secondary server 200 (SS1) using the information of the two-dimensional barcode.
  • the secondary server 200 (SS1) displays a URL (Uniform Resource Locator) as “information for accessing the secondary server 200”
  • the adjacent relationship generation control unit 310 displays the Web browser of the client 300 (C1).
  • the identifier of the client 300 (C1) may be transmitted by accessing the secondary server 200 (SS1) by (not shown).
  • the adjacency generation control unit 310 of the client 300 sets the identifier of the secondary server 200 acquired by proximity registration in the secondary server information 335 and stores it in the secondary server information storage unit 330 (step S102).
  • the sub-client list generation unit 220 of the secondary server 200 adds the identifier of the client 300 acquired by proximity registration to the sub-client list 255 and stores it in the sub-client list storage unit 250 (step S103).
  • steps S102 and S103 the generation of the adjacency relationship between the secondary server 200 and the client 300 is completed.
  • the secondary server information 335 of the client 300 (C1) includes the secondary server 200 as shown in FIG.
  • the identifier of (SS1) is set.
  • the identifier of the client 300 (C1) is added to the subclient list 255 of the subserver 200 (SS1) as shown in FIG.
  • FIG. 5 is a sequence diagram showing an operation of registration from the secondary server 200 to the primary server 100 in the first embodiment of the present invention.
  • the adjacency generation control unit 110 of the main server 100 and the adjacency generation control unit 210 of the sub server 200 perform the method described above. By using it, proximity registration is performed (step S111). By performing proximity registration, the main server 100 and the secondary server 200 acquire the identifiers of the counterpart devices. For example, in FIG. 3, when the main server 100 (S0) registers the identifier of the client 300 registered in the secondary server 200 (SS1) in the vicinity with the main server 100 (S0) (main server 100 (S0)).
  • the adjacency generation control unit 110 of the main server 100 determines the user of the main server 100 (S0). In response to the instruction, “information for accessing main server 100” including the identifier of main server 100 (S0) is displayed on a display unit (not shown) as a two-dimensional barcode.
  • the adjacency generation control unit 210 of the secondary server 200 (SS1) existing in a range where the content of the display unit of the primary server 100 (S0) can be read is responsive to a user instruction of the secondary server 200 (SS1).
  • the two-dimensional bar code displayed on the display unit of the main server 100 (S0) is read by (not shown).
  • the adjacent relationship generation control unit 210 transmits the identifier “SS1” of the secondary server 200 (SS1) to the main server 100 (S0) using the information of the two-dimensional barcode.
  • the adjacency generation control unit 210 uses the Web browser (not shown) of the secondary server 200 to execute the main relationship.
  • the identifier of the secondary server 200 may be transmitted.
  • the adjacent relationship generation control unit 210 of the secondary server 200 sets the identifier of the main server 100 acquired by proximity registration in the main server information 265 and stores it in the main server information storage unit 260 (step S112).
  • the adjacent relationship generation control unit 110 of the main server 100 sets the identifier of the secondary server 200 acquired by proximity registration in the secondary server information 165 and stores it in the secondary server information storage unit 160 (step S113).
  • the generation of the adjacency relationship between the main server 100 and the sub server 200 is completed through steps S112 and S113.
  • the primary server information 265 of the secondary server 200 (SS1) includes the primary server information 265 as shown in FIG.
  • the identifier of the server 100 (S0) is set.
  • the secondary server information 165 of the primary server 100 (S0) the identifier of the secondary server 200 (SS1) is set as shown in FIG.
  • the sub client list transmission unit 230 of the sub server 200 transmits the sub client list 255 stored in the sub client list storage unit 250 to the main server 100 using the identifier of the main server 100 set in the main server information 265. (Step S114).
  • the client list generation unit 120 of the main server 100 adds the identifier of the client 300 included in the sub client list 255 received from the sub server 200 to the client list 155 and stores it in the client list storage unit 150 (step S115).
  • the primary server 100 receives the sub-client list 255 of FIGS. 11 and 13 from the secondary server 200 (SS1, SS2) that generated the adjacency relationship, and generates the client list 155 of FIG. To do.
  • FIG. 6 is a sequence diagram illustrating an operation of providing a service from the main server 100 according to the first embodiment of this invention.
  • the server access unit 320 of the client 300 uses the identifier of the sub server 200 set in the sub server information 335 to send the server to the sub server 200.
  • An access request is transmitted (step S121).
  • the client 300 (C1) transmits a service access request to the secondary server 200 (SS1) based on the secondary server information 335 of FIG.
  • the upper server information transmission unit 240 of the secondary server 200 transmits the identifier of the main server 100 set in the main server information 265 to the client 300 as the upper server information, and instructs redirection to the main server 100 (step S122).
  • the secondary server 200 (SS1) transmits the identifier of the main server 100 (S0) to the client 300 (SS1) as the upper server information based on the main server information 265 of FIG.
  • the adjacency relationship is not generated between the main server 100 and the sub server 200 (the operation of registration in the main server 100 (FIG.
  • the higher-level server information transmission unit 240 may transmit a response indicating “being prepared” to the client 300. In this case, the higher-level server information transmission unit 240 may transmit “retry waiting time” presented to the user of the client 300 to the client 300.
  • the server access unit 320 of the client 300 transmits a server access request to the main server 100 using the identifier of the main server 100 included in the received higher-level server information (step S123). For example, the client 300 (C1) transmits a service access request to the main server 100 (S0).
  • the access control unit 130 of the main server 100 searches whether the identifier of the client 300 that has transmitted the server access request exists in the client list 155. When the identifier of the client 300 exists in the client list 155, the access control unit 130 determines that the service can be provided to the client 300 (Step S124). Thereafter, the service providing unit 140 of the main server 100 starts providing services to the client 300. For example, since the identifier of the client 300 (C1) exists in the client list 155 of FIG. 9, the main server 100 (S0) determines that the service can be provided to the client 300 (C1) and starts providing the service. To do.
  • FIG. 7 is a sequence diagram showing an operation of additional registration to the main server 100 in the first embodiment of the present invention.
  • the adjacent relationship generation control unit 310 of the new client 300 sets the identifier of the secondary server 200 acquired by proximity registration in the secondary server information 335 and stores it in the secondary server information storage unit 330 (step S132).
  • the sub client list generation unit 220 of the secondary server 200 adds the identifier of the new client 300 acquired by proximity registration to the sub client list 255 and stores it in the sub client list storage unit 250 (step S133).
  • Generation of the adjacency relationship between the secondary server 200 and the client 300 is completed through steps S132 and S133.
  • the sub client list transmission unit 230 of the sub server 200 transmits the identifier of the new client 300 to the main server 100 (step S134).
  • the client list generation unit 120 of the main server 100 adds the identifier of the new client 300 received from the sub server 200 to the client list 155 and stores it in the client list storage unit 150 (step S135). Thereafter, when the main server 100 receives a service access request from the new client 300 added to the client list 155, the main server 100 provides a service to the new client 300 according to the service providing operation from the main server 100 (FIG. 6). To do. Thus, the operation of the first embodiment of the present invention is completed. Next, a characteristic configuration of the present invention will be described.
  • FIG. 1 is a block diagram showing a characteristic configuration of the first embodiment of the present invention.
  • the ad hoc service providing system includes a main server 100, a plurality of secondary servers 200, and a plurality of clients 300.
  • the client 300 when the proximity registration is performed with the secondary server 200, the client 300 generates the adjacent relationship with the first adjacent relationship generation control unit 310 that generates the adjacent relationship with the secondary server 200.
  • a server access unit 320 that accesses the main server 100 using the upper server information received from the secondary server 200.
  • the secondary server 200 When the proximity registration is performed with the client 300, the secondary server 200 generates an adjacency relationship with the client 300.
  • the secondary server 200 A second adjacency generation control unit 210 that generates an adjacency relationship with 100, a subclient list generation unit 220 that generates a subclient list 255 including an identifier of the client 300 in which the adjacency relationship has been generated, and an adjacency relationship
  • the sub-client list transmission unit 230 that transmits the sub-client list 255 to the main server 100 in which the adjacency is generated, and the identifier of the main server 100 in which the adjacency is generated are transmitted as higher-level server information to the client 300 that has generated the adjacency.
  • an upper server information transmission unit 240 an upper server information transmission unit 240.
  • the primary server 100 When the proximity registration is performed with the secondary server 200, the primary server 100 generates the adjacent relationship with the third adjacent relationship generation control unit 110 that generates the adjacent relationship with the secondary server 200.
  • the client list generation unit 120 that receives the sub client list 255 from the sub server 200 and generates the client list 155 including the identifier of the client 300 included in the sub client list 255, and the identifier of the client 300 included in the client list 155.
  • an access control unit 130 that permits access from the identified client 300.
  • each of the plurality of secondary servers 200 generates a sub-client list 255 including the identifier of the client 300 in which the adjacent relationship is generated by proximity registration, and the main server 100 generates the adjacent relationship by proximity registration.
  • the client list 155 is generated based on the sub client list 255 received from the secondary server 200.
  • FIG. 15 is a diagram illustrating an example of the sub-client list 255 according to the second embodiment of this invention.
  • step S103 of FIG. 4 the sub client list generation unit 220 of the secondary server 200 uses the identifier of the client 300 for which the secondary server 200 has generated the adjacency and the time at which the adjacency is generated as the client identifier of the sub client list 255. And registration time respectively. 5, the client list generation unit 120 of the main server 100 generates the adjacency relationship between the registration time included in the sub client list 255 received from the sub server 200 and the main server 100 and the sub server 200.
  • the identifier of the client 300 corresponding to the registered time is added to the client list 155.
  • the main server 100 and the sub server 200 generate an adjacency relationship at time “2010/01/10 10:25”, and the main server 100 receives the sub client list 255 of FIG.
  • the identifier of the client 300 whose time difference between the registration time included in the sub-client list 255 and the time when the adjacency is generated between the main server 100 and the sub-server 200 is within 20 minutes is added to the client list 155.
  • step S115 the client list generation unit 120 of the main server 100 determines that the registration time included in the sub-client list 255 is later than the service start time of the main server 100, and the registration time and the service of the main server 100 When the time difference from the start time is equal to or less than a predetermined time difference, the identifier of the client 300 corresponding to the registration time may be added to the client list 155. For example, the identifier of the client 300 whose registration time included in the sub-client list 255 is later than the service start time of the main server 100 and whose time difference between the registration time and the service start time of the main server 100 is within 20 minutes.
  • FIG. 16 is a diagram showing another example of the sub-client list 255 according to the second embodiment of this invention.
  • step S ⁇ b> 103 of FIG. 4 the sub-client list generation unit 220 of the secondary server 200 acquires position information of the secondary server 200 at the time when the secondary server 200 generates an adjacency relationship with the client 300.
  • the secondary server 200 acquires position information by, for example, GPS (Global Positioning System).
  • the sub client list generation unit 220 adds the identifier of the client 300 that has generated the adjacency relationship and the position information of the sub server 200 to the client identifier and the registered position of the sub client list 255, respectively.
  • the client list generation unit 120 of the main server 100 acquires the position information of the main server 100 at the time when the adjacency relationship is generated between the main server 100 and the sub server 200.
  • the main server 100 acquires position information by, for example, GPS. If the difference between the registration position included in the sub-client list 255 received from the sub-server 200 and the position information of the main server 100 is equal to or less than a predetermined value, the client list generation unit 120 sets the registration position to the registration position.
  • the identifier of the corresponding client 300 is added to the client list 155.
  • the ad hoc service providing system it is possible to more reliably perform access restriction that permits access only from client devices existing in the vicinity of the server device. The reason is that when the primary server 100 registers the identifier of the client 300 in the client list 155, the registration is based on the time or position information when the adjacency is generated between the secondary server 200 and the client 300. This is to determine whether or not it is possible. Further, according to the second embodiment of the present invention, in the ad hoc service providing system, it is possible to permit access only from the client device existing in the vicinity of the server device after the service is started.
  • FIG. 18 is a diagram showing an outline of client registration in the third embodiment of the present invention.
  • the third embodiment of the present invention is different from the first embodiment of the present invention in that an adjacency relationship is generated between the secondary servers 200.
  • components having the same reference numerals as those of the first embodiment of the present invention are the same as those of the first embodiment of the present invention unless otherwise specified. is there.
  • the two secondary servers 200 When proximity registration is performed between two secondary servers 200, the two secondary servers 200 generate an adjacency relationship with one being a higher server and the other being a lower server.
  • a group formed by a plurality of secondary servers 200 that have generated an adjacent relationship (or a single secondary server 200 that has not generated an adjacent relationship) is defined as a secondary server group.
  • the secondary server 200 (the highest secondary server 200 in the secondary server group) that does not generate the adjacency relationship with the other secondary server 200 as the higher server is set as the representative secondary server.
  • an adjacency relationship is generated between the secondary servers 200 and a new secondary server is created. Create a group.
  • the adjacency relationship is generated between the secondary servers 200 that are the representative secondary servers
  • the upper secondary server 200 becomes the representative secondary server of the new secondary server group.
  • the lower secondary server 200 registers the identifier of the client 300 registered in the lower secondary server 200 in the upper secondary server 200 (representative secondary server).
  • the secondary server 200 which is the representative secondary server, holds the identifiers of all the clients 300 registered in the secondary server 200 in the new secondary server group.
  • the main server 100 and the secondary server 200 that is the representative secondary server when proximity registration is performed between the main server 100 and the secondary server 200 that is the representative secondary server, the main server 100 and the secondary server 200 that is the representative secondary server generate an adjacency relationship with each other.
  • the secondary server 200 which is the representative secondary server, registers the identifier of the client 300 in the secondary server group with the primary server 100 that has generated the adjacency relationship. For example, in FIG. 18, the client 300 is registered in each of the secondary servers 200 (SS1 to SS3), and the secondary servers 200 (SS1 to SS3) form a secondary server group (state 1).
  • the secondary server 200 (SS1) and the secondary server 200 (SS2) become the secondary server 200 (SS1).
  • the secondary server 200 (SS1) and the secondary server 200 (SS3) generate an adjacency relationship in which the secondary server 200 (SS1) is an upper server.
  • the secondary server 200 (SS1) becomes a representative secondary server of the secondary server group formed by the plurality of secondary servers 200 (SS1 to SS3) (state 2).
  • the client 300 (C1 to 6) is registered in the secondary server 200 (SS1).
  • the secondary server 200 (SS1) and the secondary server 200 (SS4) are registered.
  • the secondary server 200 (SS1) is an upper server.
  • the secondary server 200 (SS1) becomes the representative secondary server of the secondary server group formed by the plurality of secondary servers 200 (SS1 to SS6) (state 3).
  • the client 300 (C1 to 12) is registered in the secondary server 200 (SS1).
  • proximity registration is performed between the main server 100 (S0) and the secondary server 200 (SS1), whereby the primary server 100 (S0) and the secondary server 200 (SS1) generate an adjacency relationship.
  • the clients 300 (C1 to 12) registered in the secondary server 200 (SS1) are registered in the main server 100 (S0).
  • FIG. 17 is a block diagram showing a configuration of an ad hoc service providing system according to the third embodiment of the present invention.
  • the secondary server 200 includes an upper secondary server information storage unit 270 and a lower secondary server information storage unit 280 in addition to the configuration of the secondary server 200 (FIG. 2) in the first embodiment of the present invention.
  • the adjacency generation control unit 210 of the secondary server 200 generates an adjacency relationship between the client 300 and the main server 100, and also registers proximity registration with other secondary servers 200 existing in a predetermined peripheral range.
  • an adjacency relationship is generated with the other secondary server 200.
  • the adjacency generation control unit 210 stores the identifier of the secondary server 200 for which the adjacency relationship has been generated as the upper server in the upper subserver information storage unit 270 as the upper subserver information 275, and the subordinate server for which the adjacent relationship has been generated as the lower server.
  • the identifier of the server 200 is stored in the lower secondary server information storage unit 280 as lower secondary server information 285.
  • the upper server information transmission unit 240 transmits the identifier of the primary server 100 in which the adjacent relationship is generated or the identifier of the secondary server 200 in which the adjacent relationship is generated as the upper server to the client 300 in which the adjacent relationship is generated. .
  • the upper secondary server information 275 includes the secondary server identifier of the secondary server 200 in which the adjacency relationship is generated as the upper server.
  • 25 and 29 are diagrams showing examples of the lower secondary server information 285 in the third embodiment of the present invention.
  • the lower secondary server information 285 includes the secondary server identifier of the secondary server 200 in which the adjacency relationship is generated as the lower server.
  • FIGS. 26 and 30 are diagrams showing examples of the sub-client list 255 in the third embodiment of this invention.
  • FIG. 31 is a diagram illustrating an example of the secondary server information 335 according to the third embodiment of this invention.
  • FIG. 19 is a sequence diagram showing an operation of registration from the secondary server 200 to another secondary server 200 in the third embodiment of the present invention.
  • the adjacency generation control unit 210 of the secondary server 200 and the adjacency generation control unit 210 of the other secondary server 200 are described above.
  • Proximity registration is performed using such a method (step S201).
  • the secondary server 200 and the other secondary server 200 acquire the other party's identifier.
  • the adjacent relationship generation control unit 210 of one of the two secondary servers 200 that performed proximity registration registers a “neighbor relationship generation request” including the primary server information 265 and the higher secondary server information 275 of the local secondary server 200 as a proximity registration. Is transmitted to the secondary server 200 that has performed (step S202).
  • the adjacent relationship generation control unit 210 of the secondary server 200 that has received the “adjacent relationship generation request” similarly sends an “adjacent relationship generation response” including the main server information 265 and the upper secondary server information 275 of the own secondary server 200.
  • the “adjacent relationship generation request” is transmitted to the secondary server 200 that is the transmission source (step S203). For example, in the state 1 of FIG. 18, when the secondary server 200 (SS1) and the secondary server 200 (SS2) perform proximity registration, the secondary server 200 (SS1) and the secondary server 200 (SS2) An “adjacent relationship generation request” or “adjacent relationship generation response” including the server information 265 (null) and the upper secondary server information 275 (null) is transmitted.
  • the adjacent relationship generation control unit 210 of each of the two secondary servers 200 exchanging the “adjacent relationship generation request” and the “adjacent relationship generation response” receives the “adjacent relationship generation request” or “adjacent relationship generation response”. Based on the included upper secondary server information 275 and the upper secondary server information 275 of the own secondary server 200, whether each of the two secondary servers 200 is a representative secondary server (other secondary servers 200 are set as higher servers). It is determined whether or not an adjacent relationship is generated, and whether or not an adjacent relationship is generated between the two secondary servers 200 is determined (steps S204 and S205). Here, each of the adjacent relationship generation control units 210 determines to generate an adjacent relationship between the two secondary servers 200 if both of the two secondary servers 200 are the representative secondary servers.
  • the adjacency generation control unit 210 of the secondary server 200 (SS1) and the secondary server 200 (SS2) is such that both of the two secondary servers 200 are representative secondary servers (the upper secondary server information 275 is null). It is determined that an adjacent relationship is generated between the secondary server 200 (SS1) and the secondary server 200 (SS2).
  • the adjacent relationship generation control unit 210 of each of the two secondary servers 200 is included in the received “adjacent relationship generation request” or “adjacent relationship generation response”.
  • it is determined which of the two sub servers 200 is the upper or lower sub server 200 (steps S206 and S207).
  • the upper or lower determination is performed based on, for example, the following upper / lower determination rules.
  • (1) When only one of the two secondary servers 200 that generate the adjacency has generated an adjacency with the main server 100, the sub server 200 that has generated the adjacency with the main server 100 as an upper server. Is the upper secondary server 200.
  • (2) When both of the two secondary servers 200 that generate the adjacent relationship have not generated the adjacent relationship with the main server 100, one of the two secondary servers 200 is set as the upper server. In this case, for example, the secondary server 200 having a small identifier value is set as the upper server.
  • the adjacent relationship generation control unit 210 of the secondary server 200 (SS1) and the secondary server 200 (SS2) does not generate an adjacent relationship in which both of the two secondary servers 200 have the primary server 100 as an upper server (primary server). Since the information 265 is null), the secondary server 200 (SS1) having a small identifier value is determined as the upper server.
  • the adjacency generation control unit 210 of the lower secondary server 200 sets the identifier of the higher secondary server 200 in the higher secondary server information 275 and stores it in the higher secondary server information storage unit 270 (step S208).
  • the adjacency generation control unit 210 of the upper secondary server 200 sets the identifier of the lower secondary server 200 in the lower secondary server information 285 and stores it in the lower secondary server information storage unit 280 (step S209).
  • the generation of the adjacency relationship between the secondary servers 200 is completed through step S208 and step S209.
  • the higher-order secondary server 200 that has generated the adjacency relationship becomes a new representative secondary server of the sub-server group formed by the plurality of secondary servers 200 that have generated the adjacency relationship.
  • the identifier of the secondary server 200 (SS1) is set in the upper secondary server information 275 of the secondary server 200 (SS2) as shown in FIG.
  • the identifier of the secondary server 200 is set in the lower secondary server information 285 of the secondary server 200 (SS1) as shown in FIG.
  • the secondary server 200 (SS1) becomes a representative secondary server of the secondary server group formed by the secondary servers 200 (SS1, SS2).
  • the sub-client list transmission unit 230 of the lower secondary server 200 uses the identifier of the upper secondary server 200 set in the upper secondary server information 275 to store the sub-client list 255 stored in the sub-client list storage unit 250.
  • the data is transmitted to the upper secondary server 200 (step S210).
  • the sub client list generation unit 220 of the upper secondary server 200 adds the identifier of the client 300 included in the sub client list 255 received from the lower secondary server 200 to the sub client list 255 and stores it in the sub client list storage unit 250.
  • the secondary server 200 (SS1) receives the subclient list 255 of FIG. 30 from the lower secondary server 200 (SS2) that generated the adjacency relationship, and adds it to the subclient list 255 of the secondary server 200 (SS1).
  • the secondary server 200 (SS1) and the secondary server 200 (SS3) perform proximity registration, so that the secondary server 200 (SS1) is placed between the secondary server 200 (SS1) and the secondary server 200 (SS3).
  • An adjacency relationship is generated as a server.
  • the secondary server 200 (SS1) becomes a representative secondary server of the secondary server group formed by the secondary servers 200 (SS1 to SS3).
  • the secondary server 200 (SS1) and the secondary server 200 (SS4) which is the representative secondary server of another secondary server group, perform proximity registration, so that the secondary server 200 (SS1) and the secondary server 200 (SS4)
  • the adjacency relationship is generated with the secondary server 200 (SS1) as the upper server.
  • the secondary server 200 (SS1) becomes a representative secondary server of the secondary server group formed by the secondary servers 200 (SS1 to SS6).
  • the identifiers of the secondary servers 200 are set as shown in FIG. Further, the identifier of the client 300 (C1 to 12) is set in the subclient list 255 of the subserver 200 (SS1) as shown in FIG. ⁇ Registration from the secondary server 200 to the primary server 100>
  • an operation for registering the identifier of the client 300 registered in the secondary server 200 as the representative secondary server from the secondary server 200 as the representative secondary server to the main server 100 will be described.
  • the operation of registering the identifier of the client 300 registered in the secondary server 200, which is the representative secondary server, in the main server 100 is the same as in the first embodiment (FIG. 5) of the present invention.
  • step S112 the adjacency generation control unit 210 of the secondary server 200 generates an adjacency relationship with the main server 100 when the own secondary server 200 is the representative secondary server.
  • FIG. 21 is a diagram illustrating an example of the secondary server information 165 according to the third embodiment of this invention.
  • FIG. 22 is a diagram illustrating an example of the client list 155 according to the third embodiment of this invention.
  • FIGS. 23 and 27 are diagrams illustrating examples of the main server information 265 according to the third embodiment of this invention.
  • the primary server information 265 of the secondary server 200 (SS1) includes the primary server information 265 as shown in FIG.
  • the identifier of the server 100 (S0) is set. Further, as shown in FIG. 21, the identifier of the secondary server 200 (SS1) is set in the secondary server information 165 of the primary server 100 (S0). As a result, an adjacency relationship is generated between the primary server 100 (S0) and the secondary server 200 (SS1) as in state 3 in FIG. Also, the main server 100 (S0) receives the sub client list 255 of FIG. 26 from the sub server 200 (SS1), and generates the client list 155 of FIG. ⁇ Service provision from main server 100> Next, an operation for providing a service from the main server 100 to the client 300 will be described.
  • FIG. 20 is a sequence diagram showing an operation of providing a service from the main server 100 in the third embodiment of the present invention.
  • the server access unit 320 of the client 300 uses the identifier of the sub server 200 set in the sub server information 335 to send the server to the sub server 200.
  • An access request is transmitted (step S221). For example, in FIG. 18, when the client 300 (C4) registered in the secondary server 200 (SS2) (adjacent to the secondary server 200 (SS2)) accesses the main server 100, the client 300 (C4) Transmits a service access request to the secondary server 200 (SS2) based on the secondary server information 335 of FIG.
  • the higher server information transmission unit 240 of the secondary server 200 transmits the identifier as higher server information to the client 300 and redirects to the higher secondary server 200.
  • An instruction is given (step S222).
  • the secondary server 200 (SS2) transmits the identifier of the secondary server 200 (SS1) to the client 300 (C4) based on the upper secondary server information 275 in FIG.
  • the server access unit 320 of the client 300 transmits a server access request to the sub server 200 using the identifier of the upper sub server 200 included in the received upper server information (step S223).
  • the client 300 (C4) transmits a service access request to the secondary server 200 (SS1).
  • the upper server information transmission unit 240 of the upper secondary server 200 transmits the identifier to the client 300 as the upper server information and instructs redirection to the main server 100.
  • the secondary server 200 (SS1) transmits the identifier of the main server 100 (S0) to the client 300 (C4) based on the main server information 265 of FIG.
  • the server access unit 320 of the client 300 transmits a server access request to the main server 100 using the identifier of the main server 100 included in the received higher-level server information (step S225).
  • the client 300 (C4) transmits a service access request to the main server 100 (S0).
  • the access control unit 130 of the main server 100 searches whether the identifier of the client 300 that has transmitted the server access request exists in the client list 155. When the identifier of the client 300 exists in the client list 155, the access control unit 130 determines that the service can be provided to the client 300 (Step S226). Thereafter, the service providing unit 140 of the main server 100 starts providing services to the client 300. For example, since the identifier of the client 300 (C4) exists in the client list 155 of FIG. 22, the main server 100 (S0) determines that the service can be provided to the client 300 (C4) and starts providing the service. To do. In FIG.
  • a server access request (step S221). ) And a redirect instruction (step S222) are repeatedly performed until the identifier of the main server 100 is transmitted to the client 300.
  • a redirect instruction (step S222) are repeatedly performed until the identifier of the main server 100 is transmitted to the client 300.
  • the operation of the third embodiment of the present invention is completed.
  • a plurality of secondary servers 200 form a secondary server group by creating an adjacency relationship by proximity registration, and the secondary secondary server group representative secondary server includes the identifier of the client 300 in the secondary server group.
  • FIG. 32 is a diagram showing an outline of client registration according to the fourth embodiment of the present invention.
  • the third embodiment of the present invention when proximity registration is performed between the representative secondary servers of the secondary server group, the adjacency relationship is generated between the representative secondary servers.
  • the fourth embodiment of the present invention even when proximity registration is performed by the secondary server 200 that is not the representative secondary server of the secondary server group, an adjacency relationship is generated between the representative secondary servers of the secondary server group. In this respect, it differs from the third embodiment of the present invention.
  • each of the secondary server 200 (SS1) and the secondary server 200 (SS4) is a representative secondary server of the secondary server group (state 1).
  • the secondary server 200 is a representative server of each secondary server group.
  • the secondary server 200 (SS1) and the secondary server 200 (SS4) generate an adjacency relationship in which the secondary server 200 (SS1) is an upper server (state 2).
  • the secondary server 200 (SS1) becomes the representative secondary server of the secondary server group formed by the plurality of secondary servers 200 (SS1 to 6) that have generated the adjacency relationship.
  • the client 300 (C1 to 12) is registered in the server 200 (SS1).
  • the respective secondary server groups The secondary server 200 (SS1) and the secondary server 200 (SS4), which are the representative servers, generate an adjacency relationship.
  • the configuration of the ad hoc service providing system in the fourth embodiment of the present invention is the same as the configuration of the ad hoc service providing system in the third embodiment of the present invention (FIG. 17).
  • the operation of the fourth exemplary embodiment of the present invention will be described in detail with reference to the drawings.
  • the operation of “registration from the secondary server 200 to another secondary server 200”, which is different from the third embodiment of the present invention, will be described below.
  • the proximity registration is performed between the secondary server 200 of one secondary server group and the secondary server 200 of the other secondary server group, so that the representative secondary server of each secondary server group.
  • FIGS. 32 to 34 are sequence diagrams showing the registration operation from the secondary server 200 to the other secondary server 200 in the fourth embodiment of the invention. Operations from when the secondary server 200 and another secondary server 200 perform proximity registration until the “adjacent relationship generation response” and “adjacent relationship generation request” are exchanged between the two secondary servers 200 (steps S301 to S303) This is the same as the operation of the third embodiment of the present invention (FIG. 19, steps S201 to S203).
  • the adjacent relationship generation control unit 210 of each of the two secondary servers 200 exchanging the “adjacent relationship generation request” and the “adjacent relationship generation response” receives the “adjacent relationship generation request” or “adjacent relationship generation response”.
  • the processing differs as follows. “A.
  • each of the adjacent relationship generation control units 210 determines to generate an adjacent relationship between the two secondary servers 200. .
  • the two secondary servers 200 that is, the secondary server group to which the secondary server 200 that has performed proximity registration belongs. Adjacency relationships are generated between the representative secondary servers (steps S331 to S334). For example, in the state 1 of FIG.
  • the state 2 of FIG. As described above, the adjacency relationship is generated between the secondary server 200 (SS1) and the secondary server 200 (SS4) with the secondary server 200 (SS1) as an upper server.
  • the adjacent relationship generation control unit 210 of the secondary server 200 that is the representative secondary server determines to generate an adjacent relationship with the representative secondary server 200 that is higher than the secondary server 200 that has performed proximity registration. Then, the adjacency generation control unit 210 of the secondary server 200 that is the representative secondary server refers to the higher level secondary server information 275 received from the counterpart side secondary server 200 and refers to the higher level secondary server 200 of the secondary server 200 that performed proximity registration. An “adjacent relationship generation request” is transmitted to (step S321).
  • the adjacent relationship generation control unit 210 of the secondary server 200 that has received the “adjacent relationship generation request” transmits an “adjacent relationship generation response” to the secondary server 200 that is the transmission source of the “adjacent relationship generation request” (step S322). For example, in the state 1 of FIG. 32, when proximity registration is performed between the secondary server 200 (SS1) that is the representative secondary server and the secondary server 200 (SS6) that is not the representative secondary server, the secondary server 200 (SS1) Then, an “adjacent relationship generation request” including the upper secondary server information 275 (null) is transmitted to the secondary server 200 (SS6).
  • the secondary server 200 (SS6) transmits an “adjacent relationship generation response” including the higher level secondary server information 275 (SS4) to the secondary server 200 (SS1).
  • the secondary server 200 (SS1) is the representative secondary server because only the secondary server 200 (SS1) is based on the received higher secondary server information 275 and the higher secondary server information 275 of the secondary server 200 (SS1). It is determined that an adjacency is generated with the representative secondary server 200 that is higher than the secondary server 200 (SS6). Then, the secondary server 200 (SS1) refers to the received higher secondary server information 275 and transmits an “adjacent relationship generation request” including the higher secondary server information 275 (null) to the secondary server 200 (SS4).
  • the secondary server 200 transmits an “adjacent relationship generation response” including the higher level secondary server information 275 (null) to the secondary server 200 (SS1). Then, as in steps S304 and S305, the adjacent relationship generation control unit 210 of each of the two secondary servers 200 that exchanged the “adjacent relationship generation request” and the “adjacent relationship generation response” is performed between the two secondary servers 200. It is determined whether or not to generate an adjacency relationship (steps S323 and S324).
  • the secondary server 200 higher than the secondary server 200 that is not the representative secondary server among the two secondary servers 200 that performed proximity registration in step S301 is the representative secondary server, in steps S323 and S324, the two secondary servers Both 200 are representative secondary servers.
  • Adjacency relationships are generated between servers (steps S331 to S334). For example, as in state 2 in FIG. 32, an adjacency relationship is generated between the secondary server 200 (SS1) and the secondary server 200 (SS4) with the secondary server 200 (SS1) as an upper server.
  • Step S301 If the secondary server 200 that is higher than the secondary server 200 that is not the representative secondary server among the two secondary servers 200 that performed proximity registration in step S301 is not the representative secondary server, an “adjacent relationship generation request” and an “adjacent relationship generation response” Steps S321 to S324 are repeated until both of the two secondary servers 200 that have exchanged "" become representative secondary servers. “C. When both of the two secondary servers 200 are not representative secondary servers” In Steps S304 and S305, when both of the two secondary servers 200 are not representative secondary servers (FIG. 35), the adjacent relationship generation control unit 210 of each of the two secondary servers 200 establishes a connection with the secondary server 200 that has performed proximity registration. It is determined that no adjacency is generated between them.
  • the adjacent relationship generation control unit 210 refers to the higher secondary server information 275, and the secondary server 200 that has performed proximity registration with the higher secondary server 200 of the local secondary server 200.
  • An “adjacent relationship generation instruction” including the identifier is transmitted (step S311).
  • the secondary server 200 having a small identifier value transmits an “adjacent relationship generation instruction”.
  • each secondary server 200 that has received the “adjacent relationship generation instruction” refers to the upper secondary server information 275 and transfers the “adjacent relationship generation instruction” to the secondary server 200 that is the representative secondary server. For example, in the state 1 of FIG.
  • the secondary server 200 when proximity registration is performed between the secondary server 200 (SS3) that is not the representative secondary server and the secondary server 200 (SS6) that is not the representative secondary server, the secondary server 200 (SS3) An “adjacent relationship generation request” including the upper secondary server information 275 (SS1) is transmitted to the secondary server 200 (SS6). Further, the secondary server 200 (SS6) transmits an “adjacent relationship generation response” including the higher level secondary server information 275 (SS4) to the secondary server 200 (SS3). In the secondary server 200 (SS3, SS6), both the secondary servers 200 (SS3, SS6) are not representative secondary servers based on the received higher secondary server information 275 and the higher secondary server information 275 of the own secondary server 200.
  • the secondary server 200 (SS3) having a small identifier value transmits an “adjacent relationship generation instruction” including the identifier of the secondary server 200 (SS6) to the secondary server 200 (SS1), which is the upper secondary server 200.
  • the secondary server 200 which is the representative secondary server that has received the “adjacent relationship generation instruction” transmits an “adjacent relationship generation request” to the secondary server 200 indicated by the identifier included in the “adjacent relationship generation instruction” (step S312). .
  • the secondary server 200 that has received the adjacent relationship generation request transmits an “adjacent relationship generation response” to the secondary server 200 that is the transmission source of the adjacent relationship generation request (step S313).
  • the secondary server 200 (SS1) transmits an “adjacent relationship generation request” including the upper secondary server information 275 (null) to the secondary server 200 (SS6).
  • the secondary server 200 (SS6) transmits an “adjacent relationship generation response” including the higher level secondary server information 275 (SS4) to the secondary server 200 (SS1).
  • the adjacent relationship generation control unit 210 of each of the two secondary servers 200 that exchanged the “adjacent relationship generation request” and the “adjacent relationship generation response” is performed between the two secondary servers 200.
  • step S314 and S315) it is determined whether or not to generate an adjacency relationship.
  • the representative secondary server and the representative secondary server are the same as in “B.
  • Adjacent relations are generated between the representative secondary servers higher than the secondary server 200 that is not the server, that is, the representative secondary servers of the secondary server group to which the secondary server 200 that has performed proximity registration belongs (steps S321 to S334). For example, as in state 2 in FIG. 32, an adjacency relationship is generated between the secondary server 200 (SS1) and the secondary server 200 (SS4) with the secondary server 200 (SS1) as an upper server.
  • the sub-client list 255 of the lower secondary server 200 is updated as in the third embodiment (steps S210 to S211) of the present invention. It is added to the sub client list 255 of the upper secondary server 200 (steps S335 to S336).
  • the operation of the fourth embodiment of the present invention is thus completed.
  • a secondary server other than the representative secondary server is used. Adjacency can be generated by proximity registration.
  • the first secondary server group when proximity registration is performed between any secondary server 200 of the first secondary server group and any secondary server 200 of the second secondary server group, the first secondary server group This is because an adjacency relationship is generated between the representative secondary server and the representative secondary server of the second secondary server group.
  • the user of the secondary server when creating a new secondary server group by creating an adjacency relationship between secondary server groups, the user of the secondary server It is possible to generate an adjacency relationship between the secondary server groups without knowing whether the secondary server and the secondary server that performs proximity registration with the secondary server are representative secondary servers.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un système de prestations de service ad hoc, permettant d'effectuer en douceur l'inscription d'un dispositif client même en présence d'un grand nombre de dispositifs clients. Un dispositif (200) de serveur auxiliaire génère une relation de voisinage avec un client (300) par inscription de voisinage et génère une liste auxiliaire (255) de clients contenant un identifiant du client (300). Un serveur principal (100) génère une relation de voisinage avec le serveur auxiliaire (300) par inscription de voisinage et génère une liste (155) de clients en se basant sur la liste auxiliaire (255) de clients reçue du serveur auxiliaire (200). Le serveur principal (100) autorise l'accès du client (300) identifié par l'identifiant de client (300) contenu dans la liste (155) de clients.
PCT/JP2011/052963 2010-02-12 2011-02-04 Système de prestations de service ad hoc WO2011099590A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2011553906A JPWO2011099590A1 (ja) 2010-02-12 2011-02-04 アドホックサービス提供システム

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2010028786 2010-02-12
JP2010-028786 2010-02-12

Publications (1)

Publication Number Publication Date
WO2011099590A1 true WO2011099590A1 (fr) 2011-08-18

Family

ID=44367859

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2011/052963 WO2011099590A1 (fr) 2010-02-12 2011-02-04 Système de prestations de service ad hoc

Country Status (2)

Country Link
JP (1) JPWO2011099590A1 (fr)
WO (1) WO2011099590A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016096425A (ja) * 2014-11-13 2016-05-26 沖電気工業株式会社 ネットワークシステム、通信制御装置、及び通信装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008103945A1 (fr) * 2007-02-23 2008-08-28 Qualcomm Incorporated Procédé et appareil pour créer des groupes de multidiffusion basés sur la proximité

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008103945A1 (fr) * 2007-02-23 2008-08-28 Qualcomm Incorporated Procédé et appareil pour créer des groupes de multidiffusion basés sur la proximité

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
TAKASHI OSHIBA ET AL.: "Ad-hoc Endpoint Pairing for Dynamic Phone-based VoIP Enhancement with PC-based Real-time Communications", DAI 70 KAI (HEISEI 20 NEN) ZENKOKU TAIKAI KOEN RONBUNSHU (4) INTERFACE COMPUTER TO NINGEN SHAKAI, vol. 5F-2, 13 March 2008 (2008-03-13), pages 4-63 - 4-64 *
TAKASHI OSHIBA ET AL.: "Scalable Device Pairing using Adaptive Parallel Processing", IPSJ SIG NOTES, vol. 2009, no. 3, 15 January 2009 (2009-01-15), pages 127 - 132 *
YASUTAKA NISHIMURA ET AL.: "A proposal of ad hoc pairing", 2009 IEICE COMMUNICATIONS SOCIETY CONFERENCE KOEN RONBUNSHU 2, vol. B-7-26, 1 September 2009 (2009-09-01), pages 94 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016096425A (ja) * 2014-11-13 2016-05-26 沖電気工業株式会社 ネットワークシステム、通信制御装置、及び通信装置

Also Published As

Publication number Publication date
JPWO2011099590A1 (ja) 2013-06-17

Similar Documents

Publication Publication Date Title
JP5066570B2 (ja) Ｗｅｂフォーマットベースのワイヤレス通信
CN109510865B (zh) 中继装置及系统
CN107370657B (zh) 设备间应用程序联动方法及系统
JP2008131594A (ja) アプリケーション制御システムおよび制御方法
EP2651179B1 (fr) Procédé permettant de réduire un temps d'attente lors d'une annulation d'une connexion et dispositif électronique associé
US9532221B2 (en) Communicating credentials and content between multiple mobile electronic devices located within content sharing geographical area
JP2022008330A (ja) 商談支援装置、方法、及びコンピュータプログラム
US20140372528A1 (en) Information processing system, information processing apparatus, and recording medium
JP2003150481A (ja) 情報提供システム、情報端末、情報提供装置、判定装置及びそれらに用いるプログラム並びに情報提供方法
EP3425875B1 (fr) Procédé et appareil pour déterminer une position relative
KR101971621B1 (ko) 서버와 디바이스를 중개하는 방법 및 장치, 컴퓨터로 읽을 수 있는 기록 매체
JP6565607B2 (ja) 通信システム、コンテンツ取得方法、およびプログラム
CN104468499A (zh) 在跨数据处理设备传送多媒体文件前确定格式兼容性
WO2013140995A1 (fr) Système de traitement d'informations, procédé de traitement d'informations, terminal de communication, serveur, procédé de commande de ceux-ci et programme de commande
KR20150116344A (ko) 사물 인터넷 브로커링 방법 및 장치
JP5171392B2 (ja) 通信システム、情報保有装置、および管理装置
KR101931141B1 (ko) 콘텐츠를 전송하기 위한 방법 및 그 전자 장치
WO2011099590A1 (fr) Système de prestations de service ad hoc
US8832199B2 (en) Method and apparatus for connecting devices
JP6201432B2 (ja) 情報処理装置、情報処理システム及び情報処理プログラム
Yoon et al. Design of a mobile application framework with context sensitivities
JP6487278B2 (ja) 通信端末、通信方法及びプログラム
JP6524005B2 (ja) 通信端末及びプログラム
JP2004289256A (ja) 情報提供システムおよび通信端末
KR101869154B1 (ko) 복수의 스마트 기기에 대한 CoAP 메시지 기반의 비콘 서비스 제공 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11742333

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011553906

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11742333

Country of ref document: EP

Kind code of ref document: A1