Information processing device, communication device, control method, and program
Patent Information
- Application Number
- JP2021197280
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2021-12-03
- Publication Date
- 2024-11-11
- Estimated Expiration
- 2041-12-03
AI Technical Summary
The publish/subscribe type communication method is not suitable for immediate communication and may lead to indiscriminate Sidelink communication with inappropriate partner devices in cellular communication systems, particularly in 3GPP standards like LTE and 5G, due to the need for topic registration and information distribution procedures.
A system where wireless communication devices register for topics and receive Layer 2 identifiers (L2IDs) through a server, enabling direct Sidelink communication with appropriate partner devices by associating identification information and distributing information accordingly, using a publish/subscribe method combined with Sidelink communication.
Enables highly immediate communication between wireless terminals with appropriate partner devices, ensuring efficient and timely exchange of information such as traffic conditions and vehicle control data without unnecessary communication.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to setting processing for direct communication.
Background Art
[0002] As a communication method between terminals, a publish / subscribe type communication method that enables asynchronous communication between a terminal operating as a publisher that distributes information and a terminal operating as a subscriber that receives information is known (see Patent Document 1). In this communication method, the publisher registers the message to be transmitted as a topic, and the subscriber requests distribution for the topic corresponding to the information to be acquired by its own device. Then, the topic registered by the publisher is distributed to the subscriber that has requested distribution of that topic. By using this communication method, it becomes possible for the publisher and the subscriber to communicate without mutually being aware of the other device. According to this, scalability of the communication system can be ensured, and communication processing in each terminal can be easily implemented. This publish / subscribe type communication method can be applied to communication between mobile terminals.
[0003] On the other hand, in the publish / subscribe type communication method, it is necessary to execute certain procedures such as topic registration and information distribution to the subscriber, and it is not always suitable for immediate communication. Also, for example, terminals compliant with the cellular communication standards of the 3rd Generation Partnership Project (3GPP) such as Long Term Evolution (LTE) and the 5th Generation (5G) generally communicate with other terminals via the network of the cellular communication system. Thus, since terminals of the cellular communication system communicate with other terminals via a base station or other nodes, the communication itself takes a certain amount of time.
[0004] On the other hand, LTE and 5G cellular communication standards specify not only communication between base stations and terminals, but also direct communication called Sidelink communication, which is performed between a terminal and other terminals within a short range. Sidelink communication uses a Layer 2 identifier (L2ID), and the terminal generates and transmits a frame specifying the L2ID of the other device with which it is directly communicating as the destination. The terminal can also receive a frame from another terminal that includes its own L2ID as the destination and acquire data. Note that "Layer 2" refers to Layer 2 in the 3GPP protocol stack. Patent document 2 describes a technology that associates location with L2ID to efficiently perform Sidelink communication between terminals mounted on a vehicle, depending on the location of the terminal. [Prior art documents] [Patent Documents]
[0005] [Patent Document 1] Japanese Patent Publication No. 2017-027499 [Patent Document 2] Japanese Patent Publication No. 2020-188405 [Overview of the Initiative] [Problems that the invention aims to solve]
[0006] In the technology described in Patent Document 2, the L2ID is determined according to the location, and the partner with whom Sidelink communication can be performed is identified. As a result, the terminal will perform Sidelink communication indiscriminately with other terminals in the vicinity of its own device, and may not be able to communicate with the appropriate partner device with which Sidelink communication should be performed.
[0007] This invention provides a technology for wireless terminals to communicate with appropriate partner devices with high real-time accuracy. [Means for solving the problem]
[0008] An information processing device according to one aspect of the present invention includes: registration means for registering a communication device that has requested to distribute or receive such distributed information in association with identification information relating to such distribution; storage means for storing parameters for direct communication between a plurality of communication devices in association with the identification information; and providing means for providing the parameters stored in association with the identification information to a communication device that has requested to distribute or receive the information associated with the identification information. [Effects of the Invention]
[0009] According to the present invention, a wireless terminal can communicate with an appropriate partner device in real time. [Brief explanation of the drawing]
[0010] [Figure 1] This diagram shows an example of the system configuration. [Figure 2] This diagram shows an example of a situation in which a connection is established using Sidelink. [Figure 3] This figure shows an example of the device's hardware configuration. [Figure 4] This figure shows an example of the server's functional configuration. [Figure 5] This figure shows an example of information that associates a topic with an L2ID. [Figure 6] This figure shows an example of the functional configuration of a wireless communication device. [Figure 7] This diagram shows an example of the L2ID sharing process. [Figure 8] This diagram shows an example of the processing flow performed by the server. [Figure 9] This figure shows an example of the processing flow performed by a wireless communication device. [Figure 10] This diagram shows an example of a Sidelink connection using the Broadcast / Groupcast method. [Figure 11] This diagram shows an example of a Sidelink connection using the Unicast method. [Modes for carrying out the invention]
[0011] The embodiments will be described in detail below with reference to the attached drawings. Note that the following embodiments do not limit the invention as defined in the claims. While the embodiments describe multiple features, not all of these features are essential to the invention, and the features may be combined in any way. Furthermore, in the attached drawings, identical or similar configurations are given the same reference numerals, and redundant descriptions are omitted.
[0012] (System configuration) Figure 1 shows an example of the system configuration according to this embodiment. This system is a wireless communication system that enables communication between vehicles. Vehicles 102 to 104 each have an on-board wireless communication device 106. The wireless communication device 106 may be, for example, a wireless communication device compliant with the cellular communication standard of the 3rd Generation Partnership Project (3GPP). The cellular communication standard is, for example, the Long-Term Evolution (LTE) standard or the 5th generation (5G) standard, and the wireless communication device 106 is configured to communicate with the base station 105 in accordance with these standards. The communication device 106 can communicate with, for example, an information processing device (server 101) located on the internet or the cloud via the base station 105.
[0013] In this embodiment, the wireless communication device 106 is configured to be communicable with other wireless communication devices 106 by executing publish / subscribe type communication using a cellular communication system. That is, the wireless communication devices 106 mounted on the vehicles 102 to 104 function as a publisher that registers information to be distributed as a topic and a subscriber that acquires information about a predetermined topic, and have a function of performing communication. Here, the server 101 operates as a broker for this publish / subscribe type communication. That is, the server 101 receives registration of a topic from the wireless communication device 106 and distributes information related to the topic. The role of registering this topic and distributing information is called a publisher. Further, the server 101 receives a subscription registration request for a registered topic from another wireless communication device 106 and performs the registration. Distribution of information related to the topic is performed for the wireless communication device 106 for which subscription registration has been performed. The role of making this subscription registration request and receiving the distributed information is called a subscriber.
[0014] In addition, when the distance between the wireless communication device 106 and another wireless communication device 106 is sufficiently close, direct communication using Sidelink can be performed between the devices. For example, as shown in FIG. 2, as the vehicles 102 and 103 move, the wireless communication devices 106 mounted on these vehicles can enter an area where mutual Sidelink communication is possible. At this time, these wireless communication devices 106 can establish Sidelink and perform direct communication without going through the base station 105.
[0015] In this embodiment, vehicles 102 to 104 are assumed to be traveling in the direction of merging point 107. When vehicles 102 to 104 approach each other at merging point 107 or at intersections with poor visibility, it is useful for the vehicles to notify each other of their vehicle information. In this embodiment, such information notification is performed using a publish / subscribe type communication method and Sidelink communication. In this embodiment, for example, one of the wireless communication devices 106 mounted on a vehicle heading towards merging point 107 registers a topic related to merging point 107 as a publisher. Another wireless communication device 106 then registers as a subscriber to that topic and obtains information related to that topic. At this time, for example, a Layer 2 identifier (L2ID), which is identification information to be used in Sidelink communication, is assigned to each topic. Then, when vehicles 102 to 104 approach each other, Sidelink communication is performed using the L2ID. Server 101, acting as a broker, accepts registration of topics related to the merging point 107, accepts registration of subscriptions to those topics, and distributes information associated with the topics to subscribers by the publisher. Furthermore, when registering the topic, Server 101 notifies the publisher of the L2ID and distributes that L2ID to subscribers who have registered to subscribe to that topic. This enables the wireless communication devices 106 mounted on vehicles 102 to 104 to communicate directly with each other using Sidelink when they are in close proximity.
[0016] In this way, one or more wireless communication devices 106 mounted on vehicles scheduled to head towards the merging point 107 perform registration regarding a common topic by means of a publish / subscribe type communication method. As a result, these one or more wireless communication devices 106 will acquire a common L2ID. Note that the wireless communication device 106 operating as a publisher can distribute information on traffic conditions such as the road during travel obtained by analysis based on information acquired by, for example, an imaging device or sensor mounted on the vehicle and connected to the wireless communication device 106. Also, when the wireless communication devices 106 approach each other, they can exchange information for which immediacy is required by means of Sidelink communication. The information for which immediacy is required can include, for example, information for which immediacy is required among the traffic condition information, and information such as the position, speed, and vehicle control information of the vehicle on which the wireless communication device 106 itself is mounted.
[0017] On the other hand, a wireless communication device 106 not scheduled to reach the merging point 107 (for example, mounted on a vehicle whose destination does not pass through the merging point 107) can avoid unnecessary communication by not performing registration regarding that topic. In one example, vehicle 104 is generally traveling in the direction of the merging point 107 but is traveling in the lane opposite to the lane including the merging point 107. For this reason, the wireless communication device 106 mounted on vehicle 104 does not make a subscription registration request regarding the topic of this merging point 107. As a result, the wireless communication device 106 mounted on vehicle 104 can operate so as not to establish a Sidelink with the wireless communication devices 106 mounted on vehicle 102 or vehicle 103 and not to acquire the information transmitted from the publisher.
[0018] Note that in this embodiment, the operation of the wireless communication devices 106 mounted on vehicles 102 to 104 is described, but it is not limited to this. That is, the method according to this embodiment can be applied to any application in which a wireless communication device exchanges certain information with a counterpart device in a wide area cell formed by one or more base stations and performs direct communication when in proximity to the counterpart device.
[0019] (Device configuration) Figure 3 shows an example of the hardware configuration of the server 101 and the wireless communication device 106. The server 101 and the wireless communication device 106 have a CPU 301, ROM 302, RAM 303, auxiliary storage device 304, communication I / F 305, device I / F 306, and bus 307. CPU, ROM, and RAM are abbreviations for Central Processing Unit, Read Only Memory, and Random Access Memory, respectively. I / F is an abbreviation for interface.
[0020] The CPU 301 is a processor that controls the entire device by executing a computer program stored in, for example, the ROM 302. The CPU 301 may also be configured to execute processes described in this embodiment as being performed by the server 101 or the wireless communication device 106 by executing a computer program. Although Figure 3 shows one CPU 301, multiple physically separated processors or a multi-core processor may be used. Other processors such as an MPU (Micro Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), or ASIC (Application-Specific Integrated Circuit) may also be used. In other words, the CPU 301 is an example of one or more processors and may be replaced by other processors or used in combination with other processors. In one example, the processing load on the CPU 301 can be reduced by using an FPGA or DSP in combination with the CPU 301. The ROM 302 is a read-only memory configured to hold information that does not require modification, such as a computer program for device control executed by the CPU 301. RAM 303 can function, for example, as work memory when the CPU 301 executes a computer program. Auxiliary storage device 304 is a storage device that stores, for example, computer programs to be executed by the device or data to be used by the device. Information stored in auxiliary storage device 304 can be loaded, for example, into RAM 303 and processed by the CPU 301. Auxiliary storage device 304 can be composed of, for example, a hard disk drive (HDD), a solid-state drive (SSD), etc. Note that ROM 302, RAM 303, and auxiliary storage device 304 are examples of memory or storage devices, and at least one or more of these may be included in the device.
[0021] The communication interface 305 is an interface used for communication with external devices. For example, the communication interface 305 of server 101 is configured to communicate with base station 105 (for example, via one or more routers), and to communicate with the communication interface 305 of wireless communication device 106 via base station 105. The communication interface 305 of wireless communication device 106 is configured to establish a wireless connection with base station 105 and the communication interface 305 of other wireless communication devices 106 to perform wireless communication. The communication interface 305 of wireless communication device 106 is configured to connect to the core network of the cellular communication system via base station 105. Furthermore, the communication interface 305 of wireless communication device 106 is configured to communicate with various devices (for example, the communication interface 305 of server 101) connected to an external network such as the Internet via base station 105. Each device can acquire information from external devices via the communication interface 305, and can temporarily store the acquired information in, for example, the auxiliary storage device 304 or RAM 303. The device interface 306 is an interface for connecting various other devices. For example, a display device for the server administrator to check information to be managed by the server 101, or a keyboard and pointing device for operating the server 101, may be connected to the server 101 via the device interface 306. Also, for example, an in-vehicle imaging device or sensor may be connected to the wireless communication device 106 via the device interface 306.
[0022] Figure 4 shows an example of the functional configuration of server 101. Server 101 has, for example, a broker unit 401, a storage unit 402, a communication unit 403, an L2ID management unit 404, and a control unit 405. These functions can be realized, for example, by the CPU 301 executing computer programs stored in ROM 302 and RAM 303. However, it is not limited to this, and for example, some or all of the functions of server 101 described above may be implemented using dedicated hardware. Note that the functional blocks shown in Figure 4 are just examples. Some (and possibly all) of the functional blocks described may be replaced with other functional blocks that perform similar functions, some functional blocks may be omitted, or further functional blocks may be added. Also, one functional block shown in the following description may be divided into multiple functional blocks, or multiple functional blocks may be integrated into one functional block.
[0023] The broker unit 401 mediates communication between multiple communication devices (e.g., wireless communication device 106) that operate as publishers and subscribers, respectively, in a publish / subscribe communication scheme. The storage unit 402 performs control for storing various information. The communication unit 403 performs processing for communication with other devices located outside the server 101. The L2ID management unit 404 manages the L2IDs assigned to external communication devices of the server 101 that are capable of Sidelink communication. The L2ID management unit 404 may generate the L2ID and notify the external communication device, or the external communication device may, for example, perform Sidelink communication settings with a base station to obtain an L2ID and report that L2ID. In other words, the L2ID may be generated in the server 101, or it may be configured to report a value generated within, for example, a cellular communication system. The control unit 405 controls each of the above-described functions of the server 101. For example, the control unit 405 executes processing to enable each functional unit to operate in coordination.
[0024] Here, when the broker unit 401 receives a subscribe registration request from, for example, a communication device outside the server 101, it associates the identifier of the communication device with its IP address and port number, etc., and the topic name specified in the subscribe registration request. IP is an abbreviation for Internet Protocol. The topic name is identification information associated with the information to be distributed. The broker unit 401 then stores this associated information in the storage unit 402. As a result, the communication device is registered as a subscriber for the specified topic name. Furthermore, when the broker unit 401 receives a publish distribution request from a communication device acting as a publisher, it generates a publish message for distribution of the topic corresponding to the publish distribution request to subscribers. This publish message is distributed by the broker unit 401 via the communication unit 403 to the communication devices registered as subscribers for the specified topic name.
[0025] When a topic is registered in the broker unit 401, the L2ID management unit 404 obtains the L2ID necessary for Sidelink communication and stores it in the storage unit 402 in association with the topic name. The L2ID management unit 404 then notifies an external communication device acting as a publisher of the L2ID via the communication unit 403. Alternatively, the L2ID management unit 404 may have the external communication device acting as a publisher obtain the L2ID in the cellular communication system and notify the server 101 of that L2ID. In this case, the L2ID management unit 404 can store the notified L2ID in the storage unit 402. Furthermore, the L2ID management unit 404 can distribute the L2ID stored in the storage unit 402 in association with a certain topic to communication devices registered as subscribers to that topic. Furthermore, the L2ID management unit 404 may manage L2IDs only when the communication device is capable of performing communication that uses L2IDs, such as Sidelink communication, and may not manage L2IDs otherwise. In addition, if a direct communication method different from Sidelink communication is used, a function unit for managing parameters such as identifiers, modulation / demodulation information, authentication methods, encryption methods, and encryption keys used in that communication may be provided instead of the L2ID management unit 404. Furthermore, the L2ID management unit 404 may manage parameters to be used in Sidelink communication, such as modulation / demodulation information, authentication methods, encryption methods, and encryption keys, in addition to L2IDs, and may generate these parameters as needed.
[0026] As described above, the storage unit 402 stores information such as the identifier, IP address, and port number of the communication device operating as a publisher / subscriber, associating it with the topic name, and also stores the L2ID. An example of the information stored here is shown in Figure 5. As shown in Figure 5, the storage unit 402 stores the L2ID, publisher information, and subscriber information as associations with the topic name. In the example in Figure 5, three subscribers are associated with three publishers, but the number of publishers and subscribers do not have to be equal; for example, multiple subscribers may be associated with one publisher. Also, all communication devices operating as publishers may be registered as subscribers, and all communication devices registered as subscribers may operate as publishers. In other words, multiple communication devices associated with a topic name may be able to send and receive information from each other. Furthermore, the information stored in Figure 5 is just an example; other information may be stored, or the system may be configured so that some of the information shown in Figure 5 is not stored.
[0027] Figure 6 shows an example of the functional configuration of the wireless communication device 106. The wireless communication device 106 is configured to include, for example, a message processing unit 601, a storage unit 602, a control unit 603, a camera function processing unit 604, a communication unit 606, and an image analysis unit 605. These functions can be realized, for example, by the CPU 301 executing a computer program held in the ROM 302 or RAM 303. However, it is not limited to this, and for example, some or all of the functions of the wireless communication device 106 described above may be implemented using dedicated hardware. Note that the functional blocks shown in Figure 6 are merely examples. Some (or all) of the functional blocks described may be replaced with other functional blocks that perform similar functions, some functional blocks may be omitted, or further functional blocks may be added. For example, the wireless communication device 106 may have only functions related to communication processing, and the camera function processing unit 604 and the image analysis unit 605 may be omitted. Also, one functional block shown in the following description may be divided into multiple functional blocks, or multiple functional blocks may be integrated into one functional block.
[0028] The message processing unit 601 processes messages in the publish / subscribe communication method. For example, when the wireless communication device 106 is operating as a publisher, the message processing unit 601 generates a message requesting the registration of a topic for publishing and distributing a message containing information such as analysis results (road traffic information) from the video analysis unit 605. After the topic is registered, the message processing unit 601 may also generate a message requesting the distribution of the analysis results from the video analysis unit 605. Furthermore, the message processing unit 601 may generate a message requesting the deletion of a topic in order to terminate the distribution of information related to that topic. Also, when the wireless communication device 106 is operating as a subscriber, the message processing unit 601 may generate a message to receive information distributed by another wireless communication device 106 and cause the communication unit 606 to send that message. For example, the message processing unit 601 may generate a message requesting subscription registration to a topic and a message requesting its cancellation. The message processing unit 601 supplies these messages to the communication unit 606 and causes it to transmit them to the server 101. Furthermore, the message processing unit 601 can receive messages from external devices of the wireless communication device 106, such as messages related to registered topics, via the communication unit 606.
[0029] The memory unit 602 stores various information such as topic information necessary for publish / subscribe communication and L2ID necessary for Sidelink communication. The control unit 603 controls the entire wireless communication device 106. The control unit 603 is configured to control each functional unit shown in Figure 6 and perform adjustment processing so that these functional units work in coordination with each other. The camera function processing unit 604 performs processes such as acquiring image information by imaging with an image sensor, and image processing to make that image information analyzable by the video analysis unit 605, if, for example, the wireless communication device 106 is equipped with an image sensor such as a camera. The camera function processing unit 604 can also acquire image information obtained by imaging from an external image sensor connected to the wireless communication device 106 and perform image processing based on that image information. The video analysis unit 605 analyzes the image information obtained by the camera function processing unit 604 and performs detection of objects to be detected, such as analyzing the road conditions at intersections. The video analysis unit 605 detects events that may affect vehicle operation, such as the presence or absence of traffic accidents or congestion, emergency vehicles, construction vehicles, or vehicles driving abnormally. In one example, the detection results from the video analysis unit 605 can be included in the publish distribution request message by the message processing unit 601 as road traffic information, as described above.
[0030] The communication unit 606 establishes a wireless connection with the base station 105 and performs wireless communication, thereby communicating with the server 101 via the base station 105. The communication unit 606 also communicates with other devices (for example, wireless communication devices 106 mounted on other vehicles) using, for example, publish / subscribe type communication. The communication unit 606 sends a message generated by the message processing unit 601 to the base station 105, specifying the address of the server 101 as the destination information. The communication unit 606 can also send a publish distribution request generated by the message processing unit 601 to the base station 105, specifying the address of the server 101 as the destination information. As a result, these messages are forwarded from the base station 105 to the server 101. The communication unit 606 can also receive messages from the server 101 regarding registered topics via the base station 105. Furthermore, the communication unit 606 can communicate with other devices (for example, wireless communication devices 106 mounted on other vehicles) via Sidelink communication without going through the base station 105. In one example, the communication unit 606 can directly send and receive information such as the location information, driving speed, and distance traveled via Sidelink communication with the wireless communication device 106 mounted on other vehicles.
[0031] (Process flow) Next, we will explain an example of the processing flow executed in this system. Figure 7 is a diagram showing an example of the communication flow in the system. Here, we assume that vehicle A (vehicle 102) and vehicle B (vehicle 103) are traveling towards merging point 107. In the following, the wireless communication device 106 mounted on vehicle 102 will be referred to as "vehicle 102". The same applies to vehicles 103 and 104.
[0032] Vehicles 102 to 104 are configured to communicate with server 101 while in motion and to perform publish / subscribe type communication. In Figure 7, vehicles 102 and 103 are each connected to server 101 and are in a state where publish / subscribe type communication can be performed (F701). Publish / subscribe type communication can be performed according to protocols such as MQTT (Message Queueing Telementry Transport) or ROS (Robot Operating System). These are just examples, and any other communication protocol may be used. Vehicles 102 to 104 can exchange information that does not require immediate response, such as information on traffic congestion around each vehicle, using publish / subscribe type communication. Vehicles 102 and 103 will perform Sidelink communication, for example, when they are in close proximity to each other and a situation requiring immediate communication is foreseen. As an example, in this embodiment, a vehicle traveling in either the merging lane or the driving lane into which the merging lane merges will use Sidelink to communicate for control purposes to ensure proper merging around the merging point. This is merely an example, and the following processing can be applied to communication devices where it is foreseeable that highly immediate communication may be required.
[0033] In this embodiment, for example, vehicle 104 is not traveling in either the merging lane or the driving lane into which the merging lane merges. Therefore, vehicle 104 does not need to perform the highly immediate communication described here, and can therefore avoid performing the type of communication described below with vehicles 102 and 103. However, vehicle 104 can also perform publish / subscribe type communication for the exchange of general traffic information. For the exchange of such general traffic information, vehicles 102 to 104 can each act as a publisher distributing information on a predetermined topic, and also as a subscriber receiving information from other vehicles.
[0034] Vehicles 102 to 104 are configured to send and receive topic information about the merging point via publish / subscribe type communication, for example, when the lane they are traveling in merges with another lane, or when another lane merges into the lane they are traveling in. For example, a vehicle (vehicle 102) whose lane is being merged by another lane sends a topic registration request to server 101 specifying a topic name for publish distribution (F702). The topic name here may be provided by the system when publish / subscribe type communication with server 101 becomes possible. This allows, for example, multiple vehicles traveling in the same lane as vehicle 102 to act as publishers for the same topic name. In Figure 7, "join_point_A" is specified as the topic name.
[0035] Topic names can be pre-configured, for example, as names that specify topics related to merging point 107. In one example, server 101 may pre-configure information indicating topic names related to merging points, etc., included in its wireless communication area, and acquire at least a portion of this information when a vehicle initially connects to server 101. For example, when a vehicle initially connects to server 101, it may notify server 101 of its own location information, and server 101 may notify the vehicle of information associating the location information of merging points, etc., around that location with topic names. Server 101 may also estimate the vehicle's location from topic registration requests and subscribe registration requests (described later) received from the vehicle, and sequentially notify the vehicle of topic names of merging points, etc., around that vehicle. Furthermore, the vehicle may acquire and store information associating merging points, etc., with topic names in a batch during production or when setting up the navigation system. Merging points are just one example; topic names associated with any traffic-related information, such as intersections, junctions, areas with many pedestrians, or slopes, can be predefined and stored in the vehicle. Furthermore, non-traffic-related information (such as tourist information or event information) may be shared via publish / subscribe type communication, and topic names may be specified for such temporary information. Note that topic names may be expressed using names understandable to human users. For example, a list of topic names could be displayed in candidate subscriber vehicles, allowing users to select a topic name and retrieve information. Also, topic names may be expressed using names that are difficult for humans to understand, as long as the in-vehicle wireless communication device 106 can determine them. In other words, in cases where human involvement is not involved, such as in the vehicle's automated driving control, topic names can be specified using any string of characters.
[0036] When server 101 receives a topic registration request message in F702, it executes the registration process for the topic name specified in the message (F703). In this case, the topic name specified is "join_point_A". As shown in Figure 5, server 101 registers the information of vehicle 102's wireless communication device 106 (terminal identifier, IP address, port number, etc.) as the publisher for this topic name. Server 101 also generates a Layer 2 identifier (L2ID) necessary for communication in case vehicle 102, the source of this message, performs Sidelink communication with another vehicle (F703). Server 101 then notifies vehicle 102, the source of the message, of the generated L2ID (F704). Note that if the topic "join_point_A" has already been registered in response to a request from another vehicle, server 101 does not create new information about the topic, but instead registers vehicle 102 as the publisher of that topic. Furthermore, instead of generating a new L2ID, the server 101 notifies the vehicle 102 of the L2ID that is already associated with that topic and stored in memory. Note that at the time of generating the L2ID, the vehicle 102 may perform processes such as generating a common encryption key that can be used for encrypting and decrypting data in Sidelink communication.
[0037] When vehicle 102 receives an L2ID from server 101, it configures Sidelink communication (F705). For example, vehicle 102 configures itself to use the received L2ID as the source identifier and destination identifier for Sidelink communication, thereby enabling Sidelink communication. This allows vehicle 102 to perform Sidelink communication with other vehicles that share the same L2ID. Vehicle 102 sets the received L2ID as the source and destination and begins broadcasting its own location information, driving speed, distance traveled, etc., via Sidelink communication (F706).
[0038] On the other hand, a vehicle (vehicle 103) whose lane is being merged into another lane sends a subscribe request message to server 101 to receive information about the merging point 107 (F707). At this time, vehicle 103 sends the subscribe request message specifying the topic name "join_point_A" related to the merging point 107. When server 101 receives this subscribe request, it searches whether a topic related to the specified topic information is registered. If server 101 confirms that the topic "join_point_A" is registered, it distributes the L2ID stored in association with that topic name to vehicle 103 (F708). When vehicle 103 receives the L2ID distributed from server 101, it configures itself for Sidelink communication (F709). This configuration is the same as in F705. Once the vehicle 103 has completed the setup, it sets the received L2ID as the source and destination and begins broadcasting its own location information, driving speed, distance traveled, etc. via Sidelink communication (F710).
[0039] Here, we will explain Sidelink communication. Sidelink communication includes the "Broadcast communication method," the "Groupcast communication method," and the "Unicast communication method." When the "Broadcast communication method" or the "Groupcast communication method" is used, as shown in Figure 10, a wireless frame containing data set as the source and destination identifiers in the transmitting device is transmitted using the shared L2ID. The receiving device then extracts data from the wireless frame when it receives a wireless frame in which the source and destination identifiers match the shared L2ID. In this way, data communication becomes possible through the sharing of the L2ID. On the other hand, when "Unicast communication" is used, as shown in Figure 11, the transmitting device sends a connection request to the shared L2ID as the destination. The receiving device that shares that L2ID then responds to this connection request and exchanges security information. Then, in response to the receiving device sending a response to the connection request to the destination device, data communication becomes possible between these devices. The method according to this embodiment is applicable regardless of the communication method used, but here we will assume that the "Groupcast communication method" is used.
[0040] Furthermore, the information broadcast by F706 and F710 will not be received unless two wireless communication devices 106 configured for Sidelink communication using the same L2ID are in close proximity. In this situation, vehicle 102 distributes traffic road information based on the environment it has detected, for example, via wide-area communication through base station 105 using a publish / subscribe type communication. That is, vehicle 102 sends a message containing the traffic road information to server 101 for the purpose of publishing and distributing the traffic road information (F711). Vehicle 103 can also receive the traffic road information distributed by vehicle 102 from server 101, for example, via wide-area communication through base station 105 (F712).
[0041] Subsequently, as vehicles 102 and 103 each proceed toward and approach the merging point 107 (F713), vehicles 102 and 103 become capable of receiving vehicle information broadcast by the other device. In response to this state, Sidelink communication is performed between vehicles 102 and 103 (F714). At a specific location such as the merging point 107, steering and brake control are expected to occur in each vehicle, so low-latency information exchange between vehicles may be required. For this reason, in this embodiment, when vehicles 102 and 103 are in close proximity to each other near the merging point 107, they transmit and receive information such as their respective vehicle positions, speeds, and distance traveled via Sidelink communication (F715). Through this transmission and reception of information, each vehicle can not only ascertain the presence of other vehicles at the merging point 107, but also ascertain information such as the location and speed of those vehicles, making it possible, for example, to provide driving assistance to the driver. Furthermore, the ability to exchange information with low latency allows each vehicle to take action such as controlling the order of merging into traffic and controlling braking in emergencies. In addition, road traffic information such as accidents, congestion, emergency vehicles, construction vehicles, and vehicles driving abnormally, which is distributed via wide-area communication, can also be transmitted with low latency via Sidelink communication.
[0042] Subsequently, it is assumed that vehicle 103 has completed its merge (F716). In this case, vehicle 103 no longer needs to acquire any more information on the topic related to the merge point 107. Therefore, vehicle 103 sends an unsubscribe request message to server 101 to cancel the reception of published information (F717). Then, vehicle 103 deletes the L2ID associated with the topic related to the merge point 107 and stops Sidelink communication (F718). Note that vehicle 103 may perform this process not only when the merge is complete, but also, for example, if it changes course and no longer passes through the merge point 107. Note that if vehicle 103 does not approach vehicle 102 in this way, Sidelink communication between these vehicles will not occur, and settings such as the L2ID will be deleted. Furthermore, in vehicle 102, once the merge is complete and it has passed the merging point 107, or if it has changed lanes from the merging lane (F719), it is no longer necessary to distribute any further information about the topic related to merging point 107. In this case, vehicle 102 sends a topic deletion request message to server 101, specifying the topic name "join_point_A" for the topic related to merging point 107 (F720).
[0043] This topic deletion request message is a request to delete the specified topic. However, in this embodiment, as described above, there may be multiple publishers for a common topic. Therefore, if only vehicle 102 is registered as a publisher for that topic, server 101 deletes the topic, and if other publishers exist for that topic, it removes vehicle 102's information from the publisher list. Then, regardless of whether or not the topic is deleted, server 101 sends an L2ID invalidation notification to vehicle 102 to cause vehicle 102 to delete its L2ID (F721). Then, if there are no longer any publishers for the topic specified in the topic deletion request message, server 101 deletes the topic and its L2ID (F722). On the other hand, server 101 may maintain the topic and its L2ID if, for example, there are publishers other than vehicle 102 for that topic.
[0044] Upon receiving the L2ID invalidation notification, vehicle 102 deletes the L2ID and terminates Sidelink communication using that L2ID (F723). However, if vehicle 102 has other L2IDs associated with other topics, it may continue Sidelink communication (sending of broadcast information) using those L2IDs. In other words, Sidelink communication regarding the merging point 107 may be prevented here, while Sidelink communication corresponding to other locations or traffic events may be maintained. Note that in Figure 7, server 101 sends the L2ID invalidation notification only to vehicle 102, but for example, it may also send the L2ID invalidation notification to vehicle 103 as a response to the unsubscribe request message. Alternatively, server 101 may not send the L2ID invalidation notification to vehicle 102, and vehicle 102 may delete the L2ID corresponding to the topic specified in the topic request message and its associated configuration information upon sending the topic deletion request message.
[0045] Furthermore, in the example above, vehicle 103 sends an unsubscribe request message, and then vehicle 102 sends a topic deletion request message. As a result, for the topic related to merging point 107, the publisher ceases to exist after the subscriber ceases to exist. In contrast, the publisher may send a topic deletion request message first, and the publisher for a certain topic may cease to exist before the subscriber. In this case, the topic may be deleted when the publisher ceases to exist, or the topic and L2ID may be maintained by the subscriber alone. For example, if there are no other vehicles in the lane that vehicle 102 is traveling in, it is expected that information will not be delivered to vehicle 103 even if vehicle 103 has subscribed, so the topic and L2ID may be deleted when the publisher ceases to exist. On the other hand, by maintaining the topic and L2ID, when other vehicles approaching merging point 107 later register as publishers, vehicle 103 can receive the delivered information without having to re-register as a subscriber.
[0046] Alternatively, instead of a topic deletion request message or an unsubscribe request message, another message requesting the termination of information distribution or the termination of receiving distributed information may be sent or received. In this case as well, the topic and L2ID may be deleted when the publisher ceases to exist, or the topic and L2ID may be deleted when the registered vehicles, including subscribers, cease to exist.
[0047] (Server operation) Next, the operation of the server 101 will be explained using Figure 8. The processes described below can be implemented, for example, by the CPU 301 of the server 101 executing a computer program stored in the ROM 302 or loaded into the RAM 303 from the auxiliary storage device 304. Note that this is just one example, and some or all of the following processes may be implemented by dedicated hardware.
[0048] When the server 101 receives a topic registration request message from the wireless communication device 106 via the communication unit 403 by the broker unit 401 (YES in S801), it performs registration processing for the topic name specified in the message. The server 101 also uses the L2ID management unit 404 to generate a Layer 2 identifier (L2ID) necessary for Sidelink communication in case the wireless communication device 106 that sent the message performs Sidelink communication (S802). The server 101 then uses the storage unit 402 to store the L2ID in association with the topic name specified in the message (S803), and the communication unit 403 notifies the wireless communication device 106 that sent the message of the L2ID (S804).
[0049] Meanwhile, server 101 waits for subscribe registration request messages from other vehicles (S805). When server 101 receives a subscribe registration request message (YES in S805), it checks whether an L2ID exists that corresponds to the topic name specified in the message. If such an L2ID exists, server 101 distributes that L2ID to the message sender (S806). This makes it possible for vehicles acting as subscribers to communicate with a vehicle acting as a publisher without going through base station 105 when the subscriber vehicle approaches the publisher vehicle.
[0050] Server 101 acts as a broker, mediating communication between publishers and subscribers when there are topics for which both publishers and subscribers have completed registration. Specifically, Server 101 waits for publishers to register information to be distributed (S807), and when such information is registered (YES in S807), it distributes that information to subscribers (S808). Sidelink communication takes place when a vehicle acting as a publisher approaches a vehicle acting as a subscriber, but Server 101 does not participate in this communication. Subsequently, Server 101 repeats waiting for registration of information to be distributed and distributing the registered information until it receives a topic deletion request message from the publisher (NO in S809). Even if Server 101 receives a topic deletion request message from the publisher (YES in S809), it will not delete the topic if other publishers are registered for that topic (YES in S810). In other words, if the publisher no longer exists (NO in S810), server 101 deletes the topic (S811). When a topic is deleted, the associated L2ID is also deleted. After deleting the topic, server 101 notifies the publisher that sent the topic deletion request message that the L2ID has been invalidated (S812), and then terminates the process.
[0051] Note that while Figure 8 shows an example where notification is given that an L2ID has been deactivated after it has been deleted, the server is not limited to this example. Even if the L2ID has not actually been deleted, the server 101 may, for example, send an instruction to the device that sent the topic deletion request message to deactivate the L2ID of the sender of that message. Also, if the server 101 receives an unsubscribe request message corresponding to a topic, it may send a message to the device that sent that message to deactivate the L2ID.
[0052] (Operation of wireless communication device) Next, the operation of the wireless communication devices 106 mounted on vehicles 102 to 104 will be explained using Figure 9. The processes described below can be realized, for example, by the CPU 301 of the wireless communication device 106 executing a computer program stored in the ROM 302 or loaded into the RAM 303 from the auxiliary storage device 304. Note that this is just one example, and some or all of the following processes may be realized by dedicated hardware. In the following, unless otherwise specified, the wireless communication device 106 mounted on vehicle 102 will be referred to as "vehicle 102," and the wireless communication devices 106 mounted on vehicles 103 and 104 will similarly be referred to as "vehicle 103" and "vehicle 104."
[0053] Vehicles 102 to 104, while in motion, determine, based on their own location information and map information such as car navigation systems, whether they have a chance of reaching a point where they can merge with another lane in their direction of travel. For example, vehicles 102 to 104 determine if there are other lanes that could merge into the lane they are currently traveling in (S901). If vehicles 102 to 104 determine that there are no other lanes that could merge into the lane they are currently traveling in (NO in S901), they determine whether the lane they are currently traveling in has a chance of merging with another lane (S911). If vehicles 102 to 104 determine that there are no other lanes that could merge into the lane they are currently traveling in, and that there is no chance of the lane they are currently traveling in merging with another lane (NO in both S901 and S911), they terminate the process. In the example in Figure 1, vehicle 102 is traveling in a lane from which another lane, in which vehicle 103 is traveling, merges, and therefore determines that there is another lane that could merge into the lane in which vehicle 102 is traveling (YES in S901). The lane in which vehicle 103 is traveling is the lane that merges into the lane in which vehicle 102 is traveling. Therefore, vehicle 103 determines that there is no other lane that could merge into the lane in which vehicle 103 is traveling, but that the lane in which vehicle 103 is traveling may merge into another lane (NO in S901, YES in S911). On the other hand, the lane in which vehicle 104 is traveling does not merge into another lane, nor are there any lanes merging from other lanes. Therefore, vehicle 104 determines that there are no other lanes that could merge into the lane it is currently traveling in, and that there is no possibility of the lane it is traveling in merging into another lane (NO in S901 and S911), and terminates processing without performing any further actions.
[0054] First, let's focus on vehicle 102. Vehicle 102 uses the message processing unit 601 and the communication unit 606 to send a topic registration request message to the server 101, specifying the topic name for publishing (S902). The information to be published is, for example, road traffic information such as the presence or absence of accidents, traffic jams, emergency vehicles, construction vehicles, and abnormally driven vehicles, which is generated by the camera function processing unit 604 and the video analysis unit 605.
[0055] After sending a topic registration request message, vehicle 102 receives an L2ID from server 101 that is necessary for performing Sidelink communication with other vehicles (S903), and then configures for Sidelink communication (S904). Then, vehicle 102, using its communication unit 606, starts broadcasting to the surroundings a wireless frame for Sidelink communication that includes information such as its own location, driving speed, and distance traveled, with the L2ID as the source and destination (S905). On the other hand, although vehicle 102 has completed the configuration for performing Sidelink communication with another vehicle that shares the same L2ID at this point, it cannot perform Sidelink communication unless it approaches that other vehicle within a predetermined distance range. In this case, vehicle 102 acts as a publisher in a publish / subscribe type communication and distributes information. In other words, when vehicle 102 generates traffic road information to be distributed by the camera function processing unit 604 and the video analysis unit 605 (YES in S906), it publishes the traffic road information to the server 101 using the communication unit 606 (S907). Subsequently, vehicle 102 determines whether it can perform Sidelink communication depending on whether it has approached another vehicle (e.g., vehicle 103) that has a common L2ID to the extent that it can receive notification information via Sidelink communication (S908). Then, if there is another vehicle that can perform Sidelink communication with vehicle 102 (YES in S908), it performs Sidelink communication with that vehicle (S909).
[0056] Subsequently, when vehicle 102 has passed merging point 107 after completing the merge, or when it is no longer involved with merging point 107 due to a lane change or other reasons, it no longer needs to distribute information on the topic related to merging point 107. In such cases, vehicle 102 may use the message processing unit 601 and the communication unit 606 to send a topic deletion request message to server 101 regarding the topic related to merging point 107 (S910). By sending this message, vehicle 102 ceases to be the publisher of the topic related to merging point 107. After sending this message, if vehicle 102 receives an L2ID invalidation notification from server 101, it deletes the L2ID and the Sidelink communication settings using that L2ID. Vehicle 102 may also delete the L2ID and related settings corresponding to the topic name specified in the topic deletion request message in response to sending the topic deletion request message.
[0057] Next, we will explain focusing on vehicle 103. Since vehicle 103 is traveling in the lane that is merging (YES in S911), the message processing unit 601 sends a subscribe registration request message to the server 101, specifying the topic name corresponding to the merging point 107 (S912). Then, the communication unit 606 of vehicle 103 receives a message from the server 101 that includes the L2ID corresponding to the specified topic name (S913). Upon receiving the L2ID, vehicle 103 uses that information to configure Sidelink communication (S914). Then, the communication unit 606 of vehicle 103 starts broadcasting to the surroundings, including information such as the vehicle's position, speed, and distance traveled, in a wireless frame for Sidelink communication with the L2ID as the source and destination (S915). Note that the processing in S914 and S915 is the same as the processing in S904 and S905. Vehicle 103, like vehicle 102 described above, has already been configured at this point to perform Sidelink communication with another vehicle that shares the same L2ID. However, Sidelink communication cannot be performed unless it approaches that other vehicle within a predetermined distance. Therefore, vehicle 103 receives information as a subscriber in a publish / subscribe type communication. That is, vehicle 103 receives information from server 101 regarding topics that it has subscribed to (S916).
[0058] Subsequently, vehicle 103 determines whether it can perform Sidelink communication depending on whether it has approached another vehicle (e.g., vehicle 102) that has a common L2ID to the point where it can receive notification information via Sidelink communication (S917). If there is another vehicle that can perform Sidelink communication (YES in S917), vehicle 103 performs Sidelink communication with that vehicle (S918). Subsequently, vehicle 103 may no longer perform Sidelink communication with vehicle 102 at merging point 107 if the merging is completed or if it changes course before reaching merging point 107 and does not perform the merging. In such cases, vehicle 103 no longer needs to receive information distribution corresponding to merging point 107. For this reason, vehicle 103 may use the message processing unit 601 and the communication unit 606 to send an unsubscribe request message to the server 101 regarding the topic of merging point 107 (S919).
[0059] Then, by sending this message, vehicle 103 terminates the communication processing related to the merging point 107. Vehicle 103 can repeatedly perform the above-mentioned processes of vehicle 103 or vehicle 102, such as requesting subscription registration for the corresponding topic or requesting topic registration, depending on the route it is traveling on, and can appropriately send and receive information in accordance with the situation in which it is located.
[0060] In the example described above, vehicle 102, traveling in a lane where other lanes merge, acts as a publisher, and vehicle 103, traveling in a lane merging with other lanes, acts as a subscriber. However, the system is not limited to this example. For example, vehicle 102 may be configured to act as a subscriber and vehicle 103 as a publisher. Alternatively, both vehicle 102 and vehicle 103 may act as both publishers and subscribers. That is, vehicle 102 may receive traffic information from vehicle 103, and vehicle 103 may receive traffic information from vehicle 102. In this case, the topic name of the topic in which vehicle 102 acts as a publisher and the topic name of the topic in which vehicle 103 acts as a publisher may be the same or different.
[0061] In this embodiment, vehicles 102 and 103 can exchange traffic road information before they come into close proximity by using publish / subscribe type communication regarding a topic related to the merging point 107. Furthermore, since vehicles 102 and 103 are heading towards a common area (merging point 107), it is expected that these vehicles will come into close proximity. For this reason, when these vehicles register for publish / subscribe type communication, server 101 allows them to share an L2ID for Sidelink communication. This makes it possible to use Sidelink communication for exchanging control information and other information that requires immediacy as the vehicles approach each other.
[0062] The distribution of traffic information via publish / subscribe type communication is just one example, and such information does not necessarily have to be distributed. For example, only L2ID information may be distributed. In one example, a vehicle notifies a designated server of the geographical areas (e.g., the aforementioned merging point 107) that it may pass through or approach while driving, and obtains L2ID information for each of those geographical areas. Then, when the vehicle comes into close proximity with another vehicle, it can perform Sidelink communication based on that L2ID information. Alternatively, instead of the vehicle publishing and distributing information, the server may distribute general traffic information or information based on image information obtained from surveillance cameras, etc. In this case, the vehicle can receive information on its driving route or planned driving route, and when registering for the distribution of that information, it can be assigned an L2ID, thereby enabling Sidelink communication with other nearby vehicles. In such a case, the wireless communication devices to be registered may be registered without distinction between publishers and subscribers. Furthermore, Sidelink communication is merely one form of direct communication, and other forms of direct communication may also be used. In this case, other parameters may be notified to the vehicle instead of the L2ID mentioned above. That is, the server may register wireless communication devices involved in information distribution (distributing or receiving information) in association with identification information (topic name) corresponding to the information being distributed, and may associate and maintain parameters for direct communication, such as the L2ID, with that identification information. The server then provides the parameters associated with that identification information to the wireless communication devices registered in association with that identification information. This makes it possible for multiple wireless communication devices associated with the same identification information to communicate directly.
[0063] Furthermore, as mentioned above, this method can be used not only to link information distribution related to traffic information with direct communication, but also for various other purposes. For example, regarding a wireless communication device that receives information distribution about a common hobby, the server registers the wireless communication device in association with identification information related to the distributed information. At that time, the server provides the wireless communication device with parameters for direct communication that are associated with that identification information. The wireless communication device can then be configured to communicate directly with other devices that have received those parameters when it is in close proximity to them. This makes it possible for users with a common hobby to communicate directly and exchange information when they are in close proximity to each other.
[0064] The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions.
[0065] The invention is not limited to the embodiments described above, and various modifications and variations are possible without departing from the spirit and scope of the invention. Accordingly, claims are attached to disclose the scope of the invention. [Explanation of Symbols]
[0066] 101: Server, 105: Base station, 106: Wireless communication equipment, 401: Broker unit, 404: L2ID management unit, 601: Message processing unit
Claims
1. a registration means for registering a communication device that has requested distribution of information and a communication device that has requested receipt of the distributed information in association with identification information that identifies a topic of the distribution; a storage means for storing parameters for direct communication between a plurality of communication devices in association with the identification information; a providing means for providing a first parameter stored in association with the first identification information to a first communication device that has requested distribution of information on a first topic corresponding to first identification information and to a second communication device that has requested receipt of the information on the first topic corresponding to the first identification information; 13. An information processing device comprising:
2. 2. The information processing device according to claim 1, wherein the registration means registers a topic name of information distributed by publish / subscribe type communication as the identification information, and associates a communication device operating as a publisher and a communication device operating as a subscriber with the topic name.
3. 3. The information processing device according to claim 1, wherein the direct communication is Sidelink communication in the Third Generation Partnership Project (3GPP), and the parameter is a Layer 2 Identifier (L2ID).
4. 4. The information processing apparatus according to claim 1, wherein the parameters include an encryption key.
5. 5. The information processing apparatus according to claim 1, further comprising a generating unit for generating the parameters.
6. The information processing device according to any one of claims 1 to 5, characterized in that when a communication device registered in association with the identification information requests an end to the distribution of information associated with the identification information or the end of receiving the distributed information, the providing means notifies the communication device that the parameters associated with the identification information are invalid.
7. The information processing device according to any one of claims 1 to 6, characterized in that the registration means cancels the registration of a communication device registered in association with the identification information when the communication device requests to end the distribution of information associated with the identification information or the reception of the distributed information.
8. the registration means deletes the identification information when a communication device associated with the identification information and registered therein no longer exists as a result of the cancellation; 8. The information processing apparatus according to claim 7, wherein said storage means deletes said parameters stored in association with said identification information when said identification information is deleted.
9. the registration means registers a communication device that distributes information associated with the identification information and a communication device that receives the distributed information, the registration means deletes the identification information when there is no longer a communication device that distributes information associated with the identification information due to the cancellation; the storage means deletes the parameter stored in association with the identification information when the identification information is deleted; The providing means notifies a communication device that receives distribution of information associated with the deleted identification information that the parameter is invalid.
8. The information processing apparatus according to claim 7,
10. 1. A communication device, comprising: a notification means for notifying an information processing device of a request for information distribution or for receiving distributed information, the request being associated with identification information identifying a topic of the distribution and for registering the communication device; receiving means for receiving parameters for direct communication with another device in response to said request, said parameters being associated with said identification information; a communication means for directly communicating with another communication device that has received the parameters and is associated with the identification information and registered by the information processing device, using the parameters, to deliver or receive information on a topic corresponding to the identification information; A communication device comprising:
11. The delivery of information or receipt of delivered information is done through a publish / subscribe model of communication; 11. The communication device according to claim 10, wherein the identification information is a topic name of information distributed by the publish / subscribe type communication.
12. 12. The communication device according to claim 10 or 11, characterized in that the direct communication is a Sidelink communication in the Third Generation Partnership Project (3GPP), and the parameter is a Layer 2 Identifier (L2ID).
13. 13. The communication device according to claim 10, wherein the parameters include an encryption key.
14. The notification means notifies the information processing device of a request for a communication device registered in association with the identification information to terminate delivery of information associated with the identification information or termination of reception of the delivered information, 14. The communication device according to claim 10, wherein the communication means, based on the notification of the request to terminate, does not perform direct communication using the received parameters.
15. the receiving means receives a notification of invalidation of the parameter based on the request for termination; 15. The communication device according to claim 14, wherein said communication means, based on receipt of the invalidation notification, does not perform direct communication using the received parameters.
16. A control method executed by an information processing device, comprising: registering a communication device that has requested distribution of information and a communication device that has requested receipt of the distributed information in association with identification information that identifies a topic of the distribution; storing parameters for direct communication between a plurality of communication devices in association with the identification information; providing a first parameter stored in association with the first identification information to a first communication device that has requested distribution of information on a first topic corresponding to first identification information and to a second communication device that has requested reception of the information on the first topic corresponding to the first identification information; A control method comprising:
17. A control method performed by a communication device, comprising: notifying an information processing device of a request for delivery of information or for receiving delivered information, the request being associated with identification information identifying a topic of the delivery and for the communication device to be registered; receiving parameters for directly communicating with another device in response to the request, the parameters being associated with the identification information; Delivering or receiving information on a topic corresponding to the identification information by directly communicating with another communication device that has been registered in association with the identification information by the information processing device and received the parameters, using the parameters; A control method comprising:
18. A program for causing a computer to function as the information processing device according to any one of claims 1 to 9.
19. A program for causing a computer to function as the communication device according to any one of claims 10 to 15.
