CN113641936B

CN113641936B - Method, device, electronic equipment and storage medium for page skip

Info

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

Abstract

The disclosure provides a method, a device, electronic equipment and a storage medium for page skip, relates to the technical field of computers, and particularly relates to the technical field of application program design and page configuration. The implementation scheme is as follows: a method for page jumping, 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 the jump; determining a link flag of the URL link corresponding to the page element and a type of the 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, device, electronic equipment and storage medium for page skip

Technical Field

The present disclosure relates to the field of computer technology, and in particular, to the field of application programming and page configuration technology, and more particularly, to a method, an apparatus, an electronic device, a computer readable storage medium, and a computer program product for page skip.

Background

The current mainstream development modes of application programs (APP) may involve WEB APP, native APP (native APP) and hybrid APP (Hybrid APP). WEB APP is mainly developed based on the HTML5 standard, so that the development cost is low. The native APP has higher development cost, but can fully utilize equipment hardware, so that better user experience can be brought. The mixed APP can fully utilize the advantages of the WEB APP and the original APP, so that development cost advantages based on the WEB page are achieved, and user experience based on the original page is improved. However, the development of hybrid APP also brings complex technical difficulties, and how to realize automatic adaptation of the jump process from the WEB page to the native page is one of the problems to be solved.

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, the problems mentioned in this section should not be considered as having been recognized in any prior art unless otherwise indicated.

Disclosure of Invention

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

According to an aspect of the present disclosure, there is provided a method for page jumping, 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 the jump; determining a link flag of the URL link corresponding to 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 jumping, 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 of the URL link corresponding to 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 storing computer instructions for causing the computer to perform the method as described above.

According to one or more embodiments of the present disclosure, flexible and automatic adaptation of the jump procedure of a WEB page to a native page may be achieved.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

The accompanying drawings illustrate exemplary embodiments and, together with the description, serve to explain exemplary implementations of the embodiments. The illustrated embodiments are for exemplary purposes only and do not limit the scope of the claims. Throughout the drawings, identical reference numerals 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 an embodiment of the present disclosure.

FIG. 2 illustrates a flow chart of a method for page hopping in accordance with an embodiment of the present disclosure.

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

Fig. 4 shows a block diagram of a system architecture to which a method for page hopping 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 illustrates a block diagram of an apparatus for page hopping in accordance with another embodiment of the present disclosure.

Fig. 7 shows a block diagram of a structure of an electronic device that can be applied to an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one 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, the use of the terms "first," "second," and the like to describe various elements is not intended to limit the positional relationship, timing relationship, or importance relationship of the elements, unless otherwise indicated, and such terms are merely used 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, they may also refer to different instances based on the description of the context.

The terminology used in the description of the various illustrated 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, the elements may be one or more if the number of the elements is not specifically limited. Furthermore, the term "and/or" as used in this disclosure encompasses 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 separately according to various types of the native page (such as applet, video playing, online live broadcast, etc.). This often requires two sets of parameters to be defined for the WEB page and the native page, respectively, resulting in an automatic adaptation of the jump of the WEB page to the native page that is not easy to achieve.

In view of the foregoing, according to an aspect of the present disclosure, a method for page jumping 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 an embodiment 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 embodiments of the present disclosure, server 120 may run one or more services or software applications that enable execution of methods for page hopping according to embodiments of the present disclosure.

In some embodiments, server 120 may also provide other services or software applications that may include non-virtual environments and virtual environments. In some 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 that are executable by one or more processors. A user operating client devices 101, 102, 103, 104, 105, and/or 106 may in turn utilize one or more client applications to interact with server 120 to utilize the services provided by these components. It should be appreciated 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.

The user may issue instructions using client devices 101, 102, 103, 104, 105, and/or 106 to instruct execution of a method for page hopping in accordance with 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 the present disclosure may support any number of client devices.

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 the like. 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, tablet computers, personal Digital Assistants (PDAs), and the like. Wearable devices may include head mounted displays and other devices. The gaming system may include various 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 number of available protocols, including but not limited to TCP/IP, SNA, IPX, etc. For example only, the 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 that involves virtualization (e.g., one or more flexible pools of logical storage devices that may be virtualized to maintain virtual storage devices of the server). In various embodiments, 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. 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, etc.

In some implementations, server 120 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of 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 implementations, the server 120 may be a server of a distributed system or a server that incorporates a blockchain. The server 120 may also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology. The cloud server is a host product in a cloud computing service system, so as to solve the defects of large management difficulty and weak service expansibility in the traditional physical host and virtual private server (VPS, virtual Private Server) 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 databases 130 may be used to store information such as audio files and video files. 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. Database 130 may be of different types. In some embodiments, the database used by server 120 may be, for example, a relational database. One or more of these databases may store, update, and retrieve the databases and data from the databases in response to the commands.

In some embodiments, one or more of 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 conventional stores supported by the 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 illustrates a flow chart of a method 200 for page hopping in accordance with an embodiment of the present disclosure. As shown in fig. 2, a flowchart of a method 200 according to an embodiment of the present disclosure may include the steps of:

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

s204, determining a link mark of the URL link corresponding to the page element and the type of the original page serving as the jump target page corresponding to the link mark; and

s206, based on the URL link and the type of the original page corresponding to the link mark, executing jump from the WEB page to the original page.

According to the method for page jumping disclosed by the invention, by respectively determining the information about the WEB page of the jumping source and the information about the original page of the jumping target and associating the information about the WEB page and the information about the original page of the jumping target through the link mark of the URL link, contents related to the jumping behaviors can be independently set, so that the jumping behaviors can be modified conveniently to realize flexible and automatic adaptation of the jumping process.

In step S202, the WEB page may correspond to a page of a WEB APP developed based on the HTML5 standard. In the jump process from the WEB page to the original page, the WEB page is used as a jump starting page. The page elements may include, for example, a sliding banner (banner), a tab (tag) icon, a tool (tool) icon, etc., presented on a WEB page.

FIG. 3 schematically illustrates page elements in a WEB page 300. As shown in fig. 3, assuming that the user inputs the term "college entrance examination" on the search interface of the APP, the retrieved search results are first presented in a manner presented on the WEB page 300. Page elements in WEB page 300 can include a first element 301, a second element 302, and a third element 303. The first element 301 may be a sliding banner. The corresponding heading may be displayed on the sliding banner, as shown for "leave-on application purview". The user may change from the current sliding banner to the next sliding banner by sliding the touch screen left and right, for example. The second element 302 may be a label icon and the third element 303 may be a tool icon. The tag icons and tool icons may display corresponding titles below, on, or anywhere else adjacent to the icons, such as "volunteer fills", "institution 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 page elements presented on the WEB page may be any suitable modification and variation as desired in the actual page design, which is not limiting of the present disclosure.

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

Code segment example 1:

"displayData" {// reveal data

"canner" [// first element 301

{

“image”: “http://www.baidu.com/banner.jpg”,

"URL": "http:// www.baidu.com/word=banner"// corresponding URL link

}

]

}

As shown above, the first element 301 may be defined in the field "canner" 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 the disclosed embodiments, and that the schematic illustrations in code segments do not constitute limitations of the present disclosure, but are for illustrative purposes only.

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 can be obtained that uniquely characterizes the URL link, and can then be associated via the value to a page element in the WEB page that is the jump start page.

The types of native pages may include, for example, applets, video playback, online live, etc. As described above, since development of a 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 about a better user experience.

For example, in connection with the first element 301 shown in fig. 3, i.e. the sliding 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:

"featureData" {// feature data

“url_na_params”: {

"URL sign {// URL link }"

“types”: [“NAType”],

"NAType" { }// type of native page

}

As indicated above, the field "$ { URL sign }" may represent a link flag for the URL link, e.g., the link flag may be a hash value for the URL link. The type of native page may be defined in the field "NAType". The code segment examples above 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 the URL link and a type of the 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 step 204 of the disclosed embodiments may be practiced, and that the schematic illustrations in the code segments do not constitute limitations of the present disclosure, but are for illustrative purposes only.

According to some embodiments, the types of native pages may include multiple subtypes that are prioritized. Only one type, namely one subtype, is exemplarily shown in the code segment example 2 shown above. However, multiple sub-types of native pages 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 elements in the WEB page, and such a setting process does not affect the definition portion with respect to the page elements, 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 a jump is made, the jump can be made preferentially to the native page corresponding to the subtype with the highest priority among the plurality of subtypes. For example, assuming that three sub-types "video play", "applet", "online live" are arranged in descending order of priority, the "video play" means a sub-type having the highest priority among the sub-types, and thus preferentially jumps to a native page corresponding to "video play" when jumping.

Taking the third element 303 shown in fig. 3 (e.g., a tool icon titled "introduction to an institution") as an example, assuming that a user would turn on the playing of a video by clicking on the page element to access the corresponding URL link, the "video playing" may be set to the subtype with the highest priority, so that when jumping, it jumps preferentially to the native page corresponding to that subtype for presentation.

According to some embodiments, after step S204, it may also be determined whether the determined type of native page is capable of supporting 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 type of "downgrade" process for native pages.

Specifically, the types of native pages that the APP can support 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", however, knowing that the APP does not support jumping to the native page of the "applet" type through the user-agent information, the type of the "applet" may be removed at this time, while the link flag corresponding thereto is also removed.

In this way, the jump behavior can be flexibly set according to the actual situation, for example, the jump of the original page which can be realized can be selectively set according to the development needs of different manufacturers.

According to some embodiments, in step S206, it may first be determined whether a link flag is currently present. If the link flag is currently present, a jump from the WEB page to the native page is performed. If the link flag does not currently exist, the jump from the WEB page to the native page is prohibited. In this case, for example, a jump may be continued from the WEB page to the WEB page.

In this way, the link flag can be used to find out whether there is a corresponding native page type to make the corresponding jump. In other words, the link flag may be considered 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 page serving as the jump target page can be mutually associated through the link mark, so that automatic adaptation of jump from the WEB page to the original page is facilitated.

According to some embodiments, a page element may include multiple sub-page elements. In this case, in step S202, a respective URL link may be determined for each of the 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 jumped, the link flag and the type of the native page may be determined only for other sub-page elements other than those sub-page elements of the plurality of sub-page elements. In this way, the native page type capable of jumping 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 tab icon), and a third element 303 may represent a third sub-page element (e.g., a tool icon). Assuming that the sliding banner of the first sub-page element does not have a type of native page that can be jumped to (such as it relates only to the display of a web page article, not to the jump to a native page of an applet, video play, etc.), in this case, although the respective URL links are determined for all the first to third page elements in step S202, the link flags and the type of native page may be determined not 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 jumping of the present disclosure, by determining information on a WEB page of a jumping source and information on a native page of a jumping target, respectively, and associating the two by a link flag of URL link, it is possible to separately set contents related to jumping behaviors, thereby facilitating modification of the jumping behaviors to achieve flexible and automatic adaptation of a jumping process.

Fig. 4 illustrates a block diagram of a system architecture 400 to which a method for page hopping according to an embodiment of the present disclosure is applied. 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 pass-through.

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 the APP used by the user, such as a hundred degree APP or other vendor developed APP).

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

According to another aspect of the present disclosure, there is also provided an apparatus for page jumping. Fig. 5 illustrates a block diagram of an apparatus 500 for page hopping, according to one embodiment of the present disclosure. As shown in fig. 5, the apparatus 500 may include: the first determining unit 502 may be configured to determine a page element in a WEB page as a jump start page, and a URL link associated with the jump corresponding to the page element; a second determining unit 504 that may be configured to determine a link flag of the URL link corresponding to the page element and a type of the native page as the jump target page corresponding to the link flag; and an execution unit 506 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 types of native pages may include multiple subtypes ordered by priority, and the execution unit 506 may be configured to: the method includes preferentially jumping from the WEB page to a native page corresponding to a subtype having a highest priority among the 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 of the plurality of sub-page elements; and the second determining unit 504 may be configured to: a link flag and a type of a native page are determined for a predetermined sub-page element of a plurality of sub-page elements, wherein 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 thus the details thereof will not be repeated.

Fig. 6 illustrates a block diagram of an apparatus 600 for page hopping in accordance with another embodiment of the present disclosure. The modules 602, 604, and 606 shown in fig. 6 may correspond to the modules 502, 504, and 506 shown in fig. 5, respectively. In addition, the apparatus 600 may further comprise further functional modules 605, and the modules 605, 606 may further comprise further sub-functional modules, as will be described in more 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 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 not supporting the current jump.

According to some embodiments, the execution unit 606 may include: a first subunit 6060 configured to determine whether a link flag is currently present; and a second subunit 6062 configured to: in response to determining that the link flag is currently present, performing a jump from the WEB page to the native page; or in response to determining that the link flag is not currently present, disabling the jump from the WEB page to the native page.

Operations performed by the various modules described in connection with fig. 6 may correspond to the various method steps described with reference to fig. 2, and thus details thereof are not repeated.

According to another aspect of the present disclosure, there is also provided a non-transitory computer-readable storage medium storing 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 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.

With reference to fig. 7, a block diagram of a structure of an electronic device 700 that can be applied to the present disclosure will be described, which is an example of a hardware device that can be applied to aspects of the present disclosure. Electronic devices are 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 telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary 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 that can 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 may also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

Various 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, the input unit 706 may receive input numeric or character information and generate key signal inputs related to user settings and/or function control of the electronic device, and may include, but is not limited to, a mouse, a keyboard, a touch screen, a trackpad, a trackball, a joystick, a microphone, and/or a remote control. The output unit 707 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. Storage unit 708 may include, but is not limited to, magnetic disks, 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 telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and/or chipsets, such as bluetoothDevices, 1302.11 devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.

The computing unit 701 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of 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, etc. The computing unit 701 performs the respective methods and processes described above, for example, a method for page jumping. For example, in some embodiments, the method for page hopping may be implemented as a computer software program tangibly embodied on 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 RAM 703 and executed by 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 to perform the method for page jumping by any other suitable means (e.g. by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On 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, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code 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 code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. 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. The 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 pointing device (e.g., a mouse or 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 may 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 input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background 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 background, 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 a client and a server. The client and server are typically 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 appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially or in a different order, provided that the desired results of the disclosed aspects are achieved, and are not limited herein.

In the technical scheme of the disclosure, the acquisition, storage and application of the related personal information of the user all accord with the regulations of related laws and regulations, and the public sequence is not violated. It is intended that personal information data should be managed and processed in a manner that minimizes the risk of inadvertent or unauthorized use access. By limiting data collection and deleting data when it is no longer needed, risk is minimized. All information related to the personnel in the present application was collected with the knowledge and consent of the personnel.

Although embodiments or examples of the present disclosure have been described with reference to the accompanying drawings, it is to be understood that the foregoing methods, systems, and apparatus are merely exemplary embodiments or examples, and that the scope of the present application is not limited by these embodiments or examples but only by the claims following the grant and their equivalents. Various elements of the embodiments or examples may be omitted or replaced with equivalent elements thereof. Furthermore, the steps may be performed in a different order than described in the present disclosure. Further, various elements of 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 by equivalent elements that appear after the disclosure.

Claims

1. A method for page jumping, 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 the jump;

determining a link flag of the URL link corresponding to the page element, and a type of a native page as a jump target page corresponding to the link flag, wherein the link flag is obtained by hashing the URL link, and the type of the native page includes a plurality of subtypes ordered by priority; 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, wherein the 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 includes:

determining whether the link flag is currently present; and

in response to determining that the link flag is currently present, preferentially jumping from the WEB page to a native page corresponding to a subtype having a highest priority among the plurality of subtypes; or alternatively

In response to determining that the link flag is not currently present, a jump from the WEB page to the native page is prohibited.

2. The method of claim 1, further comprising:

judging whether the determined type of the native page can support current skip; and

and removing the type of the native page and the corresponding link mark in response to determining that the type of the native page does not support current jumping.

3. The method of claim 1 or 2, 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 link flag and the type of the native page for a predetermined sub-page element of the plurality of sub-page elements, wherein 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.

4. 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, wherein the link flag is obtained by hashing the URL link, the type of the native page including a plurality of subtypes ordered by priority; 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, wherein the execution unit includes:

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

a second subunit configured to:

5. The apparatus of claim 4, further comprising a feedback unit comprising:

The judging unit is configured to judge whether the determined type of the native page can support current skip; and

and the removing unit is configured to remove the type of the original page and the corresponding link mark in response to the determined type of the original page not supporting the current jump.

6. The apparatus of claim 4 or 5, 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 link flag and the type of the native page for a predetermined sub-page element of the plurality of sub-page elements, wherein 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.

7. 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 of claims 1-3.

8. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-3.