CN112995252B

CN112995252B - Method, device, equipment and storage medium for data transmission between page terminal and client terminal

Info

Publication number: CN112995252B
Application number: CN201911283655.3A
Authority: CN
Inventors: 王晓振
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-12-13
Filing date: 2019-12-13
Publication date: 2023-08-08
Anticipated expiration: 2039-12-13
Also published as: CN112995252A

Abstract

A data transmission method, device, equipment and storage medium between page end and client are disclosed. The page terminal is a page program running in the client terminal, and calls a registration interface to send a registration request for establishing a data transmission channel between the page terminal and the client terminal to the client terminal; receiving a registration result sent by a client, wherein the registration result is used for representing whether the data transmission channel is successfully registered; under the condition that the data transmission channel is successfully registered, the data transmission between the page end and the client end is realized by utilizing the data transmission channel. The data transmission channel between the page end and the client can be established by taking the page end as a unit, so that support is provided for data transmission between the page end and the client.

Description

Method, device, equipment and storage medium for data transmission between page terminal and client terminal

Technical Field

The present disclosure relates to the field of computers, and in particular, to a method, an apparatus, a device, and a storage medium for implementing data transmission between a page end and a client.

Background

The hybrid development technology of 'native+page' is utilized, and the development of application programs is becoming a mainstream. Applications developed based on this hybrid development technique include clients and pagers. The client refers to a client application installed and running in the device; the page end refers to a web page program running in the client.

In an actual business scenario, data needs to be transmitted between a page end and a client end frequently, and data transmission between the page end and the client end is mainly realized by using a Jsbridge at present. Briefly, a client injects a section of JavaScript code, and after the injected code is called by a page, data is transferred to the client in a String format.

There is no scheme for receiving data from a client in real time at the page end (injection of JavaScript code does not support sendEvent). That is, if the client sends a large piece of data to the page, a very tortuous manner is required for the page to receive the data in real time.

In addition, the use of String for large data transfers is actually a very bad solution, since String transfers are made over multiple copies before being transferred to the page end. The multiple copies Of data have not only a loss in performance, but most importantly occupy a large amount Of Memory, which easily causes the problem Of OOM (Out Of Memory, memory is not used enough).

Therefore, a more reasonable data transmission scheme is needed to achieve data transmission between the client and the page.

Disclosure of Invention

It is an object of the present disclosure to provide a data transmission scheme capable of providing technical support for data transmission between a client and a peer.

According to a first aspect of the present disclosure, there is provided a method for implementing data transmission between a page end and a client, the page end being a page program running in the client, the method comprising: the page terminal calls a registration interface to send a registration request for establishing a data transmission channel between the page terminal and the client terminal to the client terminal; receiving a registration result sent by a client, wherein the registration result is used for representing whether the data transmission channel is successfully registered; and under the condition that the registration of the data transmission channel is successful, the data transmission between the page end and the client end is realized by utilizing the data transmission channel.

Optionally, the registration request includes a token for characterizing the identity of the page end.

Optionally, in the case that the registration of the data transmission channel is successful, the registration result includes an object for characterizing the data transmission channel, where the object has one or more function interfaces, and the page end realizes data transmission with the client by calling the function interfaces.

Optionally, the functional interface includes a detection interface, and the page call detection interface detects a message sent by the client.

Optionally, the message comprises at least one of: a first message for characterizing data sent by the client; a second message for characterizing a state of the client; and a third message for characterizing the operation instruction sent by the client.

Optionally, the function interface further includes a data acquisition interface, and the page calls the data acquisition interface to acquire the data sent by the client in response to the detection interface detecting the first message for characterizing the data sent by the client.

Optionally, the function interface includes a data sending interface, and the step of using the data transmission channel to realize data transmission between the page end and the client end includes: the page terminal calls a data sending interface to send data to the client terminal.

Optionally, the function interface includes an instruction sending interface, and the step of using the data transmission channel to realize data transmission between the page end and the client end includes: the page call instruction sending interface sends a first operation instruction to the client, wherein the first operation instruction is used for representing an operation which the client needs to execute for data sent by the page.

Optionally, the method further comprises: the page call closes the interface to close the data transmission channel between the page and the client.

Optionally, the data transmitted between the page end and the client comprises text data and/or image data.

According to a second aspect of the present disclosure, there is also provided a method for implementing data transmission between a page end and a client, the page end being a page program running in the client, the method comprising: responding to a registration request which is sent by a page end and is expected to establish a data transmission channel between the page end and a client end, and judging whether the establishment of the data transmission channel is allowed or not by the client end; sending a registration result used for representing whether the data transmission channel is successfully registered to the page end; and under the condition that the registration of the data transmission channel is successful, the data transmission between the page end and the client end is realized by utilizing the data transmission channel.

Optionally, the registration request includes a token for characterizing an identity of the page, and the step of the client determining whether to allow establishment of the data transmission channel includes: the client judges whether to allow the establishment of the data transmission channel by detecting the validity of the token.

Optionally, the method further comprises: in the case of allowing the establishment of a data transmission channel, an object for characterizing the data transmission channel is generated, wherein the object has one or more functional interfaces and the registration result comprises the object.

Optionally, the functional interface comprises at least one of: the detection interface is used for detecting the message sent by the client; the data acquisition interface is used for acquiring data sent by the client; the data sending interface is used for sending data to the client; the instruction sending interface is used for sending a first operation instruction to the client, wherein the first operation instruction is used for representing an operation which the client needs to execute for data sent by the page.

Optionally, the method further comprises: the detector is arranged to trigger a method corresponding to the predetermined interface in response to the predetermined interface being invoked by the page end.

Optionally, the predetermined interface is a registration interface, a method corresponding to the predetermined interface is a registration processing method, the client calls the registration interface to send a registration request in response to the page, calls the registration processing method to obtain the registration request, judges whether to allow establishment of a data transmission channel, and returns a registration result to the page.

Optionally, the predetermined interface is a data sending interface, the method corresponding to the predetermined interface is a data receiving method, and the step of using the data transmission channel to realize data transmission between the page end and the client end includes: and responding to the page end call data transmission interface to transmit data, and calling a data receiving method by the client end to acquire the data.

Optionally, the client receives the data from other page ends after receiving the data, and/or the client sends the data to the page ends after receiving the data.

Optionally, the method corresponding to the predetermined interface further includes an identification method, and the step of implementing data transmission between the page end and the client by using the data transmission channel further includes: and responding to the page terminal to call the data sending interface to send data, calling an identification method by the client terminal to identify the identity of the page terminal sending the data, and returning a message whether to receive the data or not to the page terminal.

Optionally, the predetermined interface is an instruction sending interface, the method corresponding to the predetermined interface is an instruction processing method, and the step of using the data transmission channel to realize data transmission between the page end and the client end includes: and responding to the page terminal call instruction sending interface to send a first operation instruction, and the client terminal call instruction processing method obtains the first operation instruction and processes the received data sent by the page terminal according to the operation represented by the first operation instruction.

Optionally, the predetermined interface is a closing interface, a method corresponding to the predetermined interface is a closing method, the page end calls the closing interface to close the data transmission channel, and the client end calls the closing method to close the data transmission channel.

Optionally, the step of using the data transmission channel to realize data transmission between the page end and the client end includes: and sending a message to the page end by using the data transmission channel.

Optionally, the step of sending the message to the page using the data transmission channel includes: calling a data transmission method to transmit data to a data transmission channel corresponding to the page end; and/or calling an instruction sending method to send a second operation instruction to a data transmission channel corresponding to the page end, wherein the second operation instruction is used for characterizing the operation which needs to be executed by the page end for the data sent by the client.

Optionally, the client is a client application running based on a browser kernel, and the method for realizing data transmission between the page end and the client is executed by the browser kernel.

According to a third aspect of the present disclosure, there is also provided an apparatus for implementing data transmission between a page end and a client, the page end being a page program running in the client, the apparatus comprising: the registration interface calling module is used for calling the registration interface to send a registration request for establishing a data transmission channel between the page end and the client end to the client end; the receiving module is used for receiving a registration result sent by the client, wherein the registration result is used for representing whether the data transmission channel is successfully registered; and the data transmission module is used for realizing data transmission between the page end and the client end by utilizing the data transmission channel under the condition that the data transmission channel is successfully registered.

According to a fourth aspect of the present disclosure, there is also provided an apparatus for implementing data transmission between a page end and a client, the page end being a page program running in the client, the apparatus comprising: the judging module is used for judging whether the data transmission channel is allowed to be established or not in response to receiving a registration request which is sent by the page end and is expected to establish the data transmission channel between the page end and the client; the sending module is used for sending a registration result used for representing whether the data transmission channel is successfully registered to the page end; and the data transmission module is used for realizing data transmission between the page end and the client end by utilizing the data transmission channel under the condition that the data transmission channel is successfully registered.

According to a fifth aspect of the present disclosure, there is also presented a computing device comprising: a processor; and a memory having executable code stored thereon which, when executed by the processor, causes the processor to perform the method as described in the first or second aspect of the present disclosure.

According to a fifth aspect of the present disclosure, there is also provided a non-transitory machine-readable storage medium having stored thereon executable code which, when executed by a processor of an electronic device, causes the processor to perform a method as set forth in the first or second aspect of the present disclosure.

The scheme is suitable for transmitting data between the client and the page, and based on the scheme, a data transmission channel between the page and the client can be established by taking the page as a unit, so that support is provided for data transmission between the page and the client.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following more particular descriptions of exemplary embodiments of the disclosure as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts throughout exemplary embodiments of the disclosure.

FIG. 1 illustrates an architectural diagram of an application according to one embodiment of the present disclosure.

Fig. 2 shows a schematic flow chart of a method for enabling data transfer between a page end and a client according to one embodiment of the present disclosure.

FIG. 3 illustrates a schematic view of a running interface of a first application.

Fig. 4 shows a schematic structural diagram of an apparatus for implementing data transmission between a page end and a client according to an embodiment of the present disclosure.

Fig. 5 illustrates a schematic structural diagram of an apparatus for implementing data transmission between a page end and a client according to another embodiment of the present disclosure.

Fig. 6 shows a schematic structural diagram of a computing device according to an embodiment of the present disclosure.

Detailed Description

Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

The scheme is mainly used for transmitting data between the client and the page in the application program and can realize efficient data transmission between the client and the page based on the scheme.

A client refers to a client application installed and running in a device, more specifically a native part of the application; a page end refers to a page program running in a client, and may refer to a web page program embedded in a client, for example.

Taking an application running in an android operating system environment as an example, a client may refer to a client application developed based on android webview that can run on an android platform. AndroidWebView is an android component, and applications developed based on such components can expose an interface to Web pages. The page end refers to a web page program running in an application running on the android platform.

The page end may be designed as a web page program for implementing a specific function. The page end can be an indispensable component in the application program, namely the page end and the client end together form a complete application program; the page end may also be an optional part of the application, i.e. the client may be a stand-alone application, the page end may be regarded as an optional functional plug-in embedded in the client, and the page end and the client may be developed by different developers.

As shown in fig. 1, the application program is the client described above. The application may be any APP developed based on a browser kernel. One or more web programs may be embedded in the application program, such as may include, but not limited to, web program a, web program B, and web program C shown in fig. 1. The web page program a, the web page program B, and the web page program C may run in the application program based on the browser kernel.

Fig. 2 shows a schematic flow chart of a method for enabling data transfer between a page end (web page program) and a client (application program) according to one embodiment of the disclosure.

As shown in fig. 2, the page may perform step S110, call the registration interface to send a registration request to the client. The registration request is used to characterize that the client desires to establish a data transmission channel with the client.

The registration request may include a token (token) for characterizing the identity of the page, where the token may be pre-agreed by the page and the client, and the disclosure of the content and the specific generation process of the token will not be repeated.

In response to receiving the registration request sent by the page, the client executes step S210 to determine whether to allow establishment of the data transmission channel. Whether the data transmission channel is allowed to be established or not is judged, namely whether the page terminal is allowed to send data to the client terminal or not is judged, and the client terminal is received to send data.

As an example, the registration request includes a token for characterizing the identity of the page, and the client can determine whether to allow the establishment of the data transmission channel by detecting the validity of the token. The validity detection referred to herein may refer to detecting whether the token is pre-agreed upon by the client and the page to determine whether the identity of the page is valid.

The client may further perform step S220, where a registration result for indicating whether the data transmission channel is successfully registered is sent to the page.

Under the condition that the data transmission channel is successfully registered, the data transmission between the page end and the client end can be realized by utilizing the data transmission channel. That is, the client and the page end can execute step S230, and data transmission between the client and the page end is realized by using the data transmission channel.

The data transmission channel is a channel established in units of page ends for realizing data transmission between the page ends and the clients. In this disclosure, a data transmission channel may be considered an object in the programming arts, which may have one or more functional interfaces for implementing a particular function. Under the condition that the registration of the data transmission channel is successful, the page end can realize the data transmission with the client end by calling a specific functional interface.

For example, an object for characterizing a data transmission channel may be named a channel object, and a functional interface that a channel object has may include, but is not limited to, a detection interface (may be named a channel. Addeventlist), a data acquisition interface (may be named a channel. Fetchdata), a data transmission interface (may be named a channel. Senddata), and an instruction transmission interface (may be named a channel. Sendoption).

In case it is decided that the establishment of the data transmission channel is allowed, an object (i.e. the channel object mentioned above) for characterizing the data transmission channel may be generated (i.e. created) by the client.

The channel object may also be included in the registration result sent by the client to the peer in the case of allowing the establishment of the data transmission channel. Therefore, under the condition that the registration of the data transmission channel is successful, the page end can realize the data transmission with the client end by calling the functional interface in the channel object.

Further exemplary operations that may be performed by the client and the page, respectively, during data transfer are described below.

1. Page end

The browser kernel can provide a registration interface and a closing interface of the data transmission channel for the page end, so that the page end can realize the establishment or closing of the data transmission channel by calling the corresponding interfaces.

As an example, a window. Xxdata object may be added by the browser kernel, which may include a registration interface, which may be named window. Xxdata. Region (), and a closure interface, which may be named window. Ucdata. Region (token).

1.1 registration interface window. Xxdata. Region ()

Parameters of the registration interface may include, but are not limited to, token and info. the token and info may both be of the String type. the value of token is negotiated in advance by the client and the page. Info is a supplementary description of the token and may be a null value.

The return value of the registration interface may be a Promise type object result, characterizing the registration result.

The page end can register a data transmission channel between the page end and the client through a registration interface. For example, the page may invoke a registration interface to send a registration request including token and info to the client.

If the client side allows the page side corresponding to the token to send/receive data, the client side can generate a channel object and return the channel object to the page side, and the page side does not need to use the token when sending/receiving the data. The token may be considered an attribute inside the channel object. The client may use the token in transmitting/receiving data, as described in more detail below.

1.2 closing the interface window. Ucdata. Unregister (token)

The page may invoke a close interface to close a data transfer channel between the page and the client. Before the page end calls the closing interface, the page end needs to call the registration interface before the page end calls the closing interface, and the channel registration is successful.

When the page corresponding to the page end is closed, if the corresponding data transmission channel is not closed, the channel can be actively closed by the browser kernel. The page end typically does not have to actively invoke the interface.

In the following, a procedure of calling the function interfaces by the page end and functions that can be implemented will be exemplarily described by taking the function interfaces of the channel object including a detection interface channel.

It should be noted that window. Xxdata is a global object, and its role is to provide a static method of registering and unregistering (i.e. registering interface and closing interface). And channel is an object bound to the page end. For example, page a may call window xxdata. Region st to generate channel a and page B may call window xxdata. Region st to generate channel B. The lifecycle of ChannelA and ChannelB are different. Accordingly, the present disclosure is a method of designing a detection interface, a data acquisition interface, a data transmission interface, and an instruction transmission interface as channels, not a window.

1.3 detection interface channel. AddEventListener

The detection interface is used for detecting messages sent by the client.

The page may invoke a detection interface to detect messages sent by the client.

The messages sent by the client may include, but are not limited to, a first message to characterize data sent by the client, a second message to characterize a state of the client, and a third message to characterize operational instructions sent by the client.

As an example, parameters of the detection interface (i.e., the detected message) may include, but are not limited to, "Data", "DataError", and "DataOption". Wherein "Data" corresponds to the first message, "DataError" corresponds to the second message, and "DataOption" corresponds to the third message.

"Data" indicates that there is new Data, and at this time, the page end needs to call the Data acquisition interface to acquire the Data, and "Data" can transfer three parameters: handle, info and length. handle is used to retrieve data and may indicate the data address. Info is used to describe the data content and length is used to describe the data length.

"DataError" indicates that the client is experiencing an exception when sending data, typically that the memory is full or other error content that the client negotiates with the page in advance.

"DataOption" indicates that there is a new operation instruction. The operation instructions described herein are used to characterize the operations that the page end needs to perform with respect to the received data.

It should be noted that the page end needs to call the registration interface before calling the detection interface, and the channel registration is successful.

1.4 data acquisition interface channel. FetchData

The data acquisition interface is used for acquiring data sent by the client. The page may invoke the data acquisition interface to acquire data sent by the client in response to the detection interface detecting a first message characterizing the data sent by the client. The parameters of the data acquisition interface may include the handle described above, which may be acquired from the first message detected by the detection interface.

If the page does not call the data acquisition interface to acquire data before the next time the client sends the data to the page, the data to be transmitted to the page last time may be covered by the data sent by the current client. The client may therefore immediately invoke the data acquisition interface to acquire data in response to the detection interface detecting a first message characterizing data sent by the client, which may otherwise be covered by data sent by the client the next time, at which time the handle expires.

The data acquisition interface can acquire data sent to the page end by the client side in a blocking manner in the process of acquiring the data. The return value of the data acquisition interface may be a Promise type object result, which is used to characterize the acquired data sent from the client to the page.

1.5 data Transmission interface channel

The data transmission interface is used for transmitting data to the client.

The page may invoke a data transmission interface to transmit data to the client.

Parameters of the data transmission interface may include, but are not limited to, data and info. The data is used for representing data content, and can be ArrayBuffer type. info is a data description, may be of the String type, and info may be a null value. The return value of the data transmission interface may be a Promise type object result for returning a transmission data result.

It should be noted that, before invoking the data transmission interface, the page end needs to invoke the registration interface before and the channel registration is successful.

1.6 Command Transmission interface channel. SendOption

The present disclosure does not define a specific use of data, and thus how the client processes the data sent by the client and how the client processes the data sent by the client all need to be implemented through communication.

In the present disclosure, operations that need to be performed on data may be notified by interoperation instructions between a client and a page.

The instruction sending interface is used for sending an operation instruction to the client to inform the client of the operation required to be performed on the received data from the page.

The page may call the instruction sending interface to send a first operation instruction to the client, where the first operation instruction is used to characterize an operation that the client needs to perform on data sent by the page.

For example, assuming that the page sends a picture to the client and the picture needs to be uploaded at the client, the page may call the instruction sending interface to inform the client that the action performed by the client is uploading, and may also inform the uploaded server and other information.

As an example, the parameters of the instruction sending interface may include an option, which is an operation protocol (i.e. the second operation instruction) sent to the client, i.e. an operation protocol that the client negotiates with the page in advance. The return value of the instruction sending interface may be a Promise type result, which is used to characterize the return result, that is, the result of the operation that the client negotiates with the page in advance.

It should be noted that, before the page end calls the interface of the instruction sending interface, the page end needs to call the registration interface before and the channel registration is successful.

As described above, the page end may detect the operation instruction sent by the client through the detection interface, and after receiving the operation instruction from the client, the page end may perform corresponding processing on the data sent by the client according to the operation instruction.

2. Client terminal

As shown in fig. 1, the browser kernel may provide a data processing function, so that the client can implement data transfer with the page under the action of the data processing function.

As an example, a data management class may be added by the browser kernel, which may be named the xxDataManager class. The client may be provided with data processing functions by this class, such as, but not limited to, the ability to receive data, send data, and the like, as may include, but not limited to, data transmission channel registration/de-registration notifications. The xxDataManager class may include, but is not limited to, a detector setlist, a data transmission method sendData, and an instruction transmission method sendOption.

After receiving the registration request sent by the page end, the client end can judge whether to accept to establish a data transmission channel with the page end according to the token and the info submitted by the page end. If the establishment of the data transmission channel with the page end is accepted, namely the page end corresponding to the token is allowed to transmit/receive data, a channel object can be generated by the xxDataManager and returned to the page end.

The client may send a message to the page using the data transfer channel. When the client sends a message to the page, the message may carry a token corresponding to the data transmission channel, where the token is submitted by the page when registering the data transmission channel. The message sent by the client can be detected by the detection interface called by the page, so that after the data transmission channel is registered, the message sent by the client can be successfully transferred to the page.

As described above, the messages sent by the client may include, but are not limited to, a first message to characterize data sent by the client, a second message to notify the state of the client, and a third message to characterize operational instructions sent by the client.

2.1 data Transmission method sendData

Taking a message sent by a client as a first message as an example, the client can call a data sending method to send data to a data transmission channel corresponding to the page end.

Parameters of the data transmission method may include, but are not limited to, token, info, and data. The token is transmitted during page registration, and is used for detecting interface detection and can be of String type; info is used to describe the data content, and may be of the String type; data is transmitted data, and may be a byte [ ] type.

2.2 instruction sending method sendOption

Taking a message sent by the client as a third message as an example, the client can call an instruction sending method to send a second operation instruction to a data transmission channel corresponding to the page end, where the second operation instruction is used for characterizing an operation that needs to be executed by the page end for data sent by the client.

Parameters of the instruction sending method may include, but are not limited to, token and option. The token is transmitted during page registration, and can characterize a channel for which a transmitted instruction aims, so that the token can be detected by a detection interface called by a corresponding page; the option is used to describe the second operation instruction. Both token and option may be of the String type.

2.3 Detector setListener

The detection object may be registered by a setting detector.

The detector has a plurality of methods corresponding to the predetermined interface, and the detector is configured to trigger the method corresponding to the predetermined interface in response to the predetermined interface (i.e., the predetermined method) being invoked by the page.

The detector may have methods including, but not limited to, a registration processing method list. Onregion, a shutdown method list. Onu region, a data reception method list. Ondatachunk received, an identification method list. Ondatacomplete, an instruction processing method list, and an instruction processing method list

2.4 registration processing method Listener. OnRegist

Among the functional interfaces called by the page end, the functional interface corresponding to the registration processing method is a registration interface.

And responding to the page terminal to call the registration interface to send a registration request, wherein the client terminal can call a registration processing method to acquire the registration request, judge whether to allow the establishment of a data transmission channel, and return a registration result to the page terminal.

Parameters of the registration processing method may include, but are not limited to, token and info in the registration request. For token and info, reference is made to the relevant description above and will not be repeated here.

The return value of the registration processing method may be an intelger type registration result notification message, which is used to notify whether the page end is successfully registered.

2.5 closing method Listener. OnUnregist

Among the functional interfaces called by the page end, the functional interface corresponding to the closing method is a closing interface.

And responding to the page end call closing interface to close the data transmission channel, and calling a closing method by the client end to close the data transmission channel.

The parameters of the closing method may include token passed on at page end registration, which may be of String type.

After closing the data transmission channel, the client cannot send data to the page end corresponding to the removed token.

2.6 data receiving method Listener

Among the functional interfaces called by the page end, the functional interface corresponding to the data receiving method is a data sending interface. And responding to the page end call data transmission interface to transmit data, and calling a data receiving method by the client end to acquire the data.

Parameters of the data reception method may include, but are not limited to, token, info, and data. The token and info may be both String type, where the token value is negotiated in advance by the client and the page. Info is a supplementary description of the token and may be a null value. data is byte [ ] type data. The return value of the data receiving method may be an intelger type notification message for notifying whether the client receives data.

It should be noted that data is not received from other token until it is received (just before it is called). And/or the data can prohibit the data sending method sendData from being called to send the data to the page end before the data is received. In other words, the client receives the data from other pages after receiving the data, and/or the client sends the data to the page after receiving the data. This is because, if new data is reintroduced when the current data is not processed, internal processing is excessively complicated, and it is necessary to maintain the states of a plurality of files to be transferred (transfer in progress/to be transferred/transfer completed, etc.).

2.7 identification method Listener. OndataComplete

Among the functional interfaces called by the page end, the functional interface corresponding to the identification method is a data transmission interface.

And responding to the page terminal to call the data sending interface to send data, calling an identification method by the client terminal to identify the identity of the page terminal sending the data, and returning a message whether to receive the data or not to the page terminal.

Parameters of the identification method may include a String type token, the value of which is negotiated in advance by the client and the page. The return value of the identification method may be an intelger type notification message for notifying whether the client-side receives data.

2.8 instruction processing method Listener. OnOption

The function interface corresponding to the instruction processing method in the function interfaces called by the page end is an instruction sending interface.

And responding to the page terminal call instruction sending interface to send a first operation instruction, and the client terminal call instruction processing method obtains the first operation instruction and processes the received data sent by the page terminal according to the operation represented by the first operation instruction.

Parameters of the instruction processing method may include, but are not limited to, token and option. Wherein, token and option can be both String type. The value of Token is negotiated in advance by the client and the page end, and the option is the instruction content of the first operation instruction.

The return value of the instruction processing method may be an intelger type notification message, which is used to notify whether the page end successfully processes the instruction.

So far, the detailed description is made about the operations that the page end and the client end can execute in the data transmission process. In the present disclosure, the data transferred between the page and the client may include, but is not limited to, text data and/or image data. The specific type of data transmitted between the page end and the client end is related to actual service requirements, for example, when the screenshot of the page end needs to be sent to the client end in an actual application scene, so that the client end uploads the screenshot to the server, the data sent by the page end to the client end can be image data.

The data transmission scheme of the present disclosure can also be applied to data transmission between different applications. That is, the present disclosure also proposes a method for enabling data transfer between a first application and a second application. Wherein the first application and the second application may refer to different applications installed and running on the same terminal device. The first application and the second application may be independently run on the same terminal device. Or the first application program and the second application program can also have a certain association relation. For example, the first application may be a carrier of the second application, and the first application may provide a runtime environment for the second application, and the second application may be executed in the runtime environment provided by the first application. For example, the first application may be, but is not limited to, a social APP, a payment APP, and the like, and the second application may be an applet running in the first application. An applet refers to an application that can be issued from a server and executed within a particular container without installation.

The above-mentioned client (application program) may be replaced with a first application program, and the above-mentioned page (web page) may be replaced with a second application program, so that data transmission between the first application program and the second application program may be achieved by using the above-mentioned data transmission method. Details of implementation of the method can be found in the above related description, and are not repeated here.

In practical applications, the data transmission method disclosed by the disclosure may be executed between a designated first application program and a second application program, or the first application program may selectively establish a data transmission channel with one or more second application programs, and data transmission between the first application program and the second application program is realized by using the data transmission channel.

As shown in fig. 3, a plurality of second applications for implementing a specific function may be embedded in the first application. At this time, the first application corresponds to the client described above, and the second application corresponds to the page described above. Wherein the second application may be an applet running on the first application.

When data transmission between the first application program and the second application program is needed, the data transmission method can be executed, a data transmission channel is established between the first application program and the second application program, and the data transmission between the first application program and the second application program is realized by utilizing the data transmission channel. The specific creation principle of the data transmission channel can be referred to the above related description, and will not be repeated here.

Fig. 4 shows a schematic structural diagram of an apparatus for implementing data transmission between a page end and a client according to an embodiment of the present disclosure. Wherein the functional modules of the apparatus may be implemented by hardware, software, or a combination of hardware and software implementing the principles of the present disclosure. Those skilled in the art will appreciate that the functional modules depicted in fig. 3 may be combined or divided into sub-modules to implement the principles of the invention described above. Accordingly, the description herein may support any possible combination, or division, or even further definition of the functional modules described herein.

The following is a brief description of the functional modules that the apparatus may have and the operations that each functional module may perform, and details related thereto may be referred to the above related description, which is not repeated herein.

Referring to fig. 4, an apparatus 400 for implementing data transmission between a page and a client includes a registration interface calling module 410, a receiving module 420, and a data transmission module 430.

The registration interface calling module 410 is configured to call the registration interface to send a registration request to the client, where the registration request is expected to establish a data transmission channel between the page and the client. The registration request may include a token that characterizes the identity of the page.

The receiving module 420 is configured to receive a registration result sent by the client, where the registration result is used to characterize whether the data transmission channel is successfully registered.

The data transmission module 430 is configured to implement data transmission between the page end and the client end by using the data transmission channel if the data transmission channel is successfully registered.

In the case that the registration of the data transmission channel is successful, the registration result includes an object for characterizing the data transmission channel, where the object has one or more function interfaces, and the data transmission module 430 may implement data transmission with the client by calling the function interfaces. The functional interfaces may include, but are not limited to, a detection interface, a data acquisition interface, a data transmission interface, an instruction transmission interface.

Taking the example that the functional interface includes a detection interface, the data transmission module 430 may invoke the detection interface to detect messages sent by the client, the detected messages may include, but are not limited to, one or more of a first message to characterize data sent by the client, a second message to characterize a state of the client, and a third message to characterize operational instructions sent by the client.

The functional interface may further include a data acquisition interface, and the data transmission module 430 may invoke the data acquisition interface to acquire data sent by the client in response to the detection interface detecting a first message characterizing the data sent by the client.

Taking the example that the functional interface includes a data transmission interface, the data transmission module 430 may call the data transmission interface to transmit data to the client.

Taking the example that the functional interface includes an instruction sending interface, the data transmission module 430 may call the instruction sending interface to send a first operation instruction to the client, where the first operation instruction is used to characterize an operation that needs to be performed by the client for data sent by the page.

The apparatus 400 for implementing data transmission may further include a closing module for invoking a closing interface to close a data transmission channel between the page and the client.

Fig. 5 illustrates a schematic structural diagram of an apparatus for implementing data transmission between a page end and a client according to another embodiment of the present disclosure. Wherein the functional modules of the apparatus may be implemented by hardware, software, or a combination of hardware and software implementing the principles of the present disclosure. Those skilled in the art will appreciate that the functional modules depicted in fig. 5 may be combined or divided into sub-modules to implement the principles of the invention described above. Accordingly, the description herein may support any possible combination, or division, or even further definition of the functional modules described herein.

Referring to fig. 5, an apparatus 500 for implementing data transmission between a page end and a client end includes a judging module 510, a sending module 520, and a data transmission module 530.

The determining module 510 is configured to determine whether to allow establishment of a data transmission channel in response to receiving a registration request sent by a peer that desires to establish the data transmission channel between the peer and a client. As an example, the registration request may include a token for characterizing the identity of the page, and the determining module 510 may determine whether to allow the establishment of the data transmission channel by detecting the validity of the token.

The sending module 520 is configured to send a registration result to the peer end, where the registration result is used to indicate whether the data transmission channel is successfully registered.

The data transmission module 530 is configured to implement data transmission between the page and the client by using the data transmission channel if the data transmission channel is successfully registered. The data transfer module 530 can send messages to the page using the data transfer channel. The transmitted messages may include, but are not limited to, one or more of a first message to characterize data transmitted by the client, a second message to inform the client of the status, and a third message to characterize operational instructions transmitted by the client.

The apparatus 500 for implementing data transmission may further comprise an object creation module for generating (i.e. creating) an object for characterizing the data transmission channel, where the object has one or more functional interfaces, in case the data transmission channel is allowed to be established, the registration result comprising the object. The functional interfaces may include, but are not limited to, a detection interface, a data acquisition interface, a data transmission interface, an instruction transmission interface.

The apparatus 500 for enabling data transfer may further comprise a setting module for setting a detector having a plurality of methods corresponding to the predetermined interface, the detector being arranged to trigger the method corresponding to the predetermined interface in response to the predetermined interface being invoked by the page end.

Taking a predetermined interface as a registration interface as an example, a method corresponding to the predetermined interface can be used as a registration processing method, a registration request is sent by calling the registration interface in response to the page terminal, the client terminal calls the registration processing method to obtain the registration request, whether the establishment of a data transmission channel is allowed or not is judged, and a registration result is returned to the page terminal.

Taking a predetermined interface as a data sending interface as an example, a method corresponding to the predetermined interface is a data receiving method, and the data transmission module 530 calls the data receiving method to obtain data in response to the page calling the data sending interface to send data. The client may receive the data from other pages after receiving the data, and/or the client may send the data to the page after receiving the data.

Taking the predetermined interface as a data transmission interface as an example, the method corresponding to the predetermined interface further includes an identification method, and the data transmission module 530 may call the identification method to identify the identity of the page end that transmits the data and return a message to the page end whether to receive the data in response to the page end calling the data transmission interface to transmit the data.

Taking the predetermined interface as an instruction sending interface as an example, a method corresponding to the predetermined interface is an instruction processing method, and the apparatus 500 for implementing data transmission may further include a processing module, configured to send a first operation instruction in response to the page-end call instruction sending interface, call the instruction processing method to obtain the first operation instruction, and process the received data sent by the page end according to an operation represented by the first operation instruction.

Taking the predetermined interface as a closing interface as an example, a method corresponding to the predetermined interface is a closing method, and the apparatus 500 for implementing data transmission may further include a closing module, configured to respond to a page end calling the closing interface to close the data transmission channel, and call the closing method to close the data transmission channel.

FIG. 6 illustrates a schematic diagram of a computing device that may be used to implement the above-described methods according to one embodiment of the present disclosure.

Referring to fig. 6, a computing device 600 includes a memory 610 and a processor 620.

Processor 620 may be a multi-core processor or may include multiple processors. In some embodiments, processor 620 may include a general-purpose host processor and one or more special coprocessors, such as a Graphics Processor (GPU), digital Signal Processor (DSP), etc. In some embodiments, the processor 620 may be implemented using custom circuitry, for example, an application specific integrated circuit (ASIC, applicationSpecificIntegratedCircuit) or a field programmable gate array (FPGA, fieldProgrammableGateArrays).

Memory 610 may include various types of storage units, such as system memory, read Only Memory (ROM), and persistent storage. Where the ROM may store static data or instructions that are required by the processor 620 or other modules of the computer. The persistent storage may be a readable and writable storage. The persistent storage may be a non-volatile memory device that does not lose stored instructions and data even after the computer is powered down. In some embodiments, the persistent storage device employs a mass storage device (e.g., magnetic or optical disk, flash memory) as the persistent storage device. In other embodiments, the persistent storage may be a removable storage device (e.g., diskette, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as dynamic random access memory. The system memory may store instructions and data that are required by some or all of the processors at runtime. Furthermore, memory 610 may include any combination of computer-readable storage media including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), magnetic disks, and/or optical disks may also be employed. In some implementations, memory 610 may include readable and/or writable removable storage devices such as Compact Discs (CDs), digital versatile discs (e.g., DVD-ROMs, dual-layer DVD-ROMs), blu-ray discs read only, super-density discs, flash memory cards (e.g., SD cards, minSD cards, micro-SD cards, etc.), magnetic floppy disks, and the like. The computer readable storage medium does not contain a carrier wave or an instantaneous electronic signal transmitted by wireless or wired transmission.

The memory 610 has stored thereon executable code that, when processed by the processor 620, causes the processor 620 to perform the methods described above for enabling data transfer between a page and a client.

Methods, apparatuses, and devices for enabling data transfer between a page and a client according to the present disclosure have been described in detail above with reference to the accompanying drawings.

Furthermore, the method according to the present disclosure may also be implemented as a computer program or computer program product comprising computer program code instructions for performing the above steps defined in the above method of the present disclosure.

Alternatively, the present disclosure may also be implemented as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) having stored thereon executable code (or computer program, or computer instruction code) that, when executed by a processor of an electronic device (or computing device, server, etc.), causes the processor to perform the steps of the above-described method according to the present disclosure.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the improvement of technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method for enabling data transfer between a page end and a client, the page end being a page program running in the client, the method comprising:

the page terminal calls a registration interface to send a registration request for establishing a data transmission channel between the page terminal and the client terminal to the client terminal;

receiving a registration result sent by the client, wherein the registration result is used for representing whether the data transmission channel is successfully registered; and

under the condition that the data transmission channel is successfully registered, the data transmission between the page end and the client end is realized by utilizing the data transmission channel,

and under the condition that the data transmission channel is successfully registered, the registration result comprises an object for representing the data transmission channel, the object is provided with one or more functional interfaces, and the page end realizes data transmission with the client end by calling the functional interfaces.

2. The method of claim 1, wherein,

the registration request includes a token that characterizes the identity of the page.

3. The method of claim 1, wherein,

the functional interface comprises a detection interface,

And the page terminal calls the detection interface to detect the message sent by the client terminal.

4. A method according to claim 3, wherein the message comprises at least one of:

a first message characterizing data sent by the client;

a second message for characterizing a state of the client;

and a third message for characterizing the operation instruction sent by the client.

5. The method of claim 3, wherein,

the functional interface also includes a data acquisition interface,

and responding to the detection interface to detect a first message for representing the data sent by the client, and calling the data acquisition interface by the page end to acquire the data sent by the client.

6. The method of claim 1, wherein,

the functional interface comprises a data transmission interface,

the step of using the data transmission channel to realize the data transmission between the page end and the client end comprises the following steps: and the page terminal calls the data sending interface to send data to the client terminal.

7. The method of claim 1, wherein,

the functional interface comprises an instruction sending interface,

the step of using the data transmission channel to realize the data transmission between the page end and the client end comprises the following steps:

The page terminal calls the instruction sending interface to send a first operation instruction to the client terminal, wherein the first operation instruction is used for representing an operation instruction sending interface which needs to be executed by the client terminal for data sent by the page terminal.

8. The method of claim 1, further comprising:

and the page end call closing interface closes a data transmission channel between the page end and the client.

9. The method of any of claims 1 to 8, wherein the data transmitted between the page and the client comprises text data and/or image data.

10. A method for enabling data transfer between a page end and a client, the page end being a page program running in the client, the method comprising:

in response to receiving a registration request sent by the page end and expected to establish a data transmission channel between the page end and the client, the client judges whether to allow the establishment of the data transmission channel, and generates an object for representing the data transmission channel under the condition that the establishment of the data transmission channel is allowed, wherein the object is provided with one or more functional interfaces;

sending a registration result used for representing whether the data transmission channel is successfully registered to the page end, wherein the registration result comprises the object under the condition that the data transmission channel is successfully registered; and

And under the condition that the data transmission channel is successfully registered, the data transmission between the page end and the client end is realized by utilizing the data transmission channel.

11. The method of claim 10, wherein,

the registration request includes a token characterizing the identity of the page,

the step of the client judging whether to allow the establishment of the data transmission channel includes: and the client judges whether the establishment of the data transmission channel is allowed or not by detecting the validity of the token.

12. The method of claim 10, wherein the functional interface comprises at least one of:

the detection interface is used for detecting the message sent by the client;

the data acquisition interface is used for acquiring data sent by the client;

the data sending interface is used for sending data to the client;

and the instruction sending interface is used for sending a first operation instruction to the client, wherein the first operation instruction is used for representing an operation which the client needs to execute for the data sent by the page.

13. The method of claim 10, further comprising:

a detector is provided having a plurality of methods corresponding to a predetermined interface, the detector being configured to trigger a method corresponding to the predetermined interface in response to the predetermined interface being invoked by the page.

14. The method of claim 13, wherein,

the predetermined interface is a registration interface, the method corresponding to the predetermined interface is a registration processing method,

and responding to the page terminal to call the registration interface to send the registration request, calling the registration processing method by the client terminal to acquire the registration request, judging whether the data transmission channel is allowed to be established, and returning the registration result to the page terminal.

15. The method of claim 13, wherein,

the preset interface is a data transmission interface, the method corresponding to the preset interface is a data receiving method,

the step of using the data transmission channel to realize the data transmission between the page end and the client end comprises the following steps: and responding to the page terminal to call the data sending interface to send data, and calling the data receiving method by the client terminal to acquire the data.

16. The method of claim 15, wherein,

the client receives the data from other page ends after receiving the data, and/or

And the client sends the data to the page after receiving the data.

17. The method of claim 15, wherein,

The predetermined interface is a data transmission interface, the method corresponding to the predetermined interface further comprises an identification method,

the step of using the data transmission channel to realize data transmission between the page end and the client end further comprises: and responding to the page terminal to call the data transmission interface to transmit data, calling the identification method by the client terminal to identify the identity of the page terminal transmitting the data, and returning a message whether to receive the data or not to the page terminal.

18. The method of claim 13, wherein,

the predetermined interface is an instruction sending interface, the method corresponding to the predetermined interface is an instruction processing method,

the step of using the data transmission channel to realize the data transmission between the page end and the client end comprises the following steps: and responding to the page terminal to call the instruction sending interface to send a first operation instruction, and calling the instruction processing method by the client terminal to acquire the first operation instruction and processing the received data sent by the page terminal according to the operation represented by the first operation instruction.

19. The method of claim 13, wherein,

the preset interface is a closing interface, the method corresponding to the preset interface is a closing method,

And the client side calls the closing method to close the data transmission channel.

20. The method of claim 10, wherein,

the step of using the data transmission channel to realize the data transmission between the page end and the client end comprises the following steps: and sending a message to the page terminal by utilizing the data transmission channel.

21. The method of claim 20, wherein the message comprises at least one of:

a first message characterizing data sent by the client;

a second message for characterizing a state of the client;

22. The method of claim 20, wherein the step of sending a message to the page using the data transmission channel comprises:

calling a data sending method to send data to a data transmission channel corresponding to the page end; and/or

And the calling instruction sending method sends a second operation instruction to the data transmission channel corresponding to the page end, wherein the second operation instruction is used for representing the operation which the page end needs to execute for the data sent by the client end.

23. The method of claim 10, wherein the data transmitted between the page and the client comprises text data and/or image data.

24. The method according to any one of claims 10 to 23, wherein,

the client is a client application running based on a browser kernel,

the method for realizing data transmission between the page end and the client end is executed by the browser kernel.

25. An apparatus for enabling data transfer between a page end and a client, the page end being a page program running in the client, the apparatus comprising:

the registration interface calling module is used for calling a registration interface to send a registration request for establishing a data transmission channel between the page end and the client end to the client end;

the receiving module is used for receiving a registration result sent by the client, and the registration result is used for representing whether the data transmission channel is successfully registered; and

a data transmission module for realizing data transmission between the page end and the client end by using the data transmission channel under the condition that the data transmission channel is successfully registered,

26. An apparatus for enabling data transfer between a page end and a client, the page end being a page program running in the client, the apparatus comprising:

the judging module is used for responding to a registration request which is sent by the page end and is expected to establish a data transmission channel between the page end and the client end, and judging whether the data transmission channel is allowed to be established or not;

an object creation module for generating an object for characterizing the data transmission channel, the object having one or more functional interfaces, in case the data transmission channel is allowed to be established;

the sending module is used for sending a registration result used for representing whether the data transmission channel is successfully registered to the page end, wherein the registration result comprises the object under the condition that the data transmission channel is successfully registered; and

and the data transmission module is used for realizing data transmission between the page end and the client by utilizing the data transmission channel under the condition that the data transmission channel is successfully registered.

27. A computing device, comprising:

a processor; and

a memory having executable code stored thereon, which when executed by the processor causes the processor to perform the method of any of claims 1 to 24.

28. A non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the method of any of claims 1 to 24.