System and method for providing a qr code-based virtual contact service

Abstract

The present invention relates to a QR code-based virtual contact system, comprising: a policy management module that stores a routing policy, a virtual contact replacement policy, a call restriction policy, and a call release policy associated with a recipient profile; A control module that receives a connection request by recognizing a QR code identifying the recipient profile, determines a contact to be connected based on the time zone or day of the week at the time of the connection request based on the routing policy, and requests the issuance of a first virtual contact for the contact to be connected; and a connection execution module that issues the first virtual contact in response to the issuance request, executes a connection using the first virtual contact, and transmits communication record data regarding the result of the connection execution to the control module; wherein the control module, when the first virtual contact corresponding to the contact to be connected is received from the connection execution module, generates call screen data including display information associated with the first virtual contact, and when it is determined that the first virtual contact needs to be replaced based on the virtual contact replacement policy, transmits a virtual contact replacement request to the connection execution module, and when the second virtual contact is received from the connection execution module in response to the replacement request, updates and applies the second virtual contact to the call screen data. Accordingly, according to the present invention, it is possible to immediately connect to various channels such as telephone, messenger, and email by simply scanning a QR code, thereby ensuring constant online connectivity. Additionally, the contact to be connected is automatically switched according to the time of the connection request, reducing false calls while unavailable, and flexible response is possible by reflecting shifts, days off, etc.

Description

Technology Field

[0001] The present invention relates to a QR code-based virtual contact system and method that provides a virtual connection with a recipient via QR code scanning, and more specifically, to a QR code-based virtual contact system and method that performs a connection through a virtual contact without exposing the recipient's actual contact information. Background Technology

[0002] With the rise in digital transformation and non-face-to-face contact, there is an increasing number of cases where recipients' actual contact information is exposed in areas such as vehicle and parking communications, delivery services, store and facility inquiries, and local transactions, leading to misuse for repeated calls, unauthorized collection, and fraud inducement.

[0003] To prevent such risks, methods of mediating temporary secure numbers have become widespread; however, alternative numbers are also vulnerable to repeated call attempts as they are continuously matched with individuals, and there are problems in that multi-channel integration and policy-based control are difficult as they are mainly limited to voice calls.

[0004] Therefore, technology is required that enables connection with recipients via phone, messenger, email, etc., at any time online without disclosing the user's actual contact information, and can dynamically manage contact targets, channels, display information, and virtual contacts in accordance with the protection of recipients' personal information and operational policies. The problem to be solved

[0005] The present specification aims to provide a QR code-based virtual contact system and method that can be connected through various channels without exposing the recipient's actual contact information.

[0006] In addition, the present specification aims to provide a QR code-based virtual contact system and method capable of supporting flexible routing based on time zones or days of the week.

[0007] In addition, the present specification aims to provide a QR code-based virtual contact system and method that provides a customized call screen according to the QR code type.

[0008] In addition, the present specification aims to provide a QR code-based virtual contact system and method that prevents long-term exposure and reuse of virtual contacts by periodically replacing virtual contacts.

[0009] This specification is not limited to the problems mentioned above, and other problems not mentioned will be clearly understood by a person skilled in the art from the description below. means of solving the problem

[0010] A QR code-based virtual contact system according to an embodiment of the present invention for achieving the above-mentioned purpose comprises: a policy management module that stores a routing policy, a virtual contact replacement policy, a call restriction policy, and a call release policy associated with a recipient profile; A control module that receives a connection request by recognizing a QR code identifying the recipient profile, determines a contact to be connected based on the time zone or day of the week at the time of the connection request based on the routing policy, and requests the issuance of a first virtual contact for the contact to be connected; and a connection execution module that issues the first virtual contact in response to the issuance request, executes a connection using the first virtual contact, and transmits communication record data regarding the result of the connection execution to the control module; wherein the control module, when the first virtual contact corresponding to the contact to be connected is received from the connection execution module, generates call screen data including display information associated with the first virtual contact, and when it is determined that the first virtual contact needs to be replaced based on the virtual contact replacement policy, transmits a virtual contact replacement request to the connection execution module, and when the second virtual contact is received from the connection execution module in response to the replacement request, updates and applies the second virtual contact to the call screen data.

[0011] Here, the routing policy includes a time table in which connection target contacts corresponding to different recipient terminals are mapped according to time zone or day of the week, and the control module can select a connection target contact mapped to a slot corresponding to the time zone or day of the week at the time of the connection request by referring to the time table.

[0012] In addition, the display information is provided in the form of a button or link to which the virtual contact is mapped, and the control module can automatically update the display information according to a time zone, day of the week, or a preset period.

[0013] In addition, the control module may set an initial virtual contact corresponding to each connection target contact to be assigned in advance, and may request an update of the initial virtual contact according to the virtual contact replacement policy.

[0014] Here, the virtual contact may include one or more of a phone number, email address, messenger ID, or tokenized session link.

[0015] In addition, a QR code-based virtual contact system according to one embodiment of the present invention may further include a QR management module configured to map and store one or more QR code identifiers to a recipient profile, and to map and store at least one of a QR type, a call screen template, and organization display information to each QR code.

[0016] The above QR management module stores organization display information including organization identification information, organization name, or organization logo, and the above control module can control the organization identification information, organization name, or organization logo to be forcibly displayed in the above call screen data.

[0017] In addition, the virtual contact replacement policy may be configured to replace the virtual contact when the number of connection executions for the first virtual contact is greater than a predetermined number (N) or at preset intervals.

[0018] In addition, the communication record data includes at least one of the connection request start and end times, result status, duration, reason code, caller identifier, and virtual contact ID, and the control module can update a connection attempt counter using the communication record data and determine whether to restrict outgoing calls based on the counter.

[0019] Here, the control module may request the connection execution module to set the call restriction status of the corresponding virtual contact when the counter exceeds a threshold value (N), and may request the release of the call restriction status when the call restriction release policy is satisfied.

[0020] In addition, a QR code-based virtual contact method according to an embodiment of the present invention, which provides a virtual connection with a recipient through a QR code, may include: receiving a connection request by recognizing a QR code; obtaining one or more of a routing policy, a virtual contact replacement policy, a call restriction policy, or a call restriction removal policy regarding a recipient profile corresponding to the connection request; determining a connection target contact corresponding to a time zone or day of the week at the time of the connection request based on the routing policy; requesting the issuance or activation of a first virtual contact for the connection target contact and receiving the first virtual contact; generating and providing call screen data including display information associated with the first virtual contact; determining whether replacement of the first virtual contact assigned to the connection target contact is necessary according to the virtual contact replacement policy, and if it is determined that the virtual contact replacement policy is satisfied, transmitting a request for virtual contact replacement; and receiving a second virtual contact in response to the virtual contact replacement request and automatically reflecting the second virtual contact in the call screen data. Effects of the invention

[0021] According to the present specification, by simply scanning a QR code, one can instantly connect to various channels such as phone, messenger, and email, thereby ensuring constant online connectivity.

[0022] In addition, according to the present specification, the contact to be connected is automatically switched depending on the time of the connection request, thereby reducing false calls while out of office, and allows for flexible response by reflecting shifts, days off, etc.

[0023] In addition, according to the present specification, call screen data can be automatically generated and updated depending on the QR type to improve the user experience.

[0024] In addition, according to the present specification, the renewal or restriction and release of outgoing calls of virtual contacts are applied based on the number of times the virtual contact is used, the number of connection attempts, etc., in accordance with the virtual contact replacement policy, thereby reducing the risk of number crawling, reuse, and session hijacking.

[0025] The effects of the present invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description below. Brief explanation of the drawing

[0026] FIG. 1 is a diagram for schematically explaining the overall configuration of a QR code-based virtual contact system (100) according to one embodiment of the present invention. FIG. 2 is a diagram illustrating, in an exemplary manner, the group registration management flow in a QR code-based virtual contact system (100) according to one embodiment of the present invention. FIG. 3 is a block diagram illustrating each component of a QR code-based virtual contact system (100) according to one embodiment of the present invention. FIG. 4 is a diagram illustrating, by way of example, the outgoing processing and virtual contact issuance, activation, or replacement procedure performed by a control module (130) according to one embodiment of the present invention. FIG. 5 is a diagram illustrating, exemplarily, the procedure for restricting and releasing transmission performed by a control module (130) according to another embodiment of the present invention. FIG. 6 is a flowchart illustrating a QR code-based virtual contact method according to an embodiment of the present invention. FIG. 7 is a drawing for exemplarily illustrating a user interface according to one embodiment of the present invention. FIG. 8 is a flowchart illustrating a QR code-based virtual contact method according to another embodiment of the present invention. FIG. 9 is a block diagram showing a QR code-based virtual contact device according to one embodiment of the present invention. Specific details for implementing the invention

[0027] The following description merely illustrates the principles of the present invention. Therefore, those skilled in the art may invent various devices that embody the principles of the present invention and are included within the concept and scope of the present invention, even though they are not explicitly described or illustrated in this specification. Furthermore, all conditional terms and embodiments listed in this specification are, in principle, explicitly intended only for the purpose of understanding the concept of the present invention and should be understood not as being limited to the embodiments and conditions specifically listed as such.

[0028] The aforementioned objectives, features, and advantages will become clearer through the following detailed description in conjunction with the attached drawings, and accordingly, a person skilled in the art to which the present invention pertains will be able to easily implement the technical concept of the present invention.

[0029] In addition, in describing the present invention, if it is determined that a detailed description of known technology related to the present invention may unnecessarily obscure the essence of the present invention, such detailed description will be omitted.

[0030] In this specification, “virtual contact service” refers to a service that internally maps a virtual contact to a recipient’s actual contact and mediates or routes communication so that a sender initiates communication with a recipient through the virtual contact via channels such as telephone, text message, email, or messenger.

[0031] Additionally, in this specification, “QR code” is a machine-readable square code in the form of a two-dimensional matrix, which is an image encoded with an identifier (e.g., URL, token, key) used for system access or data for accessing said identifier. The QR code may be displayed on a printed medium or on a display, and when a user scans it with a reader device such as a camera, identifier information for system access can be obtained.

[0032] Additionally, in this specification, “recipient” refers to an individual or entity registered to receive contact through the system. A recipient terminal may refer to a terminal or service account designated by the recipient, and the recipient may be associated with one or more QR codes and one or more contacts (e.g., phone number, email, messenger ID, etc.).

[0033] Additionally, in this specification, the “sender” is an entity that recognizes a QR code, transmits a request to access the system, and initiates contact with the recipient. The sender terminal is an electronic device equipped with a camera or reader function, and may be, for example, one of a smartphone, tablet, laptop, PC, kiosk, vehicle terminal, etc.

[0034] Additionally, in this specification, the “Organization Manager” is an entity authorized to perform settings and access regarding the organization and its members, and may perform tasks such as approving or withdrawing membership of organization members, issuing organization codes, managing a registry of recipients affiliated with the organization (e.g., apartment building / unit number, vehicle identification level, etc.), setting organization display information (e.g., organization name, logo, etc.), and setting call screen templates. The Organization Manager may be restricted from directly accessing the actual contact information of recipients without authorization or the consent of the party concerned, and may be restricted to accessing the organization server only after authentication and authorization verification.

[0035] Additionally, in this specification, the “call screen” is a user interface including a button or link for initiating a connection with a recipient, which may be provided on the caller’s terminal when the caller recognizes a QR code and accesses the system. Furthermore, the call screen may additionally include a message set by the recipient and organization display information (e.g., organization name, organization logo, etc.), and the organization display information may be controlled to always be displayed according to a forced display flag. In this case, the configuration of the call screen and the display information may vary depending on the type of QR code (e.g., individual, organization, category, etc.) and policy, and the display information displayed on the call screen may be automatically updated and provided in accordance with policy changes.

[0036] Furthermore, in this specification, “virtual contact” refers to an identifier used to mediate communication or for mapping purposes without exposing the recipient’s actual contact information. For example, a virtual contact may include a logical identifier or a proxy identifier, and may be implemented in the form of, for instance, a proxy number, a messaging token, an email alias, a tokenized session link, etc. Virtual contacts may be issued, activated, updated, or invalidated, and policies such as restrictions on sending or lifting may be applied. In this case, the connection execution may be performed via a button or link provided on the call screen, or it may also be performed via gateway relay or API / deep link calls. Additionally, each QR code may be configured to have a static virtual contact assigned in advance or to have a dynamic virtual contact assigned upon the initial connection request.

[0037] Additionally, in this specification, “connection target contact” refers to the actual contact information of the recipient (e.g., phone number, email, messenger ID, etc.). Multiple connection target contacts may be registered in a single QR code account according to time zone, day of the week, role, work shift, etc., and the contact in the slot corresponding to the time of the request may be selected by a routing policy. The connection target contact is not directly exposed to the sender and can be used for routing by being internally mapped to a virtual contact issued and activated at runtime.

[0038] Various embodiments of the present invention will be described in detail below with reference to the attached drawings.

[0039] FIG. 1 is a diagram for schematically explaining the overall configuration of a QR code-based virtual contact system (100) according to one embodiment of the present invention.

[0040] A QR code-based virtual contact system (100) according to one embodiment of the present invention may include a central server (210), a virtual connection server (220), a QR management server (230), a member server (240), and an organization server (250), etc.

[0041] Referring to FIG. 1, when a central server (210) receives an online connection request via QR code scanning from a caller, it can retrieve QR metadata, such as a QR type corresponding to the QR code, from a QR management server (230). Additionally, the central server (210) can determine a contact to be connected based on the time of day or day of the week at the time of the connection request by referring to a timetable stored in a member server (240), and generate call screen data based on this and provide it to the caller terminal (10). One or more channel buttons or links may be displayed on the call screen, and a virtual contact issued by a virtual connection server (220) may be provided in association with each channel. Accordingly, the caller can initiate contact with the recipient by selecting one of the channel buttons (e.g., phone, text, chat, or email) provided through the call screen.

[0042] Meanwhile, the organization server (250) may be configured to look up and manage identification information for recipients belonging to the organization when a QR code is scanned through an administrator-only search page. The organization administrator issues an organization code from the organization server (250), and the recipient can be linked to the organization by registering the organization code when signing up for membership through the member server (240).

[0043] FIG. 2 is a diagram illustrating, in an exemplary manner, the group registration management flow in a QR code-based virtual contact system (100) according to one embodiment of the present invention.

[0044] In one embodiment, an organization manager can pre-register organization identification information via an organization code and scan a QR code assigned to a recipient belonging to the organization to retrieve information related to the recipient.

[0045] Referring to FIG. 2, the organization manager may request membership through the member server (240) (S210) and receive an organization code from the organization server (250) (S220). The organization code may be shared with recipients belonging to the organization (S230), and recipients belonging to the organization may request membership through the member server (240) (S240) and register the organization code corresponding to the QR code (S250). The organization server (250) may approve or revoke the organization registration of the recipient belonging to the organization based on the approval of the organization manager (S260), and accordingly, the QR identifier of the recipient whose organization registration has been approved and the organization display information may be mapped and stored in the QR management server (230).

[0046] Additionally, the organization server (250) can control the organization name or organization logo to always be displayed through the call screen (S270), and the organization manager can scan the QR code assigned to the recipient belonging to the organization (S280) to look up information related to the recipient (S290).

[0047] For example, in an embodiment of an apartment complex management organization, the organization manager receives an organization code through the organization server (250), and the resident (recipient) can register internal identification information such as vehicle number, building / unit number, etc. by mapping the organization code to their own QR code on the My Page of the member server (240). When the organization manager scans the QR code linked to the recipient, the apartment name or apartment logo is always displayed on the call screen, and the organization manager can look up the identification information of the recipient, such as vehicle number and building / unit number, mapped to the QR code through an administrator-only search page.

[0048] Depending on the implementation form, the functions of each server described above may be provided by combining some functions or integrating them into a single device, or they may be distributed in modular units within a single system or provided in conjunction with an external gateway.

[0049] Hereinafter, with reference to FIGS. 3 to 5, the operation of each module will be specifically explained, focusing on an embodiment in which a plurality of modules are distributed within a single system to perform the functions of the server described above.

[0050] Here, the term 'module' refers merely to a functional division and does not limit its physical arrangement; in actual implementation, two or more modules may be integrated into a single device or process, or a single module may be distributed across multiple devices or nodes for execution. Interfaces between modules may utilize standard APIs or protocols depending on the implementation, and each module may be realized as a software element, process, or hardware. Furthermore, the names of modules are for convenience of explanation, and configurations or variations performing substantially equivalent functions may also be included within the scope of the present invention.

[0051] FIG. 3 is a block diagram illustrating each component of a QR code-based virtual contact system (100) according to one embodiment of the present invention.

[0052] Referring to FIG. 3, the QR code-based virtual contact system (100) may include a policy management module (110), a QR management module (120), a control module (130), and a connection execution module (140).

[0053] The policy management module (110) can be configured to map and store routing policies, virtual contact replacement policies, outgoing restriction, and release policies associated with the recipient profile.

[0054] In one embodiment, the policy management module (110) can obtain policy information entered by a recipient or organization manager through a user interface (UI) provided on the My Page of the system (100), and can provide it for reference when determining the contact to be connected, replacing virtual contacts, restricting outgoing calls, or determining whether to lift the restriction by the control module (130) described later.

[0055] In another embodiment, the policy management module (110) can create and manage profiles for each recipient, and the recipient profile may include a recipient ID, account status (active / inactive), default display text, channel allowance range (phone / messenger / email / chat, etc.), priority information, etc.

[0056] The routing policy may include information mapping target contacts (e.g., phone number, email, messenger ID, etc.) corresponding to different recipient terminals based on time zone, day of the week, work shift, etc., as well as channel priorities, and may be stored in the form of a timetable. In this case, the timetable can be freely configured according to the recipient's preferences.

[0057] For example, from Monday to Friday between 9:00 and 12:00, the contact to be connected to the morning person in charge may be selected, between 12:00 and 18:00, the contact to be connected to the afternoon person in charge may be selected, between 18:00 and 23:00, the contact to be connected to the night person in charge may be selected, and during the period from 23:00 to 9:00, phone / messenger may be disabled and only channels such as text / email may be allowed.

[0058] Alternatively, for example, it can be configured to route to the contact of Manager A on Mondays, Wednesdays, and Fridays, to the contact of Manager B on Tuesdays and Thursdays, and to the emergency contact on weekends, or to be disabled.

[0059] Alternatively, for example, it can be set so that office contacts are selected during weekday daytime hours and personal contacts are selected during weekday evening hours.

[0060] Alternatively, for example, if no response persists for a certain period, it may be automatically rerouted to a secondary contact in the same slot, or it may be configured to apply channel priority based on the time of day or situation (e.g., phone calls prioritized during morning and afternoon hours, text messages prioritized during evening hours).

[0061] The virtual contact replacement policy can define one or more of the following as replacement triggers: the number of connection executions (N), a preset period or validity period, and the timetable slot change point.

[0062] The outgoing restriction policy may be configured to restrict outgoing calls from a sender based on the number of connection attempts by the same sender, and the control module (130), described below, may determine whether to apply the policy by counting the number of connection attempts that occurred within a time frame set based on the time of the connection request. The time frame may be operated as a sliding or fixed interval depending on the implementation.

[0063] In addition, the outgoing restriction release policy may be configured to release the outgoing restriction when a pre-set release condition is met after the outgoing restriction is set according to the aforementioned outgoing restriction policy, for example, after a predetermined period of time has elapsed.

[0064] The policy management module (110) can grant editing rights to policy information differently to the organization administrator, recipient, and operator, and all changes requiring permission can be configured to be performed after prior authentication.

[0065] Meanwhile, the aforementioned policy management module (110) may be implemented as a single management device integrated with the member server, embedded inside the server, or implemented as a separate database (DB).

[0066] The QR management module (120) is configured to store a recipient profile and one or more QR code identifiers by mapping them.

[0067] The QR management module (120) may be configured to store a recipient profile and one or more QR code identifiers by mapping them, and to store at least one of a QR type, a call screen template, and group display information for each QR code by mapping them.

[0068] QR type is metadata that determines the call path and screen configuration, and can be classified, for example, into personal type, group type, or type according to the recipient's setting purpose (e.g., lost property, missing child tag, pet tag, customer center, parking contact, etc.).

[0069] The call screen template is a user interface rendered when a QR code is scanned, and a default template based on the QR type may be stored, and it may be updated and provided according to the time of day, day of the week, or preset cycle at the time of the caller's connection request.

[0070] For example, the call screen may display messages set by the recipient (e.g., “Please use a messenger outside of business hours,” “Please contact a guardian”), contact buttons (e.g., phone, messenger, email, chat, etc.).

[0071] The organization display information may include organization identification information, organization name, or organization logo displayed on the call screen, and a forced display flag may be set to force the organization display information to be displayed on the call screen.

[0072] In one embodiment, the resident (recipient) can register a group code (apartment) on My Page and map and save the resident's vehicle number and unit number. The QR management server (120) can link the corresponding QR identifier with the group code and save group display information and a call screen template identifier. At this time, when the group manager (sender) logs into the manager-only search page and scans the QR code attached to the vehicle, the control module (130) can obtain the call screen template mapped to the corresponding QR code from the QR management server (120) to generate call screen data and control the apartment name or logo to always be displayed according to a forced display flag.

[0073] Meanwhile, metadata stored in the QR management module (120) can be referenced when creating a call screen of the control module (130), and depending on the implementation, the policy management module (110) and the QR management module (120) described above can be integrated into a single module.

[0074] The control module (130) can retrieve necessary policies and QR metadata from the policy management module (110) and the QR management module (120), and interact with the connection execution module (140) to direct and apply the issuance, activation, replacement, sending restriction, and release of virtual contacts.

[0075] Hereinafter, with reference to FIGS. 4 and 5, the operation based on the interaction between the control module (130) and the connection execution module (140) according to one embodiment of the present invention will be described in detail. FIG. 4 is a diagram illustrating, exemplarily, the outgoing processing and virtual contact issuance, activation, or replacement procedure performed by the control module (130), and FIG. 5 is a diagram illustrating, exemplarily, the outgoing restriction and restriction release sequence performed by the control module (130) according to another embodiment of the present invention. In the following, the step notation (S) is for the purpose of facilitating understanding, and the actual execution may be performed in parallel or asynchronously depending on the implementation.

[0076] Referring to FIG. 4, the control module (130) can receive a connection request generated by recognizing a QR code that identifies a recipient profile from a sender terminal (10) (S410), and can determine the contact to be connected according to the time of the connection request time or day of the week by referring to the timetable of the routing policy obtained from the policy management module (110).

[0077] The control module (130) may request the connection execution module (140) to issue a first virtual contact for the determined connection target contact (S420), and the connection execution module (140) may return the first virtual contact in response to the issuance request (S430).

[0078] Here, the virtual contact issuance request is a procedure for creating a new virtual contact and assigning it to a specific connection target contact, and if an initial virtual contact corresponding to each connection target contact is assigned in advance, the connection execution module (140) can activate the first virtual contact assigned in advance in response to the issuance request.

[0079] Additionally, the control module (130) can update the call screen data to include display information (e.g., a button or a link, etc.) associated with the first virtual contact (S440).

[0080] Here, the control module (130) can obtain a QR type corresponding to the recipient profile, a call screen template, group display information, etc. from the QR management module (120) and apply them when generating call screen data.

[0081] In one embodiment, when a connection request is received, the control module (130) may provide a call screen that includes display information associated with the first virtual contact. The caller may select a button corresponding to the first virtual contact through the call screen (S460) and request to make a call to the first virtual contact (S470). Accordingly, the connection execution module (140) may execute a connection with the recipient using the first virtual contact.

[0082] In another embodiment, the control module (130) can obtain a virtual contact replacement policy from the policy management module (110) and determine whether the virtual contact replacement policy is satisfied according to the virtual contact replacement policy (S450).

[0083] For example, if the number of connection executions for the first virtual contact is greater than a predetermined number (N), a request to replace the virtual contact with a new virtual contact may be sent when a preset period (e.g., N minutes, N hours) or validity period (e.g., 24 hours) has elapsed. Alternatively, a request to replace the virtual contact with a new virtual contact may be sent at the time of timetable slot change according to the routing policy.

[0084] When the control module (130) receives a second virtual contact in response to the replacement request from the connection execution module (140), it can control the call screen data to be automatically reflected (S440).

[0085] For example, when the control module (130) receives a connection request from the caller terminal (10) (S410), it may provide a call screen that includes display information associated with a second virtual contact. The caller may select a button corresponding to the second virtual contact through the call screen (S460) and request to make a call to the second virtual contact (S470). Accordingly, the connection execution module (140) may execute a connection with the recipient using the second virtual contact.

[0086] Meanwhile, if the connection execution module (140) issues a replacement with a second virtual contact in response to a replacement request from the control module (130), the previous virtual contact may be processed to be inactive or expired.

[0087] Hereinafter, with reference to FIG. 5, an exemplary procedure for restricting and releasing transmission performed by a control module (130) according to another embodiment of the present invention will be described.

[0088] The control module (130) can obtain a call restriction policy and a release policy from the policy management module (110), and if it is determined that a call restriction for the first virtual contact is necessary according to the call restriction policy, it can request the connection execution module (140) to restrict calls for the first virtual contact.

[0089] Referring to FIG. 5, when a caller selects a button corresponding to a virtual contact through a call screen (S510), a call may be requested to be made to the virtual contact (S520), and the connection execution module (140) may execute a connection to the recipient's contact target contact linked to the virtual contact (S530).

[0090] The connection execution module (140) can return communication record data (CDR) regarding the connection execution result to the control module (130) (S540), and can distinguish and return the communication record data regarding the connection execution result according to the channel type.

[0091] The control module (130) can determine whether the outgoing restriction policy is satisfied based on the communication record data (S550).

[0092] Here, the communication record data may include at least one of the connection request start and end times, result status, duration, reason code, caller identifier, and virtual contact ID.

[0093] For example, the control module (130) can determine whether to apply the policy by counting the number of connection attempts that occurred within a time frame set based on the time of the connection request.

[0094] Specifically, the control module (130) can update a connection attempt counter using communication record data and determine whether the outgoing restriction policy is satisfied based on the counter.

[0095] The control module (130) may set a call restriction if it determines that the call restriction policy is satisfied as a result of the determination (S555), and the connection execution module (140) may block the attempt to connect to the virtual contact when a call is requested to the virtual contact for which the call restriction has been set (S560) (S565). At this time, a message indicating that the recipient cannot be connected may be further displayed on the caller terminal (10).

[0096] In another embodiment, the control module (130) can determine whether the call restriction release policy is satisfied after setting a call restriction for a virtual contact (S570) and can request the call restriction release setting for the virtual contact (S575).

[0097] For example, if the control module (130) determines that a predetermined amount of time has elapsed since the call restriction setting, it may request the release of the call restriction setting for the virtual contact.

[0098] For example, when a request is made to make a call to a virtual contact with the call restriction lifted (S580), the connection execution module (140) may allow a connection to a recipient using the virtual contact (S585).

[0099] Accordingly, according to the present specification, immediate connection to various channels such as phone, messenger, and email can be achieved simply by scanning a QR code, thereby ensuring constant online connectivity. Additionally, the target contact is automatically switched based on the time of the connection request, reducing false calls made while the user is unavailable, and flexible responses are possible by reflecting shift changes and days off. Furthermore, call screen data is automatically generated and updated according to the QR code type, which not only enhances the user experience but also reduces the risk of number crawling, reuse, and session hijacking by replacing virtual contacts based on factors such as usage frequency according to a virtual contact replacement policy.

[0100] Hereinafter, a QR code-based virtual contact method is described with reference to FIGS. 6 to 8. For convenience of explanation, an example is provided in which a QR code for store / facility inquiries is provided.

[0101] FIG. 6 is a flowchart illustrating a QR code-based virtual contact method according to an embodiment of the present invention.

[0102] Referring to FIG. 6, a QR code-based virtual contact method according to an embodiment of the present invention comprises the steps of: receiving a connection request by recognizing a QR code (S610); obtaining one or more of a routing policy, a virtual contact replacement policy, a call restriction policy, or a call restriction release policy regarding a recipient profile corresponding to the connection request (S620); determining a connection target contact corresponding to a time zone or day of the week at the time of the connection request based on the routing policy (S630); requesting the issuance or activation of a first virtual contact for the connection target contact and receiving the first virtual contact (S640); generating and providing call screen data including display information associated with the first virtual contact (S650); determining whether to replace the first virtual contact assigned to the connection target contact according to the virtual contact replacement policy, and if it is determined that the virtual contact replacement policy is satisfied, transmitting a virtual contact replacement request (S660); receiving a second virtual contact in response to the virtual contact replacement request and reflecting the second virtual contact in the call screen data (S670), etc. It may include. Below, the operations performed at each step will be described in detail, focusing on examples.

[0103] A virtual contact system (100) can receive a connection request from a sender by recognizing a QR code, and the connection request may include at least a QR identifier, a time of the request, and day of the week information (S610).

[0104] For example, when a customer scans a QR code attached to the entrance of a store, the virtual contact system (100) can obtain the QR identifier mapped to the store account and the time of the scan to initiate a session.

[0105] Additionally, the virtual contact system (100) may obtain one or more of a routing policy, a virtual contact replacement policy, a call restriction policy, or a call restriction release policy regarding a recipient profile corresponding to a connection request (S620).

[0106] That is, the virtual contact system (100) can obtain policies regarding recipient profiles from the policy management module (110).

[0107] For example, the store profile may have a timetable with contacts mapped to be connected by time slot, such as 10-12:00: morning person in charge, 12:00-18:00: afternoon person in charge, 18:00-23:00: owner, and a virtual contact replacement policy such as "replace virtual number after 24 hours or N uses."

[0108] The virtual contact system (100) can determine a contact to be connected that corresponds to the time of day or day of the week at the time of the connection request based on a routing policy (S630).

[0109] For example, if a connection request is received from a caller at 14:30, the actual contact of the "afternoon person in charge" may be selected as the contact to be contacted. If "afternoon person in charge A" for Monday, Wednesday, and Friday and "afternoon person in charge B" for Tuesday, Thursday, and Saturday are additionally set as part of the day-of-the-week policy, the contact to be contacted may be selected by further considering the day of the week at which the connection request is received.

[0110] In addition, for example, when there is no response, it is possible to reroute to a secondary contact in the same slot or apply channel priority for the corresponding time period to reduce false calls during absences, and enable flexible response by reflecting shift changes, days off, etc.

[0111] Additionally, the virtual contact system (100) may request the issuance or activation of the first virtual contact for the contact to be connected determined in step S630, and receive the first virtual contact (S640).

[0112] Here, virtual contacts can be implemented using proxy numbers, messaging tokens, email aliases, session links, etc.

[0113] For example, if a "phone" channel is associated with the determined target contact, a proxy number in the form "050-XXXX" may be issued and returned. Alternatively, if an initial virtual contact has been pre-assigned as described above, only the activation of that virtual contact may be performed.

[0114] The virtual contact system (100) can generate and provide call screen data including display information linked to the first virtual contact (S650).

[0115] The above display information may include a button or link associated with the first virtual contact, a recipient setting message, group display information, etc.

[0116] For example, FIG. 7 is a diagram showing the configuration of a user interface (UI) of a call screen according to an embodiment of the present invention. Referring to FIG. 7, on the call screen displayed on the caller terminal (10), a store logo or store name (61) may be displayed at the top, and a guidance message set by the recipient, "Please contact us if you have any inquiries" (62), may be placed. Additionally, virtual contacts for each channel may be mapped to buttons corresponding to telephone (63a) / messenger (63b) / email (63c). Furthermore, information (64) indicating the current time (14:30) at the time the connection request was received and the person in charge (afternoon person in charge A) according to the routing policy may be further provided.

[0117] Additionally, the virtual contact system (100) determines whether to replace the first virtual contact assigned to the contact to be connected according to the virtual contact replacement policy, and if it is determined that the virtual contact replacement policy is satisfied, it may request a virtual contact replacement (S660).

[0118] That is, the virtual contact system (100) can transmit a replacement request when one or more of the following are satisfied: the number of connection executions exceeds a predetermined number (N), the period or validity period, or the timetable slot change point.

[0119] For example, the virtual contact system (100) may request the replacement of a virtual contact at a predetermined number of times (N) or at a preset period or expiration date (e.g., 24 hours) according to the virtual contact replacement policy stored in the recipient profile account.

[0120] Additionally, the virtual contact system (100) receives a second virtual contact in response to a request to replace the virtual contact, and can automatically reflect the second virtual contact in the call screen data (S670).

[0121] For example, if a connection attempt is made more than a predetermined number of times (N) to a first virtual contact linked to afternoon person A, a new second virtual contact may be assigned, and the virtual contact system (100) may immediately reflect this in the call screen data to provide an updated call screen upon the next connection request, and the existing first virtual contact may be processed as expired.

[0122] Additionally, the virtual contact system (100) may acquire at least one of a QR code type, a call screen template, and group display information regarding the recipient profile separately from step S620, and may refer to the call screen template, group display information, etc. when creating the call screen in step S650.

[0123] For example, the virtual contact system (100) may further obtain at least one of a QR code type, a call screen template, and group display information regarding a recipient profile from the QR management module (120).

[0124] For example, in the case of a QR code mapped to a store account, the store logo or store name can be controlled to be forcibly displayed on the call screen.

[0125] As another example, in the case of a QR code mapped to an apartment group code, the group display information (e.g., apartment name, logo, forced display flag) described above can be obtained from the QR management module (120), and the user interface can be configured so that the group display information is forcibly displayed when the call screen is created.

[0126] Accordingly, according to the QR code-based virtual contact method of an embodiment of the present invention, immediate connection to various channels such as telephone, messenger, and email can be achieved simply by scanning a QR code, thereby ensuring constant online connectivity. Additionally, the contact to be connected is automatically switched according to the time of the connection request, reducing false calls while the user is unavailable, and flexible responses are possible by reflecting shift changes and days off. Furthermore, call screen data is automatically generated and updated according to the QR type, which not only enhances the user experience but also reduces the risk of number crawling, reuse, and session hijacking by replacing virtual contacts based on factors such as the number of times they have been used, in accordance with a virtual contact replacement policy.

[0127] FIG. 8 is a flowchart illustrating a QR code-based virtual contact method according to another embodiment of the present invention.

[0128] Referring to FIG. 8, a QR code-based virtual contact method according to another embodiment of the present invention may include the steps of receiving communication record data (S810), updating a connection attempt counter within a time frame (S820), determining whether the counter exceeds a threshold value (S830), setting a sending restriction state (S840), determining whether a condition for releasing the sending restriction is satisfied (S850), and releasing the sending restriction and resetting the counter (S860).

[0129] The virtual contact system (100) can receive communication record data from the connection execution module (140) (S810).

[0130] The above communication record data may include at least one of the connection request start / end time, result status, duration, reason code, caller identifier, and virtual contact ID.

[0131] For example, if a customer selects the "Call" button on the store QR and makes a call to the first virtual contact, the connection execution module (140) may generate and return communication record data such as "Start=14:02:11, End=14:02:47, Result=Success, Duration=36 seconds, Caller ID=010-****-1234, Virtual ID=050-1234".

[0132] The virtual contact system (100) can update the connection attempt counter within the time frame (T) (S820).

[0133] Specifically, the virtual contact system (100) can update a connection attempt counter based on the same caller identifier for a time frame (T).

[0134] For example, if the store policy is a T=15 minute sliding window, calls with the same caller ID within the last 15 minutes can be counted. Additionally, for example, it can be configured to store counters by channel separately, and the counters can be recorded separately in the storage within the aforementioned control module (130).

[0135] Additionally, the virtual contact system (100) can determine whether the counter exceeds a threshold value (N) (S830).

[0136] For example, if the policy is T=15 minutes and N=5, it can be determined to be exceeded if there are 6 attempts from the same caller ID during the 14:00–14:15 interval. As an example, considering the congestion during lunchtime, stores may set different thresholds, such as N=5 for phone channels and N=10 for messenger channels. As another example, for group codes, security can be enhanced by applying a lower threshold during nighttime hours.

[0137] At this time, the virtual contact system (100) may determine that outgoing restrictions for the first virtual contact are required if the counter exceeds a threshold value (N). Alternatively, the virtual contact system (100) may terminate the step if the counter does not exceed a threshold value (N).

[0138] Alternatively, if the virtual contact system (100) determines at step S830 that outgoing restriction is necessary, it can set an outgoing restriction state (S840).

[0139] Specifically, the virtual contact system (100) can set a call restriction status for the first virtual contact and calculate the type of restriction and the scheduled time for release.

[0140] For example, if a call restriction is instructed for the first virtual contact, the caller may be displayed a notification message on the call screen such as "Connection has been temporarily restricted," or an alternative notification message such as "Please try again in 1 hour or use a messenger."

[0141] Additionally, the virtual contact system (100) can determine whether the conditions for lifting the call restriction for the first virtual contact restricted from calling are met at step S840 (S850).

[0142] For example, the system (100) can be configured so that the outgoing release is automatically released when the set time + t is satisfied, and can be configured so that manual release is possible.

[0143] Additionally, the virtual contact system (100) can unlock the outgoing call restriction and reset the counter (S860).

[0144] For example, if the outgoing restriction is automatically lifted after 1 hour, the control module (130) can instruct the connection execution module (140) to lift the outgoing restriction and reset the counter to 0.

[0145] Alternatively, for example, number reuse can be prevented by replacing the virtual contact at the time the outgoing restriction is lifted, and the call screen can automatically reflect the changed state.

[0146] Accordingly, according to a QR code-based virtual contact method of one embodiment of the present invention, by restricting outgoing calls based on the number of connection attempts to a specific sender's virtual contact and releasing the outgoing restriction after a certain period of time, security and convenience of use can be improved simultaneously.

[0147] FIG. 9 is a block diagram showing a QR code-based virtual contact device (101) according to an embodiment of the present invention. Referring to FIG. 9, the QR code-based virtual contact device (101) can be implemented as a computing device, and one or more of the modules constituting the computing device can be implemented on a general-purpose computing processor.

[0148] Such a QR code-based virtual contact device (101) may include a processor (108), an input / output I / O (102), a memory (104), an interface (106), and a bus (111). The processor (108), the input / output device (102), the memory (104), and / or the interface (106) may be connected to each other via the bus (111). The bus (111) corresponds to a path through which data travels.

[0149] Specifically, the processor (108) may include at least one of a CPU (Central Processing Unit), MPU (Micro Processor Unit), MCU (Micro Controller Unit), GPU (Graphic Processing Unit), microprocessor, digital signal processor, microcontroller, application processor (AP), and logic elements capable of performing similar functions.

[0150] The input / output device (102) may include at least one of a keypad, a keyboard, a touchscreen, and a display device. The memory device (104) may store data and / or programs, etc.

[0151] The interface (106) can perform the function of transmitting data to a communication network or receiving data from a communication network. The interface (106) may be wired or wireless. For example, the interface (106) may include an antenna or a wired / wireless transceiver, etc. The memory (104) is a volatile operational memory for protecting personal information, which enhances the operation of the processor (108), and may further include high-speed DRAM and / or SRAM, etc.

[0152] Additionally, the memory (104) stores programming and data configurations that provide the functions of some or all of the modules described herein. For example, it may include logic that enables the execution of selected embodiments of the QR code-based virtual contact method described above.

[0153] A program or application is loaded as a set of instructions including each step of performing the above-described QR code-based virtual contact method stored in memory (104), and the processor (108) is enabled to perform each step.

[0154] Furthermore, the various embodiments described herein may be implemented, for example, in a recording medium readable by a computer or similar device using software, hardware, or a combination thereof.

[0155] According to hardware implementation, the embodiments described herein may be implemented using at least one of ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, and other electrical units for performing functions. In some cases, the embodiments described herein may be implemented as the control module itself.

[0156] According to software implementation, embodiments such as the procedures and functions described herein may be implemented in separate software modules. Each of the software modules may perform one or more functions and operations described herein. Software code may be implemented as a software application written in a suitable programming language. The software code may be stored in a memory module and executed by a control module.

[0157] The above description is merely an illustrative explanation of the technical concept of the present invention, and those skilled in the art to which the present invention pertains will be able to make various modifications, changes, and substitutions within the scope of the essential characteristics of the present invention without departing from its nature.

[0158] Accordingly, the embodiments disclosed in this invention and the accompanying drawings are intended to illustrate, not limit, the technical concept of the invention, and the scope of the technical concept of the invention is not limited by such embodiments and accompanying drawings. The scope of protection of this invention shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of this invention.

Claims

Claim 1 A QR code-based virtual contact system that provides a virtual connection with a recipient through QR code scanning, comprising: a policy management module that stores a routing policy, a virtual contact replacement policy, an outgoing restriction policy, and an outgoing restriction release policy linked to a recipient profile; a control module that determines a contact to be connected according to a time zone or day of the week based on the routing policy and requests the issuance of a first virtual contact for the contact to be connected; and a connection execution module that issues the first virtual contact in response to the issuance request, executes a connection using the first virtual contact, and transmits to the control module communication record data including the start and end times of the connection request, result status, duration, reason code, caller identifier, and virtual contact ID regarding the result of the connection execution, distinguishing the data according to the channel type, which is any one of the connection types among telephone, messenger, email, or chat executed using the first virtual contact.The control module includes, when a first virtual contact corresponding to the connection target contact is received from the connection execution module, generates call screen data including display information associated with the first virtual contact; when it is determined that replacement of the first virtual contact is necessary based on the virtual contact replacement policy, transmits a virtual contact replacement request to the connection execution module; when a second virtual contact is received from the connection execution module in response to the replacement request, updates and applies the second virtual contact to the call screen data; when a connection using the first virtual contact is executed through the display information included in the call screen data, receives communication record data regarding the connection execution result from the connection execution module; using the communication record data, updates a connection attempt counter using the caller identifier and the virtual contact ID of the first virtual contact within a set time frame; determines whether the counter exceeds a threshold value (N) applied differently according to the channel type or the combination of a group code identifying a group linked to the recipient profile and a time zone according to the call restriction policy; and when the counter exceeds the applied threshold value, to the connection execution module A QR code-based virtual contact system characterized by requesting the setting of a call restriction status for the first virtual contact, and, if the call restriction release policy is satisfied, resetting the counter and requesting the release of the call restriction status for the first virtual contact. Claim 2 A QR code-based virtual contact system according to claim 1, wherein the routing policy includes a time table in which a connection target contact corresponding to each different recipient terminal is mapped according to time zone or day of the week, and the control module selects a connection target contact mapped to a slot corresponding to the time zone or day of the week by referring to the time table. Claim 3 A QR code-based virtual contact system according to claim 1, wherein the display information is provided in the form of a button or link mapped to the virtual contact, and the control module automatically updates the display information according to a time zone, day of the week, or preset cycle. Claim 4 A QR code-based virtual contact system according to claim 1, wherein the control module is configured to pre-assign an initial virtual contact corresponding to each connection target contact, and requests an update of the initial virtual contact according to the virtual contact replacement policy. Claim 5 In claim 1, the virtual contact is a QR code-based virtual contact system comprising one or more of a phone number, an email address, a messenger ID, or a tokenized session link. Claim 6 A QR code-based virtual contact system according to claim 1, further comprising a QR management module configured to map and store one or more QR code identifiers to the recipient profile and to map and store at least one of a QR type, a call screen template, and organization display information to each QR code. Claim 7 A QR code-based virtual contact system according to claim 6, wherein the QR management module stores organization display information including organization identification information, organization name, or organization logo, and the control module controls the call screen data to forcibly display the organization identification information, organization name, or organization logo. Claim 8 A QR code-based virtual contact system according to claim 1, wherein the virtual contact replacement policy is configured to replace the virtual contact when the number of connection executions for the first virtual contact is greater than or equal to a predetermined number (N) or at preset intervals. Claim 9 delete Claim 10 delete Claim 11 A QR code-based virtual contact method that provides a virtual connection with a recipient through a QR code performed in a QR code-based virtual contact system, comprising: a step of obtaining one or more of a routing policy, a virtual contact replacement policy, a call restriction policy, or a call restriction release policy regarding a recipient profile; a step of determining a contact to be connected corresponding to a time zone or day of the week based on the routing policy; a step of requesting the issuance or activation of a first virtual contact for the contact to be connected, executing a connection using the first virtual contact, and receiving the first virtual contact corresponding to the contact to be connected, and communication record data distinguished according to a channel type which is a connection type among telephone, messenger, email, or chat executed using the first virtual contact, including the start and end times of the connection request, result status, duration, reason code, caller identifier, and virtual contact ID regarding the result of the connection execution; and a step of generating and providing call screen data including display information associated with the first virtual contact. A step of determining whether the first virtual contact assigned to the connection target contact needs to be replaced according to the virtual contact replacement policy, and if it is determined that the virtual contact replacement policy is satisfied, transmitting a virtual contact replacement request; a step of receiving a second virtual contact in response to the virtual contact replacement request and automatically reflecting the second virtual contact in the call screen data; a step of receiving communication record data regarding the connection execution result when a connection using the first virtual contact is executed through the display information included in the call screen data; and a step of updating a connection attempt counter using the caller identifier and the virtual contact ID of the first virtual contact within a set time frame using the communication record data.A QR code-based virtual contact method comprising: a step of determining whether the counter exceeds a threshold value (N) applied differently by channel type, which is a connection type among phone, messenger, email, or chat executed using the first virtual contact according to the outgoing restriction policy, or by a combination of a group code and a time zone that identifies a group linked to the recipient profile; a step of requesting the setting of an outgoing restriction state for the first virtual contact if the counter exceeds the applied threshold value; and a step of resetting the counter and requesting the release of the outgoing restriction state for the first virtual contact if the outgoing restriction release policy is satisfied. Claim 12 A QR code-based virtual contact method according to claim 11, wherein the routing policy includes a time table in which a connection target contact corresponding to each different recipient terminal is mapped according to time zone or day of the week, and the step of determining the connection target contact is characterized by selecting a connection target contact mapped to a slot corresponding to the time zone or day of the week by referring to the time table. Claim 13 A QR code-based virtual contact method according to claim 11, wherein the display information is provided in the form of a button or link to which the virtual contact is mapped, and the display information is automatically updated according to the time zone, day of the week, or preset cycle. Claim 14 A QR code-based virtual contact method according to claim 11, characterized in that if an initial virtual contact corresponding to the contact to be connected is pre-assigned, the initial virtual contact is activated, and the update of the initial virtual contact is requested according to the virtual contact replacement policy. Claim 15 A QR code-based virtual contact method according to claim 11, wherein the virtual contact comprises one or more of a phone number, an email address, a messenger ID, or a tokenized session link. Claim 16 A QR code-based virtual contact method according to claim 11, further comprising the step of mapping and storing one or more QR code identifiers to the recipient profile, and mapping and storing at least one of a QR code type, a call screen template, and organization display information for each QR code. Claim 17 A QR code-based virtual contact method according to claim 16, wherein the organization display information includes organization identification information, an organization name, or an organization logo, and the organization display information is forcibly displayed in the call screen data. Claim 18 A QR code-based virtual contact method according to claim 11, wherein the virtual contact replacement policy is configured to replace the virtual contact when the number of connection executions for the first virtual contact is greater than or equal to a predetermined number (N), or at preset intervals. Claim 19 delete Claim 20 delete

Images