Non-face-to-face remote business processing system and method by user interface sharing

Abstract

A non-face-to-face remote business processing system and method by sharing a user interface are disclosed. The non-face-to-face remote business processing system by sharing a user interface according to one embodiment of the present invention includes a first user terminal on which a service application is installed and executed, a second user terminal that shares and displays a user interface by executing the service application, and a business support server that communicates with the first user terminal and the second user terminal, sets the user interface of the first user terminal so that it can be shared by the second user terminal under specified conditions, and enables business processing remotely without meeting the user, and at least one of the first user terminal and the second user terminal includes a user interface sharing module that performs history logging regarding the user interface sharing.

Description

Technical Field

[0001] The present invention relates to a business processing system and method, and more particularly, to a non-face-to-face remote business processing system and method that enables efficient remote business execution in a non-face-to-face manner through user interface (UI) sharing.

Background Art

[0002] Recently, digital transformation has been in the spotlight. Digital transformation means that business operations, including our lives, are converted digitally by using new digital technologies.

[0003] Companies / organizations, etc. are changing to a form of using the cloud provided as a service without configuring their own servers and operating environments. Using cloud services means that data and resources exist on an external cloud.

[0004] This has brought about a change to a new type of business environment of various collaborations and sharing through mobile devices such as smartphones, and the need for business programs that can support collaboration and sharing to adapt to this has increased rapidly.

[0005] Currently, the market is divided into a platform for mobile app development and a desktop application platform. As mobile operating systems lacking in compatibility, such as Apple's iOS and Google's Android, have emerged in the mobile ecosystem, the burden of developing different applications for specific operating systems has increased, and hybrid apps that can easily create a single app that can be efficiently performed on various platforms such as iOS, Android, and Windows with a single development have begun to attract attention.

[0006] In addition, in the post-pandemic era, non-face-to-face remote services are increasing, and there is a situation where a business process suitable for this is required.

Prior Art Documents

Patent Documents

[0007] Korean Patent Publication No. 10-2012-0063366

Summary of the Invention

Problems to be Solved by the Invention

[0008] An object of the present invention is to provide a non-face-to-face remote business processing system and method using user interface sharing that enables non-face-to-face remote business processing by sharing all user interface (UI) blocks implemented on the web between service users and providers, and improves business efficiency.

[0009] Another object of the present invention will be easily understood based on the following description.

Means for Solving the Problems

[0010] To achieve the above object, according to one aspect of the present invention, there is provided a non-face-to-face remote business processing system using user interface sharing, including a first user terminal on which a service application is installed and executed, a second user terminal that shares and displays a user interface by executing the service application, and a business support server that communicates with the first user terminal and the second user terminal and is configured to share the user interface of the first user terminal on the second user terminal under specified conditions to enable non-face-to-face remote business processing. At least one of the first user terminal and the second user terminal includes a user interface sharing module that performs history logging related to user interface sharing. A non-face-to-face remote business processing system using user interface sharing is provided.

[0011] The above user interface sharing module can record the history related to the sharing process information between the first user terminal and the second user terminal within a certain period and store it in a database.

[0012] The above sharing process information may be a combination of a shared screen and an event generated related to the user's operation.

[0013] The above generated event can include at least one of click, mouse movement, input, signature, and annotation processing.

[0014] The above user interface sharing module can provide a replay function that reads out the above history stored in the database according to a request, displays the above shared screen, and reproduces the above generated event.

[0015] The above user interface sharing module can operate the front camera provided on the terminal during history logging, attach the image data of the shared user or viewer user taken and the shooting time information as authentication materials to the above history record, and store them together.

[0016] Alternatively, the above user interface sharing module can operate the microphone provided on the terminal during history logging, attach the voice data obtained by recording the voice of the shared user or viewer user as authentication materials to the above history record, and store them together.

[0017] The above business support server generates a token corresponding to a token generation request for user interface sharing from either the first user terminal or the second user terminal, transfers it to the requesting terminal, and determines whether the token included in the sharing request from the other one of the first user terminal and the second user terminal is equal to the token transferred to either the first user terminal or the second user terminal, and decides whether to permit sharing.

[0018] Either the first user terminal or the second user terminal generates an identification code including the token and connection information to the business support server and outputs it to the screen, and the other one of the first user terminal and the second user terminal can generate the sharing request using the data obtained by photographing the identification code.

[0019] On the other hand, according to another aspect of the present invention, there is provided a non-face-to-face remote business processing method performed in a non-face-to-face remote business processing system by user interface sharing, including steps of: starting user interface sharing between a first user terminal and a second user terminal; logging a history regarding a shared screen and generated events when a preset condition is satisfied; storing the history record in a database; and when there is a replay request for the history record, reading the history record from the database, displaying the shared screen, and sequentially reproducing the generated events.

[0020] In the step of logging the history, during the logging of the history, the front camera provided in the terminal can be activated to photograph the shared user or the viewer user, and the image data and the photographing time information are attached to the history record as authentication materials and held together.

[0021] In the step of logging the history, during the logging of the history, the microphone provided in the terminal can be activated to record the voice of the shared user or the viewer user, and the voice data is attached to the history record as authentication materials and held together.

[0022] Other aspects, features, and advantages other than those described above will become apparent from the following drawings, claims, and detailed description of the invention.

Effects of the Invention

[0023] According to an embodiment of the present invention, there is an effect of improving business efficiency by enabling non-face-to-face remote business processing by sharing all user interface (UI) blocks implemented on the web between service users and providers.

Brief Description of the Drawings

[0024]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Embodiments for Carrying Out the Invention

[0025] Since the present invention can be subjected to various transformations and can have a plurality of embodiments, specific embodiments will be illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and it should be understood to include all modifications, equivalents, or alternatives included in the spirit and technical scope of the present invention.

[0026] When a certain component is referred to as being "connected" or "connected to" another component, it should be understood that it can be directly connected or connected to the other component, but other components can also exist therebetween. On the other hand, when a certain component is referred to as being "directly connected" or "directly connected to" another component, it should be understood that no other component exists therebetween.

[0027] Terms such as first, second, etc. can be used to describe various components, but the above components should not be limited by the above terms. The above terms are used only for the purpose of distinguishing one component from another component.

[0028] The terms used in this application are merely used to describe specific examples and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly indicates a different meaning. In this application, terms such as "including" or "having" are only intended to specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and do not pre-exclude the presence or possibility of addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof. It should be understood.

[0029] In addition, the components of the embodiments described with reference to the respective drawings are not limitedly applied only to the embodiments, and may be embodied so as to be included in other embodiments within the scope in which the technical idea of the present invention is maintained. It is a matter of course that, even if another explanation is omitted, or a plurality of embodiments may be reproduced as one integrated embodiment.

[0030] In addition, in referring to the accompanying drawings for explanation, regardless of the reference numerals in the drawings, the same components are assigned the same or related reference numerals, and overlapping explanations thereof are omitted. In explaining the present invention, when it is determined that a specific explanation of related known technologies obscures the gist of the present invention unnecessarily, the detailed explanation thereof is omitted.

[0031] In addition, terms such as “… section”, “… unit”, “… module”, “… device” described in the specification mean a unit that processes at least one function or operation, and this can be embodied by hardware, software, or a combination of hardware and software.

[0032] FIG. 1 is a conceptual diagram of a non-face-to-face remote business processing system by user interface sharing according to an embodiment of the present invention. FIG. 2 is a configuration block diagram of the client side (shared user terminal, viewer user terminal) included in the non-face-to-face remote business processing system by user interface sharing according to an embodiment of the present invention. FIG. 3 is a conceptual diagram of a non-face-to-face remote business processing system by user interface sharing according to an embodiment of the present invention. FIG. 4 is a conceptual diagram for overall sharing and partial sharing. FIG. 5 is a conceptual diagram for signature data sharing. FIG. 6 is a conceptual diagram for image and audio data sharing. FIG. 7 is a conceptual diagram for history logging and replay functions. FIG. 8 is a conceptual diagram for multiple sharing.

[0033] The non-face-to-face remote business processing system and method based on user interface sharing according to an embodiment of the present invention can provide a service that enables remote sharing and collaborative work of all user interface (UI) blocks implemented on the Web.

[0034] In the context of digital transformation and the post-pandemic situation, non-face-to-face remote business is positioned as an essential element. While remote service businesses using non-face-to-face technologies are booming in various fields such as finance, healthcare, and education, this embodiment also aims to enable non-face-to-face remote business processing by sharing the user interface.

[0035] Referring to FIG. 1, the non-face-to-face remote business processing system 1 based on user interface sharing according to this embodiment can include a business support server 10, a first user terminal 50, and a second user terminal 60. Here, the business support server 10, the first user terminal 50, and the second user terminal 60 may be connected via a wired or wireless network.

[0036] The first user terminal 50 is a terminal device operated by a staff member who is a service provider providing a specific service. It is a computing device equipped with an operating system that can install or is capable of installing a non-face-to-face remote business processing-related application or program (hereinafter referred to as an application) according to this embodiment and can run the application, and can be, for example, a smartphone, a tablet PC, a notebook computer, a desktop PC, etc. The first user terminal 50 can be a shared user terminal that shares its own screen.

[0037] The second user terminal 60 is a terminal device owned or operated by a customer who is a user to whom a specific service is provided. The second user terminal 60 is also equipped with a non-face-to-face remote business processing related application according to this embodiment, or can be installed through download, and is a computing device equipped with an operating system capable of executing the application, and can be, for example, a smartphone, a tablet PC, a notebook computer, a desktop PC, etc. The second user terminal 60 can be a viewer user terminal that shares and displays the screen of the first user.

[0038] The business support server 10 is a server device that communicates with the first user terminal 50 and the second user terminal 60, and enables the smooth provision of the service by sharing the user interface between the first user terminal 50 and the second user terminal 60.

[0039] The business support server 10 can include a device sharing server 11, a user interface sharing server 12, a session management server 13, and a push server 14 included in the execution architecture. Furthermore, it can further include any one or more of a monitoring server 15, a plugin management server 16, a user account management server 17, and an update server 18 included in the operating architecture.

[0040] The device sharing server 11 manages the device list and status connected to the terminal (especially the first user terminal 50). Then, it shares the devices included in the device list so that they can be accessed and used from other terminals (for example, the second user terminal 60 or the terminals of other staff).

[0041] The user interface sharing server 12 manages the connection information of application users (customers, staff, etc.). Then, it provides a cooperation function between the server and the application for sharing the user interface between user terminals (for example, screen sharing, data sharing, event sharing, annotation functions, etc.).

[0042] The session management server 13 manages the permissions and authentication for application users to access the access point gateway (AP Gateway).

[0043] The push server 14 transfers various known messages, news, etc. to the application.

[0044] The monitoring server 15 monitors and collects the states of the terminals (the first user terminal 50 and the second user terminal 60) on which the application is running. By analyzing the collected data, it can respond to failures and provide information regarding the terminal states as requested.

[0045] The plugin management server 16 registers and manages the plugins that cooperate with the application. It can provide the necessary plugin information in cooperation with the build process.

[0046] The user account management server 17 manages the accounts of application users (customers, employees, etc.).

[0047] The update server 18 provides the function of distributing and installing the application, plugins, or related files.

[0048] Referring to FIG. 2, it is a block diagram of a terminal (the first user terminal 50 or the second user terminal 60) on which the application is installed or installed after being downloaded.

[0049] The terminal 50 / 60 can include a communication module 71, a Web view module 72, an interface module 73, an update module 74, a monitoring module 75, a sharing module 76, an image / audio module 77, and a device / plugin management module 78.

[0050] The communication module 71 communicates with the business support server 10 to send and receive various data and files. The communication module 71 can include mobile communication devices such as 3G, 4G, 5G, etc. and / or short-range communication devices such as Bluetooth, Wi-Fi, etc. The data and files sent and received via the communication module 71 are encrypted via an encryption module (not shown) to provide protection against hacking and the like.

[0051] The Web view module 72 displays a screen corresponding to the execution of the application 80.

[0052] The interface module 73 can be a native interface, for example, a JavaScript Native Interface.

[0053] The update module 74 receives files distributed from the update server 18 via the communication module 71 and updates the application, plug-in, or related module.

[0054] The monitoring module 75 collects various data and logging related to the terminal state during the execution of the application and transfers them to the monitoring server 15 via the communication module 71.

[0055] The image / audio module 77 supports video calls or voice calls between staff and customers so that non-face-to-face (or contactless) services can be provided during the service delivery process. In the case of a voice call, it can include a microphone and a speaker, and in the case of a video call, it can further include a camera.

[0056] The device / plug-in management module 78 manages the devices and plug-ins with which the application cooperates.

[0057] The shared module 76 can be a user interface sharing module that provides a user interface sharing function. User interface sharing may include screen sharing, data sharing, history logging and replay, event sharing, annotation functions, etc. In addition, the shared module 76 can also provide a device sharing function.

[0058] For the user interface sharing function, especially the screen sharing function, when a connection for business support is established according to a pre-specified method among a plurality of terminals that wish to be interconnected, the entire screen or a part of the screen of the first user terminal 50 is shared and displayed in a specified area of the second user terminal 60, enabling non-face-to-face remote business processing. Alternatively, the shared user and the viewer user can be switched, and the entire screen or a part of the screen of the second user terminal 60 is shared and displayed in a specified area of the first user terminal 50, enabling the smooth execution or assistance of the business required by the customer without the staff directly handling the second user terminal 60.

[0059] The device sharing function allows access to a device (e.g., a printer, a card issuer, etc.) connected to a specific first user terminal 50 from other terminals (the second user terminal 60 or other staff terminals) that are not directly connected to the device, enabling business operations (such as printing output, card issuance, etc.) through the corresponding device.

[0060] The non-face-to-face remote business processing system and method based on user interface sharing according to this embodiment can be utilized as follows.

[0061] In the process digital environment of the financial circle of the digital transformation infrastructure, financial business staff can collaborate and share operations such as electronic signatures, product designs, and settlement requests between customers and staff in environments such as ODS (Out Door Sales) and Mobile Branch regardless of the device model. It can also be used in digital kiosks linked to a biometric authentication system without a passbook or card.

[0062] When building a naval combat system where security is essential and indispensable in the defense field, it is possible to access and control various hardware such as weapons and sensors, support high-level security requirements, and support offline execution to ensure normal operation during network disconnection.

[0063] In the e-learning field, it is possible to enable interaction between teachers and students, share the learning and lecture content of teachers with the terminals of students located remotely, and provide e-learning services. It is possible to conduct collaborative classes through two-way communication by sharing an electronic blackboard and the terminals of students, and it is possible to conduct interactive collaborative classes between teachers and students by utilizing the push function.

[0064] In public services for the general public, when entering or leaving the country at airports / ports, etc., it is possible to share the kiosks for identity verification, automatic certificate issuers, and the terminal environment of customers, enabling face-to-face / non-face-to-face sharing services for the general public by public institutions.

[0065] In the manufacturing environment of the digital twin infrastructure, the dynamic simulation of physical things and systems is digitized mainly in the manufacturing field, and the user terminal environment for the simulation of the design, operation, and maintenance of production facilities, as well as the virtual education of on-site workers, can be carried out through collaboration and sharing.

[0066] In the digital medical field, it is utilized for building a remote medical diagnosis system that supports real-time sharing of biological information collected through IoT devices, and the interlocking of medical devices and the EMR (electronic medical record) system can be utilized.

[0067] In the collaborative software development environment, it is possible to support shared development tools that enable knowledge sharing and real-time code review in collaborative work, co-ownership, and horizontal relationships.

[0068] In the field of call centers, when a help request occurs during the use of an application, remote support can be provided by using call and sharing services. The counselor can share the customer's screen through the sharing service to check the content of the inquiry and guide the customer using the screen guidance function. This makes it possible to process inquiries more easily and quickly than handling customers via calls or messages.

[0069] Referring to FIG. 3, a partial area 55 of the terminal screen 50 of the sharing user is set as a shared screen, and the shared screen 65 can be displayed on the terminal screen 60 of the viewer user connected to the network. In this embodiment, not only such screen sharing but also data sharing and event sharing are possible, and an annotation function can also be provided.

[0070] In this embodiment, the user interface sharing may include the following items.

[0071] Full sharing of a web page: A function to share the entire web page of a user with other users

[0072] Partial sharing of a web page: A function to share a partial area of a user's web page with other users (see FIG. 3)

[0073] Data sharing: A function to transfer data between shared devices, signed data sharing

[0074] History Logging & Replay: A function to log and replay the operation history on the shared screen

[0075] Multi - user collaboration function: Multiple users can interactively control the screen shared among them and update the screen

[0076] Event sharing: A function to share events such as touches, clicks, and inputs on the shared screen

[0077] Annotation function: Supports collaboration by using a fluorescent pen and / or creating annotations on a shared screen

[0078] Referring to FIG. 4, the concepts of whole sharing and partial sharing are shown.

[0079] In the case of whole sharing, it is to share the entire page 52 implemented on the Web. The shared user terminal and the viewer user terminal share the same content. The shared user and the viewer user can be controllably implemented with respect to the entire shared page.

[0080] In the case of partial sharing, it is to share only a partial area 55 of the page implemented on the Web. By sharing only a partial area, it is possible to share only the content necessary for security or business. The shared user and the viewer user can be controllably implemented with respect to the shared partial area.

[0081] Referring to FIG. 5, the concept of transfer of signature data is shown.

[0082] When it is necessary for the shared user terminal 50 processing the business to receive a handwritten signature from the viewer user, when a partial area (signature area) where a handwritten signature is required is selected, a view for signature creation is provided on the viewer screen (viewer user terminal screen), and a handwritten signature can be input using the pen function.

[0083] The view for signature creation may include a pop-up window 67 that is executed on the viewer screen for inputting a handwritten signature. In the screen shared on the viewer screen through whole sharing or partial sharing, the part where a handwritten signature is required may be displayed small depending on the screen ratio. Therefore, by displaying the pop-up window 67, the viewer user can more clearly recognize the part where the current input is required, enabling accurate input of signature data.

[0084] In this way, it is possible to store the electronically signed document signed by the real-time signature function in the situation of user interface sharing.

[0085] Referring to FIG. 6, the concept of transferring photo and audio data is shown.

[0086] The viewer user terminal can be a mobile terminal. In this case, by linking the shooting function using the camera provided in the viewer user terminal, the image (e.g., face, etc.) of the viewer user can be captured, and the image data can be transferred to the shared user terminal.

[0087] Alternatively, by linking the recording function using the microphone provided in the viewer user terminal, the voice of the viewer user can be acquired, and the audio data can be transferred to the shared user terminal.

[0088] Here, the image data can be used for personal authentication in relation to documents (e.g., contract documents) created through user interface sharing.

[0089] The audio data is data obtained by recording the voice of the contractor reading important sentences in the contract document, and can also be used for personal authentication.

[0090] Referring to FIG. 7, the concept of history logging and replay is shown.

[0091] When the user interface sharing function is used, history logging and replay functions can be provided. When the shared user terminal and the viewer user terminal are connected and the user interface sharing function is activated, for a certain period, that is, depending on whether a predetermined event has occurred or not, the history recording related to the shared processing information (e.g., a combination of the shared screen and the generated events (user operations such as clicks, mouse movements, inputs, signatures, annotation processing, etc.)) can be started or ended.

[0092] At this time, the user interface sharing server 12 functions as a broker server and stores the history recording related to the shared processing information in the database.

[0093] The history record can be replayed upon request. The replay is such that the shared processing information from the start time to the end time of the history record is reproduced over time, and it can be provided in a manner of displaying a shared screen and reproducing the generated events.

[0094] For example, in the case of non-face-to-face business where content confirmation and signature for a contract document consisting of multiple pages are required, a series of processes from the time when an input is made by a shared user or a viewer user to the time when the creation of the final contract document is completed can be recorded as a history. By checking such a history record through replay, it is possible to verify whether a normal contract has been made.

[0095] Regarding the history record, by enabling options such as filter level, filter target, storage period, etc. to be set, it is possible to prevent unlimited replay and replay by unqualified persons.

[0096] At the time of history recording, the sharing module 76 of the terminal can activate the front camera on at least one of the shared user terminal and the viewer user terminal, take a picture of the shared user or the viewer user at an arbitrary time point that the shared user and the viewer user cannot recognize, and attach the image data and the shooting time point information as authentication materials to the history record and hold them together.

[0097] This is to enable the verification of the identity of the user in the sharing function by overlapping and displaying the image data taken at the shooting time on the shared screen reproduced when replaying the history record later, or by displaying it in another area.

[0098] For example, assume a situation where an employee and a customer are concluding an insurance contract non-face-to-face through a user interface sharing function. For a normal insurance contract conclusion, it is required that the employee share multiple contract-related pages on the screen for the customer to see and receive the customer's handwritten signature. Such a series of processes is held as a history record by the history logging function, and it becomes possible to determine whether the insurance contract conclusion is normal.

[0099] Also, at the moment when the customer signs by hand or agrees and confirms the signed document, by taking a picture of the face of the person signing by hand when signing by hand using the camera of the customer terminal, it is possible to confirm whether the signature by hand is being made by someone other than the customer, prevent an improper contract from being concluded, or use it as strong evidence when disputing the validity of the contract even after the contract is concluded. Furthermore, for important clauses, the customer can be made to read them afterwards, and the voice data recorded thereof can be obtained and attached as authentication materials to the history record.

[0100] Such signature documents, image data, and voice data can be encrypted in their original forms and stored and managed in a database.

[0101] Also, FIG. 8 shows the concept of the multi-viewer function.

[0102] Contents shared by a sharing user using a terminal can be shared together by a plurality of viewer users using their respective terminals.

[0103] Some viewer user terminals are provided only in a simple viewer mode, and only for the designated viewer user terminals, they can be set to a mode that can cooperate with the sharing user terminal, and functions such as correction and annotation for the shared content can also be applied.

[0104] Hereinafter, a non-face-to-face remote business processing method performed by a non-face-to-face remote business processing system using user interface sharing according to the present embodiment will be described with reference to the related drawings. For the convenience of understanding and explanation of the present invention, it is assumed that the screen sharing function among the user interface sharing functions is applied to the financial circle ODS.

[0105] FIGS. 9 and 10 are diagrams showing a business support process by screen sharing according to an embodiment of the present invention, FIG. 11 is an exemplary diagram of business screen sharing between a customer terminal and a staff terminal, and FIG. 12 is a diagram regarding a screen view.

[0106] The customer service process in the smart store is shown in FIG. 9. Assume that the first user terminal 50 is a staff terminal, and the second user terminals 61 and 62 are customer terminals.

[0107] The customer determines whether to handle the business face-to-face with the staff or by himself / herself when visiting the store (step S100).

[0108] When the customer handles the business by himself / herself, he / she can perform deposit / withdrawal / remittance processing at an ATM (Automated Teller Machine), or directly handle counter services such as new card / re-issuance, OTP issuance, passbook re-issuance, password change, etc. at an STM (Smart Teller Machine, Self Teller Machine) (step S105).

[0109] In the case of a customer with face-to-face business processing with the staff, it is determined whether a bank application is installed on the first customer terminal 61 (mobile phone, smart phone) (step S110).

[0110] If the bank application is installed, the staff terminal 50 and the first customer terminal 61 can cooperate to process the business through screen / data sharing (step S115).

[0111] If the bank application is not installed, the second customer terminal 62 (bank-owned tablet or PC provided for customer use) provided at the counter and the staff terminal 50 can cooperate to process the business (step S120).

[0112] Here, the first customer terminal 61 and the second customer terminal 62 are terminals on which the bank application is installed. Although there is a difference in ownership between the customer and the bank, they have the common point that both are used by the customer in the process of bank business processing.

[0113] Referring to FIG. 10, in step S115, the process in which the staff terminal 50 and the first customer terminal 61 cooperate to process business will be described in more detail.

[0114] To identify the terminal that wishes to share the screen and establish an interconnection, first, the staff terminal 50 generates and displays an identification code (for example, a QR code (registered trademark)) (step S200).

[0115] On the first customer terminal 61, by using the camera to capture the identification code displayed on the staff terminal 50, information regarding the staff terminal 50 to be shared can be extracted, and an interconnection can be established between the staff terminal 50 and the first customer terminal 61 to start sharing (step S205).

[0116] Here, the case where the identification code is generated by the staff terminal 50 has been described by way of assumption, but this is merely one embodiment, and it is also possible to generate the identification code on the first customer terminal 61 and have the staff terminal 50 capture it to establish an interconnection.

[0117] That is, when there are two terminals that wish to establish an interconnection, an identification code can be generated on any terminal, and the other terminal can capture the generated identification code and extract the terminal information of the terminal that generated the identification code, thereby establishing an interconnection for sharing (screen and / or data) between the two terminals.

[0118] When the interconnection is established, the necessary business screen among the shared screens of the first customer terminal 61 is shared (step S210). The business screen sharing can be performed on all or a pre-specified partial area (screen area A) of the application execution screen of the first customer terminal 61.

[0119] On the staff terminal 50, the shared screen can be displayed at a pre-specified position. In the drawing, the shared screen (customer screen) is displayed in part A, and content (business area, common area) for smooth business processing corresponding to the content of the shared screen can be displayed in parts B and C.

[0120] Referring to FIG. 11, a case is shown where business screen sharing is performed between the first customer terminal 61 and the staff terminal 50. In a designated area (A) of the staff terminal 50, the customer screen can be mirrored and displayed.

[0121] Thereafter, on the first customer terminal 61, items that require customer input can be output via the shared screen to receive customer input (step S215). In this case, the customer input items can be minimized so as not to cause inconvenience to the customer.

[0122] In response to the customer input, reception business processes such as card issuance business, OTP issuance business, and biometric information registration, and credit-granting business processes such as loan application electronic signature are performed.

[0123] Also, a biometric authentication medium using fingerprints, iris, etc. can be registered through the bank application installed on the first customer terminal 61 and then made available as an identity authentication means on the counter ATM (or STM) device (step S220). At this time, on the first customer terminal 61, not the biometric authentication information itself is transmitted, but only the authentication result is transferred, so that sensitive personal information can be protected.

[0124] Also, bank devices such as a card issuer, a card-type OTP issuer, and a printer that are jointly used at the business office are connected to the staff terminal 50 so that the operations processed at the previous counter can be processed (step S225).

[0125] The situation where the customer is the shared user, the staff is the viewer user, and the staff terminal functions as a viewer to share the screen of the customer terminal has been mainly described. Needless to say, in the situation where the customer terminal functions as a viewer to share a part of the screen of the staff terminal, the shared user and the viewer user can be changed.

[0126] In this embodiment, screen sharing is performed between two different devices for non-face-to-face remote business processing. At this time, displays with different specifications can be applied to both devices.

[0127] Therefore, it is possible to apply a one-source multi-use (OSMU) screen view that can enlarge or reduce the same screen according to the resolutions of various devices, from smartphones, tablets to PCs.

[0128] Referring to FIG. 12, it is possible to control so that the shared screen is enlarged or reduced at a certain ratio and the same customer screen is displayed on a PC and a tablet or smartphone.

[0129] In this case, in the staff terminal 50 as shown in FIG. 11, a screen view is applied to the customer screen and the business area, and it is possible to minimize the screen scroll by customer screen mirroring. For example, when the size of the display device for displaying content becomes small, horizontal scroll and vertical scroll may occur simultaneously. The screen view function that changes the screen size so that horizontal scroll does not occur in such a situation can minimize the scroll request.

[0130] FIG. 13 is a diagram showing a user interface sharing process for non-face-to-face remote business processing.

[0131] In the case of FIG. 13, the case of generating an identification code in the first customer terminal 61 is shown.

[0132] When the application is executed in the first customer terminal 61 and there is an input of a sharing request from the customer, it requests the business support server 10 to generate a token for business sharing (step S300). In the business support server 10, particularly in the business sharing server 12, a token that can identify the terminal is generated and provided in response to the request from the terminal.

[0133] The first customer terminal 61 generates an identification code including the token and connection information (encrypted URL information including authentication information) included in the response received in response to the token generation request (step S305). The identification code can be, for example, a QR code (registered trademark).

[0134] The generated identification code is passed to the staff terminal 50 that wishes to share (step S310). As a method for distributing the identification code, a method of acquiring video data by photographing the identification code displayed on the screen of the first customer terminal 61 with the camera of the staff terminal 50 can be applied.

[0135] The staff terminal 50 transfers a sharing screen request including the identification code and the logged-in staff information to the business support server 10 (step S315). Using the session management server 13 and the user account management server 17, it is confirmed that the staff using the staff terminal 50 has the necessary permissions.

[0136] Then, the information (identification code) necessary to access the screen shared by the customer can be transmitted to the business sharing server 12 to set up a connection. The business support server 10 compares the token included in the sharing screen request of the staff terminal 50 with the token generated in step S300 above to verify that it is a legitimate request, and if the two tokens are equal, access to the sharing screen is permitted.

[0137] Thereafter, the business support server 10 accesses the sharing screen among the application screens executed on the first customer terminal 61 according to the connection information (step S320), transmits the sharing screen to the staff terminal 50, and establishes an interconnection between the first customer terminal 61 and the staff terminal 50, and screen sharing (which can also include data sharing) is performed.

[0138] In a state where screen sharing is performed, the device sharing process may additionally be performed. At the first customer terminal 61, a request to share a remote device (for example, a card issuer) with the business support server 10 is made (step S325). The sharing request includes a token, and the business support server 10 can verify the validity of the transmitted token and confirm the first customer terminal 61 that made the request.

[0139] If it is a valid request, the business support server 10 transmits a control request for the remote device to the staff terminal 50 connected to the remote device (step S330).

[0140] At the staff terminal 50, after comparing the information transmitted via the identification code with the information transmitted from the business support server 10 and confirming its validity, if it is valid, the remote device can be controlled according to the command included in the control request to cause the first customer terminal 61 to execute a desired task (step S335).

[0141] Above, the explanation was centered on screen sharing via the first customer terminal 61 held by the customer. The same screen sharing can be performed in the case of the second customer terminal 62 owned by the bank. In this case, in the case of the second customer terminal 62, after the staff confirms the customer identification certificate for the customer to log in or performs customer authentication using the biometric information (vein, fingerprint, etc.) of the customer registered with the bank, screen sharing can be performed so that the business process desired by the customer can be carried out.

[0142] Also, as described above, in other embodiments, it goes without saying that the identification code can be generated and output at the staff terminal instead of the customer terminal, and this can be photographed at the customer terminal to establish mutual connection.

[0143] FIG. 14 is a diagram showing the architecture of a multi-platform application development system according to an embodiment of the present invention.

[0144] As described above, a multi-platform application can be an application that provides business support through user interface sharing between two devices driven by different platforms.

[0145] Referring to FIG. 14, each component of the business support server 10 may be included in an execution architecture (such as a device sharing server 11, a user interface sharing server 12, a session management server 13, a push server 14, etc.) and an operation architecture (such as a monitoring server 15, a plugin management server 16, a user account management server 17, an update server 18, etc.).

[0146] In addition, it can include a build distribution (deploy) master server 30 that is additionally included in the development architecture. The build distribution master server 30 manages and controls a build node 31 and a distribution node 32 that perform the build and distribution processes of the application to be provided to developers and service operators.

[0147] The build node 31 provides a service for generating executable files that can be executed on Android, iOS, Windows, Linux (registered trademark), and Kiosk platforms.

[0148] The distribution node 32 distributes the application to stores provided by platforms such as the App Store, Play Store, and Microsoft Store.

[0149] The above non-face-to-face remote business processing method through user interface sharing can also be embodied in the form of a recording medium containing computer-executable instruction words such as an application or a program module executed by a computer. A computer-readable medium can be any available medium accessible by a computer, including all volatile and non-volatile media, and separable and non-separable media. Further, a computer-readable medium can include a computer storage medium. A computer storage medium includes volatile and non-volatile, separable and non-separable media embodied in any method or technology for storing information such as computer-readable instruction words, data structures, program modules, or other data.

[0150] The above non-face-to-face remote business processing method through user interface sharing can be executed by an application basically installed on the terminal (which can include programs included in the platform and operating system basically installed on the terminal), or can be executed by an application (i.e., a program) directly installed on the master terminal by the user via an application providing server such as an application store server, an application, or a web server related to the service. In this sense, the above non-face-to-face remote business processing method through user interface sharing is embodied in an application (i.e., a program) basically installed on the terminal or directly installed by the user, and can be recorded on a recording medium readable by a computer such as a terminal.

[0151] In the above, the embodiments of the present invention have been described with reference to the embodiments. However, those of ordinary skill in the art will understand that the present invention can be variously modified and changed without departing from the spirit and scope of the present invention described in the following claims.

Claims

1. A non-face-to-face remote business processing system by sharing a user interface, comprising: a first user terminal on which a service application is installed and executed; a second user terminal that shares and displays a user interface by executing the service application; a business support server that communicates with the first user terminal and the second user terminal and is configured to be able to share the user interface of the first user terminal on the second user terminal under specified conditions, enabling non-face-to-face and remote business processing; at least one of the first user terminal and the second user terminal includes a user interface sharing module that performs history logging related to user interface sharing; the user interface sharing module records a history related to sharing process information between the first user terminal and the second user terminal during a certain period and stores it in a database; the sharing process information is a combination of a shared screen and an event occurrence related to user operations; the user interface sharing module provides a replay function that reads out the history records stored in the database upon request, displays the shared screen, and reproduces the event occurrence; the user interface sharing module is characterized in that during history logging, it activates a front camera provided on the terminal, attaches image data obtained by photographing the shared user or viewer user and the photographing time information as authentication materials to the history record, and stores them together, a non-face-to-face remote business processing system by sharing a user interface.

2. The non-face-to-face remote business processing system by sharing a user interface according to Claim 1, wherein the event occurrence includes at least one of click, mouse movement, input, signature, and annotation processing.

3. The non-face-to-face remote business processing system by sharing a user interface according to Claim 1, wherein the user interface sharing module activates a microphone provided on the terminal during history logging, attaches voice data obtained by recording the voice of the shared user or viewer user as authentication materials to the history record, and stores them together.

4. The above business support server generates a token in response to a request for generating a token for user interface sharing from any one of the above first user terminal and the above second user terminal, and transfers the token to the terminal that made the request. The non-face-to-face remote business processing system according to claim 1, characterized in that it determines whether a token included in a sharing request from the other one of the above first user terminal and the above second user terminal is equal to the token transferred to any one of the above first user terminal and the above second user terminal, and decides whether to permit sharing.

5. Any one of the above first user terminal and the above second user terminal generates an identification code including the above token and connection information to the above business support server, and outputs the identification code on the screen. The non-face-to-face remote business processing system according to claim 4, characterized in that the other one of the above first user terminal and the above second user terminal generates the above sharing request using the data obtained by photographing the above identification code.

6. A non-face-to-face remote business processing method performed in a non-face-to-face remote business processing system by user interface sharing, comprising: a step in which a first user terminal and a second user terminal start user interface sharing; when a pre-specified condition is satisfied, a step of logging a history regarding a shared screen and generated events from a user interface sharing module included in at least one of the above first user terminal and the above second user terminal; a step in which the above user interface sharing module stores the history record in a database; a step in which, when there is a replay request for the above history record, the above user interface sharing module reads the above history record from the above database, displays the above shared screen, and sequentially reproduces the above generated events. In the step of logging the above history, during the logging of the history, the front camera provided in the terminal is operated to attach image data obtained by photographing a shared user or a viewer user and the photographing time point information to the above history record as authentication materials and hold them together. A non-face-to-face remote business processing method characterized by this.

7. In the step of logging the above history, during the logging of the history, the microphone provided in the terminal is activated, and voice data obtained by recording the voices of the shared user or the viewer user is attached to the above history record as authentication materials and held together. The non-face-to-face remote business processing method according to claim 6, characterized in that.

Images