KR20220142630A - Mobile platform system and method for interworking central and local servers - Google Patents

Abstract

The present invention relates to a technology which provides a mobile platform to increase utilization of a kiosk installed in a store by linking the kiosk with a mobile platform. A method for providing a mobile platform linked between a central server and a local server according to one embodiment may comprise: a step in which a user terminal requests authentication from the central server; a step in which, when the user terminal is approved, the central server provides store information and menu information to the user terminal; a step in which the user terminal, by referring to the provided store information and menu information, performs a payment process for a menu of a store desired to visit through a payment server; a step in which the central server collects payment information according to payment completion from the payment server; a step in which the central server transmits the payment information to a local server of the store; a step in which the user terminal requests authentication from the local server; a step in which the local server determines whether to approve the authentication request of the user terminal; a step in which the local server, when the user terminal is approved, inquires payment details for the user terminal based on the payment information transmitted from the central server; and a step in which the local server completes a usage process for the inquired payment details. According to the present invention, mobile order reservation and payment services become available even in general individual stores which are not franchise brands.

Description

Mobile platform system and method for interworking central and local servers

The present invention relates to a technology for providing a mobile platform by linking a kiosk with a mobile device in order to increase the utilization of a kiosk provided in a store.

With the start of the 2020 COVID-19 pandemic, many changes have occurred in our daily lives.

Among them, there are non-face-to-face services that can be experienced in daily life, and these are likely to be further developed even after herd immunity is established after the inoculation of the corona vaccine.

In particular, it is a time when the development of kiosks that will be created in various ways in the future in conjunction with the sharing economy and non-face-to-face socialization is expected.

Kiosk refers to an unmanned terminal installed in a public place so that the public can easily use it for unmanned automation of information services and business. In addition, the kiosk is also referred to as a multimedia station or a self service station, and usually uses a touch screen method to obtain information or process tasks such as purchase, ticketing, and registration.

The inside of the kiosk is generally in the form of a multimedia PC, and in addition to this, various input/output peripherals such as a touch screen, card reader, printer, network, speaker, video camera, intercom, and detector are installed, and user applications are executed using GUI. . Kiosk management and device control software are running inside the kiosk, and it communicates with a server system that monitors the operation status of each device over the network and diagnoses and repairs abnormalities.

Kiosks are generally installed and operated in open places with large floating populations such as public places, restaurants, bus terminals, subways, government offices, and shopping malls. make it possible

In addition, the kiosk has a push function and can transmit advertisements to a part of the screen or deliver full-page advertisements or specialized information. If a multimedia environment is built in the kiosk, video conferencing systems, scanning, screen sharing, etc. can be implemented, and virtual reality and voice recognition functions can also be installed.

Public institutions can issue various civil documents and pay utility bills based on kiosks, and universities provide various on-campus services in connection with smart cards (IC cards). In addition, kiosk devices based on smart digital signage technology are installed in the center of downtown with a large floating population, providing customized information or experiential advertising services by identifying individual situations and surrounding environments. In schools and private institutes, it is used as an electronic blackboard to enhance the interaction of education.

Despite the various uses of kiosks, there are many limitations due to the inherent locational limitations of kiosks that must be fixedly installed in stores.

Korean Patent No. 10-2029649 "A system and method for providing a mobile kiosk-type order based on a kiosk app" Korean Patent Publication No. 10-2021-0012041 "Remote order authentication on kiosk (remote order authentication on kiosk)" Korean Patent Publication No. 10-2020-0089477 "System and method for providing mobile kiosk service"

An object of the present invention is to enable a mobile order reservation and payment service such as Starbucks' siren order in general private stores that are not franchise brands.

An object of the present invention is to break away from the existing stand alone kiosk method and provide an advanced kiosk 2.0 version service business model.

An object of the present invention is to provide a system and a platform for ordering through mobile, such as ordering directly from a kiosk.

An object of the present invention is that orders can be accepted even during non-business hours even when the in-store kiosk is off due to reasons such as leaving the office, stopping work, or a breakdown.

A method for providing a mobile platform interworking between a central server and a local server according to an embodiment includes the steps of requesting authentication from a user terminal to a central server, and when the user terminal is approved, the central server provides store information and menu information to the user terminal performing payment processing for a menu of a store desired to visit through a payment server with reference to the provided store information and menu information in the user terminal, the central server according to the payment completion from the payment server Collecting payment information, transmitting the payment information from the central server to a local server of the store, the user terminal requesting authentication to the local server, approval of the authentication request of the user terminal from the local server Determining whether the user terminal is approved, in the local server, based on the payment information transmitted from the central server, inquiring the payment details for the user terminal, in the local server, the inquiry It may include the step of completing the use processing for the payment details.

According to an embodiment, the step of the user terminal requesting authentication from the local server includes performing primary authentication using a QR pattern or number displayed on the local server, and if the primary authentication result is approved, the user terminal is sent to the user terminal. It may include the step of transmitting the authentication code to the central server by clicking the link inserted in the transmitted text to perform secondary authentication.

According to an embodiment, the step of the user terminal requesting authentication from the local server includes performing primary authentication using a QR pattern or number displayed on the local server, and if the primary authentication result is approved, the user terminal is sent to the user terminal. The method may include reading the transmitted QR pattern through a reader interworking with the local server to perform secondary authentication.

In the local server according to an embodiment, the step of completing the use processing for the inquired payment details may include uploading member information and fee information for the payment details to the central server.

The uploading of member information and fee information for the payment details to the central server according to an embodiment may include transmitting member information and fee information for the payment details to a POST request body in a JSON array. have.

The method may further include synchronizing the local server and the central server according to an embodiment.

The step of synchronizing the local server and the central server according to an embodiment may include synchronizing the local server and the central server using a web-based RESTful API transmission method using SOAP or JSON.

The step of synchronizing the local server and the central server according to an embodiment may include the step of checking and mirroring real-time changes between the local server and the central server with a separate agent program in a variable asynchronous manner when a service load is applied. .

The step of synchronizing the local server and the central server according to an embodiment may include transmitting information stored in the central server to the local server in a polling manner.

The system for providing a mobile platform interworking between a central server and a local server according to an embodiment receives an authentication request from a user terminal and the user terminal, performs authentication processing, and when the user terminal is approved, stores information and menu information to the user terminal A central server that provides, and the user terminal refers to the provided store information and menu information, performs payment processing for a menu of a store desired to visit, and transmits payment information according to payment completion to the central server , a local server for receiving the payment information from a central server according to the payment completion, wherein the user terminal requests authentication to the local server, and the local server determines whether to approve the authentication request of the user terminal, , when the user terminal is approved, based on the payment information transmitted from the central server, the payment details for the user terminal may be inquired, and the use processing for the inquired payment details may be completed.

The local server according to an embodiment performs primary authentication of the user terminal by displaying a QR pattern or a number, and the user terminal is sent to the central server using a link inserted in a text transmitted according to the primary authentication. Secondary authentication is possible by sending an authentication code.

The local server according to an embodiment performs the primary authentication of the user terminal by displaying a QR pattern or number, and the user terminal, through a reader interworking with the local server, the QR pattern transmitted according to the primary authentication Secondary authentication can be done by reading.

The local server according to an embodiment may upload member information and fee information for the payment details to the central server, and transmit member information and fee information for the payment details to the POST request body in a JSON array.

The local server according to an embodiment may be synchronized with the central server, but may be synchronized with the central server through a web-based RESTful API transmission method using SOAP or JSON.

The central server according to an embodiment, but synchronizes with the local server, can be mirrored by checking real-time changes with the local server with a separate agent program in a variable asynchronous manner when the service is loaded.

The central server according to an embodiment may be synchronized with the local server, and may synchronize information stored in the central server by transmitting the information stored in the central server to the local server in a polling manner.

According to an embodiment, it is possible to enable mobile order reservation and payment services such as Starbucks siren order even in general private stores that are not franchise brands.

According to one embodiment, it is possible to break away from the existing stand alone kiosk method, and provide an advanced kiosk 2.0 version service business model.

According to one embodiment, it is possible to provide a system and platform for ordering through mobile, such as ordering directly from a kiosk.

According to one embodiment, even if the kiosk in the store is off due to work, stoppage, breakdown, etc., orders may be accepted even during non-business hours.

1 is a diagram illustrating a system for providing a mobile platform interworking between a central server and a local server according to an embodiment.
2A to 2C are diagrams for explaining a process of ordering and paying for a menu in a store through a user terminal.
3 is a diagram illustrating a process of authenticating a local server through a user terminal.
4A and 4B are diagrams for explaining a message received by a user terminal in an authentication process.
5 is a diagram illustrating an interworking architecture between a local server and a central server.

Specific structural or functional descriptions of the embodiments according to the concept of the present invention disclosed herein are only exemplified for the purpose of explaining the embodiments according to the concept of the present invention, and the embodiment according to the concept of the present invention These may be embodied in various forms and are not limited to the embodiments described herein.

Since the embodiments according to the concept of the present invention may have various changes and may have various forms, the embodiments will be illustrated in the drawings and described in detail herein. However, this is not intended to limit the embodiments according to the concept of the present invention to specific disclosed forms, and includes changes, equivalents, or substitutes included in the spirit and scope of the present invention.

Terms such as first or second may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from other components, for example, without departing from the scope of rights according to the concept of the present invention, a first component may be named as a second component, Similarly, the second component may also be referred to as the first component.

When a component is referred to as being “connected” or “connected” to another component, it may be directly connected or connected to the other component, but it is understood that other components may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that the other element does not exist in the middle. Expressions describing the relationship between elements, for example, “between” and “between” or “directly adjacent to”, etc. should be interpreted similarly.

The terminology used herein is used only to describe specific embodiments, and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present specification, terms such as "comprise" or "have" are intended to designate that the described feature, number, step, operation, component, part, or combination thereof exists, and includes one or more other features or numbers, It should be understood that the possibility of the presence or addition of steps, operations, components, parts or combinations thereof is not precluded in advance.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present specification. does not

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, the scope of the patent application is not limited or limited by these embodiments. Like reference numerals in each figure indicate like elements.

1 is a diagram illustrating a system 100 for providing a mobile platform interworking between a central server and a local server according to an embodiment.

The interlocking mobile platform providing system 100 according to an embodiment enables mobile order reservation and payment services, such as Starbucks siren order, in general private stores that are not franchise brands.

In general, it is necessary to install a separate app for each store and register a user, but in the present invention, it is possible to provide mobile ordering and payment services for a plurality of individual stores through one app by integrating individual stores of various subjects. .

To this end, the interworking mobile platform providing system 100 may be implemented including a local server 110 , a user terminal 120 , and a central server 130 .

In addition, the user terminal 120 may further include a payment server 140 capable of processing a simple payment using a mobile network.

The central server 130 according to the present invention can synchronize and manage menu information of each store with local servers located locally, and provide information on the selected store to the user through the app.

In addition, when the connection and authentication using the central server 130 is completed, an order and payment process using direct communication between the user terminal 120 and the local server 110 may be performed.

The local server 110 may be interpreted as a kiosk server or a server in a store that interworks with the kiosk. In addition, the cloud-based central server 130 can be interpreted as the HOST of the present system for data management for the extended service of the existing kiosk.

That is, the function of processing the payment directly by manipulation from the user in the store, or performing authentication on the user terminal 120 that has already processed payment through mobile and uploading it to the central server 130 to synchronize data can be done

To this end, the local server 110 may maintain a service provided by the store, for example, menu information and provide it to the central server 130 so that the user terminals requesting the menu information can share it.

The central server 130 is a remote server that can be accessed through a cloud network, and can store and manage all information about the local server 110 and information about the user terminal 120 in a database.

Through this process, it is possible to synchronize menu information between the local server 110 and the central server 130 installed in a plurality of individual stores. Also, the central server 130 may record and manage menu information provided by the local server 110 .

The information on the local server 110 may include location information of a store in which the local server 11 is located, menu information provided by the store, and the like. Also, the information on the user terminal 120 may include member information about the user of the user terminal 120 .

In particular, the central server 130 may receive an authentication request from the user terminal 120 and process the authentication, and when the user terminal is approved, the central server 130 may provide store information and menu information to the user terminal.

In this case, the user terminal 120 may process the authentication request using the mobile network regardless of whether or not the user enters the store.

The central server 130 and a plurality of local servers (kiosks) may synchronize and manage menu information of each store, and provide the information of the selected store to the user terminal 120 through the app.

On the other hand, in order to increase security such as hacking through the communication channel between the central server 130 and the local server 100, the user terminal first orders the menu online only in stores that are first authenticated offline (on-site). etc are possible.

For example, when the connection and authentication using the central server 130 is completed, thereafter, an order and payment process using direct communication between the user terminal 100 and the local server 110 may be performed.

The payment server 140 may be interpreted as a payment gateway (PG), and the user terminal 120 confirming the menu information of the store through the mobile network performs payment for a specific menu desired to be ordered through the payment server 140 . can be processed

When the payment processing is completed, the payment server 140 may notify the payment completion to the central server 130 . Accordingly, the central server 130 may request to prepare a menu by providing the payment completion to the local server 110 .

Meanwhile, when the user terminal 120 that has completed payment for the menu enters the store, the authentication procedure may be performed according to a process prepared by the local server 110 .

First, the local server 110 may display a QR code or an authentication number as the user terminal 120 enters. Accordingly, the user terminal 120 may read the displayed QR code or authentication number and transmit it to the central server 130 to perform primary authentication.

More specifically, the user terminal 120 may make an authentication request to the local server 110 , and the local server 110 may determine whether to approve the authentication request of the user terminal 120 . In addition, when the user terminal 120 is approved, the local server 110 inquires the payment details for the user terminal 120 based on the payment information transmitted from the central server 130, and You can complete the processing for use.

In addition, the central server 130 may transmit a text message or a message using an API or an app to the user terminal 120 according to the first authentication. At this time, the message includes information for secondary authentication, and when the identity authentication for the user terminal 120 is finally approved, the user is assigned a seat in the store and can use the service.

The local server 110 according to an embodiment uploads member information and fee information for payment details to the central server 130, but can transmit member information and fee information for payment details to the POST request body in a JSON array. have.

In addition, the local server 110 according to an embodiment may synchronize with the central server 130 in a web-based RESTful API transmission method using SOAP or JSON in the synchronization process with the central server.

2A to 2C are diagrams for explaining a process of ordering and paying for a menu in a store through a user terminal.

First, referring to FIG. 2A , the user terminal 210 may request membership registration or authentication of a member to the central server through a mobile network using a mobile app.

When the member is authenticated, the central server may provide store information and menu information about the store requested from the user terminal 210 .

The menu information may include an image for each menu and brief information about the menu, such as a price, a country of origin, and a cooking time.

In the present invention, once the user terminal 210 is authenticated through the central server, the subsequent authentication process of the central server may be omitted.

That is, the user terminal 210 does not need to request authentication from the central server every time it is used, and processes such as authentication, ordering, and payment are possible through direct communication with the local server.

As a specific embodiment, the menu information for menu 1 displayed on the screen of the user terminal 210 may include menu information with a price of 11,000 won, a domestic product, and a cooking time of 15 minutes.

Accordingly, when the user wants to order menu 1, the user can request food corresponding to menu 1 by touching a portion corresponding to menu 1 on the screen of the user terminal 210 .

In this specification, an embodiment in which the user terminal 210 receives the menu of the restaurant from the central server and selects the menu will be described, but it is obvious that it can be interpreted and changed in various embodiments.

For example, it is applicable to all offline stores in which kiosks are installed in stores. That is, by integrating individual stores of various entities, it is possible to provide mobile ordering and payment services for a plurality of individual stores through one app.

Next, referring to FIG. 2B , the user terminal 220 may display a detailed photo (menu 1 photo) of the menu 1 selected in FIG. 2A and display a screen through which payment can be performed.

For example, on the screen of the user terminal 220 , icons for selecting a payment method may be arranged and displayed together with the image for the menu 1 photo. Specifically, icons such as a credit card, mobile phone, and account transfer may be horizontally arranged as a payment method.

In addition, on the screen of the user terminal 220 , a message to be sent to the store may be recorded as other requests.

"Please start cooking when we arrive.", "Please provide the sweet and sour sauce separately.", "Please leave out the cucumber in the bibimbap." You can request to record messages such as, etc. and deliver them to the local server through the central server.

2C is a diagram illustrating the user terminal 230 displaying a message according to the payment completion on the display.

3 is a diagram 300 for explaining a process of authenticating a local server through a user terminal.

The user terminal 120 ordered the menu of the store through the mobile network using the mobile app regardless of inside or outside the store.

Thereafter, when the user terminal 120 enters the store, it is necessary to determine whether the user terminal 120 is the user terminal that actually ordered the menu.

To this end, the local server 120 may display a QR pattern or number on the screen, and the user terminal 120 may read it and transmit it to the central server for primary authentication processing.

In FIG. 3 , an embodiment in which the user terminal 120 recognizes and authenticates a QR pattern will be described.

As shown in FIG. 3 , the user terminal 120 may read the QR pattern displayed on the local server 110 .

That is, the user terminal 120 may perform primary authentication using the QR pattern or number displayed on the local server 110 . Accordingly, when the first authentication result is approved, the user terminal 120 can click the link inserted in the text to transmit the authentication code to the central server to perform the secondary authentication.

4A and 4B are diagrams for explaining a message received by a user terminal in an authentication process.

The user terminal 410 of FIG. 4A may confirm the first authentication result of transmitting the QR pattern or number to the central server in the form of a message displayed on the display of FIG. 4A .

In other words, if you receive the message "Your identity has been verified. Click the link below, the final authentication is complete." You can confirm that the primary authentication is complete.

In addition, when URL1 received along with a confirmation message for primary authentication is clicked, secondary authentication may be performed by accessing a URL linked to the corresponding URL1. The URL may be interpreted as a mobile web page managed by the central server, and when accessing the mobile web page, a secondary authentication request may be transmitted to the central server.

When the central server confirms the secondary authentication, the primary and secondary authentication for the user terminal 410 may be completed.

Meanwhile, the user terminal 410 may receive the QR pattern from the central server as the first authentication is completed.

For example, a QR pattern may be inserted into a text message in the form of an image and delivered, or a text message may be received in which a separate URL for loading a QR pattern is inserted.

Accordingly, the user terminal 410 may display the QR pattern transmitted from the central server on the display.

In addition, the QR pattern displayed on the user terminal 410 may be read through a reader interworking with the local server, and the QR pattern read through the reader may be determined whether or not approved by the local server.

In this case, it is possible to determine whether to approve the QR pattern by a preset algorithm in the local server itself, or to inquire whether to approve the QR pattern by transmitting the read QR pattern to the central server.

When the QR pattern read through the reader is approved, it may be determined that the second approval is completed.

4B is a message for confirming that the user authentication in the store is finally completed as the first and second authentication are completed.

5 is a diagram illustrating an interworking architecture between a local server and a central server.

As shown in FIG. 5 , according to the method of providing a mobile platform interworking between the central server and the local server, the local server may upload member information, price information, menu information in a store, etc. to the central server in advance ( 501 ). In this process, the local server can transmit data as a JSON array to the POST request body. In addition, after the first full data transmission, only modified/added data can be transmitted.

Meanwhile, the central server may collect member information, price information, and menu information in the store in advance, record it in a database, and maintain it. In particular, affiliate store information, integrated member information, member/rate information, and affiliate store rate payment information can be separately recorded and maintained in each database.

In this background, the user terminal may make an authentication request to the central server (step 502). In this process, the user terminal may proceed with the integrated membership registration process prior to the authentication request. When the integrated membership registration process is completed, the user terminal may request authentication for login to the central server.

When the user terminal is approved, the central server may provide store information and menu information to the user terminal (step 503).

In addition, the user terminal may receive the menu information provided by the store, inquire the rate information, and request payment ( 504 ).

Meanwhile, the user terminal may perform payment processing for a menu of a store desired to be visited through the payment server with reference to the provided store information and menu information ( 505 ).

Next, the payment server may provide a payment result to the central server ( 506 ), and the central server may collect payment information according to payment completion from the payment server.

In addition, the central server transmits payment information to the local server of the store (508), and the local server may receive and process an authentication request for a user terminal entering the store (step 509).

In order for the user terminal to request authentication from the local server, specifically, the first authentication is performed using the QR pattern or number displayed on the local server, and if the first authentication result is approved, click the link inserted in the text sent to the user terminal The second authentication is possible by sending the authentication code to the central server.

The local server determines whether to approve the authentication request of the user terminal, and when the user terminal is approved, the local server can inquire the payment details for the user terminal based on the payment information transmitted from the central server.

Next, the local server may complete the use processing for the inquired payment details (510). To this end, the local server may update the fee details and process the use of the prepaid menu. In addition, the local server may update the billing details in the kiosk and transmit the revision details to the cloud server.

For example, in order to complete the usage processing for the payment details retrieved from the local server, member information and fee information for the payment details may be uploaded to the central server. To this end, the local server according to an embodiment may transmit member information and fee information for payment details in a JSON array in the POST request body.

On the other hand, at least one server among the local server and the central server can be synchronized with the local server and the central server by a web-based RESTful API transmission method using SOAP or JSON to synchronize with each other.

Also, in order to synchronize the local server and the central server, a mirroring method can be used. For example, it is possible to check and mirror real-time changes between the local server and the central server with a separate agent program in a variable asynchronous manner when the service is loaded.

In addition, the central server can synchronize the stored information by transmitting it to the local server in a polling method.

For example, even if the kiosk in the store is off due to unavoidable reasons such as leaving work, business suspension, breakdown, etc., customers can receive orders and place orders on the central server through mobile devices even during non-business hours. When the kiosk is turned on, the local server can immediately execute (BATCH) a modularized process for customer orders and payment information of the store on the central server in a polling method to execute the same routine as the order and payment on the kiosk.

After all, by using the present invention, it is possible to enable mobile order reservation and payment services such as Starbucks' siren order in general private stores that are not franchise brands.

In addition, it is possible to provide an advanced kiosk 2.0 version service business model by breaking away from the existing stand alone kiosk method. In addition, it is possible to provide a system and platform for ordering through mobile as if ordering directly from a kiosk, and even when the kiosk in the store is off due to work, stoppage, breakdown, etc.

The device described above may be implemented as a hardware component, a software component, and/or a combination of the hardware component and the software component. For example, devices and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), It may be implemented using one or more general purpose or special purpose computers, such as a programmable logic unit (PLU), microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For convenience of understanding, although one processing device is sometimes described as being used, one of ordinary skill in the art will recognize that the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that may include For example, the processing device may include a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as parallel processors.

The software may comprise a computer program, code, instructions, or a combination of one or more thereof, which configures a processing device to operate as desired or is independently or collectively processed You can command the device. The software and/or data may be any kind of machine, component, physical device, virtual equipment, computer storage medium or device, to be interpreted by or to provide instructions or data to the processing device. , or may be permanently or temporarily embody in a transmitted signal wave. The software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be specially designed and configured for the embodiment, or may be known and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic such as floppy disks. - includes magneto-optical media, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with reference to the limited drawings, various modifications and variations are possible from the above description by those of ordinary skill in the art. For example, the described techniques are performed in an order different from the described method, and/or the described components of the system, structure, apparatus, circuit, etc. are combined or combined in a different form than the described method, or other components Or substituted or substituted by equivalents may achieve an appropriate result.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (16)

requesting authentication from the user terminal to the central server;
providing store information and menu information from the central server to the user terminal when the user terminal is approved;
performing, in the user terminal, payment processing for a menu of a store desired to be visited through a payment server with reference to the provided store information and menu information;
collecting, by the central server, payment information according to payment completion from the payment server;
transmitting the payment information from the central server to a local server of the store;
the user terminal requesting authentication to the local server;
determining whether the local server approves the authentication request of the user terminal;
when the user terminal is approved, inquiring, in the local server, the payment details for the user terminal based on the payment information transmitted from the central server;
Completing use processing for the inquired payment details in the local server
A method of providing a mobile platform interworking between a central server and a local server, including a. According to claim 1,
The step of the user terminal requesting authentication to the local server,
first authentication using the QR pattern or number displayed on the local server;
If approved as a result of the first authentication, click the link inserted in the text transmitted to the user terminal to transmit the authentication code to the central server to perform secondary authentication
A method of providing a mobile platform interworking between a central server and a local server, including a. According to claim 1,
The step of the user terminal requesting authentication to the local server,
first authentication using the QR pattern or number displayed on the local server;
If approved as a result of the first authentication, reading the QR pattern transmitted to the user terminal through a reader interworking with the local server to perform secondary authentication
A method of providing a mobile platform interworking between a central server and a local server, including a. According to claim 1,
In the local server, the step of completing the use processing for the inquired payment details,
Uploading member information and fee information for the payment details to the central server
A method of providing a mobile platform interworking between a central server and a local server, including a. 5. The method of claim 4,
The step of uploading member information and fee information for the payment details to the central server,
Sending member information and fee information for the payment details to the POST request body as a JSON array
A method of providing a mobile platform interworking between a central server and a local server, including a. According to claim 1,
Synchronizing the local server and the central server
A method of providing a mobile platform interworking between the central server and the local server further comprising a. 7. The method of claim 6,
The step of synchronizing the local server and the central server is,
Synchronizing the local server and the central server using a web-based RESTful API transmission method using SOAP or JSON
A method of providing a mobile platform interworking between a central server and a local server, including a. According to claim 1,
The step of synchronizing the local server and the central server is,
Checking and mirroring real-time changes between the local server and the central server with a separate agent program in a variable asynchronous manner during service load
A method of providing a mobile platform interworking between a central server and a local server, including a. According to claim 1,
The step of synchronizing the local server and the central server is,
Transmitting the information stored in the central server to the local server in a polling method
A method of providing a mobile platform interworking between a central server and a local server, including a. user terminal;
a central server receiving an authentication request from the user terminal, performing authentication processing, and providing store information and menu information to the user terminal when the user terminal is approved;
a payment server in which the user terminal performs payment processing for a menu of a store desired to visit, with reference to the provided store information and menu information, and transmits payment information according to payment completion to the central server;
A local server for receiving the payment information from the central server according to the completion of the payment
including,
The user terminal requests authentication to the local server,
The local server determines whether to approve the authentication request of the user terminal, and when the user terminal is approved, based on the payment information transmitted from the central server, inquires the payment details for the user terminal, A system for providing a mobile platform interworking between a central server and a local server, characterized in that the use processing for the inquired payment details is completed. 11. The method of claim 10,
The local server first authenticates the user terminal by displaying a QR pattern or number,
The user terminal, the central server and the local server interworking mobile platform providing system, characterized in that the secondary authentication by transmitting an authentication code to the central server using the link inserted in the text transmitted according to the primary authentication. 11. The method of claim 10,
The local server first authenticates the user terminal by displaying a QR pattern or number,
wherein the user terminal reads the QR pattern transmitted according to the first authentication through a reader interworking with the local server to perform secondary authentication. 11. The method of claim 10,
The local server is
Uploading member information and fee information for the payment details to the central server, and transmitting member information and fee information for the payment details in a JSON array to the POST request body. platform delivery system. 11. The method of claim 10,
The local server, but processing synchronization with the central server,
A system for providing a mobile platform interworking between a central server and a local server, characterized in that it synchronizes with the central server in a web-based RESTful API transmission method using SOAP or JSON. 11. The method of claim 10,
The central server, but the synchronization processing with the local server,
A system for providing a mobile platform interlocking between a central server and a local server, characterized in that it checks and mirrors the changes in real time with the local server with a separate agent program in a variable asynchronous manner when the service is loaded. 11. The method of claim 10,
The central server, but the synchronization processing with the local server,
A system for providing an interworking mobile platform between a central server and a local server, characterized in that the information stored in the central server is transmitted and synchronized to the local server in a polling method.

Images