CN113065079B - Method, equipment and storage medium for realizing calling of native page based on address protocol - Google Patents
Method, equipment and storage medium for realizing calling of native page based on address protocol Download PDFInfo
- Publication number
- CN113065079B CN113065079B CN202110393296.8A CN202110393296A CN113065079B CN 113065079 B CN113065079 B CN 113065079B CN 202110393296 A CN202110393296 A CN 202110393296A CN 113065079 B CN113065079 B CN 113065079B
- Authority
- CN
- China
- Prior art keywords
- address
- page
- protocol
- native
- parameter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to the field of browser page call, and discloses a method, equipment and a storage medium for realizing call of a native page based on an address protocol.
Description
Technical Field
The invention relates to the field of browser page calling, and particularly provides a method, equipment and a storage medium for calling a native page based on an address protocol.
Background
Nowadays, mobile internet is actively developed, and App running on intelligent mobile terminals has more and more service functions, so that in order to facilitate dynamic update and cross-platform development of pages, many App manufacturers adopt a Hybrid (Hybrid) development framework. This development framework refers to dividing the implementation of pages within an application into two ways: traditional Native (Native) pages and HTML pages, wherein the HTML pages rely on a browser (WebView) of a Native App to access and load page resources of a remote server, and are displayed in the WebView.
When the framework of the hybrid-App is used deeply, the problem of the interaction of the native page and the HTML page is likely to be encountered. Opening and accessing the HTML page in the original page flow is relatively simple and direct, opening the WebView in the corresponding jump-to-port, and designating the URL address to be accessed; while calling and/or accessing native pages in HTML pages is correspondingly complex.
The prior art mainly solves the problem of calling and/or accessing the original page by two ways, namely calling a primary method by using a JS calling interface provided by a mobile phone App Webview primary development framework, so as to realize the purpose of jumping the original page by the HTML, but the way has the compatibility limit of a system level; the method has the advantages that through integrating a JSbridge framework of a third-party open source, URL interception, analysis and calling are carried out by utilizing Bridge objects in the framework, the open source solution is existing, the invasion of the whole system is large, the cost of customized development is high, and the difficulty is large.
Disclosure of Invention
In order to solve the problems of compatibility limitation, uncontrollable safety and high custom integration cost of the calling scheme in the prior art, the invention provides a method, equipment and a storage medium for realizing calling of a native page based on an address protocol.
The technical scheme of the invention is as follows:
a method for invoking native pages based on address protocol implementation, comprising:
s1: customizing a WebView container controller class of an address protocol based on a URL format, and judging whether an HTML page is or not according with an address agreed by the protocol through a WebView interceptor integrated in the WebView container controller class;
s2: when the judgment result of the S1 is yes, the next step of processing is carried out, and when the judgment result of the S1 is no, the normal jump is carried out to a new address;
s3: the address conforming to the protocol convention is analyzed by a route distributor, and the analyzed parameter value is distributed to two branches of native and html for processing and judgment;
s4: two branches conforming to native and html are carried out, namely the next step is carried out, otherwise, no jump is carried out; s5: and judging the type of the matched branch, entering a specified address page or comparing the specified address page with the name of the original page which can be jumped, and if the comparison is matched, jumping is carried out, otherwise, no jump is carried out.
Further, the address protocol includes an HTTP domain name portion, a private address portion, a fixed parameter portion, and a service parameter portion, where the private address portion is a fixed address path agreed by the address protocol, the fixed parameter portion includes a type parameter and a target parameter, and the service parameter portion carries out parameter transmission according to a native page requirement.
Further, the step S2 is to process the HTTP domain name part and the private address part of the address protocol, judge through a WebView interceptor, judge the URL domain name and the path in a life cycle function before the jump, deliver the address conforming to the protocol to a route distributor for processing, and not conform to the protocol, and normally jump to a new address without interception and processing.
Further, the step S3 is to analyze the fixed parameter part of the address conforming to the protocol, take out and match the get parameter, and then distribute the obtained value of the type parameter to two branches of native and html for processing and judging.
Further, the S5 accords with the parameter value of the html branch, namely, the WebView container controller class opens the specified address page, the parameter value of the native branch enters the distribution process of the specific page, the router takes out the value of the target, compares the value with the parameter of the param service of the native page which can be jumped, and jumps when the comparison accords with the parameter, otherwise, does not jump.
Further, the business parameter of the original page is a natural number.
An apparatus for invoking a native page based on an address protocol implementation, the apparatus for invoking a native page based on an address protocol implementation comprising:
a memory, a processor, a communication bus, and an address protocol based implementation stored on the memory that invokes a program of native pages,
the communication bus is used for realizing communication connection between the processor and the memory;
the processor is configured to execute the address-based protocol implementation to invoke the native page program to implement the method for invoking a native page based on the address-based protocol implementation as described in any one of the above.
A computer readable storage medium storing executable instructions, said storage medium storing instructions for calling a native page program based on an address protocol implementation, said address protocol implementation implementing the steps of the method for calling a native page based on an address protocol implementation as described in any one of the above when executed by a processor.
The beneficial effects of the invention at least comprise:
(1) The method is used for calling the original page by the HTML page of the browser of the mobile phone client, has low invasion and low coupling to the original code, can use the custom developed base class or the integrated base class on the WebView page with the jump requirement, and has no code modification to various original pages of the jump target page;
(2) The development cost of the HTML page is extremely low, no additional function call and no support are needed for the existing jump mode, and the original page can be directly accessed only by replacing the target URL with a format meeting the address protocol;
(3) The security is controllable, firstly, the verification of a domain name white list can be carried out in an interceptor, then, only a business-designated original page or a jump method is opened in a route distributor, and a Web page does not have any extra authority to call the pages outside;
(4) The method can be perfectly compatible with new and old versions of the mobile phone operating system, and has good compatibility.
Drawings
FIG. 1 is a flow chart of calling a native page based on an address protocol implementation of the present invention.
FIG. 2 is a schematic diagram of an address protocol composition according to the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
1-2, the invention provides a method for calling a native page based on an address protocol, which comprises the following steps:
s1: customizing a WebView container controller class of an address protocol based on a URL format, and judging whether an HTML page is or not according with an address agreed by the protocol through a WebView interceptor integrated in the WebView container controller class;
s2: when the judgment result of the S1 is yes, the next step of processing is carried out, and when the judgment result of the S1 is no, the normal jump is carried out to a new address;
s3: the address conforming to the protocol convention is analyzed by a route distributor, and the analyzed parameter value is distributed to two branches of native and html for processing and judgment;
s4: two branches conforming to native and html are carried out, namely the next step is carried out, otherwise, no jump is carried out; s5: and judging the type of the matched branch, entering a specified address page or comparing the specified address page with the name of the original page which can be jumped, and if the comparison is matched, jumping is carried out, otherwise, no jump is carried out.
Further, the address protocol comprises an HTTP domain name part, a private address part, a fixed parameter part and a business parameter part.
The HTTP domain name part has no special requirement on the accessed domain name protocol, but the interceptor provides the capability of filtering specific white list domain names and can only process the appointed domain name information. If further control over security is required, this function can be used as a "secure domain name whitelist" and requests that are not trusted domain names will never invoke the App's native page.
The private address part, the protocol agrees with a fixed address path, and all the requests using the path are identified by the interceptor and transferred to the route distributor for subsequent work.
Fixed parameter part: get parameter part of URL starting from C, in "? The "beginning" and the respective parameters are divided by "&". The fixed parameters are agreed by the protocol itself and cannot be changed.
Specifically, there are two parameters:
type: distinguishing the types of the jump pages, wherein the enumerated values of the fields include two types of 'native' and 'html', wherein 'native' is to access the native page, and 'html' is to open a new WebView page and access a designated URL page (actually, a special native page);
target, the name of the target page of the jump. And for the 'native' mode, the 'native' mode corresponds to the original page names defined by the route distributor one by one, and jumps to the corresponding page after matching is completed, and no jump action is performed if the corresponding page cannot be matched. For the "html" approach, the "target" passes on the URL address of the website. The route distributor directly creates a new WebView and passes in the target content, opening a new HTML page.
Business parameter part: the parameters of this section are determined by the needs of each native page itself, which may require some traffic fields to be imported before entry for presentation and querying of this page. This part of the parameters is optionally variable.
The private address part is a fixed address path agreed by an address protocol, the fixed parameter part comprises a type parameter and a target parameter, and the service parameter part carries out parameter transmission according to the original page requirement.
Further, the step S2 is to process the HTTP domain name part and the private address part of the address protocol, and judge through a WebView interceptor, wherein the WebView interceptor judges the URL domain name and the path in a life cycle function before the jump occurs:
the address conforming to the protocol convention under interception is delivered to the route distributor for processing, and the address is not skipped in WebView;
the address conforming to the protocol agrees with the normal jump access, does not intercept and process.
The request conforming to the protocol contracted address is forwarded to the route distributor, in S3, the fixed parameter part of the address conforming to the protocol is firstly analyzed, get parameters are taken out one by one and matched, then the value of the obtained type parameter is judged and distributed to two branches of native and html for processing, and if the value of the type is not equal to any one, no jump is made.
Further, the S5 accords with the parameter value of the HTML branch, that is, the WebView container controller opens the specified address page, the parameter value of the native branch enters the distribution process of the specific page, the router takes out the target value, compares with the parameter of the param service of the native page that can jump, and jumps if the comparison accords with the parameter, otherwise, the service side is not ready to expose the native page to HTML call in the engineering, and does not jump at this time.
Further, the service parameters of the native page are natural number, the param is a service parameter, the parameters are transmitted according to the specific native page requirement, there may be none or a plurality of parameters, and the parameters are defined by a calling party (HTML) and a router according to the specific target page requirement
An apparatus for invoking a native page based on an address protocol implementation, the apparatus for invoking a native page based on an address protocol implementation comprising:
a memory, a processor, a communication bus, and an address protocol based implementation stored on the memory that invokes a program of native pages,
the communication bus is used for realizing communication connection between the processor and the memory;
the processor is configured to execute the address-based protocol implementation to invoke the native page program to implement the method for invoking a native page based on the address-based protocol implementation as described in any one of the above.
A computer readable storage medium storing executable instructions, said storage medium storing instructions for calling a native page program based on an address protocol implementation, said address protocol implementation implementing the steps of the method for calling a native page based on an address protocol implementation as described in any one of the above when executed by a processor.
The method is used for calling the original page by the HTML page of the browser of the mobile phone client, has low invasion and low coupling to the original code, can be used for customizing and developing the base class or the integrated base class on the WebView page with the jump requirement, and has no code modification to various original pages of the jump target page;
the HTML page has extremely low development cost, does not need additional function call and is supported by the existing jump mode, and can directly enter the original page by only replacing the target URL with a format meeting the address protocol.
The foregoing description is only illustrative of the present invention and is not intended to limit the scope of the invention, and all equivalent structures or equivalent processes or direct or indirect application in other related technical fields are included in the scope of the present invention.
Claims (5)
1. A method for calling a native page based on an address protocol is characterized by comprising the following steps: comprising the following steps:
s1: customizing a WebView container controller class of an address protocol based on a URL format, and judging whether an HTML page is or not according with an address agreed by the protocol through a WebView interceptor integrated in the WebView container controller class;
s2: when the judgment result of the S1 is yes, the next step of processing is carried out, and when the judgment result of the S1 is no, the normal jump is carried out to a new address;
s3: the address conforming to the protocol convention is analyzed by a route distributor, and the analyzed parameter value is distributed to two branches of native and html for processing and judgment;
s4: two branches conforming to native and html are carried out, namely the next step is carried out, otherwise, no jump is carried out; s5: judging the type of the matched branch, entering a specified address page or comparing the specified address page with the name of the original page which can be jumped, and if the comparison is matched, jumping is carried out, otherwise, no jump is carried out;
the address protocol comprises an HTTP domain name part, a private address part, a fixed parameter part and a service parameter part, wherein the private address part is a fixed address path agreed by the address protocol, the fixed parameter part comprises a type parameter and a target parameter, and the service parameter part carries out parameter transmission according to the original page requirement;
the S2 processes the HTTP domain name part and the private address part of the address protocol, judges through a WebView interceptor, judges the URL domain name and the path in a life cycle function before the jump, gives the address conforming to the protocol to a route distributor for processing, does not conform to the address conforming to the protocol, does not intercept and process, and jumps to a new address normally;
and S5, the parameter value conforming to the html branch, namely the WebView container controller class opens the specified address page, the parameter value conforming to the native branch enters the distribution process of the specific page, the router takes out the target value, compares the target value with the parameter service parameter of the native page which can be jumped, and jumps when the comparison conforms to the comparison, otherwise, does not do any jump.
2. The method for calling a native page based on address protocol according to claim 1, wherein: and S3, firstly resolving a fixed parameter part of an address conforming to a protocol, taking out and matching a get parameter, and then distributing the obtained value of a type parameter to two branches of native and html for processing and judging.
3. The method for calling a native page based on address protocol according to claim 1, wherein: and the service parameters of the original page are natural numbers.
4. An apparatus for implementing calling a native page based on an address protocol, characterized in that: the device for calling the native page based on the address protocol comprises:
a memory, a processor, a communication bus, and an address protocol based implementation stored on the memory that invokes a program of native pages,
the communication bus is used for realizing communication connection between the processor and the memory;
the processor is configured to execute the address protocol based implementation to invoke a native page program to implement the steps of the address protocol based implementation method of invoking a native page as claimed in any of the preceding claims 1-3.
5. A computer-readable storage medium storing executable instructions, characterized in that: the storage medium has stored thereon an address protocol based implementation calling a native page program, which when executed by a processor implements the steps of the address protocol based implementation calling a native page method of any of the preceding claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110393296.8A CN113065079B (en) | 2021-04-13 | 2021-04-13 | Method, equipment and storage medium for realizing calling of native page based on address protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110393296.8A CN113065079B (en) | 2021-04-13 | 2021-04-13 | Method, equipment and storage medium for realizing calling of native page based on address protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113065079A CN113065079A (en) | 2021-07-02 |
| CN113065079B true CN113065079B (en) | 2023-10-13 |
Family
ID=76566565
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110393296.8A Active CN113065079B (en) | 2021-04-13 | 2021-04-13 | Method, equipment and storage medium for realizing calling of native page based on address protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113065079B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114924816B (en) * | 2022-04-08 | 2023-06-09 | 青岛海尔科技有限公司 | Page jump method, storage medium and electronic device |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8887178B1 (en) * | 2012-10-23 | 2014-11-11 | Google Inc. | Method to customize native operating system views using web technologies in mobile devices |
| CN107644075A (en) * | 2017-09-19 | 2018-01-30 | 北京京东尚科信息技术有限公司 | The method and apparatus for collecting page info |
| CN108228818A (en) * | 2017-12-29 | 2018-06-29 | 网易（杭州）网络有限公司 | Web page resources loading method and device, electronic equipment and storage medium |
| CN108363588A (en) * | 2018-02-07 | 2018-08-03 | 平安科技（深圳）有限公司 | Realize method, electronic device and readable storage medium storing program for executing that web is interacted with primary function |
| CN109783742A (en) * | 2018-12-14 | 2019-05-21 | 平安科技（深圳）有限公司 | For developing method for page jump, device and the computer equipment of auxiliary |
| CN110110263A (en) * | 2019-05-13 | 2019-08-09 | 北京三快在线科技有限公司 | Webpage display process, device, terminal and storage medium |
| CN110309065A (en) * | 2019-06-03 | 2019-10-08 | 平安科技（深圳）有限公司 | Concurrently execution method, apparatus, equipment and the storage medium of test assignment |
| CN110580156A (en) * | 2019-08-21 | 2019-12-17 | 北京摩拜科技有限公司 | Page processing method and device and electronic equipment |
| CN110704783A (en) * | 2019-10-09 | 2020-01-17 | 叮当快药科技集团有限公司 | Interaction method and device of H5 page and native APP based on custom protocol |
| CN111125604A (en) * | 2019-12-30 | 2020-05-08 | 华人运通(上海)云计算科技有限公司 | Page management method and device, terminal equipment and storage medium |
| CN111459685A (en) * | 2019-01-18 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Communication method, device, equipment and readable medium of page end and native end |
| CN111767052A (en) * | 2020-06-30 | 2020-10-13 | 平安国际智慧城市科技股份有限公司 | Interaction method, device and storage medium for H5 page and native APP |
| CN112417337A (en) * | 2020-11-27 | 2021-02-26 | 贝壳技术有限公司 | Page jump implementation method and device, electronic equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9781148B2 (en) * | 2008-10-21 | 2017-10-03 | Lookout, Inc. | Methods and systems for sharing risk responses between collections of mobile communications devices |
-
2021
- 2021-04-13 CN CN202110393296.8A patent/CN113065079B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8887178B1 (en) * | 2012-10-23 | 2014-11-11 | Google Inc. | Method to customize native operating system views using web technologies in mobile devices |
| CN107644075A (en) * | 2017-09-19 | 2018-01-30 | 北京京东尚科信息技术有限公司 | The method and apparatus for collecting page info |
| CN108228818A (en) * | 2017-12-29 | 2018-06-29 | 网易（杭州）网络有限公司 | Web page resources loading method and device, electronic equipment and storage medium |
| CN108363588A (en) * | 2018-02-07 | 2018-08-03 | 平安科技（深圳）有限公司 | Realize method, electronic device and readable storage medium storing program for executing that web is interacted with primary function |
| CN109783742A (en) * | 2018-12-14 | 2019-05-21 | 平安科技（深圳）有限公司 | For developing method for page jump, device and the computer equipment of auxiliary |
| CN111459685A (en) * | 2019-01-18 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Communication method, device, equipment and readable medium of page end and native end |
| CN110110263A (en) * | 2019-05-13 | 2019-08-09 | 北京三快在线科技有限公司 | Webpage display process, device, terminal and storage medium |
| CN110309065A (en) * | 2019-06-03 | 2019-10-08 | 平安科技（深圳）有限公司 | Concurrently execution method, apparatus, equipment and the storage medium of test assignment |
| CN110580156A (en) * | 2019-08-21 | 2019-12-17 | 北京摩拜科技有限公司 | Page processing method and device and electronic equipment |
| CN110704783A (en) * | 2019-10-09 | 2020-01-17 | 叮当快药科技集团有限公司 | Interaction method and device of H5 page and native APP based on custom protocol |
| CN111125604A (en) * | 2019-12-30 | 2020-05-08 | 华人运通(上海)云计算科技有限公司 | Page management method and device, terminal equipment and storage medium |
| CN111767052A (en) * | 2020-06-30 | 2020-10-13 | 平安国际智慧城市科技股份有限公司 | Interaction method, device and storage medium for H5 page and native APP |
| CN112417337A (en) * | 2020-11-27 | 2021-02-26 | 贝壳技术有限公司 | Page jump implementation method and device, electronic equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| "Java heap protection for debugging native methods";Yuji Chiba;《Science of Computer Programming 70 (2008)》;第149-167页 * |
| "移动混合开发框架";徐隆龙 等;《计算机***应用》;第53-59页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113065079A (en) | 2021-07-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8856735B2 (en) | System and method of generating REST2REST services from WADL | |
| US6938077B2 (en) | Client version advertisement service for overriding default client version properties | |
| CN103744686B (en) | Control method and the system of installation is applied in intelligent terminal | |
| CN111708702A (en) | Simulation test method, client, server, system and readable storage medium | |
| CN103973642A (en) | Method and device for realizing JS API security access control | |
| CN103716308A (en) | Multiprotocol platform communication method and multiprotocol platform | |
| CN113065079B (en) | Method, equipment and storage medium for realizing calling of native page based on address protocol | |
| CN109510799B (en) | Page display method, browser client, equipment and storage medium | |
| CN112015495A (en) | Method, device, equipment and medium for mutual calling between Native and H5 | |
| CN106815037B (en) | Application function execution method and device | |
| CN107273118A (en) | The implementation method and device opened a kind of application program more | |
| US20100100955A1 (en) | System and method for secure os access in an ecma-script virtual machine | |
| CN111435382A (en) | Login verification method of page and terminal | |
| CN112818270A (en) | Data cross-domain transfer method and device and computer equipment | |
| CN109885792B (en) | Webdriver technology-based APP bridging method | |
| CN105912357A (en) | Starting method and device for hybrid application | |
| CN113407234B (en) | Cross-platform and cross-browser operation and maintenance access method, system and storage medium | |
| CN108509243A (en) | The method, apparatus and electronic equipment of a kind of page load in application | |
| CN112000313A (en) | Request response method, device, equipment and storage medium | |
| CN116708343A (en) | Conference processing method, apparatus, device, storage medium and program product | |
| CN112835677A (en) | Sandbox-based inherent data protection method and system | |
| US20090082003A1 (en) | Mobile Phone Code Editing Method and Apparatus | |
| CN111177660A (en) | Permission verification method for open platform script code | |
| CN104753921B (en) | The management method and system of a kind of intelligent terminal | |
| CN111953793B (en) | Application distribution method, device, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |