CN112015495A - Method, device, equipment and medium for mutual calling between Native and H5 - Google Patents
Method, device, equipment and medium for mutual calling between Native and H5 Download PDFInfo
- Publication number
- CN112015495A CN112015495A CN202010889805.1A CN202010889805A CN112015495A CN 112015495 A CN112015495 A CN 112015495A CN 202010889805 A CN202010889805 A CN 202010889805A CN 112015495 A CN112015495 A CN 112015495A
- Authority
- CN
- China
- Prior art keywords
- calling
- native
- data
- page
- websocket
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application relates to the technical field of computer application, and discloses a method, a device, equipment and a medium for mutual calling between Native and H5, wherein the method is applied to a client, and the client comprises the following steps: native terminal, calling plug-in; the method comprises the following steps: acquiring a method calling instruction; establishing a WebView according to a calling plug-in and loading an H5 page to obtain a target WebView; when the method call instruction is an H5 method call instruction, acquiring first call data through a Native terminal, sending the first call data to an H5 page through a WebSocket Server and a WebSocket Client, and calling an H5 method according to the first call data through an H5 page in a target WebView; and when the method calling instruction is a Native method calling instruction, acquiring second calling data through an H5 page, sending the second calling data to a Native terminal through a WebSocket Client and a WebSocket Server, and calling a Native method according to the second calling data through the Native terminal in the target WebView. The method and the device have better compatibility, improve the communication efficiency and can completely transmit the information of the large file.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a method, an apparatus, a device, and a medium for inter-invoking between Native and H5.
Background
With the development of the internet, various mobile apps (software for mobile electronic devices) are layered on the market. The requirements of people on the mobile App are continuously improved, so that the Hybrid technology (Hybrid development mode) is widely applied, and Native and Web are simultaneously used for building the mobile App.
For the development of Hybrid, a Native and H5 (Web page of a mobile terminal) interaction mode is the most critical technology. In the prior art, Native communication with H5 is mainly completed through Jsbridge (communication defining Native and JS), and Native completes the method for H5 to call Native by intercepting URLSCHEM sent by H5 and then analyzing the information carried by URLSCHEM. And Native loads JavaScript codes through a loadUrl method provided by WebView to finish the method of calling H5 by Native. Because the coding information of the picture is required to be transmitted on a path, the path of the large file is too long, URLSCHEMA has the limitation of URL length, the path needs to be cut off, and the transmission of the large file is incomplete after the path is cut off; and because the message is delivered in one way and Native needs to send the message in the main thread, the message transmission efficiency is low.
Disclosure of Invention
The application mainly aims to provide a method, a device, equipment and a medium for mutual calling between Native and H5, and aims to solve the technical problems that large files transmitted are incomplete and message transmission efficiency is low when Native and H5 communication is completed through Jsbridge in the prior art.
In order to achieve the above object, the present application proposes a method for invoking each other between Native and H5, where the method is applied to a client, and the client includes: the Native terminal and the calling plug-in are used for realizing mutual calling between the Native terminal and the H5 page;
the method comprises the following steps:
acquiring a method calling instruction, wherein the method calling instruction comprises the following steps: h5 method call instruction or/and Native method call instruction;
responding to the method calling instruction, creating WebView according to the calling plug-in, loading the H5 page, and establishing communication connection to obtain a target WebView;
when the method call instruction is the H5 method call instruction, acquiring first call data through the Native terminal, sending the first call data to the H5 page through a WebSocket Server and a WebSocket Client, and calling an H5 method according to the first call data through the H5 page in the target WebView;
and when the method calling instruction is the Native method calling instruction, acquiring second calling data through the H5 page, sending the second calling data to the Native terminal through the WebSocket Client and the WebSocket Server, and calling a Native method according to the second calling data through the Native terminal in the target WebView.
Further, the calling plug-in includes: customizing a WebView component, a JS file and a Native SDK, wherein the Native SDK comprises a WebSocket Server code, and the JS file comprises a WebSocket Client code; and the number of the first and second groups,
the step of creating the WebView according to the calling plug-in, loading the H5 page and establishing communication connection to obtain the target WebView comprises the following steps:
calling the customized WebView component through the Native terminal to create a WebView to obtain a first WebView;
loading the WebSocket Server code through the Native terminal, and finishing starting the WebSocket Server when the loading of the WebSocket Server code is finished;
loading the H5 page in the first WebView to obtain a second WebView, injecting the WebSocket Client code in the process of loading the H5 page, and finishing starting the WebSocket Client when the H5 page is loaded;
and establishing communication connection between the H5 page and the Native terminal according to the WebSocket Server and the WebSocket Client, and taking the second WebView as the target WebView.
Further, when the method call instruction is the H5 method call instruction, the step of obtaining first call data through the Native terminal, sending the first call data to the H5 page through the WebSocket Server and the WebSocket Client, and calling the H5 method according to the first call data through the H5 page in the target WebView includes:
acquiring first data to be packaged, wherein the first data to be packaged comprises: the name of a first H5 method to be called, first transfer data;
packaging the first H5 method name to be called and the first transfer data through the Native terminal to obtain the first calling data;
sending the first calling data to the H5 page through the WebSocket Server and the WebSocket Client;
in the target WebView, analyzing the first calling data through the H5 page to obtain a first target H5 method name;
invoking the H5 method according to the first target H5 method name through the H5 page.
Further, when the method call instruction is the H5 method call instruction, the step of obtaining first call data through the Native terminal, sending the first call data to the H5 page through the WebSocket Server and the WebSocket Client, and calling the H5 method according to the first call data through the H5 page in the target WebView further includes:
acquiring second data to be packaged, wherein the second data to be packaged comprises: the method comprises a second H5 method name to be called, second transfer data and a first callback identifier;
packaging the second H5 method name to be called, the second transfer data and the first return identifier through the Native terminal to obtain second calling data;
sending the second calling data to the H5 page through the WebSocket Server and the WebSocket Client;
in the target WebView, the second calling data is analyzed through the H5 page to obtain a second target H5 method name and a first target return identifier;
calling the H5 method according to the second target H5 method name through the H5 page to obtain a first calling result;
packaging according to the first target return identifier and the first calling result through the H5 page to obtain first return data;
and sending the first return data to the Native terminal through the WebSocket Client and the WebSocket Server.
Further, when the method call instruction is the Native method call instruction, acquiring second call data through the H5 page, and sending the second call data to the Native terminal through the WebSocket Client and the WebSocket Server, where the step of calling a Native method according to the second call data through the Native terminal in the target WebView includes:
acquiring third data to be packaged, wherein the third data to be packaged comprises: the third to-be-called Native method name and the third transfer data;
packaging the third Native method name to be called and the third transfer data through the H5 page to obtain third calling data;
sending the third calling data to the Native terminal through the WebSocket Client and the WebSocket Server;
analyzing the third calling data through the Native terminal to obtain a third target Native method name;
and calling the Native method according to the name of the third target Native method through the Native terminal.
Further, when the method call instruction is the Native method call instruction, acquiring second call data through the H5 page, and sending the second call data to the Native terminal through the WebSocket Client and the WebSocket Server, where the step of calling a Native method according to the second call data through the Native terminal in the target WebView further includes:
acquiring fourth data to be packaged, wherein the fourth data to be packaged comprises: a Native method name to be called, fourth transfer data and a second return identifier;
packaging the fourth Native method name to be called, the fourth transfer data and the second return identifier through the H5 page to obtain fourth calling data;
sending the fourth calling data to the Native terminal through the WebSocket Client and the WebSocket Server;
analyzing the fourth calling data through the Native terminal to obtain a fourth target Native method name and a second target return identifier;
calling the Native method through the Native terminal according to the fourth target Native method name to obtain a second calling result;
packaging according to the second target return identification and the second calling result to obtain second return data;
and sending the second return data to the H5 page through the WebSocket Server and the WebSocket Client through the Native terminal.
Further, the step of obtaining the method call instruction includes:
acquiring a link address;
and analyzing according to the link address through the Native terminal to obtain the method calling instruction.
The application also provides a device for mutual calling between Native and H5, the device is applied to a client, and the client comprises: the Native terminal and the calling plug-in are used for realizing mutual calling between the Native terminal and the H5 page;
the device comprises:
the instruction acquisition module is used for acquiring a method calling instruction, and the method calling instruction comprises the following steps: h5 method call instruction or/and Native method call instruction;
the target WebView creating module is used for responding to the method calling instruction, creating WebView according to the calling plug-in, loading the H5 page, and establishing communication connection between the WebSocket Server and the WebSocket Client to obtain the target WebView;
a method calling module H5, configured to, when the method calling instruction is the H5 method calling instruction, obtain first calling data through the Native terminal, send the first calling data to the H5 page through the WebSocket Server and the WebSocket Client, and call an H5 method according to the first calling data through the H5 page in the target WebView;
and the Native method calling module is used for acquiring second calling data through the H5 page when the method calling instruction is the Native method calling instruction, sending the second calling data to the Native terminal through the WebSocket Client and the WebSocket Server, and calling a Native method according to the second calling data through the Native terminal in the target WebView.
The present application further proposes an electronic device comprising a memory and a processor, the memory storing a computer program, the processor implementing the steps of any of the above methods when executing the computer program.
The present application also proposes a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method of any of the above.
According to the method, the device, the equipment and the medium for calling between the Native and the H5, the calling plug-in is loaded on the client side, the Native end and the H5 page are called mutually through the calling plug-in, the calling plug-in adopts WebSocket Server and WebSocket client based on WebSocket to communicate, and the WebSocket is a general protocol, so that the method, the device, the equipment and the medium have good compatibility; the communication of the Websocket can be completed in a single thread without occupying a Native main thread, and the Websocket supports two-way communication, so that the communication efficiency is improved; compared with a communication mode based on URLSCHEMA, the success rate can not be basically ensured when the large file is transmitted, the Websocket of the application has no limitations, and the Websocket has a set of mechanism to ensure the stability of connection and can completely transmit the information of the large file. Therefore, the method and the device have better compatibility, improve the communication efficiency and can completely transmit the information of the large file.
Drawings
Fig. 1 is a flowchart illustrating a method for inter-invoking between Native and H5 according to an embodiment of the present application;
FIG. 2 is a block diagram illustrating the structure of a device for mutual invocation between Native and H5 according to an embodiment of the present application;
fig. 3 is a block diagram illustrating a structure of an electronic device according to an embodiment of the present application.
The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Technical terms related to the embodiment of the invention include:
the Hybrid App is an App between a Web-App and a Native-App, is a Native App in appearance, but only has a UI WebView, and a Web App is accessed therein.
Native App is a third party application program written and run using Native programs based on the local operating system of the smart device, such as iOS, Android, WP, also called local App. The commonly used development languages are JAVA, C + +, Objective-C.
The Native terminal is based on a local operating system of the intelligent device such as iOS, Android and WP, and uses a Native program to write and run an application program.
H5 is a series of technologies for making interactive effects of web pages, that is, H5 is the web page of the mobile terminal.
The H5 page is also a web page. The H5 page is a page developed by adopting H5, and H5 covers a series of front-end technologies such as HTML5, CSS3 and JavaScript.
WebSocket is a protocol for full duplex communication over a single TCP (transmission control protocol) connection. The WebSocket enables data exchange between the terminal and the server to be simpler, and allows the server to actively push data to the terminal. In the WebSocket API, the browser and the server only need to complete one handshake, and persistent connection can be directly established between the browser and the server for bidirectional data transmission.
WebView, refers to a web page view. WebView can be embedded in a mobile terminal to realize mixed development of a front end, and most mixed development frameworks are secondarily developed based on a WebView mode. Such as: APIcloud, uni-app, etc.
The Remote Procedure Call can provide a termination point mapping program and RPC service by using a Remote computer to send a request program, and is one of three services of a windows system.
Referring to fig. 1, an embodiment of the present application provides a method for inter-invoking between Native and H5, where the method is applied to a client, and the client includes: the Native terminal and the calling plug-in are used for realizing mutual calling between the Native terminal and the H5 page;
the method comprises the following steps:
s1: acquiring a method calling instruction, wherein the method calling instruction comprises the following steps: h5 method call instruction or/and Native method call instruction;
s2: responding to the method calling instruction, creating WebView according to the calling plug-in, loading the H5 page, and establishing communication connection between a Websocket Server and a Websocket Client to obtain a target WebView;
s3: when the method call instruction is the H5 method call instruction, acquiring first call data through the Native terminal, sending the first call data to the H5 page through the WebSocket Server and the WebSocket Client, and calling an H5 method according to the first call data through the H5 page in the target WebView;
s4: and when the method calling instruction is the Native method calling instruction, acquiring second calling data through the H5 page, sending the second calling data to the Native terminal through the WebSocket Client and the WebSocket Server, and calling a Native method according to the second calling data through the Native terminal in the target WebView.
In the embodiment, the calling plug-in is loaded on the client, mutual calling between the Native end and the H5 page is realized by calling the plug-in, the calling plug-in adopts WebSocket Server and WebSocket client based on WebSocket to carry out communication, and the WebSocket is a general protocol, so that the application has better compatibility; the communication of the Websocket can be completed in a single thread without occupying a Native main thread, and the Websocket supports two-way communication, so that the communication efficiency is improved; compared with a communication mode based on URL SCHEMA, the success rate can not be basically ensured when the large file is transmitted, the Websocket of the application has no limitations, and the Websocket has a set of mechanism to ensure the stability of connection and can completely transmit the information of the large file.
The calling plug-in is integrated on the client. The method is used for realizing the Native end call H5 and realizing the H5 page call Native.
Preferably, the calling plug-in is implemented in the form of an SDK.
For step S1, the method call instruction is resolved according to the link address. And determining the method calling instruction according to the method calling parameter.
The H5 method call instruction is an instruction for calling a method of H5. The Native method call instruction is an instruction for calling a Native method.
And S2, responding to the method calling instruction, the client side creates WebView according to the calling plug-in, loads the H5 page, and communicates through a WebSocket Server and a WebSocket client to establish communication connection to obtain the target WebView, namely the target WebView is loaded with the H5 page. It can be understood that when the method call instruction is not acquired, a standard WebView can be created through a standard WebView component of a Native terminal, and the standard WebView cannot call between the Native terminal and the H5 page.
The WebSocket Server is a WebSocket-based Server. The WebSocket Client is a terminal based on WebSocket.
For step S3, packaging data to be called into calling data through the Native terminal, and sending the calling data to the H5 page through the communication connection of the WebSocket Server and the WebSocket Client; the target WebView is loaded with the H5 page, so that the method name of the H5 method to be called can be analyzed from the calling data through the H5 page, and the method name of the analyzed H5 method can be called through the H5 page.
Aiming at the step S4, packaging data to be called into calling data through the H5 page, and sending the calling data to the Native terminal through the communication connection between the WebSocket Client and the WebSocket Server; and resolving the method name of the Native method to be called according to the calling data through the Native terminal, and calling the resolved method name of the Native method by the Native terminal.
The H5 method is referred to as the H5 method. The Native method refers to a Native method.
In one embodiment, the calling plug-in includes: customizing a WebView component, a JS file and a Native SDK, wherein the Native SDK comprises a WebSocket Server code, and the JS file comprises a WebSocket Client code; and the number of the first and second groups,
the steps of creating the WebView according to the calling plug-in, loading the H5 page, and establishing a Websocket Server and Websocket Client communication connection to obtain the target WebView comprise:
s21: calling the customized WebView component through the Native terminal to create a WebView to obtain a first WebView;
s22: loading the WebSocket Server code through the Native terminal, and finishing starting the WebSocket Server when the loading of the WebSocket Server code is finished;
s23: loading the H5 page in the first WebView to obtain a second WebView, injecting the WebSocket Client code in the process of loading the H5 page, and finishing starting the WebSocket Client when the H5 page is loaded;
s24: and establishing communication connection between the H5 page and the Native terminal according to the WebSocket Server and the WebSocket Client, and taking the second WebView as the target WebView.
According to the embodiment, the customized WebView component, the customized JS file and the Native SDK of the calling plug-in are loaded, and a bridge is built for the mutual calling between the Native end and the H5 page.
And step S21, calling the customized WebView component through the Native terminal to create a WebView, and obtaining a first WebView. The first WebView behaves as a browser.
For step S22, the Native end loads the WebSocket Server code for starting the WebSocket Server, and when the loading of the WebSocket Server code is finished, the WebSocket Server is also started successfully.
For step S23, loading the H5 page in the first WebView, and obtaining a second WebView after loading is completed; in addition, in the process of loading the H5 page, the WebSocket Client code needs to be injected into the first WebView for starting the WebSocket Client, and when the loading of the H5 page is finished, the WebSocket Client is successfully started.
And step S24, establishing a communication connection between the WebSocket Server and the WebSocket Client, wherein when the communication connection is successfully established between the WebSocket Server and the WebSocket Client, the communication connection is established between the H5 page and the Native terminal, and the second WebView at the moment is taken as the target WebView.
It is understood that the customized JS file also defines the basic method between the Native end and the H5 page, the basic method including: send, receive, handle. send refers to sending network messages, receive refers to receiving network messages, and handle refers to processing asynchronous messages. Therefore, the terminal realizes the mutual calling between the Native terminal and the H5 page by means of RPC (remote Procedure call).
In an embodiment, the step of obtaining first call data through the Native terminal and sending the first call data to the H5 page through the WebSocket Server and the WebSocket Client when the method call instruction is the H5 method call instruction, where the step of calling the H5 method according to the first call data through the H5 page in the target WebView includes:
s311: acquiring first data to be packaged, wherein the first data to be packaged comprises: the name of a first H5 method to be called, first transfer data;
s312: packaging the first H5 method name to be called and the first transfer data through the Native terminal to obtain the first calling data;
s313: sending the first calling data to the H5 page through the WebSocket Server and the WebSocket Client;
s314: in the target WebView, analyzing the first calling data through the H5 page to obtain a first target H5 method name;
s315: invoking the H5 method according to the first target H5 method name through the H5 page.
The embodiment realizes that the Native terminal calls the H5 method under the condition of not needing returning data.
For step S311, the first to-be-packaged data is obtained through the Native terminal. The first method name to be called H5 is the name of the method for calling the H5 method from the Native terminal. The first transfer data refers to the data which needs to be transferred when the Native terminal calls the H5 method.
For step S312, the first to-be-called H5 method name and the first transfer data are packaged into a network message through the Native terminal, so as to obtain the first call data. That is, the first call data is a network message.
For step S313, the Native terminal sends the first call data to the H5 page through the communication connection between the WebSocket Server and the WebSocket Client. It is understood that the first call data sequentially passes through the WebSocket Server and the WebSocket Client.
For step S314, since the target WebView has already been loaded with the H5 page, the method name of the H5 method to be called may be parsed from the first call data by the H5 page in the target WebView, and the method name of the parsed called H5 method may be referred to as the first target H5 method name.
For step S315, in the target WebView, the first target H5 method name is called through the H5 page, so that the Native end call H5 method is completed.
In an embodiment, the step of obtaining first call data through the Native terminal and sending the first call data to the H5 page through the WebSocket Server and the WebSocket Client when the method call instruction is the H5 method call instruction, and calling the H5 method according to the first call data through the H5 page in the target WebView, further includes:
s321: acquiring second data to be packaged, wherein the second data to be packaged comprises: the method comprises a second H5 method name to be called, second transfer data and a first callback identifier;
s322: packaging the second H5 method name to be called, the second transfer data and the first return identifier through the Native terminal to obtain second calling data;
s323: sending the second calling data to the H5 page through the WebSocket Server and the WebSocket Client;
s324: in the target WebView, the second calling data is analyzed through the H5 page to obtain a second target H5 method name and a first target return identifier;
s325: calling the H5 method according to the second target H5 method name through the H5 page to obtain a first calling result;
s326: packaging according to the first target return identifier and the first calling result through the H5 page to obtain first return data;
s327: and sending the first return data to the Native terminal through the WebSocket Client and the WebSocket Server.
The embodiment realizes that the Native terminal calls the H5 method under the condition of returning data.
For step S321, a second data to be encapsulated is obtained through the Native terminal. The name of the method of the second H5 to be called is the name of the method of the Native terminal calling the H5 method. The second transfer data refers to the data which needs to be transferred when the Native terminal calls the H5 method. The first callback identification is the identification of the H5 page callback Native method after the Native end call H5 method is completed. The first loopback identifier may be an identifier that uniquely identifies a Native terminal, such as an ID number.
For step S322, the Native terminal packages the second H5 method name to be called, the second transfer data, and the first callback identifier into a network message, so as to obtain the second call data. That is, the second call data is a network message.
For step S323, the Native terminal sends the second call data to the H5 page through the communication connection between the WebSocket Server and the WebSocket Client. It is understood that the second call data sequentially passes through the WebSocket Server and the WebSocket Client.
For step S324, since the target WebView has already loaded the H5 page, in the target WebView, the method name and the first backhaul identifier of the H5 method to be called may be parsed from the second call data by the H5 page, the method name of the parsed called H5 method may be used as the second target H5 method name, and the parsed first backhaul identifier may be used as the first target backhaul identifier.
For step S325, in the target WebView, the second target H5 method name is called through the H5 page, and the calling result is used as the first calling result, so that the Native terminal calls the H5 method.
For step S326, the first target backhaul identifier and the first invocation result are packaged into a network message through the H5 page, so as to obtain the first backhaul data. That is, the first backhaul data is a network message.
For step S327, the H5 page sends the first return data to the Native terminal through the communication connection between the WebSocket Client and the WebSocket Server. It is understood that the first loopback data sequentially passes through the WebSocket Client and the WebSocket Server.
It can be understood that the Native terminal parses the first echo data to obtain a method name of a Native method, and then calls the parsed method name of the Native method, thereby completing the loop call between the Native terminal and the H5 page.
In an embodiment, the step of obtaining second call data through the H5 page and sending the second call data to the Native terminal through the WebSocket Client and the WebSocket Server when the method call instruction is the Native method call instruction, where the step of calling the Native method according to the second call data through the Native terminal in the target WebView includes:
s411: acquiring third data to be packaged, wherein the third data to be packaged comprises: the third to-be-called Native method name and the third transfer data;
s412: packaging the third Native method name to be called and the third transfer data through the H5 page to obtain third calling data;
s413: sending the third calling data to the Native terminal through the WebSocket Client and the WebSocket Server;
s414: analyzing the third calling data through the Native terminal to obtain a third target Native method name;
s415: and calling the Native method according to the name of the third target Native method through the Native terminal.
The embodiment realizes that the Native method is called by the H5 page under the condition that the data is not required to be returned.
For step S411, the third data to be packaged is obtained through the H5 page. The third Native method name to be called is the method name of the H5 page calling the Native method. The third transfer data refers to the data which needs to be transferred when the H5 page calls the Native method.
For step S412, the Native method name to be called and the third transfer data are packaged into a network message through the H5 page, so as to obtain the third transfer data. That is, the third call data is a network message.
For step S413, the H5 page sends the third call data to the Native terminal through the communication connection between the WebSocket Client and the WebSocket Server. It is understood that the third call data sequentially passes through the WebSocket Client and the WebSocket Server.
In step S414, the method name of the Native method to be called is parsed from the third call data by the Native terminal, and the parsed method name of the Native method to be called is referred to as a third target Native method name.
For step S415, the third target Native method name is then called by the Native terminal, thereby completing the H5 page calling Native method.
In an embodiment, the step of obtaining second call data through the H5 page and sending the second call data to the Native terminal through the WebSocket Client and the WebSocket Server when the method call instruction is the Native method call instruction, where the step of calling a Native method according to the second call data through the Native terminal in the target WebView further includes:
s421: acquiring fourth data to be packaged, wherein the fourth data to be packaged comprises: a Native method name to be called, fourth transfer data and a second return identifier;
s422: packaging the fourth Native method name to be called, the fourth transfer data and the second return identifier through the H5 page to obtain fourth calling data;
s423: sending the fourth calling data to the Native terminal through the WebSocket Client and the WebSocket Server;
s424: analyzing the fourth calling data through the Native terminal to obtain a fourth target Native method name and a second target return identifier;
s425: calling the Native method through the Native terminal according to the fourth target Native method name to obtain a second calling result;
s426: packaging according to the second target return identification and the second calling result to obtain second return data;
s427: and sending the second return data to the H5 page through the WebSocket Server and the WebSocket Client through the Native terminal.
The embodiment realizes that the Native method is called by the H5 page under the condition that the data needs to be returned.
For step S421, fourth data to be packaged is obtained through the H5 page. The fourth Native method name to be called is the method name of the H5 page calling the Native method. The fourth transfer data refers to the data which needs to be transferred when the H5 page calls the Native method. The second passback identification is the identification of the Native-side callback H5 method after the H5 page calls Native methods. The second backhaul identification may be an identification such as an ID number that uniquely identifies one of the H5 pages.
For step S422, the fourth Native method name to be called, the fourth transfer data, and the second return identifier are packaged into a network message through the H5 page, so as to obtain the fourth transfer data. That is, the fourth call data is a network message.
For step S423, the H5 page sends the fourth call data to the Native terminal through the communication connection between the WebSocket Client and the WebSocket server. It is to be understood that the fourth call data sequentially passes through the WebSocket Client and the WebSocket server.
In step S424, the method name of the Native method to be called and the second backhaul identifier are resolved by the Native terminal according to the fourth calling data, the resolved method name of the Native method to be called is taken as the fourth target Native method name, and the resolved second backhaul identifier is taken as the second target backhaul identifier.
In step S425, the Native terminal calls the fourth target Native method name, and the calling result is used as the second calling result, thereby completing the calling of the Native method by the H5 page.
For step S426, the Native terminal packages the second target backhaul identifier and the second invocation result into a network message, so as to obtain the second backhaul data. That is, the second backhaul data is a network message.
For step S427, the Native terminal sends the second backhaul data to the H5 page through the communication connection between the WebSocket Server and the WebSocket Client. It can be understood that the second backhaul data sequentially passes through the WebSocket Server and the WebSocket Client.
It can be understood that the H5 page parses the second backhaul data to obtain the method name of the H5 method, and then calls the parsed method name of the H5 method, thereby completing the loop call between the H5 page and the Native terminal.
In an embodiment, the step of obtaining the method call instruction includes:
s11: acquiring a link address;
s12: and analyzing according to the link address through the Native terminal to obtain the method calling instruction.
The method and the device realize that the method call instruction is determined according to the link address, and mutual call between Native and H5 is realized by adopting the method and the device.
For step S12, when the method call parameter is resolved from the link address, the method call instruction is generated from the method call parameter.
Preferably, when the method calling parameters cannot be analyzed from the link address, the WebView can be created without calling a plug-in, and only the standard WebView component carried by the Native terminal is needed to create the standard WebView.
Referring to fig. 2, in an embodiment of the present application, a device for invoking each other between Native and H5 is further provided, where the device is applied to a client, and the client includes: the Native terminal and the calling plug-in are used for realizing mutual calling between the Native terminal and the H5 page;
the device comprises:
an instruction obtaining module 100, configured to obtain a method call instruction, where the method call instruction includes: h5 method call instruction or/and Native method call instruction;
the target WebView creating module 200 is used for responding to the method calling instruction, creating WebView according to the calling plug-in, loading the H5 page, and establishing communication connection between a WebSocket Server and a WebSocket Client to obtain the target WebView;
a method calling module 300 of H5, configured to, when the method calling instruction is the H5 method calling instruction, obtain first calling data through the Native terminal, send the first calling data to the H5 page through the WebSocket Server and the WebSocket Client, and call an H5 method according to the first calling data through the H5 page in the target WebView;
a Native method calling module 400, configured to, when the method call instruction is the Native method call instruction, obtain second call data through the H5 page, send the second call data to the Native terminal through the WebSocket Client and the WebSocket Server, and call a Native method according to the second call data through the Native terminal in the target WebView.
In the embodiment, the calling plug-in is loaded on the client, mutual calling between the Native end and the H5 page is realized by calling the plug-in, the calling plug-in adopts WebSocket Server and WebSocket client based on WebSocket to carry out communication, and the WebSocket is a general protocol, so that the application has better compatibility; the communication of the Websocket can be completed in a single thread without occupying a Native main thread, and the Websocket supports two-way communication, so that the communication efficiency is improved; compared with a communication mode based on URL SCHEMA, the success rate can not be basically ensured when the large file is transmitted, the Websocket of the application has no limitations, and the Websocket has a set of mechanism to ensure the stability of connection and can completely transmit the information of the large file.
Referring to fig. 3, an electronic device, which may be a server and whose internal structure may be as shown in fig. 3, is also provided in the embodiment of the present application. The electronic device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the computer designed processor is used to provide computational and control capabilities. The memory of the electronic equipment comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the electronic equipment is used for data such as a method called by Native and H5. The network interface of the electronic device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a method of inter-calling between Native and H5. The method for mutual calling between Native and H5 is applied to a client, and the client comprises: the Native terminal and the calling plug-in are used for realizing mutual calling between the Native terminal and the H5 page; the method comprises the following steps: acquiring a method calling instruction, wherein the method calling instruction comprises the following steps: h5 method call instruction or/and Native method call instruction; responding to the method calling instruction, creating WebView according to the calling plug-in, loading the H5 page, and establishing communication connection to obtain a target WebView; when the method call instruction is the H5 method call instruction, acquiring first call data through the Native terminal, sending the first call data to the H5 page through a WebSocket Server and a WebSocket Client, and calling an H5 method according to the first call data through the H5 page in the target WebView; and when the method calling instruction is the Native method calling instruction, acquiring second calling data through the H5 page, sending the second calling data to the Native terminal through the WebSocket Client and the WebSocket Server, and calling a Native method according to the second calling data through the Native terminal in the target WebView.
According to the executed method for inter-calling between Native and H5, the plug-in is loaded at the client, the inter-calling between the Native and H5 pages is realized by calling the plug-in, the calling plug-in adopts WebSocket Server and WebSocket client based on WebSocket to communicate, and the WebSocket is a general protocol, so that the method has good compatibility; the communication of the Websocket can be completed in a single thread without occupying a Native main thread, and the Websocket supports two-way communication, so that the communication efficiency is improved; compared with a communication mode based on URL SCHEMA, the success rate can not be basically ensured when the large file is transmitted, the Websocket of the application has no limitations, and the Websocket has a set of mechanism to ensure the stability of connection and can completely transmit the information of the large file.
An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements a method for mutual invocation between Native and H5, the method is applied to a client, and the client includes: the Native terminal and the calling plug-in are used for realizing mutual calling between the Native terminal and the H5 page; the method comprises the following steps: acquiring a method calling instruction, wherein the method calling instruction comprises the following steps: h5 method call instruction or/and Native method call instruction; responding to the method calling instruction, creating WebView according to the calling plug-in, loading the H5 page, and establishing communication connection to obtain a target WebView; when the method call instruction is the H5 method call instruction, acquiring first call data through the Native terminal, sending the first call data to the H5 page through a WebSocket Server and a WebSocket Client, and calling an H5 method according to the first call data through the H5 page in the target WebView; and when the method calling instruction is the Native method calling instruction, acquiring second calling data through the H5 page, sending the second calling data to the Native terminal through the WebSocket Client and the WebSocket Server, and calling a Native method according to the second calling data through the Native terminal in the target WebView.
According to the executed method for inter-calling between Native and H5, the plug-in is loaded at the client, the inter-calling between the Native and H5 pages is realized by calling the plug-in, the calling plug-in adopts WebSocket Server and WebSocket client based on WebSocket to communicate, and the WebSocket is a general protocol, so that the method has good compatibility; the communication of the Websocket can be completed in a single thread without occupying a Native main thread, and the Websocket supports two-way communication, so that the communication efficiency is improved; compared with a communication mode based on URL SCHEMA, the success rate can not be basically ensured when the large file is transmitted, the Websocket of the application has no limitations, and the Websocket has a set of mechanism to ensure the stability of connection and can completely transmit the information of the large file.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium provided herein and used in the examples may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double-rate SDRAM (SSRSDRAM), Enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and bus dynamic RAM (RDRAM).
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A method for mutual calling between Native and H5, wherein the method is applied to a client, and the client comprises: the Native terminal and the calling plug-in are used for realizing mutual calling between the Native terminal and the H5 page;
the method comprises the following steps:
acquiring a method calling instruction, wherein the method calling instruction comprises the following steps: h5 method call instruction or/and Native method call instruction;
responding to the method calling instruction, creating WebView according to the calling plug-in, loading the H5 page, and establishing communication connection between a Websocket Server and a Websocket Client to obtain a target WebView;
when the method call instruction is the H5 method call instruction, acquiring first call data through the Native terminal, sending the first call data to the H5 page through the WebSocket Server and the WebSocket Client, and calling an H5 method according to the first call data through the H5 page in the target WebView;
and when the method calling instruction is the Native method calling instruction, acquiring second calling data through the H5 page, sending the second calling data to the Native terminal through the WebSocket Client and the WebSocket Server, and calling a Native method according to the second calling data through the Native terminal in the target WebView.
2. The method for mutual invocation between Native and H5 according to claim 1, wherein said invocation plugin comprises: customizing a WebView component, a JS file and a Native SDK, wherein the Native SDK comprises a WebSocket Server code, and the JS file comprises a WebSocket Client code; and the number of the first and second groups,
the steps of creating WebView according to the calling plug-in, loading the H5 page, and establishing a WebSocket Server and WebSocket Client communication connection to obtain the target WebView comprise:
calling the customized WebView component through the Native terminal to create a WebView to obtain a first WebView;
loading the WebSocket Server code through the Native terminal, and finishing starting the WebSocket Server when the loading of the WebSocket Server code is finished;
loading the H5 page in the first WebView to obtain a second WebView, injecting the WebSocket Client code in the process of loading the H5 page, and finishing starting the WebSocket Client when the H5 page is loaded;
and establishing communication connection between the H5 page and the Native terminal according to the WebSocket Server and the WebSocket Client, and taking the second WebView as the target WebView.
3. The method for inter-calling between Native and H5 according to claim 1, wherein when the method call command is the H5 method call command, the method obtains first call data through the Native terminal, sends the first call data to the H5 page through the WebSocket Server and the WebSocket Client, and in the target WebView, the step of calling the H5 method according to the first call data through the H5 page includes:
acquiring first data to be packaged, wherein the first data to be packaged comprises: the name of a first H5 method to be called, first transfer data;
packaging the first H5 method name to be called and the first transfer data through the Native terminal to obtain the first calling data;
sending the first calling data to the H5 page through the WebSocket Server and the WebSocket Client;
in the target WebView, analyzing the first calling data through the H5 page to obtain a first target H5 method name;
invoking the H5 method according to the first target H5 method name through the H5 page.
4. The method for inter-calling between Native and H5 according to claim 1, wherein when the method call command is the H5 method call command, the method further comprises the steps of obtaining first call data through the Native terminal, sending the first call data to the H5 page through the WebSocket Server and the WebSocket Client, and in the target WebView, calling an H5 method according to the first call data through the H5 page:
acquiring second data to be packaged, wherein the second data to be packaged comprises: the method comprises a second H5 method name to be called, second transfer data and a first callback identifier;
packaging the second H5 method name to be called, the second transfer data and the first return identifier through the Native terminal to obtain second calling data;
sending the second calling data to the H5 page through the WebSocket Server and the WebSocket Client;
in the target WebView, the second calling data is analyzed through the H5 page to obtain a second target H5 method name and a first target return identifier;
calling the H5 method according to the second target H5 method name through the H5 page to obtain a first calling result;
packaging according to the first target return identifier and the first calling result through the H5 page to obtain first return data;
and sending the first return data to the Native terminal through the WebSocket Client and the WebSocket Server.
5. The method for mutual calling between Native and H5 according to claim 1, wherein when the method call command is the Native method call command, obtaining second call data through the H5 page, sending the second call data to the Native terminal through the WebSocket Client and the WebSocket Server, and in the target WebView, calling a Native method according to the second call data through the Native terminal includes:
acquiring third data to be packaged, wherein the third data to be packaged comprises: the third to-be-called Native method name and the third transfer data;
packaging the third Native method name to be called and the third transfer data through the H5 page to obtain third calling data;
sending the third calling data to the Native terminal through the WebSocket Client and the WebSocket Server;
analyzing the third calling data through the Native terminal to obtain a third target Native method name;
and calling the Native method according to the name of the third target Native method through the Native terminal.
6. The method for mutual calling between Native and H5 according to claim 1, wherein when the method call command is the Native method call command, obtaining second call data through the H5 page, sending the second call data to the Native end through the WebSocket Client and the WebSocket Server, and in the target WebView, calling a Native method according to the second call data through the Native end further includes:
acquiring fourth data to be packaged, wherein the fourth data to be packaged comprises: a Native method name to be called, fourth transfer data and a second return identifier;
packaging the fourth Native method name to be called, the fourth transfer data and the second return identifier through the H5 page to obtain fourth calling data;
sending the fourth calling data to the Native terminal through the WebSocket Client and the WebSocket Server;
analyzing the fourth calling data through the Native terminal to obtain a fourth target Native method name and a second target return identifier;
calling the Native method through the Native terminal according to the fourth target Native method name to obtain a second calling result;
packaging according to the second target return identification and the second calling result to obtain second return data;
and sending the second return data to the H5 page through the WebSocket Server and the WebSocket Client through the Native terminal.
7. The method for mutual invocation between Native and H5 according to claim 1, wherein the step of obtaining the method invocation instruction includes:
acquiring a link address;
and analyzing according to the link address through the Native terminal to obtain the method calling instruction.
8. An apparatus for mutual calling between Native and H5, wherein the apparatus is applied to a client, and the client comprises: the Native terminal and the calling plug-in are used for realizing mutual calling between the Native terminal and the H5 page;
the device comprises:
the instruction acquisition module is used for acquiring a method calling instruction, and the method calling instruction comprises the following steps: h5 method call instruction or/and Native method call instruction;
the target WebView creating module is used for responding to the method calling instruction, creating WebView according to the calling plug-in, loading the H5 page, and establishing communication connection between the WebSocket Server and the WebSocket Client to obtain the target WebView;
a method calling module H5, configured to, when the method calling instruction is the H5 method calling instruction, obtain first calling data through the Native terminal, send the first calling data to the H5 page through the WebSocket Server and the WebSocket Client, and call an H5 method according to the first calling data through the H5 page in the target WebView;
and the Native method calling module is used for acquiring second calling data through the H5 page when the method calling instruction is the Native method calling instruction, sending the second calling data to the Native terminal through the WebSocket Client and the WebSocket Server, and calling a Native method according to the second calling data through the Native terminal in the target WebView.
9. An electronic device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010889805.1A CN112015495B (en) | 2020-08-28 | 2020-08-28 | Method, device, equipment and medium for mutual calling between Native and H5 |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010889805.1A CN112015495B (en) | 2020-08-28 | 2020-08-28 | Method, device, equipment and medium for mutual calling between Native and H5 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112015495A true CN112015495A (en) | 2020-12-01 |
| CN112015495B CN112015495B (en) | 2022-09-23 |
Family
ID=73502476
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010889805.1A Active CN112015495B (en) | 2020-08-28 | 2020-08-28 | Method, device, equipment and medium for mutual calling between Native and H5 |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112015495B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988418A (en) * | 2021-03-05 | 2021-06-18 | 杭州天阙科技有限公司 | Communication method of Web end and mobile end, mobile terminal and system |
| CN113360406A (en) * | 2021-07-01 | 2021-09-07 | 上海哔哩哔哩科技有限公司 | Method and device for testing JSbridge method of application program |
| CN114117285A (en) * | 2022-01-27 | 2022-03-01 | 浙江口碑网络技术有限公司 | Position information processing method and device based on H5 page and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9037735B1 (en) * | 2013-03-15 | 2015-05-19 | Kaazing Corporation | Establishing websocket protocol extensions |
| CN110191169A (en) * | 2019-05-24 | 2019-08-30 | 腾讯音乐娱乐科技（深圳）有限公司 | Data processing method and device |
| CN110290055A (en) * | 2019-06-25 | 2019-09-27 | 携程计算机技术（上海）有限公司 | The communication means and system of wechat small routine WebView and primary component |
| CN110691136A (en) * | 2019-09-29 | 2020-01-14 | 广州华多网络科技有限公司 | Data interaction method and device, electronic equipment and storage medium |
-
2020
- 2020-08-28 CN CN202010889805.1A patent/CN112015495B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9037735B1 (en) * | 2013-03-15 | 2015-05-19 | Kaazing Corporation | Establishing websocket protocol extensions |
| CN110191169A (en) * | 2019-05-24 | 2019-08-30 | 腾讯音乐娱乐科技（深圳）有限公司 | Data processing method and device |
| CN110290055A (en) * | 2019-06-25 | 2019-09-27 | 携程计算机技术（上海）有限公司 | The communication means and system of wechat small routine WebView and primary component |
| CN110691136A (en) * | 2019-09-29 | 2020-01-14 | 广州华多网络科技有限公司 | Data interaction method and device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 范伊红等: "高校JavaScript程序设计课程体系建设探究", 《电脑知识与技术》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988418A (en) * | 2021-03-05 | 2021-06-18 | 杭州天阙科技有限公司 | Communication method of Web end and mobile end, mobile terminal and system |
| CN113360406A (en) * | 2021-07-01 | 2021-09-07 | 上海哔哩哔哩科技有限公司 | Method and device for testing JSbridge method of application program |
| CN114117285A (en) * | 2022-01-27 | 2022-03-01 | 浙江口碑网络技术有限公司 | Position information processing method and device based on H5 page and electronic equipment |
| CN114117285B (en) * | 2022-01-27 | 2022-05-31 | 浙江口碑网络技术有限公司 | Position information processing method and device based on H5 page and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112015495B (en) | 2022-09-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112015495B (en) | Method, device, equipment and medium for mutual calling between Native and H5 | |
| CN107870821B (en) | Cross-platform calling method and system for application program | |
| US8745187B2 (en) | System and method for installing smart card applet | |
| US9602329B1 (en) | Dynamic remote procedure call | |
| US10817350B2 (en) | Method and device for starting external application program in browser | |
| CN106878460B (en) | Communication processing method and device | |
| CA2332283A1 (en) | Method for accessing an object using a "web" browser cooperating with a smart card, and architecture for implementing the method | |
| JP2015531952A (en) | Offline caching method and apparatus | |
| CN104821954A (en) | Cross-platform remote procedure call method | |
| US8966108B2 (en) | Portable data carrier comprising a CAT interpreter | |
| CN112068818A (en) | Service interaction method and device, computer equipment and storage medium | |
| CN112954629A (en) | Method and system for updating eSIM (embedded subscriber identity Module) device through network access, eSIM device and storage medium | |
| CN105786476B (en) | Data processing method and system between mobile client and server | |
| CN105677688B (en) | Page data loading method and system | |
| CN112468611B (en) | Application program starting method, terminal equipment and computer storage medium | |
| CN109725887A (en) | Data interactive method, device and terminal device based on message research and development frame | |
| CN113065079B (en) | Method, equipment and storage medium for realizing calling of native page based on address protocol | |
| CN109614188B (en) | Page online help method and device, computer equipment and storage medium | |
| WO2009153205A1 (en) | Method of generating a document from a web server located in a portable electronic device | |
| CN111078429A (en) | Method for calling local input method of web browser by cloud mobile phone | |
| US20020062340A1 (en) | System for modifying a web page | |
| CN112714148A (en) | Interface configuration method, device, equipment and medium | |
| CN106850756B (en) | Method and system for realizing communication between web page and local application | |
| CN106775768B (en) | Native code calling system and method and APP hybrid development system | |
| CN114238811B (en) | Page loading method, page request response method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210201 Address after: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant after: Shenzhen saiante Technology Service Co.,Ltd. Address before: 1-34 / F, Qianhai free trade building, 3048 Xinghai Avenue, Mawan, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong 518000 Applicant before: Ping An International Smart City Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |