Method and apparatus for generating deeplink associated with service

Abstract

An embodiment of the present invention provides a method for generating a deep link associated with a service using an electronic device, comprising the following steps: providing a first page to a first user terminal for requesting the generation of a deep link; obtaining information of the first deep link by user input corresponding to the first page; storing the information of the first deep link in a database; generating code associated with the first deep link based on the information of the first deep link stored in the database; and publishing the first deep link to an application associated with the service based on the code.

Description

Technical Field

[0001] Embodiments of the present invention relate to a method and apparatus for generating deep links associated with services. Prior Technology

[0002] With the widespread use of the internet, the e-commerce market is expanding. The proportion of people purchasing goods by visiting physical stores is gradually decreasing, while the proportion purchasing goods via e-commerce using computers or smartphones is rapidly increasing. Furthermore, the number of users ordering and having food delivered through food delivery intermediaries using their smartphones without physically visiting restaurants is also increasing.

[0003] E-commerce service providers offer e-commerce service applications (apps) to users' devices, providing information related to the e-commerce service through various pages within the application. On the other hand, even when users are not using the e-commerce service application, if a user clicks on a link (such as an advertisement or URL) on a website or other application outside the application, the service provider may expect the application to run on the user's device to redirect the user to a specific page within the application. Deep links are used for this purpose.

[0004] Deep linking is a technology that, when a user in a mobile environment clicks a URL on a website or other application, executes the application on the user's device and guides the user to a specific page. Deep linking performs the following functions: after entering a specific address or value, it executes the application or moves the user to a specific page within the application. Users only need to click a link to immediately access the content within the application, thereby optimizing the user experience and improving conversion rates and retention rates.

[0005] The typical form of deep links is to register URI scheme values ​​within an application. However, this initial form leads to the problem of duplicate application scheme values ​​as the number of applications increases. To address this issue, a new form of deep linking is used, which uses the inherent domain address of the webpage as the execution value of the deep link. Examples of this are Universal Links on iOS and App Links on Android.

[0006] On the other hand, service providers may typically need the following for developing, operating, and testing deep links.

[0007] - Code (Development): Code for registering / processing deep links (written independently for each operating system (e.g., iOS, Android))

[0008] - Files (Operations): Files used to record / share deeply linked directories / specifications (collected jointly by the operating system).

[0009] - Testing: Methods / tools used to test deep links

[0010] However, existing systems associated with service providers suffer from the following problems: the development, operation, and testing of deep links are written and managed independently by individual groups within the service provider, which reduces operational efficiency and leads to inconsistencies between these groups. Therefore, to address these issues of inefficiency and inconsistency related to deep links, a system is needed that can integrate and manage the development, operation, and testing of deep links.

[0011] Previous literature related to this invention includes Korean Patent No. 10-1756738. Summary of the Invention

[0012] [The problem the invention aims to solve]

[0013] The embodiments of the present invention are proposed to solve the above-mentioned problems, and their purpose is to provide an electronic device that can integrate and manage the development, operation and testing of deep links as an electronic device for generating deep links associated with services.

[0014] The technical issues to be addressed by this invention are not limited to those mentioned above. Those with common knowledge in the technical field of this invention can clearly understand other technical issues not mentioned based on the following description. [Technical means to solve the problem]

[0015] To achieve the aforementioned objectives, a method for generating deep links associated with a service using an electronic device according to one embodiment of the present invention is characterized by comprising the following steps: providing a first page to a first user terminal for requesting the generation of deep links; obtaining information of the first deep link through user input corresponding to the first page; storing the information of the first deep link in a database; generating code associated with the first deep link based on the information of the first deep link stored in the database; and publishing the first deep link to an application associated with the service based on the code.

[0016] According to one embodiment, the method for generating deep links associated with services by the above-described electronic device is characterized in that the step of generating code associated with the first deep link includes the following steps: confirming information of a plurality of deep links including the first deep link from a database; providing a second page including a list of the plurality of deep links to a second user terminal; and generating code associated with the first deep link based on user input corresponding to the second page.

[0017] According to one embodiment, the method for generating deep links associated with services by the above-mentioned electronic device is characterized in that the information of the first deep link includes information of at least one of the deep link version, the compatible operating system (OS), and the compatible application version.

[0018] According to one embodiment, the method for generating deep links associated with services by the above-mentioned electronic device is characterized in that the information of the first deep link includes the page type associated with the first deep link.

[0019] According to one embodiment, the method for generating deep links associated with services by the above-mentioned electronic device is characterized in that the information of the first deep link includes information of the OS compatible with the first deep link, and the step of generating code associated with the first deep link further includes the following steps: generating a link file corresponding to the OS compatible with the first deep link, the link file being uploaded to the network server for the purpose of executing the first deep link.

[0020] According to one embodiment, the method for generating deep links associated with services by the above-mentioned electronic device is characterized in that the step of publishing the first deep link further includes the following steps: before publishing the first deep link, searching in a database for code associated with the first deep link; if code associated with the first deep link is found in the database, publishing the first deep link; and if code associated with the first deep link is not found in the database, providing a notification to a second user terminal used to manage deep links.

[0021] According to one embodiment, the method for generating deep links associated with services by the above-mentioned electronic device is characterized in that the information of the first deep link includes an application version compatible with the first deep link, and the step of publishing the first deep link further includes the following steps: after publishing the first deep link, confirming the application version of the published first deep link; and updating the application version compatible with the first deep link stored in the database to the application version.

[0022] According to one embodiment, a method for generating deep links associated with a service by an electronic device is characterized by further including the following steps: confirming information about a second deep link that is no longer in use by user input corresponding to a first page; scanning the code of deep links published in the application to confirm whether code associated with the second deep link has been published; if code associated with the second deep link has been published, generating a deletion request for the code associated with the second deep link; and providing the deletion request to a second user terminal used to manage deep links.

[0023] According to one embodiment, the method for generating deep links associated with services by the above-mentioned electronic device is characterized in that the first page includes a list of a plurality of deep links stored in a database, and the step of publishing the first deep link further includes the following steps: updating the status information of the first deep link and the application version information of the published first deep link in the list.

[0024] According to one embodiment, a method for generating deep links associated with a service by an electronic device is characterized in that it further includes the steps of: obtaining user input from a first user terminal corresponding to a first deep link included in a list; and in response to the user input corresponding to the first deep link, providing a test area for testing the first deep link to a first page.

[0025] According to one embodiment, a method for generating deep links associated with a service by an electronic device is characterized by further including the following steps: obtaining parameter values ​​associated with a first deep link from a first user terminal via user input corresponding to a test area; generating a test link for the first deep link based on the parameter values; displaying the test link in the test area; and providing a page corresponding to the test link to the first user terminal according to user input corresponding to the test link.

[0026] An electronic device for generating deep links associated with a service, according to one embodiment of the present invention, is characterized by comprising: a memory storing at least one command; and a processor; the processor being configured to: execute at least one command to provide a first page to a first user terminal for requesting the generation of a deep link; obtain information of the first deep link by user input corresponding to the first page; store the information of the first deep link in a database; generate code associated with the first deep link based on the information of the first deep link stored in the database; and publish the first deep link to an application associated with the service based on the code.

[0027] An embodiment of the present invention provides a non-transitory computer-readable storage medium storing a program for executing a method for generating deep links associated with a service on a computer. The method includes the steps of: providing a first page to a first user terminal for requesting the generation of deep links; obtaining information about the first deep link by user input corresponding to the first page; storing the information about the first deep link in a database; generating code associated with the first deep link based on the information about the first deep link stored in the database; and publishing the first deep link to an application associated with the service based on the code. [Effects of the Invention]

[0028] According to embodiments of the present invention, an electronic device can obtain information about deep links that a first user wishes to generate through a first page, store and manage the deep link information in a single database, generate code associated with the deep links based on the deep link information stored in the database, and publish it to a service application, thereby simplifying the process for generating deep links and integrating and managing the multiple deep links generated. Furthermore, the first user can effectively define the specifications of deep links and prevent duplicate deep link generation by using the list of multiple deep links stored in the database displayed on the first page.

[0029] The effects that can be obtained by the present invention are not limited to those mentioned above. Those who are skilled in the art to which the present invention pertains can clearly understand other effects not mentioned based on the following description. Simple Explanation of the Diagram

[0030] Figure 1 is a schematic diagram illustrating the configuration of a system for generating deep links associated with services according to one embodiment of the present invention. Figure 2 is a flowchart illustrating a method for generating deep links associated with services using an electronic device according to one embodiment of the present invention. Figure 3 is a schematic diagram illustrating the structure and function of a deep link management system according to one embodiment of the present invention. Figures 4a to 4d illustrate exemplary pages associated with a deep link management service according to one embodiment of the present invention. Figures 5a and 5b illustrate exemplary pages associated with a deep link code generator according to one embodiment of the present invention. Figures 6a to 6d illustrate the deep link testing process according to one embodiment of the present invention. Figure 7 is a schematic diagram illustrating the various configurations of an electronic device according to one embodiment of the present invention. Implementation

[0031] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0032] In describing the embodiments, descriptions of technical content well-known in the technical field to which this invention pertains and not directly related to this invention are omitted. This is because omitting redundant descriptions clearly conveys the essence of the invention, thus avoiding confusion regarding its main points.

[0033] For the same reasons, some components are exaggerated, omitted, or represented in a generalized manner in the accompanying drawings. Furthermore, the dimensions of each component do not perfectly reflect their actual dimensions. In each drawing, the same or corresponding components are assigned the same reference number.

[0034] The advantages and features of the present invention, as well as the methods of achieving them, will become clear when referring to the accompanying drawings and the embodiments described in detail below. However, the present invention is not limited to the embodiments disclosed below, but can be implemented in various different forms. These embodiments are provided only to fully disclose the invention and to fully inform those skilled in the art of the scope of the invention. The invention is defined only by the scope of the claims. Throughout this specification, the same reference numerals refer to the same constituent elements.

[0035] At this point, it should be understood that the blocks of the flowchart and the combination of the flowchart can be implemented by computer program instructions. These computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment. Therefore, the instructions executed by the processor of the computer or other programmable data processing equipment produce methods for implementing the functions described in the blocks of the flowchart. To implement the functions in a specific manner, these computer program instructions can be stored in computer-usable or computer-readable memory that is accessible to a computer or other programmable data processing equipment. Therefore, the instructions stored in such computer-usable or computer-readable memory can also produce articles of manufacture that include the instruction method of implementing the functions described in the blocks of the flowchart. The computer program instructions can also be loaded into a computer or other programmable data processing equipment. Therefore, a series of action steps are performed in the computer or other programmable data processing equipment to produce a flow executed by the computer. Thus, the instructions executed by the computer or other programmable data processing equipment can also provide steps for executing the functions described in the blocks of the flowchart.

[0036] Furthermore, each block can represent a module, segment, or portion of code comprising one or more executable instructions used to perform a specific logical function. It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may be executed out of order. For example, two blocks shown successively may actually be executed simultaneously, or sometimes in reverse order depending on their respective functions.

[0037] In this embodiment, the term "~component" refers to software or hardware components such as FPGAs or ASICs, where the "~component" plays a certain role. However, the term "~component" is not limited to software or hardware. A "~component" can be constructed in the form of addressable storage media or by reproducing one or more processors. Therefore, as an example, a "~component" includes components such as software components, object-oriented software components, class components, and task components, programs, functions, attributes, routines, subroutines, code fragments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided by the components and the "~component" can be combined with a smaller number of components and the "~component," or further separated into other components and the "~component." Furthermore, components and the "~component" can also be implemented by reproducing one or more CPUs within a device or secure multimedia card.

[0038] Figure 1 is a schematic diagram illustrating the configuration of a system for generating deep links associated with services according to one embodiment of the present invention.

[0039] Referring to FIG1, a system according to one embodiment of the present invention may include an electronic device 110, a first user terminal 120, and a second user terminal 130. FIG1 only shows the electronic device 110, the first user terminal 120, and the second user terminal 130, but is not limited thereto. The system may include only a portion of the components shown, or may include other components besides those shown.

[0040] In one embodiment, the electronic device 110 may be included in a service server providing e-commerce services or food delivery intermediary services. In one embodiment, the electronic device 110 may communicate with a user terminal and provide information related to the e-commerce or food delivery intermediary services. In one embodiment, the electronic device 110 may be included in a deep link management system within the service server, or may communicate with the deep link management system and control the overall procedures related to the development, operation, and testing of deep links. In one embodiment, the electronic device 110 may communicate with at least one of the first user terminal 120 and the second user terminal 130 and exchange information associated with deep links.

[0041] In one embodiment, the first user terminal 120 may include a terminal used by a first user (e.g., a marketing manager) who defines the specifications of deep links and delegates the generation of deep links, the first user being a user providing e-commerce or food delivery intermediary services. In one embodiment, the first user may use the first user terminal 120 to define the specifications of the deep links to be generated, request the generation of deep links from a second user, manage the generated deep links, and test them.

[0042] In one embodiment, the second user terminal 130 may include a terminal used by a second user (e.g., a development manager) who generates and manages the code for deep links based on deep link generation requests and publishes it to the application. This second user is a user providing e-commerce or food delivery intermediary services. In one embodiment, the second user may use the second user terminal 130 to confirm deep link generation requests, generate new deep links based on the requests and store them in a database, and publish the generated deep link code to the application associated with the actual service.

[0043] In one embodiment, either the first user terminal 120 or the third user terminal 130 may include a terminal of a user (or customer) utilizing the service. The user can use the user terminal to communicate with a service server including electronic device 110. An application providing e-commerce or food delivery intermediary services can be installed on the user terminal, and under the control of the application, it connects to electronic device 110 to utilize the e-commerce or food delivery intermediary services based on information exchange with electronic device 110. The first user terminal 120 or the third user terminal 130 may be a mobile device such as a smartphone or tablet computer, or a static device such as a desktop computer. Any machine capable of setting up and executing an e-commerce or food delivery intermediary service application can be used as the first user terminal 120 or the second user terminal 130 without limitation.

[0044] In one embodiment, electronic device 110 may implement a method for generating deep links associated with a service. Electronic device 110 may provide a first page to a first user terminal 120 for requesting the generation of deep links, obtain information about the first deep link through user input corresponding to the first page, store the information about the first deep link in a database, generate code associated with the first deep link based on the information about the first deep link stored in the database, and publish the first deep link to the application associated with the service based on the code. Hereinafter, the steps of the method for electronic device 110 to generate deep links associated with a service will be described in more detail with reference to FIG. 2.

[0045] Figure 2 is a flowchart illustrating a method for generating deep links associated with services using an electronic device according to one embodiment of the present invention. The entity implementing each step of the sequence diagram 200 shown in Figure 2 may include the electronic device 110 shown in Figure 1.

[0046] In step S210, the electronic device may provide a first page to the first user terminal for requesting the generation of deep links. The first user terminal may include the first user terminal 120 shown in FIG1. ​​The first page for requesting the generation of deep links may, for example, include page 400 of FIG4a. In one embodiment, the first page may be the page used by the first user to request the generation of deep links, and the first user may enter information about the deep link to be generated (e.g., version, name, platform, parameters) through the first page. In one embodiment, the first page may include a list of more than one deep link requested by other users in the past period, and the list may include deep links that have been generated and published, deep links that are waiting to be generated, and deprecated deep links.

[0047] In step S220, the electronic device can obtain information about the first deep link through user input corresponding to the first page. Information about the first deep link input by the first user through the first user terminal can be transmitted to the electronic device.

[0048] In one embodiment, the information of the first deep link may include information on at least one of the following: deep link version, compatible operating system, and compatible application version. The deep link version may be automatically entered as "Version 1" for the first deep link, and the corresponding version may be assigned based on the number of subsequent updates. The compatible operating system refers to the operating system in which the first deep link can function, and may include Android, iOS, etc. The compatible application version may include the version of the service application in which the first deep link functions, and may vary depending on the operating system. In one embodiment, the information of the first deep link may include at least one of the following: deep link version, whether it is compatible with various platforms, compatible application version, compatible operating system version, variable information (e.g., parameter type and whether it is supported), domain information (e.g., page type, ownership information), and information associated with internal application calls (e.g., whether it is a deep link that is activated only by an internal application call or a deep link that is activated by an external application call).

[0049] In one embodiment, the information for the first deep link may include the page type associated with the first deep link. The page type refers to the type of page used to provide information in a service application, and may include, for example, a single detail page (SDP), a search result page (SRP), a cart page, etc. The electronic device enables a first user to input the page type associated with the first deep link when requesting its creation, facilitating easy retrieval and filtering within a database.

[0050] In step S230, the electronic device may store the information of the first deep link in a database. In one embodiment, the database may include the shared deep link resource 310 of the deep link management system 300 shown in FIG3. The electronic device may store and manage requested deep links from various groups associated with the service provider in a database, thereby preventing problems such as duplicate deep links or error-generated deep links, and facilitating the management of deep links.

[0051] In step S240, the electronic device may generate code associated with the first deep link based on the information of the first deep link stored in the database. In one embodiment, the electronic device may write complete code for the first deep link or write skeleton code to implement the function of the first deep link based on the information of the first deep link stored in the database.

[0052] In one embodiment, the action of the electronic device generating code associated with the first deep link may include the following actions: confirming information from a database that includes a plurality of deep links containing the first deep link; providing a second page to a second user terminal that includes a list of the plurality of deep links; and generating code associated with the first deep link based on user input corresponding to the second page. In one embodiment, the second page used to generate the deep link may, for example, include page 500 as shown in FIG. 5a. In one embodiment, the second user terminal displaying the second page may include the second user terminal 130 as shown in FIG. 1. The second user can confirm the list of a plurality of deep links stored in the database through the second page, wherein after confirming the information of the first deep link requested by the first user, code associated with the first deep link is generated based on input corresponding to the second page.

[0053] In step S250, the electronic device can publish the first deep link to the application associated with the service based on the code. In one embodiment, the electronic device can generate code modules associated with the first deep link for each operating system and publish them to the service application corresponding to each operating system.

[0054] As described above, the electronic device can obtain information about the deep links that the first user wants to generate through the first page, store and manage the deep link information in a single database, generate code associated with the deep links based on the deep link information stored in the database, and publish it to the service application, thereby simplifying the process of generating deep links and integrating and managing the multiple deep links generated. Furthermore, the first user can effectively define the specifications of deep links and prevent duplicate deep link generation by using the list of multiple deep links stored in the database displayed on the first page.

[0055] Figure 3 is a schematic diagram illustrating the structure and function of a deep link management system according to one embodiment of the present invention.

[0056] Referring to FIG3, a deep link management system 300 is shown that allows a service provider to generate and manage a plurality of deep links. In one embodiment, the deep link management system 300 may include a shared deep link resource 310, a deep link management service 320, a deep link code generator 330, and a deep link code change sensor 340.

[0057] In one embodiment, the shared deep link resource 310 may serve as a unique database for storing deep links during development, operation, and testing. The shared deep link resource 310 may be shared by multiple groups associated with the service provider (e.g., marketing teams, search teams, billing teams, development teams, etc.), storing information about each of the plurality of deep links generated by requests from these groups. The deep link information may include the deep link's specifications, platforms supporting deep links, parameters associated with the deep link, and application versions compatible with the deep link.

[0058] In one embodiment, deep link management service 320 can provide a webpage (e.g., page 400 of FIG. 4a) for managing and testing deep links. Deep link management service 320 can provide a webpage capable of managing (adding or modifying) and testing the entire list and specifications of deep links. Deep link management service 320 can confirm information on a plurality of deep links from shared deep link resource 310, thereby displaying a list including the plurality of deep links on the webpage. Deep link management service 320 can update the information of deep links included in the deep link generation request received by the user to shared deep link resource 310 again.

[0059] In one embodiment, the deep link code generator 330 can provide a page for generating deep links (e.g., page 500 of FIG. 5a). The deep link code generator 330 can automatically generate and update code for registering deep links in various operating systems or platforms (iOS, Android). The deep link code generator 330 can verify information of a plurality of deep links from the shared deep link resource 310 and generate all or part of the code associated with the deep links (e.g., skeleton code). The code associated with the deep links may include, for example, iOS code modules and Android code modules, which can be created and published to iOS service applications and Android service applications, respectively.

[0060] In one embodiment, the information of the first deep link includes information about the operating system (OS) compatible with the first deep link. When generating code associated with the first deep link, the electronic device can generate a link file corresponding to the OS compatible with the first deep link, which is uploaded to the web server for the purpose of executing the first deep link. To support deep links in service applications, it is necessary to upload link files corresponding to each OS (e.g., the AASA (apple-app-site-association) file for iOS and the assetlinks.json file for Android) to the web server. However, the electronic device can automatically generate such link files and register them with the webpage.

[0061] In one embodiment, the deep link code change sensor 340 can scan the published deep link code to confirm whether there are any changes or problems related to deep links. In one embodiment, the deep link code change sensor 340 can automatically update the shared deep link resource 310 with changes to the platform application version or OS version information of the deep links. In one embodiment, the deep link code change sensor 340 can sense whether there are any unregistered or erroneous deep links stored in the shared deep link resource 310, and prevent errors by using pull requests (PRs) as a way to prevent code merging. In one embodiment, the deep link code change sensor 340 can scan only the code changes based on events related to the release of the application or webpage (e.g., git tag hook, Apple App Store Connect API, etc.), or it can periodically scan all code.

[0062] In one embodiment, the electronic device may search for code associated with the first deep link in a database before publishing the first deep link. If code associated with the first deep link is found in the database, the first deep link is published. If no code associated with the first deep link is found in the database, a notification is provided to the second user terminal used to manage the deep links. This can be understood as the function of the deep link code change sensor 340. After generating code associated with the deep link, the electronic device may store the code in a database and compare it with the code stored in the database before publishing the deep link to confirm whether there are any changes. For example, after the code associated with the deep link is generated by the electronic device, other users (e.g., developers) may insert erroneous code due to mistakes during arbitrary modification of the generated code. If a difference is found after comparing the code stored in the database with the code to be published, the electronic device provides a notification to the second user terminal to prevent the code from being published.

[0063] In one embodiment, the information of the first deep link may include application versions compatible with the first deep link. After the electronic device publishes the first deep link, it confirms the version of the application that has been published for the first deep link and updates the database with the application versions compatible with the first deep link. This can be understood as the function of the deep link code change sensor 340. The electronic device can automatically confirm the version of the application that has been published for the deep link and update it to the database, thereby keeping the information on compatible application versions of deep links stored in the database up-to-date.

[0064] In one embodiment, the electronic device can confirm information about unused second deep links through user input corresponding to the first page, scan the code of deep links published in the application to confirm whether code associated with the second deep link has been published, and generate a deletion request for the code associated with the second deep link when such code has been published, providing the deletion request to the second user terminal used to manage deep links. This can be understood as the function of the deep link code change sensor 340. In one embodiment, the first user can change the status of a published second deep link to a deprecated state through the first page (e.g., page 400 in FIG4a), and the electronic device can transmit a deletion request to the second user terminal to delete the code associated with the second deep link in the deprecated state from the application. In one embodiment, the electronic device can identify the application version that has been released with the code associated with the second deep link, automatically update the application version to the latest compatible application version, and display it on the first page.

[0065] Figures 4a to 4d illustrate exemplary pages associated with a deep link management service according to one embodiment of the present invention.

[0066] Referring to Figure 4a, a page 400 is shown for requesting the generation of deep links, and this page is associated with a deep link management service. In one embodiment, page 400 may be displayed on a first user terminal. Page 400 may include areas 410, 420, and 430. Area 410 may include an object for retrieving a specific deep link from the deep link list, and area 420 may include an object used by the first user to request the generation of a new deep link. Area 430 may include a plurality of deep link lists, which can be verified from the database of the shared deep link resource 310 as shown in Figure 3. The list in area 430 may include information such as the ID, service (e.g., e-commerce service, food delivery intermediary service, OTT service), name (e.g., page type), link, status, platform, application version, and update date of each deep link. The status of the list can include the status of deep links being applied to the application (APPLIED), the status of being ready to apply (READY TO APPLY), the status of being no longer used (DEPRECATED), the status of being incomplete (DRAFT), and the status of being unapplicable (INVALID).

[0067] Through page 400, the first user can identify multiple deep links currently stored in the database or applied to the application, and thus use some of the applied deep links as is, request an update to some of the applied deep links, or request the generation of new deep links not in the list. This allows the first user to efficiently utilize existing deep links and reduce the generation of duplicate deep links.

[0068] If the first user selects an object displayed in area 420 on page 400 of Figure 4a to request the creation of a new deep link, page 440 of Figure 4b can be provided. Page 440 can be displayed on page 400 as a new pop-up page as shown in Figure 4b, or it can be displayed in a new expanded area on page 400.

[0069] Referring to Figure 4b, page 440 may include an area 441 for a first user to input information about deep links, and an area 442 for inputting parameters associated with deep links. The first user can input information such as service, name, link, link description, version description, and owner in area 441 as the information for the deep link to be generated. The first user can input parameters associated with deep links in area 442. After inputting the deep link information and parameters, the first user can select an object in area 443.

[0070] Figure 4c illustrates the following: When the first user completes a deep link generation request by selecting an object in area 443 of page 440 in Figure 4b, the information of the newly requested deep link is added to area 430 of page 400 as shown in area 450. The information of the deep link requested via page 440 can be transmitted to the electronic device.

[0071] In one embodiment, the first page (e.g., page 400) may include a list of multiple deep links stored in a database. After publishing the first deep link, the electronic device updates the status information of the first deep link and the application version information of the published first deep link in the list. Figure 4d shows the changes in status, platform and application version, and update date after the requested deep link is generated, as shown in area 460. In one embodiment, if the generation and publication of the first deep link requested by the first user is completed through a second user terminal, the status information of the first deep link can be changed to the application completion status, and the version information of the first deep link is automatically updated to the application version of the published first deep link.

[0072] Figures 5a and 5b illustrate exemplary pages associated with a deep link code generator according to one embodiment of the present invention.

[0073] Referring to FIG5a, a page 500 for generating deep links is shown, which is associated with a deep link code generator. In one embodiment, page 500 may be displayed on a second user terminal. Page 500 may include regions 510 and 520. Region 510 may include a list of a plurality of deep links stored in a database. Region 520 may include information on the deep links selected by the second user from the list in region 510.

[0074] As shown in Figure 4b, the information of the first deep link generated by the first user's request is displayed in area 511 of page 500. If the second user selects the first deep link in area 511, the information of the first deep link can be displayed in area 520. The second user can enter at least one of the version, domain, and parameters of the first deep link in area 520, and then select an object in area 521 to generate code associated with the first deep link. In one embodiment, the code can be all the code capable of performing the function of the first deep link, or it can be the skeleton code corresponding to the first deep link. Figure 5b shows the skeleton code 530 corresponding to the first deep link.

[0075] Figures 6a to 6d illustrate the deep link testing process according to one embodiment of the present invention.

[0076] In one embodiment, the electronic device can obtain user input from the first user terminal corresponding to the first deep link included in the list of deep links, and in response to the user input corresponding to the first deep link, provide a test area for testing the first deep link to the first page.

[0077] Referring to Figure 6a, a page 600 is shown for requesting the generation of deep links, and this page 600 is associated with a deep link management service. In one embodiment, page 600 may be displayed on a first user terminal. The first user can select a first deep link 610 to test from the list of deep links on page 600.

[0078] Referring to Figure 6b, a test area 620 for testing the first deep link 610 is shown based on the selection input of the first user corresponding to the first deep link 610. Test area 620 may include sub-areas 621 and 622. Area 621 may include information about the selected first deep link 610 and information about one or more versions of the first deep link 610. Area 622 may display parameter information and parameter values ​​of the version selected for testing from one or more versions of the first deep link 610, resulting in test links and one or more example links corresponding to that deep link.

[0079] In one embodiment, example links can be displayed in ascending order of purchase conversion rate among published deep links of the same type as the corresponding deep links. Purchase conversion rate can refer to the percentage of users who actually make a purchase among those who enter the application page via the corresponding deep link. Users can easily confirm the results by directly clicking on example links with high purchase conversion rates, and can easily design deep links in a direction that improves marketing effectiveness.

[0080] In one embodiment, the electronic device can identify marketing metrics (e.g., purchase conversion rate) associated with each version of the deep link and display these metrics on page 600 (e.g., test area 620). For example, the electronic device can display the following information on test area 620: the purchase conversion rate for version 2 of the first deep link is 75%, and the purchase conversion rate for version 3 of the first deep link is 72%. The purchase conversion rate can refer to the percentage of users who actually make a purchase after entering the application page through the corresponding deep link. By displaying the information as described above, users can easily identify that the purchase conversion rate changes according to the updates of each version of the deep link, immediately confirm the functionality of each version of the deep link through test area 620, and ultimately improve marketing effectiveness through deep link design.

[0081] Referring to FIG6c, in one embodiment, the electronic device can obtain a parameter value 623 associated with the first deep link 610 from the first user terminal through user input corresponding to the test area 620, generate a test link 624 for the first deep link 610 based on the parameter value 623, display the test link 624 in the test area 620, and provide the first user terminal with a page corresponding to the test link (e.g., page 630 in FIG6d) ​​according to user input corresponding to the test link 624.

[0082] In the example shown in Figure 6c, the first user wants to test the first deep link 610 that connects to the search results page, which displays the results obtained by searching for the keyword "diapers" through e-commerce services. The first user can input "diapers" as the parameter (q) value for the first deep link 610 that connects to the keyword search results page. The electronic device can generate a test link 624 that connects to the search results page and display it in real time in the test area 620. The search results page searches for diapers based on the input parameter value 630 "diapers". If the first user clicks the test link 624, the page 630, as shown in Figure 6d, will be displayed on the first user's terminal. Through the test area 620 described above, the electronic device can provide examples of each deep link and test links that can be confirmed immediately, providing users with an interface that allows them to easily add or update parameters associated with each deep link.

[0083] On the other hand, although the above embodiments only describe deep links associated with mobile applications, they are not limited to mobile applications. As will be understood by those with common sense, they can be fully extended by the same linking rules between mobile applications and web pages on mobile or static devices through cross-platform frameworks (e.g., React Native, Flutter).

[0084] Figure 7 is a schematic diagram illustrating the various configurations of an electronic device according to one embodiment of the present invention. The electronic device 700 shown in Figure 7 may include the electronic device 110 shown in Figure 1.

[0085] Referring to FIG7, the electronic device 700 may include a processor 710 and a memory 720, and can implement methods for creating deep links associated with services. FIG7 only shows the components relevant to this embodiment. Therefore, those skilled in the art will understand that the electronic device 700 may include other common components in addition to those shown in FIG7.

[0086] The processor 710 controls the overall functionality of the electronic device 700 for generating deep links associated with services. For example, the processor 710 controls the electronic device 700 by executing programs stored in the memory 720 within the electronic device 700. The processor 710 can be implemented as a CPU (central processing unit), GPU (graphics processing unit), or AP (application processor) within the electronic device 700, but is not limited to these.

[0087] Memory 720 is hardware that stores various data processed within electronic device 700. Memory 720 can store processed data and data to be processed in electronic device 700. Furthermore, memory 720 can store applications, drives, etc., driven by electronic device 700. Memory 720 may include: RAM (random access memory) such as DRAM (dynamic random access memory), SRAM (static random access memory), ROM (read-only memory), EEPROM (electrically erasable programmable read-only memory), CD-ROM (Compact Disc Read-Only Memory), Blu-ray or other optical disk storage, HDD (hard disk drive), SSD (solid state drive), or flash memory.

[0088] On the other hand, this specification and drawings disclose preferred embodiments of the invention. Although specific terminology is used, it is only for the purpose of readily illustrating the technical content of the invention and aiding in understanding the invention, and is not intended to limit the scope of the invention. Those skilled in the art will understand that other variations based on the technical concept of the invention can be implemented in addition to the embodiments disclosed herein.

[0089] The electronic device or terminal described in the above embodiments may include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with external devices, and a user interface device such as a touch panel, keys, and icons. Computer-readable code or program commands, implemented using software modules or algorithms and executable on the processor, can be stored on a computer-readable recording medium. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical reading media (e.g., CD-ROM, DVD, etc.). The computer-readable recording medium is distributed across a network-connected computer system, enabling distributed storage and execution of computer-readable code. The medium can be read by a computer, stored in memory, and executed by a processor.

[0090] This embodiment can be represented by functional blocks and various processing steps. These functional blocks can be implemented by different numbers of hardware and / or software components performing specific functions. For example, the embodiment can employ integrated circuits capable of performing various functions via the control of one or more microprocessors or other control devices, such as memory, processing, logic, lookup tables, etc. The components can be executed by software programs or software elements. Similarly, this embodiment includes various algorithms implemented by combinations of data structures, processes, routines, or other programming designs, and therefore can be implemented using programming or scripting languages ​​such as C, C++, Java, assemblers, Python, etc. Functionally, it can be implemented by algorithms executed in one or more processors. Furthermore, this embodiment can employ prior art for electronic environment setup, signal processing, and / or data processing. Terms such as "mechanism," "component," "mechanism," and "structure" are used broadly and are not limited to mechanical and physical structures. The above terms may be associated with processors and include the meaning of a series of software processes.

[0091] The above embodiment is only an example, and other embodiments can be implemented within the scope of the invention application described below.

[0092] 110: Electronic devices 120: First User Terminal 130: Second User Terminal 300: Deep Link Management System 310: Shared deep link resources 320: Deep Link Management Service 330: Deep Link Code Generator 340: Deep Link Code Change Sensor 400: Page 410: Area 420: Area 430: Area 440: Page 441: Area 442: Area 443: Area 450: Area 460: Area 500: Page 510: Area 511: Area 520: Area 521: Area 530: Skeleton Code 600: Page 610: The First Deep Link 620: Test Area 621: Area 622: Area 623: Parameter value 624: Test Link Page 630 700: Electronic devices 710: Processor 720: Memory S210: Steps S220: Steps S230: Steps S240: Steps S250: Steps

Claims

1. A method for generating a deep link associated with a service, implemented by an electronic device, comprising the steps of: providing a first page to a first user terminal for requesting the generation of a deep link; obtaining information of a first deep link by user input corresponding to the first page; storing the information of the first deep link in a database; generating code associated with the first deep link based on the information of the first deep link stored in the database; and publishing the first deep link to an application associated with the service based on the code.

2. The method of request item 1, wherein the step of generating the code associated with the first deep link includes the following steps: confirming information on a plurality of deep links including the first deep link from the database; providing a second page to a second user terminal containing a list of the plurality of deep links; and generating the code associated with the first deep link based on user input corresponding to the second page.

3. The method of request item 1, wherein the information of the first deep link mentioned above includes information of at least one of the deep link version, compatible operating system, and compatible application version.

4. As in request item 1, wherein the information of the first deep link includes the page type associated with the first deep link.

5. The method of request item 1, wherein the information of the first deep link includes information of the OS compatible with the first deep link, and the step of generating code associated with the first deep link further includes the following steps: generating a link file corresponding to the OS compatible with the first deep link, the link file being uploaded to the network server for the purpose of executing the first deep link.

6. The method of claim 1, wherein the step of publishing the first deep link further includes the following steps: before publishing the first deep link, searching the database for code associated with the first deep link; if code associated with the first deep link is found in the database, publishing the first deep link; and if code associated with the first deep link is not found in the database, providing a notification to the second user terminal used to manage deep links.

7. The method of Request 1, wherein the information of the first deep link includes an application version compatible with the first deep link, the step of publishing the first deep link further includes the following steps: after publishing the first deep link, confirming the version of the application for which the first deep link has been published; and updating the application versions stored in the database that are compatible with the first deep link to the version of the application.

8. The method of request item 1 further includes the following steps: confirming information about a second deep link that is no longer in use by user input corresponding to the first page mentioned above; scanning the code of deep links published in the application to confirm whether code associated with the second deep link has been published; if code associated with the second deep link has been published, generating a deletion request for the code associated with the second deep link; and providing the deletion request to a second user terminal used to manage deep links.

9. The method of request item 1, wherein the first page includes a list of multiple deep links stored in the database, and the step of publishing the first deep link further includes the following steps: updating the status information of the first deep link and the application version information of the published first deep link in the list.

10. The method of claim 9 further includes the steps of: obtaining user input from the first user terminal corresponding to the first deep link included in the above list; and in response to the user input corresponding to the first deep link, providing a test area for testing the first deep link to the first page.

11. The method of claim 10 further includes the following steps: obtaining a parameter value associated with the first deep link from the first user terminal by means of user input corresponding to the test area; generating a test link for the first deep link based on the parameter value; displaying the test link in the test area; and providing a page corresponding to the test link to the first user terminal according to user input corresponding to the test link.

12. An electronic device for generating deep links associated with a service, comprising: Memory, which stores at least one command; and processor; The processor performs the following actions: executes at least one of the commands described above to provide a first page to a first user terminal for requesting the generation of a deep link; obtains information about the first deep link by user input corresponding to the first page; stores the information about the first deep link in a database; generates code associated with the first deep link based on the information about the first deep link stored in the database; and publishes the first deep link to the application associated with the service based on the code.

13. A non-transitory computer-readable storage medium storing a program for executing a method in a computer to generate a deep link associated with an electronic device and a service, the method comprising the steps of: providing a first page to a first user terminal for requesting the generation of a deep link; obtaining information of the first deep link by user input corresponding to the first page; storing the information of the first deep link in a database; generating code associated with the first deep link based on the information of the first deep link stored in the database; and publishing the first deep link to the application associated with the service based on the code.

Images