CN117857686A

CN117857686A - Communication method, communication system and related device

Info

Publication number: CN117857686A
Application number: CN202410172393.8A
Authority: CN
Inventors: 杨光; 郑宝辉; 王莹; 郝永兴
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2024-02-07
Filing date: 2024-02-07
Publication date: 2024-04-09

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 disclosure relates to the field of terminal technologies, and in particular, to a communication method, a communication system, and a related device.

Background

Today, talking on a mobile phone, smart watch, etc. is called an indispensable ring in our daily communications and entertainment. In the current conversation scene, the opposite terminal user can record the conversation of the two parties without the permission of the local terminal user and even without knowing the local terminal user. Even if the local end user does not want the opposite party to use the recording function in the call, the opposite end user can record the call, and the privacy security of the user cannot be guaranteed.

Therefore, how to improve the privacy security of the user during the call is a urgent problem to be solved.

Disclosure of Invention

The invention aims to provide a communication method, a communication system and a related device, wherein the method is implemented, and electronic equipment can add recording inhibition information in a sent message for establishing a session in the process of establishing the session so as to limit the recording authority of a contralateral terminal and ensure the personal privacy of a local terminal user.

The above and other objects are achieved by the features of the independent claims. Further implementations are presented in the dependent claims, the description and the figures.

In a first aspect, the present application provides a communication method, applied to a first terminal, where the method includes: 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.

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

And under the condition that the first terminal is a calling terminal, the second terminal is a called terminal. Correspondingly, the first message is a request message generated by a calling terminal, and the request message characterizes the first terminal to request to establish a session with the second terminal. The first message may be sent to the second terminal via a core network. In particular, the first message may be a Setup message or an Invite message. After the second terminal receives the first message, the second terminal can analyze the first message, and after determining that the request message contains the recording inhibition information, the second terminal actively inhibits the recording function in the current call.

And under the condition that the first terminal is a called terminal, the second terminal is a calling terminal. Correspondingly, the first message is a response message generated by the called terminal after receiving the request message sent by the calling terminal, and the response message is used for responding to the request message of the calling terminal and establishing a session with the calling terminal. The first message may also be sent to the first terminal via a 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 can analyze the response message, and after determining that the first message contains the recording inhibition information, the first terminal also actively inhibits the recording function of the first terminal in the current call.

In the method, the communication process between the first terminal and the second terminal should conform to the corresponding communication standard. In the method, the specific processing mode of the recording inhibition information (namely, inhibition of recording in the call process) of the recording inhibition information at the receiving end of the recording inhibition information can be specified in the communication standard. After the second terminal receives the recording inhibition information and actively inhibits the recording function, the user of the second terminal cannot start the recording function again in the session through corresponding operation, so that the privacy security of the user of the first terminal in the communication can be ensured.

With reference to the first aspect, in a possible implementation manner, after the sending the first message to the second terminal, the method further includes: 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.

In this embodiment, the first terminal is a calling terminal, and the second terminal is a called terminal. Correspondingly, the first message is a request message generated by a calling terminal, and the request message is used for requesting to establish a session with the second terminal. The request message may be sent to the second terminal via a core network. The second message is a response message generated by the called terminal after receiving the request message sent by the calling terminal, and the response message is used for responding to the request message of the calling terminal and establishing a session with the calling terminal. The response message may also be sent to the first terminal via the core network. Specifically, the response message may be a Connect message or a 200 OK message. After the first terminal receives the response message, the first terminal can analyze the response message, and after the recording inhibition information in the response message is determined, the first terminal also actively inhibits the recording function in the current call.

After the first terminal receives the second message, analyzes the recording inhibition information contained in the second message and actively inhibits the recording function, the user of the first terminal cannot start the recording function again in the session through corresponding operation, and privacy security of the user of the second terminal (namely, the called user) in the communication can be ensured.

With reference to the first aspect, in one possible implementation manner, the first terminal communicates with the second terminal in a circuit switched domain, and the recording suppression information includes a first sequence, where the first sequence is a binary number sequence of K bits, and the first sequence identifies a suppression request of a recording function of the second terminal by the first terminal.

In the circuit switched domain, the first message may carry a plurality of cells according to a format standard defined by the 3GPP protocol. Some of the cells have an extension mechanism that can be designed or encoded according to the user's needs to provide the corresponding functionality for the user during the call. In this embodiment, the user may limit the recording authority of the second terminal in the call process by encoding a certain cell in the first message. Specifically, the first message may include a User-to-User cell, where the User-to-User cell may include at least one byte having eight bits, and the first terminal may design a corresponding binary sequence for the eight-bit byte that the User-to-User cell has (i.e. the k=8, and the first terminal assigns a value of 0 or 1 to each bit, to obtain an eight-bit binary value sequence, for example, "00001111"), where the sequence may be used to represent a protocol that implements the sound recording suppression function specified by the 3 GPP. After the second terminal receives the first message, the second terminal can analyze the binary value sequence, and inhibit the recording function of the local terminal in the call according to the protocol pair for implementing the recording inhibition 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 cell in the Setup message.

With reference to the first aspect, in one possible implementation manner, the second message is a Connect message, and the first sequence is a sequence included in a User-User cell in the Connect message.

With reference to the first aspect, in a possible implementation manner, 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.

Under the multimedia subsystem domain, according to the format standard of SIP, the header domain of the first message may include a plurality of fields, and the header domain of the first message also supports expansion, and may add corresponding parameters to provide corresponding functions for the user during the call. In this embodiment, the user may limit the recording authority of the second terminal in the call process by adding a corresponding field to the header field of the first message. Specifically, the first message may include a User-to-User field, where the User-to-User field may include a string for implementing a recording suppression function, where the string may be used to indicate that recording is prohibited (for example, recording-disabled or recording=disabled, etc.). After the second terminal receives the first message, the second terminal can analyze the character string for realizing the recording suppression function and suppress the recording function of the local terminal in the call.

With reference to the first aspect, in one possible implementation manner, 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.

With reference to the first aspect, in a possible implementation manner, 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, where the method includes: 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.

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

And under the condition that the second terminal is a calling terminal, the first terminal is a called terminal. Correspondingly, the third message is a response message generated after the called terminal receives the request message sent by the calling terminal. The third message may be sent to the second terminal via a core network. In particular, the third message may be a Connect message or a 200 OK message. After the second terminal receives the third message, the second terminal can analyze the third message, and after determining that the third message contains the recording inhibition information, the second terminal actively inhibits the recording function of the second terminal in the current call.

And under the condition that the second terminal is a called terminal, the first terminal is a calling terminal. Correspondingly, the third message is a request message generated by the calling terminal, and the third message characterizes the first terminal to request to establish a session with the second terminal. The response message may also be sent to the first terminal via the core network. In particular, the response message may be a Setup message or an Invite message. After the first terminal receives the response message, the second terminal can analyze the response message, and after the response message is determined to have the recording inhibition information, the second terminal actively inhibits the recording function of the second terminal in the current call.

In a third aspect, the present application provides a communication system, where the communication system includes a calling terminal and a called terminal, where the calling terminal is configured to generate a request message, where the request message includes 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.

In a fourth aspect, an embodiment of the present application provides an electronic device, including: one or more processors and memory; 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 call to cause the electronic device to perform the method of the first aspect or any of the possible implementations of the first aspect, or the method of the second aspect.

In a fifth aspect, there is provided 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 as in the first aspect or any of the possible implementations of the first aspect, or the method as in the second aspect.

A sixth aspect, a computer program product comprising instructions which, when run on an electronic device, cause the electronic device to perform the method as in the first aspect or any one of the possible implementations of the first aspect, or the method as in the second aspect.

In a seventh aspect, a computer readable storage medium is provided, comprising instructions which, when run on an electronic device, cause the electronic device to perform the method as in the first aspect or any of the possible implementations of the first aspect, or the method in the second aspect.

Drawings

Fig. 1 is an interactive flow chart of a call between a calling end and a called end according to an embodiment of the present application;

fig. 2 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;

fig. 3 is an interaction flow chart of a call between a calling end and a called end in a CM domain provided in an embodiment of the present application;

FIG. 4 is a block diagram of a cell according to an embodiment of the present application;

fig. 5 is a signaling interaction diagram of a call between a calling end and a called end in an IMS domain according to an embodiment of the present application;

fig. 6 is an interaction flow chart of calling and called terminals in IMS domain according to an embodiment of the present application;

fig. 7 is a schematic diagram of byte content in a header field according to an embodiment of the present application;

fig. 8 is a signaling interaction diagram of a call between a calling end and a called end according to an embodiment of the present application;

fig. 9 is an interaction flow chart of a call between a calling end and a called end according to an embodiment of the present application;

FIG. 10 is a diagram of some user interfaces provided in embodiments of the present application;

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

Detailed Description

The terminology used in the following embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates to the contrary. It should also be understood that the term "and/or" as used in this application refers to and encompasses any or all possible combinations of one or more of the listed items.

For ease of understanding, the following description will first be given of the relevant terms related to the embodiments of the present application.

(1) Calling and called terminals

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

After receiving the call request sent by the calling terminal, the called terminal can choose to accept the call request to carry out the call with the calling terminal, or reject the call request and not carry out the call with the calling terminal. Of course, during the whole call process (including before the called end is accepting the call), the calling end can hang up actively to end the call process.

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

The mobile network that users routinely access can be divided into three parts, a base station subsystem, a network subsystem, and a system support part (e.g., security management). The core network part is located in the network subsystem and is used for connecting the call request or the data request from the port A to the equipment set on different networks. For ease of understanding, the core network may be considered a "very complex enhanced router", the access network being a "window" responsible for collecting data; the bearing network is a truck and is responsible for transporting the data; the core network is a management center and is responsible for managing the data, sorting the data and then planning the destination of the data. It will be appreciated that the handling and distribution of data (in essence "routing exchanges") is essential to the core network.

The data transmission domain related to the core network mainly comprises a circuit switched domain and an IP multimedia subsystem domain.

A Circuit Switched (CS) domain is typically used for voice calls. When data transmission is performed in the CS domain, a connection for transmitting data is firstly required to be established, the data transmission can be started after the establishment is completed, the connection can not be disconnected, and the connection can not be released until the data transmission is completed. So that a link is only circuit switched and is characterized by exclusive use of a link for data transmission.

The IP multimedia subsystem domain (IP multimedia subsystem, IMS) is a completely new form of multimedia service. The method is a new generation communication exchange technical standard for realizing the integration of fixed network communication and mobile communication, and the current 4G and 5G communication exchange capacities of operators are carried by an IMS system. The protocols and interfaces used by IMS all follow the TCP/IP protocol stack, unlike the traditional CS (circuit switched) voice scheme. One of the most critical protocols is a session initiation (session initiation protocol, SIP) protocol, which is used as a control protocol in the IMS, and the corresponding protocol message can carry the content of an SDP (session description protocol), so that the method has the characteristics of simplicity, flexibility, easy expansion, convenience in media negotiation and the like, and improves the future adaptability of the network. In general, SIP protocol messages can be divided into two types, request messages, which are sent by a user agent client (which can be understood as the calling end) to a user agent server (which can be understood as the called end), and response messages, which are sent by a user agent server to the user agent client.

The terminal is processed according to 3GPP protocol when calling or receiving in CS domain, and is processed according to SIP protocol when calling or receiving in IMS domain. If the calling terminal and the called terminal are not in the same domain, the core network will do signaling processing conversion.

(3) User-to-User information

User-to-User is a type of signaling information that is transmitted end-to-end. In the CS domain, user-to-User information may be transmitted in the form of User-User information (UUI) cells in Setup messages, connect messages. In the IMS domain, user-to-User information may be conveyed in the form of a SIP User-to-User Header field in Invite messages and 200 OK messages.

When the terminal and the terminal communicate based on the core network, the core network only transmits the information and does not do additional processing.

If the calling end and the called end are in the same domain, the User-to-User can transmit thoroughly, if the calling end and the called end are not in the same domain, the signaling and the cell conversion of the User-to-User information contained in the instruction information step sent by one end are transmitted.

In addition, the User-to-User information also has an extension mechanism, namely, the User-to-User information can be recoded, and corresponding functions are provided for the calling terminal and the called terminal in the call process of the calling terminal and the called terminal. For example, in the present application, a User may limit the recording authority of a calling end and/or a called end in a call process by designing a corresponding binary sequence for a User-User cell or adding a parameter content in a User-to-User Header, so as to protect privacy security of both parties in the call process, and the following description may be referred to for specific details, which are not described herein.

Today, talking on a mobile phone, smart watch, etc. is called an indispensable ring in our daily communications and entertainment. In the current conversation scene, the opposite terminal user can record the conversation of the two parties without the permission of the local terminal user and even without knowing the local terminal user. Even if the local end user does not wish to use the recording function for the other party in the call, the opposite end user can record the call, and the privacy security of the user cannot be guaranteed.

Fig. 1 is an interactive flow chart of a call between a calling end and a called end provided by the present application. As shown in fig. 1, the terminal 101 and the terminal have established a communication connection through a request message, where the terminal 101 may be a calling terminal, the terminal 102 may be a called terminal, and users of the two terminals may communicate through the two terminals, and the interaction procedure may include the following steps:

s101: the terminal 101 records a call in response to a user operation.

After the terminal 101 and the terminal 102 establish a call and formally start the session, the terminal 101 may record the call content of the subsequent whole call through the above user operation. Specifically, the user operation may be an operation that the user of the terminal 101 clicks a "record" function option in a call interface of the terminal 101.

S102: terminal 101 sends a prompt message to terminal 102.

After the terminal 101 starts the call recording function based on the user operation, the terminal 101 may send the above-mentioned prompt information to the terminal 102, where the prompt information may be used to inform the terminal 102 that the terminal 101 has started the call recording currently, and all the conversation contents of the two users of the terminal 101 and the terminal 102 will be recorded and saved by the terminal 101 in the subsequent whole call process.

S103: after receiving the prompt message, the terminal 102 prompts the user that the opposite user has started the call recording.

After the terminal 102 receives the prompt message, the terminal 102 informs the user of the terminal 102 in some form of the result that the terminal 101 has opened the call recording. Specifically, the terminal 102 may report that the voice information prompts that the opposite user of the terminal 102 (i.e., the user of the terminal 101) has opened the call recording function; alternatively, the terminal 102 may display a text message in the call interface to indicate to the user of the terminal 102 that the opposite user (i.e., the user of the terminal 101) has turned on the call recording function.

As can be seen from fig. 1 and the foregoing description, although the local user can know that the opposite user has started the call recording function after the opposite user starts the call recording function during the whole call, the opposite user can still start recording without asking for permission of the local user. That is, when the session contents of both parties relate to the privacy information of both parties, and one or both users do not want the other party to record the call, the calling end and the called end can still record the whole session contents without obtaining the permission of the other party to record the call, so that the personal privacy and the security appeal of both parties of the session cannot be guaranteed.

Aiming at the defects existing in the conversation process, the application provides a communication method, wherein in the process of establishing a conversation between a calling terminal and a called terminal, recording inhibition information can be added in a message sent by the calling terminal and/or the called terminal and used for establishing the conversation, so that recording permission of a contralateral terminal is limited, and personal privacy of a user at the home terminal is ensured.

It should be noted in advance that, in an actual communication scenario, data of a calling end and a called end involved in a call may be located in a CS domain at the same time, may be located in an IMS domain at the same time, or may be located in the CS domain at one side, and located in the IMS domain at the other side. Because different data transmission domains are different in specification for the communication protocol, the difference of the communication protocol can influence the difference of messages received and transmitted by two terminals in the session establishment process, and further influence the format of the message type recording inhibition information where the recording inhibition information is located. Therefore, the communication method provided by the present application will be described below for different situations of the data transmission domain where the calling terminal and the called terminal are located.

1. The calling and called terminals are simultaneously in CS domain, refer to fig. 2-4.

First, the signaling interaction flow involved in the session establishment procedure between the calling and called terminals in the CS domain will be described, with reference to fig. 2.

As shown in fig. 2, the terminal 201 and the terminal 202 may be a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an augmented reality (augmented reality, AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook, a personal digital assistant (personaldigital assistant, PDA), or a special camera (e.g., a single-lens reflex camera, a card-type camera), etc., and the specific type of the electronic device is not limited in this application. Wherein, the terminal 201 is a calling terminal, the terminal 202 is a called terminal, and the steps of signaling interaction involved in the session establishment between the two terminals may include:

s201: the terminal 201 transmits a CM service request message to the core network.

In the process of establishing a session, the terminal 201 as a calling terminal may first send an initial direct transmission message, i.e., the CM service request message described above, to the core network.

S202: the core network transmits a CM service accept message to the terminal 201.

If the core network accepts the CM service request sent by the terminal 201, the core network sends the CM service accept message to the terminal 201, indicating that the request sent by the terminal 201 before (i.e., CM service request message) has been accepted.

S203: the terminal 201 transmits a call setup request message to the core network.

After performing steps S201 and S202, the terminal 201 as the calling end continues to send a message for formally starting the call procedure, i.e. the call establishment request message, to the core network. The call establishment request message may include the telephone number of the called end, and the service related to the whole call process, and the core network may perform call connection based on the call establishment request message.

In this embodiment of the present application, the call establishment request message may carry a User-User cell, where the User-User cell may carry recording suppression information to suppress a recording function of the terminal 202 in a subsequent call process.

S204: the core network sends a call setup proceeding message to the terminal 201.

When the core network receives the call setup message from the terminal 201, it checks whether the mobile phone number of the called party (the information of various number classifications is stored in the core network, and it is confirmed whether it has the capability of pointing to the number) and the capability of the calling party user themselves (i.e. according to whether the originally registered service of the calling party supports the required service of the call, if the international long distance is dialed, it checks whether there is the international long distance limitation, and the resource capability of the network itself, etc.) can accept the service requirement related to the session. If the core network supports the foregoing service requirements, the core network may send the call setup proceeding message to the terminal, which indicates that the call setup request sent by the terminal 201 as the calling terminal has passed the verification, and the call is in progress.

After step S205 is completed, the bearer between the terminal 201 and the core network is already established, and the bearer can be used for transmitting voice, data and multimedia service data packets in the subsequent process by the terminal 201 and the core network.

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

The paging message is used by the core network to find or notify one or more terminals, and the main carried content includes the identity of the terminal to be paged, the identity of the core network initiating the paging, and an indication of whether the system message has changed. Because the terminal 202 is mobile, its location is dynamically changing, and the terminal 202 may be abnormally powered off or enter a low power state, which does not maintain a radio resource control (radio resource control, RRC) connection with the base station or core network at any time. Therefore, when terminal 201 needs to talk with terminal 202, the core network needs to find terminal 202 first, and re-establish the RRC connection with terminal 202 after waking up it.

S206: terminal 202 sends a page response message to the core network.

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

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

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

If the call establishment request message carries a User-User cell, the core network will also send the User-User cell carried by the call establishment request message to the terminal 202 when the call establishment request message is sent to the terminal 202. After the terminal 202 receives the call establishment request message, the terminal 202 may parse the call establishment request message to determine recording suppression information carried by the User-User cell, and then the terminal 202 will actively suppress the recording function in the subsequent call process; it should be noted that, the operation of suppressing the recording function by the terminal 202 is actively performed 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 open the function of recording the call by operating in the subsequent process.

S208: terminal 202 sends a call setup confirm message to the core network.

After receiving the call establishment request message sent by the core network, the terminal 202 replies a call establishment confirmation message to the core network, which indicates that the terminal 202 has received all the messages required for establishing a call connection.

After step S208 is completed, the bearer between the terminal 202 and the core network is already established, and the bearer can be used for voice, data and multimedia service data packet transmission in the subsequent process between the terminal 202 and the core network.

S209: terminal 202 sends a call alert message to the core network.

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

After the terminal 202 transmits the call setup confirmation message, it indicates that the call placed by the terminal 201 has been received, and the call placed by the terminal 201 is in the process of waiting to be received. At this time, the terminal 202 sends the call alert message to the terminal 201 via the core network, which indicates that the terminal 202 has received the call request of the terminal 201 at this time, and is in a "ringing" state. In conventional call systems, the call alert message is typically in the form of a prescribed tone or ringing tone to indicate that the called party has received the call request and is about to begin answering. Through the call alert message, the caller can know that the telephone line is connecting to the called party and is waiting to answer.

S211: terminal 202 sends a call connect message to the core network.

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

If the terminal 202 makes a call under the user operation (for example, the user presses the answer key), the terminal 202 sends the call connection message to the terminal 201 through the core network, which indicates that the link between the calling end and the called end is connected, and at this time, the call establishment process is completed, and both sides enter the call or data service transmission stage.

In this embodiment of the present application, the User-User cell may also be carried in the call connection message, where the User-User cell in the call connection message may also carry recording suppression information to suppress a recording function of the terminal 201 in a subsequent call process.

Specifically, if the call connection message carries a User-User cell, the core network will also send the User-User cell carried by the call connection message to the terminal 201 when the call connection message is sent to the terminal 201. After the terminal 201 receives the call establishment connection message, the terminal 201 may parse the call establishment connection message to determine recording suppression information carried by the User-User cell, so that the terminal 201 will actively suppress the 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, and this process is not affected by the operation of the called user (i.e., the user of the terminal 201), and the user of the terminal 201 cannot open the function of recording a call by operating in the subsequent process.

In the embodiment of the present application, the signaling interaction operation involved in the call establishment process is merely an example, and in the actual call establishment process, the signaling interaction process between the calling end and the called end may include more or less operations. In addition, in the embodiment of the present application, signaling sent and received between the calling end and the called end may be called other names, which is not limited in this application, for example, the CM service request message may be called CM Service Request, the CM service Response message may be called CM Service Accept, the Call Setup request message may be called Setup, the Call Setup Proceeding message may be called Call Proceeding, the Paging message may be called Paging, the Paging Response message may be called Paging Response, the Call alert message may be called alert, and the Call connection message may be called Connect.

Fig. 3 is an interaction flow chart of a communication method provided in the embodiment of the present application, which shows a specific flow of implementing a function of suppressing recording of an opposite terminal in a communication process by a calling terminal and a called terminal in combination with a user operation on the basis of fig. 2. As shown in fig. 3, the interaction flow may include:

S301: the terminal 201 starts the inhibit opposite-end recording function in response to the first operation.

When terminal 201 calls terminal 202, if the calling user does not wish the called user to have the right to record the call, the calling user can enable the recording function of the suppression counterpart (i.e., terminal 202) through the above-mentioned first operation. Specifically, the first operation may be an operation (specifically, refer to the following description) that the calling user presses a dial key for a long time in a dial interface shown in the terminal 201, or an operation that the calling user issues a voice command to the terminal 201 (for example, the calling user speaks a command "make XXX dial forbidden recording phone" to the terminal 201).

S302: the terminal 201 sends a call setup request message to the core network, the User-User cell of the call setup request message containing the first recording suppression information.

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

After the first operation is detected, in the subsequent process of establishing a call with the terminal 202, the call establishment request information sent by the terminal 201 to the core network may carry a User-User cell, where the User-User cell may include first recording suppression information. When the subsequent core network sends the call establishment request message to the terminal 202, the first recording suppression information is sent to the terminal 202 along with the call establishment request message.

S304: the terminal 202 suppresses the local call recording function when detecting that the User-User cell in the call setup request message contains the first recording suppression information.

After the terminal 202 receives the call establishment request information sent by the core network, the terminal 202 may analyze whether the User-User cell in the call establishment request information carries the first recording suppression information. In the case that it is determined that the User-User cell included 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 cannot open the recording function of the call in the subsequent process through operation.

S305: terminal 202 initiates the inhibit opposite recording function in response to the second operation.

When the terminal 202 responds to the call of the terminal 201, if the called user does not want the calling user to have the authority to record the call, the called user can enable the recording function of the opposite terminal (i.e., the terminal 201) through the second operation. Specifically, the second operation may be an operation of the called user pressing a dial key for a long time in a call interface shown by the terminal 202 (refer to the following description for details), or an operation of the called user issuing a voice command to the terminal 202 (for example, after the called user receives a call from the terminal 201 at the terminal 202, the called user speaks a command of "answer, prohibit recording" to the terminal 202).

S306: terminal 202 sends a call connection message to the core network, the User-User cell of the call connection message containing 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 cell, where the User-User cell may also include the first recording suppression information. When the subsequent core network sends the call connection message to the terminal 201, the first recording suppression information is sent to the terminal 201 along with the call connection message.

S308: the terminal 201 suppresses the local call recording function in case that it detects that the User-User cell in the call connection message contains the first recording suppression information.

After the terminal 201 receives the call establishment request information sent by the core network, the terminal 201 may analyze whether the User-User cell in the call establishment request information carries the first recording suppression information. In the case that it is determined that the User-User cell included 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 cannot open the recording function of the call through operation in the subsequent process.

It should be noted that, in some embodiments, only one of the terminals 201 and 202 may start the operation of suppressing the recording function of the opposite terminal. For example, in the call setup process, if the user of the terminal 201 performs the first operation, but the user of the terminal 202 does not perform the second operation, only the call setup request message sent to the terminal 202 by the terminal 201 through the core network includes the first recording inhibition information, and the call connection message sent to the terminal 201 by the terminal 202 through the core network does not include the first recording inhibition information, in which case the terminal 202 will not be able to record a subsequent call, but the terminal 201 may record a call. Accordingly, in the call setup process, if the user of the terminal 201 does not perform the first operation, but the user of the terminal 202 performs the second operation, the call setup request message sent to the terminal 202 by the core network by the terminal 201 does not include the first recording inhibition information, but the call connection message sent to the terminal 201 by the core network by the terminal 202 includes the first recording inhibition information, in which case the terminal 201 cannot record a call in a subsequent call, but the terminal 202 can record a call. However, no matter whether the calling party and the called party start the recording inhibition function or only one party in the call starts the recording inhibition function, the call between the calling party and the called party can be normal.

Next, a specific pattern of the first recording suppression information included in the User-User cell and the structure of the User-User cell will be described with reference to fig. 4.

It should be noted that, in the CM domain, the User-User cell may be composed of a plurality of bytes in the above call setup request message and the call connect message, wherein each byte contains eight bits, according to the format standard defined by the 3GPP protocol (i.e., 3rd generation partnership project, which is a global applicable communication specification and technical report, covering all aspects of mobile communication technology, which were established from the third generation mobile communication system in 1998). In the 3GPP protocol, each byte contained in a User-User cell may be encoded, i.e., eight bits contained in each cell may be assigned a binary value (i.e., "0" or "1"), resulting in a binary value sequence of eight bits that may be used to represent a communication protocol as specified by the 3GPP protocol.

As shown in fig. 4, the byte 40 may be a byte included in the above-mentioned User-User cell, which has eight bits, where each bit may have a value of "0" or "1". It will be appreciated that there are 256 possible cases of binary value sequences corresponding to the bytes, each of which may be used to represent a communication protocol as specified by the 3GPP protocol. But in the current 3GPP protocols the number of binary value sequences that have been used to represent a certain communication protocol does not reach 256. That is, the above 256 binary value sequences can be divided into two types, one of which is a sequence that has been used as a sequence representing a certain communication protocol, such as a sequence 411 (i.e., "00000001" which represents an OSI higher layer protocol) and a sequence 412 (i.e., "00000010" which represents an x.244 protocol, which is a obsolete protocol) shown in the sequence table 41 in fig. 4, and the other of which is a sequence that has not been used as a sequence representing any communication protocol (here, "01010101" and "10101010" are assumed not to be used for representing any communication protocol), such as a sequence 413 (i.e., "01010101") and a sequence 414 (i.e., "10101010") shown in fig. 4, which can be set to represent a certain protocol (or a sequence for realizing a certain function that the user needs to achieve in communication) according to the user's needs, since these sequences are not occupied to represent a certain communication protocol.

For example, in the embodiment of the present application, the sequence 414 (i.e., "10101010") may be set to a sequence for implementing the function of suppressing the recording of the terminal in the communication process, where the sequence 414 is the first recording suppression information. In this case, when the terminal 201 parses from the received call connection message that there is one byte in the User-User cell, and the binary value sequence bit "10101010" consisting of eight bits thereof, the terminal 201 actively suppresses the call recording function, so that the calling subscriber cannot record the current call. Similarly, when the terminal 202 parses from the received call service request message that there is one byte in the User-User cell, and the binary value sequence bit "10101010" consisting of eight bits of the byte is included in the User-User cell, the terminal 201 also actively suppresses the call recording function, so that the called User cannot record the current call.

It should be understood that fig. 4 illustrates a specific pattern of bytes in a User-User cell by way of example only, and is not intended to be limiting in any way. In addition, in the present 3GPP protocol, the sequence that has been occupied to indicate a certain communication protocol is determined for the binary value sequence formed by the bytes in the User-User cell, so that eight bits are the above 256 binary value sequences that can be formed, and any unoccupied sequence except the sequence that has been occupied can be set as a sequence that suppresses the recording function of the terminal in the communication process, which is not limited in this application.

S309: in the case of call connection, the terminal 201 outputs a prompt message.

S310: in the case of call connection, terminal 202 outputs a prompt.

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

Under the condition that the call is connected, the two terminals can inform the user at the side whether the opposite side user opens the function of restraining the call record in the current call.

Specifically, after the call is put through, in the case that the calling end (i.e., the terminal 201) starts to inhibit the recording of the opposite end (i.e., the terminal 202) in response to the first operation of the user, the prompting information output by the terminal 201 may include "call not recorded/This call will not be recorded", and correspondingly, the prompting information output by the terminal 202 may include "call not allowed to be recorded/This call is not allowed to be recorded", where the prompting information may be respectively reported by the terminal 201 and the terminal 202 in a voice form or be respectively displayed on the call interfaces of the terminal 201 and the terminal 202 in a text form.

Similarly, in the case where the called terminal (i.e., terminal 202) enables the suppression of recording of the opposite terminal (i.e., terminal 201) in response to the second operation of the user, the above-mentioned prompt information output by terminal 202 may include "call not allowed to be recorded/This call is not allowed to be recorded", and correspondingly, the above-mentioned prompt information output by terminal 201 may include "call not recorded/This call will not be recorded".

Optionally, if the calling terminal does not start (not support) the recording suppression function, but the called terminal starts the recording suppression function, the calling terminal may not play sound to inform the called user, but the called user has the sound of the claim right at this time, so as to inform the calling terminal, that is, the prompt information output by the calling terminal (terminal 201) only includes "call disallowed to be recorded/This call is not allowed to be recorded". If the called end does not start (not support) the recording inhibition function, the calling user is not played, but the calling user has the playing of the claim right at the moment, the purpose of informing the called is achieved, namely the prompting information output by the called end (terminal 202) only comprises 'call disallowed to be recorded/This call is not allowed to be recorded'. If both the calling terminal and the called terminal start the function of suppressing the recording of the opposite terminal, the prompting information output by the calling terminal and the prompting information output by the called terminal can simultaneously comprise 'call not recorded and call not allowed to be recorded/This call will not be recored and this call is not allowed to be recorded', which means that both parties of the call start the recording suppression function.

By implementing the communication method, under the CS domain, the calling terminal and the called terminal can realize the function of suppressing the recording of the opposite terminal in the conversation process without influencing the conversation, and the privacy safety of the user in the conversation process can be effectively ensured.

In this application, both terminal 201 and terminal 202 may be referred to as a "first terminal" or a "second terminal", the above-described 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, in the case where the terminal 201 is the "first terminal", the terminal 202 is the "second terminal", the call establishment request message may be referred to as a "first message", and the call connection message may be referred to as a "second message".

Accordingly, in the case where the terminal 202 is the "first terminal", the terminal 201 is the "second terminal", and the call connection message may be referred to as the "first message".

2. The calling and called terminals are both in the IMS domain, see fig. 5-7.

First, the signaling interaction flow involved in the session establishment procedure between the calling and called terminals in the IMS domain will be described, with reference to fig. 5.

As shown in fig. 5, the terminal 501 and the terminal 502 may be a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an augmented reality (augmented reality, AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook, a personal digital assistant (personaldigital assistant, PDA), or a special camera (e.g., a single-lens reflex camera, a card-type camera), etc., and the specific type of the electronic device is not limited in this application. The step of establishing signaling interaction involved in the session between the terminal 501 and the terminal 502 may include:

S501: the terminal 501 transmits a call request message to the core network.

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

Under the IMS domain, communication (e.g., voLTE, voWIFI, voNR call, etc.) takes place between a calling party (i.e., terminal 501) and a called party (i.e., terminal 502) following the session initiation protocol (session initiation protocol, SIP). The SIP protocol is a signaling protocol like the HTTP protocol for initiating, managing and terminating voice and video sessions in a network, and in particular for generating, modifying and terminating sessions between one or more participants.

When a session is initiated, the flow needs to be implemented by the calling end initiating call request information according to the specification of the SIP protocol. Thus, in the IMS domain, after a calling user dials to the terminal 502 through the terminal 501, the terminal 501 first initiates a call request message, which is sent to the terminal 502 via the core network.

Specifically, the call request message may include a series of Header fields (Header fields) that include a plurality of attributes and additional information of the transmission message, such as a unique identifier of the call, a destination address, an address of the calling terminal, and a session type of the current session; the session type may be voice only, multimedia video for a web conference, or other types.

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

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

S504: the core network sends a connection proceeding 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 proceeding message to the terminal 501 via the core network. The connection proceeding message may be used as a temporary response message of the call request message to indicate to the terminal 501 that the terminal 502 has correctly received the call request message, so as to prevent the delay in processing the call request message by the core network and the terminal 202 from causing the terminal 501 to always resend the call request message.

S505: the 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 transmits the connection proceeding message, the terminal 502 then transmits a ringing message to the terminal 501 via the core network for indicating that the call issued by the terminal 501 has been received, when the call issued by the terminal 201 is in the process of waiting to be received, and when the terminal 502 has received the call request of 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 to answer.

S507: the 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 call request of the calling user (e.g., the user presses the answer key), the terminal 502 transmits 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 (Header fields), where the Header fields include many fields and include additional information of the transmission message, such as a unique identifier of the call, a destination address, an address of the calling end, and a session type of the current session; the session type may be voice only, multimedia video for a web conference, or other types.

In this embodiment of the present application, the connection success message may also carry the User-to-User header field, where the User-to-User header field may also carry recording suppression information to suppress a recording function of the terminal 501 in a subsequent call process. Specifically, when the core network sends the connection success message to the terminal 501, the core network also sends 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 may parse the call request message, and if it is determined that the User-to-User header field included in the header field carries recording suppression information, the terminal 501 will actively suppress a recording function in a subsequent call process. Similarly, the operation of the terminal 501 to suppress the recording function is actively performed by the terminal 501 under the instruction of the recording suppression information, and this process is not affected by the operation of the called party (i.e., the calling party), and the calling party cannot start the function of recording a call by operating in the subsequent process.

After step S508 is completed, the bearer between the terminal 502 and the core network is already established, and the bearer can be used for voice, data and multimedia service data packet transmission in the subsequent process between the terminal 502 and the core network.

S509: the terminal 501 sends an acknowledgement message to the core network.

S510: the core network sends an acknowledgement message to the terminal 502.

Thereafter, the terminal 501 may return the confirmation message to the terminal 502 through the core network, which indicates that it has successfully received the connection success message sent by the terminal 502.

Thereafter, the session may be started between the terminal 501 and the terminal 502, and the media packets may be received and transmitted in a manner prescribed by the SIP protocol.

In the embodiment of the present application, the signaling interaction operation involved in the call establishment process is merely an example, and in the actual call establishment process, the signaling interaction process between the calling end and the called end may include more or less operations. In addition, in the embodiment of the present application, signaling sent and received between the calling end and the called end may be called other names, which is not limited in this application, for example, the call request message may be called Invite, the connection proceeding message may be called 100 Trying, the ringing message may be called 180 Ring, the connection success message may be called 200 OK, and the acknowledgement message may be called ACK.

Fig. 6 is an interaction flow chart of a communication method provided in the embodiment of the present application, which shows, based on fig. 5, a specific flow of implementing a function of suppressing recording of an opposite terminal in a communication process by a calling terminal and a called terminal in combination with a user operation. As shown in fig. 6, the interaction flow may include:

S601: the terminal 501 starts the inhibit opposite-end recording function in response to the first operation.

When the terminal 501 calls the terminal 502, if the calling subscriber does not wish the called subscriber to have the authority to record the call, the calling subscriber can enable the recording function of the opposite terminal (i.e., the terminal 502) through the above first operation. Specifically, the second operation may be an operation of the calling user pressing a dial key for a long time in a call interface shown in the terminal 501 (specifically, refer to the following description), or an operation of the calling user sending a voice command to the terminal 501 (for example, the calling user sends a command of "answer, prohibit recording" to the terminal 501 after the calling user receives a call from the terminal 501).

S602: the terminal 501 sends a call request message to the core network, where 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 a subsequent call establishment process with the terminal 502, the call request information sent by the terminal 501 to the core network may carry a User-to-User header field, where the User-to-User header field may include second recording suppression information. When the subsequent core network sends the call request message to the terminal 502, the first recording suppression information is sent to the terminal 502 along with the call establishment message.

S604: the terminal 502 suppresses the local call recording function when detecting that the User-to-User header field in the call setup request message includes the second recording suppression information.

After the terminal 502 receives the call request information sent by the core network, the terminal 502 may analyze whether the User-to-User header field in the call establishment request information carries the second recording suppression information. In the case that it is determined that the User-to-User header field included in the header field carries the second recording suppression information, the terminal 502 will actively suppress the recording function in the subsequent call process, and the called User cannot start the recording function in the subsequent process through operation.

S605: the terminal 502 initiates a inhibit opposite recording function in response to the second operation.

When the terminal 502 responds to the call of the terminal 501, if the called user does not want the calling user to have the authority to record the call, the called user can enable the recording function of the opposite terminal (i.e. the terminal 501) through the second operation. Specifically, the second operation may be an operation of the called user pressing a dial key for a long time in a call interface shown by the terminal 502 (specifically, refer to the following description), or an operation of the called user sending a voice command to the terminal 502 (for example, after the called user receives a call from the terminal 501 at the terminal 502, the called user speaks a command of "answer, prohibit recording" to the terminal 502).

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

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

Similarly, after the second operation is detected, in a 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, where the User-to-User header field may include second recording suppression information. When the subsequent core network sends the connection success message to the terminal 501, the second recording suppression information is sent to the terminal 501 together with the call establishment message.

S608: the terminal 501 suppresses the local call recording function when detecting that the User-to-User header field in the connection success message contains the second recording suppression information.

After the terminal 501 receives the connection success message sent by the core network, the terminal 501 may analyze whether the field in the connection success message carries the second recording suppression information. In the case that it is determined that the User-to-User header field included 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 cannot open the recording function of the call 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 start the operation of suppressing the recording function of the opposite terminal. For example, in the call setup process, if the calling user (i.e., the user of the terminal 501) performs the first operation, but the called user (i.e., the user of the terminal 502) does not perform the second operation, only the call request message sent from the terminal 501 to the terminal 502 via the core network includes the second recording suppression information, and the connection success message sent from the terminal 502 to the terminal 501 via the core network does not include the second recording suppression information, in this case, the terminal 502 will not be able to record in the subsequent call, but the terminal 501 may record. Accordingly, in the call setup process, if the calling subscriber does not perform the first operation, but the called subscriber performs the second operation, the call request message sent by the terminal 501 to the terminal 502 through the core network will not include the second recording suppression information, but the connection success message sent by the terminal 502 to the terminal 501 through the core network includes the second recording suppression information, in which case, the terminal 501 will not be able to record in the subsequent call, but the terminal 502 may record. However, no matter whether the calling party and the called party start the recording inhibition function or only one party in the call starts the recording inhibition function, the call between the calling party and the called party can be normal.

Next, a specific style of the above-mentioned structure of the User-to-User header field and the second recording suppression information included in the User-to-User header field will be described with reference to fig. 7.

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 call request message and the connection success message, fields in the User-to-User header domain and the User-to-User header domain included in the call request message and the connection success message do not exist in a binary format, but exist in the form of a character string. In addition, these header fields and cells serve as UUI data, which may be data that is inserted by an application program (which may be call software or an application in the embodiment of the present application) into the above-mentioned call request message and connection success message for starting/accepting a previous session between the calling side and the called side. Specifically, in the embodiment of the application, the User-to-User header field may be a newly defined field, where parameters included in the User-to-User header field may be extended according to a specific service related to the session, so as to implement a responsive service function in the session. For example, in the present application, the User-to-User header field may include the second recording suppression information to suppress a recording function of the terminal during a call.

Fig. 7 (a) and (B) show specific patterns of a call request message containing no second recording suppression information and a call request message containing second recording suppression information, respectively.

As shown in fig. 7 (a), the header field of the call request message 71 includes a User-to-User header field 711 and a plurality of header fields such as the header field 712. Wherein several fields including header field 712 are necessary for all message bodies, except for User-to-User header field 711; taking the header field 712 as an example, the header field carries information such as a request method, a request address, and a SIP version number related to the call request. However, since the call request message 71 is a request message sent from the calling party to the called party without starting the function of suppressing the recording at the opposite party, the User-to-User header field 711 in the call request message 71 contains only two parameter information of "342342ef34" (indicating a protocol number) and "encoding=hex" (indicating encoding in hexadecimal), and does not contain the second recording suppression information for suppressing the recording at the called party. Therefore, after the called terminal receives the call request message 70, the called terminal will not inhibit the recording inhibition function of the call, the called user can record the call normally, and the privacy of the calling user is not guaranteed.

As shown in fig. 7 (B), the call request message 72 includes a User-to-User header field 721 and a plurality of other necessary fields. The call request message 72 is a request message sent by the calling party to the called party in the case of starting the function of suppressing the recording at the opposite end, and 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 includes the above-mentioned second recording suppression information for suppressing the recording at the called party subsequently, that is, the parameter information "recording=disabled" existing in the User-to-User header field 721, in addition to the two parameter information of "342342ef34", "encoding=hex". Therefore, after the called terminal receives the call request message 72, the called terminal detects the recording suppression information in the field, actively suppresses the recording suppression function of the call, the called user cannot record the call, and the privacy security of the calling user in the call process is ensured.

Similarly, the specific style of the connection success message that does not include the second recording suppression information and the header field of the connection success message that includes the second recording suppression information may also refer to the foregoing description related to fig. 7, and will not be repeated here.

It should be noted that fig. 7 only illustrates a specific style of header fields in the call request message, which does not constitute any limitation. For example, in some embodiments, the User-to-User header field may not be present in the call request message that does not include the second recording suppression information. In addition, in some embodiments, the parameter form corresponding to the second recording suppression information may be other types, for example, "recording=0", "recording=false", or the parameter in the User-to-User header field may also include only the parameter corresponding to the second recording suppression information, which is not limited in this application.

S609: in the case of call connection, the terminal 501 outputs a presentation message.

S610: in the case of a call being connected, the terminal 502 outputs a prompt message.

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

Under the condition that the call is connected, the two terminals can inform the user at the side whether the user at the opposite side grants permission of the call record in the current call.

Specifically, the specific operations of step S609 to step S610 may refer to the foregoing descriptions of step S309 to step S310, and will not be described herein.

By implementing the communication method, under the IMS domain, the calling terminal and the called terminal can realize the function of suppressing the recording of the opposite terminal in the conversation process without influencing the conversation, and the privacy safety of the user in the conversation process can be effectively ensured.

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

Specifically, in the case where the terminal 501 is the "first terminal", the terminal 502 is the "second terminal", the call request message may be referred to as a "first message", and the connection success message may be referred to as a "second message".

Accordingly, in the case where the terminal 502 is the "first terminal", the terminal 501 is the "second terminal", and the connection success message may be referred to as the "first message".

3. One party of the calling and called terminals is in the CS domain, and the other party is in the IMS domain, see fig. 8-9.

Here, the signaling interaction flow involved in the session establishment procedure between the calling terminal and the called terminal is described by taking the case that the calling terminal is in the CS domain and the called terminal is in the IMS domain as an example, and refer to fig. 8 specifically.

As shown in fig. 8, the terminal 801 and the terminal 802 may be a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an augmented reality (augmented reality, AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (personaldigital assistant, PDA), or a special camera (e.g., a single-lens reflex camera, a card-type camera), etc., and the present application does not limit the specific type of the electronic device. Wherein, the terminal 801 is a calling terminal, the terminal 802 is a called terminal, and the steps of signaling interaction involved in the session establishment between the two terminals may include:

s801: the terminal 801 transmits a CM service request message to the core network.

S802: the core network transmits a CM service accept message to the terminal 801.

S803: the terminal 801 transmits a call establishment request message to the core network.

S804: the core network sends a call setup proceeding 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.

The specific content of step S801 to step S805 may refer to the foregoing description of step S201 to step S205, and the specific content of step S806 may refer to the foregoing description of step S502, which is not repeated here.

In step S802, since the terminal 801 is in the CM domain, if the User-User cell in the call establishment request message sent by the terminal 801 carries the first recording suppression information, the first recording suppression information is still present in the User-User cell in 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 converts the first suppression information carried in the message, that is, converts the first recording suppression information that exists in the eight-bit binary value sequence into the second recording suppression information that exists in the form of a string, stores the second recording suppression information in the User-to-User header field of the call request information, and sends the second recording suppression information to the terminal 802 (for example, the core network may detect that the User-User cell in the call establishment request message carries the first recording suppression information "01010101", when the call request message is generated, the core network converts the first recording suppression information into the second recording suppression information "recording=disabled", and sends the second recording suppression information to the terminal 802 after adding the second recording suppression information in the User-to-User header field of the call request message. Therefore, in step S806, if the second recording suppression information is carried in the call setup request message sent by the core network, the second recording suppression information still exists in the header field of the call request information in the form of a field.

S807: the terminal 802 sends a connection proceeding message to the core network.

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

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

S810: the 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 may refer to the descriptions of step S503, step S505 and step S507, and the specific contents of step S809 and step S811 may refer to the descriptions of step S210 and step S212, which are not repeated here.

Similarly, in step S810, since the terminal 802 is in the IMS domain, if the User-to-User header field in the connection success message sent by the terminal 802 carries the second recording suppression information, the second recording suppression information is still in the form of a string in the User-to-User header field of the connection success message. However, since the terminal 801 is in the CS domain, after the core network receives the connection success message with the second recording suppression information sent by the terminal 802, the core network converts the second suppression information carried in the message, that is, converts the second recording suppression information in the form of a character string into the first recording suppression information in the form of a binary number sequence of eight bits, and stores the first recording suppression information in a User-User cell of the call connection information, and sends the first recording suppression information to the terminal 801. Therefore, in step S811, if the call establishment connection message sent by the core network carries the first recording suppression information, the first recording suppression information still exists in the User-User cell of the call request information in the form of an eight-bit binary value sequence.

In the embodiment of the present application, the signaling interaction operation involved in the call establishment process is merely an example, and in the actual call establishment process, the signaling interaction process between the calling end and the called end may include more or less operations, which is not limited in the present application.

Fig. 9 is an interaction flow chart of a communication method provided in the embodiment of the present application, which shows, based on fig. 8, a specific flow of implementing a function of suppressing recording of an opposite terminal in a communication process by a calling terminal and a called terminal in combination with a user operation. As shown in fig. 9, the interaction flow may include:

s901: terminal 801 initiates a inhibit opposite recording function in response to a first operation.

S902: the terminal 801 transmits a call setup request message to the core network, where a User-User cell in the call setup request message includes first recording suppression information.

For the specific content of step S901 to step S902, reference may be made to the foregoing description of step S301 to step S302, which is not repeated here.

S903: the core network converts the first recording inhibition information.

Since the terminal 801 is in the CM domain, in the call setup request message, the User-User cell carries the first recording suppression information and still exists as an eight-bit binary number sequence. However, since the terminal 802 is in the IMS domain, after the core network receives the call setup request message with the first recording suppression information sent by the terminal 801, the core network converts the first suppression information carried in the message, that is, converts the first recording suppression information existing in the binary number sequence of eight bits into the second recording suppression information existing in the form of a character string, and stores the second recording suppression information in the header domain of the call request information, and sends the second recording suppression information to the terminal 802.

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

S905: the terminal 802 suppresses the local call recording function when detecting that the User-to-User header field in the call setup request message includes the second recording suppression information.

S906: the terminal 802 initiates a inhibit opposite recording function in response to the second operation.

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

S908: the core network converts the second recording inhibition information.

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

For the details of step S904 to step S907, reference may be made to the foregoing description of step S603 to step S606, which is not repeated here.

Since the terminal 802 is in the IMS domain, the User-to-User header field in the connection success message carries the second recording suppression information and also exists in the header field of the connection success message in the form of a character string. However, since the terminal 801 is in the CS domain, after the core network receives the connection success message with the second recording suppression information sent by the terminal 802, the core network converts the second suppression information carried in the message, that is, converts the second recording suppression information in the form of a character string into the first recording suppression information in the form of a binary number sequence of eight bits, and stores the first recording suppression information in a User-User cell of the call connection information, and sends the first recording suppression information to the terminal 801.

S910: and under the condition that the User-User information element in the call connection message is detected to contain the first recording inhibition information, inhibiting the local terminal call recording function.

S911: when the call is on, the terminal 801 outputs a prompt message.

S912: in the case of call connection, the terminal 802 outputs a prompt message.

For details of step S910 to step S912, reference may be made to the foregoing description of step S309 to step S310, which is not repeated here.

Correspondingly, when the calling terminal is in the IMS domain and the called terminal is in the CS domain, the method of communication interaction between the two terminals and the process of suppressing the recording of the opposite terminal may also refer to the related descriptions of fig. 8 and fig. 9, which are not repeated here.

By implementing the communication method, even if the calling terminal and the called terminal are in different output transmission domains, the calling terminal and the called terminal can realize the function of suppressing the recording of the opposite terminal in the conversation process without influencing the conversation, and the privacy safety of the user in the conversation process can be effectively ensured.

In this embodiment, both the terminal 801 and the terminal 802 may be referred to as a "first terminal" or a "second terminal", the above-described first recording suppression information and second recording suppression information may also be referred to as "recording suppression information", a sequence may be referred to as a "first sequence", and "01010101" parameter information "recording=disabled" may be referred to as a "character string that identifies a suppression request of the first terminal for the recording function of the second terminal".

Specifically, when the terminal 801 is the "first terminal", the terminal 802 is the "second terminal", and the call establishment request message and the call request message may be referred to as "first message", and the call connection message and the connection success message may be referred to as "second message".

Accordingly, in the case where the terminal 802 is the "first terminal", the terminal 801 is the "second terminal", and the call connection message and the connection success message may be referred to as the "first message".

Fig. 10 illustrates a flow of suppressing recording of the opposite end during a call by a calling end and a called end in conjunction with a user interface.

Specifically, the calling terminal and the called terminal in fig. 10 may be the terminal 201 and the terminal 202 in the foregoing description, or the terminal 501 and the terminal 502 in the foregoing description, or the terminal 801 and the terminal 802 in the foregoing description, respectively.

For ease of illustration, it is assumed here that both the calling and called ends in fig. 10 are in the IMS domain.

As shown in fig. 10, when the user interface 01 shown in (a) in fig. 10 is a dialing interface displayed by the calling terminal when the calling terminal dials to the called terminal, the dialing interface may be displayed with the mobile number "191 xxxxxxx" of the called user and a dialing key 011. In order to suppress the recording function of the called terminal in the subsequent call process, the calling User may perform a User operation with respect to the User interface 01, that is, a long-press operation on the dial key 011 shown in (a) of fig. 10, so that the calling terminal sends a call request message to the called terminal, where a header field of the call request message includes a User-to-User header field in the foregoing description, and the User-to-User header field includes the second recording suppression information.

After the called terminal receives the call request message sent by the calling terminal, the called terminal analyzes that the message carries the second recording inhibition information, at this time, the called terminal can actively inhibit the recording function of the called terminal on the call in the call process, and after inhibition, the called user cannot open the call through user operation.

Thereafter, when the called terminal transmits a ringing message to the calling terminal and the called terminal starts ringing, the called terminal may display a user interface 02 as shown in (a) of fig. 10, and the user interface 02 may be an incoming call interface displayed when the called terminal receives an incoming call. The user interface 02 may have displayed therein a caller's cell phone number "131XXXXXXXX", a hang-up key, and an answer key 021. In order to suppress the recording function of the calling terminal in the subsequent call process, the called User may perform a User operation with respect to the User interface 02, that is, a long-press operation on the answer key 021 shown in (B) in fig. 10, so that the called terminal sends a connection success request message to the called terminal, where the User-to-User header field of the connection success message also includes the second recording suppression information.

After the calling terminal receives the connection success message sent by the called terminal, the calling terminal can also analyze that the message carries the second recording inhibition information, the calling terminal can actively inhibit the recording function of the called terminal on the call in the call process, and after inhibition, the calling terminal can not be started through user operation.

Further, after the called user completes the incoming call of the calling user through the second operation, the calling and called terminals may display the user interface 03 as shown in (C) of fig. 10 and the user interface 04 as shown in (D) of fig. 10, respectively. It can be seen from the record function key 031 displayed in the user interface 03 and the record function key 041 displayed in the user interface 04 that the record functions of the calling terminal and the called terminal have been suppressed at this time, so that both the record function key 031 and the record function key 041 are in a non-selectable (unable to respond to the user operation) state.

Correspondingly, after the called user connects the incoming call of the calling user through the second operation, the calling end and the called end both start the function of suppressing the recording of the opposite end, so that the calling end and the called end output the prompt information. The prompt information can be a section of voice broadcast, and the specific content of the prompt information can be that the call is not recorded and the call is not allowed to be recorded/This call will not be recored and this call is not allowed to be recorded, which indicates that both parties of the call start the recording inhibition function.

In the embodiment of the present application, the user interface and the user operation shown in fig. 10 are only examples, which do not constitute a limitation of the present application. For example, in the actual call process, the user may trigger the function of suppressing the contralateral recording through other operations, for example, by setting the call process to default to prohibit the contralateral recording in the system setting of the terminal, or adding a corresponding function menu in the call interface, the user may select to click a corresponding function control to trigger the function of prohibiting the contralateral recording, or the user may trigger the function of prohibiting the contralateral recording through voice, for example, when the called terminal displays the user interface 02, the called user may issue a voice command of "answer, prohibit recording" to the called terminal, so as to prohibit the calling terminal from recording the call.

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

Fig. 11 exemplarily shows a structure of the electronic apparatus 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, keys 190, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc.

It should be understood that the illustrated structure of the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The I2C interface is a bi-directional synchronous serial bus comprising a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 may be coupled to a touch sensor, charger, flash, camera, etc., respectively, through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor through an I2C interface, such that the processor 110 communicates with the touch sensor through an I2C bus interface to implement a touch function of the electronic device 100.

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

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

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided 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. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, a receiver, etc.), or displays images or video through display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, antenna 1 and mobile communication module 150 of electronic device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that electronic device 100 may communicate with a network and other devices through wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

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

The internal memory 121 may be used to store computer executable program code including instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device 100 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The electronic device 100 may implement audio functionality through the audio module 170, the speaker 170A. Such as music playing, recording, etc.

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

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, 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 this application, the electronic device 100 may be used as a calling end or a called end, and perform a call through the mobile communication module 150 or the wireless communication module 160.

In some embodiments, in the process of establishing a call, the electronic device 100 may be used as a calling end to respond to a first operation of the calling user on the calling end, and send a request message carrying recording suppression information to other devices through the core network, so as to suppress a recording function of the other devices on the call in a subsequent call process.

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

In addition, in some embodiments, after receiving a request message sent by other devices through the core network in the call establishment process, the electronic device 100 may also be used as a called end to respond to the second operation of the called user, and reply a response message with recording suppression information to the device sending the request message, so as to suppress the recording function of the device on the call in the subsequent call process.

For example, in the case where the SIM card interface 195 is plugged into an available SIM card, the electronic device 100 may dial a call to another device into which a SIM card is plugged under the user operation, and if the user does not want the opposite user to record the call in the subsequent call, the user may perform the first operation in the dialing interface displayed on the electronic device 100 to start the function of suppressing the recording of the opposite terminal, and in particular, the first operation may be a long-press operation of the dialing key in the dialing interface by the user. After that, the electronic device 100 may respond to the first operation, and send a request message, for example, invite message, carrying recording suppression information to the called end of the call via the core network, where after receiving the request message carrying recording suppression information, the called end actively suppresses the call recording function of the called end according to the protocol rule, so that the called user is prohibited from recording the call, and privacy security of the calling user in the call process can be ensured.

Claims

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.