CN113542512A

CN113542512A - Call processing system, method, electronic device and storage medium

Info

Publication number: CN113542512A
Application number: CN202110739200.9A
Authority: CN
Inventors: 陈拴锋; 薛超; 罗飞; 熊正
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-06-30
Filing date: 2021-06-30
Publication date: 2021-10-22
Anticipated expiration: 2041-06-30
Also published as: CN113542512B

Abstract

The application relates to a call processing system, a call processing method, an electronic device and a storage medium. The call processing system comprises a calling device and a network. The calling device is used for responding To the dialing of the called device, sending an invite signaling with a To header field in an SIP URI format To the network, receiving a 100 signaling and a 183 signaling sent by the network To the calling device, and sending the invite signaling with a TO header field in a TEL URI format To the network when determining that a Reason value in a Reason header field is a target Reason value. The network is used for responding To the invite command with the To header field in TEL URI format To carry out SIP signaling interaction with the calling device again, and establishing the call connection between the calling device and the called device after the SIP signaling interaction with the calling device is completed. When the SIP signaling interaction is carried out between the calling device and the called device, if the Reason value in the Reason head field in the 183 signaling received by the calling device is the target Reason value, the invite signaling with the To head field in the TEL URI format is sent To the network so as To re-request the establishment of the call connection with the called device, and the call completing rate of the calling device is improved.

Description

Call processing system, method, electronic device and storage medium

Technical Field

The present application relates to the field of voice communication technologies, and in particular, to a call processing system, a call processing method, an electronic device, and a storage medium.

Background

Voice services of a Long Term Evolution (LTE) network are called Voice over LTE (VoLTE), and currently, more and more user terminals can support the VoLTE function. VoLTE is a voice technology based on IP (Internet Protocol) data transmission, and all services are carried on an LTE network, so that data and voice services can be unified in the same network. When performing the VoLTE function, the calling device needs to send a call request to the network to establish a call connection with the network. The network responds to the call request and carries out signaling interaction of Session Initiation Protocol (SIP) with the calling device to realize establishment of call connection. In the process of establishing the call connection, if the network can not respond to the call request to establish the call connection, an error code is sent to the calling device to inform the network of the failure of the call connection.

Disclosure of Invention

In view of the above, it is desirable to provide a call processing system, method and storage medium, which can automatically redial to realize a call connection with a network when receiving a connection failure message of the network, thereby improving a call completion rate of a calling device.

In a first aspect, an embodiment of the present application provides a call processing system, where the call processing system includes: a calling device to: responding To the dialing of the called device, and sending an invite signaling with a To header field in an SIP URI format To the network; receiving 100 signaling and 183 signaling sent by the network to the calling device, wherein the 183 signaling comprises a Reason header field, and the Reason header field comprises a Reason value; when the Reason value in the field of the Reason header field is determined TO be a target Reason value, transmitting an invite signaling with a TO header field in a TEL URI format TO the network; the network is configured to: responding To an invite signaling with a To header field in an SIP URI format, and sending a 100 signaling To the calling device; sending 183 signaling to the calling device; and responding To an invite command with a To header field in a TEL URI format To perform SIP signaling interaction with the calling device, and establishing the call connection between the calling device and the called device after the SIP signaling interaction is completed with the calling device. When the SIP signaling interaction is carried out between the calling device and the network, if the Reason value in the Reason head field of 183 signaling received by the calling device is the target Reason value, the invite signaling with the To head field in TEL URI format is sent To the network so as To re-request the establishment of the call connection with the called device, and the call completing rate of the calling device is improved.

In one implementation, the format of the Reason header field includes Reason SIP; the cause value includes 404 or 484, where the SIP field indicates the SIP protocol and the cause field is a cause value, and the target cause value of the Reason header field corresponding to the SIP protocol includes. Through the technical scheme, when the Reason value of the Reason header field is determined TO be 404 or 484, the call connection with the called device is requested again by sending an invite signaling with a TO header field in a TEL URI format TO the network.

In one implementation, the format of the Reason header field includes Reason q.850; the cause field indicates a q.850 protocol, and the cause field indicates a cause value, where the target cause value of the Reason header field corresponding to the q.850 protocol includes 1 or 28. Through the technical scheme, when the Reason value of the Reason header field is determined TO be 1 or 28, the call connection with the called device is requested again by sending an invite signaling with the TO header field in a TEL URI format TO the network.

In an implementation manner, the SIP signaling interaction between the calling device and the network includes that the network sends 100 signaling to the calling device, the network sends 183 signaling to the calling device, the calling device sends PRACK signaling to the network, the network replies 200ok signaling to the calling device, the calling device sends UPDATE signaling to the network, the network returns 200ok signaling to the calling device, the network returns Ring signaling to the calling device, and the calling device sends ACK signaling to the network.

In one implementation, the calling device is further configured to: and when the calling device and the called device are in call connection, recording the position information of the calling device in a position table. Through the technical scheme, the position information of the calling device can be recorded in the position table for storage.

In one implementation, the calling device is further configured to: responding to the new dialing of the called device, and acquiring the position information of the current position of the calling device; and when the position information of the current position of the calling device is determined To be recorded in the position table, sending an invite signaling with a To header field in a TEL URI format To the network To request for call connection with the called device. Through the technical scheme, when the current position of the calling device is recorded in the position table, the invite signaling using the TEL URI format is preferentially sent to the called device when the called device is dialed to call so as to quickly establish the call connection between the calling device and the called device.

In one implementation, the calling device is further configured to: and when the position information of the current position of the calling device is determined not To be recorded in the position table, sending an invite signaling with a To header field in an SIP URI format To the network To request for call connection with the called device. Through the technical scheme, when the current position of the calling device is not recorded in the position table, the invite signaling using the To header field as the SIP URI format is preferentially sent To the called device when the called device is dialed To call, so that the call connection between the calling device and the called device is quickly established.

In one implementation, the location information of the calling device includes a tracking area code. Through the technical scheme, when the tracking area code of the current position of the calling device is recorded in the position table, the invite signaling using the TEL URI format is preferentially sent to the called device when the called device is dialed to establish the call connection between the calling device and the called device quickly.

In one implementation, the location table is recorded in the calling device. Through the technical scheme, the calling device can inquire whether the position information of the calling device is recorded in the position table or not from the position table stored in the calling device, and the interaction flow of data is reduced.

In one implementation, the calling device is further configured to: and dialing the called device through a dialing interface. By the technical scheme, the dialing of the calling device to the called device is realized through the dialing interface.

In one implementation, the responding To the invite command with the To header field in the TEL URI format, and performing SIP signaling interaction with the calling device again includes: the network sends 100 signaling to the calling device; the network returns 183 signaling to the calling device; triggering and establishing a special bearer of the calling device and the called device by a core network; the calling device sends PRACK signaling to the network; the network returns 200ok signaling to the calling device; the calling device responds to the 200ok signaling and sends an UPDATE signaling to the network; the network returns 200ok signaling to the calling device; the network sends Ring signaling to the calling device; and the calling device sends ACK signaling to the network. By the technical scheme, complete SIP signaling interaction is realized between the calling device and the called device.

In one implementation, the invite signaling with the To header field in SIP URI format is invite (To: < SIP: XXXXXXXXXX @ ims, mnc011.mcc460.3gppnetwork.org >), and the invite signaling with the To header field in TEL URI format is invite (To: < TEL: XXXXXXXXXXXXX), wherein XXXXXXXXXXXXXXX is the telephone number of the called device.

In a second aspect, an embodiment of the present application provides a call processing method, where the method includes: responding To the dialing of the called device, and sending an invite signaling with a To header field in an SIP URI format To the network; receiving 100 signaling and 183 signaling sent by the network, wherein the 183 signaling comprises a Reason header field, and the Reason header field comprises a Reason value; and when the Reason value in the field of the Reason header field is determined TO be the target Reason value, sending an invite signaling with a TO header field in a TEL URI format TO the network. When the SIP signaling interaction is carried out between the calling device and the network, if the Reason value in the Reason head field of 183 signaling received by the calling device is the target Reason value, the invite signaling with the To head field in TEL URI format is sent To the network so as To re-request the establishment of the call connection with the called device, and the call completing rate of the calling device is improved.

In an implementation manner, the completing SIP signaling interaction with the network includes the network sending 100 signaling to the calling device, the network sending 183 signaling to the calling device, the calling device sending PRACK signaling to the network, the network replying 200ok signaling to the calling device, the calling device sending UPDATE signaling to the network, the network returning 200ok signaling to the calling device, the network returning Ring signaling to the calling device, and the calling device sending ACK signaling to the network.

In one implementation, the method is further configured to: and when the calling device and the called device are in call connection, recording the position information of the calling device in a position table. Through the technical scheme, the position information of the calling device can be recorded in the position table for storage.

In one implementation, the method is further configured to: responding to the new dialing of the called device, and acquiring the position information of the current position of the calling device; and when the position information of the current position of the calling device is determined To be recorded in the position table, sending an invite signaling with a To header field in a TEL URI format To the network To request for call connection with the called device. Through the technical scheme, when the current position of the calling device is recorded in the position table, the invite signaling using the TEL URI format is preferentially sent to the called device when the called device is dialed to call so as to quickly establish the call connection between the calling device and the called device.

In one implementation, the method is further configured to: and when the position information of the current position of the calling device is determined not To be recorded in the position table, sending an invite signaling with a To header field in an SIP URI format To the network To request for call connection with the called device. Through the technical scheme, when the current position of the calling device is not recorded in the position table, the invite signaling using the To header field as the SIP URI format is preferentially sent To the called device when the called device is dialed To call, so that the call connection between the calling device and the called device is quickly established.

In one implementation, the method is further configured to: and dialing the called device through a dialing interface. By the technical scheme, the dialing of the calling device to the called device is realized through the dialing interface.

In one implementation, re-interacting with the network for SIP signaling comprises: receiving 100 signaling sent by the network; receiving 183 signaling sent by the network; triggering and establishing a special bearer of the calling device and the called device by a core network; sending a PRACK signaling to the network, and establishing an exclusive bearer after the PRACK signaling is sent; receiving 200ok signaling sent by the network; responding to the 200ok signaling, and sending an UPDATE signaling to the network; receiving 200ok signaling sent by the network; receiving Ring signaling sent by the network; and sending ACK signaling to the network. By the technical scheme, complete SIP signaling interaction is realized between the calling device and the called device.

In one implementation, the error code includes 404 codes. Through the technical scheme, the calling device responds To the code 404 and sends an invite signaling with a To header field in a TEL URI format To the network.

In a third aspect, some embodiments of the present application provide an electronic device comprising a memory and a processor: wherein the memory is used for storing program instructions; and a processor for reading and executing the program instructions stored in the memory, and when the program instructions are executed by the processor, the electronic device is enabled to execute the call processing method.

In a fourth aspect, an embodiment of the present application provides a computer storage medium, which stores program instructions that, when executed on an electronic device, cause the electronic device to execute the above-mentioned call processing method.

In addition, the technical effects brought by the third to fourth aspects can be referred to the description related to the methods designed in the above methods, and are not repeated herein.

Drawings

FIG. 1 is a schematic diagram of an architecture of a call processing system according to an embodiment of the present application;

fig. 2 is a schematic diagram of a dialing interface of a calling device according to an embodiment of the present application;

fig. 3 is an interaction diagram for establishing an SIP signaling flow according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a call processing method according to an embodiment of the present invention;

fig. 5 is a flowchart illustrating a call processing method according to another embodiment of the present application;

fig. 6 is a flowchart illustrating a call processing method according to another embodiment of the present application;

fig. 7 is a user interface of a mobile network setup provided by an embodiment of the present application;

fig. 8 is a flowchart illustrating a call processing method according to an embodiment of the present invention;

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

Detailed Description

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or illustrations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. It should be understood that in this application, "/" means "or" means "unless otherwise indicated. For example, A/B may represent A or B. In the present application, "and/or" is only one kind of association relation describing an associated object, and means that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. "at least one" means one or more. "plurality" means two or more than two. For example, at least one of a, b, or c, may represent: a, b, c, a and b, a and c, b and c, a, b and c.

The User Interface (UI) in the embodiment of the present application is a media Interface for performing interaction and information exchange between an application program or an operating system and a User, and can implement conversion between an internal form of information and a form acceptable to the User. The user interface of the application program is a source code written by a specific computer language such as JAVA (JAVA), extensible markup language (XML), and the like, and the interface source code is analyzed and rendered on the electronic device, and finally presented as content that can be recognized by a user, such as controls such as pictures, words, buttons, and the like. A control (control) is a basic element of a user interface, and typical controls include a button (button), a widget (widget), a toolbar (toolbar), a menu bar (menu bar), a text box (text box), a scroll bar (scrollbar), a picture (image), and a text (text). The properties and contents of the controls in the interface are defined by tags or nodes, such as XML defining the controls contained by the interface by nodes < Textview >, < ImgView >, < VideoView >, and the like. A node corresponds to a control or attribute in the interface, and the node is rendered as user-viewable content after parsing and rendering. In addition, many applications, such as hybrid applications (hybrid applications), typically include web pages in their interfaces. A web page, also called a page, can be understood as a special control embedded in an application program interface, the web page is a source code written by a specific computer language, such as hypertext markup language (HTML), Cascading Style Sheets (CSS), JAVA scripts (JavaScript, JS), etc., and the web page source code can be loaded and displayed as a content recognizable to a user by a browser or a web page display component similar to a browser function. The specific content contained in the web page is also defined by tags or nodes in the source code of the web page, such as HTML, which defines elements and attributes of the web page by < p >, < img >, < video >, < canvas >.

A commonly used presentation form of the user interface is a Graphical User Interface (GUI), which refers to a user interface related to computer operations and displayed in a graphical manner. It may be an interface element such as an icon, window, control, etc. displayed in the display screen of the electronic device.

In order to better understand the call processing system disclosed in the embodiment of the present application, the call processing system of the present application is described below.

Fig. 1 is a schematic architecture diagram of a call processing system according to an embodiment of the present application. As shown in fig. 1, the call processing system 10 includes a calling device 20, a network 30, and a called device 40. The calling device 20 and the called device are respectively in communication connection with the network 30 through a 4G-LET communication protocol or a 5G New air interface (5G-New Radio) protocol or a next generation communication technology. The calling device 20 or the called device 40 in the embodiment of the present application may be an electronic device with LTE functions, such as a mobile phone, a tablet computer, a notebook computer, and a personal computer, and fig. 1 illustrates a mobile phone as an example. The network 30 referred to in the embodiment of the present application is a generic name of a core network and an access network device responsible for processing a voice service, and includes a calling Internet Protocol (IP) multimedia subsystem (IP multimedia subsystem, IMS) domain network on a calling side and a called IMS domain network on a called side. The IMS domain network of the calling side and the IMS domain network of the called side include an IMS domain Core network and an Evolved Packet Core (EPC). The IMS domain core network comprises: a service-call session control function (S-CSCF), an inquiry-call session control function (I-CSCF), a proxy-call session control function (P-CSCF), a Home Subscriber Server (HSS), a Session Border Controller (SBC), and several dedicated servers, such AS a multimedia telephony application server (MMTel AS). Wherein the I-CSCF may be collocated with the S-CSCF and may be referred to as "I/S-CSCF" for short. The SBC and P-CSCF may be collocated, and may be referred to as "SBC/P-CSCF" for short. The EPC may include a packet data network gateway (PGW), a Serving Gateway (SGW), and a Mobile Management Entity (MME). The PGW and the SGW may be combined together, and may be referred to as "SGW/PGW" for short.

The above network elements are all corresponding network elements in the IMS domain network in the prior art, and are not described in detail here, but only briefly described. For example: the S-CSCF may be used for registration, authentication control, session routing and service trigger control of the user and to maintain session state information. The I-CSCF may be used for assignment and querying of S-CSCFs for user registrations. The P-CSCF may be used as a proxy for signaling and messages. The HSS may be used to store subscriber subscription information and location information. SBCs may provide secure access and media handling. The MMTel AS provides basic services and supplementary services of the multimedia telephone. The MME is the core device of the EPC network. The SGW may be used for connection of the IMS core network to the wireless network, and the PGW may be used for connection of the IMS core network to the IP network.

It should be noted that the above description does not limit the architecture diagram of the call processing system 10 according to the embodiment of the present invention, and the architecture diagram of the call processing system 10 according to the embodiment of the present application includes, but is not limited to, that shown in fig. 1.

The call processing method 10 in the present application is applied to the call processing system 10 described above. When the calling device 20 calls the called device 40, the calling device 20 and the called device 40 perform a complete Session Initiation Protocol (SIP) signaling procedure through the network 30, so that the call between the calling device 20 and the called device 40 can be realized. For example, after the calling device 20 dials the number of the called device 40 through the dialing interface (refer to fig. 2), the calling device 20 and the called device 40 perform a session initiation protocol signaling procedure through the network 30 to implement a call between the calling device 20 and the called device 40.

Referring to fig. 3, an interaction diagram for establishing a SIP signaling flow according to an embodiment of the present invention is shown. When the calling device and the called device are both in the VOLTE network, and when a session is established, the calling device 20 and the called device 40 complete the interaction of the SIP signaling through the cooperation of the P-CSCF1 of the calling IMS domain network, the S-CSCF1 of the calling IMS domain network, the I-CSCF2 of the called IMS domain network, the S-CSCF2 of the called IMS domain network, and the P-CSCF2 of the called IMS domain network.

(1) When the calling device 20 starts dialing, the calling device 20 sends invite signaling to the called device 40 along the paths of the P-CSCF1, the S-CSCF1, the I-CSCF2, the S-CSCF2, and the P-CSCF 2.

(2) After receiving the invite signaling, the called device 40 transmits 100 a signaling to the calling device.

(3) After receiving the invite signaling, the called device 40 returns 183 signaling to the calling device 20 along the paths of the P-CSCF2, the S-CSCF2, the I-CSCF2, the S-CSCF1, and the P-CSCF 1.

(4) The core network triggers the establishment of the proprietary bearers of the calling device 20 and the called device 40.

(5) After the 183 signaling is received by the calling device 20, the calling device 20 sends PRACK signaling to the called device 40 along the paths of the P-CSCF1, the S-CSCF1, the I-CSCF2, the S-CSCF2, and the P-CSCF 2.

(6) After the called device 40 receives the PRACK signaling, the called device 40 returns 200ok signaling to the calling device 20 along the paths of the P-CSCF2, S-CSCF2, I-CSCF2, S-CSCF1, and P-CSCF 1.

(7) After the calling device 20 receives the 200ok signaling sent by the called device 40, the calling device 20 sends UPDATE signaling to the called device 40 along the paths of the P-CSCF1, the S-CSCF1, the I-CSCF2, the S-CSCF2, and the P-CSCF 2.

(8) After the called device 40 receives the UPDATE signaling, the called device 40 returns 200ok signaling to the calling device 20 along the paths of the P-CSCF2, S-CSCF2, I-CSCF2, S-CSCF1, and P-CSCF 1.

(9) The called device 40 then returns Ring signaling to the calling device 20 along the path of the P-CSCF2, S-CSCF2, I-CSCF2, S-CSCF1, and P-CSCF 1.

......

(n) finally, calling device 20 sends ACK signaling to called device 40 along the paths of P-CSCF1, S-CSCF1, I-CSCF2, S-CSCF2, and P-CSCF 2.

When receiving the ACK signaling, the called device 40 makes a call to the called device 40 successfully from the calling device 20, and a call can be formally established between the calling device 20 and the called device 40.

However, it is found through research that, in the call processing method, when the calling device 20 and the called device 40 perform the above interaction process of the SIP signaling flow in fig. 3, and when the calling device 20 sends an invite signaling with a To header field in the SIP URI format To the network 30 To establish a communication connection with the device 40, for example, the invite signaling with the To header field in the SIP URI format is invite (To: < SIP: xxxxxxxxxxxx @ ims.mnc011.mcc460.3gppnetwork.org >). The network 30 adds @ symbols To invite signaling with a To header field in SIP URI format To address the called device 40, for example, the network 30 adds @ symbols To invite (To: < SIP: xxxxxxxxxx @ ims. mnc011.mcc460.3gpp network.org >) To address the called device 40, so that two @ symbols appear in invite signaling, which easily causes addressing failure of the called device 40 by the network 30, so that the network 30 feeds back SIP error codes To the calling device 20, and finally causes call failure between the calling device 20 and the called device 40. In view of the above technical problems, the present application provides a call processing method. Referring to fig. 4, a flowchart of a call processing method according to an embodiment of the present application is shown. The method is used for a schematic diagram of redialing to reestablish a call connection when the SIP signaling establishment process between the calling device 20 and the called device 40 fails, and some network elements through which signaling interaction passes in the diagram are not shown, such as SGW/PGW, SBC/P-CSCF, I-CSCF/S-CSCF, etc., for simplicity and understanding of description. The method specifically comprises the following steps.

In step S401, in response To the dialing To the called device 40, the calling device 20 sends an invite signaling with a To header field in the SIP URI format To the network 30.

In this embodiment, the invite signaling with the header of To in the SIP URI format is invite (To: < SIP: XXXXXXXXXX @ ims. mnc011.mcc460.3gppnetwork. org.). Where XXXXXXXXXX is the telephone number of the called device 40. For example, invite signaling with a header field of SIP URI format To invite (To: < SIP:13388888888@ ims. mnc011.mcc460.3gppnetwork. org.).

At step S402, the network 30 sends 100 a signaling to the calling device 20.

In step S403, the network 30 returns 183 signaling to the calling device 20, where the 183 signaling includes a Reason header field, and the Reason header field includes a cause value.

Step S404, when the calling device 20 determines that the cause value in the Reason header field is the target cause value, sends an invite signaling whose TO header field is in a TEL URI format TO re-request TO establish a call connection with the called device 40, where the TO header field of the invite signaling is in the TEL URI format.

The RFC 33261.0 protocol describes the Reason header as follows: "The Reason header field a can be used to be used for The sub encapsulation.." Clients and servers are from one to two of The headers field it has no impact on The protocol processing. ", i.e. The Reason header field is only a candidate additional description for The scene and is not a necessary option, and ignoring The Reason header field does not affect The protocol processing. In the embodiment, the format of the Reason header field comprises Reason and SIP; cause value and Reason q.850; cause-value. In this embodiment, the 183 signaling may further include an early media field, and the early media field in the 183 signaling is used to indicate that early media has been opened. For example, 183 is 183(P-Early-Media: sensoronly response: q.850: cause ═ 1), where P-Early-Media: sensoronly is an Early Media field used to indicate that Early Media has been opened, and Reason q.850: cause ═ 1 is a Reason header field used to indicate a call connection exception.

In this embodiment, the target cause value indicates that the call connection is abnormal and the connection abnormality is related TO the SIP URL format used in the TO header field of the invite signaling. Wherein, in the RFC 3261 protocol, "Reason: SIP; the target cause value of the Reason head field in the cause value format is defined as 404 or 484. In the ITU-T Q.850 protocol, "Reason: Q.850; the target cause value of the Reason head field of cause value "is defined as 1 or 28. For example, a cause value (cause)1 is specified in the ITU-T Q.850 protocol: "This cause indexes that the called party can not be reached at the called party's number in a valid format, it is not currently allocated".

In this embodiment, the invite signaling with the To header in TEL URI format is invite (To: < TEL: XXXXXXXXXXXXX), where XXXXXXXXXXXXX is the phone number of the called device 40. For example, invite signaling with a TO header in TEL URI format is invite (To: < TEL:13388888888 >).

The protocol RFC 32618.1.1.2 states the To header fields as follows: "The To header field MAY be MAY contact a SIP or SIPS URI, but it MAY be a male URI scheme (The TEL URI (RFC 2806[9]), for example), while The hall SIP protocol. The protocol RFC 39669.0 states the To header fields as follows: in SIP URIs, the y-shaped like the user part, i.e. SIP URI and tel URI formats, may contain telephone numbers, wherein in the SIP URI format, a telephone number is used as the user part of the SIP URI format.

Step S405, the network 30 responds To the invite command with the To header field in the TEL URI format, completes SIP signaling interaction with the calling device 20, and establishes a call connection between the calling device 20 and the called device 40 after completing the SIP signaling interaction with the calling device 20.

In this embodiment, the calling device 20 interacts with the network 30 according to the SIP signaling described in fig. 3.

In an embodiment of the present application, when the calling device 20 receives the 183 signaling sent by the network 30, it may be determined whether to send an invite command in a TEL URI format to the network 30 again to reestablish the call connection between the calling device 20 and the called device 40 based on the Reason header field of the 183 signaling returned by the network 30 to the calling device 20. Specifically, referring to fig. 5, a flowchart of a call processing method according to an embodiment of the present application is shown, which specifically includes the following steps.

In step S501, in response To the dialing To the called device 40, the calling device 20 sends an invite signaling with a To header field in the SIP URI format To the network 30.

At step S502, the network 30 sends 100 a signaling to the calling device 20.

Step S503, the network 30 returns 183 signaling to the calling device 20, where the 183 signaling includes a Reason header field, and the Reason header field includes a cause value, where the cause value indicates that the call connection is abnormal.

In this embodiment, the interaction of the SIP signaling after 183 signaling includes that the calling device 20 sends a PRACK signaling to the network 30, the network 30 replies a 200ok signaling to the calling device 20, the calling device 20 sends an UPDATE signaling to the network 30, the network 30 returns a 200ok signaling to the calling device 20, the network 30 returns a Ring signaling to the calling device … …, and the calling device 20 sends an ACK signaling to the network 30, which may specifically refer to the description content of fig. 3, and is not described in detail here.

And step S504, responding to the 183 signaling to judge whether the reason value is the target reason value. If the Reason value in the Reason header field is the target Reason value, step S505 is executed, otherwise, if the Reason value in the Reason header field is not the target Reason value, no response is made. The non-response means that the call processing method provided by the application does not perform special processing and executes a subsequent interactive process according to the existing SIP protocol.

In this embodiment, the target cause value indicates that the call connection is abnormal and the connection abnormality is related To the SIP URI format used in the To header field of the invite signaling. In the RFC 3261 protocol, the target cause value in the Reason header field is defined as 404 or 484. In the ITU-T q.850 protocol, the target cause value of the Reason header field is defined as 1 or 28.

In step S505, the calling device 20 sends invite signaling with a To header field in TEL URI format To the network 30 To request the call connection with the called device 40 again.

Step S506, after the calling device 20 and the network 30 complete the interaction of the SIP signaling, the call connection between the calling device 20 and the called device 40 is established.

In the embodiment of the present application, the calling device 20 sends an invite signaling using an SIP URI format To the network 20 To request a call connection with the called device 40 when dialing, and resends the invite signaling using a TEL URI format of a To header field To the network 30 To request a call connection with the called device 40 again if it is determined that the call connection fails according To the cause value of the Reason header field of the 183 signaling replied by the network 30 and the cause value is the target cause value. After completing the SIP signaling interaction with the network 30, the calling device 20 establishes a call connection with the called device 40, thereby improving the call completing rate.

In an embodiment of the present invention, after step S506, the method includes: when it is determined that the calling device 20 makes a call connection with the called device 40, the location information of the calling device 20 is recorded in the location table. In this embodiment, the location information of the calling device 20 includes Tracking Area Code (TAC), that is, when the calling device 20 and the called device 40 reestablish a call connection with the called device 40 through invite signaling with a To header field in a TEL URI format, the Tracking Area Code corresponding To the current location of the calling device 20 is recorded in the location table. In this embodiment, after recording the current tracking area code of the calling device 20 in the location table, the calling device 20 preferentially sends invite signaling using the TEL URI format to the called device 40 when dialing to call the called device 40 at the location corresponding to the tracking area code next time, so as to quickly establish a call connection between the calling device 20 and the called device 40. Specifically, referring to fig. 6, a flowchart of a call processing method in another embodiment of the present application is shown, the method including the following steps.

In step S601, the calling device 20 responds to the dialing of the called device 40 to obtain the tracking area code corresponding to the current location of the calling device 20.

Step S602 determines whether the tracking area code of the current position of calling device 20 is recorded in the position table. If the tracking area code of the current location of calling device 20 is recorded in the location table, step S603 is executed, otherwise, if the tracking area code of the current location of calling device 20 is not recorded in the location table, step S604 is executed.

In step S603, the calling device 20 sends invite signaling with a To header field in a TEL URI format To the network 30 To request a call connection with the called device 40. After step S603 is executed, step S605 is executed.

In step S604, the calling device 20 sends invite signaling with a To header field in the SIP URI format To the network 30 To request a call connection with the called device 40. After step S604 is executed, step S605 is executed.

In step S605, the network 30 responds to the invite instruction, completes the SIP signaling interaction procedure with the calling device 20, and establishes the call connection between the calling device 20 and the called device 40 after completing the SIP signaling interaction procedure with the calling device 20.

In this embodiment, the call processing method may be applied to an application scenario of VoLTE call. Specifically, referring to fig. 7, a user interface 7 of a mobile network setup provided in the embodiment of the present application is shown. The user interface 7 of the mobile network settings comprises a VoLTE talk function switch control 71. In this embodiment, the VoLTE call function switch control 71 is used to set an on/off state of the VoLTE call function. Specifically, the VoLTE call function switch control 71 has two display states, an "ON" state and an "OFF" state. When the VoLTE call function switch control 71 is displayed in the "ON" state, if a user operation (e.g., a leftward sliding operation) of the VoLTE call function switch control 71 by the user is received, the calling device 20 turns OFF the VoLTE call function in response to the user operation, and switches the VoLTE call function switch control 71 from the display "ON" state to the display "OFF" state. When the VoLTE function switch control 71 is displayed in the "OFF" state, if a user operation (for example, a rightward sliding operation) of the VoLTE pass-through function switch control 71 by the user is received, the calling device 20 turns ON the VoLTE call function in response to the user operation, and switches the VoLTE call function switch control 201 from the display "OFF" state to the display "ON" state. After the VoLTE call function is turned on, the calling device 20 responds to the dialing of the called device 40, completes the SIP signaling interaction process with the calling device 20, and establishes a call connection between the calling device 20 and the called device 40 after completing the SIP signaling interaction process with the calling device 20.

In another embodiment of the present application, during the interaction process of the SIP signaling flow of fig. 3, if the call fails, the network 30 sends an SIP error code to the calling device 20, and the calling device 20 initiates a Circuit Switched (CS) redial to the network 30 in response to the SIP error code to establish a call connection between the calling device 20 and the called device 40 through a CS network. Specifically, referring to fig. 8, a flowchart of a call processing method according to an embodiment of the present invention is shown. The method specifically comprises the following steps.

In step S801, the calling device 20 sends invite signaling to the network 30 in response to the dialing of the called device 40.

In this embodiment, the invite signaling may be invite signaling in which the To header field is in an SIP URI format, or invite signaling in which the To header field is in a TEL URI format.

At step S802, the network 30 sends 100 a signaling to the calling device 20.

In step S803, the network 30 returns 183 signaling to the calling device 20.

The calling device 20 receives the SIP error code of the network 30 before signaling step S804, 180, which is not limited to the network reply to the initial INVITE or UPDATE signaling.

In this embodiment, the error code is 4 XX. For example, the error code may be a 404 code (indicating that the user is not present), and the network 30 sends the error code to the calling device 20 to indicate that the user is not present when determining that the call connection between the calling device 20 and the called device 40 is failed.

In step S805, when the calling device 20 determines that the signaling received before receiving the SIP error code of the network 30 does not include the P-Early-Media Early Media field indicating that Early Media is on, the calling device 20 initiates CS redial to the network 30 to establish a call connection between the calling device 20 and the called device 40 through the CS network.

In the embodiment provided in the present application, the calling device 20 may be an electronic device, and the electronic device 100 according to the embodiment of the present application is described below. Referring to fig. 9, fig. 9 is a schematic structural diagram of an electronic device 100 according to an embodiment of the present disclosure.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

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

A memory may also be provided in processor 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 have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

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

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K via an I2C interface, such that the processor 110 and the touch sensor 180K communicate via an I2C bus interface to implement the touch functionality of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

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

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture functionality of electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

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

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

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device 100 through the power management module 141 while charging the battery 142.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140, and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

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 can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 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 disposed 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 a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the 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 modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on 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, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

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

The electronic device 100 implements display functions via the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

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

The electronic device 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

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

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

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

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

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

The internal memory 121 may include one or more Random Access Memories (RAMs) and one or more non-volatile memories (NVMs).

The random access memory may include static random-access memory (SRAM), dynamic random-access memory (DRAM), synchronous dynamic random-access memory (SDRAM), double data rate synchronous dynamic random-access memory (DDR SDRAM), such as fifth generation DDR SDRAM generally referred to as DDR5 SDRAM, and the like;

the nonvolatile memory may include a magnetic disk storage device, a flash memory (flash memory).

The FLASH memory may include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operation principle, may include single-level cells (SLC), multi-level cells (MLC), three-level cells (TLC), four-level cells (QLC), etc. according to the level order of the memory cells, and may include universal FLASH memory (UFS), embedded multimedia memory cards (eMMC), etc. according to the storage specification.

The random access memory may be read and written directly by the processor 110, may be used to store executable programs (e.g., machine instructions) of an operating system or other programs in operation, and may also be used to store data of users and applications, etc.

The nonvolatile memory may also store executable programs, data of users and application programs, and the like, and may be loaded into the random access memory in advance for the processor 110 to directly read and write.

The external memory interface 120 may be used to connect an external nonvolatile memory to extend the storage capability of the electronic device 100. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are saved in an external nonvolatile memory.

The internal memory 121 or the external memory interface 120 is used to store one or more computer programs. One or more computer programs are configured to be executed by the processor 110. The one or more computer programs include a plurality of instructions that, when executed by the processor 110, can implement the call processing method executed on the electronic device 100 in the above-described embodiments to implement the call processing function of the electronic device 100.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. 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 some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The electronic apparatus 100 can listen to music through the speaker 170A or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the electronic apparatus 100 receives a call or voice information, it can receive voice by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, perform directional recording, and so on.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be an open mobile electronic device 100 platform (OMTP) standard interface of 3.5mm, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

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

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

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 180C.

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

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

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, electronic device 100 may utilize range sensor 180F to range for fast focus.

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

The ambient light sensor 180L is used to sense the ambient light level. Electronic device 100 may adaptively adjust the brightness of display screen 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 can utilize the collected fingerprint characteristics to unlock the fingerprint, access the application lock, photograph the fingerprint, answer an incoming call with the fingerprint, and so on.

The temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 implements a temperature processing strategy using the temperature detected by temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 performs a reduction in performance of a processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, the electronic device 100 heats the battery 142 when the temperature is below another threshold to avoid the low temperature causing the electronic device 100 to shut down abnormally. In other embodiments, when the temperature is lower than a further threshold, the electronic device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown due to low temperature.

The touch sensor 180K is also called a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on a surface of the electronic device 100, different from the position of the display screen 194.

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

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

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

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

The SIM card interface 195 is used to connect a SIM card. The SIM card can be brought into and out of contact with the electronic apparatus 100 by being inserted into the SIM card interface 195 or being pulled out of the SIM card interface 195. 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 a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 195 can be inserted with multiple cards at the same time. 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 implement functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The present embodiment also provides a computer storage medium, in which computer instructions are stored, and when the computer instructions are run on the electronic device 100, the electronic device 100 executes the related method steps to implement the call processing method in the foregoing embodiment.

The present embodiment also provides a computer program product, which when running on a computer, causes the computer to execute the relevant steps described above, so as to implement the call processing method in the above embodiment.

In addition, embodiments of the present application also provide an apparatus, which may be specifically a chip, a component or a module, and may include a processor and a memory connected to each other; the memory is used for storing computer execution instructions, and when the device runs, the processor can execute the computer execution instructions stored in the memory, so that the chip can execute the call processing method in the above-mentioned method embodiments.

The electronic device 100, the computer storage medium, the computer program product, or the chip provided in this embodiment are all configured to execute the corresponding methods provided above, so that the beneficial effects achieved by the electronic device may refer to the beneficial effects in the corresponding methods provided above, and are not described herein again.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the module or unit is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed to a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Finally, it should be noted that the above embodiments are only used for illustrating the technical solutions of the present application and not for limiting, and although the present application is described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions can be made on the technical solutions of the present application without departing from the spirit and scope of the technical solutions of the present application.

Claims

1. A call processing system, the call processing system comprising:

a calling device to:

responding To the dialing of the called device, and sending an invite signaling with a To header field in an SIP URI format To the network;

receiving 100 signaling and 183 signaling sent by the network to the calling device, wherein the 183 signaling comprises a Reason header field, and the Reason header field comprises a Reason value;

when the Reason value in the field of the Reason header field is determined TO be a target Reason value, transmitting an invite signaling with a TO header field in a TEL URI format TO the network;

the network is configured to:

responding To an invite signaling with a To header field in an SIP URI format, and sending a 100 signaling To the calling device;

sending 183 signaling to the calling device;

and responding To an invite command with a To header field in a TEL URI format To perform SIP signaling interaction with the calling device, and establishing the call connection between the calling device and the called device after the SIP signaling interaction is completed with the calling device.

2. The call processing system of claim 1 wherein the format of the Reason header field includes Reason SIP; the cause value includes 404 or 484, where the SIP field indicates the SIP protocol and the cause field is a cause value, and the target cause value of the Reason header field corresponding to the SIP protocol includes.

3. The call processing system of claim 1 wherein the format of the Reason header field includes Reason q.850; the cause field indicates a q.850 protocol, and the cause field indicates a cause value, where the target cause value of the Reason header field corresponding to the q.850 protocol includes 1 or 28.

4. The call processing system of claim 1, wherein the SIP signaling interaction between the calling device and the network comprises the network sending 100 signaling to the calling device, the network sending 183 signaling to the calling device, the calling device sending PRACK signaling to the network, the network replying to 200ok signaling to the calling device, the calling device sending UPDATE signaling to the network, the network returning 200ok signaling to the calling device, the network returning Ring signaling to the calling device, the calling device sending ACK signaling to the network.

5. The call processing system of claim 1, wherein the calling device is further configured to:

and when the calling device and the called device are in call connection, recording the position information of the calling device in a position table.

6. The call processing system of claim 5, wherein the calling device is further configured to:

responding to the new dialing of the called device, and acquiring the position information of the current position of the calling device;

and when the position information of the current position of the calling device is determined To be recorded in the position table, sending an invite signaling with a To header field in a TEL URI format To the network To request for call connection with the called device.

7. The call processing system of claim 5, wherein the calling device is further configured to:

and when the position information of the current position of the calling device is determined not To be recorded in the position table, sending an invite signaling with a To header field in an SIP URI format To the network To request for call connection with the called device.

8. The call processing system of claim 5, wherein the location information of the calling device comprises a tracking area code.

9. The call processing system of claim 5, wherein the location table is recorded in the calling device.

10. The call processing system of claim 1, wherein the calling device is further configured to:

and dialing the called device through a dialing interface.

11. The call processing system of claim 1, wherein the response To header field is an invite command in TEL URI format, and the SIP signaling interaction with the calling device comprises:

the network sends 100 signaling to the calling device;

the network returns 183 signaling to the calling device;

triggering and establishing a special bearer of the calling device and the called device by a core network;

the calling device sends PRACK signaling to the network;

the network returns 200ok signaling to the calling device;

the calling device responds to the 200ok signaling and sends an UPDATE signaling to the network;

the network returns 200ok signaling to the calling device;

the network sends Ring signaling to the calling device;

and the calling device sends ACK signaling to the network.

12. The call processing system of claim 1, wherein the invite signaling with the To header field in SIP URI format is invite (To: < SIP: XXXXXXXXXX @ ims.mnc011.mcc460.3gppnetwork.org >), and the invite signaling with the To header field in TEL URI format is invite (To: < TEL: XXXXXXXXXXXXX), wherein XXXXXXXXXXXXXXXXXXX is the telephone number of the called device.

13. A method of call processing, the method comprising:

receiving 100 signaling and 183 signaling sent by the network, wherein the 183 signaling comprises a Reason header field, and the Reason header field comprises a Reason value;

and when determining that the Reason value in the field of the Reason header field is a target Reason value, sending an invite signaling with a TO header field in a TEL URI format TO the network TO perform SIP signaling interaction with the network, and establishing a call connection between a calling device and a called device after the SIP signaling interaction with the network is completed.

14. The call processing method of claim 13, wherein the format of the Reason header field includes Reason SIP; the cause value includes 404 or 484, where the SIP field indicates the SIP protocol and the cause field is a cause value, and the target cause value of the Reason header field corresponding to the SIP protocol includes.

15. The call processing method of claim 13, wherein the format of the Reason header field includes Reason q.850; the cause field indicates a q.850 protocol, and the cause field indicates a cause value, where the target cause value of the Reason header field corresponding to the q.850 protocol includes 1 or 28.

16. The call processing method of claim 13, wherein the interacting with the network through SIP signaling comprises the network sending 100 signaling to the calling device, the network sending 183 signaling to the calling device, the calling device sending PRACK signaling to the network, the network replying 200ok signaling to the calling device, the calling device sending UPDATE signaling to the network, the network returning 200ok signaling to the calling device, the network returning Ring signaling to the calling device, the calling device sending ACK signaling to the network.

17. The call processing method of claim 13, wherein the method is further configured to:

18. The call processing method of claim 17, wherein the method is further for:

19. The call processing method of claim 18, wherein the method is further for:

20. The call processing method of claim 19, wherein the location information of the calling device comprises a tracking area code.

21. The call processing method of claim 17, wherein the location table is recorded in the calling device.

22. The call processing method of claim 13, wherein the method is further configured to:

and dialing the called device through a dialing interface.

23. The call processing method of claim 13, wherein the SIP signaling interaction with the network comprises:

receiving 100 signaling sent by the network;

receiving 183 signaling sent by the network;

sending a PRACK signaling to the network,

receiving 200ok signaling sent by the network;

responding to the 200ok signaling, and sending an UPDATE signaling to the network;

receiving 200ok signaling sent by the network;

receiving Ring signaling sent by the network;

and sending ACK signaling to the network.

24. The method of claim 13, wherein the invite signaling with the To header field in SIP URI format is invite (To: < SIP: XXXXXXXXXX @ ims.mnc011.mcc460.3gppnetwork.org >), and the invite signaling with the To header field in TEL URI format is invite (To: < TEL: XXXXXXXXXXXXX), wherein XXXXXXXXXXXXXXXXXXX is the telephone number of the called device.

25. An electronic device, comprising a memory and a processor:

wherein the memory is to store program instructions;

the processor configured to read and execute the program instructions stored in the memory, and when the program instructions are executed by the processor, cause the electronic device to perform the call processing method according to any one of claims 13 to 24.

26. A computer storage medium storing program instructions that, when run on an electronic device, cause the electronic device to perform a call processing method according to any one of claims 13 to 24.