CN111885194A

CN111885194A - Communication method and device for communication application and electronic equipment

Info

Publication number: CN111885194A
Application number: CN202010755665.9A
Authority: CN
Inventors: 康小龙; 陈毅聪; 陈少伟
Original assignee: Ringslink Xiamen Network Communication Technologies Co ltd
Current assignee: Ringslink Xiamen Network Communication Technologies Co ltd
Priority date: 2020-07-31
Filing date: 2020-07-31
Publication date: 2020-11-03
Anticipated expiration: 2040-07-31
Also published as: CN111885194B

Abstract

The application discloses a communication method for communication application, which belongs to the technical field of communication application, is applied to first electronic equipment and comprises the following steps: acquiring a communication instruction; controlling the function control to load the first type of function files from the second electronic equipment to the local; wherein, the first type of function file is at least used for realizing the communication function; running the first type of function file; and a second type of function file is packaged in the communication application. When the method works, the communication function can be completed only by loading the first type of function file from the second electronic equipment and then operating. Therefore, when a new entity talkback terminal device needs to be docked, only the first-type function files on the second electronic device need to be updated, a new native APP does not need to be developed again, a new APP does not need to be downloaded by a user, the user experience is improved, and the cost for developing the native APP is also reduced.

Description

Communication method and device for communication application and electronic equipment

Technical Field

The present disclosure relates to the field of communication application technologies, and in particular, to a communication method and apparatus for communication application, and an electronic device.

Background

In apps in the current intercom field, sip calls, alarm push, remote control of intercom terminal equipment and RTSP video monitoring are almost all functions that apps have. However, there are problems with the development of these apps in this regard. For sip talkback, alarm push, RTPS monitoring and other core functions, the core functions are realized in the development of the native App by tightly combining services. It is known that an App and an entity intercom terminal device (e.g., a gate phone) in the intercom field are closely combined and used in a matching manner, because a user often needs to call through the App to open a door, remotely monitor and the like to directly communicate with the entity intercom terminal device, because the entity intercom terminal device is not changeable, software codes in the entity intercom terminal device often cannot be changed easily, and the communication protocols and the monitoring protocols of the entity intercom terminal device between different manufacturers have certain differences, even completely different implementations. Therefore, when an App in the current talkback field is compatible with a new manufacturer entity talkback terminal device or different entity talkback terminal devices are realized by the same manufacturer software layer, a native App code needs to be re-developed and then can be used after being updated by a user, so that the original App code cannot be used once and for all, and one App can be compatible with various types of devices.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The present disclosure aims to provide a communication method and apparatus for communication application, and an electronic device, so as to overcome the technical problems that a new native APP needs to be developed and a user needs to download the APP again each time a new entity intercom terminal device is docked at least to a certain extent.

According to an aspect of the present disclosure, there is provided a communication method for a communication application, applied to a first electronic device, including:

acquiring a communication instruction;

controlling the function control to load the first type of function files from the second electronic equipment to the local; wherein, the first type of function file is at least used for realizing the communication function;

running the first type of function file;

and a second type of function file is packaged in the communication application.

In an exemplary embodiment of the present disclosure, the functionality control comprises a webview control.

In an exemplary embodiment of the present disclosure, the resource file corresponding to the first type of function file is stored in the second electronic device, and can be called by the function control of the first electronic device, so as to implement loading on the first electronic device.

In an exemplary embodiment of the present disclosure, the method further comprises:

controlling the function control to load a third type of function file from the second electronic equipment to the local;

running the third type of function file;

and the third type of function file is used for displaying an interface, and the interface comprises at least one function key.

In an exemplary embodiment of the present disclosure, the first type of function file includes at least one of: the sip registration function file, the call function file and the communication protocol file.

In an exemplary embodiment of the disclosure, the second type of function file includes at least one of: socket protocol files, sip interface files and webRTC protocol files.

responding to the update instruction;

sending a query request to the second electronic device;

receiving feedback information sent by the second electronic equipment, and determining whether the first type of locally loaded functional files are files of the latest version according to the feedback information;

and if not, loading the update file from the second electronic equipment.

In an exemplary embodiment of the present disclosure, the first type function file loaded in the communication application is an H5 function file.

According to an aspect of the present disclosure, there is provided a communication apparatus including:

the acquisition module is used for acquiring a communication instruction;

the communication module is used for responding to the communication instruction and controlling the function control to load the first type of function files from the second electronic equipment to the local; wherein, the first type of function file is at least used for realizing the communication function;

the operation module is used for operating the first type of function files;

and the packaging module is used for packaging the second type of function file.

According to an aspect of the present disclosure, there is provided an electronic device including:

a processor;

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform any of the above-described communication methods via execution of the executable instructions.

According to an aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the communication method of any one of the above.

The application discloses a communication method and a communication device for communication application, wherein a first type of function file is loaded from a second electronic device (such as a server) to the local through a function control during communication, so that communication can be realized. Therefore, the first type of function files for realizing the communication function are not packaged in the native APP, but developed on the second electronic equipment. When the communication application works, the communication function can be completed only by loading the first type of function file from the second electronic equipment and then running. Therefore, when a new entity talkback terminal device needs to be docked, only the first-type function files on the second electronic device need to be updated, a new native APP does not need to be developed again, a new APP does not need to be downloaded by a user, the user experience is improved, and the cost for developing the native APP is also reduced.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

Fig. 1 schematically shows a flow chart of a communication method for a communication application.

Fig. 2 schematically shows a block diagram of a communication device.

Fig. 3 schematically illustrates a computer-readable storage medium for implementing the above-described communication method.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The noun explains:

native APP: the method is a third-party mobile application program which is based on a local operating system of the intelligent device, such as Android, IOS and Windows Phone, and runs by writing a native program. Before the APP runs on the electronic equipment, the APP can be downloaded to the electronic equipment by a user before the APP runs.

H5 and APP mix development: the native APP encapsulates part of the functionality, H5 resource files, stored on a remote server. When the APP runs, the function control can be used for loading the H5 webpage to realize the running of partial functions.

In the present exemplary embodiment, a communication method for communication application is provided first, and the communication method may be executed on an electronic device, such as an electronic device like a mobile phone or a PAD, and of course, a person skilled in the art may also execute the method of the present invention on another platform according to a requirement, which is not limited in this exemplary embodiment. Referring to fig. 1, the communication method may include the steps of:

step S110, a communication instruction is obtained;

step S120, controlling the function control to load a first type of function file from the second electronic equipment to the local; wherein, the first type of function file is at least used for realizing the communication function;

step S130, operating the first type of function file;

The first electronic device in which the communication method provided by this embodiment operates may be a smartphone, a smart watch, or other commonly used electronic devices, and this embodiment takes the smartphone as an example for description. The method may work on the APP installed in the first electronic device.

Specifically, the communication instruction may be obtained by a user clicking a communication button or triggering through other gestures on a relevant interface of the APP. Of course, the communication command may be obtained in response to a communication request from another electronic device.

And responding to the acquisition of the communication instruction, and loading the first type of function files stored on the second electronic equipment through the function control in the APP. Of course, the first type of function file may be loaded when the APP is started, and may be operated after the communication instruction is obtained. That is, the order of step S110 and step S120 may be switched according to the requirement in the actual application.

The second electronic device may be a server or a cloud, and the server is taken as an example in this embodiment for description. The first type function file stored on the server is an H5 resource file, and can perform information interaction with the first electronic device, so that the first electronic device can realize the function represented by the first type function at night through an H5 webpage.

And after loading, operating the first type of function file, and establishing communication connection with the third electronic equipment, thereby realizing the communication function. The third electronic device may be another smart phone or an entity intercom terminal device. In this embodiment, the third electronic device takes an entity intercom terminal device as an example for description.

It should be noted that, in this embodiment, the communication application may be referred to as a native APP, where the encapsulated second type function file may be a communication interface protocol, a generic function file, or a file of other basic functions. Without the need to package files that actually implement the communication function. The file actually implementing the communication function is a first type of enabling file, which is stored on the second electronic device and can also be understood as being developed or deployed on the second electronic device.

In addition, in practical applications, the fourth electronic device is actually required to participate in order to implement the communication function. The fourth electronic device may be a docking server providing a communication function. The first electronic equipment is in communication connection with the third electronic equipment through the fourth electronic equipment. Meanwhile, the fourth electronic device can also assume the following functions: and the system is responsible for accessing the third electronic equipment to the intercom system, pushing the alarm and the movement of the third electronic equipment to the first electronic equipment (communication application), and sending the processing result of the first electronic equipment (communication application) to the third electronic equipment.

In the communication method for the communication application disclosed in this embodiment, when performing communication, the first type of function file is loaded locally from the second electronic device (e.g., a server) through the function control, so as to implement communication capability. Therefore, the first type of function files for realizing the communication function are not packaged in the native APP, but developed on the second electronic equipment. When the communication application works, the communication function can be completed only by loading the first type of function file from the second electronic equipment and then running. Therefore, when a new entity talkback terminal device needs to be docked, only the first-type function files on the second electronic device need to be updated, a new native APP does not need to be developed again, a new APP does not need to be downloaded by a user, the user experience is improved, and the cost for developing the native APP is also reduced.

The webview control is encapsulated in the communication application, namely in the native APP. And when the communication function is carried out, the communication application calls the loaded first-class function file to operate through the webview control to realize the communication function. Of course, in some other embodiments, those skilled in the art may replace the webview control with other spaces having the same function, so as to implement the running of the first type function file.

In an exemplary embodiment of the present disclosure, the resource file corresponding to the first type of function file is stored in the second electronic device, and can be called by the function control of the first electronic device, so as to implement loading on the first electronic device. The first type of function file loaded in the communication application is an H5 function file. The resource files can be developed together when the communication application is originally developed, and are stored on the second electronic equipment. To a certain extent, it can be understood that the communication application is actually composed of the second type of resource file encapsulated in the native APP and the first type of function file loaded from the second electronic device.

It should be noted that, after the first type of function file is loaded, the communication application may not delete the first type of function file but may repeatedly run the first type of function file under a general condition or without other special requirements. That is, the communication application does not need to load the first type of function file once during each communication.

In an exemplary embodiment of the present disclosure, the method further comprises: controlling the function control to load a third type of function file from the second electronic equipment to the local;

running the third type of function file;

In actual application, the UI interface is changed frequently with version update or other requirements. Therefore, frequent updating of the interface is required. Accordingly, the resource file corresponding to the third type of function file is also stored on the second electronic device, so that the first electronic device can load the third type of function file from the second electronic device. Therefore, the user does not need to download new APP again when the interface is updated every time, and the user experience is improved.

In an exemplary embodiment of the present disclosure, the first type of function file includes at least one of: the sip registration function file, the call function file and the communication protocol file. The second type of function file at least comprises one of the following: socket protocol files, sip interface files and webRTC protocol files.

Specifically, it can be understood that native APP implements encapsulation of a socket protocol, interface encapsulation of a sip protocol, webRTC protocol encapsulation, an interface exposing a relevant flow to H5, and secondary encapsulation of a generic SDK and an API. The loaded first-class functional files realize the flows of sip registration, conversation, hang-up and the like, and the App does not control the services any more. In order to further facilitate understanding, the related communication protocols stored in the first type of function files are adapted according to the specific communication protocol of the entity talkback terminal equipment capable of being docked. Thereby realizing communication with the third device (the physical intercom terminal device).

responding to the update instruction;

sending a query request to the second electronic device;

and if not, loading the update file from the second electronic equipment.

Due to the fact that in actual application, a communication application provider needs to be capable of continuously communicating with more third electronic devices of different types. Therefore, the first type of function file is inevitably required to be updated, so that the adaptation of the new equipment is realized. Therefore, after the communication application runs, the query request can be sent to the second electronic device, and the feedback information returned by the second electronic device is received, so that whether the locally-loaded first-class function file is the latest version or not is determined. If yes, subsequent other operations are not needed. And if the first type of locally loaded functional files are found not to be the latest version of files, requesting to load the update files from the second electronic equipment so as to update the first type of locally loaded functional files and prevent the first type of locally loaded functional files from being incapable of normally communicating with the newly accessed third electronic equipment.

In this embodiment, the obtaining of the update instruction may be actively triggered by the user through operation, or may be automatically triggered by the communication application under a specific condition. For example, the update command is automatically triggered every time the communication application is opened or every fixed time interval.

Next, the embodiment will exemplarily explain the present communication method in terms of practical application (or practical development).

Firstly, developing a bottom layer architecture module on App, including SIP call, WEBRTC video monitoring, alarm, Socket, system command service, webview and the like, and exposing a specific method name to JavaScript call. After the user opens the App, the App calls a restful interface of the H5Model to acquire a home page file address of H5 needing to be loaded, and then relevant resources are downloaded from a server through a WebView control in a UI thread and are analyzed and rendered. From this point on App will only act after H5 calls its corresponding interface.

② the H5 file on the server, which stores the real function and interface. The Web server stores a mapping of the home address of H5, and when App requests a home address, the corresponding home address of H5 is returned in a response from the restful interface. After the App loads the H5 home page file, a user can see a complete interface, and meanwhile, H5 calls a socket module reserved by the App and a WEB server to establish a long TCP connection for the server to send information such as alarms and motion of equipment to the App. Then, the user can manage the equipment by clicking and selecting the equipment management entry equipment module in the home page of H5, and when the user needs to communicate with the equipment, H5 calls the SIP communication module of App to communicate.

When a new device is online, the device enters the whole object system through the access server, and the access server is responsible for the access, alarm and motion receiving and sending work of the device. If the functions of the SIP protocol and the video monitoring, the remote control and the like used by the equipment are different from the protocols supported by the prior App, so that the App cannot be used, the core functions of the SIP, the video monitoring, the remote control and the like are realized at H5, and at the moment, only the H5 file needs to be updated, so that the equipment can be supported without the user being aware of the equipment.

And fourthly, the specific service function is not realized due to the fact that the core protocol is encapsulated at the bottom layer of the App, the service layer is completely realized at H5, and the App can acquire completely different functions by acquiring different H5 home page addresses, so that the App becomes a brand-new talkback App.

Thus, the following technical effects can be realized:

the intercommunication App developed by the mode, the SIP protocol interface is exposed by the App package, SIP communication can be basically and directly completed at H5, and the App is not required to natively complete SIP related service codes.

Secondly, the intercom App developed by the mode expands the socket programming capability of the H5, the App is not originally developed in the required socket service, and the H5 realizes long connection with the server through the socket and does not depend on the APP.

Due to the fact that the service functions of SIP communication, video monitoring, alarm pushing and the like are directly communicated with the equipment at the H5 level, when the novel equipment or the equipment of different manufacturers needs to be compatible, the direct pushing of the H5 code can be completed without updating the App, and other talkback Apps do not have the functions.

And fourthly, when other talkback apps need to be developed, the apps are only responsible for providing interfaces, and are equivalent to a sandbox system, and the original codes of the apps can be completely reused, so that the development time is greatly shortened.

Corresponding to the communication method, an embodiment of the present application further provides a communication device, which may also be applied to various physical machines or service platforms with information processing and computing functions, such as a smart phone, a smart watch, a PAD, a notebook, a desktop, and an all-in-one machine, or a server/server cluster, a cloud platform, and the like, where a schematic structural diagram of the processing device is shown in fig. 2, and the processing device may include: the device comprises an acquisition module, a communication module, an operation module and a packaging module.

Wherein the content of the first and second substances,

the acquisition module can be used for acquiring a communication instruction;

the communication module can be used for responding to the communication instruction and controlling the function control to load the first type of function files from the second electronic equipment to the local; wherein, the first type of function file is at least used for realizing the communication function;

the running module can be used for running the first type of function files;

and the packaging module can be used for packaging the second type of function file.

The details of each module in the communication device have been described in detail in the corresponding communication method, and therefore are not described herein again.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, there is also provided.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

The electronic device is in the form of a general purpose computing device. Components of the electronic device may include, but are not limited to: the at least one processing unit, the at least one memory unit, and a bus connecting the various system components (including the memory unit and the processing unit).

Wherein the storage unit stores program code executable by the processing unit to cause the processing unit to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary methods" of the present specification. For example, the processing unit may perform step S110 as shown in fig. 1: acquiring a communication instruction; s120: controlling the function control to load the first type of function files from the second electronic equipment to the local; step S130: and running the first type of function files.

The memory unit may include a readable medium in the form of a volatile memory unit, such as a random access memory unit (RAM) and/or a cache memory unit, and may further include a read only memory unit (ROM).

The storage unit may also include a program/utility having a set (at least one) of program modules including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

The bus may be any of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device may also communicate with one or more external devices (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface. Also, the electronic device may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via a network adapter. As shown, the network adapter communicates with other modules of the electronic device over a bus. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.

Referring to fig. 3, a program product 600 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A communication method for communication application is applied to a first electronic device, and is characterized by comprising the following steps:

acquiring a communication instruction;

running the first type of function file;

2. The communication method according to claim 1, wherein the functionality control comprises a webview control.

3. The communication method according to claim 1, wherein the resource file corresponding to the first type of function file is stored in the second electronic device, and can be called by a function control of the first electronic device, so as to implement loading on the first electronic device.

4. The communication method according to claim 1, further comprising:

running the third type of function file;

5. The communication method according to claim 1, wherein the first type of function file comprises at least one of: the sip registration function file, the call function file and the communication protocol file.

6. The communication method according to claim 1, wherein the second type of function file comprises at least one of: socket protocol files, sip interface files and webRTC protocol files.

7. The communication method according to claim 1, further comprising:

responding to the update instruction;

sending a query request to the second electronic device;

and if not, loading the update file from the second electronic equipment.

8. The communication method according to claim 1, wherein the first type function file loaded in the communication application is an H5 function file.

9. A communication device, comprising:

the acquisition module is used for acquiring a communication instruction;

the operation module is used for operating the first type of function files;

10. An electronic device, comprising:

a processor;

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the communication method of any one of claims 1-8 via execution of the executable instructions.