CN109548181B - Information acquisition method and device, storage medium and mobile terminal - Google Patents

Information acquisition method and device, storage medium and mobile terminal Download PDF

Info

Publication number
CN109548181B
CN109548181B CN201910024368.4A CN201910024368A CN109548181B CN 109548181 B CN109548181 B CN 109548181B CN 201910024368 A CN201910024368 A CN 201910024368A CN 109548181 B CN109548181 B CN 109548181B
Authority
CN
China
Prior art keywords
srvcc
type information
srvcc type
network side
character string
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910024368.4A
Other languages
Chinese (zh)
Other versions
CN109548181A (en
Inventor
司广磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN201910024368.4A priority Critical patent/CN109548181B/en
Publication of CN109548181A publication Critical patent/CN109548181A/en
Application granted granted Critical
Publication of CN109548181B publication Critical patent/CN109548181B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection

Abstract

The embodiment of the application discloses an information acquisition method, an information acquisition device, a storage medium and a mobile terminal. The method comprises the following steps: in the process of establishing the long-term evolution voice-bearing call, a first character string and a second character string sent by a network side are received, first SRVCC type information is obtained from the first character string, second SRVCC type information is obtained from the second character string, and third SRVCC type information is determined according to the first SRVCC type information and the second SRVCC type information, wherein the third SRVCC type information comprises all SRVCC types supported by the network side. By adopting the technical scheme, the embodiment of the application can comprehensively acquire the SRVCC type supported by the network side, and avoids subsequent SRVCC switching failure caused by incomplete type acquisition.

Description

Information acquisition method and device, storage medium and mobile terminal
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to an information acquisition method, an information acquisition device, a storage medium and a mobile terminal.
Background
With the large-scale deployment of Long Term Evolution (LTE) networks, more and more places cover LTE networks, and LTE networks can provide hundreds of megabits of data transmission rate and can undertake data transmission in multimedia forms such as traditional voice transmission, high-definition digital voice, high-definition video and the like.
At present, more and more operators introduce an Internet Protocol (IP) Multimedia Subsystem (IMS) network based on an LTE network, so as to provide a Voice over Long Term Evolution (VoLTE) function for a user. In a place without LTE network coverage, it is necessary to maintain Call Continuity by way of Single Radio Voice Call Continuity (SRVCC). There are various types of SRVCC, and when SRVCC handover is performed, a mobile terminal needs to acquire an SRVCC type supported by a network side.
Disclosure of Invention
The embodiment of the application provides an information acquisition method, an information acquisition device, a storage medium and a mobile terminal, which can optimize the scheme for acquiring SRVCC information from a network side by the mobile terminal.
In a first aspect, an embodiment of the present application provides an information obtaining method, including:
receiving a first character string and a second character string sent by a network side in the process of establishing a long-term evolution voice bearing call;
obtaining first single-channel voice call continuity (SRVCC) type information from the first character string, and obtaining second SRVCC type information from the second character string;
and determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, wherein the third SRVCC type information comprises all SRVCC types supported by a network side.
In a second aspect, an embodiment of the present application provides an information acquiring apparatus, including:
the character string receiving module is used for receiving a first character string and a second character string sent by a network side in the process of establishing the long-term evolution voice bearing conversation;
an information obtaining module, configured to obtain first single channel voice call continuity, SRVCC, type information from a first character string in the first message, and obtain second SRVCC type information from a second character string in the first message;
and the information determining module is used for determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, wherein the third SRVCC type information comprises all SRVCC types supported by a network side.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements an information obtaining method according to an embodiment of the present application.
In a fourth aspect, an embodiment of the present application provides a mobile terminal, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the information acquisition method according to the embodiment of the present application.
According to the information acquisition scheme provided by the embodiment of the application, in the VoLTE call establishment process, a first character string and a second character string sent by a network side are received, first SRVCC type information and second SRVCC type information are respectively acquired from the first character string and the second character string, and the SRVCC type supported by the network side is determined according to the first SRVCC type information and the second SRVCC type information. By adopting the technical scheme, the SRVCC type supported by the network side can be comprehensively obtained, and the failure of subsequent SRVCC switching caused by incomplete type obtaining is avoided.
Drawings
Fig. 1 is a schematic flowchart of an information obtaining method according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of another information acquisition method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another information acquisition method according to an embodiment of the present application;
fig. 4 is a block diagram of an information acquisition apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of another mobile terminal according to an embodiment of the present application.
Detailed Description
The technical scheme of the application is further explained by the specific implementation mode in combination with the attached drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently or simultaneously. In addition, the order of the steps may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Fig. 1 is a flowchart illustrating an information obtaining method according to an embodiment of the present application, where the method may be executed by an information obtaining apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in a mobile terminal. As shown in fig. 1, the method includes:
step 101, receiving a first character string and a second character string sent by a network side in a long term evolution voice-bearing call establishment process.
For example, the mobile terminal in the embodiment of the present application may include a mobile device such as a mobile phone and a tablet computer, which is capable of communicating based on an LTE network.
At present, many operators deploy an IMS network and provide a VoLTE function for a user, and in places without LTE network coverage, call continuity needs to be maintained by means of SRVCC. SRVCC is a Voice over LTE (Voice over Internet Protocol, VoIP) service continuity scheme proposed by the third Generation Partnership Project (3 GPP), and mainly aims to solve the problem of how to ensure Voice call continuity when a single radio frequency User Equipment (UE) moves between an LTE/Pre-LTE network and a 2G/3G Circuit Switched (CS) network, i.e., to ensure smooth handover of the single radio frequency UE between IMS-controlled Voice over IP (VoIP) and CS domain Voice. However, when SRVCC handover is performed, handover failure may occur. SRVCC generally includes many types, so as to implement corresponding SRVCC handover at different stages of VoLTE call, and the premise that successful handover can be implemented is that the network side and the mobile terminal need to have the SRVCC capability required by current handover at the same time, that is, support the SRVCC type corresponding to current handover. Illustratively, the SRVCC types can include aSRVCC, bSRVCC, eSRVCC, and mid-call SRVCC. Wherein, the SRVCC represents a ringing SRVCC, namely, alerting SRVCC, which occurs during ringing; bssrvcc represents SRVCC before ringing, i.e., before-alter SRVCC, and occurs before ringing; eSRVCC represents a call state SRVCC, namely Enhanced SRVCC, enhances SRVCC and occurs in the call process; mid-call SRVCC denotes SRVCC while a call is on hold, and occurs during a call involving three parties. The network side can carry out information interaction with the mobile terminal in the VoLTE call establishment process, and in the information interaction process, a message containing the SRVCC type supported by the network side can be sent to the mobile terminal side, the mobile terminal obtains the SRVCC type supported by the network side from the message, and then the SRVCC type supported by the network side and the network side are negotiated, so that the network side can initiate corresponding SRVCC switching when needed.
In this step, the mobile terminal receives a first character string and a second character string sent by a network side in the VoLTE call establishment process. The first string and the second string include network-side supported SRVCC types. The first string and the second string may be strings in a Session Initiation Protocol (SIP) message. For example, the first string and the second string may be simultaneously included in one message, such as a first message, and when the identities of the mobile terminals are different, the first message may be a different message. For example, the first message may be a different message when the mobile terminal is a calling identity and a called identity. Illustratively, when the mobile terminal is a calling identity, the first message includes a 183session progress message; when the mobile terminal is called, the first message comprises an Invite message.
Step 102, obtaining a first single channel voice call continuity (SRVCC) type information from the first character string, and obtaining a second SRVCC type information from the second character string.
The inventor finds that the reason for the SRVCC handover failure is not all that the network side and the mobile terminal do not have the SRVCC capability required for the current handover at the same time, and sometimes the mobile terminal does not acquire all the SRVCC types supported by the network side, and mistakenly thinks that the network side does not support a certain SRVCC type, so the SRVCC handover failure of the type is caused. In the related art, the mobile terminal only obtains the SRVCC types supported by the network side from a fixed string, but the inventor finds that sometimes the string does not carry all the SRVCC types supported by the network side, which further causes the information obtained by the mobile terminal to be wrong. In the related art, the fixed character string is a character string corresponding to a Feature-header (Feature-Caps) header field, that is, the default of the mobile terminal only determines which types of SRVCC handover are specifically supported by the network side according to the default carrying capability of the Feature-Caps header field, and when a certain SRVCC type does not exist in the Feature-Caps header field, the mobile terminal also informs the network side that the SRVCC type is not supported by the network side, so that the network side does not perform the handover of the SRVCC type, resulting in a handover failure, and even if the handover is successful, the network side also issues a disconnect (disconnect) message to suspend the call after the handover.
The inventor finds that, in a message sent by a network side to a mobile terminal, other character strings, such as a character string corresponding to a connection (Contact) header field, may also carry information related to an SRVCC type supported by the network side, and the information may be different from information carried in a character string used for acquiring the SRVCC type supported by the network side as default in the related art.
Step 103, determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information.
Wherein the third SRVCC type information includes all SRVCC types supported by the network side.
For example, it may be determined whether the first SRVCC type information and the second SRVCC type information are the same, and if so, it is determined that the third SRVCC type information is the same as the first SRVCC type information, that is, the SRVCC types included in the first SRVCC type information are all SRVCC types supported by the network side; and if not, adding the SRVCC type which is not in the first SRVCC type information in the second SRVCC type information on the basis of the first SRVCC type information to obtain a third SRVCC type. Therefore, the mobile terminal can more comprehensively determine all the SRVCC types supported by the network side, lay a foundation for the success of the subsequent various types of SRVCC switching, and avoid the occurrence of the situation that the network side actually has the corresponding SRVCC switching capability but fails to switch successfully.
In the information obtaining method provided in the embodiment of the application, in the VoLTE call establishment process, a first character string and a second character string sent by a network side are received, first SRVCC type information and second SRVCC type information are respectively obtained from the first character string and the second character string, and an SRVCC type supported by the network side is determined according to the first SRVCC type information and the second SRVCC type information. By adopting the technical scheme, the SRVCC type supported by the network side can be comprehensively obtained, and the failure of subsequent SRVCC switching caused by incomplete type obtaining is avoided.
In some embodiments, the first string comprises a string corresponding to a Feature header Feature-Caps header field, and the second string comprises a string corresponding to a connection Contact header field. The advantage of this arrangement is that the SRVCC type information supported by the network side can be comprehensively obtained from the character string sent from the existing network side to the mobile terminal without changing the network side.
In some embodiments, the first string and the second string are included in a first message sent by a network side. When the mobile terminal is a calling identity, the first message comprises a 183session progress message; when the mobile terminal is called, the first message comprises an Invite message. The method has the advantages that the method is compatible with the existing calling and called interaction processes without changing the network side.
In some embodiments, the determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information includes: and acquiring a union of the first SRVCC type information and the second SRVCC type information, and taking the union as third SRVCC type information. This has the advantage that the third SRVCC type information can be determined more quickly and accurately.
In some embodiments, after determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, the method further includes: and determining target SRVCC type information according to the third SRVCC type information and the fourth SRVCC type information, and acquiring the target SRVCC type information to a network side, wherein the target SRVCC type information is used for indicating the network side to perform SRVCC switching according to the target SRVCC type information, and the fourth SRVCC type information contains SRVCC types supported by the mobile terminal. The method has the advantages that the SRVCC switching capability which is simultaneously possessed by the mobile terminal and the network side can be timely fed back to the network side, when the SRVCC switching is needed, the network side can determine whether the SRVCC switching corresponding to the current conversation stage can be carried out according to the target SRVCC type information, and then the SRVCC switching is initiated, the switching success is ensured, and the continuity of the VoLTE is maintained.
In some embodiments, determining the target SRVCC type information according to the third SRVCC type information and the fourth SRVCC type information includes: and acquiring the intersection of the third SRVCC type information and the fourth SRVCC type information, and taking the intersection as target SRVCC type information. The advantage of such an arrangement is that the SRVCC types supported by both the mobile terminal and the network side can be determined quickly and accurately.
Fig. 2 is a schematic flow chart of another information acquisition method provided in the embodiment of the present application, where the method includes the following steps:
step 201, detecting a VoLTE call event.
Step 202, judging the identity of a calling party and a called party, and if the identity is the identity of the calling party, executing step 203; if the identity is called, step 205 is executed.
Step 203, receiving a first message sent by the network side.
Wherein, the first message is a 183session progress message.
Step 204, obtaining the first SRVCC type information from the character string corresponding to the Feature-Caps header field in the first message, obtaining the second SRVCC type information from the character string corresponding to the Contact header field in the first message, and executing step 207.
For example, the following character string "Feature-Caps" may exist in the 183session progress message: a first step of; + g.3gpp.srvcc; + g.3gpp.mid-call; + g.3gpp.srvcc-alerting; + g.3gpp.ps2cs-SRVCC-orig-pre-alerting ", from which SRVCC type information including mid-call SRVCC, aSRVCC, and bsrvvcc can be obtained.
Illustratively, SRVCC type information also exists in a character string corresponding to a Contact header field in the 183session progress message, and the expression form of the character string is similar to Feature-Caps. It is assumed that the SRVCC type information obtained therefrom includes aSRVCC and eSRVCC.
And step 205, receiving a second message sent by the network side.
Wherein the second message is an Invite message.
Step 206, obtaining the first SRVCC type information from the character string corresponding to the Feature-Caps header field in the second message, obtaining the second SRVCC type information from the character string corresponding to the Contact header field in the second message, and executing step 207.
Step 207, judging whether the first SRVCC type information is consistent with the second SRVCC type information, if yes, executing step 208; otherwise, step 209 is performed.
And step 208, determining that the third SRVCC type information is the same as the first SRVCC type information.
Illustratively, the total SRVCC capability supported by the update network side is the SRVCC capability carried by the Feature-Caps header field.
And step 209, acquiring a union of the first SRVCC type information and the second SRVCC type information, and taking the union as third SRVCC type information.
Illustratively, the total SRVCC capability supported by the update network side is the union of the SRVCC capabilities carried by the Feature-Caps header field and the Contact header field.
Illustratively, as described above, if the first SRVCC type information includes mid-call SRVCC, aSRVCC, and bsrvvcc, and the second SRVCC type information includes aSRVCC and eSRVCC, the union set is taken, and the obtained third SRVCC type information includes mid-call SRVCC, aSRVCC, bSRVCC, and eSRVCC.
According to the information acquisition method provided by the embodiment of the application, after a VoLTE call event is detected, the mobile terminal receives a message sent by a network side according to the own calling and called identities, acquires the SRVCC type information from the Feature-Caps header field and the Contact header field in the message respectively, comprehensively determines all SRVCC types supported by the network side according to the union set of the acquired SRVCC type information, can comprehensively acquire the SRVCC types supported by the network side, and avoids subsequent SRVCC switching failure caused by incomplete type acquisition.
Fig. 3 is a schematic flowchart of another information obtaining method provided in an embodiment of the present application, and as shown in fig. 3, the method includes:
step 301, detecting a VoLTE call event.
Step 302, receiving a corresponding first message sent by the network side according to the own calling and called identities.
If the identity is the calling identity, the first message is a 183session progress message, and if the identity is the called identity, the second message is an Invite message.
Step 303, obtaining the first SRVCC type information from the character string corresponding to the Feature-Caps header field in the first message.
And step 304, acquiring second SRVCC type information from the character string corresponding to the Contact header field in the first message.
And 305, acquiring a union of the first SRVCC type information and the second SRVCC type information, and taking the union as third SRVCC type information.
Step 306, determining the target SRVCC type information according to the third SRVCC type information and the fourth SRVCC type information, wherein the fourth SRVCC type information includes the SRVCC type supported by the mobile terminal itself.
And 307, acquiring the target SRVCC type information to the network side, wherein the target SRVCC type information is used for indicating the network side to perform SRVCC switching according to the target SRVCC type information.
Illustratively, a network side detects whether SRVCC handover is currently required or not in a VoLTE call setup process and a call process, when a handover condition is satisfied, a current call stage needs to be determined, such as before ringing, during calling or call holding, and then a required SRVCC handover type (e.g., bsrvvcc before ringing, aSRVCC during ringing, rvescc during calling, mid-call SRVCC during call holding) is determined according to the current call stage, whether the SRVCC handover type is included in target SRVCC type information is determined, and if the SRVCC handover type is included, a handover procedure is initiated to maintain call continuity. In the related art, the SRVCC types supported by the network side are determined only according to the SRVCC types carried in the Feature-Caps header domain, and some SRVCC types may not exist in the Feature-Caps header domain, which may cause the information acquired by the mobile terminal to be incorrect, and the SRVCC types commonly supported by the two that are fed back to the network side are also inconsistent with the actual situation, thereby missing some SRVCC types that can originally implement handover. In the embodiment of the application, the mobile terminal can more comprehensively acquire the SRVCC types supported by the network side, so that the target SRVCC types are consistent with the actual situation, and the failure of switching of certain or some SRVCC types caused by the error of the information acquired by the mobile terminal is avoided.
The information obtaining method provided by the embodiment of the application, after detecting a voice over long term evolution (VoLTE) call event, a mobile terminal receives a message sent by a network side according to a calling identity and a called identity of the mobile terminal, respectively obtains SRVCC type information from a Feature-Caps header field and a Contact header field in the message, comprehensively determines all SRVCC types supported by the network side according to a union set of the obtained SRVCC type information, can comprehensively obtain the SRVCC types supported by the network side, determines the SRVCC types supported by the network side and the SRVCC types supported by the mobile terminal according to the SRVCC types supported by the network side and the SRVCC types supported by the mobile terminal, feeds back the commonly supported type information to the network side, so that when the network side needs to perform SRVCC handover, determines whether the SRVCC handover corresponding to a current call stage can be performed according to the commonly supported types, further initiates the SRVCC handover, ensures the handover success, maintains the continuity of the VoLTE, and can solve the problem that the SRVCC type supported by the network side in Feature-Caps carries the SRVCC type The problem of handover drop.
Fig. 4 is a block diagram of an information obtaining apparatus, which may be implemented by software and/or hardware, and is generally integrated in a mobile terminal, and may perform information obtaining by executing an information obtaining method according to an embodiment of the present disclosure. As shown in fig. 4, the apparatus includes:
a character string receiving module 401, configured to receive a first character string and a second character string sent by a network side in a long term evolution voice bearer call establishment process;
an information obtaining module 402, configured to obtain first single-channel voice call continuity, SRVCC, type information from a first string in the first message, and obtain second SRVCC type information from a second string in the first message;
an information determining module 403, configured to determine third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, where the third SRVCC type information includes all SRVCC types supported by a network.
In the information obtaining apparatus provided in the embodiment of the application, in a VoLTE call setup process, a first character string and a second character string sent by a network side are received, first SRVCC type information and second SRVCC type information are respectively obtained from the first character string and the second character string, and an SRVCC type supported by the network side is determined according to the first SRVCC type information and the second SRVCC type information. By adopting the technical scheme, the SRVCC type supported by the network side can be comprehensively obtained, and the failure of subsequent SRVCC switching caused by incomplete type obtaining is avoided.
Optionally, the first character string includes a character string corresponding to a Feature header Feature-Caps header field, and the second character string includes a character string corresponding to a connection Contact header field.
Optionally, the first character string and the second character string are included in a first message sent by a network side;
when the mobile terminal is a calling identity, the first message comprises a 183session progress message;
when the mobile terminal is called, the first message comprises an Invite message.
Optionally, the determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information includes:
and acquiring a union of the first SRVCC type information and the second SRVCC type information, and taking the union as third SRVCC type information.
Optionally, the apparatus further comprises:
a target information determining module, configured to determine, after determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, target SRVCC type information according to the third SRVCC type information and the fourth SRVCC type information, where the third SRVCC type information includes an SRVCC type supported by a mobile terminal itself;
and the information feedback module is used for acquiring the target SRVCC type information to a network side, and the target SRVCC type information is used for indicating the network side to carry out SRVCC switching according to the target SRVCC type information.
Optionally, determining the target SRVCC type information according to the third SRVCC type information and the fourth SRVCC type information includes:
and acquiring the intersection of the third SRVCC type information and the fourth SRVCC type information, and taking the intersection as target SRVCC type information.
Optionally, the SRVCC types include aSRVCC, bsrvvcc, eSRVCC, or mid-call SRVCC.
Embodiments of the present application also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, perform an information acquisition method, the method including:
receiving a first character string and a second character string sent by a network side in the process of establishing a long-term evolution voice bearing call;
obtaining first single-channel voice call continuity (SRVCC) type information from the first character string, and obtaining second SRVCC type information from the second character string;
and determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, wherein the third SRVCC type information comprises all SRVCC types supported by a network side.
Storage medium-any of various types of memory devices or storage devices. The term "storage medium" is intended to include: mounting media such as CD-ROM, floppy disk, or tape devices; computer system memory or random access memory such as DRAM, DDRRAM, SRAM, EDORAM, Lanbas (Rambus) RAM, etc.; non-volatile memory such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in a first computer system in which the program is executed, or may be located in a different second computer system connected to the first computer system through a network (such as the internet). The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations, such as in different computer systems that are connected by a network. The storage medium may store program instructions (e.g., embodied as a computer program) that are executable by one or more processors.
Of course, the storage medium provided in the embodiments of the present application and containing computer-executable instructions is not limited to the information obtaining operation described above, and may also perform related operations in the information obtaining method provided in any embodiment of the present application.
The embodiment of the application provides a mobile terminal, and the information acquisition device provided by the embodiment of the application can be integrated in the mobile terminal. Fig. 5 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application. The mobile terminal 500 may include: the information acquisition system comprises a memory 501, a processor 502 and a computer program stored on the memory 501 and capable of being executed by the processor 502, wherein the processor 502 executes the computer program to realize the information acquisition method according to the embodiment of the application.
The mobile terminal provided by the embodiment of the application can comprehensively acquire the SRVCC type supported by the network side, and avoids subsequent SRVCC switching failure caused by incomplete type acquisition.
Fig. 6 is a schematic structural diagram of another mobile terminal provided in an embodiment of the present application, where the mobile terminal may include: a housing (not shown), a memory 601, a Central Processing Unit (CPU) 602 (also called a processor, hereinafter referred to as CPU), a circuit board (not shown), and a power circuit (not shown). The circuit board is arranged in a space enclosed by the shell; the CPU602 and the memory 601 are disposed on the circuit board; the power supply circuit is used for supplying power to each circuit or device of the mobile terminal; the memory 601 is used for storing executable program codes; the CPU602 executes a computer program corresponding to the executable program code by reading the executable program code stored in the memory 601 to implement the steps of:
receiving a first character string and a second character string sent by a network side in the process of establishing a long-term evolution voice bearing call;
obtaining first single-channel voice call continuity (SRVCC) type information from the first character string, and obtaining second SRVCC type information from the second character string;
and determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, wherein the third SRVCC type information comprises all SRVCC types supported by a network side.
The mobile terminal further includes: peripheral interface 603, RF (Radio Frequency) circuitry 605, audio circuitry 606, speakers 611, power management chip 608, input/output (I/O) subsystem 609, other input/control devices 610, touch screen 612, other input/control devices 610, and external port 604, which communicate via one or more communication buses or signal lines 607.
It should be understood that the illustrated mobile terminal 600 is merely one example of a mobile terminal and that the mobile terminal 600 may have more or fewer components than shown, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
The following describes in detail the mobile terminal for information acquisition provided in this embodiment, and the mobile terminal is taken as an example of a mobile phone.
A memory 601, the memory 601 being accessible by the CPU602, the peripheral interface 603, and the like, the memory 601 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other volatile solid state storage devices.
A peripheral interface 603, said peripheral interface 603 may connect input and output peripherals of the device to the CPU602 and the memory 601.
An I/O subsystem 609, the I/O subsystem 609 may connect input and output peripherals on the device, such as a touch screen 612 and other input/control devices 610, to the peripheral interface 603. The I/O subsystem 609 may include a display controller 6091 and one or more input controllers 6092 for controlling other input/control devices 610. Where one or more input controllers 6092 receive electrical signals from or transmit electrical signals to other input/control devices 610, the other input/control devices 610 may include physical buttons (push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels. It is noted that the input controller 6092 may be connected to any one of: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.
A touch screen 612, which touch screen 612 is an input interface and an output interface between the user's mobile terminal and the user, displays visual output to the user, which may include graphics, text, icons, video, and the like.
The display controller 6091 in the I/O subsystem 609 receives electrical signals from the touch screen 612 or transmits electrical signals to the touch screen 612. The touch screen 612 detects a contact on the touch screen, and the display controller 6091 converts the detected contact into an interaction with a user interface object displayed on the touch screen 612, that is, to implement a human-computer interaction, where the user interface object displayed on the touch screen 612 may be an icon for running a game, an icon networked to a corresponding network, or the like. It is worth mentioning that the device may also comprise a light mouse, which is a touch sensitive surface that does not show visual output, or an extension of the touch sensitive surface formed by the touch screen.
The RF circuit 605 is mainly used to establish communication between the mobile phone and the wireless network (i.e., network side), and implement data reception and transmission between the mobile phone and the wireless network. Such as sending and receiving short messages, e-mails, etc. In particular, RF circuitry 605 receives and transmits RF signals, also referred to as electromagnetic signals, through which RF circuitry 605 converts electrical signals to or from electromagnetic signals and communicates with a communication network and other devices. RF circuitry 605 may include known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC (CODEC) chipset, a Subscriber Identity Module (SIM), and so forth.
The audio circuit 606 is mainly used to receive audio data from the peripheral interface 603, convert the audio data into an electric signal, and transmit the electric signal to the speaker 611.
The speaker 611 is used to convert the voice signal received by the handset from the wireless network through the RF circuit 605 into sound and play the sound to the user.
And a power management chip 608 for supplying power and managing power to the hardware connected to the CPU602, the I/O subsystem, and the peripheral interface.
The information acquisition device, the storage medium and the mobile terminal provided in the above embodiments may execute the information acquisition method provided in any embodiment of the present application, and have corresponding functional modules and beneficial effects for executing the method. For technical details that are not described in detail in the above embodiments, reference may be made to the information acquisition method provided in any embodiments of the present application.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims (10)

1. An information acquisition method, comprising:
receiving a first character string and a second character string sent by a network side in the process of establishing a long-term evolution voice bearing call;
obtaining first single-channel voice call continuity (SRVCC) type information from the first character string, and obtaining second SRVCC type information from the second character string;
and determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, wherein the third SRVCC type information comprises all SRVCC types supported by a network side.
2. The method of claim 1, wherein the first string comprises a string corresponding to a Feature header Feature-Caps header field, and wherein the second string comprises a string corresponding to a connection Contact header field.
3. The method according to claim 1, wherein the first string and the second string are included in a first message sent by a network side;
when the mobile terminal is the calling identity, the first message comprises a 183session progress message;
when the mobile terminal is called, the first message comprises an Invite message.
4. The method according to any of claims 1-3, wherein said determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information comprises:
and acquiring a union of the first SRVCC type information and the second SRVCC type information, and taking the union as third SRVCC type information.
5. The method of claim 1, wherein after determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, further comprising:
determining target SRVCC type information according to the third SRVCC type information and fourth SRVCC type information, wherein the fourth SRVCC type information contains SRVCC types supported by the mobile terminal;
and acquiring the target SRVCC type information to a network side, wherein the target SRVCC type information is used for indicating the network side to carry out SRVCC switching according to the target SRVCC type information.
6. The method of claim 5, wherein determining target SRVCC type information based on third SRVCC type information and the fourth SRVCC type information comprises:
and acquiring the intersection of the third SRVCC type information and the fourth SRVCC type information, and taking the intersection as target SRVCC type information.
7. The method of claim 1, wherein the SRVCC type comprises aSRVCC, bsrvvcc, eSRVCC, or mid-call SRVCC.
8. An information acquisition apparatus characterized by comprising:
the character string receiving module is used for receiving a first character string and a second character string sent by a network side in the process of establishing the long-term evolution voice bearing conversation;
an information obtaining module, configured to obtain first single channel voice call continuity, SRVCC, type information from a first character string in a first message, and obtain second SRVCC type information from a second character string in the first message;
and the information determining module is used for determining third SRVCC type information according to the first SRVCC type information and the second SRVCC type information, wherein the third SRVCC type information comprises all SRVCC types supported by a network side.
9. A computer-readable storage medium on which a computer program is stored, the program, when being executed by a processor, implementing the information acquisition method according to any one of claims 1 to 7.
10. A mobile terminal, characterized in that it comprises a memory, a processor and a computer program stored on the memory and executable on the processor, said processor implementing the information acquisition method according to any one of claims 1 to 7 when executing said computer program.
CN201910024368.4A 2019-01-10 2019-01-10 Information acquisition method and device, storage medium and mobile terminal Active CN109548181B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910024368.4A CN109548181B (en) 2019-01-10 2019-01-10 Information acquisition method and device, storage medium and mobile terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910024368.4A CN109548181B (en) 2019-01-10 2019-01-10 Information acquisition method and device, storage medium and mobile terminal

Publications (2)

Publication Number Publication Date
CN109548181A CN109548181A (en) 2019-03-29
CN109548181B true CN109548181B (en) 2020-11-10

Family

ID=65834698

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910024368.4A Active CN109548181B (en) 2019-01-10 2019-01-10 Information acquisition method and device, storage medium and mobile terminal

Country Status (1)

Country Link
CN (1) CN109548181B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104427560A (en) * 2013-08-28 2015-03-18 中兴通讯股份有限公司 Single radio voice call continuity switching configuration method, switching method and device
CN106888486A (en) * 2015-12-16 2017-06-23 中兴通讯股份有限公司 Double-mode single-standby wireless voice call continuity method and device before ring
WO2018208304A1 (en) * 2017-05-11 2018-11-15 Intel IP Corporation Bandwidth utilization during silence frames

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103168494B (en) * 2011-09-09 2017-04-26 华为技术有限公司 Method and device for srvcc handover
US20160150446A1 (en) * 2014-11-20 2016-05-26 Nokia Solutions And Networks Oy Method and apparatus for supporting enhanced single-radio-voice-call-continuity

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104427560A (en) * 2013-08-28 2015-03-18 中兴通讯股份有限公司 Single radio voice call continuity switching configuration method, switching method and device
CN106888486A (en) * 2015-12-16 2017-06-23 中兴通讯股份有限公司 Double-mode single-standby wireless voice call continuity method and device before ring
WO2018208304A1 (en) * 2017-05-11 2018-11-15 Intel IP Corporation Bandwidth utilization during silence frames

Also Published As

Publication number Publication date
CN109548181A (en) 2019-03-29

Similar Documents

Publication Publication Date Title
US11843721B2 (en) Method and terminal for supporting voice service and data service simultaneously
CN109548075B (en) Measurement report reporting method, device, storage medium and mobile terminal
US20240022969A1 (en) Co-existence mechanism for downloadable voice application client
CN103843398A (en) Method and apparatuses for selecting voice over lte or cs fallback for voice sessions
CA2784651C (en) Apparatus and method in a wireless device for reestablishing a call
CN113365234B (en) Calling method and device and electronic equipment
CN110996344A (en) System and method for enhanced call quality and success rate
CN108200618B (en) Cell switching control method, device, storage medium and mobile terminal
WO2024066150A1 (en) Network fallback method and device and storage medium
US20230139150A1 (en) Method and apparatus for processing call initiation anomaly
US20090264113A1 (en) Mobile phone that automatically makes conference calls and method for same
CN113163058A (en) Session parameter updating method and device, communication equipment and electronic equipment
CN109548181B (en) Information acquisition method and device, storage medium and mobile terminal
US20220322158A1 (en) Call network switching method and device, and memory
US11575716B2 (en) Apparatuses and methods for providing reliable delivery of application data
US20230199876A1 (en) Direct connection call method, core network device, and non-transitory storage medium
CN108243398B (en) Method and device for processing call conflict
CN116170415B (en) Call processing method, device and storage medium
CN106714254B (en) Switching method of audio and video service application network, terminal and application server
WO2023221855A1 (en) Data channel application list processing method, apparatus, and device
WO2024078493A1 (en) Paging method and apparatus, and electronic device and storage medium
WO2024051627A1 (en) Communication establishment method and apparatus, terminal device, and network side device
US20220369197A1 (en) Enhanced call control using user equipment (ue)-triggered fallback procedure
US20210185170A1 (en) Media display control method and related product
CN117082034A (en) Voice call method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant