Block chain-based data transmission method and communication device

Abstract

The embodiment of the invention provides a data transmission method based on a block chain and a communication device, which are used for providing an implementation scheme for deep integration of a block chain technology and a wireless network, and according to the implementation scheme, the block chain is directly associated and interacted with data in a protocol stack of the wireless network; the credibility of the block chain can be fully utilized to enhance the security of the data in the protocol stack. The method comprises: sending first indication information and first data, the first indication information being used for indicating that the first data is block chain data to be consensus-confirmed, the first data comprising data of a radio resource control (RRC) layer, and / or transmission parameters in a data link layer for transmitting control signaling and / or service data; obtaining a consensus confirmation result of the first data, wherein the consensus confirmation result of the first data is used for indicating that consensus confirmation of the first data is passed; and updating the first data to the local block chain.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular, to a data transmission method and a communication device based on a blockchain. Background Art

[0002] A blockchain (BC) is a distributed ledger technology (DLT) that combines various technologies such as cryptographic technology, peer-to-peer (P2P) networks, and distributed databases. It has the characteristics of being publicly transparent, immutable, traceable throughout the process, historically traceable, collectively maintained, and intelligent execution. It is very suitable for establishing multi-party collaborative trust in a wireless communication environment lacking trust. The integration of the blockchain and wireless networks has become an important evolution direction for future communication networks (such as the 6th generation (6G) communication network).

[0003] However, the current integration of the blockchain and wireless networks still remains at the mechanism splicing design, and it is difficult to fundamentally solve the security problems in complex and diverse wireless networks. Therefore, how to specifically achieve the deep integration of the blockchain and wireless networks remains to be studied. Summary of the Invention

[0004] The data transmission method and communication device based on a blockchain provided in the embodiments of this application are used to provide an implementation solution for the deep integration of blockchain technology and wireless networks. This implementation solution can directly associate and interact with the data in the protocol stack of the blockchain and wireless networks, and can make full use of the credibility of the blockchain to enhance the security of the data in the protocol stack.

[0005] To achieve the above object, the embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, a data transmission method based on a blockchain is provided. This method can be executed by a first device. The first device can be the terminal device itself, or can refer to a processor, module, chip, or chip system in the terminal device that implements this method; or, the first device can be the access network device itself, or can refer to a processor, module, chip, or chip system in the access network device that implements this method. Hereinafter, an example will be given with this method being executed by the first device. The method includes: sending first indication information and first data, where the first indication information is used to indicate that the first data is blockchain data to be consensus-confirmed, and the first data includes data in the radio resource control (RRC) layer, and / or transmission parameters in the data link layer for transmitting control signaling and / or service data; obtaining a consensus confirmation result of the first data, where the consensus confirmation result of the first data is used to indicate that the first data has passed the consensus confirmation; and updating the first data to the local blockchain.

[0007] In the embodiments of the present application, the first device can upload data in the protocol stack of a wireless network such as the RRC layer or the data link layer through the first indication information and the first data, thereby realizing the direct associated interaction between the blockchain and the data in the protocol stack of the wireless network, and thus the credibility of the blockchain can be fully utilized to enhance the security of the data in the protocol stack. Therefore, based on the blockchain-based data transmission method provided by the embodiments of the present application, the direct associated interaction between the blockchain and the data in the protocol stack of the wireless network can be realized, the deep integration of the blockchain technology and the wireless network can be achieved, and thus the credibility of the blockchain can be fully utilized to enhance the security of the data in the protocol stack.

[0008] In a possible implementation manner, the method provided in the first aspect further includes: sending a first request for requesting access to the wireless network, where the first request includes second indication information for indicating at least one of the following: the identity of the terminal device, the capabilities of the terminal device, or the protocol layer of the terminal device having blockchain capabilities. The identity of the terminal device is used to determine the permission to join the blockchain network, the capabilities of the terminal device are used to determine whether the terminal device supports joining the blockchain network, and the protocol layer of the terminal device having blockchain capabilities is used to determine the protocol layer corresponding to the first data; receiving a first response including third indication information for indicating the protocol layer of the access network device having blockchain capabilities. That is to say, the first device is the terminal device, and the first device can interact with the access network device about the relevant information of the blockchain through the first request and the first response, so as to facilitate the trusted interaction between the blockchain and the protocol stack.

[0009] In a second aspect, a blockchain-based data transmission method is provided. This method can be executed by a second device, where the second device can be the terminal device itself, or a processor, module, chip, or chip system in the terminal device that implements this method; or the second device can be the access network device itself, or a processor, module, chip, or chip system in the access network device that implements this method. Hereinafter, an example will be given with this method being executed by the second device. The method includes: receiving first indication information and first data, where the first indication information is used to indicate that the first data is blockchain data to be consensus-confirmed, and the first data includes data of the radio resource control (RRC) layer, and / or transmission parameters in the data link layer for transmitting control signaling and / or service data; obtaining the consensus confirmation result of the first data, where the consensus confirmation result of the first data is used to indicate that the first data has passed the consensus confirmation; and updating the first data to the local blockchain.

[0010] Among them, for the technical effects of the second aspect, reference can be made to the technical effects of the first aspect, which will not be elaborated here.

[0011] In a possible implementation, the method provided in the second aspect further includes: receiving a first request for requesting access to a wireless network, where the first request includes second indication information for indicating at least one of the following: the identity of the terminal device, the capabilities of the terminal device, or the protocol layer of the terminal device with blockchain capabilities. The identity of the terminal device is used to determine the permission to join the blockchain network, the capabilities of the terminal device are used to determine whether the terminal device supports joining the blockchain network, and the protocol layer of the terminal device with blockchain capabilities is used to determine the protocol layer corresponding to the first data; sending a first response, where the first response includes third indication information for indicating the protocol layer of the access network device with blockchain capabilities. That is to say, the second device is an access network device, and the second device can interact with the access network device about blockchain-related information through the first request and the first response, so as to facilitate the trusted interaction between the blockchain and the protocol stack.

[0012] Combined with the first aspect or the second aspect above, in a possible implementation, the transmission parameters include at least one of the following: scheduling parameters of the Media Access Control (MAC) layer, security parameters of the Packet Data Convergence Protocol (PDCP) layer, or Quality of Service (QoS) flow parameters of the Service Data Adaptation Protocol (SDAP) layer. That is to say, by performing consensus confirmation on the scheduling parameters of the MAC layer, the security parameters of the PDCP layer, or the QoS flow parameters of the SDAP layer, the transmission parameters of each of the above protocol layers can be recorded on the blockchain, thereby ensuring the integrity and security of the transmission parameters of each of the above protocol layers.

[0013] Combined with the first aspect or the second aspect above, in a possible implementation, the scheduling parameters include at least one of the following: channel quality parameters, modulation parameters, or retransmission indication parameters. That is to say, by performing consensus confirmation on the scheduling parameters of the MAC layer to record the scheduling parameters on the blockchain, integrity protection, multi-party trusted deposit, and traceability capabilities can be provided for the scheduling parameters of the MAC layer.

[0014] Combined with the first aspect or the second aspect above, in a possible implementation, the security parameters include a message authentication code for protecting the integrity of the data within the PDCP layer, and / or an identifier of a key for encrypting the data and / or the message authentication code within the PDCP layer. That is to say, by performing consensus confirmation on the security parameters of the PDCP layer to record the security parameters on the blockchain, the security parameters of the PDCP layer can be combined with the security mechanisms and algorithms of the blockchain. On the basis of realizing integrity protection, multi-party trusted deposit, and traceability, the linkage configuration of the key environment within a certain area can also be realized, and thus the environmental security can be more sensitive to respond and make adjustments.

[0015] Combined with the above first aspect or second aspect, in a possible implementation, the QoS flow parameters include: QoS flow identifier QFI, and / or, reflection QoS flow to data radio bearer DRB mapping indication RDI. That is to say, by performing consensus confirmation on the QoS flow parameters of the SDAP layer, the QoS flow parameters can be recorded on the blockchain, and then the QoS situation in a certain area can be uniformly and conveniently counted and analyzed through the blockchain, so as to facilitate the realization of a custom area range and the joint recording of QoS data of multiple operators, so that hot spots can be sensed, and adjustment instructions can be issued through the blockchain to achieve network QoS optimization and adjustment in a certain area or even across operators.

[0016] For example, NF network elements in the core network (such as network data analytics function (NWDAF), or operations, administration and management (OAM), etc.) can adjust the QoS policy in a certain area according to the multi-party QoS flow parameters on the blockchain, and notify the adjusted QoS policy to network elements such as the policy management function network element, the access network device, and the user plane function network element through the session management function network element.

[0017] For another example, a blockchain network where the first device and the second device are deployed has a smart contract for realizing QoS optimization and adjustment. After the security parameters in the first data are recorded on the blockchain, the instruction information for QoS optimization and adjustment can be obtained by calling the smart contract based on the security parameters of multiple blockchain nodes on the blockchain, and the NF network elements in the core network can be notified through the terminal device or the access network device in the blockchain network, so as to achieve QoS optimization and adjustment.

[0018] Combined with the above first aspect or second aspect, in a possible implementation, the data of the RRC layer includes at least one of the following: the capability information of the terminal device, the measurement report of the terminal device, or the system information. That is to say, by performing consensus confirmation on the capability information of the terminal device, the measurement report of the terminal device, or the system information in the RRC layer, the capability information, measurement report, and global system information of the terminal device can be recorded on the blockchain, which is convenient for carrying out related applications such as wireless network access authentication and authorization and regulatory review of the terminal device, can make the distributed identity tracking of mobile users more convenient, and can improve the running stability of the blockchain established in the wireless network.

[0019] Combined with the first aspect or the second aspect above, in a possible implementation manner, the first indication information and the first data are carried by a protocol data unit (PDU) of the first protocol layer. The first indication information is further used to indicate the protocol layer corresponding to the first data. The protocol layer corresponding to the first data includes at least one of the following: the RRC layer, the SDAP layer, the PDCP layer, or the MAC layer. That is to say, the first indication information and the first data can be sent in the form of being encapsulated into a PDU, and the protocol layer corresponding to the first data is indicated by the first indication information, so that the blockchain sub-layer on the receiving side can determine that there is blockchain data to be consensus-confirmed in the first PDU received this time.

[0020] Combined with the first aspect or the second aspect above, in a possible implementation manner, the first data is determined according to the blockchain parameter operation indication information, and the blockchain parameter operation indication information is used to indicate the data to be consensus-confirmed in the RRC layer and / or the transmission parameters for transmitting control signaling and / or service data to be consensus-confirmed in the data link layer. That is to say, the first device can determine which data and / or transmission parameters are to be consensus-confirmed according to the blockchain parameter operation indication information, and further can determine the first data.

[0021] Combined with the first aspect or the second aspect above, in a possible implementation manner, the method provided by the first aspect or the second aspect further includes: obtaining adjustment indication information, where the adjustment indication information is used to indicate to adjust the data to be consensus-confirmed in the RRC layer and / or the transmission parameters for transmitting control signaling and / or service data to be consensus-confirmed in the data link layer; and / or the data to be adjusted in the RRC layer and / or the transmission parameters for transmitting control signaling and / or service data to be adjusted in the data link layer; updating the blockchain parameter operation indication information according to the adjustment indication information to obtain the updated blockchain parameter operation indication information. That is to say, the blockchain parameter operation indication information in the blockchain can be updated according to the adjustment indication information, and thus can more flexibly adapt to the wireless network with dynamic channel changes.

[0022] Combined with the first aspect or the second aspect above, in a possible implementation manner, the adjustment indication information is the adjustment indication information from the first smart contract (SC) used to adjust the blockchain parameter operation indication information; the method provided by the first aspect or the second aspect further includes: sending a first call request, where the first call request is used to request to call the first SC, and the first SC is used to adjust the blockchain parameter operation indication information; receiving a first consensus message, where the first consensus message is used to indicate that the first call request has passed the consensus confirmation. That is to say, the smart contract deployed on the blockchain can collect the on-chain data of multiple blockchain nodes, and then can perform analysis and calculation to adjust the blockchain parameter operation indication information, so that the function of the protocol stack can be affected based on the adjusted blockchain parameter indication information.

[0023] Combined with the first aspect or the second aspect above, in a possible implementation, the updated blockchain operation indication information is used to indicate: the data to be adjusted in the RRC layer, and / or, the transmission parameters for transmitting control signaling and / or service data to be adjusted in the data link layer; the method provided by the first aspect or the second aspect further includes: obtaining second data, where the second data includes the data to be adjusted in the RRC layer, and / or, the transmission parameters for transmitting control signaling and / or service data to be adjusted in the data link layer; adjusting the second data according to the updated blockchain operation indication information to obtain third data; and sending the third data. That is to say, when the first device and / or the device transmits a PDU including the parameters corresponding to the updated blockchain parameter operation indication information, the PDU is processed to realize the empowerment of the blockchain to the protocol stack function.

[0024] In a third aspect, a communication device is provided for implementing the above various methods. The communication device may be the first device in any of the above aspects or any of its implementations, or a device including the first device above, or a device included in the first device above, such as a chip; or, the communication device may be the second device in any of the above aspects or any of its implementations, or a device including the second device above, or a device included in the second device above, such as a chip. The communication device includes corresponding modules, units, or means for implementing the above methods, and the modules, units, or means may be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0025] In some possible designs, the communication device may include a processing module and a transceiver module. The transceiver module, which may also be referred to as a transceiver unit, is used to implement the sending and / or receiving functions in any of the above aspects and any of its possible implementations. The transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface. The processing module may be used to implement the processing functions in any of the above aspects and any of its possible implementations.

[0026] In some possible designs, the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in any of the above aspects and any of its possible implementations.

[0027] In a fourth aspect, a communication device is provided, including: at least one processor; the processor is used to execute a computer program or instruction so that the communication device executes the method described in any of the above aspects.

[0028] In one possible implementation, the communication device further includes the memory. Optionally, the memory is coupled to the processor. The memory can be integrated with the processor, or the memory can be independent of the processor. Optionally, the processor is configured to execute the computer program or instructions stored in the memory.

[0029] In one possible implementation, the memory is independent of the communication device.

[0030] In one possible implementation, the communication device further includes a communication interface, which is configured to communicate with modules outside the communication device. The communication device can be the first device in any of the above aspects or any of its implementation manners, or a device including the above first device, or a device included in the above first device, such as a chip.

[0031] In a fifth aspect, a computer-readable storage medium is provided, in which computer programs or instructions are stored. When running on a communication device, the communication device can execute the method described in any of the above aspects or any of its implementation manners.

[0032] In a sixth aspect, a computer program product including instructions is provided. When running on a communication device, the communication device can execute the method described in any of the above aspects or any of its implementation manners.

[0033] In a seventh aspect, a communication device (for example, the communication device can be a chip or a chip system) is provided. The communication device includes a processor configured to implement the functions involved in any of the above aspects or any of its implementation manners.

[0034] In some possible designs, the communication device includes a memory, which is configured to store necessary program instructions and data.

[0035] In some possible designs, when the device is a chip system, it can be composed of chips or include chips and other discrete devices.

[0036] It can be understood that when the communication device provided in any of the third to seventh aspects is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0037] Among them, the technical effects brought by any of the design manners in the third to seventh aspects can be referred to the technical effects brought by different design manners in the above first or second aspect, which will not be elaborated here.

[0038] In an eighth aspect, a communication system is provided, which includes: the first device in the first aspect or any of its implementation manners above, and the second device in the second aspect or any of its implementation manners above. Description of the Drawings

[0039] Figure 1 is a schematic diagram of a protocol stack structure provided by an embodiment of the present application;

[0040] Figure 2 is a schematic diagram of the downlink data processing of the data link layer provided by an embodiment of the present application;

[0041] Figure 3 is a schematic diagram of the method flow for deploying a blockchain in a communication network provided by an embodiment of the present application;

[0042] Figure 4 is a schematic diagram of the system architecture for deploying a blockchain in a communication network provided by an embodiment of the present application Figure 1 ;

[0043] Figure 5 is a schematic diagram of the system architecture for deploying a blockchain in a communication network provided by an embodiment of the present application Figure 2 ;

[0044] Figure 6 is a schematic diagram of the structure of a communication system provided by an embodiment of the present application;

[0045] Figure 7 is a schematic diagram of the method flow of a data transmission method based on a blockchain provided by an embodiment of the present application;

[0046] Figure 8 is a schematic diagram of the structure of a blockchain sublayer PDU provided by an embodiment of the present application;

[0047] Figure 9 is a schematic diagram of the protocol stack structure with a blockchain sublayer deployed inside the MAC layer provided by an embodiment of the present application;

[0048] Figure 10 is a schematic diagram of the protocol stack structure with a blockchain sublayer deployed inside the PDCP layer provided by an embodiment of the present application;

[0049] Figure 11 is a schematic diagram of the protocol stack structure with a blockchain sublayer deployed inside the SDAP layer provided by an embodiment of the present application;

[0050] Figure 12 is a schematic diagram of the protocol stack structure with a blockchain sublayer deployed inside the RRC layer provided by an embodiment of the present application;

[0051] Figure 13 is a schematic diagram of the structure of a communication device provided by an embodiment of the present application Figure 1 ;

[0052] Figure 14 is a schematic diagram of the structure of a communication device provided by an embodiment of the present applicationFigure 2 。 Detailed implementation manners

[0053] To facilitate the understanding of the technical solutions provided by the embodiments of the present application, a brief introduction to the relevant technical terms of the present application is first given. The brief introduction is as follows:

[0054] First, the protocol stack structure of the wireless network:

[0055] The communication entities in the wireless network may include terminal devices and radio access network (RAN) devices. The 3rd generation partnership project (3GPP) defines the air interface protocol followed by the interface (or called the air interface, abbreviated as the air interface) between the terminal device and the RAN device in the RAN. The protocol stack of this air interface protocol can be divided into three layers and two planes. Among them, the three layers include the physical (PHY) layer (or called layer 1 (L1)), the data link layer (or called layer 2 (L2)), and the network layer (or called layer 3 (L3)), and the two planes include the control plane for transmitting control signaling and the user plane for transmitting service data.

[0056] Figure 1 It is a schematic diagram of a protocol stack structure provided by an embodiment of the present application. As Figure 1 shown in (a) of, the protocol stack structure of the control plane logically includes, from top to bottom: the network layer, the data link layer, and the PHY layer. Among them, the network layer may include the radio resource control (RRC) layer, and the RRC layer is responsible for processing the signaling exchanged between the terminal device and the RAN device. For example, the functions supported by the RRC layer may include: broadcasting, paging, RRC management, radio bearer control, mobility management, quality of service (QoS) flow management, terminal-side measurement reporting and measurement reporting control, radio link failure detection and recovery, and transmission of non-access stratum (NAS) messages, etc. Among them, the NAS message is generated by the NAS protocol layer, and the NAS protocol layer mainly supports functions such as authentication, mobility management, or security control of the terminal device.

[0057] The data link layer logically includes, from top to bottom: the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Media Access Control (MAC) layer. Among them, in the control plane, the MAC layer, the RLC layer, and the PDCP layer are responsible for the transmission, encryption, and integrity protection of radio bearer signaling. In addition, radio bearers are divided into two categories: the Data Radio Bearer (DRB) for the user plane and the Signaling Radio Bearer (SRB) for the control plane.

[0058] The PHY layer can provide the functions required for the transmission of bitstreams in the physical medium. For example, the PHY layer provides services for data transmission to the MAC layer and higher layers. The services provided by the PHY layer can be described by transport channels, which describe the characteristics of the data transmitted by the PHY layer to the MAC layer and higher layers. The PHY layer can map the transport channels to physical channels.

[0059] As Figure 1 shown in (b) of , the protocol stack structure of the user plane logically includes, from top to bottom: the data link layer and the PHY layer. Among them, the difference between the data link layer of the user plane and the control plane is that: the data link layer of the user plane also includes the Service Data Adaptation Protocol (SDAP) layer above the PDCP layer, and the SDAP layer is responsible for the mapping of QoS flows to DRBs.

[0060] In addition, the MAC layer, the RLC layer, and the PDCP layer of the user plane are similar to those of the control plane. The difference between the two is that: in the user plane, the MAC layer, the RLC layer, and the PDCP layer are responsible for the transmission and encryption of service data. In addition, the PHY layer of the user plane is the same as that of the control plane, which will not be elaborated here.

[0061] It should be understood that the above Figure 1 shown protocol stack structure is only the underlying protocol layer structure, and this protocol stack structure can also include higher-level protocol layers, such as the application layer. Among them, the application layer can provide user service data transmission services for various types of applications (APP) in communication. In addition, different types of applications correspond to different types of service data. For example, game APPs correspond to game service data, video playback APPs correspond to video service data, social APPs correspond to social service data, etc.

[0062] It can be understood that Figure 1In the protocol stack structures shown in (a) and (b), the connection points between each protocol layer are called service access points (SAPs). The SDAP layer provides QoS flow-level services for the upper layer, the PDCP layer provides radio bearer-level services for the SDAP layer, the MAC layer provides logical channel-level services for the RLC layer, and the PHY layer provides transport channel-level services for the MAC layer.

[0063] Taking the downlink data transmission of the user plane as an example below, the data processing processes of each protocol layer in the data link layer are exemplarily described.

[0064] Figure 2 It is a schematic diagram of downlink data processing of a data link layer provided by an embodiment of the present application. As Figure 2 shown, the processing process of downlink data is processed layer by layer from the SDAP layer to the MAC layer. The data of each layer in the SDAP layer to the MAC layer is introduced separately below.

[0065] SDAP layer:

[0066] The service data submitted by the upper layer of the SDAP layer (such as the internet protocol (IP) layer) to the SDAP layer can be, for example, IP packets (or called data packets or messages, etc.). The SDAP layer can complete the mapping of QoS flows in the IP data packet to DRBs. For example, the SDAP layer can encapsulate the IP data in the IP data packet into a protocol data unit (PDU) of the SDAP layer, that is, an SDAP PDU, and this SDAP PDU corresponds to a DRB. In addition, this IP data packet can be encapsulated into multiple SDAP PDUs, and these multiple SDAP PDUs correspond to a DRB.

[0067] It can be understood that the service data transmission of the terminal device is transmitted through a PDU session established between the terminal device, the access network device, and the network function (NF) network elements in the core network. Each independent PDU session can configure an SDAP entity to implement the mapping of QoS flows of each PDU session to DRBs.

[0068] In a possible implementation manner, the SDAP PDU can include a header and an SDAP layer service data unit (SDU). The SDAP SDU can include IP data in units of QoS flows. The header of the SDAP PDU can include a QoS flow identifier (QoS flow ID, QFI) of this QoS flow, and this QFI is used to indicate which QoS flow this SDAP PDU belongs to.

[0069] In addition, the header of the SDAP PDU may further include a reflective QoS flow to DRB mapping indication (RDI), and / or a reflective QoS indication (RQI). Among them, the RDI is used to indicate whether the mapping rule of the QoS flow to the DRB needs to be updated, and the RQI is used to indicate whether to notify the NAS layer to update the mapping rule of the service data flow (SDF) to the QoS flow. It can be understood that the RAN device schedules services in terms of QoS flows, and the network function (NF) network elements in the core network connected to the RAN device process service data in terms of SDFs, or rather, the service data flows are in terms of SDFs at the NAS layer. Furthermore, when the NF network elements process service data, the mapping between the SDF and the QoS flow can be achieved through the RQI, thereby achieving the QoS guarantee of services in terms of QoS flows.

[0070] It should be understood that in some cases, the SDAP PDU may not include a header. For example, when the RDI and / or the RQI do not need to be updated, the SDAP PDU may not include a header. Another example is that when the configuration parameter corresponding to the SDAP layer (such as the parameter sdap-HeaderDL) does not configure the SDAP header, the SDAP PDU may not include a header.

[0071] PDCP layer:

[0072] After the SDAP PDU enters the PDCP layer, the SDAP PDU is part of the SDU of the PDCP layer, and the PDCP layer processes the SDU of the PDCP layer to generate the PDCP PDU. Among them, the functions of the PDCP layer for the user plane may include, for example: robust header compression (ROHC) processing, security processing, and service data transmission, etc.

[0073] It should be understood that the security processing of the PDCP layer may include: encryption, decryption, or integrity protection, etc. Furthermore, the SDU of the PDCP layer may further include security information, and this security information may include, for example: a message authentication code for data integrity protection (for example, a message authentication code–integrity (MAC-I)).

[0074] In addition, the PDCP PDU may include a header, which may include a serial number (SN) of the PDCP. The SN of the PDCP may be used for reordering of logical channels to the upper layer in the acknowledged mode, delivering on demand, and duplicate detection of the underlying SDU data.

[0075] It can be understood that the PDCP PDU on the control plane is similar to the PDCP PDU on the user plane described above. The SDU in the PDCP PDU on the control plane may include SRB data, security information, etc. The embodiments of the present application do not make specific limitations thereto.

[0076] RLC layer:

[0077] After the PDCP PDU enters the RLC layer, the RLC layer entity processes the PDCP PDU to generate an RLC PDU. Among them, the RLC layer supports three transmission modes: transparent mode, unacknowledged mode, and acknowledged mode. The transparent mode is mainly used for the transmission of paging messages, system information broadcasts, and signaling radio bearer (SRB) 0 signaling. Other SRB signaling is transmitted in the acknowledged mode. The DRB for transmitting user data can be transmitted in the acknowledged mode or unacknowledged mode according to the service type.

[0078] The main functions of the RLC layer are to reorder the PDCP PDU, as well as segment, reassemble, concatenate, etc. For example, the RLC layer can execute a feedback-based retransmission mechanism, such as an automatic repeat request (ARQ) mechanism. ARQ is a function of the RLC layer in the acknowledged mode. The ARQ operations at the sending end include transmitting and retransmitting PDUs or segments, receiving status reports sent from the receiving end, and receiving HARQ transmission failure indications sent from the lower layer (such as the MAC layer). The ARQ operations at the receiving end include detecting whether the reception of the RLC layer PDU fails, and regularly feeding back the data reception situation to the sending end through the RLC layer status report. Among them, the information included in the status report includes the SN of the RLC that the receiving end has received and the SN that has not been received. When the receiving end detects a packet loss, it notifies the sending end through the RLC layer status report that a PDU or re-segment in the acknowledged mode has not been received, and requests the sending end to retransmit the PDU. The relationship between the HARQ mechanism of the MAC layer and the ARQ mechanism of the RLC layer is that when the hybrid automatic repeat request (HARQ) retransmission reaches the maximum number of retransmissions and still fails, the retransmission is performed through ARQ.

[0079] MAC layer:

[0080] After the RLC PDU enters the MAC layer, the MAC layer entity processes the RLC PDU to generate a MAC PDU. Among them, the MAC layer processes the RLC PDUs of multiple RBs to generate a MAC PDU. The MAC layer supports the mapping of logical channels to transport channels, the multiplexing and demultiplexing of MAC SDUs from multiple logical channels (for example, multiplexing one MAC SDU to multiple terminal devices, such as multiple terminal devices can be user equipment (UE) 1 and UE2, etc.), error correction through HARQ, scheduling, or priority processing, etc.

[0081] For example, the MAC layer entity can determine the scheduling output information according to channel state information (CSI), RLC data buffer status, or HARQ feedback status, etc. Among them, the channel state information can include channel quality indication (CQI). The RLC data buffer status can be used to indicate the amount of data (or data size) of the terminal device to be scheduled. The HARQ feedback status can include acknowledgment, negative-acknowledgment, or discontinuous transmission, etc. The HARQ feedback status can be used to determine whether to transmit new data or retransmit data. The scheduling output information can include: the time-domain resources, frequency-domain resources, and modulation and coding scheme (MCS) allocated by the MAC layer entity for a physical channel (such as a physical downlink shared channel (PDSCH)).

[0082] It can be understood that the MAC layer entity can determine the scheduling type according to the RLC data buffer status and / or HARQ feedback status. For example, assuming there is buffered data in the RLC layer, then the MAC layer entity can consider that there is new data to be transmitted and determine this type of scheduling as initial transmission scheduling. In addition, after the initial transmission scheduling ends, if the HARQ feedback status of the downlink transmitted data is ACK, it means that the initial transmission scheduling is successful. Further, if there is still un-scheduled RLC buffered data, then the MAC layer entity continues with the initial transmission scheduling.

[0083] If the HARQ feedback status of the downlink transmitted data is NACK or DTX, it means that the initial transmission scheduling fails, and the data needs to be re-scheduled, and this type of scheduling is determined as retransmission scheduling.

[0084] It can also be understood that the MAC layer entity can determine the MCS according to the CQI. In addition, the MAC layer entity can determine whether the currently selected MCS deviates from the actual channel quality according to the HARQ feedback status, and adjust the MCS when it is determined that there is a deviation, so that the adjusted MCS matches the actual channel quality and improves the transmission performance of downlink data.

[0085] It should be understood that for the control plane, the content encapsulated in the RRC PDU is an RRC message. The RRC message may include the capability information of the terminal device, measurement configuration information, and the master information block (MIB), etc. For details, reference can be made to the technical specifications (TS) 38.331 of 3GPP, which will not be elaborated here.

[0086] Second, blockchain (BC):

[0087] Blockchain technology can generate and store data in units of blocks, and combine them into a chain-like data structure in chronological order. Among them, all blockchain nodes in the blockchain network jointly participate in the data verification, storage, and maintenance in the blockchain. For example, a newly created block needs to be consensus-confirmed by the blockchain nodes in the blockchain network and broadcast to each blockchain node in the blockchain network to achieve synchronous storage of each blockchain node. After that, it cannot be changed or deleted. In other words, for data to be uploaded to the blockchain, not only does the data need to be published, but it also needs to obtain the consensus confirmation of the nodes in the blockchain and be stored by each node in the blockchain. It can be understood that after the data is consensus-confirmed by the nodes in the blockchain, it can be ensured that the data is accepted by all nodes on the blockchain, that is, consistency and correctness are ensured. The consensus data is stored by each node, which means that the data can avoid loss and unilateral tampering, and achieve redundancy and availability.

[0088] In addition, the smart contract (SC) technology can utilize the above characteristics of the blockchain to deploy the agreed rules or business logic (or function) in the form of an executable piece of code (such as program code) to an account address on the blockchain. When a call request (or transaction) is initiated to this address, under the constraint of the consensus mechanism, the call request will be verified in the blockchain and the code corresponding to the call request will be executed, thus ensuring the certainty and uniqueness of the execution result.

[0089] It is understandable that blockchain has the characteristics of being publicly transparent, immutable, traceable throughout the process, historically traceable, collectively maintained, and intelligently executable. It is very suitable for establishing multi-party collaborative trust in a wireless communication environment lacking trust. The integration of blockchain and wireless networks has become an important evolution direction for future communication networks. For example, blockchain can serve as a distributed trust medium to build a trust interoperability channel among device manufacturers, network operators, service providers, and a large number of terminal devices in a wireless network, solving many problems such as serious fragmentation of wireless networks, rising security risks of wireless communications, and difficulties in network supervision and privacy protection caused by the lack of a trust system in the past. Furthermore, it can empower various types of wireless network functions such as wireless resource management, terminal device access, and authentication and authorization, as well as multi-dimensional scenario applications such as cellular networks, the Internet of Things, and vehicle-to-everything networks, improving the credibility, efficiency, and security of communication networks, etc.

[0090] The following introduces some related solutions for deploying blockchain in communication networks.

[0091] Third, related solutions for deploying blockchain in communication networks:

[0092] Solution 1:

[0093] Figure 3 It is a schematic flow diagram of a method for deploying blockchain in a communication network provided by an embodiment of the present application. Figure 1 As Figure 3 shown, this method can be applied to a communication network, which includes a first network element and one or more second network elements. The main steps of this method flow mainly include:

[0094] S301. The first network element obtains first information, which includes information about the first blockchain used to carry data of the first network element and one or more second network elements.

[0095] S302. The first network element sends the first information to the one or more second network elements.

[0096] S303. The one or more second network elements update the local blockchain information according to the first information.

[0097] That is to say, Figure 3 the method shown can enable multiple network elements performing the same communication service in a communication network to use blockchain technology, meet the security requirements of communication services, and improve the security, privacy, and reliability of communication services, etc.

[0098] Solution 2:

[0099] Figure 4 It is a schematic system architecture diagram of a method for deploying blockchain in a communication network provided by an embodiment of the present application. Figure 1 AsFigure 4 As shown, the system is a blockchain system based on the data link layer, and the blockchain system includes: a first blockchain node, a second blockchain node, a first router and a second router. Among them, the first blockchain node may include: a first blockchain program and a first protocol stack, the first protocol stack may adopt a first end system routing protocol (end system routing protocol), and the first blockchain node corresponds to a first network service access point (NSAP) address identifier. The second blockchain node may include: a second blockchain program and a second protocol stack, the second protocol stack may adopt a second end system routing protocol, and the second blockchain node corresponds to a second NSAP address identifier. The first router may adopt a first intermediate system routing protocol (intermediate system routing protocol). The second router may adopt a second intermediate system routing protocol.

[0100] exist Figure 4 In the blockchain system shown, the first blockchain node can generate third data information through the first blockchain program, and use the first protocol stack to encapsulate the third data information in the first data message format to obtain the first data information.

[0101] In addition, the first blockchain node can determine the first router based on the first terminal system routing protocol and the first intermediate system routing protocol, and send the first data information to the first router. After receiving the first data information sent by the first blockchain node, the first router can determine the second router based on the first intermediate system routing protocol and the second intermediate system routing protocol, and send the first data information to the second router. After receiving the first data information forwarded by the first router, the second router can perform routing addressing on the second NSAP address identifier based on the second intermediate system routing protocol and the second terminal system routing protocol, determine the second blockchain node, and send the first data information to the second blockchain node. After receiving the first data information forwarded by the second router, the second blockchain node can use the second protocol stack to unseal the first data information in the second data message format to obtain the fourth data information, and check the fourth data information through the second blockchain program to determine the second data information, so that the second blockchain node can obtain a relatively complete second data information. In addition, since the first data information is completed in the data link layer during the transmission process, the first data information does not need to rely on protocols in other link layers, which simplifies the process of encapsulating and decapsulating the first data information, thereby reducing the performance loss of the blockchain system.

[0102] Option 3:

[0103] Figure 5 It is a schematic diagram of the system architecture for deploying blockchain in a communication network provided by an embodiment of the present application. Figure 2 As Figure 5 shown, this system architecture can utilize blockchain to manage service agreements, radio resources, and network services among mobile network operators (MNOs). Specifically, Figure 3 the system architecture shown can be divided into two layers. The upper layer is the MNO domain, and the lower layer is the network infrastructure domain. Among them, the MNO domain can include multiple MNOs, such as Figure 5 MNO#1, MNO#2, and MNO#3 in

[0104] In Figure 5 the system architecture shown, the SDN controller can decouple network operations into the control plane and the data plane to facilitate simplifying network management and programmability through software programs. For example, the SDN controller can be used to manage RAN devices and terminals, and the RAN devices can forward packets according to the rules provided by the SDN controller. In addition, the communication between the SDN controller and the forwarding device can be completed through a programmable open flow switch.

[0105] As Figure 5 shown, in the logical design, the blockchain controller is above the SDN controller, and the blockchain controller is used to verify transactions and agreements among MNOs. For example, the blockchain controller is deployed with a smart contract, which stipulates the service agreement between the MNO and the subscriber. Then, when the trigger condition is met, the smart contract will be automatically executed.

[0106] Exemplarily, Figure 5Each terminal in [the network] can send a service request to the SDN controller through the RAN device to negotiate access to the network. The SDN controller initializes and triggers the service requested by the terminal by initiating a call request (i.e., a transaction) to the account address of the smart contract on the blockchain, and then passes the service request of the terminal to the smart contract. Further, when the call request meets the trigger condition of the smart contract, the smart contract is automatically executed, that is, the transaction is broadcast to the blockchain network. Nodes for consensus verification in the blockchain network will verify the transaction, and after the transaction is confirmed by consensus, the data generated by the transaction is encapsulated into a block and appended to the blockchain, thus completing the process of being added to the blockchain.

[0107] However, in the related solutions for deploying blockchain in the above communication network, the integration of blockchain and the wireless network is only a mechanism-pieced design, and the protocol stacks in the blockchain and the wireless network are not integrated. Therefore, the credibility of blockchain cannot be fully utilized to enhance the credibility and security of data or signaling.

[0108] For example, for the above Solution 1, the deployment of blockchain in the communication network is still limited to the data at the application layer. L1-L3 in the radio access protocol stack are only used for forwarding and have no association with the blockchain. Therefore, there are still deficiencies in ensuring the credibility and security of the data source in the communication network.

[0109] For another example, for the above Solution 2, by deploying blockchain technology in the data link layer of the wired network protocol stack, the encapsulation and decapsulation of blockchain data are realized in the data link layer. In other words, the application of blockchain technology in Solution 2 only stays at the deployment level. Except for the first protocol stack newly deployed for transmitting blockchain data of the blockchain program in the data link layer, the data in other protocol layers has no direct association with the blockchain, and the function of blockchain in ensuring the credibility and security of data cannot be fully exerted.

[0110] For yet another example, for the above Solution 3, the blockchain system is integrated with the wireless network as a network element, but the deployment integration is not carried out from the perspective of the radio access protocol stack. Therefore, the data in the protocol stack cannot be directly associated and interacted with the blockchain, and the function of blockchain in ensuring the credibility and security of data cannot be fully exerted.

[0111] In summary, the embodiments of the present application provide a data transmission method and a communication device based on blockchain, which are used to provide an implementation solution for the deep integration of blockchain and the wireless network. This implementation solution can directly associate and interact the data of the protocol stack in the blockchain and the wireless network, and can fully utilize the credibility of the blockchain to enhance the credibility and security of the data in the protocol stack.

[0112] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application.

[0113] To facilitate the understanding of the embodiments of the present application, the following points are explained before introducing the embodiments of the present application.

[0114] 1. In the embodiments of the present application, for the convenience of description, when referring to numbers or indexes, continuous numbering can start from 1, can also start from 0, or can start from any parameter.

[0115] 2. The expressions "predefined", "predetermined", "preconfigured (or pre-configured)", and "protocol convention" can be used interchangeably, and the predefined can be implemented by pre-saving corresponding codes, tables or other means that can be used to indicate relevant information in a device (for example, the first device or the second device). The embodiments of the present application do not limit the specific implementation manner thereof. Among them, "saving" may mean saving in one or more memories.

[0116] 3. The "protocol" involved in the embodiments of the present application may refer to standard protocols in the communication field, for example, may include Long Term Evolution (LTE) protocol, New Radio (NR) protocol, Wireless Fidelity (Wi-Fi), and related protocols applied to future communication systems (for example, the 6th generation (6G) communication system). The embodiments of the present application do not limit this.

[0117] 4. In the embodiments of the present application, descriptions such as "when...", "in the case of...", "if", and "when" all refer to that in a certain objective situation, a device (such as the first device or the second device) will perform corresponding processing, which does not limit the time, and it is not required that the device must have a judgment action when implemented, nor does it mean other limitations exist.

[0118] 5. In the embodiments of the present application, "sending information to... (the first device)" can be understood as the destination of the information is the first device, and it can include directly or indirectly sending information to the first device. "Receiving information from... (the second device)" or "receiving information from... (the second device)" can be understood as the source of the information is the second device, and it can include directly or indirectly receiving information from the second device. The information may be subjected to necessary processing, such as format change, etc. between the source and the destination of the information sending, but the destination can understand the valid information from the source. Similar expressions in the present application can be understood similarly and will not be elaborated here.

[0119] 6. In the description of the embodiments of the present application, unless otherwise specified, "and / or" in the embodiments of the present application represents three possible relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. Moreover, "at least one (item)" or similar expressions refer to any combination of these items, including any combination of single-item (item) or multiple items (items). Additionally, for the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and "first", "second", etc. do not necessarily indicate differences. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations, or explanations.

[0120] The embodiments of the present application can be applied to an LTE system or an NR system (which can also be referred to as a fifth-generation (5G) system), a system with a hybrid network of LTE and NR, a vehicle-to-everything (V2X) system, a device-to-device (D2D) system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT) system (such as a narrow-band Internet of Things (NB-IoT) system), a Wi-Fi system, a non-terrestrial networks (NTN) system, a 6G system, and other next-generation communication systems, etc. Alternatively, the communication system can also be an open radio access network (O-RAN or ORAN), or a cloud radio access network (CRAN), without limitation.

[0121] It can be understood that the embodiments of the present application can be applied to a variety of different service scenarios, such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency services (URLLC), massive machine type communication (mMTC), immersive communication, massive communication, ubiquitous connections, integrated artificial intelligence and communication, or integrated sensing and communication, etc. To meet the further requirements for latency, reliability, and coverage in the above different service application scenarios, more flexible resource allocation is required.

[0122] In addition, the communication architecture and service scenarios described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be known to those of ordinary skill in the art that with the evolution of the communication architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0123] Figure 6 It is a schematic structural diagram of a communication system 600 provided by an embodiment of the present application. As Figure 6 shown, taking the communication system 600 including at least one access network device (such as Figure 6 610a or 610b in Figure 6 ), and at least one terminal device (such as Figure 6 620a to 620j in

[0124] In a possible implementation, the access network device in the embodiments of the present application may be a device that communicates with a terminal device. The access network device may also be referred to as a RAN device, an access node, a RAN entity, or a RAN node, etc. As Figure 6 shown, the multiple access network devices in the communication system 600 may be of the same type of nodes or different types of nodes. In some scenarios, the roles of the access network device and the terminal device are relative. For example Figure 6 the network element 620i in may be a helicopter or a drone, which may be configured as a mobile base station. For the terminal devices 620j accessing the communication system 600 through the network element 620i, the network element 620i may be the base station 610a; but for the base station 610a, the network element 620i is a terminal device. The access network device and the terminal device are sometimes both referred to as communication devices. For example Figure 6 the network elements 610a and 610b in may be understood as communication devices with base station functions, and the network elements 620a-620j may be understood as communication devices with terminal functions.

[0125] In a possible scenario, the access network device may be a transmission and reception point (TRP), a base station, a remote radio unit (RRU) of a distributed base station, or a baseband unit (BBU) (which may also be referred to as a digital unit (DU)), a broadband network gateway (BNG), an aggregation switch, a non-6GPP access device, a relay station, or an access point, etc. The access network device may be a macro base station (such as Figure 6 the network element 610a in ), a micro base station or an indoor station (such as Figure 6 the network element 610b in ), a relay node or a donor node, or a radio controller in a CRAN scenario. Optionally, the access network device may also be a server, a wearable device, a vehicle, or a vehicle-mounted device, etc. For example, the access network device in the V6X system may be a roadside unit (RSU). In addition, the access network device in the embodiments of the present application may be an eNB or eNodeB (evolutional NodeB) in LTE, a radio controller in a CRAN scenario, a base station in a 5G communication system (such as a next-generation node B (gNodeB, gNB)), or a base station in a future evolved system (such as a 6G communication system), etc., which is not specifically limited herein.

[0126] In a possible implementation, in some deployments, the gNB may include a centralized unit (CU), a DU, a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services and implementing the functions of the radio resource control (RRC) and / or packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical (PHY) layer protocols and real-time services and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the PHY layer. The AAU implements some physical layer processing functions, radio frequency processing, and functions related to active antennas. Since the information of the RRC layer will ultimately become the information of the PHY layer, or is transformed from the information of the PHY layer, thus, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or sent by the DU + AAU. It can be understood that the access network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as an access network device in the RAN, or the CU may be classified as an access network device in the CN. The embodiments of the present application do not make any limitations in this regard.

[0127] In different systems, the CU (or CU-CP and CU-UP), DU, or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU may also be referred to as an O-CU (open CU), the DU may also be referred to as an O-DU, the CU-CP may also be referred to as an O-CU-CP, the CU-UP may also be referred to as an O-CU-UP, and the RU may also be referred to as an O-RU. For the convenience of description, the embodiments of the present application use CU, CU-CP, CU-UP, DU, and RU as examples for description. Any one of the CU (or CU-CP, CU-UP), DU, and RU in the embodiments of the present application may be implemented through a software module, a hardware module, or a combination of a software module and a hardware module.

[0128] In a possible implementation, the terminal device in the embodiments of the present application may be a device for implementing wireless communication functions, such as a terminal or a chip that can be used in a terminal. Among them, the terminal may be a user equipment (UE), access terminal, terminal unit, terminal station, mobile station, mobile phone, remote station, remote terminal, mobile device, or terminal agent in a 5G network or a future evolved public land mobile network (PLMN). The access terminal may be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), a handheld device with wireless communication functions, a computing device, or other processing devices connected to a wireless modem, in-vehicle device, wearable device, VR terminal device, AR terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. In a possible implementation, the terminal device may be mobile or fixed, and this is not limited.

[0129] It can be understood that the above communication system 600 can support a variety of different service application scenarios, such as enhanced mobile broadband (eMBB), ultra-reliable & low-latency communication (URLLC), massive machine type communication (mMTC), immersive communication, massive communication, ubiquitous connections, integrated artificial intelligence and communication, or integrated sensing and communication, etc. The embodiments of this application do not make specific limitations thereto.

[0130] It should be understood that in the sidelink (SL) scenario, Figure 6 signaling and / or data can also be transmitted and received between multiple terminal devices through the air interface PC5. For example, signaling and / or data can be transmitted and received between the terminal device 620a and the terminal device 620e through the PC5 interface. In addition, in the SL scenario, the protocol stack structure corresponding to PC5 is similar to Figure 1 , and specific details can be referred to Figure 1 and its corresponding description, which will not be elaborated here.

[0131] In addition, Figure 6 the access network device in Figure 6 such as 610a or 610b in Figure 6 , and at least one terminal device connected to the access network device (such as 620a to 620j in

[0132] The embodiments of this application provide a data transmission method based on a blockchain. The execution subject of this method can be a first device. Among them, the first device can be Figure 6 the terminal device in

[0133] In a possible implementation, the first device sends first indication information and first data. The first indication information is used to indicate that the first data is blockchain data to be confirmed through consensus. The first data includes data of the RRC layer and / or transmission parameters in the data link layer for transmitting control signaling and / or service data. The first device obtains the consensus confirmation result of the first data, and the consensus confirmation result of the first data is used to indicate that the first data has passed the consensus confirmation. The first device updates the first data to the local blockchain. In this way, the first device can, through the first indication information and the first data, upload data in the protocol stack of a wireless network such as the RRC layer and / or the data link layer to the blockchain, thereby realizing direct associated interaction between the blockchain and the data in the protocol stack of the wireless network, and thus can make full use of the credibility of the blockchain to enhance the security of the data in the protocol stack. Therefore, based on the blockchain-based data transmission method provided in the embodiments of the present application, by directly associating and interacting the blockchain with the data in the protocol stack of the wireless network, the deep integration of blockchain technology and the wireless network can be realized, and thus the credibility of the blockchain can be fully utilized to enhance the security of the data in the protocol stack.

[0134] The following will be combined with Figure 7 to expand and explain the above method provided in the embodiments of the present application.

[0135] It should be understood that the signals between various devices or apparatuses, the names of the parameters in the signals, or the names of the information carried by the signals in the following embodiments of the present application are only examples, and in specific implementations, they may also be other names, and the embodiments of the present application do not make specific limitations in this regard.

[0136] It can be understood that the method provided in the embodiments of the present application can be applied to be executed by the first device and the second device.

[0137] In a possible implementation, the first device may be the terminal device described above Figure 6 , or a module or unit of the terminal device (such as a chip, a chip system, a chip circuit, or a circuit of the terminal device, etc.), and the second device may be the access network device described above Figure 6 , or a module or unit of the access network device (such as a chip, a chip system, a chip circuit, or a circuit of the access network device, etc.).

[0138] It can be understood that the first device may also be Figure 6 the access network device described above, and the second device may be Figure 6 the terminal device described above, and the embodiments of the present application do not make specific limitations in this regard.

[0139] In another possible implementation, in the SL scenario, the first device and the second device may be different terminal devices, or modules or units of different terminal devices. Among them, the air interface between the first device and the second device may be PC5.

[0140] It can be understood that the first device can operate in a high-frequency band, such as a millimeter-wave band or a terahertz band, or in a low-frequency band, such as 700 MHz, 900 MHz, 2.1 GHz, 2.6 GHz, or 3.5 GHz band, etc. It can be understood that the first device can also operate in other bands supported by the 6G system, and the embodiments of the present application do not make specific limitations in this regard.

[0141] In addition, in the embodiments of the present application, the first device and the second device are blockchain nodes in the same blockchain network. The first device or the second device can be used as a maintenance node (or called a verification node, a consensus node, etc.) in this blockchain network to verify and maintain blockchain data to be consensus-confirmed (or to be uploaded to the chain), or call requests (or called transaction requests, transaction requests, etc.). It can be understood that the first device or the second device can also be used as a broadcast node in the blockchain network to broadcast blockchain data or call requests to be consensus-confirmed in the blockchain; or, the first device or the second device can also be used as a storage node (or called a simple node, or an ordinary node) in the blockchain network to synchronize blockchain data.

[0142] For ease of understanding, the following takes the interaction between the first device and the second device as an example to detail Figure 7 the method flow shown.

[0143] Figure 7 is a schematic flow diagram of a blockchain-based data transmission method provided by the embodiments of the present application. As Figure 7 shown, the method includes the following steps:

[0144] S701. The first device sends first indication information and first data to the second device. Correspondingly, the second device receives the first indication information and the first data from the first device. Among them, the first indication information is used to indicate that the first data is blockchain data to be consensus-confirmed, and the first data includes data of the RRC layer, and / or transmission parameters in the data link layer for transmitting control signaling and / or service data.

[0145] S702. The first device obtains the consensus confirmation result of the first data.

[0146] S703. The first device updates the first data to the local blockchain.

[0147] S704. The second device obtains the consensus confirmation result of the first data.

[0148] S705. The second device updates the first data to the local blockchain.

[0149] The above steps S701 to S705 are described in detail below.

[0150] For step S701:

[0151] It can be understood that by sending the first indication information and the first data, the first device can enable the second device to determine that the first data is blockchain data to be consensus-confirmed. In this way, the second device can initiate a consensus confirmation process for the first data in the blockchain according to the participating roles in the blockchain network (such as maintenance nodes, broadcast nodes, or storage nodes), or broadcast the first data to other blockchain nodes in the blockchain network. Such other blockchain nodes can be, for example, terminal devices or access network devices other than the first device and the second device in the blockchain network. Additionally, when the second device is a storage node, the second device can cache the first data and update the local blockchain according to the consensus confirmation result of the first data.

[0152] It should be understood that "to be consensus-confirmed" can be replaced by "to be consensus" or "to be uploaded to the chain", and "blockchain data" can be replaced by "block". The embodiments of the present application do not make specific limitations on this.

[0153] It can be understood that in the embodiments of the present application, the data in the RRC layer can be an RRC PDU, and the RRC PDU can carry RRC messages. For example, RRC messages can include downlink RRC messages and uplink RRC messages. Among them, downlink RRC messages can include, for example, downlink common RRC messages, downlink dedicated RRC messages of the terminal device, system RRC messages, or paging RRC messages. Downlink common RRC messages can include, for example, RRC reconfiguration messages, RRC resume messages, security mode signaling, or UE capability reporting indications, etc. The dedicated RRC message of the terminal device can include an RRC establishment message, or an RRC rejection message, etc. System RRC messages can include system information block (system information block) X (such as SIB1 to SIB19), or MIB, etc.

[0154] In addition, uplink RRC messages can include, for example, uplink common RRC messages and uplink dedicated RRC messages of the terminal device. Among them, uplink common RRC messages can include, for example, the capability information of the terminal device, the measurement report of the terminal device, or an RRC reconfiguration complete message, etc. The embodiments of the present application do not make specific limitations on this.

[0155] In a possible implementation, the data of the RRC layer includes at least one of the following: the capability information of the terminal device, the measurement report of the terminal device, or the system information. That is to say, by performing consensus confirmation on the capability information of the terminal device, the measurement report of the terminal device, or the system information in the RRC layer, the capability information, measurement report, and global system information of the terminal device can be recorded on the chain, facilitating the development of related applications such as wireless network access authentication authorization and regulatory review of the terminal device, making the distributed identity tracking of mobile users more convenient, and improving the running stability of the blockchain established in the wireless network.

[0156] It should be understood that the system information may include SIBX and / or MIB. Table 1 shows the relevant descriptions of the capability information of the terminal device, the measurement report of the terminal device, and the system information.

[0157] Table 1

[0158]

[0159] In addition, for the recording of the capability information of the terminal device on the chain, it is convenient to carry out related applications such as wireless access identity authentication authorization and regulatory review. For the recording of the measurement report of the terminal device on the chain, it can make the distributed identity tracking of mobile users more convenient. For the recording of the system information on the chain, the global system can be recorded and managed, and thus the running stability of the blockchain established in the wireless network can be improved.

[0160] It can be understood that Table 1 is only an example, and the data of the RRC layer may also be RRC messages. The embodiments of the present application do not make specific limitations in this regard.

[0161] Next, the transmission parameters for transmitting control signaling and / or service data in the data link layer are introduced.

[0162] It should be understood that the control signaling may be, for example, control plane signaling, such as the control signaling or data carried by the above RRC message. The service data may be, for example, the service data of the user plane (or referred to as the data plane).

[0163] In a possible implementation, the transmission parameters include at least one of the following: the scheduling parameters of the MAC layer, the security parameters of the PDCP layer, or the QoS flow parameters of the SDAP layer. That is to say, by performing consensus confirmation on the scheduling parameters of the MAC layer, the security parameters of the PDCP layer, or the QoS flow parameters of the SDAP layer, the transmission parameters of each of the above protocol layers can be recorded on the chain, and thus the integrity and security of the transmission parameters of each of the above protocol layers can be guaranteed.

[0164] In a possible implementation, the scheduling parameters include at least one of the following: channel quality parameters, modulation parameters, or retransmission indication parameters. That is, by performing consensus confirmation on the scheduling parameters of the MAC layer so that the scheduling parameters are recorded on the chain, integrity protection, multi-party trusted deposit, and traceability capabilities can be provided for the scheduling parameters of the MAC layer.

[0165] It can be understood that the channel quality parameters can be used to indicate the channel state. For example, they can include Figure 2 the CQI of the MAC layer in Figure 2 , or the signal-to-noise ratio, etc. The modulation parameters can include the modulation order, modulation method, or target code rate, etc. For example, the modulation parameters can include

[0166] the MCS of the MAC layer in

[0167] The retransmission indication parameters are used to indicate the information of HARQ. For example, they indicate whether HARQ is enabled in the MAC layer, the maximum number of retransmissions of HARQ, etc.

[0168]

[0169]

[0170] It can be understood that Table 2 is only an example. The scheduling parameters of the MAC layer can also include the RLC data cache status, HARQ feedback status, precoding matrix indication, or rank indication, etc. The embodiments of the present application do not make specific limitations on this.

[0171] In a possible implementation, the security parameters include a message authentication code for integrity protection of the data within the PDCP layer, and / or an identifier of a key for encrypting the data and / or the message authentication code within the PDCP layer. That is, by performing consensus confirmation on the security parameters of the PDCP layer so that the security parameters are recorded on the chain, and then the security parameters of the PDCP layer can be combined with the security mechanisms and algorithms supporting the blockchain. On the basis of realizing integrity protection, multi-party trusted deposit, and traceability, the linkage configuration of the key environment within a certain area can also be realized, and thus the environmental security can be more sensitive to respond and make adjustments.

[0172] For example, the message authentication code can be Figure 2 the MAC-I in the PDCP layer in NRP-sess .

[0173] Exemplarily, Table 3 shows the specific content and related descriptions included in the security parameters.

[0174] Table 3

[0175]

[0176] It can be understood that the K NRP-sess ID for the PDCP layer in the SL scenario can be recorded on the blockchain, thereby achieving integrity protection, multi-party trusted evidence storage, and traceability. The traceability is not limited to between a pair of terminal devices and access network devices, and data transmitted between different terminal devices can also achieve integrity protection, multi-party trusted evidence storage, and traceability.

[0177] In addition, Table 3 is only an example. The security parameters of the PDCP layer may also include identifiers of other encryption keys in addition to K NRP-sess other than this, and the embodiments of the present application do not make specific limitations on this.

[0178] In a possible implementation manner, the QoS flow parameters include: QoS flow identifier QFI, and / or, reflection QoS flow to data radio bearer DRB mapping indication RDI. That is to say, by performing consensus confirmation on the QoS flow parameters of the SDAP layer, so that the QoS flow parameters are recorded on the blockchain, and then the QoS situation in a certain area can be uniformly and conveniently counted and analyzed through the blockchain, so as to facilitate the realization of a custom area range, and jointly record the QoS data of multiple operators, so that hot spots can be sensed, and an adjustment instruction can be issued through the blockchain to realize network QoS optimization and adjustment in a certain area or even across operators.

[0179] For example, NF network elements in the core network (such as network data analytics function (NWDAF), or operations, administration and management (OAM), etc.) can adjust the QoS policy in a certain area according to the multi-party QoS flow parameters on the blockchain, and notify the adjusted QoS policy to network elements such as the policy management function network element, access network device, and user plane function network element through the session management function network element.

[0180] For another example, a blockchain network where the first device and the second device are deployed has a smart contract for realizing QoS optimization and adjustment. After the security parameters in the first data are recorded on the blockchain, the instruction information for QoS optimization and adjustment can be obtained based on the security parameters of multiple blockchain nodes on the blockchain by calling the smart contract, and the NF network elements in the core network can be notified through the terminal device or access network device in the blockchain network, thereby realizing QoS optimization and adjustment.

[0181] Table 4

[0182] QoS flow parameters Description QFI Indicates the QoS flow to which the SDAP PDU belongs RDI Indicates whether the mapping rule of the QoS flow to the DRB needs to be updated

[0183] It can be understood that Table 4 is only an example, and the QoS flow parameters of the SDAP layer may also include other QoS flow-related parameters. For example, Figure 2 the RQI of the SDAP layer in, which is not specifically limited in the embodiments of the present application.

[0184] It can also be understood that the transmission parameters in the embodiments of the present application may also include the parameters carried by the RLC PDUs of the RLC layer, such as the segmentation parameters of the RLC layer, or the sequence numbers of SDAP SDUs, etc., which are not specifically limited in the embodiments of the present application.

[0185] In addition, the data to be consensus-confirmed included in the first data may also include data or parameters not transmitted in the PDUs of the protocol stack. For example, information that the protocol stack can schedule, such as scheduling requests, buffer status reports, or power headroom that the MAC layer can obtain; or, QoS configurations (QoS profiles), or QoS rules (QoS rules) that the SDAP layer can schedule, etc., which are not specifically limited in the embodiments of the present application.

[0186] It should be understood that the transmission parameters of the data link layer included in the above first data may be predefined by the protocol, or negotiated in advance between the first device and the second device, or indicated by the network, which is not specifically limited in the embodiments of the present application.

[0187] In a possible implementation manner, the first data is determined according to the blockchain parameter operation indication information, and the blockchain parameter operation indication information is used to indicate the data to be consensus-confirmed in the RRC layer, and / or the transmission parameters for transmitting control signaling and / or service data to be consensus-confirmed in the data link layer. That is, the first device can determine which data and / or transmission parameters are to be consensus-confirmed according to the blockchain parameter operation indication information, and then can determine the first data.

[0188] For example, the first device can determine the first data according to the blockchain parameter operation indication information. Among them, the blockchain parameter operation indication information can indicate a first operation and the parameters corresponding to the first operation. The first operation may include consensus confirmation (or called on-chain), extraction, copying, or adjusting parameter values, etc. Extraction may refer to deleting the parameter in the PDU where it is located, or extracting and putting it into the header of the PDU (for example, using the reserved bit positions in the header to carry the extracted parameters), etc., which are not specifically limited in the embodiments of the present application.

[0189] Exemplarily, the blockchain parameter operation indication information may be stored in the form of a table. As shown in Table 5, the blockchain parameter operation indication information indicates to perform consensus confirmation on MAC-I and K NRP-sess ID, and then the first device may determine that the first data includes MAC-I and K NRP-sess ID according to the blockchain operation indication information.

[0190] Table 5

[0191]

[0192] It can be understood that the blockchain parameter operation indication information may be pre-configured, or negotiated between the first device and the second device, or indicated by the network. The embodiments of the present application do not make specific limitations on this.

[0193] For example, the second device may also obtain the blockchain parameter operation indication information in advance, and then the second device may also determine the first data in the received data according to the blockchain operation indication information.

[0194] In a possible implementation manner, the protocol stack of the first device includes a blockchain sub-layer. Among them, the protocol stack of the first device includes a control plane protocol stack and / or a user plane protocol stack. That is to say, by deploying a blockchain sub-layer in the control plane protocol stack and / or the user plane protocol stack, the deep integration of the wireless network and the blockchain can be effectively promoted at the protocol layer level.

[0195] In a possible implementation manner, a blockchain sub-layer is deployed in the RRC layer and / or the data link layer of the first device. Among them, the data link layer includes the SDAP layer, the PDCP layer, the RLC layer, and the MAC layer. The blockchain sub-layer is deployed in one or more protocol layers of the SDAP layer, the PDCP layer, the RLC layer, and the MAC layer. That is to say, by deploying a blockchain sub-layer at the source of the signaling and / or transmission parameters to protect the signaling and / or transmission parameters with the security mechanism of the blockchain, the credibility and security of the signaling and / or transmission parameters can be fundamentally improved.

[0196] It should be understood that the blockchain sub-layer in the embodiments of the present application may support some functions of the blockchain, such as supporting the block structure. In addition, the blockchain sub-layer may also support at least one of the following: transaction structure, consensus algorithm, or smart contract. That is to say, the blockchain sub-layer in the embodiments of the present application may not support all functions of the blockchain, thereby reducing the deployment complexity of the blockchain sub-layer in the RRC layer and / or the data link layer.

[0197] It can be understood that the blockchain sub-layer can configure blockchain parameter operation indication information. For example, the blockchain parameter operation information can be used as a variable of the blockchain sub-layer. Then, the blockchain sub-layer entity can transparently transmit or open-process the PDUs submitted by the upper layer and the lower layer according to the blockchain parameter operation information.

[0198] For example, when the blockchain sub-layer entity determines, according to the blockchain parameter operation information, that there are parameters in the PDU header submitted by the upper layer that should be subject to consensus confirmation, the blockchain sub-layer entity can extract the PDU header and encapsulate it into a block. It can be understood that if the blockchain sub-layer entity determines, according to the blockchain parameter operation information, that there are no parameters in the PDU header submitted by the upper layer that should be subject to consensus confirmation, the blockchain sub-layer entity can transparently transmit the PDU.

[0199] For another example, the blockchain sub-layer entity can also interact with the RRC layer and / or the data link layer, and thus can obtain the parameters that should be subject to consensus confirmation.

[0200] It can be understood that the first device can obtain the parameters that should be subject to consensus confirmation according to the PDU header submitted by the upper layer and / or other protocol layer interactions. The embodiments of the present application do not make specific limitations on this.

[0201] In a possible implementation manner, the first indication information and the first data are carried by the first PDU. The first indication information is further used to indicate the protocol layer corresponding to the first data. The protocol layer corresponding to the first data includes at least one of the following: RRC layer, SDAP layer, PDCP layer, or MAC layer. That is to say, the first indication information and the first data can be sent in the form of being encapsulated into a PDU, and the protocol layer corresponding to the first data is indicated by the first indication information, so that the blockchain sub-layer on the receiving side can determine that there is blockchain data to be subject to consensus confirmation in the first PDU received this time.

[0202] For example, the first device sends the first indication information and the first data (i.e., step S701), including: the first device encapsulates the first indication information and the first data to obtain the first PDU, and sends the first PDU.

[0203] It can be understood that the PDU header of the first PDU can be used to carry the first indication information, and the SDU in the first PDU can be used to carry the first data.

[0204] In a possible implementation manner, the first PDU includes a first field, and the first field is used to carry the first indication information.

[0205] Optionally, the first PDU further includes a second field and / or a third field. The second field is used to indicate the serial number (SN) corresponding to the first PDU, and this serial number is the hash value in the blockchain message. The third field is used to indicate the size of the data area in the first PDU for carrying the block or consensus message. It can be understood that the serial number indicated by the second field can be used for blockchain verification of the first data. The third field can be used to determine where the data area where the first data is located ends, so as to better receive the first data.

[0206] In addition, the above-mentioned second field and / or third field are only optional. The serial number indicated by the second field can be maintained by the first device and the second device respectively. For example, by maintaining the order of blockchain messages to determine the hash value, or for example, the first device and the second device can pre-configure the same random seed, and then the first device and the second device can determine the same random number and determine the hash value in the blockchain message based on the random number. The embodiments of the present application do not make specific limitations on this.

[0207] In addition, the size of the data area in the first PDU for carrying the block or consensus message is fixed, and the size of this data area is pre-configured by the protocol, so it is not necessary to indicate the size of this data area through the third field either.

[0208] Exemplarily, taking the first PDU including the first field to the third field as an example, the PDU structure of the blockchain sublayer is described.

[0209] Figure 8 It is a schematic diagram of the structure of a PDU of the blockchain sublayer provided by the embodiments of the present application. As Figure 8 shown in (a) therein, the packet header of the PDU of the blockchain sublayer includes three fields, namely the first field to the third field. The blockchain sublayer SDU may include first data. It can be understood that the first device can embed the blockchain sublayer PDU into the PDU of the upper protocol layer of the blockchain sublayer to obtain the first PDU.

[0210] For example, as Figure 8 shown in (b) therein, the SDU of the blockchain sublayer further includes the packet header information of the PDU of the upper protocol layer of the blockchain sublayer. In this way, the PDU of the blockchain sublayer can be used as the packet header of the PDU of the upper protocol layer of the blockchain sublayer to obtain the first PDU, and then the first PDU is delivered to the lower protocol layer of the blockchain sublayer, so as to send the first PDU. That is to say, for the second device to receive the first data, the logical position of the blockchain sublayer of the second device should be the same as that of the blockchain sublayer of the first device. After the blockchain sublayer entity parses the first PDU, it can obtain the PDU of the upper protocol layer of the blockchain sublayer and deliver this PDU to the upper protocol layer of the blockchain sublayer.

[0211] For another example, as Figure 8 shown in (c) of Figure 8 the PDU of the blockchain sublayer shown in (a) of

[0212] It can be understood that Figure 8 the PDU of the blockchain sublayer shown in (a) of

[0213] In a possible implementation manner, the first PDU is determined according to the second PDU. The data of the RRC layer and / or the transmission parameters of the data link layer included in the first data belong to the second PDU, and the first PDU further includes the data carried by the second PDU. That is to say, the first data to be consensus-confirmed is obtained from the second PDU and sent along with the second PDU.

[0214] In another possible implementation manner, the first PDU is determined according to the second PDU. The data of the RRC layer and / or the transmission parameters of the data link layer carried by the first data belong to the second PDU, and the first PDU does not include other data carried by the second PDU except for the data of the RRC layer and / or the transmission parameters of the data link layer included in the first data. That is to say, the first PDU is not sent along with the second PDU. For example, the first PDU can be sent after the second PDU, thereby reducing the service delay.

[0215] It can be understood that the second device can also upload the data of the RRC layer and / or the transmission parameters in the data link layer for transmitting control signaling and / or service data to the blockchain, and then the second device can also send the data uploaded to the blockchain in the above-mentioned sending manner of the first PDU.

[0216] The following lists several examples to illustrate the processing of the PDU submitted by the blockchain sublayer to the upper layer and / or the lower layer.

[0217] Example A: The blockchain sublayer is deployed within the MAC layer.

[0218] Figure 9 is a schematic diagram of the protocol stack structure with the blockchain sublayer deployed within the MAC layer provided by an embodiment of the present application. As Figure 9 shown, logically, the blockchain sublayer can be deployed at the bottom within the MAC layer. In this way, the blockchain sublayer can obtain the MAC PDU, and then obtain the scheduling parameters or other information of the MAC layer according to the header in the MAC PDU.

[0219] As Figure 9As shown, assume that the first device sends service data. After the IP data packet corresponding to the service data passes through the SDAP layer, PDCP layer, RLC layer, and MAC layer in sequence, the MAC PDU#1 is obtained. After receiving the MAC PDU#1, the blockchain sub-layer entity determines, according to the blockchain parameter indication information, that the parameters to be consensus-confirmed are HARQ_I and MCS. The blockchain sub-layer entity determines that the header of the MAC PDU#1 includes HARQ_I and MCS. The blockchain sub-layer entity will take out the parameters HARQ_I and MCS in the header and assemble them into a block. The blockchain sub-layer entity can store the assembled un-verified block locally (such as a blockchain copy).

[0220] Among them, the blockchain sub-layer entity submits the MAC PDU#1 from which the parameters HARQ_I and MCS are taken out to the PHY layer (that is, continue to transmit the MAC PDU#1), and adds the above un-verified block to the MAC PDU#2 after the MAC PDU#1 as the SDU of the first PDU, so as to avoid delaying the transmission of the MAC PDU#1.

[0221] Further, the second device receives the MAC PDU#2. According to the blockchain parameter indication information and the first indication information, the second device can take out the block information in the first PDU submitted by the PHY layer of the second device, and submit the first PDU after taking out the block information to the upper protocol layer of the blockchain sub-layer. It can be understood that the blockchain sub-layer time can also add the un-verified block to the MAC PDU#1 from which the parameters HARQ_I and MCS have been taken out.

[0222] In addition, adding the above un-verified block to the MAC PDU#1 or MAC PDU#2, specifically, reference can be made to Figure 8 (b) and (c) in, which will not be elaborated here.

[0223] In addition, taking out the parameters in the header of the PDU above is only an example. It can also be to copy the parameters in the header of the PDU without changing the PDU, thereby reducing the change to the PDU and reducing the complexity of the deployment of the blockchain sub-layer.

[0224] It should be understood that the process of the second device sending data to be consensus-confirmed is similar to that of the first device sending the first data to be consensus-confirmed, which will not be elaborated here.

[0225] Example B: The blockchain sub-layer is deployed inside the PDCP layer.

[0226] Figure 10 It is a schematic diagram of the protocol stack structure in which the blockchain sub-layer is deployed inside the PDCP layer provided by an embodiment of the present application. As Figure 10As shown, logically, the blockchain sub-layer can be deployed at the bottom within the PDCP layer.

[0227] As Figure 10 shown, assume that the first device sends service data. After the IP data packet corresponding to the service data passes through the SDAP layer and the PDCP layer for processing in sequence, PDCP PDU#1 is obtained. After receiving PDCP PDU#1, the blockchain sub-layer entity determines, according to the blockchain parameter indication information, that the parameters to be consensus-confirmed are MAC-I and K NRP-sess ID. The blockchain sub-layer entity can call the relevant parameters of the PDCP layer, such as MAC-I and / or K NRP-sess ID. The blockchain sub-layer entity can combine MAC-I and / or K NRP-sess ID into a block. The blockchain sub-layer entity can store the assembled unvalidated block locally (such as a blockchain copy).

[0228] It can be understood that for the specific sending method of the above block, reference can be made to the relevant description in Figure 9 and will not be elaborated here.

[0229] Example C: The blockchain sub-layer is deployed within the SDAP layer.

[0230] Figure 11 This is a schematic diagram of the protocol stack structure with the blockchain sub-layer deployed within the SDAP layer provided by an embodiment of this application. As Figure 11 shown, logically, the blockchain sub-layer can be deployed at the bottom within the SDAP layer. In this way, the blockchain sub-layer can obtain the SDAP PDU, and then obtain the scheduling parameters or other information of the SDAP layer according to the header in the SDAP PDU.

[0231] As Figure 11 shown, assume that the first device sends service data. After the IP data packet corresponding to the service data passes through the SDAP layer for processing, SDAP PDU#1 is obtained. After receiving SDAP PDU#1, the blockchain sub-layer entity determines, according to the blockchain parameter indication information, that the parameters to be consensus-confirmed are QFI and RDI. The blockchain sub-layer entity will extract the parameters QFI and RDI in the header of SDAP PDU#1 and assemble them into a block. The blockchain sub-layer entity can store the assembled unvalidated block locally (such as a blockchain copy).

[0232] It can be understood that for the specific sending method of the above block, reference can be made to the relevant description in Figure 9 and will not be elaborated here.

[0233] Example D: The blockchain sub-layer is deployed within the SDAP layer.

[0234] Figure 12It is a schematic diagram of the protocol stack structure for deploying a blockchain sublayer inside the RRC layer provided by an embodiment of this application. As Figure 12 shown, logically, the blockchain sublayer can be deployed at the bottom inside the RRC layer. In this way, the blockchain sublayer can obtain the RRC PDU, and then obtain the RRC message according to the packet header in the RRC PDU.

[0235] As Figure 12 shown, assume that the first device sends an RRC message. After the RRC layer processes it, RRC PDU#1 is obtained. After receiving RRC PDU#1, the blockchain sublayer entity determines, according to the blockchain parameter indication information, that the data of the RRC layer that should be consensus-confirmed is the capability information and measurement report of the first device. The blockchain sublayer entity will take out the capability information and measurement report in RRC PDU#1 and assemble them into a block. The blockchain sublayer entity can store the assembled unvalidated block locally (such as a blockchain copy).

[0236] It can be understood that for the specific sending method of the above block, reference can be made to the relevant description in Figure 9 and details are not described here again.

[0237] Regarding steps S702 and S703:

[0238] It can be understood that when the first device is a storage node in the blockchain network or does not support the consensus algorithm, the first device can receive the consensus result of the first data from the blockchain node in the blockchain network it joins. Or, when the first device is a maintenance node in the blockchain network, the first device can determine the consensus confirmation result of the first data according to the votes of multiple blockchain network nodes participating in the consensus in the blockchain network regarding the first data. Or, when the first device is a node participating in the consensus vote in the blockchain network, the first device can send a vote to the maintenance node in the blockchain network and receive the consensus confirmation result of the first data sent by the broadcast node in the blockchain.

[0239] Similarly, if the second device is a broadcast node, the second device can broadcast the first data. If the second device is a storage node, the second device stores the first data. If the second device is a maintenance node, the second device can determine the consensus confirmation result of the first data according to the votes of multiple blockchain network nodes participating in the consensus in the blockchain network regarding the first data.

[0240] Regarding steps S704 and step S705:

[0241] It can be understood that after the first data is consensus-confirmed, the first data can be stored in the local blockchain (or called the local blockchain copy), which can avoid loss and unilateral tampering, and achieve redundancy and availability.

[0242] It should be understood that the blockchain parameter operation indication information in the embodiments of the present application may also indicate a second operation and the parameters corresponding to the second operation. Among them, the second operation may refer to adjusting the parameters corresponding to the second operation. For example, taking the parameter corresponding to the second operation as MCS, the blockchain parameter operation indication information may be used to indicate adding n, subtracting n, or multiplying by a certain proportional coefficient to MCS, where n may be an integer or other value, and the embodiments of the present application do not make specific limitations on this.

[0243] In addition, the blockchain parameter operation indication information may also be used to indicate performing a third operation on other parameters. For example, for Figure 8 the PDU of the blockchain sublayer shown in (a) in, the blockchain parameter operation indication information may be used to indicate operations such as taking out and storing in the first field, and the embodiments of the present application do not make specific limitations on this.

[0244] It can be understood that when the blockchain parameter operation indication information has not been uploaded to the blockchain, it is necessary to upload the blockchain parameter operation indication information to obtain consensus confirmation, and then the first device or the second device may adjust the data to be adjusted in the RRC layer and / or the transmission parameters for transmitting control signaling and / or service data to be adjusted in the data link layer.

[0245] In a possible implementation manner, Figure 7 the method shown in also includes:

[0246] S706. The first device and / or the second device obtains adjustment indication information. The adjustment indication information is used to indicate adjusting the data to be consensus-confirmed in the RRC layer and / or the transmission parameters for transmitting control signaling and / or service data to be consensus-confirmed in the data link layer. And / or, the data to be adjusted in the RRC layer and / or the transmission parameters for transmitting control signaling and / or service data to be adjusted in the data link layer.

[0247] S707. The first device and / or the second device updates the blockchain parameter operation indication information according to the adjustment indication information to obtain the updated blockchain parameter operation indication information.

[0248] That is to say, the blockchain parameter operation indication information in the blockchain can be updated according to the adjustment indication information, and thus can more flexibly adapt to the wireless network with dynamic channel changes.

[0249] It can be understood that the adjustment indication information may be initiated by a node in the blockchain network to send a call request, and after the call request passes through consensus confirmation, it is broadcast to each node in the blockchain network, and then the first device and / or the second device may receive the adjustment indication information broadcast in the blockchain network.

[0250] In addition, at least some nodes within the blockchain network may deploy a first SC for adjusting the operation instruction information of the blockchain parameters. Thus, by invoking the first SC, the first SC can be automatically executed, and then the first device and / or the second device can obtain the adjustment instruction information.

[0251] The following takes the first device deploying the first SC as an example for illustration.

[0252] In a possible implementation manner, the adjustment instruction information is the adjustment instruction information from the first SC for adjusting the operation instruction information of the blockchain parameters; Figure 7 The method shown also includes:

[0253] S708. The first device sends a first invocation request to the first blockchain node. Correspondingly, the first blockchain node receives the first invocation request from the first device. Among them, the first invocation request is used to request to invoke the first SC, and the first SC is used to adjust the operation instruction information of the blockchain parameters.

[0254] It can be understood that the first blockchain node may include: a maintenance node and / or a broadcast node within the blockchain network. In addition, the second device may be a maintenance node, a broadcast node, or a storage node within the blockchain network, and the embodiments of the present application do not make specific limitations in this regard.

[0255] S709. The first blockchain node sends a first consensus message to the first device. Correspondingly, the first device receives the first consensus message from the first blockchain node. Among them, the first consensus message is used to indicate that the first invocation request has passed the consensus confirmation.

[0256] It can be understood that the first device may execute a consensus confirmation process with multiple nodes within the blockchain network to achieve the consensus confirmation of the first invocation request. For example, when the first device is other nodes within the blockchain network except the maintenance node, the first device may receive the first consensus message from the first blockchain node.

[0257] In addition, when the first device is a maintenance node within the blockchain network, the first device may determine whether the first invocation request has passed the consensus confirmation according to the voting result of the consensus confirmation of the first invocation request.

[0258] It should be understood that in the embodiments of the present application, the second device may also deploy the first SC and execute steps S708 and S709, which will not be elaborated here.

[0259] In another possible implementation, the invocation of the first SC is triggered based on the blockchain state of the first data. That is to say, when the consensus confirmation of the first data is successful, the blockchain state (or transaction state) corresponding to the first data will change. For example, the blockchain state of the first data is that the transaction reaches a consensus, and then the first device can be triggered to invoke the first SC. In addition, triggering the invocation of the first SC through the blockchain state of the first data can reduce the process of invoking the first SC.

[0260] It can be understood that the first SC is a piece of self-executing code. Thus, when the consensus confirmation of the first invocation request passes, the first invocation request can trigger the first SC to execute automatically. Among them, the first SC can determine the adjustment indication information based on the data of the RRC layer and / or the transmission parameters of the data link layer uploaded by multiple parties on the blockchain. In this way, through the data or transmission parameters of the protocol stacks of multiple secure wireless network entities, new protocol stack functions can be empowered.

[0261] That is to say, the smart contract deployed on the blockchain can collect the uploaded data of multiple blockchain nodes, and then can perform analysis and calculation to adjust the blockchain parameter operation indication information, so that the function of the protocol stack can be affected based on the adjusted blockchain parameter indication information.

[0262] The following lists several examples to illustrate the updated blockchain parameter operation indication information.

[0263] Table 6

[0264]

[0265]

[0266] Table 6 is a comparison example of the blockchain parameter operation indication information before and after the update provided by the embodiments of the present application. Among them, some of the updated parameters can no longer continue the consensus confirmation (upload to the blockchain). For example, parameters with a relatively long change period such as K NRP-sess ID, the capability information of the terminal device, MIB, or HARQ_I, etc., can no longer be uploaded after being uploaded once, or can no longer be uploaded during the RRC connection maintenance period. In addition, some parameters (such as QFI, CQI, or measurement reports, etc.) should continue to be uploaded due to their relatively fast changes.

[0267] It can be understood that the blockchain can include the uploaded data of multiple wireless network entities, and then the ability of the blockchain to combine trusted multiple parties can be used to adjust the parameters in the protocol stack, thereby improving the transmission performance, or service QoS performance, etc., and empowering new protocol stack functions.

[0268] For example, the updated blockchain operation indication information in Table 6 indicates a decrease in HARQ_N. In this way, by reducing the maximum HARQ retransmission times, the throughput of the transmission can be improved. Additionally, the updated blockchain operation indication information can also indicate an increase in HARQ_N to improve the reliability of the transmission.

[0269] For another example, the updated blockchain operation indication information in Table 6 indicates an increase in MCS. In this way, the transmission rate can be increased or decreased. It can be understood that the first SC can determine the current channel quality based on the on-chain parameters of multiple parties on the blockchain, and when the channel quality is good, it can indicate to increase the MCS to increase the transmission rate. Additionally, for poor channel quality, the first SC can indicate to decrease the MCS to ensure the reliability of the transmission.

[0270] It can be understood that Table 6 is only an example. The updated blockchain parameter operation indication information can also indicate the specific value of the decrease in HARQ_N or the specific value of the increase in MCS. The embodiments of the present application do not make specific limitations on this.

[0271] In addition, the updated blockchain parameter operation indication information can also indicate to increase the data of the new RRC layer and / or the transmission parameters in the data link layer for transmitting control signaling and / or service data. The embodiments of the present application do not make specific limitations on this.

[0272] For example, the first SC can optimize and adjust the network QoS of the area or across operators based on the QoS parameters uploaded by multiple parties. Furthermore, the first SC can indicate to adjust the QoS configuration (QoS profile), or QoS rule (QoS rule), etc., so as to achieve the optimization and adjustment of QoS.

[0273] It can be understood that after the first device and / or the second device update the blockchain operation indication information, the first device and / or the second device can regulate the transmitted PDU according to the updated blockchain operation indication information. Hereinafter, taking the first device sending the third data as an example, an explanation will be given.

[0274] In a possible implementation manner, the updated blockchain operation indication information is used to indicate: the data to be adjusted in the RRC layer and / or the transmission parameters in the data link layer to be adjusted for transmitting control signaling and / or service data; Figure 7 The method shown also includes:

[0275] S710, the first device obtains the second data. Among them, the second data includes the data to be adjusted in the RRC layer and / or the transmission parameters in the data link layer to be adjusted for transmitting control signaling and / or service data.

[0276] It can be understood that the second data may be a PDU in the RRC layer and / or the data link layer, or the second data may be transmission parameters called by the RRC layer and / or the data link layer. The embodiments of the present application do not make specific limitations on this.

[0277] S711. The first device adjusts the second data according to the updated blockchain operation instruction information to obtain third data.

[0278] For example, Figure 9 Taking the protocol stack structure shown as an example, assuming that the MCS is carried in MAC PDU #3 and the updated blockchain operation instruction information is used to indicate that the MCS is incremented by 1, then the blockchain sublayer entity adjusts the MCS value corresponding to the MCS field in the header of MAC PDU #3 by adding 1 to obtain the third data, that is, MAC PDU #3 after changing the MCS field. In addition, the blockchain sublayer entity passes MAC PDU #3 to the physical layer.

[0279] S712. The first device sends the third data to the second device. Correspondingly, the second device receives the third data from the first device.

[0280] It can be understood that after the second device receives the third data, when the PDU carrying the third data passes through the blockchain sublayer, the blockchain sublayer entity can adjust the third data according to the updated blockchain operation instruction information in step S711, and then obtain the fourth data.

[0281] In addition, continuing with the example of step S711, the blockchain sublayer of the second device can add 1 to the MCS value +1 in the second data again.

[0282] That is to say, when the first device and / or the device transmits a PDU including the parameter corresponding to the updated blockchain parameter operation instruction information, the PDU is processed to realize the empowerment of the blockchain for the protocol stack function.

[0283] It can be understood that the second device can also execute the above steps S710 to S712, which will not be elaborated here.

[0284] It should be understood that before the first device and the second device establish a wireless connection, the first device and the second device can join the same blockchain network. In addition, when the first device establishes a wireless connection with the second device, the first device and the second device can also join the blockchain network by establishing the wireless connection, or complete the preparation work for the first device and the second device to join the blockchain network.

[0285] Next, taking the first device as the terminal device and the second device as the access network device as an example, the process of the first device accessing the second device is described.

[0286] In a possible implementation manner,Figure 7 The method shown also includes:

[0287] S713. The first device sends a first request to the second device. Correspondingly, the second device receives the first request from the first device. The first request is used to request access to the wireless network. The first request includes second indication information, and the second indication information is used to indicate at least one of the following: the identity of the terminal device, the capabilities of the terminal device, or the protocol layer of the terminal device with blockchain capabilities. The identity of the terminal device is used to determine the permission to join the blockchain network. The capabilities of the terminal device are used to determine whether the terminal device supports joining the blockchain network. The protocol layer of the terminal device with blockchain capabilities is used to determine the protocol layer corresponding to the first data.

[0288] It can be understood that the first request may be an RRC setup request, and this first request is also used to request the establishment of an RRC connection. The first request may also carry a cause value for RRC establishment.

[0289] In addition, the identity of the terminal device may include an identifier of the terminal device. The capabilities of the terminal device may include data storage capabilities, computing capabilities, and communication capabilities. For example, the data storage capabilities may include storage size, or storage rate (also known as read / write rate, read / write bandwidth, etc.). The computing capabilities may include computing frequency. The communication capabilities may include the types of network connections supported by the terminal device.

[0290] It should be understood that the second device may verify whether the first device has the permission to join the blockchain network according to the identity information of the first device. In addition, the second device may determine whether the first device supports joining the blockchain network according to the capabilities of the first device. Furthermore, the second device may determine at which layer the blockchain data of the first device is processed according to the protocol layer of the first device with blockchain capabilities.

[0291] In addition, when the second device can determine that the first device can access according to the information carried in the first request, the second device may send a first response to the first device to indicate the access resources and blockchain information to the first device.

[0292] S714. The second device sends a first response to the first device. Correspondingly, the first device receives the first response from the second device. The first response includes third indication information, and the third indication information is used to indicate the protocol layer of the access network device with blockchain capabilities.

[0293] It can be understood that the first response may be an RRC establishment message, and the first response may also include configuration information of the SRB1 resource. In addition, the first device can determine at which layer the blockchain data of the first device is processed through the third indication information.

[0294] It should be understood that asFigures 9 to 12 As shown, the first request in step S713 and the first response in step S714 are interacted at the RRC layer, and the protocol layers with blockchain capabilities between the first device and the second device are peer-to-peer. In addition, in the embodiments of the present application, the protocol layers with blockchain capabilities between the first device and the second device may be non-peer-to-peer. For example, the protocol layer with blockchain capabilities of the first device may be at the MAC layer, and the protocol layer with blockchain capabilities of the second device may be at the RLC layer. The embodiments of the present application do not make specific limitations on this.

[0295] That is to say, when the first device and the second device establish a connection, relevant information about the blockchain between the two can be interacted through the first request and the first response, so as to facilitate the trusted interaction between the blockchain and the protocol stack.

[0296] Since in the embodiments of the present application, the first device can upload data in the protocol stack of the wireless network such as the RRC layer or the data link layer to the blockchain through the first indication information and the first data, thereby realizing the direct associated interaction between the blockchain and the data in the protocol stack of the wireless network, and thus the trustworthiness of the blockchain can be fully utilized to enhance the security of the data in the protocol stack. Therefore, based on the blockchain-based data transmission method provided by the embodiments of the present application, the direct associated interaction between the blockchain and the data in the protocol stack of the wireless network can be achieved, realizing the deep integration of blockchain technology and the wireless network, and thus the trustworthiness of the blockchain can be fully utilized to enhance the security of the data in the protocol stack.

[0297] The above mainly introduces the solution provided by the embodiments of the present application from the perspective of the interaction between the first device and the second device. Correspondingly, the embodiments of the present application also provide a communication device, which is used to implement the above various methods. The communication device may be the first device in the above method embodiments, or a device including the above first device, or a component applicable to the first device; or, the communication device may be the second device in the above method embodiments, or a device including the above second device, or a component applicable to the second device. It can be understood that in order to implement the above functions, the communication device includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0298] Embodiments of the present application can divide functional modules of a communication device according to the above method embodiments. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, merely a logical function division, and there can be other division methods in actual implementation.

[0299] Taking the communication device as the first device or the second device in the above method embodiments as an example, Figure 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application. As Figure 13 shown, the communication device 1300 includes: a processing module 1301 and a transceiver module 1302. Among them, the processing module 1301 is used to execute the processing function of the first device or the second device in the above method embodiments. The transceiver module 1302 is used to execute the transceiver function of the first device or the second device in the above method embodiments.

[0300] Among them, all relevant contents of each step involved in the above method embodiments can be cited in the function descriptions of the corresponding functional modules, and will not be elaborated here.

[0301] Since the communication device 1300 provided in this embodiment can execute the above blockchain-based data transmission method, the technical effects it can obtain can refer to the above method embodiments and will not be elaborated here.

[0302] In a possible design, the transceiver module 1302 can include a receiving module and a sending module ( Figure 13 not shown in the figure). Among them, the transceiver module is used to implement the sending function and the receiving function of the communication device 1300.

[0303] In a possible design, the communication device 1300 can further include a storage module ( Figure 13 not shown in the figure), and the storage module stores programs or instructions. When the processing module 1301 executes the program or instruction, the communication device 1300 can execute Figures 6 to 12 the functions of the first device or the second device in any of the methods shown in the figure.

[0304] It should be understood that the processing module 1301 involved in the communication device 1300 can be implemented by a processor or processor-related circuit components, and can be a processor or a processing unit; the transceiver module 1302 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or a transceiver unit.

[0305] Exemplarily, Figure 14FIG. 0 is a schematic structural diagram of another communication device provided by an embodiment of the present application. The communication device may be a first device or a second device, or may be a chip (system), or other components or assemblies that can be disposed in the first device or the second device. As Figure 14 shown, the communication device 1400 may include a processor 1401. In a possible design, the communication device 1400 may further include a memory 1402 and / or a transceiver 1403. The processor 1401 is coupled to the memory 1402 and the transceiver 1403, such as by a communication bus.

[0306] Next, the components of the communication device 1400 will be specifically introduced in conjunction with Figure 14 :

[0307] The processor 1401 is the control center of the communication device 1400, and may be a single processor or a collective term for multiple processing elements. For example, the processor 1401 is one or more central processing units (CPUs), or may be an application specific integrated circuit (ASIC), or may be one or more integrated circuits configured to implement the embodiments of the present application, such as: one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).

[0308] In a possible design, the processor 1401 may execute various functions of the communication device 1400 by running or executing software programs stored in the memory 1402 and calling data stored in the memory 1402.

[0309] In a specific implementation, as an embodiment, the processor 1401 may include one or more CPUs, such as Figure 14 the CPU0 and CPU1 shown in

[0310] In a specific implementation, as an embodiment, the communication device 1400 may also include multiple processors, such as Figure 14 the processor 1401 and the processor 1404 shown in

[0311] Among them, the memory 1402 is used to store the software program for executing the solution of this application, and is controlled by the processor 1401 for execution. The specific implementation method can refer to the above method embodiment and will not be elaborated here.

[0312] In a possible design solution, the memory 1402 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1402 can be integrated with the processor 1401, or can exist independently and be coupled to the processor 1401. The embodiments of this application do not make specific limitations on this.

[0313] The transceiver 1403 is used for communication with other communication devices. For example, if the communication device 1400 is the first device, the transceiver 1403 can be used for communication with the second device, or the first blockchain node, etc. For another example, if the communication device 1400 is the second device, the transceiver 1403 can be used for communication with the first device, or the first blockchain node, etc.

[0314] In a possible design solution, the transceiver 1403 can include a receiver and a transmitter ( Figure 14 not shown separately). Among them, the receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

[0315] In a possible design solution, the transceiver 1403 can be an input / output interface or an interface circuit for inputting and / or outputting signals.

[0316] In a possible design solution, the transceiver 1403 can be integrated with the processor 1401, or can exist independently and be coupled to the processor 1401. The embodiments of this application do not make specific limitations on this.

[0317] It should be noted that Figure 14The structure of the communication device 1400 shown does not constitute a limitation on the communication device. An actual communication device may include more or fewer components than shown, or combine certain components, or have a different component arrangement.

[0318] In addition, the communication device 1400 can execute the above information transmission method. Therefore, the technical effects it can obtain can refer to the above method embodiments and will not be elaborated here.

[0319] In a possible implementation manner, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program or instruction is stored. When the computer program or instruction is executed by a computer, the functions of the above method embodiments are implemented.

[0320] In a possible implementation manner, an embodiment of the present application further provides a computer program product. When the computer program product is executed by a computer, the functions of the above method embodiments are implemented.

[0321] In a possible implementation manner, an embodiment of the present application further provides a communication system, which includes the first device and the second device described in the above method embodiments.

[0322] In a possible implementation manner, the communication system further includes the first blockchain node described in the above method embodiments.

[0323] In a possible implementation manner, an embodiment of the present application further provides a communication method, which includes the method described in any of the above method embodiments or any of its implementation manners.

[0324] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more media integrated therein. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium, or a semiconductor medium (such as a solid-state drive (SSD)), etc.

[0325] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present application.

[0326] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0327] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in an electrical, mechanical, or other form.

[0328] The unit described as a separation component may or may not be physically separated. The component shown as a unit may or may not be a physical unit, that is, it may be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0329] In addition, in each embodiment of the present application, each functional unit may be integrated in a processing unit, may exist physically separately for each unit, or two or more units may be integrated in one unit.

[0330] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs.

[0331] Although the present application has been described in conjunction with various embodiments herein, however, in the process of implementing the claimed present application, those skilled in the art can understand and implement other variations of the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0332] Although the present application has been described in connection with specific features and their embodiments, it will be apparent that various modifications and combinations can be made thereto without departing from the scope of the present application. Accordingly, the present specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these changes and modifications.

Claims

1. A data transmission method based on blockchain, characterized in that, The method includes: Sending first indication information and first data, where the first indication information is used to indicate that the first data is blockchain data to be consensus-confirmed, and the first data includes data of the Radio Resource Control (RRC) layer, and / or transmission parameters in the data link layer for transmitting control signaling and / or service data; Obtaining the consensus confirmation result of the first data, where the consensus confirmation result of the first data is used to indicate that the first data has passed the consensus confirmation; Updating the first data to the local blockchain.

2. The method according to claim 1, wherein The method further includes: Sending a first request, where the first request is used to request access to a wireless network, and the first request includes second indication information, where the second indication information is used to indicate at least one of the following: the identity of the terminal device, the capabilities of the terminal device, or the protocol layer of the terminal device with blockchain capabilities. The identity of the terminal device is used to determine the permission to join the blockchain network, the capabilities of the terminal device are used to determine whether the terminal device supports joining the blockchain network, and the protocol layer of the terminal device with blockchain capabilities is used to determine the protocol layer corresponding to the first data; Receiving a first response, where the first response includes third indication information, and the third indication information is used to indicate the protocol layer of the access network device with blockchain capabilities.

3. A data transmission method based on blockchain, characterized in that, The method includes: Receiving first indication information and first data, where the first indication information is used to indicate that the first data is blockchain data to be consensus-confirmed, and the first data includes data of the Radio Resource Control (RRC) layer, and / or transmission parameters in the data link layer for transmitting control signaling and / or service data; Obtaining the consensus confirmation result of the first data, where the consensus confirmation result of the first data is used to indicate that the first data has passed the consensus confirmation; Updating the first data to the local blockchain.

4. The method according to claim 3, wherein The method further includes: Receiving a first request, where the first request is used to request access to a wireless network, and the first request includes second indication information, where the second indication information is used to indicate at least one of the following: the identity of the terminal device, the capabilities of the terminal device, or the protocol layer of the terminal device with blockchain capabilities. The identity of the terminal device is used to determine the permission to join the blockchain network, the capabilities of the terminal device are used to determine whether the terminal device supports joining the blockchain network, and the protocol layer of the terminal device with blockchain capabilities is used to determine the protocol layer corresponding to the first data; Sending a first response, where the first response includes third indication information, and the third indication information is used to indicate the protocol layer of the access network device with blockchain capabilities.

5. The method according to any one of claims 1-4, characterized in that, The transmission parameters include at least one of the following: scheduling parameters of the Medium Access Control (MAC) layer, security parameters of the Packet Data Convergence Protocol (PDCP) layer, or Quality of Service (QoS) flow parameters of the Service Data Adaptation Protocol (SDAP) layer.

6. The method according to claim 5, wherein The scheduling parameters include at least one of the following: channel quality parameters, modulation parameters, or retransmission indication parameters.

7. The method according to claim 5 or 6, characterized in that, The security parameters include a message authentication code for integrity protection of data within the PDCP layer, and / or an identifier of a key for encrypting the data within the PDCP layer and / or the message authentication code.

8. The method according to any one of claims 5 to 7, characterized in that, The QoS flow parameters include: a QoS flow identifier QFI, and / or a reflection QoS flow to data radio bearer DRB mapping indication RDI.

9. The method according to any one of claims 1-8, characterized in that, The data of the RRC layer includes at least one of the following: capability information of the terminal device, a measurement report of the terminal device, or system information.

10. The method according to any one of claims 1-9, characterized in that The first indication information and the first data are carried by a protocol data unit PDU of a first protocol layer, and the first indication information is further used to indicate the protocol layer corresponding to the first data, and the protocol layer corresponding to the first data includes at least one of the following: the RRC layer, the SDAP layer, the PDCP layer, or the MAC layer.

11. The method according to any one of claims 1 to 10, characterized in that, The first data is determined according to blockchain parameter operation indication information, and the blockchain parameter operation indication information is used to indicate data to be consensus-confirmed in the RRC layer, and / or transmission parameters for transmitting control signaling and / or service data to be consensus-confirmed in the data link layer.

12. The method according to claim 11, wherein The method further includes: Obtaining adjustment indication information, where the adjustment indication information is used to indicate adjustment of data to be consensus-confirmed in the RRC layer, and / or transmission parameters for transmitting control signaling and / or service data to be consensus-confirmed in the data link layer; and / or The data to be adjusted in the RRC layer, and / or the transmission parameters for transmitting control signaling and / or service data to be adjusted in the data link layer; Updating the blockchain parameter operation indication information according to the adjustment indication information to obtain updated blockchain parameter operation indication information.

13. The method according to claim 12, characterized in that, The adjustment indication information is adjustment indication information from a first smart contract SC for adjusting the blockchain parameter operation indication information; the method further includes: Sending a first call request, where the first call request is used to request calling the first SC, and the first SC is used to adjust the blockchain parameter operation indication information; Receiving a first consensus message, where the first consensus message is used to indicate that the first call request has passed the consensus confirmation.

14. The method according to claim 12 or 13, characterized in that, The updated blockchain operation indication information is used to indicate: the data to be adjusted in the RRC layer, and / or the transmission parameters for transmitting control signaling and / or service data to be adjusted in the data link layer; the method further includes: Obtaining second data, where the second data includes the data to be adjusted in the RRC layer, and / or the transmission parameters for transmitting control signaling and / or service data to be adjusted in the data link layer; Adjusting the second data according to the updated blockchain operation indication information to obtain third data; Sending the third data.

15. A communication device, characterized in that, The communication device includes a module or unit for executing the method according to any one of claims 1-2, 5-14, or includes a module or unit for executing the method according to any one of claims 3-4, 5-14.

16. A communication device, characterized in that, The communication device includes a processor, and the processor is configured to cause the communication device to execute the method according to any one of claims 1-2, 5-14 through logic circuits and / or by executing instructions, or to cause the communication device to execute the method according to any one of claims 3-4, 5-14.

17. The communication device according to claim 16, wherein The communication device further includes a memory, and the memory is configured to store the instructions.

18. The communication device according to claim 16 or 17, characterized in that, The communication device further includes a communication interface, and the communication interface is configured to input and / or output signaling and / or data.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions, and when the instructions are run by a processor, the method according to any one of claims 1-2, 5-14 is implemented, or the method according to any one of claims 3-4, 5-14 is implemented.

20. A computer program product, characterized in that, The computer program product includes instructions, and when the instructions are run on a computer, the computer is caused to execute the method according to any one of claims 1-2, 5-14, or the computer is caused to execute the method according to any one of claims 3-4, 5-14.

21. A communication system, characterized in that, The communication system includes a first device and a second device, the first device is configured to execute the method according to any one of claims 1-2, 5-14, and the second device is configured to execute the method according to any one of claims 3-4, 5-14.

Images