WO2022124036A1

WO2022124036A1 - Communication device, communication method, and communication system

Info

Publication number: WO2022124036A1
Application number: PCT/JP2021/042405
Authority: WO
Inventors: 亮太木村
Original assignee: ソニーグループ株式会社
Priority date: 2020-12-08
Filing date: 2021-11-18
Publication date: 2022-06-16
Also published as: JP2024015458A

Abstract

[Problem] To provide a communication device, a communication method, and a communication system that realize efficient broadcasting or multicasting of relevant data. [Solution] This communication device comprises a first reception unit for receiving a first request message that requests the transmission of relevant data to at least one information device to which the data is to be broadcasted or multicasted, and a first transmission unit for transmitting the relevant data to the at least one information device on the basis of the first request message.

Description

Communication equipment, communication methods and communication systems

This disclosure relates to communication devices, communication methods and communication systems.

Blockchain is used as a technology to realize a distributed ledger for settlement of virtual currency and cryptocurrency and management of transaction data of remittance. In the future, there is a possibility that the number of applications that use blockchain will increase in addition to virtual currencies and cryptocurrencies. For example, distribution traces, rights processing (eg copyrights, land rights), sharing of monitoring data, etc. can be considered.

Depending on the application that uses the blockchain, communication via a wireless network may be required. In particular, in a system using a blockchain, messages such as transactions and approval data are exchanged on a broadcast or multicast basis. Efficient broadcast or multicast bases are required on wireless networks. However, conventional wireless networks do not support efficient broadcast or multicast-based methods when sending messages from a terminal device over an uplink. For example, when a terminal device transmits a message on a broadcast or multicast basis, it is necessary to form a connection (or session) for each device to be transmitted and transmit the message.

Japanese Patent Publication No. 2007-527178

The present disclosure provides a communication device, a communication method, and a communication system that can efficiently broadcast or multicast the target data.

The communication device of the present disclosure is based on a first receiving unit that receives a first request message requesting transmission of target data to at least one information device to be broadcast or multicast, and the first request message. A first transmission unit that transmits the target data to the at least one information device.

The communication device of the present disclosure comprises a processing unit that generates a first request message requesting a server to transmit target data to at least one information device that is a target of broadcast or multicast, and the first request message. It is provided with a transmission unit that transmits to the server via an uplink.

The communication method of the present disclosure receives a first request message requesting transmission of target data to at least one information device to be broadcast or multicast, and based on the first request message, the at least one device. The target data is transmitted to the information device of.

The communication method of the present disclosure generates a first request message requesting a server to transmit target data to at least one information device to be broadcast or multicast, and the first request message is transmitted by uplink. Send to the server.

The communication system of the present disclosure links a processing unit that generates a first request message requesting transmission of target data to at least one information device to be broadcast or multicast, and the first request message. The target data is transmitted to at least one information device based on the first communication device including the transmission unit for transmitting the first request message, the reception unit for receiving the first request message, and the first request message. A second communication device including a transmitter and a second communication device.

The block diagram of the distributed network provided with the blockchain system which is the information processing system which concerns on 1st Embodiment of this disclosure. The figure which shows an example of a communication network. The figure which showed the blockchain communication between the application layers of a plurality of terminal devices from the viewpoint of a protocol stack. A diagram showing an example of broadcasting approval data including information about a block approved from a terminal device from the viewpoint of the application layer. The figure which shows the example which a terminal apparatus forms a connection with other terminal apparatus via a base station. The figure which shows the example which a terminal device broadcasts approval data to another terminal device through a core network. The figure which shows the outline of a blockchain. In the blockchain system of FIG. 1, a diagram schematically showing an example in which user A registers target data to be a transaction. The figure which shows the example which the terminal device first discovers a nonce which meets a predetermined condition, and broadcasts or multicasts an approval request. The block diagram of the terminal apparatus including the communication apparatus which concerns on embodiment of this disclosure. The block diagram of the BC server including the communication apparatus which concerns on embodiment of this disclosure. The figure which shows the specific example of the communication system of FIG. 1 as the communication system which concerns on this embodiment. The figure which shows the other specific example of the communication system of FIG. The figure which shows still another specific example of the communication system of FIG. The figure which shows the sequence example which the terminal apparatus acquires the information of BC server from the initial setting server of a blockchain system. The sequence diagram which shows an example of the procedure of broadcasting a BC message using a BC server. The figure which shows the sequence example of the operation of the on-demand type broadcast. The flowchart of an example of the process of performing an on-demand type broadcast in a BC server. The figure which shows the sequence example of the operation of a push type broadcast. The figure which shows the other example of the sequence of the operation of the push type broadcast. A flowchart of an example of a process of performing a push-type broadcast on a BC server. The flowchart of another example of the process of performing a push-type broadcast in a BC server. The figure which shows the sequence example of the operation of a pull type broadcast. A flowchart of an example of a process of performing a pull-type broadcast on a BC server. Flowchart of another example of the process of performing a pull-type broadcast. The figure which shows the example which maps BC request message to DTCH (or BCH), UL-SCH, PUSCH in the terminal apparatus on the transmitting side. An example of transmitting a BC request message mapped to BCH in a terminal device to a base station via UL-BCH and PUBCH is shown. FIG. 6 is a diagram showing an example in which a BC request message is received in a base station with a mapping opposite to the channel mapping shown in FIG. 27. The figure which shows the sequence example of the operation which a terminal apparatus maps a BC request message and a channel, and sends a BC request message. An example of the sequence from the terminal device transmitting the BC request message to the base station to the reception of the BC message by another terminal device is shown. The figure which shows the sequence example when the base station fails to receive a BC request message. A flowchart of an example of the operation of the retransmission process in the terminal device. The figure which shows the format example of the body part of a BC request message. The figure which shows an example of the hardware composition of the communication apparatus which concerns on this embodiment.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In one or more embodiments shown in the present disclosure, the elements included in each embodiment can be combined with each other, and the combined result is also part of the embodiments shown in the present disclosure.

FIG. 1 is a block diagram of a distributed network provided with a blockchain system, which is an information processing system according to the first embodiment of the present disclosure. The distributed network (blockchain system) 100 of FIG. 1 includes a plurality of terminal devices (communication devices or information devices) 101A, 101B, 101C, 101D, 101E, a BC (Broadcast) server 105, and a communication network 102. The plurality of terminal devices 101A to 101E correspond to nodes or users of a distributed network. Any one of the plurality of terminal devices 101A to 101E is referred to as a terminal device 101. The communication network 102 is a wireless network, a wired network, or a mixed network of wireless and wired. The

terminal devices

101A, 101B, 101C, and 101D wirelessly connect to the communication network 102 and perform communication. The terminal device 101C is connected to the communication network 102 by wire to perform communication. All terminal devices may be connected to the communication network 102 wirelessly or by wire. The communication network 102 may be any network such as a mobile network (cellular network), a wireless LAN (Local Area Network), and the Internet. Further, the communication network 102 may be a network in which a plurality of types of networks are mixed. The communication network 102 may include various network devices such as a base station, a router, a gateway device, or a firewall. The BC server 105 is a server or communication device that supports broadcasting or multicast by the terminal device 101. Broadcasting is transmission to unspecified or arbitrary one or more information devices, and is also called notification, broadcasting, or broadcasting. Multicast is a transmission that designates one or more specific information devices as destinations. Although the BC server 105 is wirelessly connected to the communication network 102, it may be connected by wire. Details of the BC server 105 will be described later.

FIG. 2 shows an example of the communication network 102. The communication network 102 includes a plurality of base stations (communication devices) 103A and 103B. The base station 103A communicates wirelessly with the

terminal devices

101A and 101B, and communicates with the terminal device 101C by wire. The base station 103B wirelessly communicates with the

terminal devices

101E and 101D and the BC server 105. The function of the BC server 105 may be included in the base station 103B or the base station 103A. The base station 103A and the base station 103B are connected by wire. Further, the core network including the network devices (gateway device, router, etc.) other than the

base stations

103A and 103B is, for example, between the

base stations

103A and 103B, or between the base station 103B and the

terminal devices

101E, 101D and the BC server 105. It may exist in between.

The

base stations

103A and 103B transmit the packet received from the terminal device in the cell of the own station to the terminal device in the cell or relay it to the other base station according to the destination of the packet. The base station that receives the relayed packet transmits the packet to the terminal device in the cell according to the destination of the packet. A packet is an example of a transmission unit of information, and can be read as another term such as a segment, a frame, or a datagram. In the example of FIG. 2, the

base stations

103A and 103B are connected by wire, but may be connected wirelessly.

The distributed network 100 of FIG. 1 or FIG. 2 distributes and manages target data which is the same data among terminal devices 101A to 101E by a block chain which is a technique for realizing a distributed ledger. That is, the same data is stored, recorded, retained, or stored between the terminal devices 101A to 101E by the blockchain. The terminal devices 101 to 101E are equipped with an application (blockchain program) that realizes a blockchain, and information processing is performed by each terminal device so that the blockchain is correctly realized by each terminal device executing the application. Is done. Regardless of the physical configuration of the communication network 102, the terminal devices communicate with each other regarding the blockchain in the application layer.

FIG. 3 is a diagram showing that blockchain communication is performed between application layers of a plurality of terminal devices from the viewpoint of a protocol stack. As an example, application communication between the terminal device 101A and the terminal device 101D is shown, but the same can be performed between other terminal devices. Everything above the transport layer may be the application layer, or the upper part of the transport layer may be divided into a session layer, a presentation layer, and an application layer. The data link layer includes a PDCP (Packet Data Convergence Protocol) layer, an RLC (Radio Link Control) layer, and a MAC (Medium Access Control) layer. The configuration of the data link layer is an example, and other configurations are possible.

Here, the technical background of this embodiment will be described. In blockchain communication, for example, a terminal device receives a broadcast or multicast transaction from another terminal device. The terminal device generates a block containing one or more transactions, and performs a process of obtaining approval based on an agreement algorithm for the generated block. Upon obtaining approval, the terminal device broadcasts or multicasts approval data containing information about the approved block. Further, the terminal device receives approval data from the distributed network and performs a process of updating the blockchain by adding the approved block to the blockchain. By adding the blocks approved in this way, the same blockchain is maintained in each terminal device. When a terminal device broadcasts a message such as a transaction or approval data, it is assumed that a connection (for example, a TCP (Transmission Control Protocol) connection) is formed for each other terminal device to be a communication partner via a communication network 102. In this case, broadcasting cannot be performed efficiently, and the update of the blockchain may be delayed. The connection represents a virtual connection state (logical line for data transfer) with the communication partner. Hereinafter, when it is described as broadcasting, broadcast may be read as multicast.

FIG. 4 is a diagram showing an example of broadcasting approval data (message) including information about a block approved from the terminal device 101A from the viewpoint of the application layer. More specifically, FIG. 4 shows an example of broadcasting approval data including information about an approved block from the application of the terminal device 101A to the application of the terminal devices 101B to 101E. The application of the terminal device 101A simultaneously transmits the same message having the broadcast address defined by the application to the applications of the terminal devices 101B to 101D. A connection is formed with the terminal device 101A for each of the terminal devices 101B to 101D, and approval data is transmitted from the terminal device 101A via the connection.

FIG. 5 shows an example in which the terminal device 101A

forms connections

111B, 111C, 111D, 111E with the terminal devices 101B to 101E via the base station 103. The base station 103 receives the approval data transmitted by the connections 111B to 111E via the uplink channel formed between the base station 103 and the terminal device 101A, and transmits the received approval data to the terminal devices 101B to 101E. The base station 103 is, for example, a base station such as 4G or 5G. If the base station 103 does not have a mechanism for broadcasting the uplink, the terminal device 101A cannot broadcast at the data link layer even if the terminal devices 101B to 101E are in the same wireless network.

FIG. 6 shows an example in which the terminal device 101A broadcasts approval data to other terminal devices via the core network 106. Similar to the example of FIG. 5, the terminal device 101A broadcasts the approval data to the terminal devices 101B to 101E belonging to the same wireless network, and also broadcasts the approval data to the

terminal devices

101F, 101G, and 101H via the core network 106. .. The

terminal devices

101F, 101G, and 101H belong to the wireless network formed by the base station 107, and belong to a wireless network different from the terminal devices 101A to 101E. The terminal device 101A individually forms a connection with the terminal devices 101F to 101H in addition to the terminal devices 101B to 101E.

As can be understood from the examples shown in FIGS. 5 and 6, as the number of terminal devices to be broadcast increases, the terminal device 101A needs to form more connections. Therefore, it takes a lot of time to complete the broadcast, which is not efficient. In addition, the load on the terminal device 101A becomes high.

This embodiment provides a mechanism for efficiently transmitting approval data related to the blockchain and target data for broadcasting such as transactions. However, the subject of this disclosure is not limited to the blockchain, and the present disclosure can be applied to any communication system that broadcasts messages.

Below, prior to explaining the details of this embodiment, the outline of the procedure for approval of transactions and blocks related to the blockchain will be described. The blockchain according to the present embodiment includes a distributed ledger (Distributed Ledger), a distributed database (Distributed Database), a de-centralized Ledger, and a de-centralized Ledger. It includes various data or algorithms called Bitcoin Core, Ethereum, and Hyperledger Fabric.

FIG. 7 is a diagram showing an outline of the blockchain. A blockchain is data in which a plurality of blocks are connected like a chain. Each block contains one or more transactions 1-n (n is an integer greater than or equal to 1). In addition, each block includes, as an example, the hash value of the immediately preceding block and a value called a nonce. Other information, such as hash values of all transactions contained in the block, may be included.

The hash value of the immediately preceding block is information used to determine whether or not the block connected from the immediately preceding block is a legitimate block correctly connected from the immediately preceding block. When a transaction contained in a block is deleted or tampered with, the hash value of the block changes and the consistency with the hash contained in the block immediately after it is lost, so it is possible to detect the transaction deletion and tampering. It becomes. As a hash function that generates a hash value, there is SHA-256 (in this case, the hash value is a fixed 256 bits). However, the type of hash function is not particularly limited.

Nance is information used to prevent spoofing in authentication using a hash value. Tampering is prevented by using a nonce. As the nonce, for example, a character string, a number string, data indicating a combination thereof, or the like can be used.

In this example, it is assumed that POW (Proof of Work) is used as the algorithm for consensus building in the blockchain system, but the type of algorithm is not particularly limited.

In addition, each transaction is given an electronic signature using an encryption key. This prevents spoofing. Each transaction is public and shared across the blockchain network. Note that each transaction may be encrypted using an encryption key.

FIG. 8 schematically shows an example in which user A registers target data to be a transaction (for example, a request for remittance of 10 bit coins (BTC) from user A to user D) in the blockchain system of FIG. 1. User A is an operator of the terminal device 101A or the terminal device 101A. The user A adds an electronic signature generated by using the private key of the user A to the target data to be registered in the blockchain. By adding the electronic signature, it is guaranteed that the owner of the target data is User A. The terminal device 101A broadcasts or multicasts a transaction including the target data with a digital signature to the blockchain network. Broadcast or multicast transactions are received by terminal device 101B to terminal device 101E. The public key of the user D to be transmitted may be included in the transaction.

The terminal devices 101B to 101E store the transaction received from the terminal device 101A in the internal storage unit. The terminal devices 101B to 101E specify one or more transactions to be included in the new block from the transactions stored in the storage unit, and perform processing related to the generation of the new block. At this time, the validity of the transaction generation source is authenticated based on the electronic signature attached to the transaction.

The terminal devices 101B to 101E perform a procedure for obtaining the approval of the newly generated block as a process for consensus building in the blockchain system. Terminal devices 101B to 101E add the specified transaction, the hash value of the immediately preceding block, and the nonce to the newly generated block. For example, the hash value of the immediately preceding block, the hash values of all the specified transactions, and the parameters are added, and the added value is input to a predetermined hash function. A parameter whose hash value, which is an output value of the hash value, satisfies a predetermined condition is searched for, and the found parameter is adopted as a nonce. As a predetermined condition, the hash value may be less than or equal to the threshold value. If a nonce that satisfies a predetermined condition can be found, an approval request including information about the block (information specifying the contents of the block or the block itself) is broadcast or multicast to the blockchain system 100. That is, the terminal device that first discovers the nonce satisfying the predetermined condition broadcasts or multicasts the approval request.

FIG. 9 shows an example in which the terminal device 101E first discovers a nonce satisfying a predetermined condition and broadcasts or multicasts an approval request. The terminal device 101E officially adds a new block to the blockchain when it is approved by a certain number of other terminal devices. The content of the approval process performed by the other terminal device includes, for example, a process of confirming that the nonce is appropriate. When the approval of another terminal device is obtained, the terminal device 101E generates approval data including information about the block for which the approval has been obtained. The terminal device 101E broadcasts or multicasts the approval data. When the other terminal devices 101A to 101D receive the approval data including the information about the block for which the approval has been obtained from the terminal device 101E, the block for which the approval has been obtained is newly added to the blockchain. Alternatively, the other terminal devices 101A to 101D may add the approved block to the blockchain when the approval process is performed by the own device and it is confirmed that the nonce is appropriate.

This embodiment introduces the BC server 105 that assists broadcasting, as shown in FIG. 1, as a mechanism for efficiently transmitting a message (BC message) including target data for broadcasting such as transaction or approval data. As a result, even when the terminal device transmits a BC message via the uplink, efficient broadcasting is realized. The BC server 105 may be provided as a single device, or the function of the BC server may be provided in the base station or the terminal device.

FIG. 10 is a block diagram of a terminal device 101 including a communication device according to an embodiment of the present disclosure. The terminal device 101 includes an antenna 10, a communication unit 11, a processing unit 14, and a storage unit 15. FIG. 10 shows a configuration when the terminal device 101 performs wireless communication, but when wired communication is performed, the antenna 10 may not be provided. Alternatively, the communication unit 11 may be connected to the wired network together with the antenna 10.

The processing unit 14 performs various processes related to the blockchain by executing a program (application) related to the blockchain. The processing unit 14 generates a transaction which is an example of the target data according to the present embodiment. For example, the processing unit 14 generates a transaction by using the detection of a predetermined event such as a user's operation input as a trigger. The transaction may be data input by the user, data detected by the sensing device, or other data. The processing unit 14 stores the generated transaction in the storage unit 15. Further, the processing unit 14 sends a BC request message requesting the BC server 105 to send the generated transaction as target data to at least one information device to be broadcast or multicast (hereinafter, unified to broadcast). Generate. When the target of transmission is an unspecified or arbitrary one or more information devices, a message requesting that the target data be transmitted to at least one arbitrary information device to be broadcast is generated as a BC request message. do. When the target of transmission is one or more specific information devices, a message requesting that the target data be transmitted to at least one specific information device to be multicast is generated as a BC request message. .. The latter BC request message may be particularly referred to as a multicast (MC) request message. In the following, messages requesting either broadcast or multicast will be referred to as BC request messages in the same way. The BC request message corresponds to the first request message requesting broadcast or multicast. The detailed format of the BC request message will be described later (see FIG. 33). The processing unit 14 may encode the BC request message. The processing unit 14 transmits a BC request message to the distributed network 100 via the communication unit 11 including the transmitting unit and the receiving unit. BC request messages are sent in the form of packets, depending on the protocol used. The final destination (eg, IP address) of the BC request message is the BC server 105. A message including target data transmitted by the BC server 105 in response to the BC request message is called a BC message. In particular, when the BC request message is an MC request message, the message including the target data transmitted by the BC server 105 may be referred to as an MC message. In the following, both broadcast and multicast messages will be referred to as BC messages.

The processing unit 14 receives the BC message transmitted (broadcast or multicast) from the BC server 105 via the communication unit 11. When the BC message includes a transaction, the processing unit 14 stores the transaction in the storage unit 15. If the BC message is encoded, the processing unit 14 decodes the BC message.

The storage unit 15 stores various information or data. The storage unit 15 stores a blockchain program or the like that realizes each function of the terminal device 101 (information device). By executing the blockchain program stored in the storage unit 15 by the processing unit 14, various processes for realizing the blockchain are realized. The storage unit 15 stores the transaction generated by the processing unit 14. Further, the storage unit 15 stores the transaction received from the BC server 105. Further, the storage unit 15 stores a blockchain, which is a set of data (blocks) shared by terminal devices (information devices) participating in the blockchain system. The terminal device acquires blockchain information via the distributed network 100, and updates the blockchain while maintaining consistency with the blockchain held by other terminal devices.

The processing unit 14 performs processing related to the generation of a new block to be added to the blockchain. The processing unit 14 starts a new block generation process at a predetermined timing. As an example, the predetermined timing may be immediately after the processing unit 14 generates the block generated immediately before, or after a predetermined time has elapsed since the block was generated immediately before. Alternatively, the predetermined timing may be a timing determined by a user's operation input as a trigger, or may be another timing.

The processing unit 14 specifies a transaction to be included in the new block from the transactions stored in the storage unit 15 as a process related to the generation of a new block. For example, the processing unit 14 may specify a transaction of one or more predetermined items as a transaction to be included in a new block. Alternatively, the transaction until the predetermined data size is reached may be specified as the transaction to be included in the new block. You may specify the transaction to be included in the new block by other methods.

The processing unit 14 performs a procedure for obtaining the approval of the newly generated block as a process for consensus building in the blockchain system. Examples of approval algorithms include POW (Proof of Work), POS (Proof of Stake), POI (Proof of Importance), POC (Proof of Consensus), POB (Proof of Burn), and PBFT (Practical Byzantine Fault Tolerance). be. In the case of POW, the processing unit 14 adds, for example, the specified transaction, the hash value of the immediately preceding block, and the nonce to the newly generated block. At this time, the processing unit 14 searches for a nonce whose hash value input and output to the predetermined hash function satisfies a predetermined condition, and adds a nonce satisfying the predetermined condition. The processing unit 14 adds a new block to the blockchain. The processing unit 14 generates a BC request message requesting the BC server 105 to broadcast an approval request including information about the block (information specifying the contents of the block or the block itself) as target data. The processing unit 14 transmits the BC request message to the distributed network 100. Then, for example, with the approval of a certain number or more of other terminal devices, a new block is officially added to the blockchain. The content of the approval process performed by the other terminal device includes, for example, a process of confirming that the nonce is appropriate.

When approval is obtained, the processing unit 14 generates approval data including information on the block for which approval has been obtained. The processing unit 14 generates a BC request message requesting the BC server 105 to broadcast the approval data as the target data. The processing unit 14 transmits the BC request message to the distributed network 100.

When the processing unit 14 receives approval data including information about the block for which approval has been obtained from another terminal device, the processing unit 14 newly adds the block for which approval has been obtained to the blockchain.

Further, for example, when the approval algorithm is POW, the processing unit 14 performs approval processing when an approval request is received from another terminal device. The processing unit 14 transmits an approval response including the result of the approval process to the terminal device from which the approval request is transmitted. When the processing unit 14 approves the block, the block may be added to the blockchain at the time of approval. In this case, it is not necessary to receive the approval data from other terminal devices.

The communication unit 11 transmits or receives a BC request message, various data, and a BC message via the antenna 10. The communication unit 11 establishes a wireless link with the base station 103, and communicates with respect to the data link layer and the physical layer via the channel of the wireless link (for example, a physical channel, a transmission channel, a logical channel, etc.). The wireless link includes at least one of an uplink and a downlink. The communication unit 11 may transmit the above-mentioned BC request message on the uplink channel (first channel). The BC request message may include identification information of at least one information device to be broadcast. The BC request message may include the type of application or service that generated the target data (transaction, approval data, approval request, etc.). The communication unit 11 or the processing unit 14 may determine a server such as a BC server that is a destination of the BC request message according to the type of application or service that uses the BC request message.

The communication unit 11 may receive a delivery confirmation response to the BC request message from the BC server 105. When the communication unit 11 detects that the transmission of the BC request message has failed based on the delivery confirmation response, the BC request message may be retransmitted. The communication unit 11 may receive a BC message (including, for example, a transaction, an approval request, an approval data, etc.) transmitted from the BC server 105.

The communication unit 11 may transmit user data different from the BC request message on the uplink channel (second channel). At this time, the parameters related to at least one of the retransmission control, the modulation method, and the transmission power control may be independently set for the first channel and the second channel.

Processing of each layer of the protocol stack is performed at least one of the processing unit 14 and the communication unit 11. As an example, the application layer, the presentation layer, and the session layer may be performed by the processing unit 14, and the processing of the layers below the transport layer may be performed by the communication unit 11. Alternatively, all layers may be processed by the processing unit 14, and the communication unit 11 may perform only processing related to conversion between the packet of the physical layer and the radio signal (modulation / demodulation, band limitation, AD / DA conversion, amplification, etc.). good. The block for processing each layer may be determined by another method.

FIG. 11 is a block diagram of the BC server 105 including the communication device according to the embodiment of the present disclosure. The BC server 105 includes an antenna 20, a communication unit 21, a processing unit 24, and a storage unit 25. The processing unit 24 includes a timer 22 and a counter 23. At least one of the timer 22 and the counter 23 may be provided. A configuration without the timer 22 and the counter 23 is also possible. FIG. 11 shows a configuration when the BC server 105 performs wireless communication, but the antenna 20 may be omitted when performing wired communication. Alternatively, the communication unit 21 may be connected to the wired network together with the antenna 20. Further, the communication unit 21 may be provided with a plurality of communication interfaces depending on the number of communication networks to be connected.

The communication unit 21 (first receiving unit) is a BC request message (first request message) requesting that the target data be transmitted to at least one information device that is the target of broadcasting or multicast (hereinafter, unified to broadcast). To receive. In the case of a blockchain application, the target data includes transactions, approval requests, approval data, and the like.

The processing unit 24 generates a BC message for at least one information device requested by the BC request message based on the information included in the BC request message, and the generated BC message is transmitted to the communication unit 21 (first transmission unit). Send via. For example, the destination information device is selected based on the BC request message, and the BC message including the target data is transmitted to the information device. The information included in the BC request message includes the identification information of at least one information device, and the processing unit 24 may specify the information device to which the BC message is transmitted based on the identification information.
The processing unit 24 uses information related to the target data based on the information associated with the type of the application or service that uses the BC message and the information device that uses the application or service of the type. The device may be specified. The communication unit 21 may transmit a BC message to the specified information device. The BC request message includes the type of the application or service of the target data, and the processing unit 24 may specify the application or service of the target data based on the type included in the BC request message.

The storage unit 25 stores the received BC request message. The counter 23 counts the number of BC request messages stored in the storage unit 25. When the number reaches the first number, the processing unit 24 resets the counter 23 to the initial value. Every time the value of the counter reaches the first value, the processing unit 24 identifies the BC request message accumulated between the previous reset and reaching the first value. The processing unit 24 generates a BC message including the target data for each specified BC request message, and transmits the generated BC message via the communication unit 21.

The processing unit 24 activates the timer 22 set to a predetermined value, and identifies the first request message stored in the storage unit 25 after the timer 22 is activated and before the timer 22 times out. The processing unit 24 generates a BC message including the target data for each of the specified first request messages. The processing unit 24 transmits the generated BC message via the communication unit 21.

When the BC server 105 is included in the base station, the communication unit 21 (first receiving unit) may receive the BC request message from the terminal device 101 on the first channel of the uplink. The communication unit 21 (second transmission unit) may transmit a delivery confirmation response to the terminal device 101 depending on whether or not the BC request message has been successfully received.

The communication unit 21 (second receiving unit) may receive a target data acquisition request (BC message acquisition request) from the terminal device (first information device) to which the BC message is transmitted. When the acquisition request is received, the processing unit 24 determines whether the storage unit 25 has a BC request message requesting transmission to the terminal device. When the BC request message exists, the communication unit 21 transmits the BC message requested by the BC request message to the terminal device.

Communication unit 21 (first receiving unit) may receive user data different from the BC request message on the second channel of the uplink. The parameters related to at least one of the retransmission control, the modulation method, and the transmission power control may be independently set for the first channel and the second channel described above.

FIG. 12 shows a specific example of the communication system of FIG. 1 as the communication system according to the present embodiment. The terminal device 101X is connected to the base station 103 via a wireless link. The terminal device 101X is connected to the gateway device 104 of the core network via the base station 103. The gateway device 104 is connected to the BC server 105 in the core network. The BC server 105 is connected to the

terminal devices

101Y, 101Z, etc. via the base station 107. The base station 107 is connected to the

terminal devices

101Y, 101Z, etc. via a wireless link.

FIG. 13 shows another specific example of the communication system of FIG. The BC server 105 is provided in the base station 107. Other configurations are the same as in FIG.

FIG. 14 shows still another specific example of the communication system of FIG. The terminal device 101R is connected to the base station 107 via a wireless link. The BC server 105 is provided in the terminal device 101R. Other configurations are the same as in FIG.

FIG. 15 shows an example of a sequence in which the terminal device 101X acquires BC server information from a server (initial setting server) that manages a blockchain system (information processing system or communication system). The terminal device 101X participates in the blockchain system by setting the blockchain application (S101). Specifically, the terminal device 101X sends a participation request message to the terminal device having the participation approval authority, and when the participation approval is decided, the participation approval message is sent from the terminal device having the participation approval authority. , And also receive a message containing blockchain information. Upon receiving the participation approval message, the terminal device 101X determines that participation in the blockchain system has been approved, and stores the blockchain information in the storage unit. The terminal device 101 may acquire the information of the terminal device having the above-mentioned authority to approve the participation from the server of the blockchain system (or the following initial setting server). Alternatively, the information of the terminal device having the authority to approve the participation may be registered in the blockchain application in advance.

The terminal device 101X selects one or more of one or more preset initialization servers (S102) and connects to the selected initialization server (S103). The initialization server is included in the same wireless network as, for example, the core network 106 or the terminal device 101X. The criteria for selecting the initialization server will be described.
[Initial setting server selection criteria: Example 1]

The address of the initial setting server candidate is retained (pre-installed) on the terminal device 101X side in advance. The address includes, for example, URL / URI / IP address / MAC address / host name / server name. The terminal device 101X accesses one or more addresses in order, and confirms the connection with the server having the addresses. Alternatively, a specific server may provide one or more candidate addresses to the terminal device 101X, and the terminal device 101X may in turn confirm the connection. The terminal device 101X may select one or more initialization servers that can be connected first.

[Initial setting server selection criteria: Example 2]
As another selection criterion, the terminal device 101X side holds (pre-installs) one or more position information of the initial setting server candidate in advance. The terminal device 101X acquires the position information of its own device from an external server such as a sensor or the Internet, and attempts to connect to the initial setting server based on the acquired position information. For example, access is performed in order from the initial setting server located near or far from the terminal device to check the connection. Examples of location information include coordinates (latitude / longitude / altitude, etc.), addresses (country / state / prefecture / city, etc.), etc. Alternatively, a specific server may provide the terminal device 101X with one or more position information of the initial setting server candidates, and the terminal device 101X may confirm the connection in order. The terminal device 101X may select one or more initialization servers that can be connected first.

The initial setting server connected to the terminal device 101X designates a BC server for the terminal device 101X, and transmits the information of the designated BC server to the terminal device 101X (S104). For example, the initial setting server holds information on one or more BC servers in advance, and all the held BC servers may be specified. Alternatively, the initial setting server may specify a BC server according to the address or location information of the terminal device 101X. For example, a table associated with addresses or location information may be prepared for each BC server, and an initial setting server may be specified based on the table. The terminal device 101X acquires the information of the BC server specified by the initial setting server from the initial setting server and sets it in the application (S105). The BC server information includes, for example, the following information.

(Example of BC server information)
-Address (URL / URI / IP address / MAC address / host name / server name, etc.)
・ Location information (coordinates (latitude / longitude / altitude, etc.), address (country / state / prefecture / city, etc.), etc.)
・ OS / version (Windows / Mac / Unix / Linux, etc.)
-Hardware configuration (CPU type / clock frequency / number of cores / number of threads, memory type / capacity, network interface type / speed, etc.)
-Process load (CPU utilization ZZ%, memory usage AA Bytes, etc.)
・ At the start of operation (YYYY / MM / DD, etc.)
・ Operation time (continuous operation XX hours / minute / second, etc.)
・ Scheduled suspension (period), scheduled maintenance (period) (YYYY / MM / DD to YYYY / MM / DD, etc.)
・ Server owner (company) ・ Administrator (company) information (name, company name, ID, contact information (email address, phone number, fax number, address), etc.)

The terminal device 101X stores the BC server information acquired from the initial setting server in the storage unit. By acquiring the information of the BC server, the terminal device 101X grasps that the BC server can be used to broadcast the BC message. The BC server may be a single device, or any of the base station, the terminal device, and the initialization server may include the function of the BC server.

FIG. 16 is a sequence diagram showing an example of a procedure for broadcasting a BC message using a BC server. Here, it is assumed that the function of the BC server is included in the base station. The broadcast of the BC message includes not only the case where the BC message is simultaneously transmitted to each target terminal device but also the case where the BC message is transmitted to each terminal device at different timings. The terminal device 101X has already acquired the BC server information by the procedure of FIG.

The terminal device 101X requests the BC server to transmit the target data (BC message) for broadcasting to at least one target terminal device (information device) (BC request message or first request message). Is generated (S111). The terminal device 101X transmits the generated BC request message to the base station 103 on the uplink channel (first channel) (S112). The details of the uplink channel will be described later. The BC request message includes, for example, target data (approval data, transaction, etc.), and includes a request to transmit the target data to a terminal device to be broadcast. The destination address (for example, IP address) of the BC request message is the BC server. The terminal device 101X may form a connection with the BC server by TCP or the like.

The base station 103 transmits a BC request message to the gateway device 104 of the core network (S113). The gateway device 104 transmits a BC request message to the BC server 105 via the core network (S114).

The BC server 105 generates a BC message for broadcasting based on the BC request message received from the gateway device 104 (S115). As an example, the target data included in the received BC request message is specified, and the BC message including the target data is generated. The destination address (data link layer or network layer address) of the BC message may be either a unicast address or a broadcast address.

The BC server 105 transmits (broadcast or multicast) a BC message to the target terminal device requested by the BC request message. In this example, the target terminal device is a

terminal device

101Y, 101Z or the like constituting a blockchain system (distributed system). The BC server 105 may simultaneously transmit BC messages to the

terminal devices

101Y, 101Z and the like, or may transmit them at different timings. The BC message is received by the

terminal devices

101Y, 101Z and the like. The BC server 105 may establish a connection such as TCP with the

terminal devices

101Y, 101Z, etc. and transmit the BC message, or may transmit the BC message without establishing the connection. Even when establishing a connection, it is assumed that the performance of the BC server 105 is usually higher than that of the terminal device 101X, so that the effect of the decrease in efficiency due to the establishment of the connection is small. Further, when the number of terminal devices in charge of the BC server 105 is smaller than that in the case where one terminal device 101X establishes a connection with all other terminal devices, efficiency can be improved. The BC message received by the

terminal devices

101Y, 101Z, etc. is passed to the blockchain application.

As a method of broadcasting a BC message from the BC server 105, there are an on-demand type broadcast, a push type broadcast cast, or a pull type broadcast.

[On-demand broadcast]
The on-demand broadcast is a method of broadcasting a message including the target data as soon as the BC request message arrives at the BC server 105.

FIG. 17 is a diagram showing a sequence example of the operation of the on-demand type broadcast. When the BC server 105 receives the BC request message (S121), it selects one or more destinations (terminal devices) for transmitting the BC message including the target data (approval data, transaction, etc.). The BC server 105 broadcasts a BC message to the selected destination (S122). Details of the destination selection method will be described later.

FIG. 18 is a flowchart of an example of a process of performing an on-demand broadcast on the BC server 105. The flowchart of FIG. 18 corresponds to the sequence of FIG.
The BC server 105 waits for the BC request message until it receives the BC request message (NO in S131 and S132). When the BC server 105 receives the BC request message (YES in S132), it selects one or more destinations (terminal devices) of the BC message to be broadcast (S133). The BC server 105 sends a BC message to one or more selected destinations (S134). After transmission, it is determined whether the end condition of the process is satisfied (S135), and if the end condition is not satisfied (NO), the process returns to step S131. If the processing end condition is satisfied (YES), the processing is terminated. Examples of the termination condition include the case where an instruction to stop the BC server 105 is input from the operation terminal of the administrator of the BC server 105, or the case where an abnormality in processing is detected.

[Push type broadcast]
The push-type broadcast is a method of broadcasting a BC message including target data at a timing determined by the BC server 105 according to a predetermined policy after the BC request message is received by the BC server 105. If a policy is used to broadcast the message as soon as the BC request message is received, the push-type broadcast behaves the same as or similar to the on-demand type.

FIG. 19 is a diagram showing an example of a sequence of push-type broadcast operations. When the BC server 105 receives the BC request message (S141), it determines whether to transmit the BC message including the target data (approval data, transaction, etc.) (push transmission determination) (S142). When the BC server 105 decides to transmit by the push transmission determination, it selects one or more transmission destinations (terminal devices). Details of the destination selection method will be described later. The BC server 105 transmits a notification for notifying the transmission of the BC message to the selected destination and the BC message (S143). The notification and the BC message may be transmitted at the same time as integrated data, or the notification may be transmitted first as shown in FIG. 20 described below.

FIG. 20 is a diagram showing another example of the sequence of push-type broadcast operations. Steps S151 and S152 are the same as steps S141 and S142 in FIG. When the BC server 105 decides to send a BC message by the push transmission determination, it selects one or more destinations (terminal devices) of the message and announces that the message will be transmitted to the selected destination. A notification is transmitted (S153). Upon receiving the notification from the BC server 105, the transmission destination of the notification (for example, the

terminal device

101Y, 101Z, etc.) transmits the BC message acquisition request to the BC server 105 (S154). The BC server 105 that has received the BC message acquisition request transmits the BC message related to the request to the sender of the BC message acquisition request (S155).

FIG. 21 is a flowchart of an example of a process of performing a push-type broadcast on the BC server 105. The flowchart of FIG. 21 corresponds to the sequence of FIG. 19 or FIG. The BC server 105 initializes the timer to a predetermined value and starts it (S161). The BC server 105 stores the received BC request message in the internal storage unit every time the BC request message is received until the timer times out (NO in S162 and S163). When the timer times out, the BC server 105 determines whether or not one or more BC request messages are stored in the storage unit (S164), and if no one is stored, the process returns to step S161. When one or more BC request messages are accumulated (YES in S164), the accumulated BC request messages are processed from the start of the timer to the timeout. Specifically, for each BC request message, one or more destinations (terminal devices) of the BC message to be broadcast are selected (S165). The BC server 105 transmits a BC message to one or more selected destinations (S166). After transmission, it is determined whether the end condition of the process is satisfied (S167), and if the end condition is not satisfied (NO), the process returns to step S161. If the end condition is satisfied (YES), the process is terminated.

FIG. 22 is a flowchart of another example of the process of performing the push-type broadcast on the BC server 105. The flowchart of FIG. 22 corresponds to the sequence of FIG. 19 or FIG. The BC server 105 initializes the counter and sets the value of the counter as the initial value (S171). Each time the BC server 105 receives a BC request message, the BC request message is stored in the internal storage unit (S172), and the counter is incremented by a constant value (for example, 1) (S173). The BC server 105 determines whether the counter has reached a predetermined value (S174), and if not, returns to step S172. When the counter reaches a predetermined value (YES), the BC request message accumulated between the start of counting and the time when the counter reaches the predetermined value is processed. That is, for each BC request message, one or more BC message transmission destinations (terminal devices) are selected (S175). The BC server 105 transmits a BC message to one or more selected destinations (S176). After transmission, it is determined whether the end condition of the process is satisfied (S177), and if the end condition is not satisfied (NO), the process returns to step S171. If the end condition is satisfied (YES), the process is terminated.

The method of selecting the destination of the BC message performed in step S122 of FIG. 17, step S133 of FIG. 18, step S143 of FIG. 19, step S153 of FIG. 20, step S165 of FIG. 21, and step S175 of FIG. 22 will be described in detail. ..

[1] The BC server 105 may select the destination of the BC message based on the type of application or service that uses the BC message. For example, at the time of initial setting of the terminal device, the BC server or another server (for example, the initial setting server) may read as a node or a user, and the same shall apply hereinafter. Acquire and store the information of. Upon receiving the BC request message, the BC server 105 identifies the type of application or service of the requested BC message, and selects the terminal device using the specified type of application or service as the transmission destination.

[2] The BC server includes information (selection information) for selecting to which terminal device the BC message is to be transmitted in the BC request message (which may be a control field or a data field described later) transmitted by the terminal device. 105 selects a destination based on the selection information. The selection information may be information that specifies the type of application or service. Instead of the BC server 105, another server (for example, an initial setting server) may select a destination. In this case, the BC server 105 sends the selection information included in the BC message to another server, and acquires the information of the destination selected by the other server.

[3] The transmission source terminal device sends an application for an application or service that uses a BC message to a BC server, an initial setting server, or the like. Alternatively, the information of the application or service that uses the BC message is registered in advance in the BC server or the initial setting server for each type of application or service. Registration may be performed by an administrator or the like using an operation terminal. The BC server selects a terminal device that uses the same type of application or service as the received BC request message as the transmission destination.

[4] When transmitting a BC request message, the terminal device selects a destination terminal device based on the type of application or service that uses the BC message. The selection of the terminal device is performed by, for example, the address or ID of the terminal device. The BC server or the initialization server may provide a terminal device list (address, ID, name, etc.) that uses BC messages to the terminal device for each type of application or service. The BC server or the initialization server may send a list to the terminal device only for the type of application or service used by the terminal device. Alternatively, the BC server or initialization server may send a list of types of applications or services that the terminal device does not plan to use. The terminal device may specify another terminal device that uses the same type of application or service as the own device by using the list, and select the specified other terminal device as the terminal device to which the BC message is sent. .. The BC server or the initialization server may send the updated list (or the difference before and after the update of the list) to the terminal device when the list is updated (for example, addition or deletion of the terminal device).

[Pull type broadcast]
The pull-type broadcast is a method of transmitting a BC message to the terminal device when the BC server 105 receives a BC message acquisition request transmitted as a trigger from the terminal device of the transmission destination.

FIG. 23 is a diagram showing an example of a sequence of pull-type broadcast operations. The terminal device (

terminal devices

101Y, 101Z, etc. in the example of the figure) determines whether to transmit a BC message acquisition request (hereinafter, acquisition request) (BC message pull determination) (S181). When it is determined by the pull determination to transmit the acquisition request, the acquisition request is transmitted to the BC server 105 (S182). The BC server 105 to which the acquisition request is transmitted is the BC server designated by the initialization server in the sequence example of FIG. Upon receiving the acquisition request, the BC server 105 determines whether or not a BC message for transmission exists in the terminal device. For example, it is determined whether or not the terminal device corresponds to the destination requested by the BC request message. If present, the BC server 105 sends a BC message (S183). If it does not exist, a notification that the BC message does not exist is transmitted (S183). The transmission of the notification to the effect that it does not exist may be omitted.

FIG. 24 is a flowchart of an example of a process of performing a pull-type broadcast on the BC server 105. The flowchart of FIG. 24 corresponds to the sequence of FIG. The terminal device (

terminal device

101Y, 101Z, etc.) initializes the timer to a predetermined value and starts (S191). The terminal device waits until the timer times out (NO in S192 and S193). When the timer times out, the terminal device sets the destination of the BC message acquisition request based on the BC information (S194), and transmits the BC message acquisition request (S195). The terminal device receives the BC message transmitted from the BC server 105 (S196) and passes it to the application. It is determined whether the end condition of the process is satisfied (S197), and if the end condition is not satisfied (NO), the process returns to step S191. If the end condition is satisfied (YES), the process is terminated. As an example of the termination condition, there is a case where an application termination instruction is input by the user of the terminal device.

FIG. 25 is a flowchart of another example of the process of performing a pull-type broadcast. The flowchart of FIG. 25 corresponds to the sequence of FIG. The terminal device (

terminal device

101Y, 101Z, etc.) waits until a BC message transmission request is generated from the application of the own device (NO in S201, S202). When a request to send a BC message occurs (YES in S202), a BC message is generated (S203). Further, the terminal device generates a request for acquiring a BC message for reception of the own device (S204). The terminal device transmits a BC message for broadcasting to another terminal device and a request for acquiring a BC message for receiving the own device to the BC server (S205). The BC server to which the BC message for broadcasting is sent and the BC server to which the acquisition request for the BC message for receiving is sent may be the same or different. When the BC message for reception of the own device exists in the BC server, the terminal device receives the BC message from the BC server (S206) and passes it to the application. It is determined whether the end condition of the process is satisfied (S208), and if the end condition is not satisfied (NO), the process returns to step S201. If the end condition is satisfied (YES), the process is terminated. As an example of the termination condition, there is a case where an application termination instruction is input by the user of the terminal device.

Hereinafter, assuming a cellular wireless network such as 4G or 5G, the mapping between the BC request message generated by the application (blockchain application, etc.) in the terminal device and the uplink channel used for communication between the base station and the like. explain.

FIG. 26 shows an example of mapping a BC request message to DTCH (or BCH), UL-SCH, and PUSCH in a terminal device on the transmitting side. A physical channel, a transport channel, and a logical channel are shown. The layer between the physical channel and the transmission channel corresponds to the physical layer, and the layer between the transmission channel and the logical channel corresponds to the data link layer. The layer above the logical channel is not shown. There is no distinction between uplink and downlink for logical channels, and transmission channels and physical channels are for uplink and downlink, respectively.

PUCCH (Physical Uplink Control Channel) is a control channel that transmits uplink control data. PRACH (Physical Random Access Channel) is used when the terminal device establishes a connection with a base station by initial access or handover. PUSCH (Physical Uplink Shared Channel) is a shared channel for transmitting uplink user data.

RACH (RandomAccessChannel) is a channel transmitted at random timing via PRACH. UL-SCH (Uplink Shared Channel) is a channel including uplink user data (actual user data), and is transmitted via PUSCH.

CCCH (Common Control Channel) is a logical channel used to transmit control information between a terminal device and a base station, and is used when the terminal device has not been connected to the base station by wireless resource control. Be done. The DCCH (Dedicated Control Channel) is a one-to-one bidirectional channel between a terminal device and a base station, and is a logical channel used for transmitting individual control information. A DTCH (Dedicated Traffic Channel) is a one-to-one bidirectional channel between a terminal device and a base station, and is dedicated to one terminal device used for transmitting user data (for example, a unicast (UC) message). It is a logical channel. BCH (Broadcast Channel) is a logical channel for transmitting a broadcast signal, and the broadcast signal includes information to be notified to all terminal devices belonging to a base station.

SRB (Signaling Radio Bearer) 0 is a radio bearer (logical path for transmitting data) for CCCH. The SRB0 is used for transmitting an RRC connection setting request (RRCConnectionEstablishmentRequest) and an RRC reconnection request (RRCConnectionRe-establishmentRequest) on the uplink. RRC is an abbreviation for Radio Resource Control. SRB0 is used for transmission of RRCConnectionEstablishment, RRCConnectionReject, RRCConnectionRe-establishment and RRCConnectionRe-establishmentReject on the downlink. SRB1 is a radio bearer for DCCH and is used for transmitting all RRC messages that are not transmitted by SRB0.

The terminal device maps the BC request message to the DTCH and transmits it to the base station via the UL-SCH and PUSCH. Alternatively, the terminal device maps the BC request message to the BCH and transmits it to the base station via the UL-SCH and PUSCH. By mapping to DTCH or BCH and sending a BC request message, a retransmission algorithm such as ARQ (Automatic Repeat Request) or HARQ (Hybrid Automatic Repeat Request) should be used in the same way as when sending user data by unicast. Can be done. This makes it possible to improve the reliability of the BC request message when the BC request message is transmitted to the base station on the uplink. As a comparative example, the BCH is used only for transmitting the broadcast signal on the downlink, but in the present embodiment, the BCH is used for transmitting the BC request message on the uplink.

FIG. 27 shows a BC request message mapped to BCH in a terminal device via UL-BCH, which is a transmission channel newly introduced in this embodiment, and PUBCH, which is a physical channel newly introduced in this embodiment. , An example of transmitting to a base station is shown. UL-BCH is an abbreviation for Uplink Broadcast Channel, and PUBCH is an abbreviation for Physical Uplink Broadcast Channel. The unicast (UC) message is mapped to the DTCH as in FIG. 26 and transmitted via the UL-SCH and PUCCH. In this way, the unicast message and the BC request message are transmitted via different sets of logical channels, transmission channels and physical channels. At this time, the ARQ or HARQ is set on the transmission channel (layer 2, MAC, RLC, PDCP, etc.), and the MCS and TPC are set on the physical channel (layer 1, PHY layer, etc.). This makes it possible to set parameters such as ARQ or HARQ, MCS (Modulation and Coding Scheme) and TPC (Transmission Power Control) individually for the unicast message and the BC request message. When the MCS and TPC settings are common to both messages, a BC request message may be transmitted using UL-BCH as a logical channel and PUCCH as a physical channel as shown in the figure.

FIG. 28 shows an example in which a BC request message is received at a base station with a mapping opposite to the channel mapping shown in FIG. 27. The BC request message is received by PUBCH, processing is proceeded in the order of UL-BCH and BCH, and the BC request message is passed to the upper layer. Alternatively, the BC request message may be received by PUCCH, the process may proceed in the order of UL-BCH, BCH, and the BC request message may be passed to the upper layer.

FIG. 29 shows a sequence example of the operation in which the terminal device maps the BC request message and the channel and transmits the BC request message. The terminal device 101X accesses the base station 103 using the initial access (for example, random access) (S211), and acquires UL-SCH and UL-BCH setting information from the base station 103 (S212). The terminal device 101X sets UL-SCH (S213) and further sets UL-BCH (S214) based on the acquired setting information. For example, UL-SCH and UL-BCH are set with different ARQ or HARQ, MCS, and TPC parameters. The terminal device 101X generates a BC request message (S215), maps the BC request message to UL-BCH via BCH, and further maps it to PUBCH (S216). The terminal device 101X transmits a BC request message to the base station 103 via the mapped channel (logical channel, transmission channel, physical channel) (S217).

FIG. 30 shows an example of a sequence from when the terminal device 101X transmits a BC request message to a base station using the channel mapping shown in FIG. 26 or FIG. 27 until the BC message is received by another terminal device. Step S221 is added between steps S111 and S112 in FIG. 16, and step S222 is added after S112. Steps S111 to S116 are the same as in FIG. In step S221, BC request message and channel mapping are performed. The operation of step S221 is the same as that of step S216 of FIG. The terminal device 101X transmits a BC request message via the mapped channel (S112). When the base station 103 correctly receives the BC request message, it transmits an ACK message of the wireless link (data link layer) to the terminal device 101X (S222). The reception of the BC request message at the base station 103 is performed, for example, based on the channel mapping shown in FIG. 3Y. The base station 103 transmits the received BC request message to the gateway device 104. Subsequent steps are the same as in FIG.

In the example of FIG. 30, a sequence example is shown when the base station 103 succeeds in receiving the BC request message but fails.

FIG. 31 shows a sequence example when the base station 103 fails to receive the BC request message. The same steps as in FIG. 30 are designated by the same reference numerals, and detailed description thereof will be omitted. When the base station 103 fails to receive the BC request message, it transmits a NACK message to the terminal device 101X (S231). The terminal device 101X retransmits the BC request message using the channel mapping of step S221 (S232). When the base station 103 succeeds in receiving the BC request message, it transmits an ACK message (S233). Subsequent steps are the same as in FIG.

FIG. 32 is a flowchart of an example of the operation of the retransmission process in the terminal device 101X. The terminal device 101X transmits a BC request message (S241), and determines whether or not a wireless link ACK message has been received within a certain period of time (S242). When the ACK message is received (YES), it is determined that the transmission was successful (S243), and the process is terminated. When the ACK message is not received or the NACK message is received (NO in S242), it is determined whether the upper limit of the number of retransmissions of the BC request message has been reached (S244). When the upper limit is reached (YES), successful reception at the data link layer is abandoned, and decoding of the BC request message is performed at the upper level of other devices (for example, base station 103 or the terminal device that is the final destination). Leave it to the layer (S245). If the decryption fails even in the upper layer of the other device, the retransmission request may be transmitted from the upper layer of the other device. In this case, the terminal device 101X may transmit the BC request message again in response to the retransmission request. If the upper limit of the number of times the BC request message is retransmitted has not been reached (NO in S244), the MCS for retransmitting the BC request message is applied (S246), and the TPC for retransmitting the BC request message is applied (S247). , The BC request message is transmitted again (S241).

FIG. 33 shows an example of the format of the body part of the BC request message. Control fields and data fields are shown.

[Control field]
The control fields include BC channel mapping information (or BC channel mapping ID), retransmission flag (or retransmission ID), destination address (destination ID) and other fields.

The BC channel mapping information (or BC channel mapping ID) indicates the channel type to which the BC request message is mapped in each layer (physical layer, data link layer, etc.). For example, there are types of physical channels, types of transmission channels, types of logical channels, and the like.

The resend flag (or resend ID) indicates whether or not the BC request message is resend. Further, the number of retransmissions and at least one of the maximum number of retransmissions may be indicated.

The destination address (or destination ID) indicates an information device (terminal device, node, user, etc.) that is the destination (candidate) of the BC request message. Further, the destination address (or destination ID) may specify a destination type such as broadcast (a plurality of unspecified information devices) or multicast (a plurality of specific information devices). For example, it may be a type of information device in the same cell as the source device (source terminal device, node, user, etc.). Further, it may be a type of information device in a cell different from the source device (source terminal device, node, user, etc.). The type may be specified in place of the destination address (or destination ID) or may be specified together with the destination address (or destination ID).

Other fields may include the address (or ID) of the source device (node, user, etc.) of the BC request message. It may also include a flag (or delimiter) indicating the boundary between the control field and the data field.

[Data field]
The data field includes a data body field (Actual BC message) of the BC request message and one or more upper layer control fields (Control fields). In the data body field, the actual data of the body part of the BC request message is stored. The actual data includes data details (sensing data, notification data, data time stamps, etc.) based on the application type or service type, application type or service type. In the case of blockchain, the actual data may include target data such as approval data and transactions. When generating a BC message from a BC request message, as an example, the data body field or both the upper layer control field and the data body field are fetched, and the BC message including the fetched field is based on the above control field. Generate. The upper layer control field includes, for example, a control field for at least one of a session layer, a presentation layer, and an application layer. A header of at least one layer of a transport layer, a network layer, a data link layer, and a physical layer is added to the BC message depending on the protocol used for transmission to the terminal device. In some cases, a part or all of the control field may be extracted from the BC request message, and the extracted control field may be included in the BC message as it is.

An example of a use case of a blockchain system according to this embodiment will be described. In the following description, the fact that the device broadcasts or multicasts means that the device sends a BC request message and the BC server that receives the BC request message broadcasts or multicasts when the above-described embodiment is applied. Interpret.

(Map management)
The blockchain system according to this embodiment can be used when a map is shared among a plurality of users. As an example, an electronic device mounted on a moving body such as an automobile or an airplane, an electronic device held by a pedestrian, a database device (server) arranged on the Internet, or the like is used as a terminal device 101 (communication device or information device) in FIG. Etc.). Electronic devices mounted on the mobile body, electronic devices held by pedestrians, and database devices generate transactions and broadcast or multicast them to the blockchain system.

Examples of transactions generated by electronic devices and database devices include location information, time stamps, camera moving images and sounds, building names, store names / categories (for example, restaurants, retail stores, hospitals, etc.).

A node in an electronic device or database device collects transactions from a blockchain system and creates a block containing the collected transactions. The approval of the generated block is obtained based on the consensus algorithm, and the approval data including the information about the approved block is broadcast or multicast. Other nodes receive broadcast or multicast approval data and add the approved block to the blockchain. As a result, the map can be shared between the electronic device and the database device, and the map can be updated.

(Operation instructions / records)
The blockchain system according to the present embodiment can be used to provide auxiliary information for instructing a moving body such as a vehicle or an airplane to drive (including automatic driving). In addition, the blockchain system can be used for verification of a moving body such as a vehicle when a failure or accident occurs and for recording data for determining whether insurance is applicable or not.

As an example, an electronic device mounted on a mobile body, a database device (server) located on the Internet, or the like is used as a terminal device 101 (communication device, information device, etc.) in FIG. Electronic devices and database devices mounted on the mobile device generate transactions and broadcast or multicast them to the blockchain system.

Examples of transactions generated by electronic devices and database devices include location information, time stamps, vehicle type / maintenance status, video / audio of in-vehicle cameras, detection results of in-vehicle radar, and driving operation history (automatic driving) such as accelerator / brake. Including the case of), driver status, etc.

A node in an electronic device or database device collects transactions from a blockchain system and creates a block containing the collected transactions. The approval of the generated block is obtained based on the consensus algorithm, and the approval data including the information about the approved block is broadcast or multicast. Other nodes receive broadcast or multicast approval data and add the approved block to the blockchain. As a result, the electronic device or the database device can generate an operation instruction by using the information registered in the blockchain as auxiliary information, and send the generated instruction to the moving body or the driver. In addition, in the event of a breakdown or accident of a moving object, the information registered in the blockchain can be used for verification of the breakdown or accident and for determining whether or not insurance is applicable.

(Robot task management)
The blockchain system according to this embodiment can be used for task management of a plurality of robots operating in a facility such as a warehouse or a factory.

As an example, an electronic device mounted on a plurality of robots in a facility, a database device (server) located on the Internet, etc. are used as a terminal device 101 (communication device, information device, etc.) in FIG. Electronic devices and database devices mounted on the robot generate transactions and broadcast or multicast them to the blockchain system.

An example of a transaction generated by a database device is a work instruction for a robot. Examples of transactions generated by electronic devices mounted on robots include work start, work status, work completion, and work report.

A node among the electronic devices and database devices mounted on the robot collects transactions from the blockchain system and generates a block containing the collected transactions. The approval of the generated block is obtained based on the consensus algorithm, and the approval data including the information about the approved block is broadcast or multicast. Other nodes receive broadcast or multicast approval data and add the approved block to the blockchain. Information registered in the blockchain can be used for work management and inventory management by multiple robots. In addition, the information registered in the blockchain can be used to avoid duplication of work and omission of work between a plurality of robots. This makes it possible to improve work efficiency.

(People trace)
The blockchain system according to this embodiment can be used for tracing a person such as tracking a criminal or a criminal record.

As an example, an electronic device held by a person to be tracked, a sensing device installed in an environment where the person to be tracked moves, a database device (server) placed on the Internet, and the like can be used as a terminal device 101 (the terminal device 101 in FIG. 1). Used as a communication device or information device).

Examples of transactions generated by electronic devices held by the person to be tracked include location information, time stamps, action history, and the like. Examples of transactions generated by the sensing device include location information, time stamps, sensing data, and the like. Examples of sensing data include moving images, sounds, information for identifying a detected person, and information for identifying a detected object (for example, an object held by the detected person).

A node in an electronic device or sensing device generates a transaction and broadcasts or multicasts it to the blockchain system. The database device collects transactions from the blockchain system and generates a block containing the collected transactions. The approval of the generated block is obtained based on the consensus algorithm, and the approval data including the information about the approved block is broadcast or multicast. The other node (eg, a database device) receives broadcast or multicast approval data and adds the approved block to the blockchain. Information registered in the blockchain can be used for tracing people. In this example, the node that holds the blockchain is only the database device, but at least one of the electronic device and the sensing device may also hold the blockchain.

(others)
Other data examples that can be the target data of the blockchain system according to this embodiment are listed below.
・ Financial transactions (stocks, private equity, crowdfunding, bonds, mutual funds, derivatives, annuity insurance, annuities, etc.)
・ Public information (real estate registration, car registration, motorcycle registration, bicycle registration, business registration, marriage certificate, death certificate, etc.)
・ ID (driver's license, ID card, passport, voter registration, etc.)
・ Private (borrowing certificate, loan, contract, gambling, signature, will, trust, etc.)
・ Certificate (insurance certificate, ownership certificate, notary, etc.)
・ Key (house, hotel, rental car, car use, etc.)
・ Intangible assets (patents, trademarks, copyrights, reservations, domain names, etc.)
・ Transactions (escrow transactions, collateralized transactions, third-party arbitrage, multi-party transactions, etc.)

(Hardware configuration)
FIG. 34 shows an example of the hardware configuration of the communication device according to the present embodiment. The communication device included in the terminal device 101, the BC server 105, or the base station 103 is composed of the computer device 300. The computer device 300 includes a CPU 301, an input interface 302, a display device 303, a communication circuit 304, a main storage device 305, and an external storage device 306, which are connected to each other by a bus 307.

The CPU (Central Processing Unit) 301 executes a computer program on the main storage device 305. A computer program is a program that realizes each of the above-mentioned functional configurations of a communication device. The computer program may be realized not by one program but by a combination of a plurality of programs and scripts. Each functional configuration is realized by the CPU 301 executing a computer program.

The input interface 302 is a circuit for inputting operation signals from input devices such as a keyboard, mouse, and touch panel to a communication device.

The display device 303 displays the data stored in the communication device or the data calculated by the communication device. The display device 303 is, for example, an LCD (liquid crystal display), an organic electroluminescence display, a CRT (cathode ray tube), or a PDP (plasma display), but is not limited thereto.

The communication circuit 304 is a circuit for the communication device to communicate with the external device wirelessly or by wire. Data used in the communication device can be input from an external device via the communication circuit 304. The communication circuit 304 includes an antenna. The data input from the external device can be stored in the main storage device 305 or the external storage device 306.

The main storage device 305 stores a computer program, data necessary for executing the computer program, data generated by executing the computer program, and the like. The computer program is expanded and executed on the main storage device 305. The main storage device 305 is, for example, RAM, DRAM, and SRAM, but is not limited thereto. The storage unit of FIG. 5 may be built on the main storage device 305.

The external storage device 306 stores a computer program, data necessary for executing the computer program, data generated by executing the computer program, and the like. These computer programs and data are read out to the main storage device 305 when the computer program is executed. The external storage device 306 is, for example, a hard disk, an optical disk, a flash memory, and a magnetic tape, but is not limited thereto. The storage unit of FIG. 5 may be constructed on the external storage device 306.

The computer program may be installed in the computer device 300 in advance, or may be stored in a storage medium such as a CD-ROM. Further, the computer program may be uploaded on the Internet.

Further, the computer device 300 may be configured by a single device or may be configured as a system composed of a plurality of computer devices connected to each other.

It should be noted that the above-described embodiment shows an example for embodying the present disclosure, and the present disclosure can be implemented in various other forms. For example, various modifications, substitutions, omissions, or combinations thereof are possible without departing from the gist of the present disclosure. The forms in which such modifications, substitutions, omissions, etc. are made are also included in the scope of the invention described in the claims and the equivalent scope thereof, as are included in the scope of the present disclosure.

Further, the effects of the present disclosure described in the present specification are merely examples, and other effects may be obtained.

The present disclosure may also have the following structure.
[Item 1]
A first receiver that receives a first request message requesting that the target data be transmitted to at least one information device that is the target of broadcasting or multicast.
A communication device including a first transmission unit that transmits the target data to the at least one information device based on the first request message.
[Item 2]
The first request message includes identification information of the at least one information device.
The communication device according to item 1, further comprising a processing unit that identifies at least one information device based on the identification information.
[Item 3]
A processing unit that identifies an information device that uses the application or service of the target data based on information that associates the type of application or service with the information device that uses the application or service of the type.
The communication device according to item 1 or 2, wherein the first transmission unit transmits the target data to the specified information device.
[Item 4]
The first request message includes the type of application or service of the target data.
The communication device according to item 3, wherein the processing unit identifies an application or service of the target data based on the type included in the first request message.
[Item 5]
A storage unit that stores the first request message,
A counter for counting the first request message stored in the storage unit is provided, and the first transmission unit has the first number of the first request messages when the number of the first request messages reaches the first number. The communication device according to any one of items 1 to 4 for transmitting the target data based on each of the first request messages.
[Item 6]
A storage unit that stores the first request message,
A processing unit for activating the timer and specifying the first request message stored after the timer is activated and before the timer times out is provided.
The communication device according to any one of items 1 to 5, wherein the first transmission unit transmits the target data for each specified first request message.
[Item 7]
A storage unit that stores the first request message,
A second receiver that receives a request to acquire target data from the first information device, and
A processing unit for determining whether or not the first request message for which the first information device is to be transmitted exists in the storage unit when the acquisition request is received is provided.
When the first request message for which the first information device is to be transmitted exists, the first transmission unit transmits the target data requested by the first request message to the first information device. The communication device according to any one of 1 to 6.
[Item 8]
The communication device according to any one of items 1 to 7, wherein the first receiving unit receives the first request message from the second information device via an uplink.
[Item 9]
Item 8. The communication device according to item 8, further comprising a second transmission unit that transmits a delivery confirmation response to the second information device according to the success or failure of reception of the first request message.
[Item 10]
The first receiving unit receives the first request message on the first channel of the uplink, and receives the first request message.
The first receiving unit receives user data different from the first request message on the second channel of the uplink.
The communication device according to item 8 or 9, wherein parameters related to at least one of retransmission control, modulation method, and transmission power control can be independently set between the first channel and the second channel.
[Item 11]
The communication device according to any one of items 1 to 10, wherein the target data is data generated by a blockchain application.
[Item 12]
The communication device according to item 11, wherein the target data is a transaction of the blockchain.
[Item 13]
The communication device according to item 11 or 12, wherein the target data is a block approval request or approval data in the blockchain.
[Item 14]
A processing unit that generates a first request message requesting the server to send the target data to at least one information device that is the target of broadcasting or multicast.
A transmission unit that transmits the first request message to the server via an uplink, and a transmission unit.
A communication device equipped with.
[Item 15]
A receiver for receiving a delivery confirmation response to the first request message is provided.
The communication device according to item 14, wherein when the transmission unit detects that the transmission of the first request message has failed based on the delivery confirmation response, the transmission unit retransmits the first request message.
[Item 16]
The transmission unit transmits the first request message on the first channel of the uplink.
The transmission unit transmits user data different from the first request message on the second channel of the uplink.
The communication device according to

item

14 or 15, wherein parameters relating to at least one of retransmission control, modulation method, and transmission power control can be independently set between the first channel and the second channel.
[Item 17]
The communication device according to any one of items 14 to 16, wherein the first request message includes identification information of at least one information device.
[Item 18]
The communication device according to any one of items 14 to 17, wherein the processing unit determines the server to be the destination of the first request message according to the type of the application or service of the target data.
[Item 19]
The communication device according to any one of items 14 to 18, wherein the first request message includes the type of application or service of the target data.
[Item 20]
The communication device according to any one of items 14 to 19, wherein the transmission unit establishes the uplink with the base station and transmits the first request message to the base station.
[Item 21]
The communication device according to item 20, wherein the server is included in the base station.
[Item 22]
Receives a first request message requesting that the target data be transmitted to at least one information device that is the target of broadcasting or multicast.
A communication method for transmitting the target data to the at least one information device based on the first request message.
[Item 23]
Generates a first request message requesting the server to send the target data to at least one information device that is the target of broadcast or multicast.
A communication method for transmitting the first request message to the server via an uplink.
[Item 24]
A processing unit that generates a first request message requesting transmission of target data to at least one information device that is the target of broadcasting or multicast, and a transmission unit that transmits the first request message via an uplink. The first communication device equipped with
A second communication device including a receiving unit that receives the first request message, and a transmitting unit that transmits the target data to at least one information device based on the first request message.
Communication system with.

10 Antenna 11 Communication unit 14 Processing unit 15 Storage unit 20 Antenna 21 Communication unit 22 Timer 23 Counter 24 Processing unit 25 Storage unit 100 Distributed network (blockchain system)
101 Terminal equipment (communication equipment or information equipment)
102 Communication network 103 Base station 104 Gateway device 105 BC server 106 Core network 107 Base station 111B Connection 111C Connection 111D Connection 111E Connection 300 Computer device 302 Input interface 303 Display device 304 Communication circuit 305 Main storage device 306 External storage device 307 Bus

Claims

A first receiver that receives a first request message requesting that the target data be transmitted to at least one information device that is the target of broadcasting or multicast.
A communication device including a first transmission unit that transmits the target data to the at least one information device based on the first request message.
The first request message includes identification information of the at least one information device.
The communication device according to claim 1, further comprising a processing unit that identifies at least one information device based on the identification information.
A processing unit that identifies an information device that uses the application or service of the target data based on information that associates the type of application or service with the information device that uses the application or service of the type.
The communication device according to claim 1, wherein the first transmission unit transmits the target data to the specified information device.
The first request message includes the type of application or service of the target data.
The communication device according to claim 3, wherein the processing unit identifies an application or service of the target data based on the type included in the first request message.
A storage unit that stores the first request message,
A counter for counting the first request message stored in the storage unit is provided, and the first transmission unit has the first number of the first request messages when the number of the first request messages reaches the first number. The communication device according to claim 1, wherein the target data is transmitted based on each of the first request messages.
A storage unit that stores the first request message,
A processing unit for activating the timer and specifying the first request message stored after the timer is activated and before the timer times out is provided.
The communication device according to claim 1, wherein the first transmission unit transmits the target data for each specified first request message.
A storage unit that stores the first request message,
A second receiver that receives a request to acquire target data from the first information device, and
A processing unit for determining whether or not the first request message for which the first information device is to be transmitted exists in the storage unit when the acquisition request is received is provided.
The first transmission unit requests to transmit the target data requested by the first request message to the first information device when the first request message to be transmitted by the first information device exists. Item 1. The communication device according to item 1.
The communication device according to claim 1, wherein the first receiving unit receives the first request message from the second information device via an uplink.
The communication device according to claim 8, further comprising a second transmission unit that transmits a delivery confirmation response to the second information device according to the success or failure of reception of the first request message.
The first receiving unit receives the first request message on the first channel of the uplink, and receives the first request message.
The first receiving unit receives user data different from the first request message on the second channel of the uplink.
The communication device according to claim 8, wherein the first channel and the second channel can independently set parameters related to at least one of retransmission control, modulation method, and transmission power control.
The communication device according to claim 1, wherein the target data is data generated by a blockchain application.
The communication device according to claim 11, wherein the target data is a transaction of the blockchain.
The communication device according to claim 11, wherein the target data is a block approval request or approval data in the blockchain.
A processing unit that generates a first request message requesting the server to send the target data to at least one information device that is the target of broadcasting or multicast.
A transmission unit that transmits the first request message to the server via an uplink, and a transmission unit.
A communication device equipped with.
A receiver for receiving a delivery confirmation response to the first request message is provided.
The communication device according to claim 14, wherein when the transmission unit detects that the transmission of the first request message has failed based on the delivery confirmation response, the transmission unit retransmits the first request message.
The transmission unit transmits the first request message on the first channel of the uplink.
The transmission unit transmits user data different from the first request message on the second channel of the uplink.
The communication device according to claim 14, wherein the first channel and the second channel can independently set parameters related to at least one of retransmission control, modulation method, and transmission power control.
The communication device according to claim 14, wherein the first request message includes identification information of the at least one information device.
The communication device according to claim 14, wherein the processing unit determines the server to be the destination of the first request message according to the type of the application or service of the target data.
The communication device according to claim 14, wherein the first request message includes a type of application or service of the target data.
The communication device according to claim 14, wherein the transmission unit establishes the uplink with the base station and transmits the first request message to the base station.
The communication device according to claim 20, wherein the server is included in the base station.
Receives a first request message requesting that the target data be transmitted to at least one information device that is the target of broadcasting or multicast.
A communication method for transmitting the target data to the at least one information device based on the first request message.
Generates a first request message requesting the server to send the target data to at least one information device that is the target of broadcast or multicast.
A communication method for transmitting the first request message to the server via an uplink.
A processing unit that generates a first request message requesting transmission of target data to at least one information device that is the target of broadcasting or multicast, and a transmission unit that transmits the first request message via an uplink. The first communication device equipped with
A second communication device including a receiving unit that receives the first request message, and a transmitting unit that transmits the target data to at least one information device based on the first request message.
Communication system with.