DATA LINKAGE PROGRAM, DATA LINKAGE METHOD, AND DATA LINKAGE APPARATUS

The data linkage program enables independent processing of EC front sections by sequentially calling APIs, simplifying modifications and reducing software dependencies across e-commerce sites.

JP7579097B2Active Publication Date: 2024-11-07유겐가이샤티아이에스
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2020158875
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-09-23
Publication Date
2024-11-07
Estimated Expiration
2040-09-23

AI Technical Summary

Technical Problem

Modifying an EC front section in an e-commerce site can affect other linked EC front sections due to dependencies in the package software, making it difficult to maintain and customize the e-commerce site securely.

Method used

A data linkage program and device that receives input data from users, sequentially calls corresponding APIs, and transmits result data, allowing independent processing of the EC front section without affecting the internal system or other EC front sections.

Benefits of technology

Facilitates easier modification and customization of the EC front section by absorbing changes within the data linkage program, reducing the need to modify package software across multiple EC sites.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579097000001
    Figure 0007579097000001
  • Figure 0007579097000002
    Figure 0007579097000002
  • Figure 0007579097000003
    Figure 0007579097000003
Patent Text Reader

Abstract

To solve the problem that the package software side of an internal system unit needs to be repaired if repairing an EC front unit of an EC site, and therefore the repair of one of EC front units also affects the other EC front units if data of a plurality of EC front units is linked to one package software.SOLUTION: A data linkage program causes a first information processing apparatus to execute processes of: receiving, from a second information processing apparatus, a group of input data including a plurality of pieces of input data from a user for an EC site; calling an API corresponding to each input data sequentially based on the group of input data; and transmitting result data output from the API to the second information processing apparatus.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a data linking program, a data linking method, and a data linking device. [Background technology]

[0002] An EC (Electronic Commerce) site that sells and provides products and services over the Internet is realized by an EC front section that interacts with users via web screens, etc., and an internal system section that handles internal processing such as data integration between the EC front section and a database (DB).

[0003] However, since EC sites handle customer information, they require security and robustness, and developing them is not easy.Therefore, one method to build an EC site is to introduce a package software into the internal system section and customize the package software to suit the EC front section. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6224283 Summary of the Invention [Problem to be solved by the invention]

[0005] However, when making modifications to the EC front end, modifications may also be required to the package software. This is because, if multiple EC front ends are linked to one package software, modifications to one EC front end will affect the other EC front ends as well.

[0006] Therefore, the present disclosure proposes a data linking program, a data linking method, and a data linking device that can make it easier to renovate the EC front end. [Means for solving the problem]

[0007] According to the present disclosure, there is provided a data linkage program which causes a first information processing device to receive an input data group including multiple input data from a user to an EC site from a second information processing device, and based on the input data group, sequentially call application program interfaces (APIs) corresponding to each of the input data, and transmit result data output from the API to the second information processing device.

[0008] In addition, according to the present disclosure, there is provided a data linking method characterized in that a first information processing device receives an input data group including multiple input data from a user to an EC site from a second information processing device, and executes a process of calling APIs corresponding to each of the input data in sequence based on the input data group, and transmitting result data output from the API to the second information processing device.

[0009] In addition, according to the present disclosure, there is provided a data linking device which is a first information processing device, characterized in that it includes a receiving unit which receives an input data group including multiple input data from a user to an EC site from a second information processing device, a calling unit which calls APIs corresponding to each of the input data in sequence based on the input data group, and a transmitting unit which transmits result data output from the API to the second information processing device. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of the configuration of an information processing system according to an embodiment of the present invention. [Diagram 2] 1 is a block diagram showing an example of a functional configuration of an information processing device 100 according to an embodiment of the present invention. [Diagram 3] FIG. 11 is a sequence diagram showing an example of a conventional order process. [Figure 4] FIG. 11 is a sequence diagram showing an example of an order process according to the embodiment. [Diagram 5]FIG. 11 is a sequence diagram showing an example of a member information update process according to the embodiment. [Figure 6] 1 is a block diagram showing an example of a hardware configuration of an information processing device 100 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the present embodiment will be described in detail with reference to the drawings. In this specification and the drawings, the same reference numerals are used to denote substantially the same components, and redundant description will be omitted.

[0012] The explanation will be given in the following order. 1. Embodiment 1.1. System configuration example 1.2. Example of functional configuration 1.3. Feature Details 2. Hardware configuration example 3. Summary 4.Effects

[0013] <1. Embodiment> <<1.1. System configuration example>> First, a configuration example of an information processing system according to this embodiment will be described. Fig. 1 is a diagram showing a configuration example of an information processing system according to this embodiment. As shown in Fig. 1, the information processing system includes an information processing device 100, a user terminal 200, and a coordination source device 300. As shown in Fig. 1, the information processing device 100, the user terminal 200, and the coordination source device 300 are communicatively connected via a network N. Note that the communication method of the network N may be either wired or wireless, and the network N may be any of various communication networks such as the Internet.

[0014] The information processing device 100 is, for example, a server device managed by a company that provides an EC site, and is an internal system part of the EC site that handles internal processing such as data linkage between a coordination source device 300, which is an EC front end, and a DB. The information processing device 100 receives a group of input data from a user terminal 200 for the EC site via the coordination source device 300, and calls APIs corresponding to each of the input data in order. Here, the APIs to be called are, for example, APIs provided by a package software introduced into the internal system part of the EC site. The information processing device 100 also transmits result data output from the called API to the user terminal 200 via the coordination source device 300.

[0015] The user terminal 200 is a terminal owned and used by a user who uses the EC site. The user terminal 200 may be a mobile terminal such as a smartphone or a tablet PC, or may be a stationary terminal installed in the user's home or the like. The user inputs data to the EC site via the user terminal 200. The user also receives result data for the data input to the EC site via the user terminal 200.

[0016] The coordination source device 300 is also, for example, an information processing device managed by a company that provides an EC site. More specifically, the coordination source device 300 is, for example, a Web server that provides a Web screen or Web application of an EC site to the user terminal 200, and is an EC front unit. The coordination source device 300 may also be an information processing terminal installed in a store or the like, and a user can directly input data to the coordination source device 300. In this case, the user terminal 200 does not need to be included in the configuration of the information processing system according to this embodiment.

[0017] 1 shows the information processing system according to the present embodiment as including at least three devices: the information processing device 100, the user terminal 200, and the coordination source device 300. However, as described above, the information processing system according to the present embodiment can be configured, depending on the mode of use, without including the user terminal 200, by combining the information processing device 100 and the coordination source device 300 into one device, or by distributing the devices more finely.

[0018] <<1.2. Example of functional configuration>> Next, a functional configuration example of the information processing device 100 according to the present embodiment will be described. Fig. 2 is a block diagram showing a functional configuration example of the information processing device 100 according to the present embodiment. As shown in Fig. 2, the information processing device 100 according to the present embodiment includes a storage unit 110, a receiving unit 120, a calling unit 130, a transmitting unit 140, an extracting unit 150, a converting unit 160, and a control unit 170.

[0019] (Storage unit 110) The storage unit 110 according to this embodiment is a storage area for temporarily or permanently storing various programs and data. The storage unit 110 may store programs and data for the information processing device 100 to execute various functions. As a specific example, the storage unit 110 may store a program for ordering a product via an EC site, various data for managing membership information and various settings of users who use the EC site, and the like. Of course, the above is merely an example, and the type of data stored in the storage unit 110 is not particularly limited.

[0020] (Receiving unit 120) The receiving unit 120 according to the present embodiment receives an input data group including a plurality of pieces of input data input to an EC site by a user from the coordination source device 300. The input data group received here refers to input data that would conventionally be received by multiple exchanges between the information processing device 100 and the coordination source device 300, and that is collectively received as one input data group. The input data group is received, for example, in an XML (Extensible Markup Language) format.

[0021] (Calling unit 130) The calling unit 130 according to this embodiment calls APIs corresponding to each piece of input data in order based on the input data group received by the receiving unit 120. Note that the input data included in the input data group and the order of APIs to be called differ depending on the process to be executed and are determined in advance.

[0022] Here, the API to be called is, for example, an API provided by a package software introduced into the internal system of the EC site. Specifically, for example, the API to be called is, but is not limited to, an API for authenticating a user to the EC site, an API for ordering a product or service of the EC site, an API for searching for the product or service, an API for registering a user as a member of the EC site, an API for acquiring the member information of the user to the EC site, an API for updating the member information, an API for canceling the user from the EC site, an API for acquiring the purchasing information of the user to the EC site, etc.

[0023] Furthermore, the calling unit 130 may call the next API when it is determined that the next API is executable based on the result data output from the already called API. Specifically, for example, the calling unit 130 calls an API for authenticating a user to an EC site, and when it is determined that the user has been normally authenticated based on the result data output from the API, it calls the next API.

[0024] (Transmitter 140) The transmission unit 140 according to the present embodiment transmits result data output from the API called by the calling unit 130 to the coordination source device 300. The result data is also transmitted in, for example, an XML format.

[0025] (Extraction part 150) The extraction unit 150 according to this embodiment extracts input data from the input data group received by the receiving unit 120. More specifically, the extraction unit 150 extracts input data corresponding to the API to be called next by the calling unit 130 from the input data group in XML format.

[0026] (Conversion unit 160) The conversion unit 160 according to the present embodiment converts the input data extracted by the extraction unit 150 into a data format for calling an API. Specifically, for example, the conversion unit 160 converts the input data in XML format into form data.

[0027] Furthermore, the conversion unit 160 converts the result data output from the API into a data format for transmission to the coordination source device 300. Specifically, for example, the conversion unit 160 converts the result data in a JSON (JavaScript (registered trademark) Object Notation) format into data in an XML format.

[0028] (Control unit 170) The control unit 170 according to this embodiment is a processing unit that controls the entire information processing device 100, and controls each component included in the information processing device 100. The functions of the control unit 170 will be described in detail later.

[0029] An example of the functional configuration of the information processing device 100 according to the present embodiment has been described above. Note that the functional configuration described above using FIG. 2 is merely an example, and the functional configuration of the information processing device 100 according to the present embodiment is not limited to this example. For example, the information processing device 100 does not necessarily have to include all of the configurations shown in FIG. 2, and each configuration can be included in a computer different from the information processing device 100. The functional configuration of the information processing device 100 according to the present embodiment can be flexibly modified according to specifications and operation.

[0030] The functions of each component may be performed by a computing device such as a CPU (Central Processing Unit) reading a control program from a storage medium such as a ROM (Read Only Memory) or a RAM (Random Access Memory) that stores a control program describing the processing procedures for realizing these functions, and interpreting and executing the program. Therefore, the configuration to be used can be changed appropriately depending on the technical level at the time of implementing this embodiment. An example of the hardware configuration of the information processing device 100 will be described later.

[0031] <<1.3. Feature Details>> Next, the functions of the information processing device 100 according to this embodiment will be described in detail using specific processing as an example. The control unit 170 of the information processing device 100 according to this embodiment receives a group of input data from a user terminal 200 for an EC site, calls APIs corresponding to each of the input data in order, and transmits the output result data to the user terminal 200.

[0032] First, conventional data linkage processing will be described using product ordering processing as an example. FIG. 3 is a sequence diagram showing an example of conventional order processing. First, as shown in FIG. 3, the user terminal 200 requests the coordination source device 300 to display an order screen for ordering a product. In response to this, the coordination source device 300 calls an API for displaying the order screen of the information processing device 100. Then, the coordination source device 300 obtains screen information for displaying the order screen, which is output as result data from the API for displaying the order screen, and provides it to the user terminal 200. As a result, the order screen is displayed on the user terminal 200.

[0033] Next, in response to a user pressing a button or link on the order screen, the user terminal 200 requests the coordination source device 300 to display a product list display for product search. In response to the request to display the product list, the coordination source device 300 calls the product search API of the information processing device 100. At this time, keywords or categories for narrowing down the products may be passed as arguments to the product search API. The coordination source device 300 then obtains screen information for displaying the product list, which is output as result data from the product search API, and provides it to the user terminal 200. As a result, the product list is displayed on the user terminal 200.

[0034] Next, the user terminal 200 requests the coordination source device 300 to input the product selected by the user from a product list or the like into the product cart. In response to this, the coordination source device 300 calls an API for inputting the product into the product cart of the information processing device 100. At this time, an identifier that uniquely identifies the selected product is passed as an argument to the API for inputting the product into the product cart. Furthermore, when there is a request from the user terminal 200 to display the contents of the product cart, the coordination source device 300 calls an API for displaying the product cart of the information processing device 100. Then, the coordination source device 300 acquires screen information for displaying the product cart, which is output as result data from the API for displaying the product cart, and provides it to the user terminal 200. As a result, the contents of the product cart are displayed on the user terminal 200.

[0035] Next, the user terminal 200 requests the coordination source device 300 to carry out the purchase procedure for the product added to the cart. In response to this, the coordination source device 300 calls an API for displaying member settings of the information processing device 100. Note that if the user's membership information has already been set, the membership setting process may be skipped, or the set membership information may only be displayed and confirmed. The coordination source device 300 acquires screen information for displaying member settings, etc., output as result data from the API for displaying member settings, and provides it to the user terminal 200. As a result, the member setting screen is displayed on the user terminal 200.

[0036] Next, the user terminal 200 requests the coordination source device 300 to set the member information input by the user via the member setting screen. In response to this, the coordination source device 300 calls the member setting API of the information processing device 100. At this time, the input member information is passed as an argument to the member setting API and set. The coordination source device 300 then obtains screen information for displaying the delivery destination selection screen, which is output as result data from the member setting API, and provides it to the user terminal 200. As a result, the delivery destination selection screen is displayed on the user terminal 200.

[0037] Next, the user terminal 200 requests the coordination source device 300 to set the delivery destination information of the product input by the user via the delivery destination selection screen. In response to this, the coordination source device 300 calls the API for setting the delivery destination of the information processing device 100. At this time, the input delivery destination information is passed as an argument to the API for setting the delivery destination and set. Then, the coordination source device 300 obtains screen information for displaying the payment method selection screen, which is output as result data from the API for setting the delivery destination, and provides it to the user terminal 200. As a result, the payment selection screen is displayed on the user terminal 200.

[0038] Next, the user terminal 200 requests the coordination source device 300 to set the payment method for the price input by the user via the payment selection screen. In response to this, the coordination source device 300 calls the API for setting the payment method of the information processing device 100. At this time, an identifier that uniquely indicates the input payment method is passed as an argument to the API for setting the payment method, and is set. The coordination source device 300 then obtains screen information for displaying a confirmation screen, which is output as result data from the API for setting the payment method, and provides this to the user terminal 200. As a result, a confirmation screen showing the product to be purchased, the delivery address, the payment method, and the like is displayed on the user terminal 200.

[0039] Next, in response to a button press or the like by the user on the confirmation screen, the user terminal 200 requests the coordination source device 300 to register an order for the product desired to be purchased. In response to this, the coordination source device 300 calls an API for order registration of the information processing device 100. As a result, the information processing device 100 executes order registration for the product desired to be purchased, and outputs an order completion message as result data from the order registration API. The coordination source device 300 then transmits an order completion message to the user terminal 200, and the product order processing shown in FIG. 3 ends.

[0040] In this way, in the conventional data linking process, in response to a request from the user terminal 200, the linking source device 300, which is an EC front end, calls an API for each process provided by a package software.

[0041] Therefore, modifications to the EC front section may affect the internal system section configured by package software, etc., and other EC front sections (EC sites) that use each API of the package software. Therefore, in this embodiment, a data linking method that can make it easier to modify the EC front section will be described using product order processing as an example, as in FIG. 3.

[0042] FIG. 4 is a sequence diagram showing an example of order processing according to this embodiment. First, as shown in FIG. 4, the user terminal 200 requests the coordination source device 300 to register an order for a product. At this time, the user terminal 200 transmits an input data group for order registration to the coordination source device 300. The input data group is input by the user via a user interface (UI) provided from the coordination source device 300 to the user terminal 200. At this time, general input checks such as type, number of characters, required input, etc. may be performed on each input data. Furthermore, each input data may be directly input into a text box provided via the UI, or may be selected from a list box or the like.

[0043] In this way, the input format and content of each input data can be set via the UI for each EC front section, and input data groups are created for each process without going through the internal system section configured with package software, etc. Therefore, modifications to the EC front section do not affect the internal system section configured with package software, etc., or other EC front sections, or if they do, the effect is extremely small.

[0044] The input data group sent to the coordination source device 300 includes, for example, an identifier that uniquely identifies the product desired to be purchased, the user's membership information (which may be login information, etc.), product delivery address information, and an identifier that uniquely identifies the payment method.

[0045] Next, in response to the request for product order registration, the coordination source device 300 calls the order registration API of the information processing device 100. At this time, the coordination source device 300 passes the input data group received from the user terminal 200 as an argument to the order registration API. Note that this API is not an API provided by a package software introduced into the internal system of the EC site, but an API created for each EC site.

[0046] Next, in response to a request for product order registration, i.e., execution of the order registration API, the information processing device 100 extracts each input data from the input data group received from the coordination source device 300 and converts it into a data format for calling various APIs. Note that the extraction and conversion of each input data may be performed for each API when calling various APIs. Also, the various APIs called by the information processing device 100 are APIs provided by package software introduced into the internal system of the EC site.

[0047] Next, the information processing device 100 calls an API for displaying an order screen. The API for displaying an order screen is only called to perform processing equivalent to the conventional order processing shown in FIG. 3. In other words, the information processing device 100 calls APIs that are required to be called in the flow of order processing, even if they are not necessary for the processing. In this way, the processing required on the information processing device 100 side, that is, the processing defined by a package software introduced into the internal system section of the EC site, is controlled so as not to be affected even if the processing on the cooperation source device 300 side is changed.

[0048] However, since there is no need to perform processes such as obtaining screen information for displaying the order screen, which is output as result data from the API for displaying the order screen, and displaying the order screen, these processes are not performed here.

[0049] The order in which the information processing device 100 calls various APIs may be determined for each API called by the coordination source device 300 (in the case of FIG. 4, the order registration API), or may be set by input data in the input data group.

[0050] Next, the information processing device 100 calls an API for adding products to the cart. At this time, the information processing device 100 passes an identifier that uniquely identifies the product desired to be purchased, which is one of the input data extracted and converted from the input data group, as an argument to the API for adding products to the cart. Note that, compared to the conventional order processing in Fig. 3, the API for product search is not called before the API for adding products to the cart. In this way, it is possible to control the flow of order processing so that APIs that are not essential to be called are skipped and not called.

[0051] Next, the information processing device 100 calls the API for member settings. At this time, the information processing device 100 passes the user's membership information, which is one of the input data extracted and converted from the input data group, as an argument to the API for member settings.

[0052] Next, the information processing device 100 calls the API for member settings. At this time, the information processing device 100 passes the user's member information, which is one of the input data extracted and converted from the input data group, as an argument to the API for member settings. As shown in FIG. 3, in conventional order processing, screen information for displaying a delivery destination selection screen is output as result data from the API for member settings. However, in the order processing according to the present embodiment shown in FIG. 4, since the input data group already contains product delivery destination information, processing such as displaying a delivery destination selection screen is not executed using the output screen information for displaying the delivery destination selection screen.

[0053] Next, the information processing device 100 calls the API for setting the payment method. At this time, the information processing device 100 passes an identifier that uniquely indicates the payment method, which is one of the input data extracted and converted from the input data group, as an argument to the API for setting the payment method.

[0054] Next, the information processing device 100 calls the API for order registration, which executes order registration for the product desired to be purchased, and outputs an order completion message as result data from the API for order registration.

[0055] Next, the information processing device 100 converts the order completion message output from the order registration API into a data format for transmission to the coordination source device 300, and outputs the converted message as result data of the order registration API to the coordination source device 300. The coordination source device 300 then transmits an order completion message to the user terminal 200, and the product order processing shown in FIG. 4 is completed.

[0056] The order processing according to this embodiment has been described above, but the APIs that are called and executed in this embodiment are not limited to those for order processing, as described above. In addition, the result data of the previously executed API may be included in the input data group of the next API to be executed to determine whether the next API to be executed can be executed.

[0057] Fig. 5 is a sequence diagram showing an example of a member information update process according to the present embodiment. First, as shown in Fig. 5, the user terminal 200 requests the coordination source device 300 for user authentication. At this time, the user terminal 200 transmits an input data group for user authentication to the coordination source device 300. The input data group includes each input data such as the user's membership information (which may be login information, etc.).

[0058] Next, in response to the request for user authentication, the coordination source device 300 calls an API for user authentication of the information processing device 100. At this time, the coordination source device 300 passes the input data group received from the user terminal 200 as an argument to the API for user authentication.

[0059] Next, in response to a request for user authentication, that is, execution of the authentication API, the information processing device 100 extracts each input data from the input data group received from the coordination source device 300, and converts the extracted input data into a data format for calling various APIs.

[0060] Next, the information processing device 100 calls an API for displaying an authentication screen. Like the API for displaying an order screen in Fig. 3, the API for displaying an authentication screen is an API that must be called in the authentication process, and is called even if it is not necessary for the process.

[0061] Next, the information processing device 100 calls the API for member authentication. At this time, the information processing device 100 passes the user's member information, which is input data extracted and converted from the input data group, as an argument to the API for member authentication. As a result, user authentication is executed, and the authentication result is output as result data from the API for member authentication.

[0062] Next, the information processing device 100 converts the authentication result output from the member authentication API into a data format for transmission to the coordination source device 300, and outputs the result data of the authentication API to the coordination source device 300. Then, the coordination source device 300 transmits the authentication result to the user terminal 200.

[0063] Next, the user terminal 200 requests the coordination source device 300 to update the member information. At this time, the user terminal 200 transmits an input data group for user authentication to the coordination source device 300. The input data group includes each input data such as the member information to be changed and the authentication result of the user authentication received from the coordination source device 300.

[0064] Next, in response to the request to update the member information, the coordination source device 300 calls the API for updating the member information of the information processing device 100. At this time, the coordination source device 300 passes the input data group received from the user terminal 200 as an argument to the API for updating the member information.

[0065] Next, in response to a request to update member information, i.e., execution of the member information update API, the information processing device 100 extracts each input data from the input data group received from the coordination source device 300, and converts it into a data format for calling various APIs.

[0066] Next, if the information processing device 100 determines that the user was not successfully authenticated based on the authentication result data of the user authentication included in the input data group, it outputs an error message to the coordination source device 300 as result data of the member information update API without calling various APIs, and the member information update process shown in Figure 5 is terminated.

[0067] On the other hand, if the information processing device 100 determines that the user has been successfully authenticated, it calls the API for displaying member settings. Like the API for displaying the authentication screen, the API for displaying member settings is an API that must be called in the flow of the member information update process, and is called even if it is not necessary for the process.

[0068] Next, the information processing device 100 calls the API for updating member information. At this time, the information processing device 100 passes the member information to be changed, which is the input data extracted and converted from the input data group, as an argument to the API for updating member information. As a result, the member information is updated based on the member information to be changed, and a completion message is output as result data from the API for updating member information.

[0069] Next, information processing device 100 converts the completion message output from the member information update API into a data format for transmission to coordination source device 300, and outputs the completion message as result data of the member information update API to coordination source device 300. Then, coordination source device 300 transmits the completion message to user terminal 200, and the member information update process shown in FIG. 5 ends.

[0070] As shown in Figure 5, the result data of a previously executed API can be included in the input data group of the next API to be executed, making it possible to determine whether the next API to be executed can be executed or to control the API to be called.

[0071] <2. Hardware configuration example> Next, a hardware configuration example of the information processing device 100 according to this embodiment will be described. FIG. 6 is a block diagram showing a hardware configuration example of the information processing device 100 according to this embodiment. Referring to FIG. 6, the information processing device 100 has, for example, a processor 801, a ROM 802, a RAM 803, a host bus 804, a bridge 805, an external bus 806, an interface 807, an input device 808, an output device 809, a storage 810, a drive 811, a connection port 812, and a communication device 813. Note that the hardware configuration shown here is an example, and some of the components may be omitted. In addition, components other than those shown here may be further included.

[0072] (Processor 801) The processor 801 functions, for example, as an arithmetic processing device or control device, and controls all or part of the operation of each component based on various programs recorded in the ROM 802, the RAM 803, the storage 810, or the removable recording medium 901.

[0073] (ROM802, RAM803) The ROM 802 is a means for storing the programs to be read into the processor 801, data to be used for calculations, etc. The RAM 803 temporarily or permanently stores, for example, the programs to be read into the processor 801, various parameters that change appropriately when the programs are executed, etc.

[0074] (host bus 804, bridge 805, external bus 806, interface 807) The processor 801, ROM 802, and RAM 803 are connected to each other via, for example, a host bus 804 capable of high-speed data transmission. On the other hand, the host bus 804 is connected to an external bus 806 having a relatively low data transmission speed via, for example, a bridge 805. In addition, the external bus 806 is connected to various components via an interface 807.

[0075] (Input device 808) Examples of the input device 808 include a mouse, a keyboard, a touch panel, a button, a switch, and a lever. Furthermore, a remote controller capable of transmitting control signals using infrared rays or other radio waves may be used as the input device 808. The input device 808 also includes an audio input device such as a microphone.

[0076] (Output Device 809) The output device 809 is a device capable of visually or audibly notifying the user of acquired information, such as a display device such as a CRT (Cathode Ray Tube), LCD, or organic EL, an audio output device such as a speaker or a headphone, a printer, a mobile phone, a facsimile, etc. The output device 809 according to this embodiment also includes various vibration devices capable of outputting tactile stimuli.

[0077] (Storage 810) The storage 810 is a device for storing various types of data. For example, a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, or a magneto-optical storage device may be used as the storage 810.

[0078] (Drive 811) The drive 811 is a device that reads information recorded on a removable recording medium 901 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, and writes information to the removable recording medium 901.

[0079] (Connection port 812) The connection port 812 is a port for connecting an external device 902, such as a Universal Serial Bus (USB) port, an IEEE1394 port, a Small Computer System Interface (SCSI), an RS-232C port, or an optical audio terminal.

[0080] (Communication device 813) The communication device 813 is a communication device for connecting to a network, such as a communication card for wired or wireless LAN, Bluetooth (registered trademark), or WUSB (Wireless USB), a router for optical communications, a router for ADSL (Asymmetric Digital Subscriber Line), or a modem for various types of communications.

[0081] (Removable recording media 901) The removable recording medium 901 is, for example, a DVD medium, a Blu-ray (registered trademark) medium, an HD DVD medium, various semiconductor storage media, etc. Of course, the removable recording medium 901 may be, for example, an IC card equipped with a non-contact type IC chip, or an electronic device.

[0082] (External connection device 902) The external connection device 902 is, for example, a printer, a portable music player, a digital camera, a digital video camera, or an IC recorder.

[0083] The storage unit 110 according to the present embodiment is realized by the ROM 802, the RAM 803, and the storage 810. The control unit 170 according to the present embodiment, which is realized by the processor 801, reads out and executes each control program that realizes the receiving unit 120, the calling unit 130, the transmitting unit 140, the extracting unit 150, and the converting unit 160 from the ROM 802, the RAM 803, etc. The transmitting unit 140 according to the present embodiment reads out data from the ROM 802, the RAM 803, etc., and transmits the data to the communication device 813 via the host bus 804, the bridge 805, the external bus 806, and the interface 807, thereby transmitting the data to the external device.

[0084] <3. Summary> As described above, the information processing device 100 receives an input data group including multiple input data from a user to the EC site from the coordination source device 300, calls APIs corresponding to each of the input data in sequence based on the input data group, and transmits the result data output from the APIs to the coordination source device 300.

[0085] In this way, by the information processing device 100 performing data linkage between the link source device 300, i.e., the EC front-end unit, and the internal system unit (package software) of the EC site, modifications to the EC front-end unit can be absorbed by the processing of the data linking part of the information processing device 100. As a result, modifications to the EC front-end unit do not require modifications to the package software or to other EC front-end units that call the same API of the package software, making it easier to modify the EC front-end unit.

[0086] Although the preferred embodiment of the present disclosure has been described in detail above with reference to the attached drawings, the technical scope of the present disclosure is not limited to such examples. It is clear that a person having ordinary knowledge in the technical field of the present disclosure can conceive of various modified or amended examples within the scope of the technical ideas described in the claims, and it is understood that these also naturally belong to the technical scope of the present disclosure.

[0087] <4. Effects> As described above, the information processing device 100 may have the following configuration and provide various effects. However, the effects described in this specification are merely explanatory or exemplary and are not limiting. In other words, the technology according to the present disclosure may provide other effects that are obvious to a person skilled in the art from the description of this specification, in addition to or in place of the above effects.

[0088] (1) A first information processing device (information processing device 100) receiving an input data group including a plurality of pieces of input data from a user to the EC site from a second information processing device (coordination source device 300); calling APIs corresponding to each of the input data in sequence based on the input data group; Transmitting result data output from the API to the second information processing device. A data linking program that causes processing to be executed.

[0089] In this way, the input data group is created via the coordination source device 300, which is the EC front unit of the EC site, without going through the internal system unit of the EC site. Furthermore, the information processing device that receives the input data group performs data coordination between the EC front unit and the internal system unit, so that modifications to the EC front unit can be absorbed by the processing of the data coordination part of the information processing device 100. As a result, modifications to the EC front unit do not require modifications to the package software or to other EC front units that call the same API of the package software, making it easier to modify the EC front unit.

[0090] (2) the first information processing device; Extracting the input data from the input data group; The input data is converted into a data format for calling the API. The data linkage program according to (1) above, further comprising:

[0091] As a result, even if there is a difference in the data format handled by the EC front section and the internal system section, the difference can be absorbed by the information processing device 100. This also leads to easier modification of the EC front section.

[0092] (3) the first information processing device, The result data is converted into a data format for transmission to the second information processing device. The data linkage program according to (1) or (2), further comprising:

[0093] As a result, even if there is a difference in the data format handled by the EC front section and the internal system section, the difference can be absorbed by the information processing device 100. This also leads to easier modification of the EC front section.

[0094] (4) The first information processing device receiving a second input data group including a plurality of second input data from the user from the second information processing device; when it is determined based on the result data that the second API is executable, calling the second API corresponding to each of the second input data in sequence based on the second input data group; Transmitting second result data output from the second API to the second information processing device. The data linkage program according to (1) above, further comprising:

[0095] In this way, by including the result data of a previously executed API in the input data set for the next API to be executed, it is possible to determine whether the next API to be executed can be executed and to control the API to be called.

[0096] (5) the API is an API for authenticating the user to the EC site, The first information processing device, receiving a second input data group including a plurality of second input data from the user from the second information processing device; when it is determined based on the result data that the user has been successfully authenticated, calling second APIs corresponding to each of the second input data in sequence based on the second input data group; Transmitting second result data output from the second API to the second information processing device. The data linkage program according to (1) above, further comprising:

[0097] In this way, by including the result data of a previously executed API in the input data set for the next API to be executed, it is possible to determine whether the next API to be executed can be executed and to control the API to be called.

[0098] (6) The data linkage program described in any one of (1) to (5), characterized in that the API is any one of an API for authenticating the user to the EC site, an API for ordering products or services on the EC site, an API for searching for the products or services, an API for registering the user as a member to the EC site, an API for obtaining membership information of the user for the EC site, an API for updating the membership information, an API for canceling the user's membership from the EC site, and an API for obtaining purchasing information of the user for the EC site.

[0099] In this way, the present embodiment can be applied to various processes, not limited to specific processes on an EC site, making it easier to modify various processes in the EC front end. [Explanation of symbols]

[0100] 100 Information processing device 110 Storage section 120 Receiving unit 130 Calling Department 140 Transmitter 150 Extraction part 160 Conversion unit 170 Control section 200 User terminals 300 Linked Device

Claims

1. A first information processing device, receiving an input data group including a plurality of pieces of input data from a user to the EC site from a second information processing device; a process of calling application program interfaces (APIs) installed in the device in order based on the group of input data, the process of calling an API that corresponds to each of the input data in order among the APIs that are currently being implemented, causing the called API to output result data corresponding to the input data corresponding to that API, and, when the result data has been output, calling an API that is next in order among the APIs, and causing the called API to output result data corresponding to the input data corresponding to that API; When the result data output from the called APIs is collected by calling all the APIs according to the order, data based on the result data output from the called APIs is transmitted to the second information processing device. A data linking program that causes processing to be executed.

2. The first information processing device includes: Extracting the input data corresponding to the API to be called from the input data group; The input data is converted into a data format for calling the API.

2. The data linking program according to claim 1, further comprising: a program for executing a process.

3. The first information processing device includes: Converting data based on the result data into a data format for transmission to the second information processing device.

3. The data linking program according to claim 1, further comprising: a processor for executing a process for linking data between the data linking program and the computer;

4. The first information processing device includes: receiving a second input data group including a plurality of second input data from the user from the second information processing device; When it is determined that the second API is executable based on the result data, the second API corresponding to each of the second input data is called in order from among the APIs introduced into the own device based on the second input data group; Transmitting data based on the second result data output from the second API to the second information processing device.

2. The data linking program according to claim 1, further comprising: a program for executing a process.

5. the API is an API for authenticating the user with respect to the EC site, The first information processing device includes: receiving a second input data group including a plurality of second input data from the user from the second information processing device; when it is determined based on the result data that the user has been normally authenticated, calling second APIs corresponding to each of the second input data, among APIs introduced into the own device, in order, based on the second input data group; Transmitting data based on the second result data output from the second API to the second information processing device.

2. The data linking program according to claim 1, further comprising: a program for executing a process.

6. The data linkage program of claim 1, characterized in that the API introduced into the device is any one of an API for authenticating the user to the EC site, an API for ordering products or services on the EC site, an API for searching for the products or services, an API for registering the user as a member on the EC site, an API for obtaining membership information of the user for the EC site, an API for updating the membership information, an API for canceling the user's membership from the EC site, and an API for obtaining purchasing information of the user for the EC site.

7. A first information processing device, receiving an input data group including a plurality of pieces of input data from a user to the EC site from a second information processing device; a process of calling application program interfaces (APIs) installed in the device in order based on the group of input data, the process of calling an API that corresponds to each of the input data in order among the APIs that are currently being implemented, causing the called API to output result data corresponding to the input data corresponding to that API, and, when the result data has been output, calling an API that is next in order among the APIs, and causing the called API to output result data corresponding to the input data corresponding to that API; When the result data output from the called APIs is collected by calling all the APIs according to the order, data based on the result data output from the called APIs is transmitted to the second information processing device. A data linking method comprising: executing a process.

8. A data linking device that is a first information processing device, a receiving unit that receives an input data group including a plurality of pieces of input data from a user to the EC site from a second information processing device; a calling unit that executes a process of calling application program interfaces (APIs) installed in the device in order based on the group of input data, the process calling an API that is currently in the order among the APIs, causing the called API to output result data corresponding to the input data corresponding to the API, and when the result data has been output, calling a next API among the APIs, and causing the called API to output result data corresponding to the input data corresponding to the API; a transmission unit that transmits data based on the result data output from the called API to the second information processing device when the result data output from the called API is completed by calling all the APIs according to the order; A data linking device comprising:

Citation Information

Patent Citations

  • Developing device

    JP1987024283A

  • Bank service system and bank service method

    JP2018032081A

  • API adapter, API adapter creation method, and program

    JP2019144848A