Digital coding method based on alliance chain, MEC server and user terminal

Abstract

The application provides a digital code assignment method based on a consortium chain, an MEC server and a user terminal. The MEC server is a node of the consortium chain, a master node of the consortium chain is provided with a consortium chain management cloud platform, the nodes of the consortium chain are managed, and a unified API interface is provided for the user terminal. The user sends a digital code application request to the MEC server through the user terminal, the MEC server generates a target digital code corresponding to a target application program for the user according to the received digital code application request, generates a ledger for the target digital code, randomly sends the ledger to at least three consortium chain nodes for backup, and sends the target digital code to the target user. A unified code assignment platform is provided for each application program through the consortium chain, the workload of the application party is reduced, and the security of the digital code is effectively improved through the backup to provide anti-tampering security measures.

Description

Technical Field

[0001] This application relates to information technology, and more particularly to a digital coding method based on a consortium blockchain, an MEC server, and a user terminal. Background Technology

[0002] Information technology refers to the technology used to acquire, process, store, transform, display, and transmit text, numerical, image, and sound information with the support of computer and communication technologies. In general, information technology studies how to acquire, process, transmit, and use information. Digital codes, as carriers of information, can achieve functions such as information processing and transmission with the help of computer and communication technologies.

[0003] Digital codes are widely used in people's work and daily life, such as health codes and enterprise codes. Currently, the assignment of digital codes is completed by the independent platforms of each application. In other words, applications that require digital codes can generate the corresponding digital codes according to their needs.

[0004] However, the independent generation of digital codes by each application platform increases the workload for application developers, and the security of the digital codes cannot be guaranteed. Summary of the Invention

[0005] This application provides a digital coding method, MEC server, and user terminal based on a consortium blockchain to solve the problem that the security of digital codes generated by application-independent coding platforms cannot be guaranteed.

[0006] Firstly, this application provides a digital coding method based on a consortium blockchain, applied to a mobile edge computing (MEC) server. The MEC server acts as a node in the consortium blockchain, and the master node of the consortium blockchain deploys a consortium blockchain management cloud platform. This cloud platform manages the nodes of the consortium blockchain and provides a unified application programming interface (API) for user terminals. The method includes:

[0007] Receive a digital code application request sent by a user terminal, wherein the digital code application request includes the user's identity information and the target application's information;

[0008] According to the digital code application request, a target digital code corresponding to the target application is generated for the user, and a ledger is generated for the target digital code. The ledger is randomly sent to at least three consortium blockchain nodes for backup. The ledger includes the time when the target digital code was generated, the user information corresponding to the target digital code, and the content of the target digital code.

[0009] The target digital code is sent to the user terminal.

[0010] Optionally, sending the target digital code to the user terminal includes:

[0011] Receive a digital code request sent by the user terminal, wherein the digital code request includes information about the target application and the user's account information;

[0012] According to the digital code request, a target digital code corresponding to the target application is selected for the user from the saved digital codes, and the target digital code is sent to the user terminal.

[0013] After sending the target digital code to the user terminal, the method further includes:

[0014] Receive a digital code verification request sent by the user terminal, wherein the digital code verification request includes information about the target digital code;

[0015] The information of the target digital code is matched with the information of the digital code stored locally to obtain the verification result;

[0016] The verification result is then sent to the user terminal, and the verification result is used to indicate whether the target numeric code is valid.

[0017] Optionally, after sending the digital code to the user terminal, the method further includes:

[0018] Receive a digital code modification request sent by the user terminal, wherein the digital code modification request includes the content that the user needs to modify;

[0019] The content of the user's target numeric code is modified and updated according to the numeric code modification request.

[0020] Optional, also includes:

[0021] The deregistered digital code is recycled, and the deregistered digital code includes the corresponding user's historical data;

[0022] Receive a query request sent by the first node of the consortium blockchain, the query request including the account information of the user to be queried;

[0023] Query the historical data of the user to be queried according to the query request;

[0024] The system returns a response message corresponding to the query request to the first node of the consortium blockchain. The response message includes the historical data of the user to be queried.

[0025] Secondly, this application provides a digital coding method based on a consortium blockchain, applied to a user terminal, including:

[0026] Send a digital code request to the mobile edge computing (MEC) server. The digital code request includes information about the target application and the user's identity information.

[0027] The system receives a target digital code sent by the MEC server. The target digital code is generated by the MEC server based on the digital code application request and is used by the user in the target application.

[0028] Optionally, receiving the target digital code sent by the MEC server includes:

[0029] Obtain the information of the target application selected by the user, and send a digital code request to the MEC server, wherein the digital code request includes the information of the target application;

[0030] The system receives a response to the digital code request sent by the MEC server, the response including the target digital code requested by the user.

[0031] Optional, also includes:

[0032] Send a digital code verification request to the MEC server. The digital code verification request includes information about the target digital code and is used to request verification of whether the target digital code is valid.

[0033] The system receives a verification result sent by the MEC server, which indicates whether the target numeric code is valid.

[0034] Optional, also includes:

[0035] A digital code modification request is sent to the MEC server, the digital code modification request including the content that the user needs to modify.

[0036] Thirdly, this application provides a mobile edge computing (MEC) server, wherein the MEC server serves as a node in a consortium blockchain, the master node of which deploys a consortium blockchain management cloud platform, the consortium blockchain management cloud platform manages the nodes of the consortium blockchain, and provides a unified application programming interface (API) for user terminals, including:

[0037] The receiving module is used to receive a digital code application request sent by a user terminal, wherein the digital code application request includes the user's identity information and the target application information;

[0038] The generation module is used to generate a target digital code corresponding to the target application for the user according to the digital code application request, generate a ledger for the target digital code, and randomly send the ledger to at least three consortium blockchain nodes for backup. The ledger includes the time of generation of the target digital code, the user information corresponding to the target digital code, and the content of the target digital code.

[0039] The sending module is used to send the target digital code to the user terminal.

[0040] Fourthly, this application provides a user terminal, including:

[0041] The sending module is used to send a digital code application request to the mobile edge computing (MEC) server. The digital code request includes information about the target application and the user's identity information.

[0042] The receiving module is used to receive the target digital code sent by the MEC server. The target digital code is generated by the MEC server according to the digital code application request, and the target digital code is used by the user in the target application.

[0043] Fifthly, this application provides a mobile edge computing (MEC) server, comprising: a processor, and a memory communicatively connected to the processor;

[0044] The memory stores computer-executed instructions;

[0045] The processor executes computer execution instructions stored in the memory to implement the method as described in the first aspect.

[0046] Sixthly, this application provides a user terminal, including: a processor, and a memory communicatively connected to the processor;

[0047] The memory stores computer-executed instructions;

[0048] The processor executes computer execution instructions stored in the memory to implement the method as described in the second aspect.

[0049] In a seventh aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the service scheduling method as described in the first or second aspect.

[0050] Eighthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect or the second solution.

[0051] This application provides a digital code assignment method based on a consortium blockchain, an MEC server, and a user terminal. The MEC server acts as a node in the consortium blockchain, whose master node deploys a consortium blockchain management cloud platform to manage the nodes and provide a unified API interface for the user terminal. Users send digital code application requests to the MEC server through their user terminals. Based on the received digital code application requests, the MEC server generates a target digital code corresponding to the target application for the user, generates a ledger for the target digital code, randomly sends this ledger to at least three consortium blockchain nodes for backup, and then sends the target digital code to the target user. By providing a unified code assignment platform for various applications through the consortium blockchain, the workload of application developers is reduced, and the backup provides tamper-proof security measures, effectively improving the security of the digital codes. Attached Figure Description

[0052] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0053] Figure 1 This is a schematic diagram illustrating one application scenario to which this application applies;

[0054] Figure 2 This is a schematic diagram of the basic architecture of the consortium blockchain node in this application;

[0055] Figure 3 A flowchart illustrating a digital coding method based on a consortium blockchain, provided in Embodiment 1 of this application;

[0056] Figure 4 A flowchart illustrating a digital coding method based on a consortium blockchain, provided in Embodiment 2 of this application;

[0057] Figure 5 A signaling flowchart for a digital coding method based on a consortium blockchain provided in Embodiment 3 of this application;

[0058] Figure 6 This is a schematic diagram of the structure of a mobile edge computing (MEC) server provided in Embodiment 4 of this application;

[0059] Figure 7 This is a schematic diagram of the structure of a user terminal provided in Embodiment 5 of this application;

[0060] Figure 8 This is a schematic diagram of the structure of a mobile edge computing (MEC) server provided in Embodiment Six of the present invention;

[0061] Figure 9 This is a schematic diagram of the structure of a user terminal provided in Embodiment 7 of the present invention.

[0062] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0063] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0064] Digital codes are widely used in people's work and daily lives, such as health codes and enterprise codes. Currently, the assignment of digital codes is handled by independent platforms for each application; that is, applications that require digital codes can generate the corresponding codes according to their needs. As the types of applications increase, the scenarios requiring code assignment also increase. The lack of a unified digital code management platform and the fact that each application's independent platform generates digital codes increases the workload for application developers and compromises the security of the digital codes. Furthermore, achieving data interoperability between digital codes generated by different applications is quite difficult.

[0065] Therefore, this application provides a digital coding method, MEC server, and user terminal based on consortium blockchain. Through the consortium blockchain, a unified digital code management platform is provided for various applications, providing reliable and secure digital codes for each application, while reducing the workload of application users. The digital code can be a QR code or barcode, etc.

[0066] The following is an explanation of the terms used in this application:

[0067] Consortium blockchain: A consortium blockchain is between a private blockchain and a public blockchain. It is a blockchain in which multiple organizations or institutions participate. That is, it is a blockchain jointly managed by multiple institutions or institutions. Each organization or institution manages one or more nodes. Data in a consortium blockchain can only be accessed by the institutions or institutions on the nodes.

[0068] MEC: Mobile Edge Computing (MEC) servers are edge servers deployed by operators close to mobile devices to provide services to users nearby. This greatly reduces the latency of the network responding to user requests and also reduces the possibility of network congestion in the transmission network and core network, which can greatly improve the user's service quality experience.

[0069] Figure 1 This is a schematic diagram illustrating one application scenario to which this application applies. For example... Figure 1 As shown, the nodes in consortium blockchain 10 include MEC server 101 and MEC server 102, i.e., MEC server 101 and MEC server 102 serve as nodes of consortium blockchain 10. Consortium blockchain 10 may have more nodes, not shown in the figure. The master node of the consortium blockchain deploys a consortium blockchain management cloud platform to manage the various nodes of the consortium blockchain and provide a unified API interface for the user terminals of user terminal 20. User terminal 20 consists of user terminal 103 and user terminal 104, each with at least one application installed. User terminal 20 may have more user terminals, not shown in the figure. User terminal 20 communicates with the nodes of consortium blockchain 10 via the Internet. Each node of consortium blockchain 10 deploys a digital code management platform to generate digital codes corresponding to the applications in the user terminals and manage these digital codes. The infrastructure of each node in consortium blockchain 10 in this application includes an application layer 201, a contract layer 202, a consensus layer 203, a network layer 204, and a data layer 205, as shown below. Figure 2 As shown.

[0070] The digital code management platform is deployed in the user-facing application layer 201. It includes a digital code generation module, a verification module, a statistics module, a service module, a selection module, and a recycling module. The generation module generates digital codes for users. The verification module verifies the information of the digital codes to confirm their authenticity. The statistics module tracks the assignment status and usage frequency of digital codes. The service module modifies the content of existing digital codes. The selection module helps users choose target digital codes corresponding to specific applications. The recycling module recycles deactivated digital codes. The digital code management platform in application layer 201 completes the code assignment process and manages the functions of the digital codes. For the specific implementation of each module, please refer to Embodiment 1.

[0071] The contract layer 202 mainly includes script code, algorithm mechanisms, and smart contracts, which are used to manage the legality of digital codes after they are assigned to users, especially to manage the security and legality of all codes.

[0072] Consensus layer 203 includes various consensus mechanisms, provides consensus on block data storage among nodes, and storage rules for backup blocks.

[0073] Network layer 204 provides rules for broadcasting and network services in the consortium blockchain, as well as data transmission between nodes.

[0074] Data layer 205 primarily describes the physical form of blockchain technology, providing underlying data services for consortium blockchains. It offers data computation for blocks and related data services for block headers. For example, timestamps ensure that each block is linked in chronological order, and hash functions ensure that transaction information is not tampered with.

[0075] The technical solutions of this application and how they solve the aforementioned technical problems are described in detail below with specific embodiments. These specific embodiments may exist independently or in combination with each other. Identical or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0076] refer to Figure 3 , Figure 3 The following is a flowchart illustrating a digital coding method based on a consortium blockchain, which is provided in Embodiment 1 of this application. This method can be executed by an MEC server, which is a node of the consortium blockchain. The method includes the following steps.

[0077] S301. Receive a digital code application request sent by a user terminal. The digital code application request includes the user's identity information and the target application information.

[0078] When a user needs to apply for a target digital code, the user terminal sends a digital code application request to the MEC server. This request requests the MEC server to allocate a digital code to the user. The user terminal can send this request through the API interface provided by the MEC server. The digital code application request includes the user's identity information and the target application's information. The user's identity information includes the user's name and identification document number, while the target application information includes the application name and version number.

[0079] S302. Generate a target digital code corresponding to the target application for the user based on the digital code application request, generate a ledger for the target digital code, and randomly send the ledger to at least three consortium blockchain nodes for backup.

[0080] The MEC server generates a target digital code corresponding to the target application for the user based on the user's identity information and the target application information in the digital code application request. The target digital code can be a QR code or a barcode. This application does not restrict the type of digital code.

[0081] After the MEC server generates the target digital code, to ensure its security and prevent tampering, it generates a ledger containing the code's generation time, corresponding user information, and other relevant details. This ledger is then randomly sent to at least three consortium blockchain nodes (MEC servers on at least three consortium blockchains) for backup. While normal modification of the target digital code modifies the backup ledgers on other consortium blockchain nodes, unauthorized tampering with the target digital code on the MEC server prevents malicious modification by preserving the ledger information.

[0082] S303. Send the target digital code to the user terminal.

[0083] The MEC server sends the generated target digital code to the user terminal, which stores the digital code for user use. Specifically, the MEC server can request the user terminal's information based on the digital code and send the target digital code to the user terminal immediately after generating the data code.

[0084] Optionally, the MEC server can also store the target numeric code after generating it. When a user needs to use the numeric code, the user terminal sends a numeric code request to the MEC server. The numeric code request is used to request the MEC server to select a target numeric code for the user. The numeric code request can be sent by the user terminal through the API interface provided by the MEC server. The numeric code request includes information about the target application and the user's account information. It can be understood that the target numeric code requested by the user is used in the target application on the user terminal.

[0085] The MEC server determines the user's PIN based on the user's account information in the received PIN request, then selects the target PIN for the user based on the target application information, and finally sends a PIN response to the user terminal, including the requested target PIN. The MEC server can send the target PIN to the user terminal as an image. It can be understood that the MEC server can store one or more PINs for a user; one PIN corresponds to one application, or multiple PINs can correspond to one application, meaning multiple functions within an application correspond to specific PINs. For example, a payment function corresponds to a payment code, and a collection function corresponds to a collection code. It should be noted that for applications that can have multiple PINs, the PIN request in step S301 can also include the target application's function information, instructing the MEC server to generate a PIN related to that function. Furthermore, the PIN request also includes the target application's function information, instructing the MEC server to select the appropriate PIN for the target user.

[0086] Optionally, after the MEC server sends the target digital code to the user terminal, when the user uses the target digital code through the target application, the validity of the target digital code needs to be verified first. For example, when a user uses a payment code to make a payment, the payment code needs to be scanned and verified. The MEC server can receive digital code verification requests sent by the user terminal. The digital code verification request can be sent by the user terminal through the API interface provided by the MEC server. This request includes information about the target digital code, namely the user information corresponding to the target digital code and related content of the digital code. The MEC server matches the information of the target digital code with the information of digital codes stored locally according to the digital code verification request, and obtains a verification result, that is, it determines whether the information of the target digital code is consistent with the information of digital codes stored locally. Then, it sends the verification result to the user terminal. The verification result is used to indicate the validity of the target digital code. That is, when the match is successful, the verification result indicates that the target digital code is valid; when the match is unsuccessful, the matching message indicates that the target digital code is invalid, and the user can initiate verification again.

[0087] Optionally, after the MEC server sends the target numeric code to the user terminal, when the user needs to modify the content of the target numeric code, the user terminal sends a numeric code modification request to the MEC server. This request requests the MEC server to modify the relevant content of the target numeric code. The numeric code modification request can be sent by the user terminal through the API interface provided by the MEC server. The request includes the content that the user needs to modify; for example, the content of the target numeric code is data in a table, and the user can modify any value in the table. The MEC server modifies the content of the target numeric code according to the content in the numeric code modification request, and saves and updates the content. Modifying the content of the target numeric code can be an addition or deletion operation. Optionally, the MEC server can send the updated target numeric code to the user terminal, or the MEC server can send the updated target numeric code to the user terminal only when the user needs to use the numeric code.

[0088] Optionally, at preset intervals, such as once a week or once a month, the MEC server can count the number of digital codes generated during that period, as well as the number of times each digital code is used, to obtain the usage frequency of the digital codes. It can also count the number of digital codes by type, such as the number of health codes generated and the number of enterprise codes generated, or count the usage time of each digital code, etc.

[0089] It should be noted that the data collected by the MEC server mentioned above is the data collected by one node in the consortium blockchain. The MEC server needs to send the collected data to the master node MEC server of the consortium blockchain. The master node's consortium blockchain management cloud platform can collect data from each node, which can provide a reference for the subsequent development of more functions.

[0090] The MEC server can also reclaim deregistered digital codes, which include the corresponding user's historical data. The MEC server can receive query requests from the first node of the consortium blockchain, including the account information of the user to be queried. Based on the query request, the MEC server retrieves the user's historical data, including data generated by the user using digital codes. Then, the MEC server returns a response message to the first node of the consortium blockchain, containing the user's historical data. For example, the historical data could include information such as the number of times the user used digital codes and the usage time.

[0091] In this embodiment, the MEC server acts as a node in the consortium blockchain. The master node of this consortium blockchain deploys a consortium blockchain management cloud platform to manage the nodes and provide a unified API interface for user terminals. Based on the received digital code application request, the MEC server generates a target digital code corresponding to the target application for the user, creates a ledger for the target digital code, randomly sends this ledger to at least three consortium blockchain nodes for backup, and then sends the target digital code to the target user. By providing a unified digital management platform for various applications through the consortium blockchain, the workload of application developers is reduced, and the tamper-proof security measures provided through backup effectively improve the security of the digital code.

[0092] The encoding method in Example 1 is executed by the MEC server. The encoding method in Example 2 will be used to illustrate the encoding method in which the user terminal is the executing entity.

[0093] refer to Figure 4 , Figure 4 This is a flowchart illustrating a digital coding method based on a consortium blockchain, provided in Embodiment 2 of this application. This method can be executed by a user terminal and includes the following steps.

[0094] S401. Send a digital code request to the mobile edge computing (MEC) server. The digital code request includes information about the target application and the user's identity information.

[0095] When a user needs to apply for a target digital code, the user sends a digital code application request to the MEC server through the user terminal. In this embodiment, the user terminal can communicate with the MEC server through the API interface provided by the MEC server. The description of the target application information and the user's identity information can be referred to step S301 of Embodiment 1.

[0096] S402, Receive the target digital code sent by the MEC server.

[0097] The target numeric code is generated by the MEC server based on the numeric code request, and is used by the user in the target application.

[0098] Optionally, the user terminal can receive the target digital code sent by the MEC server after the MEC server generates the target digital code, and then store the target digital code for later use by the user. Alternatively, when the user needs to use the digital code, the user terminal can also obtain the information of the target application selected by the user, and then send a digital code request to the MEC server. This digital code request includes the target application information and the user's account information. After the MEC server selects the target digital code corresponding to the target application for the user based on the digital code request, the user terminal can receive the target digital code sent by the MEC server and provide it to the user for use in the target application. The target digital code received by the target user can be in the form of an image.

[0099] Optionally, when a user uses the target numeric code through the target application, the validity of the target numeric code needs to be verified first. The user terminal sends a numeric code verification request to the MEC server. The numeric code verification request includes information about the target numeric code, namely the user information corresponding to the target numeric code and related content of the numeric code. The numeric code verification request is used to verify whether the target numeric code is valid. When the MEC server matches the information of the target numeric code with the information of numeric codes stored locally according to the numeric code verification request, and obtains the verification result, the user terminal can receive the verification result sent by the MEC server. The verification result is used to indicate whether the target numeric code is valid. That is, if the match is successful, the verification result indicates that the target numeric code is valid; if the match is unsuccessful, the matching message indicates that the target numeric code is invalid.

[0100] Optionally, when a user needs to modify the content of the target numeric code, the user can send a numeric code modification request to the MEC server through the user terminal. The numeric code modification request includes the content that the user needs to modify. After the MEC server modifies the content of the target numeric code according to the numeric code modification request, the MEC server stores and updates the target numeric code, and the user can use the updated target numeric code when using it again.

[0101] In this embodiment, the user sends a digital code application request to the MEC server through the user terminal. Based on the received request, the MEC server generates a target digital code corresponding to the target application for the user. The user then receives the target digital code from the MEC server and can use it in the target application. Each application obtains its digital code through the digital code management platform provided by the MEC server on the consortium blockchain, reducing the workload for application developers. Furthermore, the MEC server provides tamper-proof security measures, effectively improving the security of the digital codes.

[0102] The above embodiments one and two illustrate the implementation process of the digital coding method based on consortium blockchain provided by the MEC server and user terminal for this application. The interaction process between devices will be described below through embodiment three.

[0103] Figure 5 This is a signaling flowchart for a digital coding method based on a consortium blockchain, provided in Embodiment 3 of this application. Based on Embodiments 1 and 2, this embodiment describes in detail the interaction process between devices, such as... Figure 5 As shown, the method provided in this embodiment includes the following steps.

[0104] S501, The user terminal sends a digital code request to the MEC server.

[0105] The digital code application request includes the user's identity information and the target application's information. The user terminal can send the digital code application request to the MEC server through the API interface provided by the MEC server.

[0106] The S502 and MEC servers generate target digital codes corresponding to the target application for the user based on the digital code application request.

[0107] A ledger is generated for the target digital code. The ledger includes the time when the target digital code was generated, the user information corresponding to the target digital code, and the content of the target digital code. The ledger is then randomly sent to at least three consortium blockchain nodes for backup.

[0108] The S503 and MEC servers send the target digital code to the user terminal.

[0109] The MEC server can send the target numeric code to the user terminal after generating it. Alternatively, the MEC server can store the target numeric code after generation. When the user needs to use the numeric code, the MEC receives a numeric code request from the user terminal. This request includes information about the target application and the user's account information. The MEC server can select the target numeric code corresponding to the target application for the user based on the received request, and then send a response to the numeric code request to the user terminal. The response includes the target numeric code requested by the user.

[0110] MEC servers can send target digital codes to user terminals in the form of images.

[0111] S504. The user terminal sends a digital code verification request to the MEC server.

[0112] The digital code verification request includes information about the target digital code, namely the user information corresponding to the target digital code and related content of the digital code.

[0113] The S505 and MEC servers match the target digital code information with the locally stored digital code information based on the received digital code verification request to obtain the verification result.

[0114] The S506 and MEC servers send verification results to the user terminals.

[0115] The verification result indicates whether the target numeric code is valid. When a match is successful, a matching message indicates that the user can use the target numeric code.

[0116] If the match fails, the matching message indicates that the user cannot use the target numeric code, and the user can initiate the verification again.

[0117] The S507 and MEC servers send a digital code modification request to the user terminal.

[0118] The digital code modification request includes the content that the user needs to modify.

[0119] The S508 and MEC servers modify the content of the target digital code based on the received digital code modification request.

[0120] The MEC server can send the updated target numeric code to the user terminal, or the MEC server can send the updated target numeric code to the user terminal when the user needs to use the numeric code.

[0121] In this embodiment, the user sends a digital code application request to the MEC server through the user terminal. Based on the received digital code application request, the MEC server generates a target digital code corresponding to the target application for the user, generates a ledger for the target digital code, randomly sends this ledger to at least three consortium blockchain nodes for backup, and then sends the target digital code to the target user. By providing a unified code assignment platform for various applications through the consortium blockchain, the workload of application developers is reduced, and the backup provides tamper-proof security measures, effectively improving the security of the digital code.

[0122] refer to Figure 6 , Figure 6 This is a schematic diagram of the structure of a mobile edge computing (MEC) server provided in Embodiment 4 of this application. Figure 6 As shown, the server 60 includes: a receiving module 601, a generating module 602, and a sending module 603.

[0123] The receiving module 601 is used to receive a digital code application request sent by a user terminal. The digital code application request includes the user's identity information and the target application information.

[0124] The generation module 602 is used to generate a target digital code corresponding to the target application for the user according to the digital code application request, generate a ledger for the target digital code, and randomly send the ledger to at least three consortium blockchain nodes for backup. The ledger includes the time of generation of the target digital code, the user information corresponding to the target digital code, and the content of the target digital code.

[0125] The sending module 603 is used to send the target digital code to the user terminal.

[0126] Optionally, the sending module 603 is specifically used for:

[0127] Receive a digital code request sent by the user terminal. The digital code request includes information about the target application and the user's account information.

[0128] Based on the digital code request, the system selects the target digital code corresponding to the target application for the user from the stored digital codes, and sends a response to the digital code request to the user terminal. The response to the digital code request includes the target digital code requested by the user.

[0129] Optionally, after sending the target digital code to the user terminal, the process may also include:

[0130] Receive a digital code verification request sent by a user terminal. The digital code verification request includes information about the target digital code.

[0131] The verification result is obtained by matching the information of the target numeric code with the information of the locally stored numeric code.

[0132] The verification result is sent to the user terminal, and the verification result is used to indicate whether the target numeric code is valid.

[0133] Optionally, after sending the digital code to the user terminal, the process may also include:

[0134] Receive a digital code modification request sent by the user terminal. The digital code modification request includes the content that the user needs to modify.

[0135] Modify and update the content of the user's target numeric code based on the numeric code modification request.

[0136] The deregistered digital code is reclaimed; the deregistered digital code includes the corresponding user's historical data.

[0137] Receive a query request sent by the first node of the consortium blockchain. The query request includes the account information of the user to be queried.

[0138] Retrieve historical data of the user to be queried based on the query request.

[0139] The system returns a response message corresponding to the query request to the first node of the consortium blockchain. The response message includes the historical data of the user to be queried.

[0140] The mobile edge computing (MEC) server in this embodiment can be used to execute the digital coding method steps based on consortium blockchain in Embodiment 1. The specific implementation and technical effects are similar, and will not be repeated here.

[0141] refer to Figure 7 , Figure 7 This is a schematic diagram of the structure of a user terminal provided in Embodiment 5 of this application. Figure 7 As shown, the terminal 70 includes a transmitting module 701 and a receiving module 702.

[0142] The sending module 701 is used to send a digital code request to the mobile edge computing (MEC) server. The digital code request includes information about the target application and the user's identity information.

[0143] The receiving module 702 is used to receive the target digital code sent by the MEC server. The target digital code is generated by the MEC server according to the digital code application request and is used by the user in the target application.

[0144] Optionally, the receiving module 702 is specifically used for:

[0145] Obtain the user's selected target application information and send a digital code request to the MEC server. The digital code request includes the target application information and the user's account information.

[0146] Receive the response to the digital code request sent by the MEC server. The response to the digital code request includes the target digital code requested by the user.

[0147] Optional, also includes:

[0148] Send a digital code verification request to the MEC server. The digital code verification request includes information about the target digital code and is used to request verification of whether the target digital code is valid.

[0149] Receive the verification result sent by the MEC server. The verification result is used to indicate whether the target numeric code is valid.

[0150] Optional, also includes:

[0151] Send a numeric code modification request to the MEC server. The numeric code modification request includes the content that the user needs to modify.

[0152] The user terminal in this embodiment can be used to execute the steps of a digital coding method based on a consortium blockchain in Embodiment 2. The specific implementation and technical effects are similar, and will not be described again here.

[0153] Figure 8 This is a schematic diagram of the structure of a mobile edge computing (MEC) server provided in Embodiment Six of the present invention. Figure 8 As shown, the server 80 includes: a processor 801, a memory 802, and a transceiver 803. The processor 801 executes computer execution instructions stored in the memory 802 and controls the receiving and sending actions of the transceiver 803, so that at least one processor executes the steps of a digital coding method based on a consortium blockchain in Embodiment 1. The specific implementation and technical effects are similar and will not be described in detail here.

[0154] Figure 9 This is a schematic diagram of the structure of a user terminal provided in Embodiment Seven of the present invention. Figure 9 As shown, the terminal 90 includes: a processor 901, a memory 902, and a transceiver 903. The processor 901 executes computer execution instructions stored in the memory 902 and controls the receiving and sending actions of the transceiver 903, so that at least one processor executes the steps of a digital coding method based on a consortium blockchain in Embodiment 2. The specific implementation and technical effects are similar and will not be described in detail here.

[0155] This application provides a computer-readable storage medium storing computer-executable instructions. When executed by a processor, these instructions are used to implement the steps of a digital coding method based on a consortium blockchain, as described in either embodiment one or embodiment three above. The specific implementation and technical effects are similar and will not be repeated here.

[0156] Embodiment 9 of the present invention provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the steps of a digital coding method based on a consortium blockchain as described in Embodiment 1 or Embodiment 3 above. The specific implementation method and technical effects are similar and will not be repeated here.

[0157] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0158] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A digital coding method based on a consortium blockchain, characterized in that, The method is applied to a mobile edge computing (MEC) server, where the MEC server acts as a node in a consortium blockchain. The master node of the consortium blockchain deploys a consortium blockchain management cloud platform, which manages the nodes of the consortium blockchain and provides unified digital encoding services for multiple different applications, as well as a unified application programming interface (API) for user terminals. The method includes: Receive a digital code application request sent by a user terminal through the unified application programming interface (API), wherein the digital code application request includes the user's identity information and the target application's information; According to the digital code application request, a target digital code corresponding to the target application is generated for the user, and an independent ledger is generated for the target digital code. The operation of generating the independent ledger is performed by the digital code management platform deployed on the MEC server. The ledger is actively and randomly sent by the MEC server to at least three consortium blockchain nodes for backup. The ledger includes the generation time of the target digital code, the user information corresponding to the target digital code, and the content of the target digital code. Send the target digital code to the user terminal; The system receives a digital code modification request sent by the user terminal, the digital code modification request including the content that the user needs to modify; modifies the content of the user's target digital code according to the digital code modification request, and updates the content of the target digital code; Also includes: The deregistered digital code is recycled, and the deregistered digital code includes the corresponding user's historical data; Receive a query request sent by the first node of the consortium blockchain, the query request including the account information of the user to be queried; Query the historical data of the user to be queried according to the query request; The system returns a response message corresponding to the query request to the first node of the consortium blockchain. The response message includes the historical data of the user to be queried.

2. The method according to claim 1, characterized in that, Sending the target digital code to the user terminal includes: Receive a digital code request sent by the user terminal, wherein the digital code request includes information about the target application and the user's account information; Based on the digital code request, a target digital code corresponding to the target application is selected for the user from the stored digital codes, and a response to the digital code request is sent to the user terminal. The response to the digital code request includes the target digital code requested by the user.

3. The method according to claim 1 or 2, characterized in that, After sending the target digital code to the user terminal, the method further includes: Receive a digital code verification request sent by the user terminal, wherein the digital code verification request includes information about the target digital code; The verification result is obtained by matching the information of the target digital code with the information of the digital code stored locally. The verification result is sent to the user terminal, and the verification result is used to indicate whether the target numeric code is valid.

4. A digital coding method based on a consortium blockchain, characterized in that, Applied to user terminals, including: A digital code request is sent to the mobile edge computing (MEC) server through a unified application programming interface (API). The digital code request includes information about the target application and the user's identity information. The system receives a target digital code sent by the MEC server. The target digital code is a target digital code corresponding to the target application generated by the MEC server according to the digital code application request. This enables the MEC server to generate an independent ledger based on the target digital code. The MEC server actively and randomly sends the ledger to at least three consortium blockchain nodes for backup. The ledger includes the generation time of the target digital code, the user information corresponding to the target digital code, and the content of the target digital code. The target digital code is used by the user in the target application. A digital code modification request is sent to the MEC server. The digital code modification request includes the content that the user needs to modify, so that the MEC server modifies and updates the content of the user's target digital code according to the digital code modification request. When the target digital code is cancelled and recycled, if it is necessary to query historical data related to the user, the first node of the consortium blockchain initiates a query request to the MEC server, and the user terminal indirectly obtains the query results of the historical data through the target application or the consortium blockchain authorization mechanism.

5. The method according to claim 4, characterized in that, The target digital code received from the MEC server includes: Obtain the information of the target application selected by the user, and send a digital code request to the MEC server. The digital code request includes the information of the target application and the user's account information. The system receives a response to the digital code request sent by the MEC server, the response including the target digital code requested by the user.

6. The method according to claim 5, characterized in that, Also includes: Send a digital code verification request to the MEC server. The digital code verification request includes information about the target digital code and is used to request verification of whether the target digital code is valid. The system receives a verification result sent by the MEC server, which indicates whether the target numeric code is valid.

7. The method according to any one of claims 4-6, characterized in that, Also includes: A digital code modification request is sent to the MEC server, the digital code modification request including the content that the user needs to modify.

8. A mobile edge computing (MEC) server, characterized in that, The MEC server serves as a node in the consortium blockchain. The master node of the consortium blockchain deploys a consortium blockchain management cloud platform. This platform manages the nodes of the consortium blockchain and provides unified digital coding services for multiple different applications. It also provides a unified application programming interface (API) for user terminals, including: The receiving module is used to receive a digital code application request sent by a user terminal through the unified application programming interface (API), wherein the digital code application request includes the user's identity information and the target application information; The generation module is used to generate a target digital code corresponding to the target application for the user according to the digital code application request, and to generate an independent ledger for the target digital code. The operation of generating the independent ledger is performed by the digital code management platform deployed on the MEC server. The ledger is actively and randomly sent by the MEC server to at least three consortium blockchain nodes for backup. The ledger includes the generation time of the target digital code, the user information corresponding to the target digital code, and the content of the target digital code. A sending module is used to send the target digital code to the user terminal; A receiving module is configured to receive a digital code modification request sent by the user terminal, the digital code modification request including the content that the user needs to modify; modify the content of the user's target digital code according to the digital code modification request, and update the content of the target digital code; The recycling module is used to recycle the deregistered digital code, which includes the corresponding user's historical data. The receiving module is also used to receive a query request sent by the first node of the consortium blockchain, wherein the query request includes the account information of the user to be queried; The query module is used to query the historical data of the user to be queried according to the query request; and return a response message corresponding to the query request to the first node of the consortium blockchain, the response message including the historical data of the user to be queried.

9. A user terminal, characterized in that, include: The sending module is used to send a digital code application request to the mobile edge computing (MEC) server through a unified application programming interface (API). The digital code request includes information about the target application and the user's identity information. A receiving module is configured to receive a target digital code sent by the MEC server. The target digital code is a target digital code corresponding to the target application generated by the MEC server according to the digital code application request, so that the MEC server generates an independent ledger based on the target digital code, and actively and randomly sends the ledger to at least three consortium blockchain nodes for backup. The ledger includes the generation time of the target digital code, the user information corresponding to the target digital code, and the content of the target digital code, wherein the target digital code is used by the user in the target application. The sending module is further configured to send a digital code modification request to the MEC server, the digital code modification request including the content that the user needs to modify, so that the MEC server modifies and updates the content of the user's target digital code according to the digital code modification request; When the target digital code is cancelled and recycled, if it is necessary to query historical data related to the user, the first node of the consortium blockchain initiates a query request to the MEC server, and the user terminal indirectly obtains the query results of the historical data through the target application or the consortium blockchain authorization mechanism.

10. A mobile edge computing (MEC) server, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 3.

11. A user terminal, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 4 to 7.

Images