CN115686339A

CN115686339A - Cross-process information processing method, electronic device, storage medium, and program product

Info

Publication number: CN115686339A
Application number: CN202110823852.0A
Authority: CN
Inventors: 李国刚
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-07-21
Filing date: 2021-07-21
Publication date: 2023-02-03

Abstract

The embodiment of the application provides a cross-process information processing method, electronic equipment, a storage medium and a program product, wherein the method comprises the steps that a first application sends first service data to a third application; the third application stores the first service data in an independent storage partition corresponding to the third application; the third application sends first identification information to the first application, wherein the first identification information corresponds to the first service data; the first application sends first identification information to the second application; and the second application acquires the first service data in the independent storage partition of the third application according to the first identification information. In this embodiment of the present application, the third application is used as an application for implementing data storage, and the second application may obtain service data of the first application through the third application, so as to implement cross-process information processing. In addition, since the traffic data of the first application is stored in the independent memory partition of the third application, the traffic data of the first application is not lost even if both the first application and the second application are uninstalled.

Description

Cross-process information processing method, electronic device, storage medium, and program product

Technical Field

The present application relates to the field of computer technologies, and in particular, to a cross-process information processing method, an electronic device, a storage medium, and a program product.

Background

In order to limit the unordered use of the external memory card by a user, effectively manage files of each application and reduce confusion, an Android system introduces a partitioned Storage (Scoped Storage) mechanism. Under a partition storage mechanism, each application has a storage space of the application; the application cannot directly access the storage space of other applications by means of an absolute file path, i.e. the application cannot directly read the data of other applications without authorization from other applications.

However, in some application scenarios, an application needs to read data across processes, i.e., an application may need to read the data of its application. For example, in a Rich Communication Suite (RCS) application scenario, an application a needs to implement an RCS function, and sends a file path to an RCS service application, and the RCS service application acquires a file based on the file path provided by the application a and then sends the file to a server. However, after the partition storage mechanism is introduced, the storage space of each application is relatively independent, and the RCS service application cannot read the data of other applications, so that the RCS function cannot be realized.

Disclosure of Invention

In view of this, the present application provides a cross-process information processing method, an electronic device, a storage medium, and a program product, so as to solve the problem in the prior art that after a partition storage mechanism is introduced, a storage space of each application is relatively independent, and cross-process information processing cannot be implemented.

In a first aspect, an embodiment of the present application provides a cross-process information processing method, including:

the first application sends the first service data to the third application;

the third application stores the first service data in an independent storage partition corresponding to the third application;

the third application sends first identification information to the first application, wherein the first identification information corresponds to the first service data;

the first application sends the first identification information to the second application;

and the second application acquires the first service data in an independent storage partition of the third application according to the first identification information.

Preferably, the method further comprises:

the second application receives second service data;

the second application sends the second service data to the third application;

the third application stores the second service data in an independent storage partition corresponding to the third application;

and the first application acquires the second service data in an independent storage partition of the third application.

Preferably, the obtaining, by the first application, the second service data in an independent storage partition of the third application includes:

the first application monitors data change in an independent storage partition of the third application through a monitor mode;

and after the third application stores the second service data in the independent storage partition corresponding to the third application, the first application acquires the second service data in the independent storage partition of the third application.

Preferably, the method further comprises:

the second application receives second service data;

and the second application sends the second service data to the first application.

Preferably, the method further comprises:

the first application sends the second service data to the third application;

and the third application stores the second service data in an independent storage partition corresponding to the third application.

Preferably, the first application is an information service application, the first service data is information edited by a user, and the sending of the first service data by the first application to the third application includes:

the information service application receives information edited by a user;

and responding to the information sending operation of the user, and sending the converged communication file edited by the user to the third application by the information service application.

Preferably, the first application is a call service application, the first service data is a pre-call interaction file edited by a user, and the sending of the first service data by the first application to the third application includes:

before a call, receiving a pre-call interactive file edited by a user;

and responding to the call calling operation of the user, and sending the pre-call interaction file to the third application by the call service application.

Preferably, the first application is a call service application, the first service data is an interactive file edited by a user in a call process, and the sending of the first service data by the first application to the third application includes:

in the conversation process, the conversation service application receives interactive files edited by a user in the conversation process;

and the call service application sends the interactive file in the call process to the third application.

Preferably, the first application is a call service application, the first service data is an interactive file edited by a user after the call is suspended, and the sending of the first service data by the first application to the third application includes:

after receiving an incoming call and triggering a call hangup operation, the call service application receives a call hangup interactive file edited by a user;

and the call service application sends the interaction file after the call is hung up to the third application.

Preferably, the second application is a converged communication RCS service application.

In a second aspect, an embodiment of the present application provides an electronic device, including:

one or more processors;

a memory;

and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions, which when executed by the electronic device, cause the electronic device to perform the method of any of the first aspects above.

In a third aspect, an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium includes a stored program, where when the program runs, the apparatus where the computer-readable storage medium is located is controlled to execute the method in any one of the above first aspects.

In a fourth aspect, the present application provides a computer program product, which contains executable instructions that, when executed on a computer, cause the computer to perform the method of any one of the above first aspects.

In this embodiment of the present application, the third application is used as an application for implementing data storage, and the second application may obtain service data of the first application through the third application, so as to implement cross-process information processing. In addition, since the service data of the first application is stored in the independent memory partition of the third application, the service data of the first application is not lost even if both the first application and the second application are uninstalled.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.

Fig. 1 is a schematic diagram of an electronic device according to an embodiment of the present disclosure;

fig. 2 is a schematic view of an application scenario of a cross-process information processing method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a cross-process information processing method according to an embodiment of the present application;

fig. 4 is a schematic view of a first application provided in an embodiment of the present application;

fig. 5 is a schematic view of an application scenario of another cross-process information processing method according to an embodiment of the present application;

fig. 6 is a schematic flowchart of another cross-process information processing method according to an embodiment of the present application;

fig. 7 is a schematic view of another scenario of a first application provided in an embodiment of the present application;

fig. 8 is a schematic view of an application scenario of another cross-process information processing method according to an embodiment of the present application;

fig. 9 is a schematic flowchart of another cross-process information processing method according to an embodiment of the present application;

fig. 10A is a schematic view of a RCS function switch scenario provided in an embodiment of the present application;

fig. 10B is a schematic diagram of an RCS application scenario provided in an embodiment of the present application;

fig. 11 is a block diagram of a software structure of an electronic device according to an embodiment of the present application;

fig. 12 is a schematic flowchart of another cross-process information processing method according to an embodiment of the present application;

fig. 13 is a schematic flowchart of another cross-process information processing method according to an embodiment of the present application;

fig. 14 is a schematic flowchart of another cross-process information processing method according to an embodiment of the present application;

fig. 15 is a schematic view of a scenario of a call service application according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to better understand the technical solution of the present application, the following detailed description is made with reference to the accompanying drawings.

It should be understood that the embodiments described are only a few embodiments of the present application, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be understood that the term "and/or" as used herein is merely one type of associative relationship that describes an associated object, meaning that three types of relationships may exist, e.g., A and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

Referring to fig. 1, a schematic view of an electronic device provided in an embodiment of the present application is shown. In fig. 1, an electronic device is illustrated by taking a mobile phone 100 as an example. It can be understood that the electronic device according to the embodiment of the present application may be a tablet computer, a Personal Computer (PC), a Personal Digital Assistant (PDA), a smart watch, a netbook, a wearable electronic device, an Augmented Reality (AR) device, a Virtual Reality (VR) device, an in-vehicle device, a smart car, a smart audio, a robot, smart glasses, a smart television, and the like, besides the mobile phone 100.

It should be noted that, in some possible implementations, the electronic device may also be referred to as a terminal device, a User Equipment (UE), and the like, which is not limited in this embodiment of the present application.

In order to limit unordered use of an external memory card by a user, effectively manage files of each application and reduce confusion, an Android (Android) system introduces a partitioned Storage (scanned Storage) mechanism. Under a partition storage mechanism, each application has a storage space of the application; the application cannot flip its own memory space to access the memory space of other applications, i.e. the application cannot read the data of other applications.

However, in some application scenarios, applications need to read data across processes, i.e., an application may need to read data of other applications. For example, in a Rich Communication Suite (RCS) application scenario, an application a needs to implement an RCS function, and sends a file path to an RCS service application, and the RCS service application acquires a file based on the file path provided by the application a and then sends the file to a server. However, after the partition storage mechanism is introduced, the storage space of each application is relatively independent, and the RCS service application cannot read data of other applications, that is, cannot implement cross-process information processing, and further cannot implement the RCS function.

One possible solution to the above problem is for application a, which holds file C, to access file C and send file C to application B. For example, in a converged Communication (RCS) application scenario, an application a needs to implement an RCS function, and the application a saves a file C to its own independent storage area, and when the file C needs to be sent through the RCS function, the application a reads the file C to a cache and then sends the file C to an RCS service application. And the RCS service application receives the file C and then sends the file C to the server.

However, although the above solution can implement cross-process data reading, when the application a is uninstalled, the file C saved by the application a is deleted synchronously, and after that, other applications cannot access the file C when they need to access the file C. Therefore, the embodiment of the application provides a cross-process information processing scheme to ensure that data is not automatically deleted due to application uninstallation on the premise of realizing cross-process data access. The following detailed description is made with reference to the accompanying drawings.

Referring to fig. 2, a schematic view of an application scenario of a cross-process information processing method provided in an embodiment of the present application is shown. Fig. 2 shows a first application, a second application, and a third application, which may be located in the same electronic device, and in the application scenario shown in fig. 2, the electronic device is a sending end.

When a first application needs to send data through a second application, the second application cannot directly acquire the data in an independent storage partition of the first application, so that the first application firstly sends service data to a third application and stores the service data in an independent storage partition of the third application; the second application then retrieves the relevant data stored by the third application. Specifically, the method comprises the following steps: (1) The first application sends the first service data to the third application; (2) The third application stores the first service data in the independent storage partition of the third application and generates first identification information, the first identification information corresponds to the first service data, the first service data (3) stored in the independent storage partition of the third application can be accessed through the first identification information, and the third application sends the first identification information to the first application; (4) The first application sends first identification information to the second application; (5) The second application acquires first service data in the third application according to the first identification information; and (6) the second application sends the first service data to the server.

Referring to fig. 3, a schematic flow chart of a cross-process information processing method provided in the embodiment of the present application is shown. The method corresponds to the application scenario shown in fig. 2, and as shown in fig. 3, it mainly includes the following steps.

Step S301: the first application sends the first service data to the third application.

Step S301 may be triggered by any manner, for example, before S301, the electronic device receives a service triggering operation to trigger execution of S301; the service triggering operation may be a user input, such as a touch input or a voice input; the input may also be a message or instruction sent by another smart device.

For example, the electronic device is a sending end, and the user sends the service data through the first application. It is understood that the first application is a service execution application. The business trigger operation may be understood as information edited by a user in the display interface of the first application or a trigger instruction input by the user. The first service data is data corresponding to a service triggering operation of a user.

Fig. 4 is a schematic view of a first application provided in an embodiment of the present application. As shown in fig. 4, the first application is an information service application 400, and a user 401 can edit information in a display interface of the information service application, where the first service data 402 is information edited by the user. Specifically, the information Service application may be a short message Service application or a Multimedia Messaging Service (MMS) Service application.

Of course, the first application may also be other types of applications such as a call service application, and this is not specifically limited in this embodiment of the application. When the first application is a call service application, the user can make a call with the call service application of the receiving end through the call service application of the transmitting end.

Step S302: the third application stores the first service data.

In this embodiment, the third application is an application for implementing data storage, and the third application stores the first service data in its independent storage partition. It can be appreciated that since the traffic data of the first application is stored in the independent memory partition of the third application, the traffic data of the first application is not lost even though both the first application and the second application are uninstalled.

Step S303: the third application sends the first identification information to the first application.

After the storage of the first service data is completed, the third application generates first identification information corresponding to the first service data, sends the first identification information to the first application, and can access the first service data stored in the independent storage partition of the third application through the first identification information.

In a specific implementation, the first identification information may be Uniform Resource Identifier (URI) information. Of course, other identification information may also be adopted by those skilled in the art, and the embodiment of the present application does not limit this.

Step S304: the first application sends the first identification information to the second application.

It is understood that the second application is an application that provides a service to the first application. Specifically, after receiving first identification information sent by a third application, a first application sends the first identification information to a second application, so that the second application obtains corresponding service data in the third application according to the first identification information.

Step S305: and the second application acquires the first service data in the independent storage partition of the third application according to the first identification information.

Because the first identification information and the first service data have a corresponding relationship, after receiving the first identification information, the second application can acquire the first service data in the independent storage partition of the third application according to the first identification information.

Step S306: the second application sends the first service data to the server.

And after receiving the first service data, the second application sends the first service data to the server so that the server can send the service data to the receiving end.

In the above embodiment, as a cross-process information processing method at a sending end, the following describes the cross-process information processing method provided in the embodiment of the present application from a receiving end.

Referring to fig. 5, a schematic view of an application scenario of another cross-process information processing method provided in the embodiment of the present application is shown. Fig. 5 shows a first application, a second application, and a third application, which may be located in the same electronic device, and in the application scenario shown in fig. 5, the electronic device is a receiving end.

When the server receives second service data sent by the sending end, the second service data is sent to a third application and stored in an independent storage partition of the third application; the first application then retrieves the relevant data stored by the third application. Specifically, the method comprises the following steps: (1) After receiving the second service data sent by the sending end, the server sends the second service data to a second application; (2) The second application sends second service data to the third application; (3) The third application stores the second service data in the independent storage partition; (4) The first application monitors the data change of the third application through the listener mode, and acquires the updated data of the third application, namely the second service data, in the third application.

In the embodiment of the application, after the electronic device serving as a receiving end receives the service data, the second application sends the service data to the third application and stores the service data in the independent storage partition of the third application, and even if the first application and the second application are both uninstalled, the service data of the first application cannot be lost.

Referring to fig. 6, a schematic flow chart of another cross-process information processing method provided in the embodiment of the present application is shown. The method corresponds to the application scenario shown in fig. 4, as shown in fig. 6, which mainly comprises the following steps.

Step S601: the server sends the second service data to the second application.

In this embodiment of the application, the electronic device is a receiving end, and the server receives the second service data sent by the sending end and then sends the second service data to the second application. The second application may be understood as an application providing a service to the first application.

It should be noted that, in a possible implementation manner, the second application may also directly receive the second service data sent by the other terminal device, which is not specifically limited in this embodiment of the application.

Step S602: the second application sends the second service data to the third application.

In this embodiment of the application, the third application is an application for implementing data storage, and after receiving the second service data, the second application sends the second service data to the third application, so that the third application stores the second service data in its independent storage partition.

Step S603: the third application stores the second service data.

And after receiving the second service data, the third application stores the second service data in the independent storage partition.

Step S604: the first application acquires the second service data in the third application.

Specifically, the first application may monitor a data change in the independent memory partition of the third application, and when there is a data update in the independent memory partition of the third application, the third application requests to obtain the updated data.

After the first application acquires the second service data, the second service data can be output in the electronic device, so that a user can acquire related information.

Referring to fig. 7, a schematic view of another first application provided in the embodiment of the present application is shown. As shown in fig. 7, the first application is an information service application 400, and the second service data 702 is information data sent by a user 701 on the sending end. After the information service application 400 acquires the second service data 702, the second service data 702 is displayed in the display interface of the information service application 400, so that the user 401 can acquire related information.

Of course, the first application may also be other types of applications such as a call service application, and this is not limited in this embodiment of the application.

In the embodiment of the application, after the electronic device serving as a receiving end receives the service data, the second application sends the service data to the third application, and the service data is stored in the independent storage partition of the third application, so that the service data of the first application cannot be lost even if the first application and the second application are both unloaded.

It can be understood that, when the electronic device is a receiving end, after the second application receives the second service data sent by the server, the second service data may also be sent to the first application first, and then the first application sends the second service data to the third application for storage, which will be described in detail below.

Referring to fig. 8, a schematic view of an application scenario of another cross-process information processing method provided in the embodiment of the present application is shown. Fig. 8 shows a first application, a second application, and a third application, which may be located in the same electronic device, and in the application scenario shown in fig. 8, the electronic device is a receiving end.

In the embodiment of the present application, the method specifically includes the steps of: (1) After receiving the second service data, the server sends the second service data to a second application; (2) The second application sends second service data to the first application; (3) The first application sends second service data to the third application; (4) The third application stores the second service data in its separate memory partition.

That is to say, after receiving the second service data sent by the server, the second application first sends the second service data to the first application, and then the first application sends the second service data to the third application for storage.

Referring to fig. 9, a schematic flow chart of another cross-process information processing method provided in the embodiment of the present application is shown. The method corresponds to the application scenario shown in fig. 8, and as shown in fig. 9, it mainly includes the following steps.

Step S901: and the server sends the second service data to the second application.

In this embodiment of the application, the electronic device is a receiving end, and the server receives the second service data sent by the sending end and then sends the second service data to the second application.

Step S902: the second application sends the second traffic data to the first application.

And the second application directly sends the second service data to the first application after receiving the second service data.

Step S903: the first application outputs the second service data.

The first application may output the second service data after receiving the second service data. For example, when the first application is an information service application, text information corresponding to the second service data is displayed in an information service application display interface.

Step S904: the first application sends the second service data to the third application.

In the embodiment of the present application, the first application receives the second service data, and the second service data is stored in the cache of the first application. If the second service data is not sent to the third application for storage, the second service data is lost after the first application is restarted or unloaded. Therefore, in the embodiment of the present application, after the first application receives the second service data, the second service data still needs to be sent to the third application for storage.

Step S905: the third application stores the second service data.

For details of the embodiment shown in fig. 9, reference may be made to the description of the embodiment shown in fig. 6, and for brevity, the details are not repeated herein.

In a possible implementation manner, the second application is an RCS service application. The following describes a scenario of the application of the RCS service. RCS refers to the convergence of communication technology services and information technology services. The communication technology-based Service refers to various services of the conventional telecommunication network, such as a call Service, a short message Service, a Multimedia Messaging Service (MMS) Service, and the like. The information technology services refer to various services of Internet Protocol (IP) class, such as Instant Messaging (IM); video and application sharing, such as video monitoring, information sharing, and downloading services; and internet services such as email, voicemail, etc. In addition, there are also information processing services, such as e-commerce, information inquiry, etc. The RCS is a new generation of international standard for message service, and a new generation of information service platform created by telecom operators can realize 'information namely platform, user namely customer and mobile phone namely application'.

Referring to fig. 10A, a schematic view of a RCS function switch scenario provided in the embodiment of the present application is shown. As shown in fig. 10A, the RCS information setting interface 1010 is provided with an RCS information switch 1011, and a user can turn on or off the RCS information function of the terminal through the RCS information switch 1011. For example, when the slider in the RCS information switch 1011 slides to the right, the RCS information function of the terminal is turned on (the state shown in fig. 10A); when the slider in the RCS information switch 1011 slides to the left side, the RCS information function of the terminal is turned off. Specifically, when the RCS information function of the terminal is turned on, the user can receive and send information through a mobile network or a Wireless Local Area Network (WLAN) by default on the short message interface, and meanwhile, multiple information types including pictures, voices and geographic positions are supported, so that communication is more convenient.

In addition, a read report switch 1012 is provided in the RCS information setting interface 1010, and a user can turn on or off the read report function of the terminal through the read report switch 1012. For example, when the slider in the read report switch 1012 slides to the right, the read report function of the terminal is turned on (the state shown in fig. 10A); when the slider in the read report switch 1012 slides to the left side, the read report function of the terminal is turned off.

It is understood that fig. 10A is only an exemplary description of the embodiments of the present application, and should not be taken as limiting the scope of the present application.

Referring to fig. 10B, a schematic view of an RCS application scenario provided in the embodiment of the present application is shown. In the embodiment shown in fig. 10B, the RCS is referred to as RCS information. As shown in fig. 10B, the first application is a short message service application 1020, and in the short message service application 1020, a user 1021 can perform information interaction with a user 1022 based on RCS information. The RCS information can be information types such as characters and pictures, and information is received and sent through a mobile network or a WLAN in a short message service application interface in a default mode, so that communication is more convenient. The specific interaction process is described in detail in the following embodiments.

It is understood that fig. 10B is only an exemplary description of the embodiments of the present application, and should not be taken as limiting the scope of the present application.

Referring to fig. 11, a block diagram of a software structure of an electronic device according to an embodiment of the present application is provided. The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android (Android) system is divided into four layers, an application layer, a framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom. Wherein android runtime and system libraries, and kernel layers are not shown in the figure.

An Application layer (App) may comprise a series of Application packages. As shown in fig. 11, the application package may include a multimedia messaging service application, a phonebook application, a call service application, and the like. In addition, the application layer can be divided into three modules of an interface, logic and data, and the modules communicate with each other through software interfaces. The interface module is used for displaying information for interaction of a user; the logic module is used for information processing; the data module is used for storing data.

Specifically, the applications shown in the interface module correspond to the first applications in the above embodiments, and may include, for example, multimedia Messaging Service (MMS), phone book (Contacts), and call Service (IncallUI), where the IncallUI is mainly used for displaying and updating a call interface, querying call information, and simple logic, such as answering/hanging up.

The logic module corresponds to the second application in the above embodiments, and may include, for example, an RCS service.

The data module corresponds to the third application in the foregoing embodiment, and is configured to store the service data. In order to store different service data respectively, the data modules include a phonebook provider (contactprovider), a call record provider (CallLogProvider), and an information content provider (TelephonyProvider). The contact provider is used for storing business data corresponding to the telephone directory application; the CallLogProvider is used for storing service data corresponding to the call service application; the TelephonyProvider is used for storing service data corresponding to the multimedia information service application.

The Framework layer (FWK) provides an Application Programming Interface (API) and a programming Framework for an application program of the application layer. The application framework layer includes a number of predefined functions. As shown in fig. 11, the framework layer includes a content provider (ContentProvider) and a content parser (ContentResolver). Wherein, the ContactsProvider, callLogProvider and TelephonyProvider of the application layer are realized based on the ContentProvider of the framework layer.

The ContentProvider is one of four major components in the Android, and is mainly used for sharing data externally, that is, the data in the application is shared by the ContentProvider to be accessed by other applications, and the other applications can operate the data in the specified application through the ContentProvider. When an external application needs to add, delete, modify, and query data in the ContentProvider, it can be done using ContentResolver.

Taking the call service application as an example, the user may trigger an access request of the data module on an interface of the call service application, the call service application sends the access request to the ContentResolver, the ContentResolver analyzes the access request, and the corresponding unit in the data module is accessed through the ContentProvider. Since the application is a call service application, after the ContentResolver parses the access request, it is determined that the access request corresponds to the CallLogProvider in the data module, and therefore the CallLogProvider in the data module is accessed through the ContentProvider. Specifically, the service data corresponding to the call service application may be stored in the independent storage partition corresponding to the CallLogProvider, or the service data corresponding to the call service application may be acquired in the independent storage partition corresponding to the CallLogProvider.

Referring to fig. 12, a schematic flow chart of another cross-process information processing method provided in the embodiment of the present application is shown. In the embodiment of the application, the first application is a multimedia information service application, the second application is an RCS service application, and the third application is an information content provider in an Android system. The method can be applied to the software architecture in fig. 11, as shown in fig. 12, which mainly includes the following steps.

Step S1201: in response to an edit information operation by a user, the multimedia information service application transmits first information data to an information content provider.

The user can edit information in a display interface of the multimedia messaging service application, and the multimedia messaging service application sends first information data to the information content provider according to the information edited by the user. It can be understood that the first information data is information edited by the user.

Specifically, the first information data may be text type information, picture type information, or the like. For example, the first service data 402 in the embodiment shown in fig. 7 is text type information.

Step S1202: the information content provider stores the first information data, and generates first identification information.

The information content provider is an application that implements data storage, and the information content provider stores the first information data in its independent storage partition. It can be understood that since the information data of the multimedia messaging service application is stored in the separate storage partition of the content provider, the information data of the multimedia messaging service application is not lost even though both the multimedia messaging service application and the RCS service application are uninstalled.

After the storage of the first information data is completed, the information content provider generates first identification information corresponding to the first information data, and the first information data stored in the independent storage partition of the information content provider can be accessed through the first identification information.

Step S1203: the information content provider sends first identification information to the multimedia information service application.

After the information content provider generates the first identification information, the first identification information is sent to the multimedia information service application.

Specifically, the generating of the first identification information in step S1202 and the sending of the first identification information to the multimedia information service application in step S1203 may call a ContentResolver implementation of the architecture layer.

Step S1204: the multimedia information service application transmits the first identification information to the RCS service application.

After receiving the first identification information sent by the information content provider, the multimedia information service application sends the first identification information to the RCS service application, so that the RCS service application can obtain corresponding information data in the information content provider according to the first identification information.

Step S1205: the RCS service application acquires first information data in the information content provider according to the first identification information.

Because the first identification information and the first information data have a corresponding relationship, after receiving the first identification information, the RCS service application may acquire the first information data in the independent storage partition of the information content provider according to the first identification information.

In particular, the process may call the contentresolution implementation of the architecture layer.

Step S1206: the RCS service application sends the first information data to the server.

After receiving the first information data, the RCS service application sends the first information data to the server, so that the server sends the information data to the receiving end.

Step S1207: the server receives the second information data.

When the electronic device is a receiving end, the second information data sent by the server can be received.

Step S1208: the server sends the second information data to the RCS service application.

In the embodiment of the application, after receiving the second information data, the server sends the second information data to the RCS service application.

Step S1209: the RCS service application sends the second information data to the information content provider.

And after receiving the second information data, the RCS service application sends the second information data to the information content provider so that the information content provider can store the second information data in the independent storage partition.

Step S1210: the information content provider stores the second information data.

And after receiving the second information data, the information content provider stores the second information data in the independent storage partition. It is understood that the information content provider may generate the second identification information corresponding to the second information data after completing the storage of the second information data.

Step S1211: the multimedia information service application monitors the data change of the information content provider and acquires second information data updated by the information content provider.

In one possible implementation, the multimedia messaging service application may monitor data changes of the content provider in real time in a listener mode, and when there is a data update in the content provider, the multimedia messaging service application requests to acquire the updated data and displays the updated data, i.e., the second information data, in a display interface of the multimedia messaging service application. For example, the second service data 702 in the embodiment shown in fig. 7.

In the embodiment of the application, the information content provider is used as an application for realizing data storage, and the RCS service application can acquire service data of the multimedia information service application through the information content provider to realize the RCS function. Information data applied by the multimedia messaging service is stored in a separate storage partition of the content provider, and thus, even if both the multimedia messaging service application and the RCS service application are uninstalled, the information data of the multimedia messaging service application is not lost.

Referring to fig. 13, a schematic flow chart of another cross-process information processing method provided in the embodiment of the present application is shown. In the embodiment of the application, the first application is a call service application, the second application is an RCS service application, and the third application is a call record provider in an Android system. The method can be applied to the software architecture in fig. 11, as shown in fig. 13, which mainly includes the following steps.

Step S1301: the phone book application triggers a call operation.

In the embodiment of the application, the first service data is a pre-call interactive file, and a user can edit the pre-call interactive file on a phonebook application interface before triggering a call operation, so that the user can send the pre-call interactive file when triggering the call operation; the interactive file before the call may be text type information, picture type information, shared information (for example, a shared geographic location), an importance level identifier, and the like, which is not specifically limited in the embodiment of the present application.

Step S1302: the call service application sends the pre-call interaction file to the call record provider.

And after receiving the call triggering operation of the user, the call service application sends a pre-call interaction file to a call record provider.

Step S1303: the call record provider stores the interactive file before call and generates first identification information.

The call record provider stores the interactive file before call in the independent memory partition for realizing the application of data storage. It can be understood that since the pre-call interaction file of the call service application is stored in the independent storage partition of the call record provider, the pre-call interaction file of the call service application is not lost even though both the call service application and the RCS service application are uninstalled.

After the storage of the interactive file before the call is finished, the call record provider can generate first identification information corresponding to the interactive file before the call, and the interactive file before the call stored in the independent storage partition of the call record provider can be accessed through the first identification information.

Step S1304: the call record provider sends first identification information to the call service application.

After generating the first identification information, the call record provider sends the first identification information to the call service application.

Specifically, the generating of the first identification information in step S1303 and the sending of the first identification information to the call service application in step S1304 may be implemented by calling ContentResolver of the architecture layer.

Step S1305: the call service application sends the first identification information to the RCS service application.

After receiving the first identification information sent by the call record provider, the call service application sends the first identification information to the RCS service application, so that the RCS service application obtains corresponding information data in the call record provider according to the first identification information.

Step 1306: and the RCS service application acquires the interactive file before the call from the call record provider according to the first identification information.

Because the first identification information and the interactive file before the call have the corresponding relation, after receiving the first identification information, the RCS service application can acquire the interactive file before the call in the independent storage partition of the call record provider according to the first identification information.

In particular, the process may call the ContentResolver implementation of the architecture layer.

Step S1307: and the RCS service application sends the interactive file before the call to the server.

After receiving the interactive file before the call, the RCS service application sends the interactive file before the call to the server so that the server can send the interactive file before the call to the receiving end.

In the embodiment of the application, a user edits the pre-call interaction file before calling, and after triggering the call calling operation, the user firstly sends the pre-call interaction file to the calling object so that the calling object refers to the relevant information.

In another application scenario, after receiving an incoming call, a user may be inconvenient to answer the call, and can directly trigger a call hang-up operation and then edit an interactive file after the call hang-up. Referring to fig. 14, a schematic flow chart of another cross-process information processing method provided in the embodiment of the present application is shown. The embodiment of the present application further describes a processing procedure of the interactive file after the call is suspended. As shown in fig. 14, it mainly includes the following steps.

Step S1401: and after receiving the incoming call, the user triggers the operation of hanging up the call and edits the interactive file after the call is hung up.

In the embodiment of the application, the first service data is an interactive file after the call is disconnected, and the call may not be conveniently answered after the call is received. At the moment, the call can be directly triggered to hang up without answering the incoming call, and then the interactive file after the call is hung up is edited. The interactive file after the call is suspended may be text type information, picture type information, shared information (for example, a shared geographic location), an importance level identifier, and the like, which is not specifically limited in the embodiment of the present application.

Step S1402: and the call service application sends the call hang-up interactive file to the call record provider.

After the user finishes editing the interaction file after the call is hung up in the call service application, the call service application sends the interaction file after the call is hung up to the call record provider.

Step S1403: and the call record provider stores the interactive file after the call is hung up and generates first identification information.

The call record provider stores the interaction file after hanging up in the independent storage partition of the call record provider for realizing the application of data storage. It can be understood that, since the interaction file after the call of the call service application is suspended is stored in the independent storage partition of the call record provider, the interaction file after the call of the call service application is suspended will not be lost even if both the call service application and the RCS service application are uninstalled.

After the storage of the interactive file after the call is hung up is completed, the call record provider can generate first identification information corresponding to the interactive file after the call is hung up, and the interactive file after the call is hung up stored in the independent storage partition of the call record provider can be accessed through the first identification information.

Step S1404: the call record provider sends the first identification information to the call service application.

Specifically, the generation of the first identification information in step S1403 and the sending of the first identification information to the call service application in step S1404 may be implemented by invoking contentresolution of the architecture layer.

Step S1405: the call service application sends the first identification information to the RCS service application.

Step S1406: and the RCS service application acquires the interactive file after the call is hung up from the call record provider according to the first identification information.

Because the first identification information and the interaction file after the call is hung up have a corresponding relation, after receiving the first identification information, the RCS service application can acquire the interaction file after the call is hung up in the independent storage partition of the call record provider according to the first identification information.

Step S1407: and the RCS service application sends the interactive file after the call is hung up to the server.

After receiving the interaction file after the call is hung up, the RCS service application sends the interaction file after the call is hung up to the server, so that the server sends the interaction file after the call is hung up to the receiving end.

In the embodiment of the application, the user can edit the interaction file after the call is hung up in the call process, and the interaction file after the call is hung up is sent to the call object in real time so that the call object can look up related information.

Based on the same principle, the calling object can also edit the interaction file after the call is hung up in the call process, and send the edited interaction file after the call is hung up to the user in real time. The process of receiving the interactive file after the call object is sent to hang up by the user may refer to the process of receiving the second service data in the foregoing embodiment, and for brevity, details are not repeated here.

In addition, in addition to the interactive file before the call and the interactive file after the call is suspended, the user may also edit the interactive file during the call in the call process, and send the interactive file during the call to the receiving party in real time during the call, and the specific process may refer to the description of the above embodiment, and is not described herein again.

Referring to fig. 15, a scene diagram of a call service application provided in the embodiment of the present application is shown. As shown in fig. 15, a user 1501 and a user 1503 are included in the call interface 1500, and the user 1501 may send a pre-call interaction file 1502 to the user 1503 before a call, where the pre-call interaction file 1502 is geographical location information shared by the user 1501. During the call, the user 1503 may send the in-call interaction file 1504 to the user 1501 in real time, where the in-call interaction file 1504 is the text type information sent by the user 1503 during the call.

It is understood that the application scenario shown in fig. 15 is only an exemplary description, and should not be taken as a limitation to the scope of the present application.

Corresponding to the above method embodiment, the present application also provides an electronic device, which includes one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions which, when executed by the electronic device, cause the electronic device to perform some or all of the steps of the above-described method embodiments.

Fig. 16 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. As shown in fig. 16, the electronic device 1600 may include a processor 1610, an external memory interface 1620, an internal memory 1621, a Universal Serial Bus (USB) interface 1630, a charging management module 1640, a power management module 1641, a battery 1642, an antenna 1, an antenna 2, a mobile communication module 1650, a wireless communication module 1660, an audio module 1670, a speaker 1670A, a receiver 1670B, a microphone 1670C, a headset interface 1670D, a sensor module 1680, keys 1690, a motor 1691, an indicator 1692, a camera 1693, a display 94, and a Subscriber Identification Module (SIM) card interface 1695, etc. The sensor module 1680 may include a pressure sensor 1680A, a gyroscope sensor 1680B, an air pressure sensor 1680C, a magnetic sensor 1680D, an acceleration sensor 1680E, a distance sensor 1680F, a proximity light sensor 1680G, a fingerprint sensor 1680H, a temperature sensor 1680J, a touch sensor 1680K, an ambient light sensor 1680L, a bone conduction sensor 1680M, and the like.

It is to be understood that the illustrated configuration of the embodiment of the invention does not constitute a specific limitation to the electronic device 1600. In other embodiments of the present application, electronic device 1600 may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 1610 may include one or more processing units, such as: processor 1610 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), among others. The different processing units may be separate devices or may be integrated into one or more processors.

The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 1610 for storing instructions and data. In some embodiments, memory in processor 1610 is cache memory. The memory may hold instructions or data that have just been used or recycled by processor 1610. If processor 1610 needs to reuse the instructions or data, it can call directly from the memory. Avoiding repeated accesses reduces the latency of the processor 1610, thereby increasing the efficiency of the system.

In some embodiments, processor 1610 may include one or more interfaces. The interface may include an integrated circuit (I16C) interface, an integrated circuit built-in audio (I16S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I16C interface is a bidirectional synchronous serial bus including a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 1610 may include multiple sets of I16C buses. Processor 1610 may be coupled to touch sensor 1680K, charger, flash, camera 1693, etc., respectively, through various I16C bus interfaces. For example: processor 1610 may be coupled to touch sensor 1680K via an I16C interface, such that processor 1610 and touch sensor 1680K communicate via an I16C bus interface to implement touch functionality of electronic device 1600.

The I16S interface may be used for audio communication. In some embodiments, processor 1610 may include multiple sets of I16S buses. Processor 1610 may be coupled to audio module 1670 via an I16S bus enabling communication between processor 1610 and audio module 1670. In some embodiments, the audio module 1670 can transmit the audio signal to the wireless communication module 1660 through the I16S interface, so as to receive the call through the bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, audio module 1670 and wireless communication module 1660 may be coupled by a PCM bus interface. In some embodiments, the audio module 1670 can also pass audio signals to the wireless communication module 1660 through the PCM interface, enabling answering calls through a bluetooth headset. Both the I16S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is typically used to connect the processor 1610 and the wireless communication module 1660. For example: the processor 1610 communicates with the bluetooth module in the wireless communication module 1660 through the UART interface to implement the bluetooth function. In some embodiments, the audio module 1670 can transmit the audio signal to the wireless communication module 1660 through the UART interface, so as to realize the function of playing music through the bluetooth headset.

The MIPI interface may be used to connect processor 1610 with peripheral devices such as display 1694, camera 1693, etc. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 1610 and camera 1693 communicate over a CSI interface to implement the capture functionality of electronic device 1600. Processor 1610 and display 1694 communicate via the DSI interface to implement display functions for electronic device 1600.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 1610 with the camera 1693, the display 1694, the wireless communication module 1660, the audio module 1670, the sensor module 1680, and so forth. The GPIO interface may also be configured as an I16C interface, an I16S interface, a UART interface, a MIPI interface, and the like.

The USB interface 1630 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 1630 may be used to connect a charger to charge the electronic device 1600, and may also be used to transmit data between the electronic device 1600 and a peripheral device. And the method can also be used for connecting a headset and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It should be understood that the connection relationship between the modules according to the embodiment of the present invention is only illustrative, and is not limited to the structure of the electronic device 1600. In other embodiments of the present application, the electronic device 1600 may also adopt different interface connection manners in the above embodiments, or a combination of multiple interface connection manners.

The charge management module 1640 is used to receive charging input from the charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 1640 may receive charging input for a wired charger via the USB interface 1630. In some wireless charging embodiments, the charging management module 1640 may receive wireless charging input through a wireless charging coil of the electronic device 1600. The charging management module 1640 can also supply power to the electronic device via the power management module 1641 while charging the battery 1642.

The power management module 1641 is used to connect the battery 1642, the charging management module 1640 and the processor 1610. The power management module 1641 receives input from the battery 1642 and/or the charge management module 1640 and provides power to the processor 1610, the internal memory 1621, the display screen 1694, the camera 1693, and the wireless communication module 1660, among other things. The power management module 1641 may also be used to monitor parameters such as battery capacity, battery cycle number, battery state of health (leakage, impedance), etc. In other embodiments, the power management module 1641 may be disposed in the processor 1610. In other embodiments, the power management module 1641 and the charging management module 1640 may be provided in the same device.

The wireless communication function of the electronic device 1600 can be implemented by the antenna 1, the antenna 2, the mobile communication module 1650, the wireless communication module 1660, the modem processor, the baseband processor, and the like.

The

antennas

1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 1600 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 1650 can provide a solution including wireless communication of 2G/3G/4G/5G, etc. applied to the electronic device 1600. The mobile communication module 1650 may include at least one filter, switch, power amplifier, low Noise Amplifier (LNA), and the like. The mobile communication module 1650 may receive the electromagnetic wave from the antenna 1, filter, amplify, and transmit the received electromagnetic wave to the modem processor for demodulation. The mobile communication module 1650 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 1650 may be disposed in the processor 1610. In some embodiments, at least some of the functional blocks of the mobile communication module 1650 may be disposed in the same device as at least some of the blocks of the processor 1610.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 1670A, the receiver 1670B, etc.) or displays images or video through the display screen 1694. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be separate from the processor 1610, and may be implemented in the same device as the mobile communication module 1650 or other functional modules.

The wireless communication module 1660 may provide a solution for wireless communication applied to the electronic device 1600, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), global Navigation Satellite System (GNSS), frequency Modulation (FM), near Field Communication (NFC), infrared (IR), and so on. The wireless communication module 1660 may be one or more devices that integrate at least one communication processing module. The wireless communication module 1660 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering on the electromagnetic wave signal, and transmits the processed signal to the processor 1610. Wireless communication module 1660 may also receive signals to be transmitted from processor 1610, frequency modulate them, amplify them, and convert them to electromagnetic radiation via antenna 2.

In some embodiments, antenna 1 of electronic device 1600 is coupled with mobile communication module 1650 and antenna 2 is coupled with wireless communication module 1660 such that electronic device 1600 may communicate with networks and other devices via wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), general Packet Radio Service (GPRS), code Division Multiple Access (CDMA), wideband Code Division Multiple Access (WCDMA), time division code division multiple access (time-division multiple access, TD-SCDMA), long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 1600 performs display functions via the GPU, display screen 1694, and application processor, among other things. The GPU is an image processing microprocessor coupled to a display screen 1694 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 1610 may include one or more GPUs that execute program instructions to generate or change display information.

Display screen 1694 is used to display images, videos, and the like. Display screen 1694 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the electronic device 1600 may include 1 or N display screens 1694, N being a positive integer greater than 1.

The electronic device 1600 may implement a capture function via the ISP, camera 1693, video codec, GPU, display 1694, application processor, etc.

The ISP is used to process the data fed back by the camera 1693. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 1693.

Camera 1693 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV and other formats. In some embodiments, electronic device 1600 may include 1 or N cameras 1693, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 1600 selects at a frequency bin, the digital signal processor is used to perform a fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The electronic device 1600 may support one or more video codecs. In this way, the electronic device 1600 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent cognition of the electronic device 1600 can be implemented by the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 1620 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 1600. The external memory card communicates with the processor 1610 through an external memory interface 1620 to implement a data storage function. For example, files such as music, video, etc. are saved in the external memory card.

Internal memory 1621 may be used to store computer-executable program code, including instructions. The internal memory 1621 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The data storage area may store data created during use of the electronic device 1600 (e.g., audio data, phone books, etc.), and the like. Further, the internal memory 1621 may include a high speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a Universal Flash Storage (UFS), and the like. The processor 1610 performs various functional applications and data processing of the electronic device 1600 by executing instructions stored in the internal memory 1621 and/or instructions stored in a memory provided in the processor.

Electronic device 1600 may implement audio functions via audio module 1670, speaker 1670A, microphone 1670C, headphone interface 1670D, and application processor, among others. Such as music playing, recording, etc.

Audio module 1670 is used to convert digital audio information to an analog audio signal output and also to convert an analog audio input to a digital audio signal. Audio module 1670 may also be used to encode and decode audio signals. In some embodiments, the audio module 1670 may be disposed in the processor 1610, or some functional modules of the audio module 1670 may be disposed in the processor 1610.

Speaker 1670A, also known as a "speaker," is used to convert electrical audio signals into sound signals. Electronic device 1600 may listen to music or to a hands-free conversation via speaker 1670A.

A receiver 1670B, also called "earpiece", is used to convert the electrical audio signal into a sound signal. When the electronic device 1600 answers a call or voice message, the voice can be answered by placing the receiver 1670B near the ear.

A microphone 1670C, also known as a "microphone", converts sound signals into electrical signals. When making a call or sending voice information, the user can speak via his/her mouth near the microphone 1670C and input a voice signal into the microphone 1670C. Electronic device 1600 may be provided with at least one microphone 1670C. In other embodiments, the electronic device 1600 may be provided with two microphones 1670C, which may implement noise reduction functions in addition to collecting sound signals. In other embodiments, the electronic device 1600 may further include three, four, or more microphones 1670C to collect audio signals, reduce noise, identify audio sources, and perform directional recording.

The headset interface 1670D is used to connect wired headsets. The headset interface 1670D may be the USB interface 1630, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, or a Cellular Telecommunications Industry Association (CTIA) standard interface.

The pressure sensor 1680A is used for sensing a pressure signal and converting the pressure signal into an electrical signal. In some embodiments, pressure sensor 1680A may be disposed on display screen 1694. Pressure sensor 1680A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on pressure sensor 1680A, the capacitance between the electrodes changes. The electronic device 1600 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 1694, the electronic apparatus 1600 detects the intensity of the touch operation according to the pressure sensor 1680A. The electronic apparatus 1600 can also calculate the touched position from the detection signal of the pressure sensor 1680A. In some embodiments, the touch operations that are applied to the same touch position but have different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

Gyroscope sensor 1680B may be used to determine a motion gesture of electronic device 1600. In some embodiments, the angular velocity of electronic device 1600 about three axes (i.e., x, y, and z axes) may be determined by gyroscope sensor 1680B. The gyro sensor 1680B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyroscope 1680B detects the shake angle of the electronic device 1600, and calculates the distance that the lens module needs to compensate according to the shake angle, so that the lens can counteract the shake of the electronic device 1600 through reverse movement, thereby achieving anti-shake. The gyroscope sensor 1680B may also be used for navigation, somatosensory gaming scenes.

Barometric pressure sensor 1680C is used to measure barometric pressure. In some embodiments, the electronic device 1600 calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 1680C.

The magnetic sensor 1680D includes a hall sensor. The electronic device 1600 can detect the opening and closing of the flip holster with the magnetic sensor 1680D. In some embodiments, when the electronic device 1600 is a flip phone, the electronic device 1600 can detect the opening and closing of the flip according to the magnetic sensor 1680D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set.

Acceleration sensor 1680E may detect the magnitude of acceleration of electronic device 1600 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the electronic device 1600 is stationary. The method can also be used for identifying the posture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and the like.

A distance sensor 1680F for measuring distance. The electronic device 1600 may measure distance by infrared or laser. In some embodiments, shooting a scene, the electronic device 1600 may utilize the range sensor 1680F to range for fast focus.

The proximity light sensor 1680G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 1600 emits infrared light to the outside through the light emitting diode. The electronic device 1600 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 1600. When insufficient reflected light is detected, electronic device 1600 can determine that there are no objects near electronic device 1600. The electronic device 1600 can utilize the proximity sensor 1680G to detect that the user holds the electronic device 1600 close to the ear for communication, so as to automatically turn off the screen to achieve the purpose of saving power. The proximity light sensor 1680G may also be used in a holster mode, a pocket mode automatically unlocks and locks the screen.

The ambient light sensor 1680L is used to sense ambient light brightness. The electronic device 1600 may adaptively adjust the brightness of the display 1694 according to the perceived ambient light level. The ambient light sensor 1680L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 1680L may also cooperate with the proximity light sensor 1680G to detect whether the electronic device 1600 is in a pocket to prevent inadvertent contact.

The fingerprint sensor 1680H is used to collect a fingerprint. The electronic device 1600 can utilize the collected fingerprint characteristics to implement fingerprint unlocking, access to an application lock, fingerprint photographing, fingerprint incoming call answering, and the like.

The temperature sensor 1680J is used to detect temperature. In some embodiments, electronic device 1600 utilizes the temperature detected by temperature sensor 1680J to implement a temperature processing strategy. For example, when the temperature reported by temperature sensor 1680J exceeds a threshold, electronic device 1600 performs a reduction in performance of a processor located near temperature sensor 1680J in order to reduce power consumption to implement thermal protection. In other embodiments, electronic device 1600 heats battery 1642 when the temperature is below another threshold to avoid abnormal shutdown of electronic device 1600 due to low temperatures. In other embodiments, electronic device 1600 performs a boost on the output voltage of battery 1642 when the temperature is below a further threshold to avoid abnormal shutdown due to low temperature.

Touch sensor 1680K, also referred to as a "touch device. The touch sensor 1680K may be disposed on the display screen 1694, and the touch sensor 1680K and the display screen 1694 form a touch screen, which is also called a "touch screen". The touch sensor 1680K is used to detect a touch operation applied thereto or therearound. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operations can be provided through the display screen 1694. In other embodiments, the touch sensor 1680K can also be disposed on a surface of the electronic device 1600 at a different location than the display screen 1694.

Bone conduction sensor 1680M may acquire a vibration signal. In some embodiments, bone conduction sensor 1680M may acquire a vibration signal of a human voice vibrating a bone mass. The bone conduction sensor 1680M can also contact the human pulse to receive the blood pressure pulse signal. In some embodiments, bone conduction sensor 1680M may also be provided in a headset, incorporated into a bone conduction headset. The audio module 1670 may analyze the voice signal based on the vibration signal of the bone block vibrated by the sound part obtained by the bone conduction sensor 1680M, so as to implement the voice function. The application processor can analyze heart rate information based on the blood pressure pulsation signal acquired by the bone conduction sensor 1680M, so as to realize the heart rate detection function.

Keys 1690 include a power on key, a volume key, etc. Keys 1690 may be mechanical keys. Or may be touch keys. The electronic device 1600 may receive key inputs, generate key signal inputs related to user settings and function control of the electronic device 1600.

Motor 1691 can generate a vibration cue. Motor 1691 can be used for incoming call vibration cues, as well as touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motors 1691 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 1694. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 1692 may be an indicator light that can be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 1695 is used to connect a SIM card. The SIM card can be attached to and detached from the electronic device 1600 by being inserted into or removed from the SIM card interface 1695. The electronic device 1600 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 1695 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 1695 can be inserted into multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 1695 is also compatible with different types of SIM cards. The SIM card interface 1695 is also compatible with external memory cards. The electronic device 1600 interacts with the network through the SIM card to implement functions such as telephony and data communications. In some embodiments, the electronic device 1600 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 1600 and cannot be separated from the electronic device 1600.

In a specific implementation manner, the present application further provides a computer storage medium, where the computer storage medium may store a program, and when the program runs, the computer storage medium controls a device in which the computer readable storage medium is located to perform some or all of the steps in the foregoing embodiments. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).

In specific implementation, the embodiment of the present application further provides a computer program product, where the computer program product includes executable instructions, and when the executable instructions are executed on a computer, the computer is caused to execute some or all of the steps in the foregoing method embodiments.

In the embodiments of the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, and indicates that three relationships may exist, for example, a and/or B, and may indicate that a exists alone, a and B exist simultaneously, and B exists alone. Wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" and the like, refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.

Those of ordinary skill in the art will appreciate that the various elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of electronic hardware and computer software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided by the present invention, any function, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only an embodiment of the present invention, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the protection scope of the present invention. The protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A cross-process information processing method is characterized by comprising the following steps:

the first application sends the first service data to the third application;

2. The method of claim 1, further comprising:

the second application receives second service data;

the second application sends the second service data to the third application;

3. The method of claim 2, wherein the first application obtains the second service data in a separate memory partition of the third application, comprising:

the first application monitors data change in an independent storage partition of the third application through a listener mode;

4. The method of claim 1, further comprising:

the second application receives second service data;

5. The method of claim 4, further comprising:

the first application sends the second service data to the third application;

6. The method according to any one of claims 1 to 5, wherein the first application is an information service application, the first service data is information edited by a user, and the first application sends the first service data to a third application, including:

the information service application receives information edited by a user;

7. The method according to any one of claims 1 to 5, wherein the first application is a call service application, the first service data is a pre-call interaction file edited by a user, and the first application sends the first service data to a third application, including:

before a call, receiving a pre-call interactive file edited by a user;

8. The method according to any one of claims 1 to 5, wherein the first application is a call service application, the first service data is an in-call interactive file edited by a user, and the sending of the first service data by the first application to a third application includes:

9. The method according to any one of claims 1 to 5, wherein the first application is a call service application, the first service data is a user-edited interaction file after a call is suspended, and the sending of the first service data by the first application to a third application comprises:

10. The method of claim 1, wherein the second application is a converged communication (RCS) service application.

11. An electronic device, comprising:

one or more processors;

a memory;

and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions, which when executed by the electronic device, cause the electronic device to perform the method of any of claims 1-10.

12. A computer-readable storage medium, comprising a stored program, wherein the program, when executed, controls an apparatus in which the computer-readable storage medium is located to perform the method of any one of claims 1-10.

13. A computer program product comprising executable instructions that when executed on a computer cause the computer to perform the method of any one of claims 1 to 10.