CN117857686A - Communication method, communication system and related device - Google Patents

Abstract

The application provides a communication method, a communication system and a related device, wherein the method is applied to a first terminal, and comprises the following steps: generating a first message, wherein the first message comprises recording suppression information; the first message is sent to the second terminal, the first message is used for establishing a call with the second terminal, the recording inhibition information is used for inhibiting the second terminal from implementing the method for the recording function of the call, and the electronic equipment can add the recording inhibition information in the sent message for establishing the session in the process of establishing the session so as to limit the recording authority of the opposite terminal and ensure the personal privacy of the user at the home terminal.

Description

Communication method, communication system and related device

Technical Field

The present application relates to the field of terminal technology, and in particular to a communication method, a communication system and related devices.

Background technique

Nowadays, making calls through mobile phones, smart watches and other devices has become an indispensable part of our daily communication and entertainment. In today's call scenarios, the other end user can record the call between the two parties without the permission of the local user or even without informing the local user. Even if the local user does not want the other party to use the recording function during the call, the other end user can still record the call, and the user's privacy and security cannot be guaranteed.

Therefore, how to improve the privacy and security of users during calls is an urgent problem to be solved.

Summary of the invention

The purpose of the present application is to provide a communication method, a communication system and related devices. When the method is implemented, the electronic device can add recording suppression information to the message sent for establishing a session during the process of establishing a session, so as to limit the recording authority of the terminal on the other side and ensure the personal privacy of the user on the local side.

The above-mentioned and other objects are achieved by the features of the independent claims. Further implementations are reflected in the dependent claims, the description and the drawings.

In a first aspect, the present application provides a communication method, applied to a first terminal, the method comprising: generating a first message, the first message comprising recording suppression information; sending the first message to a second terminal, the first message being used to establish a call with the second terminal, the recording suppression information being used to suppress a recording function of the second terminal for the call.

In this method, the first terminal may be a calling terminal or a called terminal.

In the case where the first terminal is the calling terminal, the second terminal is the called terminal. Accordingly, the first message is a request message generated by the calling terminal, and the request message indicates that the first terminal requests to establish a session with the second terminal. The first message can be sent to the second terminal through the core network. Specifically, the first message can be a Setup message or an Invite message. After the second terminal receives the first message, the second terminal can parse the first message, and after determining that the request message carries the recording suppression information, the second terminal will actively suppress its recording function in this call.

In the case where the first terminal is the called end, the second terminal is the calling end. Correspondingly, the first message is a response message generated by the called end after receiving the request message sent by the calling end. The response message is used to respond to the request message of the calling end and establish a session with the calling end. The first message may also be sent to the first terminal through the core network. Specifically, the first message may be a Connect message or a 200 OK message. After the first terminal receives the first message, the first terminal may parse the response message. After determining that the first message carries the recording suppression information, the first terminal will also actively suppress its recording function in this call.

In this method, the communication process between the first terminal and the second terminal should comply with the corresponding communication standard. In this method, the communication standard may specify the specific processing method of the receiving end of the recording suppression information (i.e., suppressing the recording during the call). After the second terminal receives the recording suppression information and actively suppresses the recording function, the user of the second terminal cannot turn on the recording function again in this conversation through corresponding operations, so the privacy security of the user of the first terminal during the call can be guaranteed.

In combination with the first aspect, in a possible implementation, after sending the first message to the second terminal, the method also includes: receiving a second message sent by the second terminal, the second message being used to establish the call with the second terminal, the second message including the recording suppression information; and suppressing the recording function of the call.

In this embodiment, the first terminal is the calling end, and the second terminal is the called end. Accordingly, the first message is a request message generated by the calling end, and the request message is used to request to establish a session with the second terminal. The request message can be sent to the second terminal through the core network. The second message is a response message generated by the called end after receiving the request message sent by the calling end, and the response message is used to respond to the request message of the calling end and establish a session with the calling end. The response message can also be sent to the first terminal through the core network. Specifically, the response message can be a Connect message or a 200 OK message. After the first terminal receives the response message, the first terminal can parse the response message, and after determining that the response message carries the recording suppression information, the first terminal will also actively suppress its recording function in this call.

After the first terminal receives the second message, parses the recording suppression information contained therein and actively suppresses the recording function, the user of the first terminal cannot turn on the recording function again in this session through corresponding operations, so the privacy security of the user of the second terminal (i.e., the called user) during the call can be guaranteed.

In combination with the first aspect, in a possible implementation, the first terminal communicates with the second terminal in a circuit switching domain, and the recording suppression information includes a first sequence, where the first sequence is a K-bit binary numerical sequence, and the first sequence identifies the first terminal's request to suppress the recording function of the second terminal.

In the circuit switching domain, according to the format standard defined by the 3GPP protocol, the first message may carry multiple information elements. Some of the information elements have an extension mechanism, which can be used to design or encode according to user needs to provide users with corresponding functions during the call. In this embodiment, the user can limit the recording authority of the second terminal during the call by encoding a certain information element in the first message. Specifically, the first message may include a User-to-User information element, and the User-to-User information element may include at least one byte with eight bits. The first terminal may design a corresponding binary sequence for the eight bits of the byte owned by the User-to-User information element (that is, the K=8, the first terminal assigns 0 or 1 to each bit, and obtains an eight-bit binary value sequence, such as "00001111"). In this application, the sequence can be used to represent a protocol for implementing the recording suppression function specified by the 3GPP protocol. After the second terminal receives the first message, the second terminal can parse the binary value sequence and suppress the recording function of the local terminal during the call according to the protocol for implementing the recording suppression function corresponding to the sequence.

With reference to the first aspect, in a possible implementation manner, the first message is a Setup message, and the first sequence is a sequence included in a User-User information element in the Setup message.

In combination with the first aspect, in a possible implementation, the second message is a Connect message, and the first sequence is a sequence included in a User-User information element in the Connect message.

In combination with the first aspect, in a possible implementation, the first terminal communicates with the second terminal in an IP multimedia subsystem domain, and the recording suppression information includes a character string for identifying a suppression request of the first terminal for a recording function of the second terminal.

In the multimedia subsystem domain, according to the format standard of SIP, the header field of the first message may contain many fields, and the header field of the first message also supports extension, and corresponding parameters may be added to provide corresponding functions for the user during the call. In this embodiment, the user can limit the recording authority of the second terminal during the call by adding corresponding fields to the header field of the first message. Specifically, the first message may contain a User-to-User field, and the User-to-User field may contain a string for implementing a recording suppression function, which may be used to indicate that recording is prohibited (for example, recoding-disabled or recoding=disabled, etc.). After the second terminal receives the first message, the second terminal may parse out the string for implementing a recording suppression function and suppress the recording function of this terminal during the call.

In combination with the first aspect, in a possible implementation, the first message is an Invite message, and the character string is a parameter included in a User-to-User header field of the Invite message.

In combination with the first aspect, in a possible implementation, the second message is a 200 OK message, and the character string is a parameter included in a User-to-User header field of the 200 OK message.

In a second aspect, the present application provides a communication method, applied to a second terminal, the method comprising: receiving a third message sent by the first terminal, the third message being used to establish a call with the first terminal, the third message comprising the recording suppression information; and suppressing the recording function of the call.

In this method, the second terminal may be a calling terminal or a called terminal.

In the case where the second terminal is the calling end, the first terminal is the called end. Correspondingly, the third message is a response message generated after the called end receives the request message sent by the calling end. The third message can be sent to the second terminal through the core network. Specifically, the third message can be a Connect message or a 200 OK message. After the second terminal receives the third message, the second terminal can parse the third message, and after determining that the third message carries the recording suppression information, the second terminal will actively suppress its recording function in this call.

In the case where the second terminal is the called terminal, the first terminal is the calling terminal. Accordingly, the third message is a request message generated by the calling terminal, and the third message represents that the first terminal requests to establish a session with the second terminal. The response message may also be sent to the first terminal through the core network. Specifically, the response message may be a Setup message or an Invite message. After the first terminal receives the response message, the second terminal may parse the response message, and after determining that the response message carries the recording suppression information, the second terminal actively suppresses its recording function in this call.

In the third aspect, the present application provides a communication system, which includes a calling terminal and a called terminal, the calling terminal being used to generate a request message, the request message including recording suppression information; and sending the request message to the called terminal, the request message being used to establish a call with the called terminal, the recording suppression information in the request message being used to suppress the recording function of the called terminal for the call; the called terminal being used to generate a response message, the response message including the recording suppression information; and sending the response message to the calling terminal, the response message being used to establish a call with the calling terminal, the recording suppression information in the response message being used to suppress the recording function of the calling terminal for the call.

In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the method in the first aspect or any possible implementation of the first aspect, or the method in the second aspect.

In a fifth aspect, a chip system is provided, which is applied to an electronic device, and the chip system includes one or more processors, and the processors are used to call computer instructions so that the electronic device executes a method such as the first aspect or any possible implementation of the first aspect, or the method in the second aspect.

In a sixth aspect, a computer program product comprising instructions, when the computer program product is run on an electronic device, enables the electronic device to execute the method in the first aspect or any possible implementation of the first aspect, or the method in the second aspect.

In a seventh aspect, a computer-readable storage medium is provided, comprising instructions, which, when executed on an electronic device, cause the electronic device to execute a method in the first aspect or any possible implementation of the first aspect, or a method in the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flowchart of an interaction between a calling end and a called end for a call according to an embodiment of the present application;

FIG2 is a signaling interaction diagram of a call between a calling end and a called end in a CM domain according to an embodiment of the present application;

FIG3 is a flowchart of an interaction between a calling end and a called end in a CM domain for a call according to an embodiment of the present application;

FIG4 is a structural diagram of a cell provided in an embodiment of the present application;

FIG5 is a signaling interaction diagram of a call between a calling end and a called end in an IMS domain provided by an embodiment of the present application;

FIG6 is a flowchart of an interaction between a calling end and a called end in an IMS domain for a call according to an embodiment of the present application;

FIG7 is a schematic diagram of byte contents contained in a message header field provided in an embodiment of the present application;

FIG8 is a signaling interaction diagram of a call between a calling end and a called end provided in an embodiment of the present application;

FIG9 is a flowchart of an interaction between a calling end and a called end for a call according to an embodiment of the present application;

FIG10 is a diagram of some user interfaces provided in an embodiment of the present application;

FIG. 11 is an architecture diagram of an electronic device provided in an embodiment of the present application.

Detailed ways

The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to be used as limitations to the present application. As used in the specification and appended claims of the present application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include plural expressions, unless there is a clear indication to the contrary in the context. It should also be understood that the term "and/or" used in the present application refers to and includes any or all possible combinations of one or more listed items.

To facilitate understanding, the relevant terms involved in the embodiments of the present application are first introduced below.

(1) Calling and called ends

The calling end may also be referred to as the calling party, which in this application may be an electronic device that actively initiates a call, and its user may be referred to as the calling user. Correspondingly, the called end may also be referred to as the called party, which in this application may be an electronic device that receives a call request initiated by the calling end, and its user may be referred to as the called user. For example, for two mobile phones equipped with SIM cards respectively (here it is assumed that the two mobile phones are Tel1 and Tel2, and the mobile phone numbers corresponding to the SIM cards they are equipped with are No.1 and Nol.2 respectively), Tel1 can make a call with Tel2 by dialing mobile number No.2. In this case, Tel1 is the calling end and Tel2 is the called end.

After receiving the call request sent by the calling party, the called party can choose to accept the call request and talk to the calling party, or reject the call request and not talk to the calling party. Of course, during the entire call process (including before the called party formally accepts the call), the calling party can actively hang up to end the call process.

(2) Core network, circuit switching domain, IP multimedia subsystem domain

The mobile network that users access daily can be divided into three parts: the base station subsystem, the network subsystem, and the system support part (such as security management). The core network part is located in the network subsystem and is used to connect the call request or data request from port A to a collection of devices on different networks. For ease of understanding, the core network can be regarded as a "very complex enhanced router". The access network is the "window" responsible for collecting data; the bearer network is the "truck" responsible for transporting data; and the core network is the "management center" responsible for managing this data, sorting the data, and then planning the destination for the data. It can be understood that the processing and distribution of data (actually "routing and switching") is the essence of the core network.

The data transmission domains involved in the core network mainly include the circuit switching domain and the IP multimedia subsystem domain.

Circuit switched (CS) is usually used for voice calls. When data is transmitted in the CS domain, a connection for data transmission must be established first. Data transmission will not start until the establishment is complete. This connection will not be disconnected until the data transmission is completed. The connection can only be released. Therefore, the characteristic of a link being circuit switched is that it occupies a link exclusively and is always used for data transmission.

IP multimedia subsystem (IMS) is a new form of multimedia service. It is a new generation of communication exchange technology standard that realizes the integration of fixed network communication and mobile communication. The current 4G and 5G communication exchange capabilities of operators are all carried by the IMS system. Different from the traditional CS (circuit switching) voice solution, the protocols and interfaces used by IMS all follow the TCP/IP protocol stack. One of the most critical protocols is the session initiation protocol (SIP). As the control protocol in IMS, the SIP protocol can carry the content of SDP (Session Description Protocol) in its corresponding protocol message. It has the characteristics of simplicity, flexibility, easy expansion, and convenient media negotiation, which improves the future adaptability of the network. Generally speaking, SIP protocol messages can be divided into two categories: request messages and response messages. The request message is sent by the user agent client (which can be understood as the calling end) to the user agent server (which can be understood as the called end), and the response message is sent by the user agent server to the user agent client.

When the terminal calls or receives a call in the CS domain, it follows the 3GPP protocol. When calling or receiving a call in the IMS domain, it follows the SIP protocol. If the calling terminal and the called terminal are not in the same domain, the core network will perform signaling processing conversion.

(3) User-to-User Information

User-to-User is a signaling information transmitted end-to-end. In the CS domain, User-to-User information can be transmitted in the Setup message and Connect message in the form of User-User information (UUI) information element. In the IMS domain, User-to-User information can be transmitted in the Invite message and 200 OK message in the form of SIP User-to-User Header field.

When terminals communicate with each other based on the core network, the core network only transmits the information without performing any additional processing.

If the calling end and the called end are in the same domain, User-to-User will be transparently transmitted. If the calling end and the called end are not in the same domain, the User-to-User information contained in the command information sent by one end will be converted into signaling and cells before transmission.

In addition, User-to-User information also has an extension mechanism, that is, User-to-User information can be re-encoded to provide corresponding functions for the calling end and the called end during the call process. For example, in this application, the user can limit the recording rights of the calling end and/or the called end during the call process by designing a corresponding binary sequence for the User-User information element or adding parameter content in the User-to-User Header to protect the privacy and security of both parties during the call process. For details, please refer to the subsequent instructions, which will not be repeated here.

Nowadays, making calls through mobile phones, smart watches and other devices has become an indispensable part of our daily communication and entertainment. In today's call scenarios, the other end user can record the call between the two parties without the permission of the local user or even without the local user's knowledge. Even if the local user does not want the other party to use the recording function during the call, the other end user can still record the call, and the user's privacy and security cannot be guaranteed.

FIG1 is an interactive flow chart of a call between a calling terminal and a called terminal provided by the present application. As shown in FIG1, a terminal 101 and a terminal have established a communication connection through a request message, wherein the terminal 101 can be the calling terminal, and the terminal 102 can be the called terminal. Users of the two terminals can talk through the two terminals, and the interactive process may include the following steps:

S101: The terminal 101 records the call in response to the user operation.

After the terminal 101 and the terminal 102 establish a call and formally start a conversation, the terminal 101 can record the call content of the entire subsequent call through the above user operation. Specifically, the user operation can be the operation of the user of the terminal 101 clicking the "recording" function option in the call interface of the terminal 101.

S102: Terminal 101 sends prompt information to terminal 102.

After terminal 101 turns on the call recording function based on the user operation, terminal 101 can send the above-mentioned prompt information to terminal 102. The prompt information can be used to notify terminal 102 that terminal 101 has turned on call recording. Subsequently, all conversation contents between the two users of terminal 101 and terminal 102 during the entire call process will be recorded and saved by terminal 101.

S103: After receiving the prompt information, the terminal 102 prompts the user that the other party has turned on call recording.

After receiving the above prompt information, terminal 102 will inform the user of terminal 102 that terminal 101 has enabled call recording in some form. Specifically, terminal 102 may broadcast a voice message to remind the user on the other side of terminal 102 (that is, the user of terminal 101) that the call recording function has been enabled; or terminal 102 may display a text message in the call interface to remind the user on the other side of terminal 102 (that is, the user of terminal 101) that the call recording function has been enabled.

As can be seen from Figure 1 and the above description, during the entire call process, after the user on the other side turns on the call recording function, although the user on this side can know that the user on the other side has turned on the call recording function, the user on the other side can still turn on the recording without asking for the permission of the user on this side. In other words, when the conversation between the two parties involves the privacy information of both parties, and one or both users do not want the other party to record the call, the calling party and the called party can still record the entire call content without obtaining the permission of the other party, resulting in the personal privacy and security demands of both parties in the conversation not being guaranteed.

In response to the defects existing in the above-mentioned call process, the present application provides a communication method. During the process of establishing a session between the calling end and the called end, the communication method can add recording suppression information in the message sent by the calling end and/or the called end for establishing the session, so as to limit the recording authority of the terminal on the other side and ensure the personal privacy of the user on this side.

It should be noted in advance that in an actual communication scenario, the data of the calling and called ends involved in the call may be in the CS domain at the same time, or in the IMS domain at the same time, or one party may be in the CS domain and the other party may be in the IMS domain. Because different data transmission domains have different communication protocol regulations, and the difference in communication protocols will affect the difference in messages sent and received by the two terminals during the session establishment process, and thus affect the message type and format of the recording suppression information. Therefore, the communication method provided by this application will be described below for different situations of the data transmission domains where the calling and called ends are located.

1. The calling end and the called end are both in the CS domain. For details, please refer to Figures 2 to 4.

First, the signaling interaction process involved in establishing a session between the calling end and the called end in the CS domain is introduced. Please refer to Figure 2 for details.

As shown in FIG. 2 , in FIG. 2 , terminal 201 and terminal 202 may be mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA) or special cameras (such as SLR cameras, card cameras), etc., and the present application does not impose any restrictions on the specific types of the electronic devices. Among them, terminal 201 is the calling end, and terminal 202 is the called end. The steps of signaling interaction involved in the process of establishing a session between the two may include:

S201: Terminal 201 sends a CM service request message to the core network.

In the process of establishing a session, the terminal 201 as the calling end will first send an initial direct transfer message, ie, the above-mentioned CM service request message, to the core network.

S202: The core network sends a CM service acceptance message to the terminal 201.

If the core network accepts the CM service request sent by the terminal 201 , the core network will send the CM service acceptance message to the terminal 201 , indicating that the request (ie, the CM service request message) previously sent by the terminal 201 has been accepted.

S203: Terminal 201 sends a call establishment request message to the core network.

After executing step S201 and step S202, terminal 201 as the calling end will continue to send a message for formally starting the call process to the core network, that is, the call establishment request message. The call establishment request message may include the called party's phone number and the services involved in the entire call process, and the core network may connect the call based on the call establishment request message.

In an embodiment of the present application, the call establishment request message may carry a User-User information element, and the User-User information element may carry recording suppression information to suppress the recording function of the terminal 202 during subsequent calls.

S204: The core network sends a call establishment progress message to the terminal 201.

When the core network receives the call establishment message from the terminal 201, it will analyze the mobile phone number of the called party (the core network stores information on various number classifications to confirm whether it has the ability to point to the number) and the capabilities of the calling party user (i.e., whether the service originally registered by the calling party supports the required services of this call, such as whether there are restrictions on international long-distance calls, and the resource capabilities of the network itself, etc.) to check whether the service requirements involved in this session can be accepted. If the core network supports the aforementioned service requirements, the core network can send the above-mentioned call establishment progress message to the terminal, indicating that the call establishment request sent by the terminal 201 as the calling party has passed the verification and the call is in progress.

After completing step S205, the bearer between the terminal 201 and the core network has been established, and the bearer can be used for the terminal 201 and the core network to transmit voice, data and multimedia service data packets in subsequent processes.

S205: The core network sends a paging message to the terminal 202.

The paging message is used by the core network to find or notify one or more terminals. The main contents carried include the identifier of the terminal to be paged, the identifier of the core network that initiated the paging, and an indication of whether the system message has changed. Because terminal 202 is mobile, its location changes dynamically, and terminal 202 may be abnormally shut down or enter a low-power state, it does not always maintain a radio resource control (RRC) connection with the base station or the core network. Therefore, when terminal 201 needs to talk to terminal 202, the core network needs to find terminal 202 first, and re-establish an RRC connection with it after waking up terminal 202.

S206: Terminal 202 sends a paging response message to the core network.

After receiving the paging message sent by the core network, terminal 202 can send the above-mentioned paging response message to the core network, indicating that it has successfully received the paging message sent by the core network and can respond to the call establishment request initiated by terminal 101.

S207: The core network sends a call establishment request message to the terminal 202.

After receiving the paging response message sent by the terminal 202 , the core network will send the call establishment request message to the terminal 202 .

If the call establishment request message carries a User-User information element, the core network will also send the User-User information element carried by the call establishment request message to the terminal 202 when sending the call establishment request message to the terminal 202. After the terminal 202 receives the call establishment request message, the terminal 202 can parse the call establishment request message to determine the recording suppression information carried by the User-User information element contained therein, and the terminal 202 will actively suppress its recording function in the subsequent call process; it should be noted that the operation of the terminal 202 to suppress the recording function is actively performed by the terminal 202 under the instruction of the recording suppression information, and this process is not affected by the operation of the called user (i.e., the user of the terminal 202), and the user of the terminal 202 cannot turn on the call recording function through operation in the subsequent process.

S208: Terminal 202 sends a call establishment confirmation message to the core network.

After receiving the call establishment request message sent by the core network, the terminal 202 will reply a call establishment confirmation message to the core network, indicating that the terminal 202 has received all the messages required to establish the call connection.

After completing step S208, the bearer between the terminal 202 and the core network has been established, and the bearer can be used for the terminal 202 and the core network to transmit voice, data and multimedia service data packets in subsequent processes.

S209: Terminal 202 sends a call reminder message to the core network.

S210: The core network sends a call reminder message to the terminal 201.

After the terminal 202 sends the call establishment confirmation message, it indicates that the call sent by the terminal 201 has been received, and the call sent by the terminal 201 is in the process of waiting for answering. At this time, the terminal 202 will send the call reminder message to the terminal 201 via the core network, indicating that the terminal 202 has received the call request of the terminal 201 and is in the "ringing" state. In the traditional call system, the call reminder message is usually carried out in the form of a prescribed tone or ringing sound to indicate that the called party has received the call request and is about to start answering. Through the call reminder message, the caller can know that the telephone line is connecting to the called party and is waiting for answering.

S211: Terminal 202 sends a call connection message to the core network.

S212: The core network sends a call connection message to the terminal 201.

If terminal 202 answers the call under user operation (for example, the user presses the answer button), terminal 202 will send the above-mentioned call connection message to terminal 201 through the core network, indicating that the link between the calling end and the called end is connected. At this time, the call establishment process is completed, and both parties enter the call or data transmission service stage.

In an embodiment of the present application, the above-mentioned call connection message may also carry the above-mentioned User-User information element, and the User-User information element in the call connection message may also carry recording suppression information to suppress the recording function of the terminal 201 during subsequent calls.

Specifically, if the above call connection message carries a User-User information element, the core network will also send the User-User information element carried by the above call establishment connection message to the terminal 201 when sending the above call establishment connection message to the terminal 201. After the terminal 201 receives the call establishment connection message, the terminal 201 can parse the call establishment connection message to determine the recording suppression information carried by the User-User information element contained therein, and the terminal 201 will actively suppress its recording function in the subsequent call process. Similarly, the operation of the terminal 201 to suppress the recording function is actively performed by the terminal 201 under the instruction of the recording suppression information. This process is not affected by the operation of the calling user (i.e., the user of the terminal 201), and the user of the terminal 201 cannot turn on the call recording function through operation in the subsequent process.

In the embodiment of the present application, the signaling interaction operations involved in the above-mentioned call establishment process are only examples. In the actual call establishment process, the signaling interaction process between the calling end and the called end may include more or fewer operations. In addition, in the embodiment of the present application, the signaling sent and received between the calling end and the called end may also be called other names, and the present application does not limit this. For example, the above-mentioned CM service request message may also be called CM Service Request, the above-mentioned CM service response message may also be called CM Service Accept, the above-mentioned call establishment request message may also be called Setup, the above-mentioned call establishment proceeding message may also be called Call Proceeding, the above-mentioned paging message may also be called Paging, the above-mentioned paging response message may also be called Paging Response, the above-mentioned call reminder message may also be called Alerting, and the above-mentioned call connection message may also be called Connect.

FIG3 is an interactive flow chart of a communication method provided in an embodiment of the present application, which is based on FIG2 and combines user operations to illustrate the specific process of the calling end and the called end implementing the function of suppressing the recording of the other end during the communication process. As shown in FIG3, the interactive process may include:

S301: The terminal 201 starts a function of suppressing recording of the other end in response to a first operation.

When terminal 201 calls terminal 202, if the calling user does not want the called user to have the right to record the call, the calling user can enable the recording function of the other party (i.e., terminal 202) through the above-mentioned first operation. Specifically, the above-mentioned first operation can be the operation of the calling user long pressing the dial key in the dial interface shown by the terminal 201 (for details, please refer to the subsequent description), or the operation of the calling user issuing a voice command to the terminal 201 (for example, the calling user says the command "make a call to XXX to prohibit recording" to the terminal 201).

S302: The terminal 201 sends a call establishment request message to the core network. The User-User information element of the call establishment request message includes the first recording suppression information.

S303: The core network sends a call establishment request message to the terminal 202.

After detecting the first operation, in the subsequent process of establishing a call with the terminal 202, the call establishment request message sent by the terminal 201 to the core network may carry a User-User information element, and the User-User information element may include the first recording suppression information. When the core network subsequently sends the call establishment request message to the terminal 202, the first recording suppression information will be sent to the terminal 202 along with the call establishment request message.

S304: When the terminal 202 detects that the User-User information element in the call establishment request message includes the first recording suppression information, the terminal 202 suppresses the call recording function at the local end.

After the terminal 202 receives the call establishment request information sent by the core network, the terminal 202 can analyze whether the User-User information element in the call establishment request information carries the first recording suppression information. In the case of determining that the User-User information element contained therein carries the first recording suppression information, the terminal 202 will actively suppress its recording function in the subsequent call process, and the called user will not be able to turn on the call recording function through operation in the subsequent process.

S305: The terminal 202 starts the function of suppressing the recording of the other end in response to the second operation.

When terminal 202 responds to the call of terminal 201, if the called user does not want the calling user to have the right to record the call, the called user can enable the recording function of the other party (i.e., terminal 201) through the above second operation. Specifically, the above second operation can be the operation of the called user long pressing the dial key in the call interface displayed by terminal 202 (for details, please refer to the subsequent description), or the operation of the called user issuing a voice command to terminal 202 (for example, after terminal 202 receives the call from terminal 201, the called user speaks the command "answer, prohibit recording" to terminal 202).

S306: The terminal 202 sends a call connection message to the core network, and the User-User information element of the call connection information includes the first recording suppression information.

S307: The core network sends a call connection message to the terminal 201.

Similarly, after detecting the second operation, the call connection message sent by the terminal 202 to the core network may also carry a User-User information element, and the User-User information element may also include the first recording suppression information. When the core network subsequently sends the call connection message to the terminal 201, the first recording suppression information will be sent to the terminal 201 along with the call connection message.

S308: When the terminal 201 detects that the User-User information element in the call connection message includes the first recording suppression information, the terminal 201 suppresses the call recording function at the local end.

After the terminal 201 receives the call establishment request information sent by the core network, the terminal 201 can analyze whether the User-User information element in the call establishment request information carries the first recording suppression information. If it is determined that the User-User information element contained therein carries the first recording suppression information, the terminal 201 will actively suppress its recording function in the subsequent call process, and the calling user will not be able to turn on the call recording function through operation in the subsequent process.

It should be noted that, in some embodiments, only one of the terminal 201 and the terminal 202 may enable the operation of suppressing the recording function of the other party. For example, during the call establishment process, if the user of the terminal 201 performs the above-mentioned first operation, but the user of the terminal 202 does not perform the above-mentioned second operation, at this time, only the call establishment request message sent by the terminal 201 to the terminal 202 via the core network contains the above-mentioned first recording suppression information, and the call connection message sent by the terminal 202 to the terminal 201 via the core network does not contain the above-mentioned first recording suppression information. In this case, the terminal 202 will not be able to record in subsequent calls, but the terminal 201 can record. Correspondingly, during the call establishment process, if the user of the terminal 201 does not perform the above-mentioned first operation, but the user of the terminal 202 does not perform the above-mentioned second operation, the call establishment request message sent by the terminal 201 to the terminal 202 via the core network will not contain the above-mentioned first recording suppression information, but the call connection message sent by the terminal 202 to the terminal 201 via the core network contains the above-mentioned first recording suppression information. In this case, the terminal 201 will not be able to record in subsequent calls, but the terminal 202 can record. However, no matter whether both the calling party and the called party have the recording suppression function enabled or only one party in the call has the recording suppression function enabled, the calling party and the called party can still have a normal conversation.

Next, the structure of the above-mentioned User-User cell and the specific format of the first recording suppression information contained in the User-User cell are described in conjunction with FIG. 4 .

First of all, it should be noted that in the CM domain, according to the format standard defined by the 3GPP protocol (i.e., 3rd generation partnership project, which is a globally applicable communication technology specification and technical report developed since the third generation mobile communication system in 1998, covering all aspects of mobile communication technology), in the above call establishment request message and call connection message, the User-User information element can be composed of multiple bytes, each of which contains eight bits. In the 3GPP protocol, each byte contained in the User-User information element can be encoded, that is, the eight bits contained in each information element can be assigned a binary value (i.e., "0" or "1"), and an eight-bit binary value sequence is obtained, which can be used to represent a communication protocol specified by the 3GPP protocol.

As shown in FIG4 , byte 40 may be a byte included in the above User-User information element, which has eight bits, each of which may have a value of “0” or “1”. It can be understood that there are 256 possible binary value sequences corresponding to the byte, each of which may be used to represent a communication protocol specified by the 3GPP protocol. However, in the current 3GPP protocol, the number of binary value sequences that have been used to represent a communication protocol does not reach 256. That is to say, the above 256 binary value sequences can be divided into two categories, one of which is a sequence that has been used to represent a certain communication protocol, such as sequence 411 (i.e., "00000001", which represents an OSI high-level protocol) and sequence 412 (i.e., "00000010", which represents the X.244 protocol, an obsolete protocol) shown in sequence table 41 in Figure 4, and the other is a sequence that has not yet been used to represent any communication protocol (here it is assumed that "01010101" and "10101010" are not used to represent any communication protocol), such as sequence 413 (i.e., "01010101") and sequence 414 (i.e., "10101010") shown in Figure 4. Since these sequences are not occupied to represent a certain communication protocol, these sequences can be set as sequences representing a certain protocol (or used to implement a certain function that the user needs to achieve in communication) according to user needs, and this application does not limit this.

For example, in an embodiment of the present application, sequence 414 (i.e., "10101010") can be set as a sequence for suppressing the terminal recording function during the communication process. In this case, sequence 414 is the above-mentioned first recording suppression information. In this case, when terminal 201 parses the received call connection message and finds that there is a byte in the User-User cell, and its eight bits form a binary numerical sequence of "10101010", terminal 201 will actively suppress the call recording function, and the calling user will not be able to record the current call. Similarly, when terminal 202 parses the received call service request message and finds that there is a byte in the User-User cell, and its eight bits form a binary numerical sequence of "10101010", terminal 201 will also actively suppress the call recording function, and the called user will not be able to record the current call.

It should be understood that FIG. 4 only exemplarily shows the specific format of bytes in the User-User cell, which does not constitute any limitation. In addition, in the current 3GPP protocol, for the binary value sequence composed of bytes in the User-User cell, the sequence that has been occupied to represent a certain communication protocol is determined, so among the 256 binary value sequences that can be composed of eight bits, except for this part of the occupied sequence, any unoccupied sequence can be set as a sequence to realize the suppression of the terminal recording function during the communication process, and this application does not limit this.

S309: When the call is connected, the terminal 201 outputs a prompt message.

S310: When the call is connected, the terminal 202 outputs a prompt message.

After terminal 202 receives the call from terminal 201, if the user presses the answer key in the call interface displayed on terminal 202, the call between the two terminals is connected, and the users of the two terminals can start the call.

When the call is connected, both terminals can inform the user on the local side whether the user on the other side has enabled the function of suppressing call recording during the call.

Specifically, after the call is connected, if the calling end (i.e., terminal 201) enables the suppression of recording on the other end (i.e., terminal 202) in response to the user's first operation, the above-mentioned prompt information output by terminal 201 may include "This call will not be recorded", and accordingly, the above-mentioned prompt information output by terminal 202 may include "This call is not allowed to be recorded". The prompt information can be broadcasted by terminal 201 and terminal 202 in the form of voice, or displayed in the form of text on the call interface of terminal 201 and terminal 202, respectively. The present application does not limit this.

Similarly, when the called end (i.e., terminal 202) enables suppression of recording on the other end (i.e., terminal 201) in response to the user's second operation, the prompt information output by terminal 202 may include “This call is not allowed to be recorded”, and correspondingly, the prompt information output by terminal 201 may include “This call will not be recorded”.

Optionally, if the calling end does not enable (does not support) the recording suppression function, but the called end enables the recording suppression function, the calling end may not play a voice message to inform the called user, but at this time the called user has the right to play a voice message to inform the calling user, that is, the above prompt information output by the calling end (terminal 201) only includes "This call is not allowed to be recorded". If the called end does not enable (does not support) the recording suppression function, no voice message is played to inform the calling user, but at this time the calling user has the right to play a voice message to inform the called user, that is, the above prompt information output by the called end (terminal 202) only includes "This call is not allowed to be recorded". If both the calling end and the called end enable the function of suppressing the recording of the other end, then the above prompt information output by the calling end and the above prompt information output by the called end may both include "This call will not be recorded and this call is not allowed to be recorded", indicating that both parties of the call have enabled the recording suppression function.

By implementing the communication method, in the CS domain, both the calling end and the called end can suppress the recording function of the other end during the call without affecting the call, which can effectively ensure the privacy security of the user during the call.

In the present application, terminal 201 and terminal 202 may both be referred to as a "first terminal" or a "second terminal", the above-mentioned first recording suppression information may also be referred to as "recording suppression information", and sequence 414 may be referred to as a "first sequence".

Specifically, when terminal 201 is the "first terminal", terminal 202 is the "second terminal", the call establishment request message can be called the "first message", and the call connection message can be called the "second message".

Correspondingly, when terminal 202 is the "first terminal", terminal 201 is the "second terminal", and the above call connection message can be called the "first message".

2. The calling end and the called end are both in the IMS domain. For details, please refer to Figures 5 to 7.

First, the signaling interaction process involved in establishing a session between a calling end and a called end in an IMS domain is introduced. Please refer to FIG. 5 for details.

As shown in FIG5 , in FIG5 , terminal 501 and terminal 502 may be mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA) or special cameras (such as SLR cameras, card cameras), etc., and the present application does not impose any restrictions on the specific types of the electronic devices. Among them, terminal 501 is the calling end, and terminal 502 is the called end. The steps of signaling interaction involved in the process of establishing a session between the two may include:

S501: Terminal 501 sends a call request message to the core network.

S502: The core network sends a call request message to the terminal 502.

In the IMS domain, the calling end (i.e., terminal 501) and the called end (i.e., terminal 502) communicate with each other in accordance with the session initiation protocol (SIP) (e.g., VoLTE, VoWIFI, VoNR calls, etc.). The SIP protocol is a request-response signaling protocol similar to the HTTP protocol, which is used to initiate, manage, and terminate voice and video sessions in the network, specifically, to generate, modify, and terminate sessions between one or more participants.

According to the SIP protocol, when initiating a session, the calling end needs to initiate a call request message to implement the process. Therefore, in the IMS domain, after the calling user dials the terminal 502 through the terminal 501, the terminal 501 will first initiate a call request message, and the call request message will be sent to the terminal 502 via the core network.

Specifically, the call request message may include a series of header fields, which contain many attributes and additional information of the transmitted message, such as a unique call identifier, a destination address, an address of the calling party, and a session type of the current session; the session type may be pure voice, or it may be multimedia video or other types used for network conferencing.

In the embodiment of the present application, the call request message may also carry a User-to-User header field, and the User-to-User header field may carry recording suppression information to suppress the recording function of the terminal 502 in the subsequent call process. Specifically, when the core network sends the call establishment message to the terminal 502, the core network will also send the User-to-User header field in its header field to the terminal 502. After the terminal 502 receives the call request message, the terminal 502 can parse the call request message. If it is determined that the User-to-User header field contained therein carries recording suppression information, the terminal 502 will actively suppress its recording function in the subsequent call process. It should be noted that the operation of suppressing the recording function of the terminal 502 is actively performed by the terminal 502 under the instruction of the recording suppression information. This process is not affected by the operation of the called user (i.e., the called user), and the called user cannot turn on the call recording function through operation in the subsequent process.

S503: The terminal 502 sends a connection progress message to the core network.

S504: The core network sends a connection progress message to the terminal 501.

After the terminal 502 successfully receives the call request message sent by the terminal 501 via the core network, the terminal 502 may send the connection progress message to the terminal 501 via the core network. The connection progress message may be used as a temporary response message to the call request message, and is used to indicate to the terminal 501 that the terminal 502 has correctly received the call request message, so as to prevent the delay in the core network and the terminal 202 processing the call request message from causing the terminal 501 to keep resending the call request message.

S505: Terminal 502 sends a ringing message to the core network.

S506: The core network sends a ringing message to the terminal 501.

After the terminal 502 sends the above connection completion message, the terminal 502 will then send a ringing message to the terminal 501 via the core network, indicating that the call sent by the terminal 501 has been received, and the call sent by the terminal 201 is in the process of waiting for answering, and the terminal 502 has received the call request from the terminal 101 and is in the "ringing" state. Through the ringing message, the caller can know that the telephone line is connecting to the called party and is waiting for answering.

S507: Terminal 502 sends a connection success message to the core network.

S508: The core network sends a connection success message to the terminal 501.

After the terminal 502 starts ringing and the called user responds to the calling user's call request (for example, the user presses the answer key), the terminal 502 sends the above connection success message to the terminal 501 through the core network.

Specifically, the call request message may also include a series of header fields, which contain many fields and additional information of the transmitted message, such as a unique call identifier, a destination address, an address of the calling party, and a session type of the current session; the session type may be pure voice, or it may be multimedia video or other types used for network conferencing.

In the embodiment of the present application, the above-mentioned connection success message can also carry the above-mentioned User-to-User header field, and the User-to-User header field can also carry recording suppression information to suppress the recording function of the terminal 501 in the subsequent call process. Specifically, when the core network sends the above-mentioned connection success message to the terminal 501, the core network will also send the second recording suppression information carried by the User-to-User header field to the terminal 501. After the terminal 501 receives the call request message, the terminal 501 can parse the call request message. If it is determined that the User-to-User header field contained in its header field carries recording suppression information, the terminal 501 will actively suppress its recording function in the subsequent call process. Similarly, the operation of suppressing the recording function of the terminal 501 is actively performed by the terminal 501 under the instruction of the recording suppression information. This process is not affected by the operation of the calling user (i.e., the calling user), and the calling user cannot turn on the call recording function through operation in the subsequent process.

After completing step S508, the bearer between the terminal 502 and the core network has been established, and the bearer can be used for the terminal 502 and the core network to transmit voice, data and multimedia service data packets in subsequent processes.

S509: Terminal 501 sends a confirmation message to the core network.

S510: The core network sends a confirmation message to the terminal 502.

Afterwards, the terminal 501 may reply the above confirmation message to the terminal 502 through the core network, indicating that it has successfully received the above connection success message sent by the terminal 502.

Afterwards, the terminal 501 and the terminal 502 can start a conversation, and receive and send media packets in a manner specified by the SIP protocol.

In the embodiment of the present application, the signaling interaction operations involved in the call establishment process are only examples. In the actual call establishment process, the signaling interaction process between the calling end and the called end may include more or fewer operations. In addition, in the embodiment of the present application, the signaling sent and received between the calling end and the called end may also be called other names, which are not limited in the present application. For example, the call request message may also be called Invite, the connection progress message may also be called 100 Trying, the ringing message may also be called 180 Ring, the connection success message may also be called 200 OK, and the confirmation message may also be called ACK.

FIG6 is an interactive flow chart of a communication method provided in an embodiment of the present application, which is based on FIG5 and combines user operations to illustrate the specific process of the calling end and the called end implementing the function of suppressing the recording of the other end during the communication process. As shown in FIG6, the interactive process may include:

S601: The terminal 501 starts a function of suppressing recording of the other end in response to a first operation.

When terminal 501 calls terminal 502, if the calling user does not want the called user to have the right to record the call, the calling user can enable the suppression of the recording function of the other party (i.e., terminal 502) through the above-mentioned first operation. Specifically, the above-mentioned second operation can be the operation of the calling user long pressing the dial key in the call interface shown by terminal 501 (for details, please refer to the subsequent description), or the operation of the calling user issuing a voice command to terminal 501 (for example, after the calling user receives the call from terminal 501, the calling user speaks the command "answer, prohibit recording" to terminal 501).

S602: The terminal 501 sends a call request message to the core network. The User-to-User header field of the call request message includes second recording suppression information.

S603: The core network sends a call request message to the terminal 502.

After detecting the first operation, in the subsequent process of establishing a call with the terminal 502, the call request message sent by the terminal 501 to the core network may carry a User-to-User header field, and the User-to-User header field may include the second recording suppression information. When the core network subsequently sends the call request message to the terminal 502, the first recording suppression information will be sent to the terminal 502 along with the call establishment message.

S604: When the terminal 502 detects that the User-to-User header field in the call establishment request message includes the second recording suppression information, the terminal 502 suppresses the call recording function of the local end.

After the terminal 502 receives the call request information sent by the core network, the terminal 502 can analyze whether the User-to-User header field in the call establishment request information carries the second recording suppression information. If it is determined that the User-to-User header field contained therein carries the second recording suppression information, the terminal 502 will actively suppress its recording function in the subsequent call process, and the called user will not be able to turn on the call recording function through operation in the subsequent process.

S605: The terminal 502 starts the function of suppressing the recording of the other end in response to the second operation.

When terminal 502 responds to the call of terminal 501, if the called user does not want the calling user to have the right to record the call, the called user can enable the suppression of the recording function of the other party (i.e., terminal 501) through the above second operation. Specifically, the above second operation can be the operation of the called user long pressing the dial key in the call interface displayed by terminal 502 (for details, please refer to the subsequent description), or the operation of the called user issuing a voice command to terminal 502 (for example, after terminal 502 receives the call from terminal 501, the called user speaks the command "answer, prohibit recording" to terminal 502).

S606: The terminal 502 sends a connection message to the core network. The User-to-User header field of the connection success message includes the second recording suppression information.

S607: The core network sends a connection success message to the terminal 501.

Similarly, after detecting the second operation, in the subsequent process of establishing a call with the terminal 501, the connection success message sent by the terminal 502 to the core network may also carry the User-to-User header field, and the User-to-User header field may include the second recording suppression information. When the core network subsequently sends the connection success message to the terminal 501, the second recording suppression information will be sent to the terminal 501 along with the call establishment message.

S608: When the terminal 501 detects that the User-to-User header field in the connection success message includes the second recording suppression information, the terminal 501 suppresses the call recording function at the local end.

After the terminal 501 receives the above connection success message sent by the core network, the terminal 501 can parse the field in the connection success message to see whether it carries the second recording suppression information. If it is determined that the User-to-User header field contained therein carries the second recording suppression information, the terminal 501 will actively suppress its recording function in the subsequent call process, and the calling user will not be able to turn on the call recording function through operation in the subsequent process.

It should be noted that, in some embodiments, only one of the terminal 501 and the terminal 502 may enable the operation of suppressing the recording function of the other party. For example, during the call establishment process, if the calling user (i.e., the user of the terminal 501) performs the above-mentioned first operation, but the called user (i.e., the user of the terminal 502) does not perform the above-mentioned second operation, at this time, only the call request message sent by the terminal 501 to the terminal 502 via the core network contains the above-mentioned second recording suppression information, and the connection success message sent by the terminal 502 to the terminal 501 via the core network does not contain the above-mentioned second recording suppression information. In this case, the terminal 502 will not be able to record in subsequent calls, but the terminal 501 can record. Correspondingly, during the call establishment process, if the calling user does not perform the above-mentioned first operation, but the called user performs the above-mentioned second operation, the call request message sent by the terminal 501 to the terminal 502 via the core network will not contain the above-mentioned second recording suppression information, but the connection success message sent by the terminal 502 to the terminal 501 via the core network contains the above-mentioned second recording suppression information. In this case, the terminal 501 will not be able to record in subsequent calls, but the terminal 502 can record. However, no matter whether both the calling party and the called party have the recording suppression function enabled or only one party in the call has the recording suppression function enabled, the calling party and the called party can still have a normal conversation.

Next, the structure of the above-mentioned User-to-User header field and the specific format of the second recording suppression information contained in the User-to-User header field are described in conjunction with FIG. 7 .

First of all, it should be noted that, unlike in the CM domain, in the IMS domain, according to the format standard defined by the SIP protocol, in the above-mentioned call request message and the connection success message, the User-to-User header field and the fields in the User-to-User header field contained in the above-mentioned call request message and the connection success message do not exist in binary format, but in the form of a string. In addition, these header fields and information elements are inserted into the above-mentioned call request message and the connection success message by an application (which may be a call software or application in the embodiment of the present application) as UUI data, and are used to start/accept the data of the previous session between the calling end and the called end. Specifically, in the embodiment of the application, the above-mentioned User-to-User header field may be a newly defined field, and the parameters contained in the User-to-User header field may be expanded according to the specific business involved in the session to implement the corresponding business function in the session. For example, in the present application, the User-to-User header field may contain the above-mentioned second recording suppression information to suppress the recording function of the terminal during the call.

(A) and (B) in FIG. 7 respectively show specific formats of a call request message not including the second recording suppression information and a call request message including the second recording suppression information.

As shown in (A) of FIG. 7 , the header field of the call request message 71 includes a User-to-User header field 711 and multiple header fields such as header field 712. Among them, in addition to the User-to-User header field 711, several fields including header field 712 are required for all message bodies; taking header field 712 as an example, the header field carries information such as the request method, request address, and SIP version number involved in this call request. However, since the call request message 71 is a request message sent by the calling end to the called end without starting the function of suppressing the recording of the other end, the User-to-User header field 711 in the call request message 71 only includes two parameter information "342342ef34" (indicating the protocol number) and "encoding=hex" (indicating encoding in hexadecimal), and does not include the above-mentioned second recording suppression information for suppressing the recording of the called end in the subsequent process. Therefore, after the called end receives the call request message 70, the called end will not suppress the recording suppression function of the call, the called user can record the call normally, and the privacy of the calling user cannot be guaranteed.

As shown in (B) of FIG. 7 , the call request message 72 includes a User-to-User header field 721 and other necessary fields. The call request message 72 is a request message sent by the calling end to the called end when the function of suppressing the recording of the other end is activated. Therefore, unlike the User-to-User header field 711 shown in (A) of FIG. 7 , the User-to-User header field 721 in the call request message 72 not only includes the two parameter information "342342ef34" and "encoding=hex", but also includes the above-mentioned second recording suppression information for suppressing the recording of the called end in the future, that is, the parameter information "recording=disabled" in the User-to-User header field 721. Therefore, after the called end receives the call request message 72, the called end will detect the recording suppression information in this field and actively suppress the recording suppression function of the call. The called user cannot record the call, and the privacy and security of the calling user during the call is guaranteed.

Similarly, the specific styles of the header fields of the connection success message that does not include the second recording suppression information and the connection success message that includes the second recording suppression information can also refer to the aforementioned description of FIG. 7 , which will not be repeated here.

It should be noted that FIG. 7 only exemplarily shows the specific style of the header field in the call request message, which does not constitute any limitation. For example, in some embodiments, the User-to-User header field may not exist in the call request message that does not include the second recording suppression information. In addition, in some embodiments, the parameter format corresponding to the second recording suppression information may also be in other styles, such as "recording=0", "recording=false", etc., or the parameters in the User-to-User header field may only include the parameters corresponding to the second recording suppression information, which is not limited in this application.

S609: When the call is connected, the terminal 501 outputs a prompt message.

S610: When the call is connected, the terminal 502 outputs a prompt message.

After terminal 502 receives the call from terminal 501, if the user presses the answer key in the call interface displayed on terminal 502, the call between the two terminals is connected, and the users of the two terminals can start talking.

When the call is connected, both terminals can inform the user on the local side whether the user on the other side has granted the permission to record the call during the call.

Specifically, the specific operations of step S609-step S610 can refer to the aforementioned description of step S309-step S310, which will not be repeated here.

By implementing the communication method, in the IMS domain, both the calling end and the called end can suppress the recording function of the other end during the call without affecting the call, which can effectively ensure the privacy security of the user during the call.

In the present application, terminal 501 and terminal 502 can both be referred to as the "first terminal" or the "second terminal", the above-mentioned second recording suppression information can also be referred to as "recording suppression information", and the parameter information "recording=disabled" can be referred to as "a character string identifying the first terminal's request to suppress the recording function of the second terminal".

Specifically, when terminal 501 is the "first terminal", terminal 502 is the "second terminal", the call request message can be called the "first message", and the connection success message can be called the "second message".

Correspondingly, when terminal 502 is the "first terminal", terminal 501 is the "second terminal", and the above connection success message can be called the "first message".

3. One of the calling end and the called end is in the CS domain, and the other is in the IMS domain. For details, please refer to Figures 8 and 9.

Here, the signaling interaction process involved in establishing a session between the calling end and the called end is introduced by taking the case where the calling end is in the CS domain and the called end is in the IMS domain as an example. For details, please refer to FIG. 8 .

As shown in FIG8 , in FIG8 , terminal 801 and terminal 802 may be mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA) or special cameras (such as SLR cameras, card cameras), etc., and the present application does not impose any restrictions on the specific types of the electronic devices. Among them, terminal 801 is the calling end, and terminal 802 is the called end. The steps of signaling interaction involved in the process of establishing a session between the two may include:

S801: Terminal 801 sends a CM service request message to the core network.

S802: The core network sends a CM service acceptance message to the terminal 801.

S803: Terminal 801 sends a call establishment request message to the core network.

S804: The core network sends a call establishment progress message to the terminal 801.

S805: The core network sends a paging message to the terminal 802.

S806: The core network sends a call request message to the terminal 802.

For the specific contents of steps S801 to S805, reference may be made to the aforementioned description of steps S201 to S205. For the specific contents of step S806, reference may be made to the aforementioned description of step S502, which will not be repeated here.

It should be noted that in step S802, since terminal 801 is in the CM domain, if the User-User information element in the call establishment request message sent by terminal 801 carries the above-mentioned first recording suppression information, the first recording suppression information still exists in the User-User information element in the form of an eight-bit binary value sequence. However, since the terminal 802 is in the IMS domain, after the core network receives the call establishment request message with the first recording suppression information sent by the terminal 801, the core network will convert the first suppression information carried in the message, that is, convert the first recording suppression information in the form of an eight-bit binary numerical sequence into the second recording suppression information in the form of a character string, and store the second recording suppression information in the User-to-User header field of the call request message, and send it to the terminal 802 (for example, the core network can detect that the User-User information element in the call establishment request message carries the first recording suppression information "01010101", then when generating the call request message, the core network will convert the first recording suppression information into the second recording suppression information "recording=disabled", and after adding it to the User-to-User header field of the call request message, send it to the terminal 802). Therefore, in step S806, if the call establishment request message sent by the core network carries the second recording suppression information, the second recording suppression information still exists in the header field of the call request message in the form of a field.

S807: Terminal 802 sends a connection progress message to the core network.

S808: The core network sends a ringing message to the terminal 802.

S809: The core network sends a call reminder message to the terminal 801.

S810: Terminal 802 sends a connection success message to the core network.

S811: The core network sends a call connection message to terminal 801.

The specific contents of step S807, step S808 and step S810 can refer to the aforementioned related descriptions of step S503, step S505 and step S507, and the specific contents of step S809 and step S811 can refer to the aforementioned related descriptions of step S210 and step S212, which will not be repeated here.

Similarly, in step S810, since terminal 802 is in the IMS domain, if the User-to-User header field in the connection success message sent by terminal 802 carries the above-mentioned second recording suppression information, the second recording suppression information is still present in the User-to-User header field of the connection success message in the form of a string. However, since terminal 801 is in the CS domain, after the core network receives the connection success message with the second recording suppression information sent by terminal 802, the core network will convert the second suppression information carried in the message, that is, convert the second recording suppression information in the form of a string into the first recording suppression information in the form of an eight-bit binary numerical sequence, and store the first recording suppression information in the User-User information element of the call connection information, and send it to terminal 801. Therefore, in step S811, if the call establishment connection message sent by the core network carries the above-mentioned first recording suppression information, the first recording suppression information is still present in the User-User information element of the call request information in the form of an eight-bit binary numerical sequence.

In the embodiment of the present application, the signaling interaction operations involved in the above-mentioned call establishment process are only examples. In the actual call establishment process, the signaling interaction process between the calling end and the called end may include more or fewer operations, and the present application does not limit this.

FIG9 is an interactive flow chart of a communication method provided in an embodiment of the present application, which is based on FIG8 and combines user operations to illustrate the specific process of the calling end and the called end implementing the function of suppressing the recording of the other end during the communication process. As shown in FIG9, the interactive process may include:

S901: The terminal 801 starts a function of suppressing recording of the other end in response to a first operation.

S902: The terminal 801 sends a call establishment request message to the core network. The User-User information element in the call establishment request message includes the first recording suppression information.

The specific contents of step S901-step S902 can refer to the above-mentioned related description of step S301-step S302, which will not be repeated here.

S903: The core network transforms the first recording suppression information.

Since the terminal 801 is in the CM domain, in the call establishment request message, the User-User information element carries the first recording suppression information in the form of an eight-bit binary value sequence. However, since the terminal 802 is in the IMS domain, after the core network receives the call establishment request message with the first recording suppression information sent by the terminal 801, the core network will convert the first suppression information carried in the message, that is, convert the first recording suppression information in the form of an eight-bit binary value sequence into the second recording suppression information in the form of a character string, and store the second recording suppression information in the header field of the call request message, and send it to the terminal 802.

S904: The core network sends a call request message to the terminal 802.

S905: When the terminal 802 detects that the User-to-User header field in the call establishment request message includes the second recording suppression information, the terminal 802 suppresses the call recording function of the local end.

S906: The terminal 802 starts the function of suppressing the recording of the other end in response to the second operation.

S907: The terminal 802 sends a connection success message to the core network, and the User-to-User header field of the connection success message includes the second recording suppression information.

S908: The core network transforms the second recording suppression information.

S909: The core network sends a call connection message to the terminal 801.

The specific contents of steps S904 to S907 may refer to the aforementioned descriptions of steps S603 to S606, which will not be repeated here.

Since terminal 802 is in the IMS domain, the User-to-User header field in the above connection success message carries the above second recording suppression information and is still in the header field of the connection success message in the form of a string. However, since terminal 801 is in the CS domain, after the core network receives the connection success message with the second recording suppression information sent by terminal 802, the core network will convert the second suppression information carried in the message, that is, convert the second recording suppression information in the form of a string into the first recording suppression information in the form of an eight-bit binary numerical sequence, and store the first recording suppression information in the User-User information element of the call connection information, and send it to terminal 801.

S910: When it is detected that the User-User information element in the call connection message includes the first recording suppression information, suppress the call recording function of the local end.

S911: When the call is connected, the terminal 801 outputs a prompt message.

S912: When the call is connected, the terminal 802 outputs a prompt message.

The specific contents of step S910 to step S912 can refer to the above-mentioned related descriptions of step S309 to step S310, which will not be repeated here.

Correspondingly, when the calling end is in the IMS domain and the called end is in the CS domain, the communication interaction method between the two terminals and the process of suppressing the recording of the opposite terminal can also refer to the relevant descriptions of Figures 8 and 9, which will not be repeated here.

By implementing this communication method, even if the calling end and the called end are in different output transmission domains, the calling end and the called end can suppress the recording function of the other end during the call without affecting the call, which can effectively ensure the privacy and security of the user during the call.

In this embodiment, terminal 801 and terminal 802 can both be referred to as the "first terminal" or the "second terminal", the above-mentioned first recording suppression information and the second recording suppression information can also be referred to as "recording suppression information", the sequence can be referred to as the "first sequence", and the "01010101" parameter information "recording=disabled" can be referred to as "a character string identifying the first terminal's request to suppress the recording function of the second terminal".

Specifically, when terminal 801 is the "first terminal", terminal 802 is the "second terminal", the above-mentioned call establishment request message and call request message can both be called "first messages", and the above-mentioned call connection message and connection success message can both be called "second messages".

Correspondingly, when terminal 802 is the "first terminal", terminal 801 is the "second terminal", and the above-mentioned call connection message and connection success message can be called the "first message".

FIG. 10 shows, in conjunction with the user interface, a process of suppressing recording of the other party by the calling party and the called party during a call.

Specifically, the calling end and the called end in FIG. 10 may be the terminal 201 and the terminal 202 in the aforementioned description, or the terminal 501 and the terminal 502 in the aforementioned description, or the terminal 801 and the terminal 802 in the aforementioned description.

For the sake of convenience, it is assumed here that both the calling end and the called end in FIG. 10 are in the IMS domain.

As shown in FIG10 , the user interface 01 shown in (A) of FIG10 is a dialing interface displayed by the calling end when the calling end dials the called end, which may display the called user's mobile phone number "191XXXXXXXX" and the dial key 011. In order to suppress the recording function of the called end during the subsequent call, the calling user may perform a user operation on the user interface 01, that is, a long press operation on the dial key 011 shown in (A) of FIG10 , so that the calling end sends a call request message to the called end, and the header field of the call request information includes the User-to-User header field in the aforementioned description, and the User-to-User header field includes the above-mentioned second recording suppression information.

After the called end receives the call request message sent by the calling end, the called end will parse the message to find that it carries the above-mentioned second recording suppression information. At this time, the called end will actively suppress the recording function of the called end during this call, and after the suppression, the called user cannot turn it on through user operation.

Afterwards, when the called end sends a ringing message to the calling end and the called end starts ringing, the called end may display the user interface 02 as shown in (A) of FIG10 . The user interface 02 may be the incoming call interface displayed when the called end receives an incoming call. The calling user's mobile phone number "131XXXXXXXX", the hang-up key, and the answer key 021 may be displayed in the user interface 02. In order to suppress the recording function of the calling end during the subsequent call, the called user may perform a user operation on the user interface 02, that is, a long press operation of the answer key 021 as shown in (B) of FIG10 , so that the called end sends a connection success request message to the called end, and the User-to-User header field of the connection success message also includes the above-mentioned second recording suppression information.

After the calling end receives the connection success message sent by the called end, the calling end will also parse the message to find that it carries the above-mentioned second recording suppression information. The calling end will actively suppress the recording function of the called end during this call, and after the suppression, the calling user cannot turn it on through user operation.

In addition, after the called user connects the incoming call of the calling user through the second operation, the calling end and the called end can respectively display the user interface 03 shown in (C) of FIG. 10 and the user interface 04 shown in (D) of FIG. 10. It can be seen from the recording function key 031 displayed on the user interface 03 and the recording function key 041 displayed on the user interface 04 that the recording functions of the calling end and the called end have been suppressed at this time, so the recording function key 031 and the recording function key 041 are both in a state of being unselectable (unable to respond to user operations).

Correspondingly, after the called user connects the call of the calling user through the second operation, since both the calling end and the called end have enabled the function of suppressing the recording of the other end, the calling end and the called end output the above prompt information. The prompt information can be a voice broadcast, and its specific content can be "This call will not be recorded and this call is not allowed to be recorded", indicating that both parties of the call have enabled the recording suppression function.

In the embodiment of the present application, the user interface and user operation shown in FIG10 are only examples and do not constitute a limitation of the present application. For example, in an actual call process, the user can also trigger the function of suppressing the recording of the opposite side through other operations, such as by setting the call process to prohibit the recording of the opposite side by default in the system settings of the terminal, or adding a corresponding function menu in the call interface, the user can choose to click the corresponding function control to trigger the function of prohibiting the recording of the opposite side, or the user can trigger the function of prohibiting the recording of the opposite side through voice, such as when the called end displays the user interface 02, the called user can send a voice command of "Answer, prohibit recording" to the called end to prohibit the calling end from recording the call.

Next, an architecture diagram of an electronic device 100 provided in an embodiment of the present application is introduced. Specifically, the electronic device 100 can be any one of the aforementioned terminals 201, 202, 501, 502, 801, and 802.

FIG. 11 exemplarily shows the structure of the electronic device 100 .

The electronic device 100 may include a processor 110, an internal memory 121, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a button 190, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (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), etc. Different processing units may be independent devices or integrated into one or more processors.

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

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) 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 I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be coupled to a touch sensor, a charger, a flash, a camera, etc. through different I2C bus interfaces. For example, the processor 110 may be coupled to a touch sensor through an I2C interface, so that the processor 110 communicates with the touch sensor through the I2C bus interface to realize the touch function of the electronic device 100.

The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

The mobile communication module 150 can provide solutions for wireless communications including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. 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 (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS) and/or satellite based augmentation system (SBAS).

The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the internal memory 121, and/or instructions stored in a memory provided in the processor.

The electronic device 100 can implement audio functions such as music playing and recording through the audio module 170 and the speaker 170A.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

The speaker 170A, also called a "speaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 170A.

The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195. The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

In the present application, the electronic device 100 can act as a calling end or a called end and make calls with other devices through the mobile communication module 150 or the wireless communication module 160.

In some embodiments, during the process of establishing a call, the electronic device 100 can act as a calling end and respond to the calling user's first operation on it, and send a request message carrying recording suppression information to other devices via the core network to suppress the recording function of other devices on the call during subsequent calls.

In some embodiments, during the process of establishing a call, the electronic device 100 may also serve as the called party and receive a response message with recording suppression information sent by other devices via the core network, and actively suppress the recording function of the current call on this end based on the recording suppression information in the response message.

In addition, in some embodiments, after the electronic device 100 receives a request message sent by other devices via the core network during the call establishment process, it can also act as the called party in response to the second operation of the called user and reply to the device that sent the request message with a response message containing recording suppression information, so as to suppress the recording function of the device for the call during subsequent calls.

For example, when an available SIM card is inserted into the SIM card interface 195, the electronic device 100 can dial other devices with the same SIM inserted under user operation. If the user does not want the other party to record the call in subsequent calls, the user can perform the above-mentioned first operation in the dialing interface displayed by the electronic device 100 to start the function of suppressing the recording of the other party terminal. Specifically, the first operation can be a long press operation of the user on the dialing key in the dialing interface. Afterwards, the electronic device 100 can respond to the first operation and send a request message carrying recording suppression information, such as an Invite message, to its called party via the core network. After receiving the above-mentioned request message carrying the recording suppression information, the called party will follow the protocol rules to actively suppress the call recording function of the called party and prohibit the called user from recording the call. The privacy and security of the calling user during the call can be guaranteed.

Claims (13)

1. A communication method applied to a first terminal, the method comprising:

generating a first message, wherein the first message comprises recording suppression information;

and sending the first message to a second terminal, wherein the first message is used for establishing a call with the second terminal, and the recording inhibition information is used for inhibiting a recording function of the second terminal on the call.

2. The method of claim 1, wherein after the sending the first message to the second terminal, the method further comprises:

receiving a second message sent by the second terminal, wherein the second message is used for establishing the call with the second terminal, and the second message contains the recording inhibition information;

and suppressing the recording function of the call.

3. The method of claim 1 or 2, wherein the first terminal communicates with the second terminal in a circuit switched domain, the recording suppression information comprising a first sequence of K-bit binary value sequences, the first sequence identifying a suppression request by the first terminal for a recording function of the second terminal.

4. The method of claim 3, wherein the first message is a Setup message and the first sequence is a sequence contained in User-User cells in the Setup message.

5. A method according to claim 3, wherein the second message is a Connect message and the first sequence is a sequence contained in a User-User cell in the Connect message.

6. The method according to claim 1 or 2, wherein the first terminal communicates with the second terminal under an IP multimedia subsystem domain, and the recording suppression information includes a string for identifying a suppression request of the first terminal for a recording function of the second terminal.

7. The method of claim 6, wherein the first message is an Invite message and the string is a parameter contained in a User-to-User header field of the Invite message.

8. The method of claim 6 wherein the second message is a 200 OK message and the string is a parameter contained in a User-to-User header field of the 200 OK message.

9. A communication method applied to a second terminal, the method comprising:

receiving a third message sent by the first terminal, wherein the third message is used for establishing a call with the first terminal, and the third message contains the recording inhibition information;

and suppressing the recording function of the call.

10. A communication system, characterized in that the communication system comprises a calling terminal and a called terminal,

the calling terminal is used for generating a request message, and the request message comprises recording suppression information; the request message is used for establishing a call with the called terminal, and the recording inhibition information in the request message is used for inhibiting the recording function of the called terminal on the call;

The called terminal is used for generating a response message, and the response message comprises the recording suppression information; and sending the response message to the calling terminal, wherein the response message is used for establishing a call with the calling terminal, and the recording inhibition information in the response message is used for inhibiting the recording function of the calling terminal on the call.

11. An electronic device, the electronic device comprising: one or more processors, memory, and a display screen;

the memory is coupled with the one or more processors, the memory for storing computer program code comprising computer instructions that the one or more processors invoke to cause the electronic device to perform the method of any of claims 1-9.

12. A chip system for application to an electronic device, the chip system comprising one or more processors for invoking computer instructions to cause the electronic device to perform the method of any of claims 1-9.

13. A computer readable storage medium comprising instructions which, when run on an electronic device, cause the electronic device to perform the method of any of claims 1-9.