Hub server, publishing system, publishing method, and program

The hub server integrates multiple ABT systems to issue a unified ID, simplifying the use of combined services by providing a single code image for multiple transportation systems, addressing the inefficiencies of managing multiple IDs in existing systems.

JP2026182169APending Publication Date: 2026-11-19KK TOSHIBA
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2025078146
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-08
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

In existing account-based ticketing systems, users need multiple IDs for different transportation systems when purchasing combined services, leading to inefficiencies and complexity in managing and using these IDs across various systems.

Method used

A hub server integrates with multiple ABT servers to issue a unified account identification (IDq) for a single product, facilitating the creation of accounts across different ABT systems and providing a single code image for multiple services.

Benefits of technology

Users receive a single code image for multiple services, simplifying the use of integrated services across different ABT systems without needing to manage multiple IDs, and enabling seamless service access across various transportation systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026182169000001_ABST
    Figure 2026182169000001_ABST
Patent Text Reader

Abstract

This invention provides a hub server, an issuance processing system, an issuance processing method, and a program that can integrate account identification information used in multiple systems. [Solution] According to the embodiment, the hub server has a communication unit and a processor. The communication unit communicates with a plurality of ABT servers provided in each of the plurality of ABT systems. The processor identifies the ABT products issued by each ABT server included in a single product for sale, sends an issuance request for each ABT product to each ABT server to create an account for each ABT product, which includes one ID for the product for sale, and provides information indicating the ID to the source of the issuance request for the product for sale.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to a hub server, an issuance processing system, an issuance processing method, and a program.

Background Art

[0002] In recent years, in transportation and the like, account-based systems (ABT systems) that provide services such as boarding and alighting from railways and buses using an ID indicated by a code image presented by a user have been proposed. The ABT system is a system that provides a service enabling the use of railways and buses by having a server manage status information such as boarding and alighting of railways and buses for each account. At present, business operators of transportation such as railways and buses often operate ABT systems using IDs issued according to predetermined standards.

[0003] However, in ABT systems of different business operators, account data is created for a unique ID independently issued by the server of the own system. For this reason, when selling a product that combines a plurality of services provided by business operators of different ABT systems, the seller needs to provide the user with a plurality of IDs issued for each of the different ABT systems that provide the plurality of services included in the product. In addition, there is a problem that a user has to obtain a plurality of IDs for each ABT system for one product that combines a plurality of services provided by a plurality of business operators, and use those IDs properly for each ABT system that is actually used.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The present invention aims to provide a hub server, an issuance processing system, an issuance processing method, and a program that can integrate account identification information used in multiple systems, in order to solve the above-mentioned problems. [Means for solving the problem]

[0006] According to the embodiment, the hub server has a communication unit and a processor. The communication unit communicates with a plurality of ABT servers provided in each of the plurality of ABT systems. The processor identifies the ABT products issued by each ABT server included in a single product for sale, sends an issuance request for each ABT product to the respective ABT server to create an account for each ABT product, which includes one ID for the product for sale, and provides information indicating the ID to the source of the sales product issuance request. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 is a schematic diagram showing an example of the overall configuration of an account issuance system as an issuance processing system according to the embodiment. [Figure 2] Figure 2 is a block diagram showing an example configuration of a hub function server in an account issuance system as an issuance processing system according to the embodiment. [Figure 3] Figure 3 is a block diagram showing an example configuration of the ABT server in the account issuance system as an issuance processing system according to the embodiment. [Figure 4] Figure 4 shows an example of the configuration of the product master in the hub function server of the account issuance system, which is an issuance processing system according to the embodiment. [Figure 5] Figure 5 shows an example of the configuration of the account database of the ABT server of the account issuance system, which is an account issuance processing system according to the embodiment. [Figure 6] Figure 6 is a sequence illustrating the flow of a first operational example in the account issuance system as an issuance processing system according to the embodiment. [Figure 7]Figure 7 is a sequence illustrating the flow of a second operational example in the account issuance system as an issuance processing system according to the embodiment. [Figure 8] Figure 8 is a sequence illustrating the flow of a third operational example in the account issuance system as an issuance processing system according to the embodiment. [Modes for carrying out the invention]

[0008] The embodiments will be described below with reference to the drawings. First, we will briefly describe the entire account issuance system 1 as an issuance processing system, which includes a hub server and multiple ABT servers according to the embodiment. Figure 1 is a conceptual diagram showing an example configuration of the account issuance system 1 according to an embodiment. The account issuance system 1 includes a hub function server (hub server) 2, multiple ABT (Account Based Ticketing) servers 3, and a sales server (sales site) 4. In the configuration example shown in Figure 1, the first ABT server (bus ABT server) 3a and the second ABT server (railway ABT server) 3b are shown as examples of multiple ABT servers 3.

[0009] Hub function server 2 is an example of a hub server that constitutes the publishing system. Hub function server 2 is connected to multiple ABT servers 3 (3a, 3b, ...) and sales server 4. Hub function server 2 mediates the transmission and reception of data related to product sales between sales server 4 and each ABT server, as well as the transmission and reception of data between multiple ABT servers 3. Hub function server 2 also manages information about the products that sales server 4 sells to users.

[0010] ABT Server 3 is an example of multiple operational servers in the issuance processing system. ABT Server 3 is a server device that manages accounts created for each IDq (ID) used as identification information for providing products (ABT products) such as services in ABT Systems A, B, ... Each ABT Server 3a, 3b, ... manages information such as validity (boarding validity information) and status (boarding and alighting information) associated with IDq in their respective ABT Systems A, B, ... as account data.

[0011] For example, each ABT server 3a, 3b, ... creates (issues) account data to provide services in ABT systems A, B, ... in response to an issuance request from the hub function server 2. After creating the account data, ABT servers 3a, 3b, ... refer to the account data and instruct the execution of processing in response to processing (service) requests from devices in ABT systems A, B, .... ABT servers 3a, 3b, ... also update the information in the account data according to information indicating the processing results from devices within ABT systems A, B, ....

[0012] In the embodiments described below, as specific examples, the first ABT server 3a will be described as a server in a bus ABT system A that handles bus boarding and alighting processes (bus ABT server), and the second ABT server 3b will be described as a server in a railway ABT system B that handles ticket gate processing in railways (railway ABT server).

[0013] However, the multiple ABT servers included in the account issuance system 1 according to the embodiment may be any ABT system servers that can use code images indicating IDs in a common format, and may include ABT system servers operated by businesses in different industries. Furthermore, the ABT servers included in the account issuance system 1 according to the embodiment are not limited to two, but may include ABT system servers (ABT servers) operated by three or more businesses (or business claims).

[0014] Furthermore, the plurality of ABT servers in the account issuance system 1 according to the present embodiment may be servers of ABT systems (ABT servers) divided by regions or the like. For example, the first ABT server may be a server of an ABT system for railways in a first region, and the second ABT server may be a server of an ABT system for railways in a second region different from the first region.

[0015] The sales server 4 is a server that provides a site (sales site) for selling services and the like provided by the ABT system as products. The sales server 4 sells not only products provided by only one ABT system, but also products combining a plurality of services provided by a plurality of ABT systems. For example, the sales server 4 sells a product that combines a bus product, which is a service (e.g., a bus ticket) provided by the bus ABT system A including the bus ABT server 3a, and a railway product, which is a service (e.g., a railway ticket) provided by the railway ABT system B including the railway ABT server 3b. In the embodiment, the products sold by the sales server 4 are products handled by the hub function server 2, and issuance thereof is requested to each ABT server 3 via the hub function server 2.

[0016] Next, the configuration of the hub function server 2 as the hub server in the account issuance system 1 as the issuance processing system according to the embodiment will be described. Figure 2 is a block diagram showing a configuration example of the hub function server 2 in the account issuance system 1 according to the embodiment. As shown in Figure 2, the hub function server 2 includes a processor (first processor) 21, ROM 22, RAM 23, a data memory 24, and communication interfaces (I / F) (first communication units) 25, 26, and the like.

[0017] The processor 21 performs various processes such as arithmetic processing and control of each unit in the hub function server 2. The processor 21 implements various processing functions by executing programs. The processor 21 is, for example, a CPU. The processor 21 is connected to each unit in the hub function server 2 via an internal interface.

[0018] The ROM 22 is a non-rewritable nonvolatile memory. The ROM 22 stores, for example, programs and control data. The RAM 23 functions as a working memory or a buffer memory. The processor 21 uses the RAM 23 to execute programs stored in the ROM 22 or the data memory 24 to perform various processes.

[0019] The data memory 24 is a rewritable nonvolatile memory. For example, the data memory 24 is configured by a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The data memory 24 stores various data such as programs, control data, and setting information.

[0020] The data memory 24 has a storage area for storing a product master 241 that stores information on various products. The product master 241 is a database (product database) that stores information on various products handled by the hub function server 2. For example, the product master 241 stores information on products (ABT products) provided by a plurality of ABT systems included in the sales product, in association with identification information (product ID) indicating the product (sales product) sold by the sales server (sales site) 4.

[0021] For example, when handling a sales product that combines a bus product as a service provided by the bus ABT system A and a railway product as a service provided by the railway ABT system B, the product information of the bus product (e.g., bus product ID) and the product information of the railway product (e.g., railway product ID) are registered in the product master 241 in association with the identification information of the sales product (e.g., sales product ID).

[0022] Communication interfaces 25 and 26 are interfaces for communicating with external devices. Communication interface 25 is an interface for communicating with the sales server (sales site) 4. Communication interfaces 26 (26a, 26b, ...) are communication interfaces for communicating with the ABT servers 3 (3a, 3b, ...) of each ABT system. Communication interfaces 25 and 26 consist of one or more interfaces that perform data communication, for example, by wireless or wired communication. Furthermore, communication interfaces 25 and 26 may include interfaces that communicate with external devices via a network, or they may include interfaces that communicate with locally connected external devices.

[0023] In the hub function server 2 according to this embodiment, the communication interface 26 includes communication interfaces 26a, 26b, ... for communicating with the ABT servers 3 (3a, 3b, ...) of each ABT system. For example, communication interface 26a is an interface for communicating with ABT server 3a and is composed of a communication interface corresponding to the communication method provided by ABT server 3a. Communication interface 26b is an interface for communicating with ABT server 3b and is composed of a communication interface corresponding to the communication method provided by ABT server 3b.

[0024] The hub function server 2 can easily communicate with multiple ABT servers 3a, 3b, ... by implementing communication interfaces 26a, 26b, ... for each ABT server 3a, 3b, .... In other words, the issuance processing system according to the embodiment can minimize the impact of protocol changes when connecting the hub function server 2 with each ABT server 3a, 3b, ..., even if the communication protocol is not unified because each ABT server 3a, 3b, ... is an existing server, because the hub function server 2 is equipped with multiple communication interfaces.

[0025] Next, the configuration of the ABT server 3 (3a, 3b, ...) as an operational server in the account issuance system, which is an issuance processing system according to the embodiment, will be described. Figure 3 is a block diagram showing an example configuration of the ABT server 3 (3a, 3b, ...) in the account issuance system according to the embodiment. As shown in Figure 3, each ABT server 3 (3a, 3b, ...) has a processor (second processor) 31, ROM 32, RAM 33, data memory 34, and a communication interface (I / F) (second communication unit) 35, respectively.

[0026] The processor 31 implements various processing functions by executing programs. The processor 31 is, for example, a CPU. The processor 31 connects to various parts via internal interfaces. ROM32 functions as program memory for storing programs. ROM32 is a non-rewritable, non-volatile memory. RAM33 functions as working memory or buffer memory. The processor 31 performs various processes by executing programs stored in ROM32 or data memory 34 using RAM33.

[0027] The data memory 34 is a rewritable, non-volatile memory. For example, the data memory 34 is composed of a storage device such as an HDD (hard disk drive) or an SSD (solid state drive). The data memory 34 stores various types of data, such as control data, application programs (hereinafter also referred to as applications), configuration information, and image data.

[0028] The data memory 34 has a storage area for storing account data in the account database 341. The account database 341 stores account data for the ABT system, including the ABT server 3, to provide services. For example, when the bus ABT server 3a issues bus product a as a service provided by the bus ABT system A, it creates account data for providing bus product a and registers it in the account database 341. This enables the bus ABT system A to provide services as bus products to users based on the account data registered in the account database 341.

[0029] The communication interface 35 is an interface for communicating with external devices. The communication interface 35 consists of one or more interfaces that perform data communication, for example, wirelessly or via wired communication. The communication interface 35 may also include an interface for communicating with external devices via a network, or an interface for communicating with external devices connected serially. In the ABT server 3 according to this embodiment, the communication interface 35 also includes an interface for communicating with the hub function server 2 and an interface for communicating with each device in its own ABT system.

[0030] Next, we will describe an example of the configuration of the product master 241 of the hub function server 2, which serves as the hub server for the account issuance system 1, which serves as the issuance processing system according to the embodiment. Figure 4 illustrates an example of the configuration of the product master 241 in the hub function server 2 of the account issuance system 1 according to this embodiment. The product master 241 is stored in the data memory 24 of the hub function server 2, which is located between each ABT server 3 and the sales server 4. The product master 241 stores information about products provided by multiple ABT systems that are included in the various sales products handled by the hub function server 2.

[0031] In the configuration example shown in Figure 4, the product master 241 stores the product IDs of each ABT system that are included in the product being sold, in association with the product ID of the product being sold. The product master 241 is configured to register the product ID of each ABT system for each product sold by the sales server 4. Figure 4 illustrates that, for each product ID, which is the identification information for the product (bus product) provided by the bus ABT system (first ABT system) A, and the railway product ID, which is the identification information for the product (railway product) provided by the railway ABT system (second ABT system) B, are registered in the product master 241.

[0032] Furthermore, the product master 241 only needs to be a database that shows the products of each ABT system included in each sales product handled by the hub function server 2, and it is not necessary to register products from multiple ABT systems for every sales product. For example, if a sales product does not include products from multiple ABT systems (i.e., the sales product includes only products from one ABT system), the product master 241 only needs to register the product ID of one ABT system for that sales product.

[0033] Furthermore, in the configuration example shown in Figure 4, the product master 241 also stores information indicating the ABT server that issues IDq, which is the identification information of an account commonly used for each sales product ID. The IDq for each product ID may be issued by a specific ABT server or by the hub function server 2. For example, as shown in Figure 4, the product master 241 may register information indicating the server that issues the IDq for each product ID. In this case, the hub function server 2 can refer to the product master 241 to identify the IDq for each product. Note that if the IDq for all products is to be issued by a fixed ABT server or the hub function server 2, it is not necessary to register information indicating the server that issues the IDq for each product in the product master 241.

[0034] Next, we will describe an example of the configuration of the account database 341 that each ABT server 3 has in the account issuance system 1 according to the embodiment. Figure 5 illustrates an example of the configuration of the account database 341 in each ABT server 3 in the account issuance system 1 according to this embodiment. The account database 341 provided on each ABT server 3 is a database that stores account data used to provide services (products) on its own ABT system. For example, the account database 341 on the bus ABT server 3a stores account data used on the bus ABT system A. The account database 341 on the railway ABT server 3b stores account data used on the railway ABT system B.

[0035] In the configuration example shown in Figure 5, the account database 341 stores information such as IDq, product ID, validity, and status for each account data. When each ABT server 3 issues an account for a single product, this information is sequentially registered in the account database 341 as one account data.

[0036] IDq is the identification information for an account. IDq is provided to the user as a code image. IDq is composed of a predetermined format that each ABT system in the issuing processing system supports, and the code image representing IDq conforms to a predetermined standard that each ABT system device can read as IDq. For example, each device in each ABT system reads the IDq represented by the code image and supplies a service execution request to the ABT server 3 along with the read IDq. The ABT server 3 supplies service execution instructions to each device based on the account data including the IDq read by the devices in the ABT system.

[0037] The product ID (product ID in the relevant ABT system) is identification information that indicates products such as services provided by each ABT system. For example, the product ID registered in the account database 341 of the bus ABT server 3a is identification information for bus products (e.g., bus tickets) provided by the bus ABT system A. Similarly, the product ID registered in the account database 341 of the railway ABT server 3b is identification information for railway products (e.g., railway tickets) provided by the railway ABT system B.

[0038] Validity (validity information) is information that indicates the content of products such as services provided in the ABT system. For example, validity information indicates the conditions and scope under which the services (products) provided by the account identified by the corresponding IDq are valid. As a specific example, validity information indicates the sections and periods during which boarding and alighting are permitted on buses or trains in which the ABT system is operated.

[0039] The status (status information) is information that indicates the usage status of the product (service) in question. For example, status information may include information indicating the location and time of boarding and alighting using the account identified by the corresponding IDq. For example, the ABT server 3 identifies the content of the service (product) that can be provided to the account identified by the IDq based on the combination of the validity information and status information corresponding to the IDq.

[0040] Next, a first example of operation in the account issuance system 1, which can issue multiple accounts including a common ID according to the embodiment, will be described. Figure 6 is a sequence diagram illustrating the flow of a first operational example in the account issuance system 1 according to the embodiment. First, the user accesses the sales server (sales site) 4 using a terminal device they operate and performs an operation to purchase the desired product. The sales server 4, which provides the sales site, sells the product in response to instructions from the terminal device operated by the user. Here, the sales server 4 accepts the sale of products (products for sale), including bus products and railway products, that the user instructs to purchase using the terminal device.

[0041] When the sales server 4 receives a request to sell a product specified by the user, it sends an issuance request for that product to the hub function server 2 (step ST11). For example, the sales server 4 identifies the product ID (sales product ID), which is the identification information of the product that the user has instructed to purchase, and sends an issuance request for that product, specifying the sales product ID, to the hub function server 2.

[0042] The hub function server 2 receives issuance requests from the sales server 4 via the communication interface 25. When the processor 21 of the hub function server 2 receives an issuance request from the sales server 4, it identifies the product IDs of all products provided by each ABT system included in the sales product based on the sales product ID specified in the received issuance request (step ST12). For example, the processor 21 refers to the product master 241 to identify the product IDs of each ABT system corresponding to the sales product ID for which issuance was requested.

[0043] Furthermore, the processor 21 of the hub function server 2 identifies an ABT server 3 as the first operational server that issues an IDq, which is account identification information for the sales product specified in the received issuance request (step ST13). For example, the processor 21 refers to the product master 241 and identifies one ABT server 3 that issues an IDq based on the information indicating the IDq issuer set for the sales product ID for which issuance was requested. Also, if a specific ABT server that issues IDqs for sales products for which issuance was requested from the sales site has been pre-configured, the processor 21 sets the pre-configured ABT server 3 as the IDq issuer (first ABT server, first operational server).

[0044] In the example shown in Figure 6, the sales products requested by the sales site include products from the bus ABT system (first ABT system) A (bus products) and products from the railway ABT system (second ABT system) B (railway products), and the bus ABT server 3a is set as the IDq issuer (first operation server) that issues the IDq. In this case, the processor 21 of the hub function server 2 identifies the bus ABT server (first ABT server) 3a as the IDq issuer.

[0045] The processor 21 of the hub function server 2 identifies the bus product ID of the bus product of the bus ABT system A included in the product being sold, assuming the bus ABT server 3a is the IDq issuer. Once the processor 21 has identified the bus product ID corresponding to the product ID being sold, it creates an issue request that requests the issuance of an IDq by specifying the bus product ID, which is the identification information of the product in the bus ABT system A corresponding to the product ID being sold.

[0046] Furthermore, if there is no bus product (product of the first ABT system) corresponding to the sales product ID, the processor 21 may create an issuance request that requests the issuance of IDq without specifying a bus product ID. For example, if the sales product includes only railway products (and does not include bus products), the processor 21 creates an issuance request that requests the bus ABT server 3a to issue IDq without creating an account for the bus ABT system (without specifying a bus product ID).

[0047] Furthermore, the processor 21 of the hub function server 2 may include information indicating whether or not an issuance process (account creation) has already been performed on other ABT servers when making an issuance request to the bus ABT server 3a, which is the IDq issuer. For example, if the products for sale include both bus products and railway products, the processor 21 may create an issuance request that requests the issuance of an IDq (common IDq) to be used in other ABT systems as well, and also requests the creation of an account for the bus ABT system. Alternatively, if the products for sale include only bus products, the processor 21 may create an issuance request that requests the issuance of an IDq to be used only in the bus ABT system A, and also requests the creation of an account for the bus ABT system.

[0048] When the processor 21 of the hub function server 2 creates an issuance request specifying the bus product ID of the bus ABT (first ABT) system included in the sales product ID, it sends the issuance request to the bus ABT server 3a, which is the IDq issuer, via the communication interface 26a (step ST14). Here, the processor 21 creates an issuance request specifying the bus product ID of the bus product for a sales product that includes both bus products and railway products, and sends the issuance request to the bus ABT server 3a via the communication interface 26a.

[0049] The bus ABT server 3a receives an issuance request from the hub function server 2 via the communication interface 35. When the processor 31 of the bus ABT server 3a receives an issuance request from the hub function server 2, it issues an IDq to be used as account identification information (step ST15) and generates a code image showing the IDq (step ST16). The processor 31 shall create the IDq based on a predetermined standard that each ABT system corresponds to. For example, each ABT system A, B, ... in the account issuance system 1 shall correspond to a predetermined standard (e.g., CJRC) which is a predetermined code format (however, the hub function server 2 does not have to correspond to the predetermined standard). In this case, the processor 31 generates a code image showing the issued IDq in accordance with the predetermined standard.

[0050] When the processor 31 of the bus ABT server 3a issues an IDq, it creates an account that makes the bus product indicated by the bus product ID specified in the issuance request available with that IDq (step ST17). The creation of the account in the bus ABT server 3a corresponds to the issuance process in the bus ABT system A that makes the service as a bus product available with that IDq.

[0051] The processor 31 of the bus ABT server 3a registers account data, including IDq, in the account database 341 as part of account creation. For example, as shown in Figure 5, the processor 31 of the bus ABT server 3a creates account data that includes information such as the bus product ID, validity information, and status information, associated with the issued IDq, and registers it in the account database 341. After registering the account data for the IDq in the account database 341, the processor 31 of the bus ABT server 3a provides the bus product service to the user who presents the code image showing the IDq in the bus ABT system A.

[0052] When the bus ABT server 3a creates an account, the processor 31 uses the issued IDq to determine whether an issuance process (account creation) is also required in other ABT systems (in this case, the railway ABT system) (step ST18). For example, the bus ABT server 3a's processor 31 determines whether an issuance process is required in other ABT servers based on the information attached to the issuance request from the hub function server 2.

[0053] If the processor 31 of the bus ABT server 3a does not require issuance processing in other ABT systems (step ST18, NO), it proceeds to step ST24. In step ST24, the processor 31 of the bus ABT server 3a sends response data to the hub function server 2 in response to the issuance request from the hub function server 2, which includes information indicating the completion of issuance of the bus product specified by the bus product ID and a code image indicating IDq.

[0054] The processor 31 of the bus ABT server 3a sends an issuance completion notification to the hub function server 2, including the IDq and a code image representing the IDq, if issuance processing is required in another ABT system (railway ABT system) (step ST18, YES) (step ST19). For example, the processor 31 of the bus ABT server 3a sends response data to the hub function server 2 as a response to an issuance request from the hub function server 2, including information indicating the completion of issuance of the bus product specified by the bus product ID, the IDq, and a code image representing the IDq. However, since the IDq is information that can be identified from the code image, the processor 31 of the bus ABT server 3a may send an issuance completion notification to the hub function server 2 that includes the code image but does not include the IDq.

[0055] The hub function server 2 receives an issuance completion notification from the bus ABT server 3a as a response to the issuance request via the communication interface 26a. When the processor 21 of the hub function server 2 receives the issuance completion notification from the bus ABT server 3a, which includes the IDq and a code image indicating the IDq, it stores the received code image as the code image of the product for sale (step ST20). For example, the processor 21 stores the code image and the IDq in the data memory 24 or RAM 23.

[0056] When the processor 21 of the hub function server 2 obtains the IDq issued by the bus ABT server 3a, it creates an issuance request specifying the railway product ID and IDq, which are the identification information of the railway ABT system B product corresponding to the sales product ID. When the processor 21 of the hub function server 2 creates an issuance request specifying the railway product ID and IDq (the IDq issued by the bus ABT server 3a) of the railway product included in the sales product, it sends the issuance request to the railway ABT server 3b via the communication interface 26b (step ST21).

[0057] The railway ABT server 3b receives an issuance request from the hub function server 2 via the communication interface 35, specifying the railway product ID and IDq. When the processor 31 of the railway ABT server 3b receives an issuance request from the hub function server 2 specifying IDq, it creates an account that makes the railway product indicated by the railway product ID specified in the issuance request available with that IDq, without issuing the IDq itself (step ST22). The creation of the account in the railway ABT server 3b corresponds to the issuance process in the railway ABT system B that makes the service as a railway product available with that IDq.

[0058] The processor 31 of the railway ABT server 3b registers account data, including the IDq (the IDq issued by the bus ABT server 3a), in the account database 341 as part of account creation. The account data registered in the account database 341 is information such as product ID, validity information, and status information, associated with the IDq, as shown in Figure 5. After registering the account data in the account database 341, the processor 31 of the railway ABT server 3b provides the railway product service to the user who presents the code image showing the IDq in the railway ABT system B.

[0059] When the processor 31 of the railway ABT server 3b creates an account, it sends response data to the hub function server 2 in response to the issuance request from the hub function server 2, which includes information indicating that the issuance of the railway product specified by the railway product ID has been completed (step ST23).

[0060] The hub function server 2 receives an issuance completion notification from the railway ABT server 3b via the communication interface 26b as a response to an issuance request specifying the railway product ID and IDq. When the processor 21 of the hub function server 2 receives the issuance completion notification from the railway ABT server 3b, it determines that the issuance process for all products included in the sales product for which an issuance request was received from the sales server 4 has been completed.

[0061] When the processor 21 of the hub function server 2 determines that the issuance process for all products included in the sales product for which an issuance request has been received from the sales server 4 has been completed, it sends an issuance completion notification to the sales server 4, which includes a code image showing the IDq generated by the bus ABT server 3a as the IDq of the sales product (step ST25).

[0062] Furthermore, if the processor 21 of the hub function server 2 receives an issuance completion notice including a code image from the bus ABT server 3a as step ST24, it determines that the issuance process for all products included in the sales product for which the sales server 4 has requested the issuance has been completed. In other words, if the sales product does not include any products of the railway ABT system, the processor 21 of the hub function server 2 determines that the issuance of the sales product is complete when it receives an issuance completion notice including a code image from the bus ABT server 3a. In this case, the processor 21 of the hub function server 2 sends an issuance completion notice to the sales server 4 including a code image indicating the IDq obtained from the bus ABT server 3a as the IDq of the sales product (step ST25).

[0063] The sales server 4 sends a request to issue a product specified by the user to the hub function server 2, and then waits for a completion notification from the hub function server 2. As part of the process in step ST25 above, the sales server 4 receives the completion notification from the hub function server 2, which includes a code image for the product in question. The sales server 4 notifies the user of the code image for the product in question, which it received along with the completion notification from the hub function server 2.

[0064] Through the above process, the hub function server can integrate (unify) the account identification information (IDq) for sales products, including bus and rail products, offered by multiple different ABT servers sold by sales server 4, into a single IDq, and issue a single code image representing the IDq for that sales product. As a result, the sales site only needs to provide the user with a single code image for sales products, even if the sales product includes multiple services (products) provided by multiple different ABT systems. Furthermore, the user can use multiple services provided by multiple different ABT systems using a single code image purchased from the sales site.

[0065] As described above, the hub function server according to the first operational example of the embodiment, when a single sales product for which an issuance request has been received from a sales site includes products from multiple different ABT systems, causes one of the ABT servers to issue a single unified (common) account identification information (IDq) for the sales product, and causes each ABT server of each ABT system that provides each product included in the sales product to create an account associated with that single IDq.

[0066] This allows an IDq issued by any one ABT server in the issuance processing system to be integrated and linked as the IDq for account data in multiple different ABT systems. Even when providing services for a single product across multiple ABT systems, a single code image representing the IDq for the product can be used across multiple ABT systems. As a result, a single code image usable across multiple ABT systems can be provided to the user, allowing the user to receive various services with a single code image without having to be aware of the different ABT systems providing those services.

[0067] Next, a second example of operation in the account issuance system 1, which can issue multiple accounts including a common ID according to the embodiment, will be described. Figure 7 is a sequence diagram illustrating the flow of a second operational example in the account issuance system 1 according to the embodiment. In the first operational example, one of the ABT servers 3 issues the IDq, but in the second operational example, the hub function server 2 issues the IDq. However, in the second operational example, the hub function server 2 is capable of corresponding to a predetermined standard for the IDq handled by each ABT system and generating a code image that indicates the IDq usable by each ABT system.

[0068] First, the user accesses the sales server (sales site) 4 using a terminal device they operate and performs an operation to purchase the desired product. The sales server 4, which provides the sales site, sells the product in response to instructions from the terminal device operated by the user. Here, the sales server 4 accepts the sale of products (products for sale), including bus products and railway products, that the user instructs to purchase using the terminal device.

[0069] When the sales server 4 receives a request from a user to sell a product, it sends an issuance request for that product to the hub function server 2 (step ST31). For example, the sales server 4 identifies the product ID (sales product ID), which is the identification information of the product, and sends an issuance request for that product, specifying the sales product ID, to the hub function server 2.

[0070] The hub function server 2 receives issuance requests from the sales server 4 via the communication interface 25. When the processor 21 of the hub function server 2 receives an issuance request from the sales server 4, it identifies the product ID of each ABT system product included in the sales product based on the sales product ID specified in the received issuance request (step ST32). The processor 21 refers to the product master 241 to identify the product ID of each ABT system corresponding to the sales product ID for which issuance was requested.

[0071] Furthermore, the processor 21 of the hub function server 2 issues an IDq for a sales product if the sales product ID specified in the issuance request from the sales server 4 is an issueable product (step ST33), and generates a code image that encodes the issued IDq (step ST34). The IDq issued by the hub function server 2 is an account identification information used in common by each ABT system (here, bus ABT system A and railway ABT system B). The code image showing the IDq is composed of a predetermined format that can be used by each ABT system.

[0072] In the example shown in Figure 7, the sales products requested by the sales site include bus products from bus ABT system A and railway products from railway ABT system B. In this case, the processor 21 of the hub function server 2 creates an issuance request specifying the IDq issued for the sales product and the bus product ID of the product in bus ABT system A that corresponds to the sales product ID.

[0073] The processor 21 of the hub function server 2 creates an issuance request specifying the product ID of any one of the products included in the sales product that is provided by an ABT system and the IDq issued for that product, and sends the issuance request to the ABT server 3 that provides the product with the specified product ID via the communication interface 26 (step ST35). Here, the processor 21 of the hub function server 2 creates an issuance request specifying the bus product ID and IDq of the bus product included in the sales product, and sends the issuance request to the bus ABT server 3a via the communication interface 26a.

[0074] The bus ABT server 3a receives an issuance request from the hub function server 2 via the communication interface 35, specifying a bus product ID and IDq. When the bus ABT server 3a's processor 31 receives an issuance request from the hub function server 2 specifying an IDq, it creates an account that makes the bus product indicated by the bus product ID specified in the issuance request available with that IDq, without issuing the IDq itself (step ST36). The creation of the account in the bus ABT server 3a corresponds to the issuance process in the bus ABT system A that makes the service as a bus product available with that IDq.

[0075] The processor 31 of the bus ABT server 3a registers account data, including the IDq (the IDq issued by the hub function server 2), in the account database 341 as part of account creation. The account data registered in the account database 341 is information such as product ID, validity information, and status information, associated with the IDq, as shown in Figure 5. After registering the account data in the account database 341, the bus ABT server 3a provides the bus product service to the user who presents a code image showing the IDq in the bus ABT system A.

[0076] When the processor 31 of the bus ABT server 3a creates an account for IDq specified in the issuance request from the hub function server 2, it sends response data to the hub function server 2 as a response to the issuance request, which includes information indicating that the bus product specified by the bus product ID has been issued (step ST37).

[0077] When the processor 21 of the hub function server 2 receives a notification of completion of issuance from the bus ABT server 3a, it uses the IDq issued for the sales product to determine whether account creation (issuance process) is also required in other ABT systems (in this case, the railway ABT system) (step ST38). For example, the processor 21 of the hub function server 2 determines whether issuance processing is required in other ABT servers based on whether the sales product for which issuance request was received from the sales server 4 includes products from other ABT systems (other than ABT systems for which an account has already been created).

[0078] If the processor 31 of the hub function server 2 determines that issuance processing is required on another ABT server (step ST38, YES), it identifies the railway product ID of the railway product provided by the railway ABT system B as a product of another ABT system included in the product for sale. In this case, the processor 31 of the hub function server 2 determines that issuance processing is required for the railway product provided by the railway ABT system B and identifies the railway product ID of the railway product included in the product for sale.

[0079] The processor 21 of the hub function server 2 identifies the railway product ID of a railway product included in the sales product and creates an issuance request specifying that railway product ID and the IDq issued for that sales product. After creating the issuance request specifying the railway product ID and IDq, the processor 21 of the hub function server 2 sends the issuance request to the railway ABT server 3b via the communication interface 26b (step ST39).

[0080] The railway ABT server 3b receives an issuance request from the hub function server 2 via the communication interface 35, specifying the railway product ID and IDq. When the processor 31 of the railway ABT server 3b receives an issuance request from the hub function server 2 specifying IDq, it creates an account that makes the railway product indicated by the railway product ID specified in the issuance request available with that IDq, without issuing the IDq itself (step ST40). The creation of the account in the railway ABT server 3b corresponds to the issuance process in the railway ABT system B that makes the service as a railway product available with that IDq.

[0081] The processor 31 of the railway ABT server 3b registers account data, including the IDq (the IDq issued by the hub function server 2), in the account database 341 as part of account creation. The account data registered in the account database 341 is information such as product ID, validity information, and status information, associated with the IDq, as shown in Figure 5. After registering the account data associated with the IDq in the account database 341, the railway ABT server 3b provides the service as a railway product to the user who presents the code image showing the IDq.

[0082] When the processor 31 of the railway ABT server 3b creates an account for IDq specified in the issuance request from the hub function server 2, it sends response data to the hub function server 2 as a response to the issuance request, which includes information indicating that the issuance of the railway product specified by the railway product ID has been completed (step ST41).

[0083] The hub function server 2 receives an issuance completion notification from the railway ABT server 3b via the communication interface 26b as a response to an issuance request specifying the railway product ID and IDq. When the processor 21 of the hub function server 2 receives the issuance completion notification from the railway ABT server 3b, it determines that the issuance process for all products included in the sales product for which an issuance request was received from the sales server 4 has been completed.

[0084] If the processor 21 of the hub function server 2 determines that the issuance process for all products included in the sales product for which an issuance request has been received from the sales server 4 has been completed, or if it determines that issuance processing by other ABT systems is not required (step ST38, NO), it sends an issuance completion notification to the sales server 4, which includes a code image showing the IDq generated by the hub function server 2 as the IDq of the sales product (step ST42).

[0085] Furthermore, if the products for sale include ABT system products other than the bus ABT system and the railway ABT system, the processor 21 of the hub function server 2 should perform the same operation as in steps ST39-41 above, specifying the IDq issued by the hub function server 2 to the ABT servers 3 of those ABT systems to create accounts (issue processes).

[0086] As described above, the hub function server according to the second operational example of the embodiment issues one account identification information (IDq) for one sales product for which an issuance request has been received from the sales site. If the sales product includes products from multiple different ABT systems, it causes each ABT server of each ABT system that provides each product included in the sales product to create an account associated with the one IDq issued for the sales product.

[0087] This allows a single IDq issued by the hub server to link account data across multiple different ABT systems. Even when providing services for a single product across multiple ABT systems, a single code image representing the IDq for that product can be used across multiple ABT systems. As a result, a single code image usable across multiple ABT systems can be provided to the user, allowing them to access various services with a single code image without having to be aware of the different ABT systems providing those services.

[0088] Next, a third example of operation in the account issuance system 1, which can issue multiple accounts including a common ID according to the embodiment, will be described. Figure 8 is a sequence diagram illustrating the flow of a first operational example in the account issuance system 1 according to the embodiment. First, the user accesses the sales server (sales site) 4 using a terminal device they operate and performs an operation to purchase the desired product. The sales server 4, which provides the sales site, sells the product in response to instructions from the terminal device operated by the user. Here, the sales server 4 accepts the sale of products (products for sale), including bus products and railway products, that the user instructs to purchase using the terminal device.

[0089] When the sales server 4 receives a request to sell a product specified by the user, it sends an issuance request for that product to the hub function server 2 (step ST51). For example, the sales server 4 identifies the product ID (sales product ID), which is the identification information of the product that the user has instructed to purchase, and sends an issuance request for that product, specifying the sales product ID, to the hub function server 2.

[0090] The hub function server 2 receives issuance requests from the sales server 4 via the communication interface 25. When the processor 21 of the hub function server 2 receives an issuance request from the sales server 4, it identifies the product IDs of all products provided by each ABT system included in the sales product based on the sales product ID specified in the received issuance request (step ST52). For example, the processor 21 refers to the product master 241 to identify the product IDs of each ABT system corresponding to the sales product ID for which issuance was requested.

[0091] Furthermore, the processor 21 of the hub function server 2 identifies an ABT server 3 as the first operational server that issues an IDq, which is account identification information for the sales product specified in the received issuance request (step ST53). For example, the processor 21 refers to the product master 241 and identifies one ABT server 3 that issues an IDq based on the information indicating the IDq issuer set for the sales product ID for which issuance was requested. Also, if a specific ABT server that issues IDqs for sales products for which issuance was requested from the sales site has been pre-configured, the processor 21 sets the pre-configured ABT server 3 as the IDq issuer (first ABT server, first operational server).

[0092] In the example shown in Figure 8, the sales products requested by the sales site include products from the bus ABT system (first ABT system) A (bus products) and products from the railway ABT system (second ABT system) B (railway products), and the bus ABT server 3a is set as the IDq issuer (first operation server) that issues the IDq. In this case, the processor 21 of the hub function server 2 identifies the bus ABT server (first ABT server) 3a as the IDq issuer.

[0093] The processor 21 of the hub function server 2 identifies the bus product ID of the bus product of the bus ABT system A included in the product being sold, assuming the bus ABT server 3a is the IDq issuer. Once the processor 21 has identified the bus product ID corresponding to the product ID being sold, it creates an issue request that requests the issuance of an IDq by specifying the bus product ID, which is the identification information of the product in the bus ABT system A corresponding to the product ID being sold.

[0094] Furthermore, if there is no bus product (product of the first ABT system) corresponding to the sales product ID, the processor 21 may create an issuance request that requests the issuance of IDq without specifying a bus product ID. For example, if the sales product includes only railway products (and does not include bus products), the processor 21 creates an issuance request that requests the bus ABT server 3a to issue IDq without creating an account for the bus ABT system (without specifying a bus product ID).

[0095] Furthermore, the processor 21 of the hub function server 2 may include information indicating whether or not an issuance process (account creation) has already been performed on other ABT servers when making an issuance request to the bus ABT server 3a, which is the IDq issuer. For example, if the products for sale include both bus products and railway products, the processor 21 may create an issuance request that requests the issuance of an IDq (common IDq) to be used in other ABT systems as well, and also requests the creation of an account for the bus ABT system. Alternatively, if the products for sale include only bus products, the processor 21 may create an issuance request that requests the issuance of an IDq to be used only in the bus ABT system A, and also requests the creation of an account for the bus ABT system.

[0096] When the processor 21 of the hub function server 2 creates an issuance request specifying the bus product ID of the bus ABT (first ABT) system included in the sales product ID, it sends the issuance request to the bus ABT server 3a, which is the IDq issuer, via the communication interface 26a (step ST54). Here, the processor 21 creates an issuance request specifying the bus product ID of the bus product for a sales product that includes both bus products and railway products, and sends the issuance request to the bus ABT server 3a via the communication interface 26a.

[0097] The bus ABT server 3a receives an issuance request from the hub function server 2 via the communication interface 35. When the processor 31 of the bus ABT server 3a receives an issuance request from the hub function server 2, it issues an IDq to be used as account identification information (step ST55) and generates a code image showing the IDq (step ST56). The processor 31 shall create the IDq based on a predetermined standard that each ABT system corresponds to. For example, each ABT system A, B, ... in the account issuance system 1 shall correspond to a predetermined standard (e.g., CJRC) which is a predetermined code format (however, the hub function server 2 does not have to correspond to the predetermined standard). In this case, the processor 31 generates a code image showing the issued IDq in accordance with the predetermined standard.

[0098] When the processor 31 of the bus ABT server 3a issues an IDq, it creates an account that makes the bus product indicated by the bus product ID specified in the issuance request available with that IDq (step ST57). The creation of the account in the bus ABT server 3a corresponds to the issuance process in the bus ABT system A that makes the service as a bus product available with that IDq.

[0099] The processor 31 of the bus ABT server 3a registers account data, including IDq, in the account database 341 as part of account creation. For example, as shown in Figure 5, the processor 31 of the bus ABT server 3a creates account data that includes information such as the bus product ID, validity information, and status information, associated with the issued IDq, and registers it in the account database 341. After registering the account data for the IDq in the account database 341, the processor 31 of the bus ABT server 3a provides the bus product service to the user who presents the code image showing the IDq in the bus ABT system A.

[0100] When the processor 31 of the bus ABT server 3a creates an account, it sends an issuance completion notification to the hub function server 2 that includes the IDq registered to the account and a code image representing the IDq (step ST58). However, since the IDq is information that can be identified from the code image, the processor 31 of the bus ABT server 3a may send an issuance completion notification to the hub function server 2 that includes the code image but does not include the IDq.

[0101] The hub function server 2 receives an issuance completion notification from the bus ABT server 3a as a response to the issuance request via the communication interface 26a. When the processor 21 of the hub function server 2 receives the issuance completion notification from the bus ABT server 3a, which includes the IDq and a code image indicating the IDq, it stores the received code image as the code image of the product for sale (step ST59). For example, the processor 21 stores the code image and the IDq in the data memory 24 or RAM 23.

[0102] When the processor 21 of the hub function server 2 obtains the IDq issued by the bus ABT server 3a, it determines whether account creation (issuance process) is required in other ABT systems (in this case, the railway ABT system) for the product being sold using the IDq issued by the bus ABT server 3a (step ST60). For example, the processor 21 of the hub function server 2 determines whether an issuance process is required in other ABT servers based on whether the product for which an issuance request has been received from the sales server 4 includes products from other ABT systems (other than ABT systems for which an account has already been created).

[0103] If the processor 21 of the hub function server 2 determines that there are no products other than those in the ABT system for which an account has already been created (step ST60, NO), it determines that the issuance process for all products included in the sales product for which an issuance request has been received from the sales server 4 is complete, and proceeds to step ST64.

[0104] If the processor 31 of the hub function server 2 determines that issuance processing is required on another ABT server (step ST60, YES), it identifies the railway product ID of the railway product provided by the railway ABT system B as a product of another ABT system included in the product for sale. In this case, the processor 31 of the hub function server 2 determines that issuance processing is required for the railway product provided by the railway ABT system B and identifies the railway product ID of the railway product included in the product for sale.

[0105] The processor 21 of the hub function server 2 identifies the railway product ID of a railway product included in the sales product and creates an issuance request specifying that railway product ID and the IDq issued by the bus ABT server 3a for that sales product. After creating the issuance request specifying the railway product ID and IDq, the processor 21 of the hub function server 2 sends the issuance request to the railway ABT server 3b via the communication interface 26b (step ST61).

[0106] The railway ABT server 3b receives an issuance request from the hub function server 2 via the communication interface 35, specifying the railway product ID and IDq. When the processor 31 of the railway ABT server 3b receives an issuance request from the hub function server 2 specifying IDq, it creates an account that makes the railway product indicated by the railway product ID specified in the issuance request available with that IDq, without issuing the IDq itself (step ST62). The creation of the account in the railway ABT server 3b corresponds to the issuance process in the railway ABT system B that makes the service as a railway product available with that IDq.

[0107] The processor 31 of the railway ABT server 3b registers account data, including the IDq (the IDq issued by the hub function server 2), in the account database 341 as part of account creation. The account data registered in the account database 341 is information such as product ID, validity information, and status information, associated with the IDq, as shown in Figure 5. After registering the account data associated with the IDq in the account database 341, the railway ABT server 3b provides the service as a railway product to the user who presents the code image showing the IDq.

[0108] When the processor 31 of the railway ABT server 3b creates an account for IDq specified in the issuance request from the hub function server 2, it sends response data to the hub function server 2 as a response to the issuance request, which includes information indicating that the issuance of the railway product specified by the railway product ID has been completed (step ST63).

[0109] The hub function server 2 receives an issuance completion notification from the railway ABT server 3b via the communication interface 26b as a response to an issuance request specifying the railway product ID and IDq. When the processor 21 of the hub function server 2 receives the issuance completion notification from the railway ABT server 3b, it determines that the issuance process for all products included in the sales product for which an issuance request was received from the sales server 4 has been completed.

[0110] When the processor 21 of the hub function server 2 determines that the issuance process for all products included in the sales product for which an issuance request has been received from the sales server 4 has been completed, it sends an issuance completion notification to the sales server 4, which includes a code image showing the IDq generated by the bus ABT server 3a as the IDq of the sales product (step ST64).

[0111] The sales server 4 sends a request to issue a product specified by the user to the hub function server 2, and then waits for a completion notification from the hub function server 2. As part of the process in step ST25 above, the sales server 4 receives the completion notification from the hub function server 2, which includes a code image for the product in question. The sales server 4 notifies the user of the code image for the product in question, which it received along with the completion notification from the hub function server 2.

[0112] Through the above process, the hub function server can integrate (unify) the account identification information (IDq) for sales products, including bus and rail products, offered by multiple different ABT servers sold by sales server 4, into a single IDq, and issue a single code image representing the IDq for that sales product. As a result, the sales site only needs to provide the user with a single code image for sales products, even if the sales product includes multiple services (products) provided by multiple different ABT systems. Furthermore, the user can use multiple services provided by multiple different ABT systems using a single code image purchased from the sales site.

[0113] As described above, in the third operational example of the embodiment, when a single sales product for which an issuance request has been received from a sales site includes products from multiple different ABT systems, the hub function server causes one specific ABT server to issue a single unified (common) account identification information (IDq) for the sales product, and after obtaining the single IDq issued by one ABT server, it causes the ABT servers of each ABT system that provide each product included in the sales product to create an account associated with the single IDq issued by the specific ABT server.

[0114] This allows an IDq issued by any one ABT server in the issuance processing system to be integrated and linked as the IDq for account data in multiple different ABT systems. Even when providing services for a single product across multiple ABT systems, a single code image representing the IDq for the product can be used across multiple ABT systems. As a result, a single code image usable across multiple ABT systems can be provided to the user, allowing the user to receive various services with a single code image without having to be aware of the different ABT systems providing those services.

[0115] Furthermore, in the third operational example, the processor 21 of the hub function server 2 determines whether or not other ABT servers have processed the issuance based on whether or not the product includes products from other ABT systems for which an account has already been created, after the ABT server of a specific ABT system has issued an IDq for the product being sold. Therefore, in the third operational example, the addition and modification of processing in existing ABT servers can be minimized, and even when applying this issuance processing system to existing ABT servers, the changes to programs, etc., can be minimized.

[0116] As detailed above, according to the embodiment, the hub function server can integrate (unify) account identification information (IDq) for sales products, including bus and rail products, provided by multiple different ABT servers sold by the sales server (sales site) 4, into one, and issue a single code image indicating the IDq for the sales product. As a result, the sales site only needs to provide the user with a single code image for a sales product, even if the sales product includes multiple services (products) provided by multiple different ABT systems. Furthermore, the user can use multiple services provided by multiple different ABT systems using a single code image purchased from the sales site.

[0117] Furthermore, each of the processes described above can be executed by several software programs. Therefore, the above processes can be easily implemented by installing and executing these programs on the issuing system (hub function server and each ABT server) via a computer-readable storage medium containing several programs that execute the procedures of the above processes. For example, the hub function server and each ABT server may install the programs by downloading them via the network and storing the downloaded programs. Alternatively, the hub function server and each ABT server may install the programs by reading them from various information storage media and storing the read programs.

[0118] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. [Explanation of Symbols]

[0119] 1…Account Issuance System 2…Hub function server (hub server) 3…ABT Server 3a...First ABT server (bus ABT server) 3b...Second ABT server (Railway ABT server) A, B... ABT System 4…Sales server (sales site) 21…Processor (first processor) 22…ROM 23…RAM 24...Data memory 241... Product Master (Product Database) 25…Communication Interface 26 (26a, 26b, ...) ... Communication interface (first communication unit) 31…Processor (second processor) 32...ROM 33…RAM 34…Data memory 341…Account Database 35...Communication interface (second communication unit).

Claims

1. A communication unit that communicates with multiple ABT servers provided in each of the multiple ABT systems, A processor that identifies ABT products issued by each ABT server included in a single product for sale, sends an issuance request for each ABT product to each ABT server to create an account for each ABT product containing a single ID for the product for sale, and provides information indicating the ID to the source of the issuance request for the product for sale. A hub server.

2. The aforementioned plurality of ABT servers include a first ABT server and a second ABT server, The aforementioned processor, A request to issue a first ABT product, which is included in the product for sale and issued by the first ABT server, is sent to the first ABT server. The system obtains the ID issued by the first ABT server and sends a request to the second ABT server to issue a second ABT product, specifying the ID. The hub server according to claim 1.

3. The processor issues the ID for the product being sold and sends an issuance request for each ABT product included in the product being sold to the respective ABT server, specifying the ID. The hub server according to claim 1.

4. The processor determines whether the product for sale has a second ABT product issued by the second ABT server, and if it determines that the product for sale has a second ABT product, it sends a request to the second ABT server to issue the second ABT product, specifying the ID issued by the first ABT server. The hub server according to claim 2.

5. The processor provides the requester of the sales product with a code image representing the ID as information representing the ID. The hub server according to claim 1.

6. The aforementioned communication unit communicates with the sales server that provides the sales site for the aforementioned products, The processor receives a request to issue the sales product from the sales server and transmits the code image to the sales server. The hub server according to claim 5.

7. It has a memory that stores a database containing information indicating ABT products included in the aforementioned sales products, The processor identifies the ABT products issued by each ABT server included in the sales product based on the database. The hub server according to claim 1.

8. It has a memory that stores information indicating the first ABT server that issues the ID in association with the aforementioned sales product, The processor identifies the first ABT server that issues the ID based on the information stored in the memory. The hub server according to claim 2.

9. The first ABT server and the second ABT server are servers that manage accounts using IDs conforming to a predetermined standard. The hub server according to claim 2.

10. An issuance processing system having multiple ABT servers and a hub server, each of which is provided in multiple ABT systems, The aforementioned hub server is A communication unit that communicates with multiple ABT servers, The system includes a first processor that identifies ABT products issued by each ABT server included in a single product for sale, sends an issuance request for each ABT product to each ABT server to create an account for each ABT product containing a single ID for the product for sale, and provides information indicating the ID to the source of the issuance request for the product for sale. Each of the aforementioned ABT servers is: A second communication unit that communicates with the aforementioned hub server, A second processor that creates an account for an ABT product including the ID in response to an ABT product issuance request specifying the ID received from the hub server, An issuance processing system having the following features.

11. The aforementioned plurality of ABT servers include a first ABT server and a second ABT server, The first processor of the hub server is A request to issue a first ABT product, which is included in the product for sale and issued by the first ABT server, is sent to the first ABT server. The first ABT server issues the ID, and the second ABT server issues a request to issue a second ABT product to the second ABT server, specifying the ID issued by the first ABT server. The second processor of the first ABT server issues the ID in response to the issuance request for the first ABT product received from the hub server, creates an account for the first ABT product including the ID, and sends the ID to the hub server. The second processor of the second ABT server creates an account for the second ABT product including the ID in response to a request to issue the second ABT product specifying the ID received from the hub server. The issuance processing system according to claim 10.

12. The first processor of the hub server issues the ID for the product being sold. The issuance processing system according to claim 10.

13. The first processor of the hub server determines whether the product for sale has a second ABT product issued by the second ABT server, and if it determines that the product for sale has a second ABT product, it sends a request to the second ABT server to issue the second ABT product, specifying the ID issued by the first ABT server. The issuance processing system according to claim 11.

14. A method for issuing data using an issuance processing system having multiple ABT servers and a hub server, each of which is provided in multiple ABT systems, The aforementioned hub server identifies the ABT products issued by each ABT server included in a single sales product, The hub server sends an issuance request for each ABT product to each ABT server, which contains one ID for the product being sold, The ABT server creates an account for the ABT product that includes the ID in response to an ABT product issuance request that specifies the ID received from the hub server. The hub server provides the requester of the sales product with information indicating the ID. An issuance processing method having the following characteristics.

15. A hub server is connected to multiple ABT servers located in each of the multiple ABT systems, Identify the ABT products issued by each ABT server included in a single product for sale, Send an issuance request for each ABT product to its respective ABT server to create an account for each ABT product, which includes one ID for the aforementioned product being sold. Provide information indicating the ID to the person requesting the issuance of the aforementioned product. A program that performs an action.

Citation Information

Patent Citations

  • Digital ticket system and digital ticket issuing program

    JP2024131139A