Method, device, chip system and storage medium for calling

Abstract

The present application provides a method, device, chip system and storage medium for a call. The method is applied to a terminal device, by verifying the first information in the first RRC reconfiguration message currently received from the first cell and the first parameter in the first configuration item stored locally and the value corresponding to the first parameter, and when the value corresponding to the first parameter is abnormal, ignoring the abnormal value corresponding to the first parameter, so that the first RRC reconfiguration message is successfully verified, thereby ensuring that the terminal device can complete the RRC reconfiguration and reducing the probability of RRC reconfiguration failure.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device, chip system and storage medium for making calls. Background Art

[0002] In the 5G, i.e. NR (New Radio) network, the RRC reconfiguration (Radio Resource Control Reconfiguration) initiated by the network side (referring to the 5G base station, such as gNB (gNodeB, the next Generation Node B)) to the terminal device (also referred to as: UE) is intended to modify the RRC connection that has been established between the UE and the network side to better adapt to actual business scenarios.

[0003] However, there is currently a situation where the UE fails to verify the RRC reconfiguration message, which leads to call interruption. Summary of the invention

[0004] In order to solve the above technical problems, the present application provides a method, device, chip system and storage medium for calls, aiming to reduce call failures and improve user experience.

[0005] In the first aspect, the present application provides a method for making a call. The method is applied to a terminal device, comprising: during a call in a first cell, receiving a first RRC reconfiguration message sent by a base station corresponding to the first cell; wherein, before receiving the first RRC reconfiguration message, a first configuration item is stored in the terminal device; the first configuration item includes a first parameter and a first value corresponding to the first parameter; verifying the first RRC reconfiguration message and the first configuration item; wherein the first RRC reconfiguration message includes first information; verifying the first RRC reconfiguration message and the first configuration item includes verifying the first information, the first parameter, and the first value corresponding to the first parameter; in the process of verifying the first RRC reconfiguration message and the first configuration item, when there is an abnormality in the value corresponding to the first parameter, ignoring the abnormal value corresponding to the first parameter, so that the first RRC reconfiguration message is successfully verified; wherein the value corresponding to the first parameter includes the first value.

[0006] The first cell is a cell where the terminal equipment (UE) currently resides, for example, it may be Cell A, Cell B, or Cell C mentioned below. Specifically in this application, the first cell is taken as Cell B as an example below.

[0007] The RRC reconfiguration message is the RRCReconfiguration message sent to the UE by the base station corresponding to the cell as mentioned below. Specifically in the present application, in the scenario where the first cell is Cell B as an example, the first RRC reconfiguration message mentioned here is, for example, the RRC reconfiguration message 3 or the RRC reconfiguration message 4 mentioned below.

[0008] Among them, the first configuration item is a configuration item locally saved by the terminal device, which may include the first parameter mentioned above, and the value corresponding to the first parameter. In this embodiment, the value corresponding to the first parameter saved in the terminal device is taken as the first value. However, in actual applications, the value corresponding to the first parameter is not limited to the first value, and may also be the second value, the third value, etc. mentioned below.

[0009] The terminal device verifies the first message, the first parameter, and the first value corresponding to the first parameter, which may specifically refer to verifying whether the first message and the first parameter, as well as the first value corresponding to the first parameter, match or are compatible.

[0010] Therefore, when there is an abnormality in the value corresponding to the first parameter, the abnormal value corresponding to the first parameter is ignored, so that the first RRC reconfiguration message is successfully verified, thereby ensuring that the terminal device can complete the RRC reconfiguration and reducing the probability of RRC reconfiguration failure.

[0011] The ignoring of the abnormal value corresponding to the first parameter may be to not consider the abnormal value corresponding to the first parameter (which can be understood as ignoring the verification abnormality caused by the abnormal value corresponding to the first parameter when determining the verification result of the first RRC reconfiguration message), or may be to update the value corresponding to the first parameter so that the abnormal value corresponding to the first parameter is corrected or deleted or ineffective. Furthermore, when determining the verification result of the first RRC reconfiguration message, the abnormal value corresponding to the first parameter will not cause the first RRC reconfiguration message verification to fail and thus cause call abnormality.

[0012] Exemplarily, ignoring the abnormal value corresponding to the first parameter refers to an implementation method of updating the value corresponding to the first parameter. Specifically, the value corresponding to the first parameter may be updated according to method 1 or method 2 described in the following embodiments.

[0013] Exemplarily, in some implementations, the operation of updating the value corresponding to the first parameter, or the value corresponding to the parameter with an abnormal parameter value, can be uniformly represented as updating the configuration item where the parameter is located, that is, updating the configuration item. Hereinafter, the representation of updating the configuration item is taken as an example for explanation.

[0014] It should be noted that in actual applications, the update of these configuration items according to method 1 or method 2 can be understood as updating the configuration of these configuration items, or can be understood as updating the values ​​of these configuration items, or can be understood as updating the content of these configuration items. This application takes updating the values ​​corresponding to the abnormal parameters in these configuration items as an example for explanation.

[0015] According to the first aspect, after the first RRC reconfiguration message is successfully verified, the method further includes: performing RRC reconfiguration according to the first RRC reconfiguration message, and after completing the RRC reconfiguration, feeding back an RRC reconfiguration completion message.

[0016] The RRC reconfiguration completion message, for example, the RRC Reconfiguration Complete mentioned below.

[0017] According to the first aspect, or any implementation of the first aspect above, ignoring the abnormal value corresponding to the first parameter includes: updating the value corresponding to the first parameter.

[0018] According to the first aspect, or any implementation method of the first aspect above, the value corresponding to the first parameter also includes a second value; the first RRC reconfiguration message carries a second configuration item about the first cell, and the second configuration item includes the first parameter and the second value corresponding to the first parameter; when there is an abnormality in the value corresponding to the first parameter, the abnormal value corresponding to the first parameter is ignored, including: when the first value and the second value are different, the abnormal value corresponding to the first parameter is ignored.

[0019] According to the first aspect, or any implementation of the first aspect above, ignoring the abnormal value corresponding to the first parameter includes: updating the first value corresponding to the first parameter to a second value.

[0020] That is, when the value corresponding to the same parameter currently received from the network side is different from the value corresponding to the parameter already stored locally in the terminal device, the method 2 described below can be used to update the configuration item. Specifically, the value corresponding to the parameter with an abnormality in the configuration item is updated to the value corresponding to the parameter currently received from the network side (see S409a in the following embodiment). In this way, by updating the value corresponding to the parameter with an abnormality in the configuration item, the first RRC reconfiguration message is successfully verified, and the terminal device can continue to reside in the first cell and make calls normally.

[0021] According to the first aspect, or any implementation method of the first aspect above, the first information includes information of the second cell, and the first RRC reconfiguration message is used to instruct the terminal device to switch from the first cell to the second cell; when there is an abnormality in the value corresponding to the first parameter, the abnormal value corresponding to the first parameter is ignored, including: when the value corresponding to the first parameter is incompatible with the information of the second cell, the abnormal value corresponding to the first parameter is ignored.

[0022] According to the first aspect, or any implementation of the first aspect above, ignoring the abnormal value corresponding to the first parameter includes: updating the value corresponding to the first parameter from the first value to a third value.

[0023] That is, for the case where the first RRC reconfiguration message indicates that the terminal device switches from the first cell to the second cell, the first information usually includes relevant information of the second cell, such as whether the second cell currently supports the first parameter and the first value corresponding to the first parameter. Therefore, when the first information does not match or is incompatible with the first parameter and the first value corresponding to the first parameter, it can be determined that the value corresponding to the first parameter is incompatible with the information of the second cell. In this case, the configuration item can be updated using method 1 described below. Specifically, the value corresponding to the abnormal parameter in the configuration item is updated to a value indicating that the parameter is not effective, such as the third value mentioned above. In this way, by updating the value corresponding to the abnormal parameter in the configuration item to a value indicating that it is not effective, the first RRC reconfiguration message is successfully verified, and the terminal device can reside in the second cell to achieve normal calls in the second cell.

[0024] According to the first aspect, or any implementation manner of the first aspect, the first cell is a cell of a TDD system, and the second cell is a cell of an FDD system.

[0025] For example, the first cell is Cell B of the TDD system mentioned below, and the second cell is Cell C of the FDD system.

[0026] According to the first aspect, or any implementation manner of the first aspect above, the first configuration item is a configuration item of an SRS resource of an antenna switching mode.

[0027] Exemplarily, when the first configuration item is a configuration item of an SRS resource of an antenna switching mode, the first parameter is, for example, srs_tx_switch mentioned below, and the first value corresponding to the first parameter is, for example, "1".

[0028] According to the first aspect, or any implementation of the first aspect above, the first value is 1 and the third value is 0.

[0029] Exemplarily, when the first configuration item is a configuration item of an SRS resource of an antenna switching mode, the first parameter is, for example, srs_tx_switch mentioned below, the first value corresponding to the first parameter is, for example, "1", and the third value is, for example, "0". In this case, the update of the first configuration item is, for example, updating srs_tx_switch=1 to srs_tx_switch=0 as mentioned below.

[0030] According to the first aspect, or any implementation method of the first aspect above, ignoring the abnormal value corresponding to the first parameter includes: when the first parameter is an ignorable parameter, ignoring the abnormal value corresponding to the first parameter; wherein the first parameter is an ignorable parameter, including: the first parameter is the same as any parameter in a parameter list saved in the terminal device, the parameter list includes at least one parameter, and the parameter value corresponding to each of the at least one parameter can be ignored.

[0031] The parameter list stored in the terminal device and the configuration item list mentioned below refer to the same list. In the following embodiments, the updateable configuration items recorded in the configuration item list are the negligible parameters mentioned here.

[0032] According to the first aspect, or any implementation of the first aspect above, the ignorable parameters in the parameter list are determined according to an existing standard protocol and pre-stored in the terminal device. In this way, the ignorable parameters corresponding to each cell are determined according to the existing standard protocol, so that the terminal device can perform RRC reconfiguration between various cells.

[0033] According to the first aspect, or any implementation method of the first aspect above, when the first parameter is a ignorable parameter, the abnormal value corresponding to the first parameter is ignored, including: when the first parameter is a ignorable parameter and the terminal device supports a compatible function, the abnormal value corresponding to the first parameter is ignored; wherein, the terminal device supports the compatible function, indicating that the terminal device supports ignoring the abnormal value corresponding to the ignorable parameter.

[0034] Among them, the terminal device supports the compatible function, for example, the UE mentioned below has enabled the compatible function. For determining whether the terminal device supports the compatible function, please refer to the description of S313 or S405 below, which will not be repeated here. S313 or S405 may be an optional step, in which case the terminal device may support the compatible function by default.

[0035] According to the first aspect, or any implementation of the first aspect above, the method also includes: when the first parameter is a negligible parameter and the terminal device does not support the compatible function, replying an RRC connection re-establishment message to the base station corresponding to the first cell.

[0036] The RRC connection re-establishment message, for example, is referred to as RRC Connection re-establishment below.

[0037] Among them, the terminal device does not support the compatibility function, for example, the compatibility function is not enabled as mentioned below.

[0038] Regarding the terminal device replying to the RRC connection re-establishment message to the first cell and triggering the RRC connection re-establishment process, please refer to the following part where the UE executes the RLF process and reselects the cell to reside, such as selecting the original cell or the new cell to reside, such as S113 to S115, or S213 to S220, or S314 to S316, etc.

[0039] According to the first aspect, or any implementation of the first aspect above, it is characterized in that the first configuration item is a configuration received by the cell where the terminal device resides before residing in the first cell.

[0040] Illustratively, when the first cell is Cell B mentioned below, the cell where the terminal device resides before the first cell may be Cell A mentioned below, for example.

[0041] Correspondingly, when the cell that resides before the first cell is Cell A, the first configuration item is, for example, the configuration carried in the RRC reconfiguration message sent by the base station corresponding to Cell A to the terminal device, for example, through the RRC reconfiguration message 1 or RRC reconfiguration message 2 mentioned below.

[0042] According to the first aspect, or any implementation of the first aspect above, when the first information is information for the first cell, performing RRC reconfiguration according to the first RRC reconfiguration message, and after completing the RRC reconfiguration, feeding back an RRC reconfiguration completion message, includes: performing RRC reconfiguration according to the first RRC reconfiguration message, and after completing the RRC reconfiguration, feeding back an RRC reconfiguration completion message to the base station corresponding to the first cell. For details, please refer to S409a and S409b in the following embodiments.

[0043] According to the first aspect, or any implementation of the first aspect above, it is characterized in that when the first RRC reconfiguration message indicates that the terminal device switches from the first cell to the second cell, RRC reconfiguration is performed according to the first RRC reconfiguration message, and after the RRC reconfiguration is completed, an RRC reconfiguration completion message is fed back, including: performing RRC reconfiguration according to the first RRC reconfiguration message, and after completing the RRC reconfiguration, after residing in the second cell, replying an RRC reconfiguration completion message to the base station corresponding to the second cell. For details, please refer to S409c and S409d in the following embodiments.

[0044] The second cell is the cell to which the terminal equipment (UE) is to switch. Specifically in the present application, when the cells to which the UE can switch are Cell A, Cell B and Cell C, when the first cell is Cell B, the second cell can be Cell A or Cell C. In order to facilitate the description of the method for making a call provided by the present application, the second cell is taken as Cell C as an example below.

[0045] Specifically in the present application, in a scenario where the second cell is Cell C, the first RRC reconfiguration message mentioned here is, for example, the RRC reconfiguration message 4 mentioned below. For this scenario, the incompatible first configuration item is, for example, the SRS resource configuration item of the antenna switching mode configured in the RRC reconfiguration message 3 below.

[0046] In a second aspect, the present application provides a method for making a call. The method is applied to a terminal device, comprising: during a call in a first cell, receiving a first RRC reconfiguration message sent by a base station corresponding to the first cell; verifying the first RRC reconfiguration message; in the process of verifying the first RRC reconfiguration message, when there is a parameter with an abnormal parameter value, ignoring the abnormal parameter value corresponding to the parameter, so that the first RRC reconfiguration message is successfully verified.

[0047] The first cell is a cell where the terminal equipment (UE) currently resides, for example, it may be Cell A, Cell B, or Cell C mentioned below. Specifically in this application, the first cell is taken as Cell B as an example below.

[0048] The RRC reconfiguration message is the RRCReconfiguration message sent by the base station corresponding to the cell to the UE as mentioned below.

[0049] Among them, the verification of the first RRC reconfiguration message may, for example, include verification of the content in the first RRC reconfiguration message sent by the first cell, and verification of the parameters included in the configuration items locally stored in the terminal device and the parameter values ​​corresponding to the parameters.

[0050] Therefore, by ignoring the abnormal parameter values ​​corresponding to the parameters with abnormal parameter values ​​verified by the terminal device in the RRC reconfiguration process, the first RRC reconfiguration message can be verified successfully, thereby ensuring that the terminal device can complete the RRC reconfiguration and reducing the probability of RRC reconfiguration failure.

[0051] According to the second aspect, ignoring an abnormal parameter value corresponding to a parameter includes: updating the parameter value corresponding to the parameter.

[0052] According to the second aspect, or any implementation method of the second aspect above, ignoring the abnormal parameter value corresponding to the parameter includes: when the parameter with the abnormal parameter value is an ignorable parameter, ignoring the abnormal parameter value corresponding to the parameter; wherein the parameter with the abnormal parameter value is an ignorable parameter, including: the parameter with the abnormal parameter value is the same as any parameter in the parameter list saved in the terminal device, the parameter list includes at least one parameter, and the parameter value corresponding to the at least one parameter can be ignored.

[0053] The parameter list stored in the terminal device and the configuration item list mentioned below refer to the same list. In the following embodiments, the updateable configuration items recorded in the configuration item list are the negligible parameters mentioned here.

[0054] According to the second aspect, or any implementation of the second aspect above, the ignorable parameters in the parameter list are determined according to an existing standard protocol and pre-stored in the terminal device. In this way, the ignorable parameters corresponding to each cell are determined according to the existing standard protocol, so that the terminal device can perform RRC reconfiguration between various cells.

[0055] According to the second aspect, or any implementation method of the second aspect above, when the first parameter is a ignorable parameter, the abnormal parameter value corresponding to the parameter is ignored, including: when the parameter with an abnormal parameter value is a ignorable parameter and the terminal device supports a compatible function, the abnormal parameter value corresponding to the parameter is ignored; wherein, the terminal device supporting the compatible function indicates that the terminal device supports ignoring abnormal values ​​corresponding to ignorable parameters.

[0056] Among them, the terminal device supports the compatible function, for example, the UE mentioned below has enabled the compatible function. For determining whether the terminal device supports the compatible function, please refer to the description of S313 or S405 below, which will not be repeated here. S313 or S405 may be an optional step, in which case the terminal device may support the compatible function by default.

[0057] According to the second aspect, or any implementation of the second aspect above, the method also includes: when the parameter with the abnormal parameter value is a negligible parameter and the terminal device does not support the compatible function, replying an RRC connection re-establishment message to the base station corresponding to the first cell.

[0058] The RRC connection re-establishment message, for example, is referred to as RRC Connection re-establishment below.

[0059] Among them, the terminal device does not support the compatibility function, for example, the compatibility function is not enabled as mentioned below.

[0060] Regarding the terminal device replying to the RRC connection re-establishment message to the first cell and triggering the RRC connection re-establishment process, please refer to the following part where the UE executes the RLF process and reselects the cell to reside, such as selecting the original cell or the new cell to reside, such as S113 to S115, or S213 to S220, or S314 to S316, etc.

[0061] In a third aspect, the present application provides a terminal device. The terminal device includes: a memory and a processor, the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the terminal device executes instructions of the method in the first aspect or any possible implementation of the first aspect.

[0062] The third aspect and any implementation of the third aspect correspond to the first aspect and any implementation of the first aspect, respectively; or correspond to the second aspect and any implementation of the second aspect, respectively. The technical effects corresponding to the third aspect and any implementation of the third aspect can refer to the technical effects corresponding to the above-mentioned first aspect and any implementation of the first aspect, or the technical effects corresponding to the above-mentioned second aspect and any implementation of the second aspect, which will not be repeated here.

[0063] In a fourth aspect, the present application provides a computer-readable medium for storing a computer program, wherein the computer program includes instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0064] The fourth aspect and any implementation of the fourth aspect correspond to the first aspect and any implementation of the first aspect, respectively; or correspond to the second aspect and any implementation of the second aspect, respectively. The technical effects corresponding to the fourth aspect and any implementation of the fourth aspect can refer to the technical effects corresponding to the above-mentioned first aspect and any implementation of the first aspect, or the technical effects corresponding to the above-mentioned second aspect and any implementation of the second aspect, which will not be repeated here.

[0065] In a fifth aspect, the present application provides a computer program comprising instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0066] The fifth aspect and any implementation of the fifth aspect correspond to the first aspect and any implementation of the first aspect, respectively; or correspond to the second aspect and any implementation of the second aspect, respectively. The technical effects corresponding to the fifth aspect and any implementation of the fifth aspect can refer to the technical effects corresponding to the first aspect and any implementation of the first aspect, or the technical effects corresponding to the second aspect and any implementation of the second aspect, which will not be repeated here.

[0067] In a sixth aspect, the present application provides a chip system, the chip system comprising a processor. The processor is used to support a terminal device to implement instructions of the method in the above-mentioned first aspect or any possible implementation manner of the first aspect.

[0068] According to a sixth aspect, the processor includes a modem.

[0069] Accordingly, the processor is used to support the terminal device to implement the instructions of the method in the first aspect or any possible implementation manner of the first aspect, specifically including:

[0070] The modem is used to support the terminal device to implement instructions of the method in the above-mentioned first aspect or any possible implementation manner of the first aspect.

[0071] The sixth aspect and any implementation of the sixth aspect correspond to the first aspect and any implementation of the first aspect, respectively; or correspond to the second aspect and any implementation of the second aspect, respectively. The technical effects corresponding to the sixth aspect and any implementation of the sixth aspect can refer to the technical effects corresponding to the first aspect and any implementation of the first aspect, or the technical effects corresponding to the second aspect and any implementation of the second aspect, which will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1 A schematic diagram of a mobile communication architecture is shown as an example;

[0073] Figure 2a This is a schematic diagram of the interaction between the UE and the network side when the RRC reconfiguration is successful;

[0074] Figure 2b This is a schematic diagram of the interaction between the UE and the network side when RRC reconfiguration fails;

[0075] Figure 3 This is a schematic diagram showing an exemplary case of cell switching failure in an RRC reconfiguration process;

[0076] Figure 4This is a schematic diagram showing an exemplary cell switching failure in another RRC reconfiguration process;

[0077] Figure 5 A schematic diagram of implementing RRC reconfiguration based on a method for a call provided in an embodiment of the present application is exemplified;

[0078] Figure 6 A schematic diagram for exemplarily illustrating another method for call provided in an embodiment of the present application to implement RRC reconfiguration;

[0079] Figure 7 A schematic diagram of the software structure and hardware of a terminal device is shown as an example;

[0080] Figure 8 The figure is a schematic diagram of the hardware structure of a terminal device shown as an example. DETAILED DESCRIPTION

[0081] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0082] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0083] The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects rather than to describe a specific order of objects. For example, a first target object and a second target object are used to distinguish different target objects rather than to describe a specific order of target objects.

[0084] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0085] In the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" refers to two or more than two. For example, multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.

[0086] Based on the above premise, the technical solution provided in the embodiments of the present application is described below.

[0087] Specifically, the technical solution provided by the embodiment of the present application is the processing logic performed when performing the RRC reconfiguration process during the call between the calling party and the called party. In order to better illustrate the technical solution provided by the embodiment of the present application, the mobile communication architecture targeted by the method for calling provided by the embodiment of the present application is first described in conjunction with the accompanying drawings.

[0088] See also Figure 1 , exemplarily showing a mobile communication architecture. In the mobile communication architecture, terminal equipment, (wireless) access network, core network and IP Multimedia Subsystem (IMS) network required for implementing voice / audio and video call services are shown.

[0089] Continue to see Figure 1 , exemplarily, the terminal equipment may include a calling party (such as terminal A) that initiates a call service and a called party (such as terminal B) that responds to the call service; the access network may include a base station corresponding to terminal A (such as base station A) and a base station corresponding to terminal B (such as base station B); the core network may include an operator computer room corresponding to base station A (such as computer room A) and an operator computer room corresponding to base station B (such as computer room B); the IMS network may include a calling IMS domain (network) and a called IMS domain (network) corresponding to terminal A.

[0090] Exemplarily, in some implementations, base station A and base station B may be the same, for example, in a scenario where terminal A and terminal B are oriented to the same operator and terminal A and terminal B access the same cell.

[0091] For example, in other implementations, base station A and base station B may be two different base stations, for example, in a scenario where terminal A and terminal B are facing different operators. Alternatively, terminal A and terminal B are facing the same operator, but terminal A is located in one city or cell, and terminal B is located in another city or cell.

[0092] Exemplarily, in a scenario where base station A and base station B are the same, machine room A and machine room B may be the same or two different machine rooms.

[0093] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0094] based on Figure 1In the mobile communication architecture shown, when terminal A initiates a call service to terminal B, a media session (Media Session) is established between the two. During the call process described in the following embodiments and drawings, terminal A will send a SIP request message to the called IMS domain through base station A, computer room A and the calling IMS domain. Then it is sent to terminal B via the called IMS domain, computer room B and base station B. Correspondingly, the SIP response message made by terminal B for the SIP request message initiated by terminal A will be fed back to terminal A via base station B, computer room B, called IMS domain, calling IMS domain, computer room A and base station A. Thus, the establishment of a media session between terminal A and terminal B is realized.

[0095] It should be noted that SIP refers to Session Initialization Protocol. SIP is a multimedia communication protocol developed by the Internet Engineering Task Force (IETF). It is a text-based application layer control protocol used to create, modify and release sessions of one or more participants.

[0096] Exemplarily, in the process of establishing a media session between terminal A and terminal B, the SIP request messages involved may include, for example, INVITE, ACK, PRACK, etc.; the SIP response messages involved may include, for example, 200OK, and various response messages starting with "1", such as 100Trying, 183Session Progress, 180Ringing, etc.

[0097] In addition, it should be noted that when terminal A or terminal B initiates the operation of hanging up the call, the SIP request message involved (such as BYE) will also be transmitted to the IMS domain, computer room and base station corresponding to terminal B through the terminal that initiates BYE, such as the base station, computer room and IMS domain corresponding to terminal A, and finally reach terminal B. Correspondingly, after receiving the BYE sent by terminal A, terminal B will make a 200OK SIP response message and send it to terminal A via base station B, computer room B, called IMS domain, calling IMS domain, computer room A and base station A. At this point, the media session between terminal A and terminal B will be disconnected.

[0098] It should be understood that the above description is only an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation of this embodiment. For the specific process involved in establishing a media session between terminal A and terminal B, the specific process of ending a media session, and the meaning of each SIP request message and SIP response message involved, please refer to the existing protocol standards, which will not be repeated here.

[0099] In addition, it should be understood that the normal progress of the call depends on the wireless network resources determined by the base station and the terminal device (hereinafter referred to as: UE (User Equipment)) based on RRC. With the development of communication technology, for example, 5G network, in order to ensure that the wireless network resources can better adapt to the actual business scenarios during the call, RRC reconfiguration is introduced to modify the RRC connection between the UE and the base station. For example, establish / modify / release RB (Resource Block), perform cell switching (base station switching), set / modify / release measurement reports, etc.

[0100] In addition, it should be understood that RRC reconfiguration can also be implemented in 4G networks. Specifically in 4G networks, RRC reconfiguration is called RRC connection reconfiguration (RRC Reconfiguration). For ease of explanation, this embodiment is described by taking RRC reconfiguration performed in a 5G network as an example.

[0101] Specifically, in the 5G network, the RRC reconfiguration is initiated by the network side (5G base station). That is, the base station actively sends an RRC reconfiguration message to the corresponding UE, such as Figure 2a , and then click “RRC Reconfiguration” in the pop-up window.

[0102] Exemplarily, the RRC reconfiguration message may carry measurement configurations that instruct the UE to perform a measurement operation, configurations of SRS resources for antenna switching modes, configurations of encryption and decryption algorithms used for data packets exchanged with the base station, etc., which are not listed one by one here, and only the configurations involved in the scenarios listed in the subsequent embodiments are taken as examples. For the specific content and format of the RRC reconfiguration message under different configurations, please refer to the existing standard protocol, which will not be repeated here.

[0103] Exemplarily, when the UE receives an RRC reconfiguration message (for example, carrying a measurement configuration instructing the UE to perform a measurement operation) sent by a 5G base station (the base station corresponding to the current cell), the UE will perform the measurement operation according to the measurement configuration and feedback the generated measurement report to the 5G base station. The 5G base station will, based on the measurement report, send an RRC reconfiguration message to the UE instructing the UE to switch to the target base station, so that the UE switches from the currently connected 5G base station to the target base station. In addition, based on the provisions of the existing standard protocol, the UE completes the RRC reconfiguration in accordance with the RRC reconfiguration message sent by the 5G base station, that is, after switching to the target base station, it will reply to the target base station with a message indicating that the RRC reconfiguration is complete, such as Figure 2a”RRC ReconfigurationComplete” shown in the figure. On the contrary, if the target base station cannot match or be compatible with the configuration in the RRC reconfiguration message sent by the 5G base station, the UE will not be able to switch to the target base station. In addition, based on the existing standard protocol regulations, the UE will perform the RLF (Radio Link Failure, RLF) process, such as releasing the connection with the 5G base station in the current cell, reselecting the cell, and then performing the RRC connection re-establishment process with the reselected 5G base station, such as Figure 2b "RRC Connection re-establishment" shown in the figure. When the reselected 5G base station is the 5G base station that has just been disconnected, since the RRC between the UE and the 5G base station was originally normal, the 5G base station will consider that the current RRC connection is abnormal after implementing RRC Connection re-establishment with the UE. Based on the existing standard protocol regulations, the 5G base station will send a BYE message to the UE to end the current call, thereby hanging up the current call.

[0104] Based on the above provisions of the existing standard protocol, if the RRC reconfiguration message sent by the 5G base station is configured strictly in accordance with the existing standard protocol, for example, if the target base station does not support certain configurations, these configurations are canceled in the RRC reconfiguration message instructing the UE to switch to the target base station, the RRC Connection re-establishment process will not be triggered.

[0105] However, in actual application scenarios, it is found that 5G base stations in some areas do not fully follow the existing standard protocol to generate RRC reconfiguration messages. This causes the UE to fail to switch cells according to the RRC reconfiguration message, which in turn causes call interruption.

[0106] For a better understanding, the following combination Figure 3 and Figure 4 , two specific situations that lead to RRC reconfiguration failure are explained.

[0107] Before explaining two specific situations that lead to RRC reconfiguration failure, some descriptions involved in the following embodiments are first explained.

[0108] Specifically, in each embodiment of the present application, the verification operation performed by the UE when receiving the RRC reconfiguration message sent by the network side includes the verification of the information in the RRC reconfiguration message currently received from the network side, and the verification of the contents of the configuration items stored locally by the UE, such as parameters and the values ​​corresponding to the parameters. Specifically, it can be understood that the UE will perform a union processing on the information in the RRC reconfiguration message sent by the network side and the contents of the configuration items stored locally, and then verify all the obtained contents, such as checking whether these contents match or are compatible. For the convenience of description, the present application directly expresses in the drawings and embodiments as verifying the RRC reconfiguration message.

[0109] See also Figure 3 For example, it is assumed that the base stations corresponding to cell A (Cell A), cell B (Cell B) and cell C (Cell C) are all 5G base stations, that is, they all support sending RRC reconfiguration messages.

[0110] Continue to see Figure 3 , for example, in Figure 3 In the scenario shown, the frequency band corresponding to Cell B is the time division duplexing (TDD) mode, such as the n78 cell with a frequency in the n78 frequency range; the frequency band corresponding to Cell C is the frequency division duplexing (FDD) mode, such as the n1 cell with a frequency in the n1 frequency range.

[0111] Continue to see Figure 3 , exemplarily, when the UE establishes a media session with the called party through the base station corresponding to Cell A, the core network, and the IMS domain, via the IMS domain, the core network, and the base station corresponding to the called party, that is, when the UE is making a call in Cell A (S101), Cell A can perform an RRC Reconfiguration process (S102) with the UE.

[0112] Continue to see Figure 3 , exemplarily, the RRC Reconfiguration process mentioned in S102 may include S102a, S102b and S102c.

[0113] Exemplarily, S102a is a step in which a base station in Cell A (hereinafter directly described as a cell) sends an RRC reconfiguration message to the UE. In this embodiment, the RRC reconfiguration message sent by Cell A to the UE is an RRC reconfiguration message carrying measurement configuration (hereinafter referred to as: RRC reconfiguration message 1).

[0114] Exemplarily, S102b is a step in which the UE verifies the content in the RRC reconfiguration message 1. Specifically, the UE verifies whether the information (cell) configured for Cell A in the RRC reconfiguration message 1 is reasonable according to the existing standard protocol and the attributes of Cell A.

[0115] Exemplarily, if the UE successfully verifies the RRC reconfiguration message 1, that is, there is no abnormal information element (or configuration item) in the RRC reconfiguration message 1, the UE will perform RRC reconfiguration according to the RRC reconfiguration message 1, and after completing the RRC reconfiguration, execute S102c. That is, send RRC Reconfiguration Complete to Cell A to inform Cell A that the RRC reconfiguration for the RRC reconfiguration message 1 has been completed.

[0116] Exemplarily, if the UE fails to verify the RRC reconfiguration message 1, the UE will perform RLF, release the connection with Cell A, and then reselect a cell to reside in. When the UE reselects a cell to reside in, it can select the original cell, that is, the currently accessed cell to reside in, or it can select a new cell to reside in. The specific processing after the verification fails, such as S113 to S115, is not described in detail here.

[0117] Exemplarily, this embodiment takes the verification of the content in the RRC reconfiguration message 1 in S102b as successful verification, that is, the UE executes S102c as an example.

[0118] Continue to see Figure 3 For example, since the RRC reconfiguration message 1 carries the measurement configuration, after the UE completes the RRC reconfiguration according to the RRC reconfiguration message 1, the UE will perform a measurement operation.

[0119] Understandably, the purpose of RRC reconfiguration is to ensure that the wireless network resources can better adapt to the actual business scenario during the call. Therefore, it is necessary to ensure that the signal of the cell to be switched to is stronger than the signal of the currently connected cell. Therefore, the measurement configuration carried in the RRC reconfiguration message can be the measurement configuration for triggering the UE to perform the A3 event (the measurement configurations carried in other subsequent RRC reconfiguration messages are all used as an example to trigger the UE to perform the A3 event).

[0120] Based on this, the UE will execute S103 according to the measurement configuration, that is, when the signal of Cell A gradually weakens and the signal of Cell B gradually strengthens during the process of moving from Cell A to Cell B, the UE will generate an A3 measurement report (A3 MR).

[0121] Continue to see Figure 3, exemplarily, after the UE generates the A3 MR, it sends the A3 MR to Cell A, that is, executes S104.

[0122] Continue to see Figure 3 For example, after Cell A receives the A3 MR sent by the UE, it sends an RRC reconfiguration message 2 to the UE to instruct the UE to switch to Cell B, that is, execute S105.

[0123] It is understandable that the A3 MR generated by the UE may include the address information of Cell B whose signal is gradually getting stronger. Therefore, the RRC reconfiguration message 2 sent by CellA to the UE may carry the address information of Cell B to be switched to, so that the UE can switch to Cell B according to the address information of CellB.

[0124] In addition, the RRC reconfiguration message 2 may also carry relevant information of Cell B, such as attributes, which configuration items are currently configured, etc., which are not listed here one by one and are not limited in this application.

[0125] Understandably, the UE needs to perform a verification operation when receiving any RRC reconfiguration message sent by the network side. Therefore, after receiving the RRC reconfiguration message 2 sent by Cell A, the UE will also verify the content in the RRC reconfiguration message 2.

[0126] Exemplarily, if the UE successfully verifies the RRC reconfiguration message 2, the UE will switch to Cell B according to the address information of Cell B carried in the RRC reconfiguration, and will stay in Cell B before receiving the next cell switching instruction.

[0127] It should be understood that after the UE camps on Cell B, if the call is not hung up, the current media session will continue in Cell B, that is, the call between the UE and Cell A in S101 will be conducted between the UE and Cell B.

[0128] Exemplarily, if the UE fails to verify the RRC reconfiguration message 2, the UE will perform the RLF process, such as releasing the connection with the current cell, and then reselecting a cell to reside in. When the UE reselects a cell to reside in, it can also select the original cell to reside in, or select a new cell to reside in. The specific processing performed after the verification fails, such as S113 to S115, is not described in detail here.

[0129] Exemplarily, this embodiment takes the case where the UE verifies the content in the RRC reconfiguration message 2 successfully as an example, that is, after the UE receives the RRC reconfiguration message 2 sent by Cell A, S106 is executed.

[0130] Since the result of S106 is that the UE successfully verifies the content in RRC reconfiguration message 2, the UE will send RRC Reconfiguration Complete to Cell A after residing in Cell B, informing Cell A that the RRC reconfiguration (switching to Cell B) for RRC reconfiguration message 2 is completed, that is, S107 is executed.

[0131] Continue to see Figure 3 , exemplarily, if the call is continuing between the UE and Cell B, Cell B performs an RRC Reconfiguration process (S108) with the UE.

[0132] Continue to see Figure 3 , exemplarily, the RRC Reconfiguration process mentioned in S108 may include S108a, S108b, S108c and S108d.

[0133] Exemplarily, S108a is a step in which a base station in Cell B (hereinafter directly described as a cell) sends an RRC reconfiguration message to a UE. In this embodiment, an RRC reconfiguration message sent by Cell B to a UE is an RRC reconfiguration message (hereinafter referred to as RRC reconfiguration message 3) carrying the configuration of an SRS resource of an antenna switching mode as an example.

[0134] The SRS (Sounding Reference Signal) mentioned above is a signal used to detect the channel quality of the uplink frequency band. Specifically in practical applications, the configuration of the SRS resources for periodically sending SRS provided to the UE can be notified to the UE through the SIB (System Information Blocks) message sent by the network side, or the RRC Connection Setup message, or the RRC reconfiguration message mentioned above.

[0135] Among them, the configuration of SRS resources sent through SIB corresponds to Cell Specific SRS (cell-specific SRS); the configuration of SRS resources sent through RRC connection establishment message or RRC reconfiguration message corresponds to Dedicated SRS (UE-specific SRS).

[0136] Among them, the configuration of SRS resources can support four modes: beam management, codebook, non-codebook, and antenna switching.

[0137] For the beam management mode, which is related to SSB (Synchronization Signal / PBCH Block) beam management, no base station feedback is required.

[0138] For the codebook mode, the base station obtains SRI (SRS resource indicator, SRS resource configuration identifier), TPMI (Transmitted Precoding Matrix Indicator, broadband precoding matrix indication), and RI (Rank Indicator) information by measuring SRS, and then feeds back the three to the UE as needed based on the codebook situation.

[0139] For the non-codebook mode, the base station obtains SRI, TPMI, and RI information by measuring SRS, and feeds back SRI to the UE. The PUSCH (Physical Uplink Shared CHannel) selects the same precoding matrix as the SRS (the precoding matrix selection of the SRS corresponding to the SRI may come from the CSI-RS (Channel State Information-Reference Signal) measurement).

[0140] For the antenna switching mode, when the downlink CSI (channel state information) cannot be obtained, SRS is used to measure the downlink CSI. Because the UE generally has fewer transmitting antennas, the UE needs to traverse all antennas through antenna switching (it can be understood that the UE transmits SRS on multiple antennas in turn) to measure the uplink CSI. The base station obtains the downlink CSI based on the uplink CSI according to the reciprocity of the uplink and downlink channels. This does not require base station feedback. However, according to the provisions of the existing standard protocol, TDD cells (i.e., cells whose corresponding frequency bands belong to the TDD mode) support the configuration of SRS resources in the antenna switching mode, but FDD cells (i.e., cells whose corresponding frequency bands belong to the FDD mode) do not support the configuration of SRS resources in the antenna switching mode. The specific reasons are as follows: For TDD systems, uplink and downlink share the same spectrum resource, and time division is used to distinguish uplink and downlink. In this way, in most cases, for a given UE, we can assume that the uplink and downlink it experiences are the same path, that is, the spatial characteristics are approximately the same, which we also call uplink and downlink channel reciprocity. In this way, the TDD system can use the uplink and downlink channel reciprocity to obtain the CSI of the downlink channel through the uplink SRS. Furthermore, in order to obtain the downlink CSI information of each channel, the base station can let the UE switch to different antenna ports to send SRS in turn, thereby achieving the purpose of obtaining the CSI of each downlink channel through the uplink SRS of each uplink channel. For FDD systems, downlink and uplink are two independent spectrum resources, and uplink and downlink channel reciprocity cannot be used. Therefore, SRS cannot be used to evaluate the downlink channel quality in FDD mode, and thus the FDD system does not support the configuration of SRS resources in antenna switching mode.

[0141] For the specific implementation of SRS round-robin transmission, please refer to the existing protocol and will not be repeated here.

[0142] Exemplarily, S108b is a step in which the UE verifies the content in the RRC reconfiguration message 3. Specifically, the UE verifies whether the information (cell) configured for Cell B in the RRC reconfiguration message 3 is reasonable according to the existing standard protocol and the attributes of Cell B.

[0143] From the above description, it can be known that Cell B is a TDD system, and the TDD system supports the configuration of SRS resources in the antenna switching mode. Therefore, it is reasonable to carry the configuration of SRS resources in the antenna switching mode in the RRC reconfiguration message 3, so the UE successfully verifies the content in the RRC reconfiguration message 3. The UE will perform RRC reconfiguration according to the RRC reconfiguration message 3, for example, configure the SRS resources in the antenna switching mode, that is, execute S108c.

[0144] Continue to see Figure 3 Exemplarily, after completing the RRC reconfiguration according to the RRC reconfiguration message 3, the UE will execute S108d, that is, send an RRC Reconfiguration Complete message to Cell B to inform Cell B that the RRC reconfiguration for the RRC reconfiguration message 3 has been completed.

[0145] Continue to see Figure 3 , exemplarily, in some implementations, Cell B may also send an RRC reconfiguration message carrying measurement configuration to the UE.

[0146] Exemplarily, in some other implementations, the measurement configuration that instructs the UE to perform a measurement operation may also be directly carried in the RRC reconfiguration message 3.

[0147] Regarding the processing of the RRC reconfiguration message by the UE, please refer to S102a to S102c, which will not be described in detail here.

[0148] For ease of explanation, this embodiment still takes verification success as an example, that is, the UE will perform measurement and reporting operations according to the measurement configuration, that is, execute S109. Specifically, in S109, when the UE moves from Cell B to Cell C, when the signal of Cell B gradually weakens and the signal of Cell C gradually strengthens, an A3 measurement report (A3 MR) will be generated.

[0149] Continue to see Figure 3 , exemplarily, after generating A3 MR, UE sends A3 MR to Cell B, that is, executes S110.

[0150] Continue to see Figure 3 , exemplarily, after Cell B receives the A3 MR sent by the UE, it sends the RRC reconfiguration message 4 to the UE to instruct the UE to switch to Cell C, that is, execute S111. Exemplarily, in this embodiment, the configuration of the SRS resources for the antenna switching mode is not removed in the RRC reconfiguration message 4, that is, the configuration of the SRS resources for the antenna switching mode is still retained. After the UE receives the RRC reconfiguration message 4 sent by Cell B, it will also verify the content in the RRC reconfiguration message 4, that is, execute S112.

[0151] It can be seen from the above description that Cell C is an FDD system, and the FDD system does not support the configuration of the SRS resources of the antenna switching mode. Therefore, according to the provisions of the existing standard protocol, Cell B should send an RRC reconfiguration message for removing the configuration of the SRS resources of the antenna switching mode to the UE before the RRC reconfiguration message 4, so as to instruct the UE to release the SRS resources of the antenna switching mode that have been configured. Alternatively, the information for removing the configuration of the SRS resources of the antenna switching mode is directly carried in the RRC reconfiguration message 4.

[0152] However, in Figure 3 In the scenario shown, when Cell B sends RRC reconfiguration message 4 to UE, it does not carry information for removing the configuration of SRS resources of antenna switching mode in RRC reconfiguration message 4. However, UE configures SRS resources of antenna switching mode in S108d. The configuration of a parameter previously received in Cell B and saved in UE has not been deleted by the network according to the protocol. When UE applies the configuration of the parameter previously saved in Cell B to Cell C to be switched, because Cell C does not support the configuration of the parameter, the configuration of the parameter in UE will be incompatible or mismatched with Cell C, which will cause the RRC reconfiguration message verification to fail. It should be understood that in the verification of an RRC reconfiguration message involved in this article, in some actual scenarios, the terminal device will verify the information carried in the RRC reconfiguration message (or the content in the message) in combination with the configuration information already saved in the terminal device (the saved configuration information may be from another one or more RRC reconfiguration messages before the RRC reconfiguration message) to obtain the verification result of the RRC reconfiguration message. Therefore, when the UE verifies the RRC reconfiguration message 4 (the message may include relevant information of Cell C), because Cell C does not support the configuration of SRS resources of the antenna switching mode already saved in the terminal device, the UE's verification result for the RRC reconfiguration message 4 is verification failure.

[0153] Continue to see Figure 3 For example, when the UE fails to verify the RRC reconfiguration message 4, the UE will execute the RLF process (including releasing the connection with Cell B), and then reselect the cell, and then reside in the reselected cell.

[0154] For the operation performed by the UE when the RRC reconfiguration message verification fails, reference may be made to the existing standard protocol. This embodiment takes the selection of the original cell to camp on as an example, that is, after the UE fails to verify the RRC reconfiguration message 4, the UE performs S113 as an example.

[0155] Continue to see Figure 3For example, if the UE chooses to reside in the original cell (i.e., Cell B where the UE resides before switching), the UE will send an RRC connection re-establishment request (RRC Connection re-establishment Request) message carrying the reason value of RRC reconfiguration failure (such as Reconfiguration failure) to Cell B, for example, sending an RRC Connection re-establishment Request carrying Reconfiguration failure to Cell B, thereby enabling Cell B and the UE to perform the RRC connection re-establishment process, that is, execute S114.

[0156] Exemplarily, after receiving the RRC Connection re-establishment Request, Cell B will reply to the UE with an RRC Connection Setup message indicating the radio bearer and the serving cell group, so that the UE and Cell B re-establish the RRC connection.

[0157] For the specific implementation process of re-establishing the RRC connection between the UE and the base station, please refer to the existing standard protocol, which will not be repeated here.

[0158] Exemplarily, since the RRC Connection re-establishment Request carries Reconfiguration failure, after the RRC connection between the UE and Cell B is successfully re-established, Cell B will immediately send the reason for the RRC reconfiguration failure to the UE. Since the RRC connection between Cell B and the UE is normal before the RRC connection is re-established, in the scenario where the cell reselected by the UE is the original cell, the original cell, i.e. Cell B, will think that there is an abnormality in the RRC connection between the UE. In this case, Cell B will immediately send a BYE message to the UE. And the reason field of the BYE message carries the reason that Cell B determines that the reason for the failure to switch from Cell B to Cell C is insufficient bearer resources (Insufficient Bearer Resource), and the corresponding error code is 503, i.e. S115.

[0159] Since Cell B sends a BYE message to release the current call, the call between the UE and Cell B will be disconnected.

[0160] Through analysis, it was found that the reason why the UE failed to HO (handover) from the n78 cell (n78 frequency band belongs to the TDD mode) to the n1 cell (n1 frequency band belongs to the FDD mode) during the call was that the network (here "network" specifically refers to the base station corresponding to the n78 cell) configured the SRS resources of the antenna switching mode for the UE in the n78 cell, and before switching to the cell that does not support the configuration of the SRS resources of the antenna switching mode, the network (here "network" specifically refers to the base station corresponding to the n78 cell) did not instruct the UE to remove this configuration (in this case, according to the provisions of the standard protocol process, the base station corresponding to the n78 cell should send an RRC message carrying the configuration of removing the SRS resources of the antenna switching model to the UE before instructing the UE to switch to another cell (the cell does not support the configuration of the SRS resources of the antenna switching mode). Reconfiguration message to instruct the UE to release the SRS resources on the UE side), and the n1 cell cannot support the configuration of SRS resources in the antenna switching mode. Therefore, when the UE switches to the n1 cell, the SRS switching will fail based on the SRS resources previously configured by the network for the UE in the n78 cell.

[0161] Therefore, from the above description, it can be seen that the UE does not switch from Cell B to Cell C not because of insufficient bearer resources, but because there is a configuration incompatible with Cell C in the RRC reconfiguration message 4, such as the configuration of SRS resources with an antenna switching mode incompatible with Cell C mentioned above.

[0162] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0163] See also Figure 4 For example, take the scenario where the UE selects a new cell to reside in when the RRC reconfiguration message verification fails.

[0164] Specifically in this embodiment, Figure 3 Taking the limitation of Cell A, Cell B, and Cell C in the embodiment shown as an example, the specific implementation of S201 to S207 can be referred to. Figure 3 S101 to S107 in the illustrated embodiment are not described in detail here. Figure 4 S208 to S220 shown in the figure illustrate the specific processing involved when the UE selects a new cell (such as Cell A, which is a new cell relative to Cell B to which the UE has just released the connection and Cell C to which it is trying to switch) to reside when the RRC reconfiguration message 4 verification fails.

[0165] S208: The UE performs an RRC Reconfiguration process with Cell B.

[0166] See also Figure 4 , exemplarily, the RRC Reconfiguration process mentioned in S208 may include S208a, S208b, S208c and S208d.

[0167] Exemplarily, S208a is the step of Cell B sending an RRC reconfiguration message to the UE. In this embodiment, the RRC reconfiguration message 3 sent by Cell B to the UE is an RRC reconfiguration message carrying the configuration of the SRS resources of the antenna switching mode and the configuration of starting the ROHC algorithm as an example. It should be understood that in actual applications, the configuration of the SRS resources of the antenna switching mode and the configuration of starting the ROHC algorithm can be sent to the UE through the same RRC reconfiguration message, or can be sent to the UE through different RRC reconfiguration messages, and this embodiment does not limit this.

[0168] Exemplarily, S208b is a step in which the UE verifies the content in the RRC reconfiguration message 3. Specifically, the UE verifies whether the information (cell) configured for Cell B in the RRC reconfiguration message 3 is reasonable according to the existing standard protocol and the attributes of Cell B.

[0169] Understandably, both the base station and the UE are usually capable of using the ROHC algorithm (an algorithm that is generally recognized as being ideal for data header compression and decompression on a wireless link). By default, the UE can be set to turn off the ROHC algorithm (i.e., the UE does not use the ROHC algorithm). When receiving an RRC reconfiguration message sent by the base station and the RRC reconfiguration message carries a configuration for starting the ROHC algorithm, the UE starts the ROHC algorithm.

[0170] In addition, it should be understood that when the base station notifies the UE to start the ROHC algorithm, it will also start the ROHC algorithm. In this way, when the UE resides in the cell where the base station is located, the two can use the ROHC algorithm to compress the sent data packets and decompress the received data packets.

[0171] In addition, in this embodiment, Cell B is a TDD system, and the TDD system supports the configuration of SRS resources in the antenna switching mode. Therefore, it is reasonable to carry the configuration of SRS resources in the antenna switching mode in the RRC reconfiguration message 3, so the UE successfully verifies the content in the RRC reconfiguration message 3. The UE will perform RRC reconfiguration according to the RRC reconfiguration message 3, such as configuring the SRS resources in the antenna switching mode, and start the ROHC algorithm, that is, execute S208c.

[0172] Continue to see Figure 4 Exemplarily, after completing the RRC reconfiguration according to the RRC reconfiguration message 3, the UE will execute S208d, that is, send an RRC Reconfiguration Complete message to Cell B to inform Cell B that the RRC reconfiguration for the RRC reconfiguration message 3 has been completed.

[0173] Continue to see Figure 4 , exemplarily, in some implementations, Cell B may also send an RRC reconfiguration message carrying measurement configuration to the UE.

[0174] Exemplarily, in some other implementations, the measurement configuration that instructs the UE to perform a measurement operation may also be directly carried in the RRC reconfiguration message 3.

[0175] Regarding the processing of the RRC reconfiguration message by the UE, please refer to S102a to S102c, which will not be described in detail here.

[0176] For the convenience of description, this embodiment still takes verification success as an example, that is, the UE will perform a measurement and reporting operation according to the measurement configuration, that is, execute S209.

[0177] S209: When the UE moves from Cell B to Cell C, when the signal of Cell B gradually becomes weaker and the signal of Cell C gradually becomes stronger, an A3 measurement report (A3 MR) is generated.

[0178] S210: UE sends A3 MR to Cell B.

[0179] S211: Cell B sends an RRC reconfiguration message 4 to the UE, instructing the UE to switch to Cell C.

[0180] This embodiment still takes the configuration of the SRS resources without removing the antenna switching mode in the RRC reconfiguration message 4 as an example.

[0181] S212: The UE verifies the RRC reconfiguration message 4.

[0182] Understandably, when Cell B sends RRC reconfiguration message 4 to UE, it has already exchanged data with Cell C according to A3 MR reported by UE in S210. Assuming that Cell C also starts ROHC algorithm, there is no need to carry the configuration of shutting down ROHC algorithm in RRC reconfiguration message 4. Therefore, UE will not shut down ROHC algorithm.

[0183] In addition, regarding the processing logic of the S212 verification process, reference may be made to S112 in the above embodiment, which will not be repeated here.

[0184] S213: Execute the RLF process and select a new cell (Cell A) to reside.

[0185] For specific operations involved in executing RLF, refer to existing standard protocols.

[0186] Continue to see Figure 4 For example, if after executing the RLF process, the UE chooses to reside in the new cell (Cell A), the UE will send an RRC Connection re-establishmentRequest carrying a Reconfiguration failure to Cell A, thereby enabling Cell A and the UE to perform the RRC connection re-establishment process, that is, execute S214.

[0187] S214: RRC connection re-establishment process for the new cell.

[0188] Specifically, since Cell A is a new cell, Cell A can send RRC reconfiguration message 5 to the UE. After successfully verifying RRC reconfiguration message 5, the UE can send RRC Reconfiguration Complete to Cell A to inform Cell A that the RRC reconfiguration for RRC reconfiguration message 5 has been completed. In this way, the RRC connection between the UE and Cell A is established.

[0189] Continue to see Figure 4 For example, in S208c, after the UE successfully verifies the RRC reconfiguration message 3, the UE starts the ROHC algorithm according to the configuration of starting the ROHC algorithm carried in the RRC reconfiguration message 3. However, before residing in Cell A, the UE does not receive the RRC reconfiguration message of disabling the ROHC algorithm sent by Cell B. Therefore, after residing in Cell A, the UE still starts the ROHC algorithm.

[0190] Based on this, if Cell A does not start the ROHC algorithm, after the RRC connection between the UE and Cell A is established, the UE will continue to compress and decompress the data packet based on the ROHC algorithm, that is, execute S215. Cell A will use a non-ROHC algorithm to compress and decompress the data packet, that is, execute S216.

[0191] S215: compressing and decompressing the data packet based on the ROHC algorithm.

[0192] That is, the UE will compress the uplink RTP sent to Cell A based on the ROHC algorithm, and decompress the downlink RTP packet received from Cell A based on the ROHC algorithm.

[0193] S216: The base station corresponding to Cell A does not start the ROHC algorithm and uses a non-ROHC algorithm to compress and decompress the data packet.

[0194] That is, Cell A will use a non-ROHC algorithm to compress the uplink RTP sent to the UE, and use a non-ROHC algorithm to decompress the downlink RTP packet received from the UE.

[0195] S217: Uplink RTP packet / downlink RTP packet.

[0196] Understandably, for the UE, the uplink RTP in S217 is the RTP packet sent by the UE to Cell A, and the downlink RTP packet is the RTP packet sent by Cell A to the UE. For Cell A, the uplink RTP in S217 is the RTP packet sent by Cell A to the UE, and the downlink RTP packet is the RTP packet sent by the UE to Cell A.

[0197] S218: Decompression failed, discarded.

[0198] Understandably, after receiving the RTP packet sent by Cell A, the UE decompresses the received RTP packet based on the ROHC algorithm, while Cell A does not use the ROHC algorithm to compress the RTP to be sent to the UE. Therefore, the UE will not be able to decompress the RTP packet sent by Cell A, that is, the decompression will fail. For the RTP packet that fails to be decompressed, the UE will directly discard it.

[0199] S219: Decompression failed, discarded.

[0200] Understandably, after receiving the RTP packet sent by the UE, Cell A does not decompress the received RTP packet based on the ROHC algorithm, while the UE uses the ROHC algorithm to compress the RTP to be sent to Cell A. Therefore, Cell A will not be able to decompress the RTP packet sent by the UE, that is, the decompression will fail. Cell A will also directly discard the RTP packet that fails to be decompressed.

[0201] In this way, the UE and Cell A will not receive the RTP packets related to the current call sent by each other. Based on the provisions of the existing standard protocol, when the UE does not receive the RTP packets related to the current call within a certain period of time, it will determine that the current call has an RTP or RTCP (Real-time Transport Control Protocol) resource timeout. In this case, the UE will send a BYE message to Cell A. And the RTP / RTPC resource timeout (RTP / RTCP timeout Resource) is carried in the reason field of the BYE message, and the corresponding error code is 2, that is, S220.

[0202] S220: BYE message (reason field: cause = 2; text = "RTP / RTCP timeout Resource").

[0203] Since the UE sends a BYE message to release the current call, the call between the UE and Cell A will be disconnected. The reason why the UE and Cell A cannot receive the RTP packets sent by each other is not that the UE and Cell A do not send RTP packets at the set time, but that the configurations of the UE and Cell A do not match, such as one has the ROHC algorithm enabled and the other has not.

[0204] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0205] Through the above Figure 3 and Figure 4From the description of the scenario, it can be seen that the call drop problem that occurs after the UE is triggered to execute the RLF process and reselect the cell to reside is caused by the UE's failure to verify the RRC reconfiguration message sent by the network side. For example, in one scenario, during the verification of the RRC reconfiguration message, since the RRC reconfiguration message instructs the UE to switch to the specified cell C, and the RRC reconfiguration message does not carry a configuration item about a parameter of cell C (such as not carrying information for deleting the configuration of the SRS resources of the antenna switching mode), but the UE has a configuration of the SRS resources of the antenna switching mode that is incompatible with cell C, this will cause the RRC reconfiguration message to fail to verify. In view of this, some embodiments of the present application provide a method for calls, which aims to enable the terminal device to update abnormal configuration items (there are abnormalities in the parameters of the configuration items, such as the current corresponding values ​​are incompatible with the cell to be stationed, do not match, etc.) when the network side does not fully control the configuration of certain parameters in accordance with the existing standard protocol, so that the RRC reconfiguration message used to instruct the UE to switch to the designated cell is successfully verified, and then the UE can smoothly switch from the original cell to the designated cell, thereby reducing the occurrence of switching failures, so that during a call, even if the UE switches cells, it will not cause problems with the call, thereby reducing call failures and improving user experience. Or, as in another scenario, in the process of verifying the RRC reconfiguration message, because the RRC reconfiguration message carries a certain configuration item corresponding to the current cell B (a certain configuration item may also be referred to as the configuration of a certain parameter), but the configuration item carried by the RRC reconfiguration message is incompatible or does not match the corresponding configuration item corresponding to the current cell B previously saved in the UE (it can be understood that the value of a certain parameter corresponding to the current cell B carried by the RRC reconfiguration message is incompatible or does not match the value of the parameter corresponding to the current cell B previously saved in the UE), resulting in an error or failure in the subsequent process, and then causing the call to be abnormal. In this scenario, some embodiments of the present application provide a method for calls, which is intended to enable a terminal device to update abnormal configuration items when the network side does not fully control the configuration of certain parameters in accordance with existing standard protocols, so that the RRC reconfiguration message is successfully verified, and then the call can continue smoothly.

[0206] Specifically, in the method for calls provided in some embodiments of the present application, a method for updating configuration items with abnormalities is introduced, a method for updating some configuration items in the RRC reconfiguration message, that is, when the UE verifies the RRC reconfiguration sent by the currently connected base station and carrying the configuration for switching to the target base station, it detects whether the UE has turned on a function that allows updating of incompatible configuration items (hereinafter referred to as: compatible function). Furthermore, when it is determined that the function is started, and the configuration items that are not matched / incompatible with the target base station (also referred to herein as: abnormal configuration items) in the RRC reconfiguration message are configuration items in the preset configuration item list, these abnormal configuration items are updated, such as by not taking into effect the configuration of these abnormal configuration items (hereinafter referred to as method 1, for method 1, in practice, the value corresponding to the abnormal configuration item can be changed from "1" (which can indicate that the configuration item has a corresponding configuration) to "0" (which can indicate that the configuration corresponding to the configuration item is removed), so that the configuration of the abnormal configuration item can be not taken into effect (it can also be understood as removing the configuration corresponding to the abnormal configuration item), so as to achieve the effect of ignoring the abnormal configuration item. The configuration of the abnormal configuration item that is not effective can be understood as ignoring the abnormal configuration item.), or by updating the content of the configuration item with abnormality in the UE to the content of the configuration item in the RRC reconfiguration message (hereinafter referred to as method 2), so that the RRC reconfiguration message verification is successful, thereby achieving switching from the current base station to the target base station.

[0207] It should be noted that the configuration items in the preset configuration item list mentioned in this application are specifically determined based on the existing standard protocol and the attributes of the target base station actually to be switched to, and the configuration items allowed to be updated in accordance with the above-mentioned method 1 or method 2 are determined, and after the configuration items in the preset configuration item list are updated, it will not affect the RRC reconfiguration.

[0208] In order to better understand the method for making a call provided by the present application, Figure 3 and Figure 4 Based on the scenario shown, the method for making a call provided in the embodiment of the present application is introduced, combined with Figure 5 The specific implementation scenario is described.

[0209] Before explaining the method for making a call provided in the embodiments of the present application, some descriptions involved in the following embodiments are first explained.

[0210] Specifically, in each embodiment of the present application, the preset configuration item list is the parameter configuration list pre-saved in the terminal device mentioned above.

[0211] Accordingly, the updateable configuration items are the above-mentioned ignorable parameters.

[0212] In addition, in each embodiment of the present application, the configuration item with an abnormality is the configuration item with an abnormal value corresponding to the above-mentioned parameter. For example, when the value corresponding to the first parameter is abnormal, the first configuration item including the first parameter is the configuration item with an abnormality.

[0213] Based on this premise, in the following embodiments and the accompanying drawings corresponding to the embodiments, it is determined whether the configuration item with an abnormality is a configuration item in the preset configuration item list (such as S404). In essence, when the value corresponding to the first parameter is abnormal, it is determined whether the first parameter is the same as any parameter in the parameter list saved in the terminal device. Since the parameter value corresponding to each parameter included in the parameter list can be updated. Therefore, when it is determined that the first parameter is the same as any parameter in the parameter list saved in the terminal device, it can be determined that the first parameter is a negligible parameter. That is, the configuration item with an abnormality in the following embodiments is an updateable configuration item.

[0214] Accordingly, when a configuration item includes parameters and corresponding parameter values, updating the configuration item essentially means updating the values ​​corresponding to the parameters in the configuration item.

[0215] See also Figure 5 , S301 to S311 and Figure 4 S201 to S211 in the embodiment are similarly implemented, and the specific implementation details are described in S201 to S211, which will not be repeated here. Among them, S312 to S319 are the processing logics performed by the UE and the network side after the method for calling provided by the present application is introduced.

[0216] Continue to see Figure 5 For example, after receiving the RRC reconfiguration message 4 sent by Cell B, when verifying the RRC reconfiguration message 4, the UE will detect whether the Cell C to which it is requested to switch is an FDD system, and whether the UE has configured the antenna switching mode based on the RRC reconfiguration message previously received from the network side.

[0217] It can be seen from the description of the above embodiment that when the target base station to be switched to is an FDD system, that is, it does not support the configuration of SRS resources in the antenna switching mode, but the UE is configured with SRS resources in the antenna switching mode, the UE will make a result of RRC reconfiguration message verification failure. Therefore, after introducing the method for calling provided by the present application, the UE needs to determine through S312 whether the current Cell C is an FDD system and the UE is configured with SRS resources in the antenna switching mode.

[0218] Accordingly, when it is determined that the above situation occurs, based on the user call method provided in the present application, the UE will further detect whether the compatible function is activated, that is, execute S313.

[0219] According to the provisions of the existing standard protocol, for the FDD system, the configuration of the SRS resources in the antenna switching mode is not supported. Therefore, when the target base station to be switched to is an FDD system, the UE may not check the configuration of the SRS resources in the antenna switching mode, and make the RRC reconfiguration message 4 verification successful when other configurations are compatible.

[0220] For example, in some implementations, the configuration of the SRS resources in the antenna switching mode may be agreed upon, such as srs_tx_switch=1 indicating that the SRS resources in the antenna switching mode are configured. When the compatible function is activated, in S317, the UE may locally modify the configuration of the SRS resources in the antenna switching mode from the above-mentioned "1" to "0", that is, modify srs_tx_switch=1 to srs_tx_switch=0.

[0221] The enabling of the compatibility function can be understood as the function of updating the abnormal configuration item being enabled, which may be enabled by the UE by default or enabled by the user on the UE.

[0222] Continue to see Figure 5 , exemplarily, after completing S317, since the configuration items of Cell C of the FDD system that do not conform to the existing standard protocol in RRC reconfiguration message 4, such as the configuration of the SRS resources of the antenna switching mode, have been updated to srs_tx_switch=0 in the UE, that is, the UE has removed the SRS resources of the antenna switching mode, the verification result of the UE on the RRC reconfiguration message 4 is successful. In this way, the UE can switch to Cell C according to the address information corresponding to Cell C in the RRC reconfiguration message 4, and stay in Cell C before receiving the next instruction to switch the cell, that is, execute S318.

[0223] From the above description, it can be known that after the UE completes the RRC reconfiguration, it will send RRCReconfiguration Complete to the network side to inform the network side that the UE has completed the RRC reconfiguration. Based on this, after the UE resides in CellC, the UE will also send RRC Reconfiguration Complete to CellC to inform CellC that the RRC reconfiguration (switching to CellC) for RRC reconfiguration message 4 has been completed, that is, S319 is executed.

[0224] Exemplarily, after the UE resides in Cell C, if the call is not hung up, the current media session will continue in Cell C, that is, the call is conducted between the UE and Cell C.

[0225] Exemplarily, if it is determined in S313 that the UE has not enabled the compatible function, in this case, the UE may be configured to execute the existing cell reselection process according to the existing standard protocol.

[0226] Continue to see Figure 5 For example, this embodiment takes the scenario where the UE selects the original cell to camp on when the UE does not enable the compatible function as an example. Among them, S314 to S316 involved in camping on the original cell are the same as Figure 3 The implementation of S113 to S115 in the illustrated embodiment is similar, and the specific implementation details are described in S113 to S115, which will not be repeated here.

[0227] For example, in some other implementations, for example, when the UE does not enable the compatible function, the UE selects a new cell, such as Cell A, to camp on. For details, see Figure 4 The description of S213 to S220 in the illustrated embodiment will not be repeated here.

[0228] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0229] In addition, it should be noted that regarding the activation of the compatibility function (the name of the function may also be other names), in some implementations, the terminal manufacturer may turn on the compatible function switch of the UE deployed in a certain area or a certain type of UE in accordance with the customization requirements before the UE leaves the factory. In this way, for the UE in the area or the type of UE, the configuration items with abnormalities can be updated according to the user call method provided in the embodiment of the present application, so that the RRC reconfiguration message is successfully verified, thereby ensuring that there will be no abnormalities in the call. For example, according to the above method 1, the UE updates the configuration item of the SRS resource configuration of the antenna switching mode, thereby ensuring that the UE can smoothly switch from the cell of the TDD system to the cell of the FDD system, reducing the occurrence of switching failures and ensuring that the call is not hung up.

[0230] For example, in some other implementations, all UEs generated by the terminal manufacturer may be configured to enable the compatibility function by default. For this implementation, when it is determined that Cell C is an FDD system and the UE is configured with an antenna switching mode, S313 to S316 may be skipped directly and S317 may be executed.

[0231] Exemplarily, in some other implementations, an entry for user operation may also be provided in the UE, and the user may decide whether to enable the compatible function according to needs.

[0232] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0233] because Figure 5 The described embodiment is mainly aimed at the problem scenario caused by the configuration of the SRS resources of the antenna switching mode, so the configuration items with abnormalities that can be updated are mainly the configuration items of the SRS resources of the antenna switching mode. However, in actual application scenarios, for scenarios that do not involve the configuration of the SRS resources of the antenna switching mode, there will also be problems such as cell switching failure due to incompatibility of configuration items. In view of this, the embodiment of the present application proposes another method for calls, by pre-determining the configuration items that can be updated by the UE in different scenarios according to the existing standard protocol (the configuration items that can be updated by the UE can also be understood as the configuration items that can be modified by the UE), and these UE-updatable configuration items can be pre-configured in the UE, such as the preset configuration item list described above can be configured in the UE. In this way, when the UE verifies the content in the RRC reconfiguration message from the network side, it directly determines whether the configuration item that caused the verification failure can be updated according to the above method 1 or method 2 based on the pre-set updateable configuration items, and then when the configuration item that caused the abnormality can be updated, these abnormal configuration items are updated according to the above method 1 or method 2 (it can also be understood as correcting these abnormal configuration items), so that the UE can be unaffected by these abnormal configuration items and can switch to the target cell normally. Regarding this implementation method, the following is combined with Figure 6 Provide specific instructions.

[0234] See also Figure 6 Exemplarily, when the UE is making a call in the first cell (S401), if it receives a first RRC reconfiguration message sent by the first cell (S402), the UE will verify the first RRC reconfiguration message (S403).

[0235] The process of establishing a media session between the UE and the first cell may be referred to S101 in the above embodiment, which will not be described in detail here.

[0236] The first cell mentioned above may be, for example, Cell A, Cell B, or Cell C in the above embodiment. For ease of understanding, this embodiment takes Cell B as the first cell as an example.

[0237] When the first cell is Cell B, the first RRC reconfiguration message, for example, may be RRC reconfiguration message 3 or RRC reconfiguration message 4 sent by Cell B to the UE in the above embodiment.

[0238] Regarding the verification logic of the UE for the first RRC reconfiguration message, please refer to S108b, or S112, or S208b, or S212, or S308b, etc. in the above embodiments, which will not be repeated here.

[0239] Continue to see Figure 6 For example, if after verification, it is determined that there are no abnormal configuration items (or incompatible configuration items) in the first RRC reconfiguration message, it can be considered that the verification of RRC reconfiguration message 4 is successful, and the UE can execute S410 at this time; conversely, if there are abnormal configuration items, it can be considered that the verification of RRC reconfiguration message 4 has failed, and the UE can execute S405 at this time.

[0240] It should be noted that the configuration carried by the first RRC reconfiguration message may be for the first cell, or may indicate switching to the second cell (taking Cell C as an example). Therefore, in S410, the UE may perform specific operations according to the cell targeted by the first RRC reconfiguration message.

[0241] Continue to see Figure 6 Exemplarily, when the first RRC reconfiguration message indicates switching to the second cell, the operation to be performed by the UE is to reside in the second cell according to the first RRC reconfiguration message, that is, to perform S410a. Accordingly, after the UE resides in the second cell, it will send an RRC Reconfiguration Complete to the second cell, that is, to perform S410b. The current call of the UE will continue in the second cell.

[0242] Continue to see Figure 6 Exemplarily, when the first RRC reconfiguration message carries the configuration for the first cell (such as RRC reconfiguration message 3 in the above embodiment), the operation to be performed by the UE is to configure according to the configuration carried in the first RRC reconfiguration message, that is, to execute S410c. In this case, after the UE is configured according to the first RRC reconfiguration message, it still resides in the first cell, so the UE will send RRC Reconfiguration Complete to the first cell, that is, to execute S410d. The call currently being conducted by the UE will continue in the first cell.

[0243] Continue to see Figure 6 Exemplarily, after the verification of the first RRC reconfiguration message fails, the UE may execute S404 to determine whether the abnormal configuration item is a configuration item (updatable configuration item) in the preset configuration item list.

[0244] Exemplarily, if the abnormal configuration items (all) are preset updatable configuration items, the UE can further detect whether the compatible function is turned on, that is, execute S405. Correspondingly, if the compatible function is turned on, S409 can be executed. On the contrary, if the compatible function is not turned on, in this case, the UE can be set to execute the existing RLF process and reselect the process of the resident cell in accordance with the existing standard protocol. This embodiment takes the resident cell as an example, that is, when the compatible function is not turned on, the UE executes S406 to S408 as an example. For the specific implementation process of S406 to S408, please refer to S113 to S115, or S314 to S316 in the above embodiment, which will not be repeated here.

[0245] In actual applications, when the compatibility function is not enabled, the UE may also camp on the new cell, that is, execute S213 to S220 in the above embodiment, which will not be described in detail here.

[0246] It should be noted that the configuration carried by the first RRC reconfiguration message may be for the first cell or may indicate switching to the second cell (taking Cell C as an example). Therefore, in S409, the UE may perform different operations according to the different cells targeted by the first RRC reconfiguration message, as described in detail below.

[0247] Continue to see Figure 6 , exemplarily, when the first RRC reconfiguration message carries the configuration for the first cell (such as the RRC reconfiguration message 3 in the above embodiment), the UE can update the abnormal configuration item to the corresponding configuration in the first RRC reconfiguration message according to the above-mentioned method 1, that is, execute S409a. Specifically, if the first RRC reconfiguration message carries the second configuration item about the first cell (the second configuration item can also be understood as the first configuration item corresponding to the first configuration item stored in the UE, and the two have the same name but different corresponding values), before receiving the first RRC reconfiguration message, the terminal device stores the first configuration item, and the first configuration item and the second configuration item have the same parameters but different parameter values, and then the UE will find that the first configuration item is abnormal in the process of verifying the first RRC reconfiguration message (it can be understood that the configuration corresponding to the parameter is abnormal). In this case, after the UE updates the value of the first configuration item according to the first RRC reconfiguration message, it still resides in the first cell, so the UE will send an RRCReconfiguration complete message to the first cell, that is, execute S409b. The call currently being conducted by the UE will continue in the first cell.

[0248] Exemplarily, for the scenario where the abnormal configuration items are updated by adopting mode 2, for example, when the UE switches from the above-mentioned Cell A to Cell B, it is configured according to the configuration of Cell B sent by Cell A. After residing in Cell B, Cell B modifies these already configured configurations and carries them in the first RRC reconfiguration message to send to the UE, which leads to the problem that some configuration items configured for Cell B in the UE are incompatible with the configuration carried in the first RRC reconfiguration message. In this case, the UE actually has to operate according to the configuration in the most recently received RRC reconfiguration message. Therefore, it is necessary to update the abnormal configuration items to the configuration in the most recently received RRC reconfiguration message.

[0249] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0250] Continue to see Figure 6 , exemplarily, when the first RRC reconfiguration message indicates switching to the second cell, the operation to be performed by the UE is to disable the configuration item with the abnormality, such as updating the configuration item with the abnormality by adopting the aforementioned method 1, so that the first RRC reconfiguration message verification succeeds, and then resides in the second cell according to the first RRC reconfiguration message, that is, executing S409c. Correspondingly, after the UE resides in the second cell, it will send RRC Reconfiguration Complete to the second cell, that is, executing S409d. The call currently being conducted by the UE will continue in the second cell.

[0251] Exemplarily, taking the configuration item with an abnormality as the configuration item of the SRS resource of the antenna switching mode mentioned above as an example, in S409c, the UE can update the configuration item srs_tx_switch=1 of the SRS resource of the antenna switching mode to srs_tx_switch=0, so that the configuration of the SRS resource of the antenna switching mode can be invalid (it can also be understood as removing the configuration of the SRS resource of the antenna switching mode), and then the UE can verify the success of the first RRC reconfiguration message. It can be understood that when srs_tx_switch=1, the UE initially verifies that there is an abnormality in the check item when verifying the first RRC reconfiguration message (that is, the configuration item does not match Cell C), and the UE can make the configuration item invalid by modifying the value of the configuration item, so that the first RRC reconfiguration message can be finally verified successfully by the UE.

[0252] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0253] In addition, it should be noted that, based on the method for calling provided by the present application, determining whether the abnormal configuration item is a preset updatable configuration item, and when it is determined that all the abnormal configuration items are updatable configuration items, the operation of detecting whether the compatible function is turned on can occur when the UE receives any RRC reconfiguration message. The above description is only an example listed for a better understanding of the technical solution of this embodiment, and is not the only limitation to this embodiment.

[0254] In addition, it should be understood that the above description of the method for making a call provided in the embodiment of the present application only takes the 5G network as an example, and the method is also applicable to the 4G network. Moreover, with the subsequent development of communication technology, in the future next generation communication technology, such as 6G, if these networks can implement RRC reconfiguration based on the existing standard protocol, the method for making a call provided in the embodiment of the present application is also applicable.

[0255] In addition, it should be understood that in order to implement the above functions, the terminal device includes hardware and / or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of this application.

[0256] In order to better understand the technical solution provided in the embodiments of the present application, taking a mobile phone as an example, based on the relationship between the software structure and hardware of the mobile phone, the functional modules, hardware, and the interaction between the functional modules and hardware involved in implementing the method for making calls provided in the embodiments of the present application are explained.

[0257] Before explaining the software structure of the mobile phone, the architecture that can be adopted by the software system of the mobile phone is first explained.

[0258] Specifically, in actual applications, the software system of a mobile phone can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture.

[0259] In addition, it is understandable that the software systems used by the current mainstream terminal devices include but are not limited to Windows systems, Android systems, and iOS systems. For the sake of convenience, the embodiment of the present application takes the layered architecture Android system as an example to illustrate the software structure of the mobile phone. The subsequent technical solution for making calls provided in the embodiment of the present application is also applicable to other systems in specific implementation.

[0260] In addition, it should be understood that the current layered architecture of mobile phones divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. These layers may include, for example, an application layer, an application framework layer, an Android runtime and a system library, a hardware abstraction layer, a kernel layer, etc. The following is only an example of the layer where the functional modules involved in the method for making a call provided in the embodiment of the present application are located.

[0261] See also Figure 7 , is a schematic diagram of the software structure and related hardware of the mobile phone of the embodiment of the present application. Figure 7 In the diagram, from top to bottom, they are the application layer, application framework layer, kernel layer, and hardware.

[0262] The application layer may include a series of application packages. The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. In some implementations, these programming interfaces and programming frameworks may be described as functions.

[0263] Continue to see Figure 7 Specifically, in the technical solution provided in the embodiment of the present application, the application layer may include phone applications, setting applications, compatible function activation applications, etc.

[0264] Among them, the telephone application allows users to initiate call service operations.

[0265] Accordingly, the mobile phone responds to the operation behavior based on Figure 1 The mobile communication architecture shown in the figure establishes a media session with the called party. Regarding the establishment of the media session, please refer to the above terminal A and terminal B. Figure 1 The description part of establishing a media session in the mobile communication architecture shown is not repeated here.

[0266] Among them, the compatible function activation application can provide an entry to activate the compatible function.

[0267] Exemplarily, in the case where the compatible function mentioned in the above embodiment can be turned on by the user, the user can turn on the compatible function through the entrance provided by the compatible function turning on application specifically used to turn on the compatible function, so that when the configuration items that can be updated in the above embodiment appear, the mobile phone can use the user call method provided in the embodiment of the present application to update these configuration items, thereby completing the RRC reconfiguration, that is, switching from the currently connected 5G base station to the target base station.

[0268] Among them, the settings application can also provide an entry to enable compatible functions.

[0269] For example, in the above embodiment, when the compatible function can be enabled by the user, the entry for enabling the compatible function can be integrated into the setting application. In this way, the user does not need to install the compatible function enabling application separately in the mobile phone, and can enable the compatible function through the entry provided by the setting application.

[0270] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0271] Continue to see Figure 7 Specifically, in the technical solution provided in the embodiment of the present application, the application framework layer may include telephone / IMS services, camera services, CS Phone, PS Phone, etc.

[0272] The telephone / IMS service is used to call the SIP module in the modem to make various SIP request messages, such as INVITE, ACK, 200OK, etc., when establishing a media session and after the media session is established, that is, during a call.

[0273] Among them, the camera service is used to call camera-related devices and functional modules when the user initiates a video call, such as calling the camera driver, which in turn enables the camera driver to drive the camera to work, and calling the functional module that processes the video stream collected by the camera.

[0274] Among them, CS Phone is used for calls in CS (Circuit Switched) network. When IMS service is unavailable (the mobile phone is stationed in 2G / 3G or IMS registration is unsuccessful), calls can be made through CS calls. It can also be used for domain change and redialing when IMS call fails (commonly known as CS redial).

[0275] Among them, PS Phone is used for calls in PS (Packet Switched) network. When IMS service is available, IMS calls (VOLTE, VONR) can be made through the PS domain.

[0276] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0277] In addition, it can be understood that the kernel layer in the Android system is a layer between hardware and software. Figure 7Specifically, in the technical solution provided in the embodiment of the present application, the kernel layer may include a transmission control protocol / Internet protocol stack (Transmission Control Protocol / Internet Protocol STACK, TCP / IP protocol stack).

[0278] TCP / IP refers to a protocol suite that enables information transmission between multiple networks. In practical applications, the TCP / IP STACK at the kernel layer mainly serves Internet access services and also provides services for video-related data processing during call services.

[0279] Continue to see Figure 7 Specifically, in the technical solution provided in the embodiments of the present application, the hardware involved may include a modem, an ADSP (digital signal processor), a camera, an antenna, a MIC (microphone), a receiver, a speaker, etc.

[0280] The antenna is used to receive content sent by the network side, such as the RRC connection configuration message, SIP request message, and SRS that needs to be sent in turn in the above embodiments.

[0281] The camera is used to collect video streams when the initiated call service is a video call.

[0282] Among them, MIC is used to collect the user's audio data during the call and transmit the collected audio data to ADSP.

[0283] Among them, the AFE (Audio Front-End) module, 3A module, and encoder in the ADSP process the audio data collected by the MIC in turn, and then hand it over to the RTP / RTCP module in the Modem for processing, and then after being processed by the TCP / UDP layer and the IP layer, it is handed over to the PDCP layer to use an open algorithm, such as the ROHC algorithm mentioned in the above embodiment for encryption.

[0284] It should be noted that the 3A module specifically refers to a functional module that integrates three audio algorithms: acoustic echo cancellation (AEC), active noise control (ANS), and automatic gain control (AGC).

[0285] Among them, the data packets encrypted by PDCP will be transmitted to the antenna through the RLC layer, MAC layer and PHY layer in sequence, and finally sent to the network side through the antenna.

[0286] Accordingly, the data packets received by the antenna from the network side will be transmitted to the PDCP layer for processing via the PHY layer, MAC layer, and RLC layer in sequence. For example, the data packets are decrypted based on the ROHC algorithm, and then the decrypted RTP packets / RTCP packets are processed by the IP layer and TCP / UDP layer, and then transmitted to the ADSP after being processed by the RTP / RTCP module. The ADSP processes the data provided by the RTP / RTCP module in sequence through the decoder, 3A module, and AFE module, and parses out the audio data that can be played, which is finally played by the receiver, speaker, or earphone.

[0287] In addition, it should be noted that the processing of various SIP signaling messages involved in the embodiments of the present application is implemented by the SIP module in the modem. The processing of various RRC messages involved in the embodiments of the present application, such as RRCReconfiguration, RRC Reconfiguration Complete, RRC Connection re-establishment, etc., is implemented by the RRC module in the modem.

[0288] This is the end of the introduction to the software structure of the mobile phone. It is understandable that, Figure 7 The layers in the software structure shown and the components contained in each layer do not constitute a specific limitation on the mobile phone. In other embodiments of the present application, the mobile phone may include more or fewer layers than shown in the figure, and each layer may include more or fewer components, which is not limited by the present application.

[0289] In order to better understand the technical solution provided in the embodiments of the present application, still taking the terminal device as a mobile phone as an example, see Figure 8 , the specific structure of the mobile phone and the devices involved in implementing the embodiments of the present application are specifically described.

[0290] See also Figure 8 The mobile phone 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 button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

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

[0292] Specifically in each embodiment of the present application, the base station, such as the gNB mentioned in the above embodiments, sends messages to the mobile phone 100, which is a UE, such as the RRC reconfiguration message corresponding to the current cell, the RRC connection configuration message corresponding to the cell to be switched to, and the SIP signaling messages sent by the gNB to the UE during the multimedia session, etc., which can be implemented through antenna 1 or antenna 2.

[0293] Correspondingly, messages sent by mobile phone 100 to gNB, such as RRC Reconfiguration Complete, RRCConnection Reestablishment, and SIP signaling messages sent by UE to gNB involved in the multimedia session, are also implemented through antenna 1 or antenna 2.

[0294] Among them, the mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied on the mobile phone 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The wireless communication module 160 can provide solutions for wireless communications including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. applied on the mobile phone 100.

[0295] For example, in some implementations, the antenna 1 of the mobile phone 100 may be coupled to the mobile communication module 150, and the antenna 2 may be coupled to the wireless communication module 160. Thus, the mobile phone 100 may communicate with the network and other devices through mobile communication technology or wireless communication technology.

[0296] Continue to see Figure 8For example, the audio module 170 of the mobile phone 100 may include a speaker 170A, a receiver 170B, a microphone 170C, an earphone jack 170D, and the like.

[0297] Exemplarily, the mobile phone 100 can implement audio functions such as music playback, recording, and the voice call services described in the various embodiments of the present application through the speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor in the audio module 170.

[0298] In addition, regarding the sensor module 180 in the mobile phone 100, in some implementations, it may include: pressure sensor, gyroscope sensor, air pressure sensor, magnetic sensor, acceleration sensor, distance sensor, proximity light sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, bone conduction sensor, etc., which are not listed here one by one and this application does not impose any restrictions on this.

[0299] In addition, it should be noted that, in some implementations, the processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc.

[0300] It is understandable that, in a specific implementation, different processing units may be independent devices or may be integrated into one or more processors.

[0301] It should be noted that, in practical applications, the mobile phone 100 can implement the technical solutions provided by the embodiments of the present application through the two processing units AP110A and Modem110B. For example, the AP can respond to the call request initiated by the user and then call the Figure 7 The services related to the call service in the application framework layer shown in the figure, and the corresponding driver in the kernel layer, hand over the call request to the modem. The modem can interact with the network side according to the processing logic involved in the method for calling provided in each embodiment of the present application. For specific implementation details, please refer to the above embodiments, which will not be repeated here.

[0302] In addition, it is also understandable that the processing unit, the controller, included in the processor 110 can be the nerve center and command center of the mobile phone 100. In practical applications, the controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0303] In addition, the memory in the processor 110 is mainly used to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory.

[0304] In addition, regarding Figure 8 The USB interface 130 shown in the figure is an interface that complies with USB standard specifications, and may specifically be a MiniUSB interface, a Micro USB interface, a USB Type C interface, etc.

[0305] The charging management module 140 is used to receive charging input from the charger. Figure 8 The power management module 141 shown in the figure 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 charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160. The wireless communication function of the mobile phone 100 can be realized through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0306] also, Figure 8 The mobile phone 100 shown in the figure implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or change display information.

[0307] The display screen 194 is specifically used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the mobile phone 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0308] In addition, the mobile phone 100 can realize the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194 and the application processor, etc. Among them, the camera 193 is used to capture static images or videos. In some embodiments, the mobile phone 100 can include 1 or N cameras 193, where N is a positive integer greater than 1.

[0309] For example, if the initiated call service is a video call service, such as a video call, a video conference, etc., in the process of implementing the call service, in addition to the audio module 170, the camera 193 also needs to be involved.

[0310] also, Figure 8 The external memory interface 120 shown in the figure can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos are stored in the external memory card.

[0311] also, Figure 8 The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the mobile phone 100 by running the instructions stored in the internal memory 121.

[0312] Specifically, the file recording the updateable configuration items mentioned in the above embodiment can be pre-configured into the internal memory 121 in the mobile phone 100 when the mobile phone 100 leaves the factory.

[0313] also, Figure 8 The motor 191 shown in the figure may be, for example, a vibration motor; the indicator 192 may be an indicator light.

[0314] also, Figure 8 The SIM card interface 195 shown in the figure can be used to connect a SIM card or a USIM card. The SIM card can be connected to or separated from the mobile phone 100 by inserting into or pulling out from the SIM card interface 195. The mobile phone 100 can support 1 or N (N is an integer greater than 1) SIM card interfaces 195. That is, multiple SIM cards or USIM cards can be inserted into the terminal.

[0315] The hardware structure of the mobile phone 100 is introduced here. It should be understood that: Figure 8 The illustrated mobile phone 100 is merely an example, and in a specific implementation, the mobile phone 100 may have more or fewer components than those shown in the figure, may combine two or more components, or may have a different component configuration. Figure 8 The various components shown in the EMBODIMENTS 2000 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.

[0316] In addition, it should be noted that the method for making a call provided by the above-mentioned embodiments implemented by the terminal device in the actual application scenario can also be performed by a chip system included in the terminal device. Based on this, an embodiment of the present application also provides a chip system, which may include a processor. The chip system can be coupled to a memory so that the processor in the chip system calls the computer program stored in the memory when it runs to implement the steps performed by the above-mentioned terminal device. Among them, the processor in the chip system can be an application processor (AP) or a non-application processor, such as a modem.

[0317] In addition, an embodiment of the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a terminal device, the terminal device executes the above-mentioned related method steps to implement the method for making calls in the above-mentioned embodiment.

[0318] In addition, an embodiment of the present application further provides a computer program product. When the computer program product is run on a terminal device, the terminal device executes the above-mentioned related steps to implement the method for making calls in the above-mentioned embodiment.

[0319] In addition, it can be seen from the above description that the terminal device, computer-readable storage medium, computer program product or chip provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0320] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for making a call, characterized in that: Applied to a terminal device, the method comprises: During a call in a first cell, a first RRC reconfiguration message sent by a base station corresponding to the first cell is received; wherein before receiving the first RRC reconfiguration message, a first configuration item is stored in the terminal device; the first configuration item includes a first parameter and a first value corresponding to the first parameter; Verifying the first RRC reconfiguration message and the first configuration item; wherein the first RRC reconfiguration message includes first information, and the first information includes information of the first cell or information of the second cell; the verifying the first RRC reconfiguration message and the first configuration item includes verifying the first information, the first parameter, and a first value corresponding to the first parameter; During the process of verifying the first RRC reconfiguration message and the first configuration item, when there is an abnormality in the value corresponding to the first parameter, the first parameter is a ignorable parameter and the terminal device supports a compatible function, the abnormal value corresponding to the first parameter is ignored, so that the first RRC reconfiguration message is verified successfully; wherein, the value corresponding to the first parameter includes the first value, the terminal device supports the compatible function, indicating that the terminal device supports ignoring abnormal values ​​corresponding to ignorable parameters, and the first parameter being a ignorable parameter indicates that the parameter value corresponding to the first parameter can be ignored.

2. The method according to claim 1, characterized in that The method further comprises: During the process of verifying the first RRC reconfiguration message and the first configuration item, if there is an abnormality in the value corresponding to the first parameter, and the first parameter is an ignorable parameter but the terminal device does not support ignoring the abnormal value corresponding to the ignorable parameter, an RRC connection re-establishment message is replied to the base station corresponding to the first cell.

3. The method according to claim 1, characterized in that The ignoring the abnormal value corresponding to the first parameter includes: Update the value corresponding to the first parameter.

4. The method according to claim 1, characterized in that: The value corresponding to the first parameter also includes a second value; the first RRC reconfiguration message carries a second configuration item about the first cell, and the second configuration item includes the first parameter and the second value corresponding to the first parameter; The ignoring the abnormal value corresponding to the first parameter includes: When the first value and the second value are different, the first value corresponding to the first parameter is ignored.

5. The method according to claim 4, characterized in that The ignoring the first value corresponding to the first parameter includes: The first value corresponding to the first parameter is updated to the second value.

6. The method according to claim 1, characterized in that The first RRC reconfiguration message is used to instruct the terminal device to switch from the first cell to the second cell; The ignoring the abnormal value corresponding to the first parameter includes: When the value corresponding to the first parameter is incompatible with the information of the second cell, the abnormal value corresponding to the first parameter is ignored.

7. The method according to claim 6, characterized in that The ignoring the abnormal value corresponding to the first parameter includes: The first value corresponding to the first parameter is updated to a third value.

8. The method according to claim 7, characterized in that The first value is 1, and the third value is 0.

9. The method according to any one of claims 1 to 8, characterized in that: The first cell is a cell of a TDD system, and the second cell is a cell of an FDD system.

10. The method according to any one of claims 1 to 8, characterized in that: The first configuration item is a configuration item of an SRS resource of an antenna switching mode.

11. The method according to any one of claims 1 to 8, characterized in that: The first parameter is a negligible parameter, including: The first parameter is the same as any parameter in a parameter list stored in the terminal device, the parameter list includes at least one parameter, and a parameter value corresponding to each of the at least one parameter can be ignored.

12. The method according to any one of claims 1 to 8, characterized in that: The first configuration item is the configuration received by the cell where the terminal device resides before residing in the first cell.

13. A terminal device, characterized in that: The terminal device comprises: a memory and a processor, wherein the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the terminal device executes the method for making calls as described in any one of claims 1 to 12.

14. A chip system, characterized in that: The chip system includes a processor, and the processor is used to support the terminal device to implement the method for making calls as described in any one of claims 1 to 12.

15. The chip system according to claim 14, characterized in that: The processor includes a modem.

16. A computer-readable storage medium, characterized in that: The method comprises a computer program, which, when executed on a terminal device, enables the terminal device to execute the method for making a call as claimed in any one of claims 1 to 12.

Images