CN113641936A

CN113641936A - Method and device for page jump, electronic equipment and storage medium

Info

Publication number: CN113641936A
Application number: CN202110925458.8A
Authority: CN
Inventors: 杨效桐; 杨磊; 吴志殿; 李环宇
Original assignee: Baidu Online Network Technology Beijing Co Ltd
Current assignee: Baidu Online Network Technology Beijing Co Ltd
Priority date: 2021-08-12
Filing date: 2021-08-12
Publication date: 2021-11-12
Anticipated expiration: 2041-08-12
Also published as: CN113641936B

Abstract

The disclosure provides a method and a device for page jump, electronic equipment and a storage medium, and relates to the technical field of computers, in particular to the technical field of application program design and page configuration. The implementation scheme is as follows: a method for page hopping, comprising: determining a page element in a WEB page serving as a jump starting page and a URL link corresponding to the page element and associated with jump; determining a link flag corresponding to a URL link of a page element and a type of a native page corresponding to the link flag as a jump target page; and performing a jump from the WEB page to the native page based on the URL link and the type of the native page corresponding to the link flag.

Description

Method and device for page jump, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to the field of application program design and page configuration technologies, and in particular, to a method and an apparatus for page jump, an electronic device, a computer-readable storage medium, and a computer program product.

Background

Currently, mainstream development modes of application programs (APP) may relate to WEB APP, native APP (native APP) and hybrid APP (hybrid APP). WEB APP is mainly developed based on the HTML5 standard, so the development cost is low. Native APP is relatively expensive to develop, but can make full use of device hardware, and therefore can bring a better user experience. Hybrid APP can make full use of the advantages of both WEB APP and native APP, and the development cost advantage brought based on WEB pages and the user experience promotion based on native pages are also provided. However, the development of hybrid APP also brings complex technical difficulties, and how to implement automatic adaptation in the process of jumping from a WEB page to a native page is one of the problems to be solved urgently.

The approaches described in this section are not necessarily approaches that have been previously conceived or pursued. Unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section. Similarly, unless otherwise indicated, the problems mentioned in this section should not be considered as having been acknowledged in any prior art.

Disclosure of Invention

The present disclosure provides a method, an apparatus, an electronic device, a computer-readable storage medium, and a computer program product for page hopping.

According to an aspect of the present disclosure, there is provided a method for page jump, including: determining a page element in a WEB page serving as a jump starting page and a URL link corresponding to the page element and associated with jump; determining a link flag corresponding to the URL link of the page element and a type of a native page as a jump target page corresponding to the link flag; and performing a jump from the WEB page to the native page based on the URL link and the type of the native page corresponding to the link flag.

According to another aspect of the present disclosure, there is provided an apparatus for page jump, including: a first determination unit configured to determine a page element in a WEB page as a jump start page, and a URL link associated with a jump corresponding to the page element; a second determination unit configured to determine a link flag corresponding to the URL link of the page element, and a type of a native page as a jump target page corresponding to the link flag; and an execution unit configured to execute a jump from the WEB page to the native page based on the URL link and the type of the native page corresponding to the link flag.

According to another aspect of the present disclosure, there is provided an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor, which when executed by the at least one processor, cause the at least one processor to perform the method as described above.

According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method as described above.

According to another aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein the computer program realizes the method as described above when executed by a processor.

According to one or more embodiments of the disclosure, flexible and automatic adaptation of a jump process from a WEB page to a native page can be realized.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the embodiments and, together with the description, serve to explain the exemplary implementations of the embodiments. The illustrated embodiments are for purposes of illustration only and do not limit the scope of the claims. Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements.

Fig. 1 illustrates a schematic diagram of an exemplary system in which various methods and apparatus described herein may be implemented in accordance with embodiments of the present disclosure.

FIG. 2 shows a flow diagram of a method for page hopping according to an embodiment of the present disclosure.

FIG. 3 illustrates an exemplary diagram of page elements in a WEB page according to an embodiment of the disclosure.

FIG. 4 shows a block diagram of a system architecture to which a method for page jumping according to an embodiment of the present disclosure is applied.

FIG. 5 shows a block diagram of an apparatus for page hopping, according to one embodiment of the present disclosure.

FIG. 6 shows a block diagram of an apparatus for page jumping, according to another embodiment of the present disclosure.

Fig. 7 shows a block diagram of an electronic device to which the embodiments of the present disclosure can be applied.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

In the present disclosure, unless otherwise specified, the use of the terms "first", "second", etc. to describe various elements is not intended to limit the positional relationship, the timing relationship, or the importance relationship of the elements, and such terms are used only to distinguish one element from another. In some examples, a first element and a second element may refer to the same instance of the element, and in some cases, based on the context, they may also refer to different instances.

The terminology used in the description of the various described examples in this disclosure is for the purpose of describing particular examples only and is not intended to be limiting. Unless the context clearly indicates otherwise, if the number of elements is not specifically limited, the elements may be one or more. Furthermore, the term "and/or" as used in this disclosure is intended to encompass any and all possible combinations of the listed items.

In the related art, for the jump from the WEB page to the native page, the jump process is generally designed individually according to the types of various native pages (e.g., applet, video playing, online live broadcasting, etc.). This often requires two sets of parameters for the WEB page and the native page to be defined separately, which makes it difficult to achieve automatic adaptation of the jump from the WEB page to the native page.

In view of the above problems, according to an aspect of the present disclosure, a method for page jump is provided. Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

Fig. 1 illustrates a schematic diagram of an exemplary system 100 in which various methods and apparatus described herein may be implemented in accordance with embodiments of the present disclosure. Referring to fig. 1, the system 100 includes one or

more client devices

101, 102, 103, 104, 105, and 106, a server 120, and one or more communication networks 110 coupling the one or more client devices to the server 120.

Client devices

101, 102, 103, 104, 105, and 106 may be configured to execute one or more applications.

In an embodiment of the present disclosure, the server 120 may run one or more services or software applications that enable the execution of the method for page hopping according to an embodiment of the present disclosure.

In some embodiments, the server 120 may also provide other services or software applications that may include non-virtual environments and virtual environments. In certain embodiments, these services may be provided as web-based services or cloud services, for example, provided to users of

client devices

101, 102, 103, 104, 105, and/or 106 under a software as a service (SaaS) model.

In the configuration shown in fig. 1, server 120 may include one or more components that implement the functions performed by server 120. These components may include software components, hardware components, or a combination thereof, which may be executed by one or more processors. A user operating a

client device

101, 102, 103, 104, 105, and/or 106 may, in turn, utilize one or more client applications to interact with the server 120 to take advantage of the services provided by these components. It should be understood that a variety of different system configurations are possible, which may differ from system 100. Accordingly, fig. 1 is one example of a system for implementing the various methods described herein and is not intended to be limiting.

A user may issue instructions using

client devices

101, 102, 103, 104, 105, and/or 106 to instruct performance of a method for page hopping according to an embodiment of the present disclosure. The client device may provide an interface that enables a user of the client device to interact with the client device. The client device may also output information to the user via the interface. Although fig. 1 depicts only six client devices, those skilled in the art will appreciate that any number of client devices may be supported by the present disclosure.

Client devices

101, 102, 103, 104, 105, and/or 106 may include various types of computer devices, such as portable handheld devices, general purpose computers (such as personal computers and laptop computers), workstation computers, wearable devices, gaming systems, thin clients, various messaging devices, sensors or other sensing devices, and so forth. These computer devices may run various types and versions of software applications and operating systems, such as Microsoft Windows, Apple iOS, UNIX-like operating systems, Linux, or Linux-like operating systems (e.g., Google Chrome OS); or include various Mobile operating systems, such as Microsoft Windows Mobile OS, iOS, Windows Phone, Android. Portable handheld devices may include cellular telephones, smart phones, tablets, Personal Digital Assistants (PDAs), and the like. Wearable devices may include head mounted displays and other devices. The gaming system may include a variety of handheld gaming devices, internet-enabled gaming devices, and the like. The client device is capable of executing a variety of different applications, such as various Internet-related applications, communication applications (e.g., email applications), Short Message Service (SMS) applications, and may use a variety of communication protocols.

Network 110 may be any type of network known to those skilled in the art that may support data communications using any of a variety of available protocols, including but not limited to TCP/IP, SNA, IPX, etc. By way of example only, one or more networks 110 may be a Local Area Network (LAN), an ethernet-based network, a token ring, a Wide Area Network (WAN), the internet, a virtual network, a Virtual Private Network (VPN), an intranet, an extranet, a Public Switched Telephone Network (PSTN), an infrared network, a wireless network (e.g., bluetooth, WIFI), and/or any combination of these and/or other networks.

The server 120 may include one or more general purpose computers, special purpose server computers (e.g., PC (personal computer) servers, UNIX servers, mid-end servers), blade servers, mainframe computers, server clusters, or any other suitable arrangement and/or combination. The server 120 may include one or more virtual machines running a virtual operating system, or other computing architecture involving virtualization (e.g., one or more flexible pools of logical storage that may be virtualized to maintain virtual storage for the server). In various embodiments, the server 120 may run one or more services or software applications that provide the functionality described below.

The computing units in server 120 may run one or more operating systems including any of the operating systems described above, as well as any commercially available server operating systems. The server 120 may also run any of a variety of additional server applications and/or middle tier applications, including HTTP servers, FTP servers, CGI servers, JAVA servers, database servers, and the like.

In some implementations, the server 120 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of the

client devices

101, 102, 103, 104, 105, and 106. Server 120 may also include one or more applications to display data feeds and/or real-time events via one or more display devices of

client devices

101, 102, 103, 104, 105, and 106.

In some embodiments, the server 120 may be a server of a distributed system, or a server incorporating a blockchain. The server 120 may also be a cloud server, or a smart cloud computing server or a smart cloud host with artificial intelligence technology. The cloud Server is a host product in a cloud computing service system, and is used for solving the defects of high management difficulty and weak service expansibility in the traditional physical host and Virtual Private Server (VPS) service.

The system 100 may also include one or more databases 130. In some embodiments, these databases may be used to store data and other information. For example, one or more of the databases 130 may be used to store information such as audio files and video files. The database 130 may reside in various locations. For example, the database used by the server 120 may be local to the server 120, or may be remote from the server 120 and may communicate with the server 120 via a network-based or dedicated connection. The database 130 may be of different types. In certain embodiments, the database used by the server 120 may be, for example, a relational database. One or more of these databases may store, update, and retrieve data to and from the database in response to the command.

In some embodiments, one or more of the databases 130 may also be used by applications to store application data. The databases used by the application may be different types of databases, such as key-value stores, object stores, or regular stores supported by a file system.

The system 100 of fig. 1 may be configured and operated in various ways to enable application of the various methods and apparatus described in accordance with the present disclosure.

FIG. 2 shows a flow diagram of a method 200 for page jumping, according to an embodiment of the present disclosure. As shown in fig. 2, a flow chart of a method 200 according to an embodiment of the present disclosure may include the steps of:

s202, determining a page element in the WEB page as a jump starting page and a URL (uniform resource locator) link corresponding to the page element and associated with the jump;

s204, determining a link mark corresponding to the URL link of the page element and the type of a native page which is a jump target page and corresponds to the link mark; and

s206, based on the URL link and the type of the native page corresponding to the link mark, jumping from the WEB page to the native page is executed.

According to the method for page jump disclosed by the invention, the information about the WEB page of the jump source and the information about the original page of the jump target are respectively determined and are associated through the link mark of the URL link, so that the content related to the jump behavior can be independently set, and the jump behavior can be conveniently modified to realize flexible and automatic adaptation of the jump process.

In step S202, the WEB page may correspond to a page of WEB APP developed based on the HTML5 standard. And in the process of jumping from the WEB page to the original page, the WEB page serves as a jump starting page. The page elements may include, for example, a slide banner (banner), tab icon, tool (tool) icon, etc. that is shown on the WEB page.

Fig. 3 exemplarily shows a schematic diagram of a page element in a WEB page 300. As shown in fig. 3, assuming that the user inputs the search term "college entrance" on the search interface of APP, the retrieved search result is first presented in a manner shown on the WEB page 300. The page elements in WEB page 300 may include a first element 301, a second element 302, and a third element 303. The first element 301 may be a slide banner. The corresponding title may be displayed on the slide banner as shown "study-leaving application strategy". The user may, for example, change from the current slide banner to the next slide banner by sliding the touch screen left or right. The second element 302 may be a label icon and the third element 303 may be a tool icon. The tab icon and tool icon may display corresponding headings below the icon, on the icon, or in any other location adjacent to the icon, such as "volunteer fill," "college introduction," "panoramic campus," etc., as shown. It will be appreciated that fig. 3 shows some examples of page elements by way of example only. However, the form and number of the page elements presented on the WEB page may be modified and changed as needed in the actual page design, and the present disclosure does not limit this.

The page elements may have corresponding URL links. The user may access the corresponding URL link, for example, by clicking on the slide banner, tab icon, and tool icon. For example, in connection with the first element 301 shown in fig. 3, i.e. the slide banner, in step S202, the page element and the corresponding URL link may be defined in different fields in the code segment.

Code segment example 1:

as shown above, the first element 301 may be defined in the field "banner" and the URL link corresponding to the first element 301 may be defined in the field "URL". In other words, step S202 may be referred to as a determination of "presentation data," which may include a page element and a URL link associated with a jump corresponding to the page element.

It will be appreciated that the above code segment examples are intended to illustrate by way of example how to practice step 202 of embodiments of the present disclosure, and that the schematic illustrations in the code segments are not to be construed as limiting the present disclosure, but merely as illustrative purposes.

In step S204, the link flag of the URL link may be a result obtained by performing a numerical operation on the URL link.

According to some embodiments, the link flag may be obtained by hashing the URL link. In this way, a value uniquely characterizing the URL link can be obtained, and then a page element in the WEB page as the jump start page can be associated via the value.

The types of native pages may include, for example, applets, video playback, live online, and the like. As described above, since the development of native APP can make full use of device hardware, there is a need to jump from a WEB page to a native page for presentation and interaction to bring better user experience.

For example, again in connection with the first element 301 shown in fig. 3, i.e. the slide banner, in step S204, the link flag of the URL link and the type of the native page corresponding to the link flag may be defined in different fields in the code segment.

Code segment example 2:

as indicated above, the field "$ { urlsign }" may represent a link flag for a URL link, which may be a hash value of the URL link, for example. The type of native page may be defined in the field "NAType". The above example of a code segment may follow a schema data structure. In other words, step S204 may be referred to as determination of "feature data", which may include a link flag of a URL link and a type of a native page corresponding to the link flag.

It will also be appreciated that the above code segment examples are intended to illustrate by way of example how to practice step 204 of embodiments of the present disclosure, and that the schematic illustrations in the code segments are not to be construed as limiting the present disclosure, but merely as illustrative.

According to some embodiments, the type of native page may include a plurality of sub-types, ordered by priority. Only one type, i.e. one subtype, is exemplarily shown in the code segment example 2 as shown above. However, multiple subtypes of the native page to jump to may also be defined under the field "types". In this way, the type of the corresponding native page can be flexibly set according to the page element in the WEB page, and such a setting process does not affect the definition part on the page element, thereby facilitating automatic adaptation of the jump from the WEB page to the native page.

The subtypes may be ordered by priority such that when jumping, it is possible to jump preferentially to a native page corresponding to a subtype having the highest priority among the plurality of subtypes. For example, assuming that three subtypes "video play", "applet", "live online" are arranged in descending order of priority, "video play" indicates a subtype having the highest priority among the subtypes, and thus preferentially jumps to a native page corresponding to "video play" at the time of jumping.

Taking the third element 303 shown in FIG. 3 (e.g., a tool icon titled "introduction to college") as an example, assuming that a user accessing a corresponding URL link by clicking on the page element will initiate the playing of a video, "video play" may be set to the subtype with the highest priority, thus, when jumping, jumping preferentially to the native page corresponding to the subtype for presentation.

According to some embodiments, after step S204, it may also be determined whether the determined type of native page can support the current jump. If the determined type of the native page does not support the current jump, the type of the native page and the corresponding link flag may be removed. This process may also be referred to as a "destage" process for the type of native page.

Specifically, the types of native pages that can be supported by the APP can be known from, for example, user-agent information of the APP used by the user. For example, assuming that the type of the native page determined in step S202 includes "applet", but it is known through the user-agent information that the APP does not support jumping to the native page of the "applet" type, the type of the "applet" may be removed at this time, and the link flag corresponding thereto is also removed.

In this way, the jump behavior can be flexibly set according to actual conditions, and the realized native page jump can be selectively set according to the development requirements of different manufacturers.

According to some embodiments, in step S206, it may first be determined whether a link flag is currently present. And if the link mark currently exists, executing jump from the WEB page to the original page. And if the link mark does not exist currently, prohibiting the jump from the WEB page to the original page. In this case, for example, a jump can be continued from the WEB page to the WEB page.

In this way, the link flag can be utilized to find whether there is a corresponding native page type to jump accordingly. In other words, the link flag may be viewed as a link between the URL link and the type of native page. The page elements in the WEB page serving as the jump starting page and the types of the original pages serving as the jump target pages can be mutually associated through the link marks, and automatic adaptation of jump from the WEB page to the original pages is facilitated.

According to some embodiments, a page element may include a plurality of sub-page elements. In this case, in step S202, a respective URL link may be determined for each of a plurality of sub-page elements. However, in step S204, when some of the plurality of sub-page elements do not have the type of the native page that can be skipped, the link flag and the type of the native page may be determined only for the other sub-page elements of the plurality of sub-page elements other than the sub-page elements. In this way, the native page type that can be jumped to can be flexibly set according to the actual situation of the page element.

Referring again to fig. 3, a first element 301 may represent a first sub-page element (e.g., a sliding banner), a second element 302 may represent a second sub-page element (e.g., a label icon), and a third element 303 may represent a third sub-page element (e.g., a tool icon). Assuming that the slide banner for the first sub page element does not have the type of native page that can be jumped to (such as it relates only to the display of a web page article, not to a native page that jumps to an applet, video play, etc.), in this case, although the respective URL links are determined for the first to third page elements in step S202, the link flags and the type of native page may not be determined for the first sub page element, but only for the second and third sub page elements in step S204.

As described above, according to the method for page jump of the present disclosure, by separately determining information on a WEB page of a jump source and information on a native page of a jump target and associating the two through a link flag of a URL link, it is possible to separately set contents related to a jump behavior, thereby facilitating modification of the jump behavior to achieve flexible and automatic adaptation of a jump process.

FIG. 4 shows a block diagram of a system architecture 400 applying a method for page hopping according to an embodiment of the present disclosure. As shown in fig. 4, the system architecture 400 may include, from bottom to top, a data layer 402, an adaptation layer 404, and a rendering layer 406.

The data layer 402 may upload presentation data and feature data as described above to the adaptation layer 404. This process may also be referred to as feature path passthrough.

The adaptation layer 404 may decide whether to remove (i.e., "demote") a portion of the types of native pages defined in the feature data based on user-agent information (which may indicate an APP used by the user, such as a hundredth APP or an APP developed by another vendor).

Rendering layer 406 may be used to implement jump behavior, i.e., finding in the feature data whether a corresponding link flag exists to implement a jump. For example, in the rendering layer 406, the incoming parameter may be a URL link to a page element. The rendering layer 406 may utilize the unified call-up component to generate a link flag corresponding to the URL link and look for the presence of the corresponding link flag in the feature data to implement the jump. If the WEB page exists, the jump from the WEB page to the original page is realized, and if the WEB page does not exist, the jump from the WEB page to the WEB page can be continuously realized.

According to another aspect of the present disclosure, there is also provided an apparatus for page jump. FIG. 5 shows a block diagram of an apparatus 500 for page jumping according to one embodiment of the present disclosure. As shown in fig. 5, the apparatus 500 may include: a first determination unit 502, which may be configured to determine a page element in a WEB page as a jump start page, and a URL link associated with a jump corresponding to the page element; a second determining unit 504, which may be configured to determine a link flag corresponding to a URL link of the page element, and a type of a native page as a jump target page corresponding to the link flag; and an execution unit 506, which may be configured to execute a jump from the WEB page to the native page based on the URL link and the type of the native page corresponding to the link flag.

According to some embodiments, the link flag may be obtained by hashing the URL link.

According to some embodiments, the type of native page may include a plurality of sub-types in a priority order, and the execution unit 506 may be configured to: preferentially jumping from a WEB page to a native page corresponding to a subtype having a highest priority among a plurality of subtypes.

According to some embodiments, the page element may comprise a plurality of sub-page elements, and the first determining unit 502 may be configured to: determining a URL link for each sub-page element of a plurality of sub-page elements; and the second determining unit 504 may be configured to: determining a type of a link flag and a native page for a predetermined sub-page element of a plurality of sub-page elements, wherein the remaining sub-page elements of the plurality of sub-page elements other than the predetermined sub-page element do not have a type of a native page that can be jumped.

The operations performed by the

modules

502, 504, and 506 correspond to the steps S202, S204, and S206 described with reference to fig. 2, and therefore the details thereof are not repeated.

FIG. 6 shows a block diagram of an apparatus 600 for page jumping according to another embodiment of the present disclosure.

Modules

602, 604, and 606 of fig. 6 may correspond to

modules

502, 504, and 506 of fig. 5, respectively. In addition, the apparatus 600 may further comprise a further functional module 605, and the

modules

605, 606 may further comprise further sub-functional modules, as will be explained in detail below.

According to some embodiments, the apparatus 600 may further comprise a feedback unit 605, the feedback unit 605 may comprise: a judging unit 6050, which may be configured to judge whether the determined type of the native page can support the current jump; and a removing unit 6052, which may be configured to remove the type of the native page and the corresponding link flag in response to the determined type of the native page does not support the current jump.

According to some embodiments, the execution unit 606 may include: a first sub-unit 6060 configured to determine whether a link flag currently exists; and a second sub-unit 6062 configured to: in response to determining that a link flag currently exists, performing a jump from the WEB page to the native page; or in response to determining that the link flag does not currently exist, inhibiting a jump from the WEB page to the native page.

The operations performed by the modules described in conjunction with fig. 6 may correspond to the method steps described with reference to fig. 2, and therefore, the details thereof are not repeated.

According to another aspect of the present disclosure, there is also provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method as described above.

According to another aspect of the present disclosure, there is also provided a computer program product comprising a computer program, wherein the computer program realizes the method as described above when executed by a processor.

According to another aspect of the present disclosure, there is also provided an electronic device comprising at least one processor; and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor, which when executed by the at least one processor, cause the at least one processor to perform the method as described above.

Referring to fig. 7, a block diagram of a structure of an electronic device 700, which is an example of a hardware device that can be applied to aspects of the present disclosure, which can be applied to the present disclosure, will be described. Electronic device is intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 7, the electronic device 700 includes a computing unit 701, which may perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the electronic device 700 can also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other by a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

A number of components in the electronic device 700 are connected to the I/O interface 705, including: an input unit 706, an output unit 707, a storage unit 708, and a communication unit 709. The input unit 706 may be any type of device capable of inputting information to the electronic device 700, and the input unit 706 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device, and may include, but is not limited to, a mouse, a keyboard, a touch screen, a track pad, a track ball, a joystick, a microphone, and/or a remote controller. Output unit 707 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, a video/audio output terminal, a vibrator, and/or a printer. Storage unit 708 may include, but is not limited to, magnetic or optical disks. The communication unit 709 allows the electronic device 700 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks, and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and/or a chipset, such as bluetooth^TMDevices, 1302.11 devices, WiFi devices, WiMax devices, cellular communication devices, and/or the like.

Computing unit 701 may be a variety of general purpose and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 701 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 701 performs the respective methods and processes described above, such as the method for page jumping. For example, in some embodiments, the method for page hopping may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 708. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 700 via the ROM 702 and/or the communication unit 709. When the computer program is loaded into the RAM 703 and executed by the computing unit 701, one or more steps of the method for page jumping described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured by any other suitable means (e.g., by means of firmware) to perform the method for page hopping.

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be performed in parallel, sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

In the technical scheme of the disclosure, the acquisition, storage and application of the personal information of the related user are all in accordance with the regulations of related laws and regulations, and do not violate the good customs of the public order. It is an intention of the present disclosure that personal information data should be managed and processed in a manner that minimizes the risk of inadvertent or unauthorized access to the use. By limiting data collection and deleting data when it is no longer needed, risks are minimized. All information related to a person in the present application is collected with the knowledge and consent of the person.

Although embodiments or examples of the present disclosure have been described with reference to the accompanying drawings, it is to be understood that the above-described methods, systems and apparatus are merely exemplary embodiments or examples and that the scope of the present invention is not limited by these embodiments or examples, but only by the claims as issued and their equivalents. Various elements in the embodiments or examples may be omitted or may be replaced with equivalents thereof. Further, the steps may be performed in an order different from that described in the present disclosure. Further, various elements in the embodiments or examples may be combined in various ways. It is important that as technology evolves, many of the elements described herein may be replaced with equivalent elements that appear after the present disclosure.

Claims

1. A method for page hopping, comprising:

determining a page element in a WEB page serving as a jump starting page and a URL link corresponding to the page element and associated with jump;

determining a link flag corresponding to the URL link of the page element and a type of a native page as a jump target page corresponding to the link flag; and

performing a jump from the WEB page to the native page based on the URL link and the type of the native page corresponding to the link flag.

2. The method of claim 1, wherein the link flag is obtained by hashing the URL link.

3. The method of claim 1 or 2, further comprising:

judging whether the determined type of the native page can support the current jump or not; and

and in response to the determined type of the native page does not support the current jump, removing the type of the native page and the corresponding link mark.

4. The method of claim 3, wherein performing a jump from the WEB page to the native page based on the URL link and the type of the native page comprises:

determining whether the link flag currently exists; and

in response to determining that the link flag currently exists, performing a jump from the WEB page to the native page; or

In response to determining that the link flag does not currently exist, inhibiting a jump from the WEB page to the native page.

5. The method of any of claims 1-4, wherein the type of the native page includes a plurality of subtypes that are ordered by priority, and wherein,

the executing the jump from the WEB page to the native page comprises: preferentially jumping from the WEB page to a native page corresponding to a subtype having a highest priority among the plurality of subtypes.

6. The method of any of claims 1-5, wherein the page element comprises a plurality of sub-page elements, and wherein

Determining the URL link for each sub-page element of the plurality of sub-page elements; and

determining the type of the link flag and the native page for a predetermined sub-page element of the plurality of sub-page elements, wherein the remaining sub-page elements of the plurality of sub-page elements other than the predetermined sub-page element do not have the type of native page that can be skipped.

7. An apparatus for page hopping, comprising:

a first determination unit configured to determine a page element in a WEB page as a jump start page, and a URL link associated with a jump corresponding to the page element;

a second determination unit configured to determine a link flag corresponding to the URL link of the page element, and a type of a native page as a jump target page corresponding to the link flag; and

an execution unit configured to execute a jump from the WEB page to the native page based on the URL link and a type of the native page corresponding to the link flag.

8. The apparatus of claim 7, wherein the link flag is obtained by hashing the URL link.

9. The apparatus of claim 7 or 8, further comprising a feedback unit comprising:

the judging unit is configured to judge whether the determined type of the native page can support current jump or not; and

a removing unit configured to remove the type of the native page and the corresponding link flag in response to determining that the type of the native page does not support the current jump.

10. The apparatus of claim 9, wherein the execution unit comprises:

a first subunit configured to determine whether the link flag currently exists; and

a second subunit configured to:

11. The apparatus of any of claims 7-10, wherein the type of the native page comprises a plurality of subtypes that are ordered by priority, and wherein,

the execution unit is configured to: preferentially jumping from the WEB page to a native page corresponding to a subtype having a highest priority among the plurality of subtypes.

12. The apparatus of any of claims 7 to 11, wherein the page element comprises a plurality of sub-page elements, and wherein

The first determination unit is configured to: determining the URL link for each sub-page element of the plurality of sub-page elements; and

the second determination unit is configured to: determining the type of the link flag and the native page for a predetermined sub-page element of the plurality of sub-page elements, wherein the remaining sub-page elements of the plurality of sub-page elements other than the predetermined sub-page element do not have the type of native page that can be skipped.

13. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor,

wherein the memory stores instructions executable by the at least one processor, which when executed by the at least one processor, cause the at least one processor to perform the method of any one of claims 1-6.

14. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-6.

15. A computer program product comprising a computer program, wherein the computer program realizes the method according to any of claims 1-6 when executed by a processor.