JP7235363B1 - Access distribution method - Google Patents

Abstract

The present invention provides an access distribution method that performs URI mapping to code IDs even in the event of a server failure or connection failure, and performs URI mapping at high speed regardless of the state of a distributed ledger network. An access distribution method using a specific code image as a code image, wherein the management server generates a code ID, and the management server gives a specific flag to the code ID that matches a predetermined criterion. Then, the code ID with the specific flag is registered in the smart terminal, and the smart terminal acquires the URI corresponding to the target code ID from its own database based on the target code ID obtained from the code image. and, if the smart terminal cannot obtain the URI from its own database, obtain the URI by using a non-substitutable token or by connecting to the relay server, and access the content using the URI obtained by the smart terminal. including doing and [Selection drawing] Fig. 6

Description

The present disclosure relates to server-evadable access distribution methods using Internet servers, non-fungible tokens in distributed ledger systems, and smart terminals.

Since the code of the one-dimensional barcode consists of only numerical values, it cannot directly store a URI (Uniform Resource Identifier) unlike the two-dimensional code. In order to read a one-dimensional barcode with a code reader and transfer it to an arbitrary website, it is necessary to map the code ID stored in the read code to a URI. Note that the URI referred to in this specification is information mainly used to represent the location information of data, services, equipment, etc. on the Internet or the like.

A widely used method is to prepare a database in which code IDs and URIs are linked on an Internet server, and to map read codes by a relay server. However, there is a problem that URI mapping cannot be performed when access to the relay server is instantaneously concentrated due to an event or the like, or when a server failure occurs.

According to the description in paragraph 0018 of Japanese Patent Application Publication No. 2021-519488 (Patent Document 1), by obtaining the URI of the metadata in the non-alternative token among the distributed ledger tokens, 1 Dimensional barcodes can be transferred to content such as websites and apps.

However, since a network connection is required for the conversion of the code ID to the token ID that identifies the non-alternative token and the metadata acquisition process from the non-alternative token, if a connection failure occurs, the code ID URI corresponding to cannot be obtained.

Also, if the distributed ledger network is not sufficiently fast, a waiting time occurs in URI mapping to the code ID, and processing from code reading to content transfer takes time.

Japanese Patent Publication No. 2021-519488

A specific aspect of the present disclosure is to be able to perform URI mapping to a code ID even in the event of a server failure or connection failure, and to perform the processing at high speed regardless of the state of the distributed ledger network. be one of

The method according to the present disclosure is generally characterized by the avoidance of relay servers and redundant mapping of URIs to code IDs. This has the technical effect of improving the speed and availability of URI mapping to code IDs and transfer from code readers to content even in the event of a server failure or connection failure.

An access distribution method according to one aspect of the present disclosure is an access distribution method executable in a system including one or more management servers and one or more smart terminals that are communicatively connected to each other via a network. There is
a first step in which the management server generates a code ID in response to a code issuance request;
a second step in which the management server assigns a specific flag to the code ID having a high priority or importance determined based on a predetermined criterion;
a third step in which the management server associates and stores a predetermined URI with the code ID, and stores the code ID and the URI in a relay server that can communicate with each other via the network;
a fourth step in which the management server converts the code ID into a token ID that is mutually convertible with the code ID;
a fifth step in which the management server stores the token ID and the URI in a computer on a distributed ledger network that can communicate with each other via the network;
a sixth step in which the management server and the smart terminal communicate with each other, and the code ID to which the specific flag is attached and the URI corresponding to the code ID are registered in the smart terminal;
The smart terminal determines the target code ID from a database of the code ID and the URI stored in advance in the smart terminal based on the target code ID obtained from the code image that can be optically read by the smart terminal. a seventh step of obtaining the corresponding URI;
When the smart terminal fails to acquire the URI from the database pre-stored in the smart terminal, the non-substitutable token specified based on the token ID obtained by converting the target code ID is used. an eighth step of obtaining the URI from the computer on the distributed ledger network or obtaining the URI corresponding to the target code ID from the relay server;
a ninth step in which the smart terminal accesses the content using the URI obtained in the seventh step or the eighth step;
including
The code image has a one-dimensional barcode portion , has a vertical length to horizontal length ratio of 1:10 to 50, and has a horizontal length of 300 mm or more.
This access distribution method is characterized by:

In a preferred form of the present disclosure, the distributed ledger is a blockchain based on one or more nodes and a proof-of-work and/or proof-of-stake consensus algorithm, and includes a storage area It is characterized by having a virtual machine (distributed ledger virtual machine). With such a configuration, the present disclosure can realize URI mapping to code ID while avoiding a relay server. In addition, with such a configuration, the present disclosure has the further technical effect of being able to provide the system with the high availability that the distributed ledger system has.

In a preferred form of the present disclosure, the management server is equipped with a web server and a database server capable of high-speed, large-capacity processing on one or more computer devices, and the databases of the management server and the relay server are synchronized in real time. , and high-speed, large-capacity connection with a distributed ledger network is possible. With such a configuration, the present disclosure can realize suitable code and token management regardless of the load of the code registration process. Moreover, with such a configuration, the present disclosure has the further technical effect of increasing the availability of code and token management regardless of the load of the code registration process.

In a preferred embodiment of the present disclosure, the code reader used for image reading on smart terminals is built as an application program for iOS, Android, Windows and other smart terminals, or an application program for other terminals, and the application It is characterized by a high-speed and high-precision image recognition engine running on the program, a database engine running on the terminal OS, and high-speed communication with the management server, relay server, and distributed ledger network. With such a configuration, the present disclosure enables high-speed and redundant mapping of URIs to code IDs read by a code reader. Moreover, with such a configuration, there is a technical effect of improving the speed and availability of the URI mapping to the code ID and the transfer from the code reader to the content even in the event of a server failure or connection failure.

A preferred form of the present disclosure is characterized by using an XPAND code as the code. With such a configuration, the present disclosure allows for a reduced code footprint and long range reading. In addition, by adopting such a configuration, it is possible to obtain a technical effect of improving the area efficiency of the code with respect to the reading distance while using the existing code image recognition algorithm.

According to the present disclosure, URI mapping to code ID and access to content from smart terminals are realized at high speed and high availability based on URI acquisition from multistage and different paths and redundancy of URI mapping to code ID. system can be realized.

1 is a system configuration diagram according to an embodiment of the present disclosure; FIG. FIG. 4 is a diagram showing the flow of a code generation method according to an embodiment of the present disclosure; FIG. 3 is a flow chart showing the operation procedure of the management server 10 when executing the code generation method outlined in FIG. 2. FIG. FIG. 3 is a diagram showing the structure of data stored in each of a management server, a relay server, a distributed ledger virtual machine, and a smart terminal; FIG. 3 is a flowchart showing an operation procedure of synchronization processing of the code ID and the mapping URI of the smart terminal 13 in the code generation method outlined in FIG. 2. FIG. FIG. 3 is a diagram showing the flow of a code reading method according to an embodiment of the present disclosure; FIG. 10 is a graphical diagram showing the configuration of an XPAND code as an example of code for storing code IDs; 7 is a flow chart showing the operation procedure of the smart terminal when executing the code reading method outlined in FIG. 6;

An access distribution system according to the present disclosure will be described below with reference to the drawings. Note that the embodiments shown below are examples of the present disclosure, and the present disclosure is not limited to the following embodiments, and various configurations can be adopted. Although the configuration, operation, and functions of the access distribution system will be described in this embodiment, a method, program, or recording medium having a similar configuration will have similar effects.

FIG. 1 is a system configuration diagram according to an embodiment of the present disclosure. The distributed access system 100 shown in FIG. 1 comprises at least one management server 10 , at least one relay server 11 , distributed ledger virtual machines 12 and at least one smart terminal 13 . Functions related to the access distribution system are implemented using applications stored in a computer device and hardware resources provided in the computer device. The application is implemented in the form of installed software or cloud software.

The management server 10 includes an arithmetic unit 101 , a storage unit 102 , an input unit 103 , an output unit 104 and a communication unit 105 .

The relay server 11 includes an arithmetic unit 111 , a storage unit 112 , an input unit 113 , an output unit 114 and a communication unit 115 .

The distributed ledger virtual machine 12 includes an arithmetic unit 121 , a storage unit 122 and a communication unit 125 . The distributed ledger virtual machine 12 is a virtual information processing system that functions on a known distributed ledger network. Therefore, the calculation unit 121, the storage unit 122, and the communication unit 125 described here are actually virtual concepts realized by a plurality of computers forming a distributed ledger network, but the content according to the present disclosure This description is used in this specification to facilitate understanding.

Any known distributed ledger network can be used as long as it performs the same calculations and verifications on a large number of computers distributed on the network and holds the same data (ledger). . This embodiment assumes the use of a well-known distributed ledger network called Ethereum (registered trademark).

The smart terminal 13 includes an arithmetic unit 131 , a storage unit 132 , an input unit 133 , an output unit 134 and a communication unit 135 .

Operation units 101, 111, 121 and 131 each comprise a processor capable of executing an instruction set.

Storage units 102, 112, 122 and 132 each include a recording medium. Storage media include, for example, hard disk drives, solid state drives, random access memories, and the like.

The input units 103, 113, and 133 are, for example, keyboard devices, pointing devices, and touch panels, respectively, and there are no restrictions on their types.

Each of the output units 104, 114 and 134 includes, for example, a frame buffer for holding drawing information and a display device such as a liquid crystal panel.

Communication units 105, 115, 125 and 135 each perform processing for communication via IP (Internet Protocol), for example.

For the network NW in the access distributed system 100, for example, TCP/IP (Transmission Control Protocol/Internet Protocol) is used as a communication protocol.

FIG. 2 is a diagram illustrating the flow of a code generation method according to an embodiment of the present disclosure.
A user who is a code issuance requester transmits a code issuance request to the management server 10 through any web browser executable on the computer 14 . In response to this, the management server 10 issues a code ID and stores it in the database of its own storage unit 102 . The management server 10 then transmits the code ID to the relay server 11 and smart terminal 13 . Relay server 11 and smart terminal 13 that have received the code ID register the code ID in the databases of storage units 122 and 132, respectively.

The management server 10 converts a code ID into a token ID by means of a prestored program 20 for converting a code ID into a token ID. A method of converting a code ID into a token ID can be mutually converted. For example, there is a method of adding a prefix to a code ID to obtain a token ID. As an example, consider the case where the code ID is "12345678". By adding the prefix "XPD" to this code ID, a token ID "XPD12345678" can be generated.

The management server 10 sends the converted token ID to the smart contract 30, which is a function implemented by a computer program running on the distributed ledger virtual machine 12. The smart contract 30 issues a token having the token ID and sends this token to the address on the distributed ledger network used by the user. The management server 10 issues the code image data and ends the code generation. A code image based on the code image data is displayed on the screen of the computer 14 used by the user.

Next, the user installs a code reader application program (hereinafter referred to as an “application”) for reading code images in the smart terminal 13 . As a result, a database file is generated in the storage unit 132 of the smart terminal 13 .

The database is implemented, for example, by inputting/outputting data to/from a data file generated in the storage area of the storage unit 132 in the smart terminal 13 through SQLite, which is a database management system.

In the smart terminal 13, the application for reading the code image is periodically started and connected to the management server 10, and whether the code ID with a specific flag (details will be described later) exists in the management server 10. Inquire about what

If there are code IDs with specific flags, the application of the smart terminal 13 stores those code IDs and mapping URIs in the database within the storage unit 132 of the smart terminal 13 .

FIG. 3 is a flow chart showing the operation procedure of the management server 10 when executing the code generation method outlined in FIG. 2 above. FIG. 4 is a diagram showing the structure of data stored in each of the management server, relay server, distributed ledger virtual machine, and smart terminal.

The user who is the code issue requester accesses the management server 10 using the computer 14 (see FIG. 2), and inputs the necessary information in the form of the code issuance screen displayed on the computer 14 by the management server 10 (S201). When a code issuance application (S202) is made, the management server 10 generates a code ID, stores it in the database of its own storage unit 102, and stores it in the storage unit 112 database of the relay server 11 ( S203).

The calculation unit 101 of the management server 10 converts the code ID into a token ID using the conversion program 20 (see FIG. 2) (S204).

Note that the specific flag (distribution flag) for access distribution is generated or not generated by the parameters input at the time of application for issuance (S202) and the determination program of the management server 10. FIG.

The specific flag referred to here indicates an item based on a predetermined criterion such as the priority or importance of the code ID, and is arbitrarily set in advance. For example, when the URI corresponding to the code ID is expected to be used many times, a specific flag is attached, and in other cases, the specific flag is not attached. As a result, the amount of code IDs held (stored) in the smart terminal 13 can be reduced, and only those with high priority or importance can be held, thereby reducing consumption of storage capacity in the smart terminal 13. .

When the specific flag is generated (S205; YES), the calculation unit 101 of the management server 10 stores the specific flag in the database of its own storage unit 102 and in the database of the storage unit 112 of the relay server 11. (S206).

As shown in FIG. 4, the code ID is stored in the code ID column 402 of the database 401 constructed in the storage unit 102 of the management server 10, and is stored in the database 406 constructed in the storage unit 112 of the relay server 11. is stored in the code ID column 407 of . Also, the token ID is stored in the token ID constant 422 of the non-alternative token NFT (Non-Fungible Token) metadata 421 in the storage unit 122 of the distributed ledger virtual machine 12 .

The mapping URI is stored in the URI column 403 in the database 401 in the storage unit 102 of the management server 10 and in the URI column 408 in the database 406 in the storage unit 112 of the relay server 11 . Furthermore, the mapping URI is stored in the URI constant 423 within the storage unit 122 of the distributed ledger virtual machine 12 .

Further, the specific flag is stored in the specific flag column 404 of the database 401 built in the storage unit 102 of the management server 10, and is stored in the specific flag column 409 of the database 406 built in the storage unit 112 of the relay server 11. stored in

The calculation unit 101 of the management server 10 issues code image data (S207) and transmits it to the user's computer 14. FIG. With this, the code issuing process ends.

FIG. 5 is a flow chart showing the operation procedure of synchronization processing of the code ID of the smart terminal 13 and the mapping URI in the code generation method outlined in FIG.

The computing unit 131 of the smart terminal 13 periodically activates the application installed in the storage unit 132 (S251), accesses the management server 10, and adds a specific flag to the database in the storage unit 102 of the management server 10. exists (S252).

If there is a code ID with a specific flag (S253; YES), the calculation unit 131 of the smart terminal 13 determines whether or not the code ID has been stored in the database within the storage unit 132 of the smart terminal 13 (S254).

If the code ID is not stored (S254; NO), the calculation unit 131 of the smart terminal 13 acquires the code ID and mapping URI from the management server 10. FIG. Then, the calculation unit 131 of the smart terminal 13 stores the code ID in the code ID column 412 of the database 411 of the storage unit 132 shown in FIG. 4 and stores the mapping URI in the URI column 413 (S255).

If there is no code ID with a specific flag (S253; NO), or if the code ID has already been stored in the smart terminal 13 (S254; YES), or if the storage is completed in S255, the computing unit of the smart terminal 13 131 ends a series of processing.

FIG. 6 is a diagram showing the flow of a code reading method according to an embodiment of the present disclosure.
The user activates the above application pre-installed in the smart terminal 13 and takes a picture of the code ID with the camera (not shown) of the smart terminal 13 . The calculation unit 131 of the smart terminal 13 obtains a code ID from the code image data by performing predetermined image processing on the code image data obtained by photographing the code with a camera.

Next, the calculation unit 131 of the smart terminal 13 inquires the database in its own storage unit 132 whether a URI corresponding to the code ID exists. If the URI does not exist, the calculation unit 131 of the smart terminal 13 converts the code ID into a token ID using the predetermined conversion program 20 . Specifically, conversion to a token ID is performed by using a predetermined prefix as described above. As an example, consider the case where the code ID is "12345678". By adding the prefix "XPD" to this code ID, a token ID "XPD12345678" can be generated.

Next, the computing unit 131 of the smart terminal 13 accesses the distributed ledger virtual machine 12 and inquires whether a URI corresponding to the token ID exists in the database within the distributed ledger virtual machine 12 . If the URI does not exist, the computing unit 131 of the smart terminal 13 accesses the relay server 11 and obtains from the relay server 11 the URI corresponding to the code ID.

When the URI can be obtained by any method, the computing unit 131 of the smart terminal 13 uses the obtained URI to access the website corresponding to this URI, and displays the content obtained from the website on the display of the output unit 134. display on the screen of the device. Thus, the code reading process is completed. In addition to accessing a website, the URI may be used, for example, to launch a native application of the smart terminal 13 with a hyperlink using the URI.

Here, an XPAND code as an example of a code image photographed and read by the smart terminal 13 will be described in detail with reference to FIG. The XPAND code shown in FIG. 7 is a code that can use any method such as a one-dimensional bar code, optical ID, infrared reflective marker, or image-embedded marker as a code for storing the code ID.

As one form of implementation, FIG. 7 shows a configuration in which a one-dimensional bar code is used as a code. Specifically, the XPAND code has a horizontally long shape, and a one-dimensional bar code part shown by arranging a plurality of vertical bars with different thicknesses in the figure, and the one-dimensional bar code part It has auxiliary lines for reading correction arranged on the upper and lower outer sides of the . As shown in the figure, each auxiliary line is arranged with a margin provided between it and the one-dimensional barcode portion.

In addition, extended guard bars for reading correction can be added to the left and right sides of the one-dimensional bar code portion. In the illustrated example, extended guard bars each including three vertical bars are arranged on the left and right sides of the one-dimensional bar code part with a margin between them and the one-dimensional bar code part. Also, a graphic area for reading correction can be added to the left or right end. In the illustrated example, a substantially circular mark is added.

The ratio of the height to width of the XPAND code is preferably 1 height to 24 widths, or in the range of 10 to 50 widths to 1 height. The width of the XPAND code is preferably 300 millimeters or more. The XPAND code of this embodiment can be optically read and used in the same manner as general JAN codes, one-dimensional barcodes, two-dimensional barcodes, and the like. Because of its oblong shape, it can be easily attached to various signboards. It also has excellent reading performance from a relatively distant position. According to the verification by the applicant of the present application, it has been confirmed that reading is possible with a terminal such as a general smart phone from a short distance of about 10 cm to a long distance of 200 m.

FIG. 8 is a flow chart showing the operation procedure of the smart terminal 13 when executing the code reading method outlined in FIG. 6 above. First, when the application of the smart terminal 13 is activated by the user (S301) and a code image is captured by the camera of the smart terminal 13, the calculation unit 131 of the smart terminal 13 converts the code image into a code ID (target code ID). Convert (S302).

The calculation unit 131 of the smart terminal 13 determines whether or not the code ID column 412 of the database in its own storage unit 132 exists (S303). An attempt is made to acquire a URI corresponding to the code ID from column 413 (S304).

If the URI can be obtained from the URI column 413 (S305; YES), the computing unit 131 of the smart terminal 13 uses the obtained URI to access the corresponding website (S309).

If the URI could not be obtained in step S304 (S305; NO), the calculation unit 131 of the smart terminal 13 converts the code ID into a token ID, and based on this, identifies the non-alternative token NFT contained in the token ID constant 422. Then, an attempt is made to obtain a URI from the URI variable 423 from the distributed ledger virtual machine 12 (S306).

If the URI can be acquired (S307; YES), the computing unit 131 of the smart terminal 13 uses the acquired specified URI to access the corresponding website (S309).

If the URI could not be acquired in step S306 (S307; NO), the calculation unit 131 of the smart terminal 13 accesses the relay server 11 and extracts the code ID from the code ID column 407 of the database in the storage unit 122 of the relay server 11. , and acquires the URI from the URI column 408 (S308).

The computing unit 131 of the smart terminal 13 that has obtained the URI accesses the corresponding website using this designated URI (S309).

The user can acquire content to the smart terminal 13 from the website accessed based on the URL acquired by any method.

As described above, the URI may be used in S309 by launching a native application of the smart terminal 13 with a hyperlink using the URI, for example.

As described above, according to this embodiment, by reading the code with a smart terminal, even in the event of a server failure or connection failure, URI mapping to the code ID can be performed, and the feasibility of transferring to the content can be increased. can.

In addition, according to this embodiment, by reading the code with a smart terminal, regardless of the state of the distributed ledger network, URI mapping to the code ID can be performed at high speed, and the feasibility of transferring to content can be improved. can be done.

Also, according to this embodiment, the code can be read from a relatively long distance and the content specified by the code can be accessed.

10 Management Server 11 Relay Server 12 Distributed Ledger Virtual Machine 13 Smart Terminal 14 Computer 20 Program for Mutual Conversion of Code ID and Token ID 30 Smart Contract Operating on Distributed Ledger Virtual Machine 100 Access Distributed System 101, 111, 121, 131 calculation unit 102, 112, 122, 132 storage unit 103, 113, 133 input unit 104, 114, 134 output unit 105, 115, 125, 135 communication unit DB database NFT non-substitutable token 401 database of management server 402 of management server Database code ID column 403 Management server database URI column 404 Management server database identification flag column 406 Relay server database 407 Relay server database code ID column 408 Relay server database URI column 409 Relay server database Specific flag column 411 Database of smart terminal 412 Code ID column of database of smart terminal 413 URI column of database of smart terminal 421 Non-alternative token metadata 422 Token ID constant of non-alternative token metadata 423 URI variable of non-alternative token metadata

Claims (1)

An access distribution method executable in a system comprising one or more management servers and one or more smart terminals communicably connected to each other via a network, comprising:
a first step in which the management server generates a code ID in response to a code issuance request;
a second step in which the management server assigns a specific flag to the code ID having a high priority or importance determined based on a predetermined criterion;
a third step in which the management server associates and stores a predetermined URI with the code ID, and stores the code ID and the URI in a relay server that can communicate with each other via the network;
a fourth step in which the management server converts the code ID into a token ID that is mutually convertible with the code ID;
a fifth step in which the management server stores the token ID and the URI in a computer on a distributed ledger network that can communicate with each other via the network;
a sixth step in which the management server and the smart terminal communicate with each other, and the code ID to which the specific flag is attached and the URI corresponding to the code ID are registered in the smart terminal;
The smart terminal determines the target code ID from a database of the code ID and the URI stored in advance in the smart terminal based on the target code ID obtained from the code image that can be optically read by the smart terminal. a seventh step of obtaining the corresponding URI;
When the smart terminal fails to acquire the URI from the database pre-stored in the smart terminal, the non-substitutable token specified based on the token ID obtained by converting the target code ID is used. an eighth step of obtaining the URI from the computer on the distributed ledger network or obtaining the URI corresponding to the target code ID from the relay server;
a ninth step in which the smart terminal accesses the content using the URI obtained in the seventh step or the eighth step;
including
The code image has a one-dimensional barcode portion , has a vertical length to horizontal length ratio of 1:10 to 50, and has a horizontal length of 300 mm or more.
An access distribution method characterized by:

Images