Conversation method and device, chip system and storage medium

Abstract

The invention provides a call method and device, a chip system and a storage medium. The method is applied to the terminal equipment, first information in a first RRC reconfiguration message currently received from a first cell, a first parameter in a locally stored first configuration item and a value corresponding to the first parameter are verified, and when the value corresponding to the first parameter is abnormal, an abnormal value corresponding to the first parameter is ignored, so that the first RRC reconfiguration message is reconfigured. Therefore, the first RRC reconfiguration message is verified successfully, thereby ensuring that the terminal device can complete RRC reconfiguration, and reducing the probability of RRC reconfiguration failure.

Description

Method, device, chip system and storage medium for call

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on April 5, 2023, with application number 202310392810.5 and invention name “A method and device for calls”, and the Chinese patent application filed with the China Patent Office on April 28, 2023, with application number 202310491058.X and invention name “Method, device, chip system and storage medium for calls”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] 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

[0003] In 5G, or NR (New Radio) networks, an RRC reconfiguration (Radio Resource Control Reconfiguration) initiated by the network (referring to a 5G base station, such as the next Generation Node B (gNB)) to the terminal device (also known as: UE) aims to modify the RRC connection already established between the UE and the network to better adapt to actual service scenarios.

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

[0005] Summary of the Invention

[0006] 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.

[0007] In a 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 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; wherein the value corresponding to the first parameter includes the first value.

[0008] The first cell is the 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.

[0009] The RRC reconfiguration message is the RRC Reconfiguration message sent to the UE by the base station corresponding to the cell as mentioned below. Specifically in this 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 RRC reconfiguration message 4 mentioned below.

[0010] The first configuration item is a configuration item stored locally on the terminal device, and may include the first parameter and the value corresponding to the first parameter. In this embodiment, the value corresponding to the first parameter stored on 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, third value, etc. described below.

[0011] 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.

[0012] 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 verified successfully, thereby ensuring that the terminal device can complete the RRC reconfiguration and reducing the probability of RRC reconfiguration failure.

[0013] Ignoring the abnormal value corresponding to the first parameter may mean not considering 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 mean updating the value corresponding to the first parameter so that the abnormal value corresponding to the first parameter is corrected or deleted or becomes 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 verification of the first RRC reconfiguration message to fail, thereby causing a call abnormality.

[0014] 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 can be updated according to method 1 or method 2 described in the following embodiments.

[0015] For example, in some implementations, 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 resides, i.e., updating the configuration item. Below, the representation of updating the configuration item is used as an example for explanation.

[0016] It should be noted that in actual applications, updating these configuration items according to Method 1 or Method 2 can be understood as updating the configuration of these configuration items, or updating the values ​​of these configuration items, or updating the content of these configuration items. This application uses the example of updating the values ​​corresponding to the abnormal parameters in these configuration items to illustrate.

[0017] 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 feeding back an RRC reconfiguration completion message after the RRC reconfiguration is completed.

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

[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 value corresponding to the first parameter.

[0020] According to the first aspect, or any implementation method of the above first aspect, 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.

[0021] 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.

[0022] 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 configuration item can be updated using the method 2 described below. 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.

[0023] According to the first aspect, or any implementation method of the above first aspect, 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.

[0024] 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.

[0025] That is, for the case where the first RRC reconfiguration message instructs the terminal device to switch 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 and conduct normal calls in the second cell.

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

[0027] 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.

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

[0029] Exemplarily, when the first configuration item is a configuration item of an SRS resource in 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".

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

[0031] For example, when the first configuration item is a configuration item for SRS resources in an antenna switching mode, the first parameter is, for example, srs_tx_switch (hereinafter referred to as "srs_tx_switch"), 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 (hereinafter referred to as "srs_tx_switch = 0").

[0032] 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 the 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.

[0033] The parameter list stored in the terminal device and the configuration item list mentioned below are the same list. In the following embodiments, the updateable configuration items recorded in the configuration item list are the parameters that can be ignored.

[0034] 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, thereby enabling the terminal device to perform RRC reconfiguration between various cells.

[0035] 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.

[0036] The terminal device supports the compatibility function, for example, the UE has enabled the compatibility function as described below. Regarding determining whether the terminal device supports the compatibility function, please refer to the description of S313 or S405 below, which will not be repeated here. S313 or S405 may be optional steps. In this case, the terminal device may support the compatibility function by default.

[0037] 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.

[0038] The RRC connection re-establishment message is, for example, the RRC Connection re-establishment mentioned below.

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

[0040] 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.

[0041] 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.

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

[0043] Accordingly, when the cell previously camped on by 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, such as RRC reconfiguration message 1 or RRC reconfiguration message 2 mentioned below.

[0044] According to the first aspect, or any implementation of the first aspect above, when the first information is information about the first cell, performing RRC reconfiguration according to the first RRC reconfiguration message, and feeding back an RRC reconfiguration complete message after the RRC reconfiguration is completed, includes: performing RRC reconfiguration according to the first RRC reconfiguration message, and feeding back an RRC reconfiguration complete message to a base station corresponding to the first cell after the RRC reconfiguration is completed. For details, see S409a and S409b in the following embodiments.

[0045] According to the first aspect, or any implementation of the first aspect above, it is characterized in that when the first RRC reconfiguration message instructs the terminal device to switch 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.

[0046] 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, and the first cell is Cell B, the second cell can be either Cell A or Cell C. To facilitate explanation of the method for making a call provided in the present application, the following takes Cell C as the second cell as an example.

[0047] Specifically in the present application, in a scenario where the second cell is Cell C, the first RRC reconfiguration message referred to herein 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.

[0048] 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; and during the verification of the first RRC reconfiguration message, when a parameter has an abnormal parameter value, ignoring the abnormal parameter value corresponding to the parameter, so that the first RRC reconfiguration message is successfully verified.

[0049] The first cell is the 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.

[0050] The RRC reconfiguration message is referred to below as RRC Reconfiguration sent by the base station corresponding to the cell to the UE.

[0051] Among them, the verification of the first RRC reconfiguration message may, for example, include verification of the content of 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.

[0052] 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.

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

[0054] According to the second aspect, or any implementation method of the above second aspect, 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.

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

[0056] 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, thereby enabling the terminal device to perform RRC reconfiguration between various cells.

[0057] According to the second aspect, or any implementation method of the above second aspect, 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 supports the compatible function, indicating that the terminal device supports ignoring the abnormal value corresponding to the ignorable parameter.

[0058] The terminal device supports the compatibility function, for example, the UE has enabled the compatibility function as described below. Regarding determining whether the terminal device supports the compatibility function, please refer to the description of S313 or S405 below, which will not be repeated here. S313 or S405 may be optional steps. In this case, the terminal device may support the compatibility function by default.

[0059] 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.

[0060] The RRC connection re-establishment message is, for example, the RRC Connection re-establishment mentioned below.

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

[0062] 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.

[0063] 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 being coupled; the memory storing program instructions, which, when executed by the processor, cause the terminal device to execute the instructions of the method in the first aspect or any possible implementation of the first aspect.

[0064] The third aspect and any implementation of the third aspect respectively correspond to the first aspect and any implementation of the first aspect; or respectively correspond to the second aspect and any implementation of the second aspect. The technical effects corresponding to the third aspect and any implementation of the third 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, and are not further described here.

[0065] 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.

[0066] The fourth aspect and any implementation thereof respectively correspond to the first aspect and any implementation thereof; or respectively correspond to the second aspect and any implementation thereof. The technical effects corresponding to the fourth aspect and any implementation thereof may refer to the technical effects corresponding to the first aspect and any implementation thereof, or the technical effects corresponding to the second aspect and any implementation thereof, and are not further elaborated here.

[0067] 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.

[0068] The fifth aspect and any implementation of the fifth aspect respectively correspond to the first aspect and any implementation of the first aspect; or respectively correspond to the second aspect and any implementation of the second aspect. 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, and are not further described here.

[0069] In a sixth aspect, the present application provides a chip system, the chip system including a processor, wherein the processor is configured to support a terminal device in implementing instructions of the method in the first aspect or any possible implementation of the first aspect.

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

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

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

[0073] The sixth aspect and any implementation of the sixth aspect respectively correspond to the first aspect and any implementation of the first aspect; or respectively correspond to the second aspect and any implementation of the second aspect. 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, and are not further described here. BRIEF DESCRIPTION OF THE DRAWINGS

[0074] FIG1 is a schematic diagram illustrating an exemplary mobile communication architecture;

[0075] FIG2 a is a schematic diagram illustrating interaction between the UE and the network side when RRC reconfiguration is successful;

[0076] FIG2 b is a schematic diagram illustrating interaction between the UE and the network side when RRC reconfiguration fails;

[0077] FIG3 is a schematic diagram illustrating an exemplary case of cell handover failure in an RRC reconfiguration process;

[0078] FIG4 is a schematic diagram illustrating another exemplary RRC reconfiguration process in which a cell handover fails;

[0079] FIG5 is a schematic diagram illustrating an exemplary method for implementing RRC reconfiguration based on a call method provided in an embodiment of the present application;

[0080] FIG6 is a schematic diagram illustrating another exemplary method for implementing RRC reconfiguration based on an embodiment of the present application;

[0081] FIG7 is a schematic diagram showing an exemplary software structure and hardware of a terminal device;

[0082] FIG8 is a schematic diagram showing an exemplary hardware structure of a terminal device. DETAILED DESCRIPTION

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

[0084] The term "and / or" in this article is merely a description of the association relationship between 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.

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

[0086] In the embodiments of this 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 this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0087] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

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

[0089] Specifically, the technical solution provided by the embodiment of the present application is the processing logic performed when performing the RRC reconfiguration process during a call between a calling party and a 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 with reference to the accompanying drawings.

[0090] 1 , a mobile communication architecture is shown, which includes terminal equipment, a (wireless) access network, a core network, and an IP Multimedia Subsystem (IMS) network required to implement voice / audio / video call services.

[0091] Continuing to refer to Figure 1, illustratively, the terminal device 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.

[0092] 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 facing the same operator and terminal A and terminal B access the same cell.

[0093] 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 for different operators. Alternatively, terminal A and terminal B are for the same operator, but terminal A is located in one city or cell, and terminal B is located in another city or cell.

[0094] For example, in a scenario where base station A and base station B are the same, computer room A and computer room B can be the same or two different computer rooms.

[0095] 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 on this embodiment.

[0096] Based on the mobile communications architecture shown in Figure 1, when terminal A initiates a call to terminal B, a media session is established between the two. During the call process described in the following embodiments and figures, terminal A sends a SIP request message to the called party's IMS domain via base station A, computer room A, and the calling party's IMS domain. The message is then sent to terminal B via the called party's IMS domain, computer room B, and base station B. Accordingly, the SIP response message generated by terminal B in response to the SIP request message initiated by terminal A is fed back to terminal A via base station B, computer room B, the called party's IMS domain, the calling party's IMS domain, computer room A, and base station A. This establishes a media session between terminals A and B.

[0097] It's important to note that SIP stands for Session Initialization Protocol. SIP is a multimedia communication protocol developed by the Internet Engineering Task Force (IETF). It's a text-based application-layer control protocol used to create, modify, and release sessions between one or more participants.

[0098] For example, 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, 183SessionProgress, 180Ringing, etc.

[0099] It's also worth noting that when either terminal A or terminal B initiates a call hang-up, the resulting SIP request message (e.g., BYE) is also transmitted through the terminal initiating the BYE, such as the base station, computer room, and IMS domain corresponding to terminal A, to the IMS domain, computer room, and base station corresponding to terminal B, ultimately reaching terminal B. Accordingly, upon receiving the BYE message from terminal A, terminal B generates a 200OK SIP response message, which is then sent to terminal A via base station B, computer room B, the called party's IMS domain, the calling party's IMS domain, computer room A, and base station A. At this point, the media session between terminals A and B is terminated.

[0100] It should be understood that the above description is merely an example to facilitate a better understanding of the technical solution of this embodiment and is not intended to be the sole limitation of this embodiment. The specific processes involved in establishing and terminating a media session between Terminal A and Terminal B, as well as the meanings of the various SIP request and response messages involved, can be found in existing protocol standards and will not be further elaborated here.

[0101] In addition, it should be understood that the normal progress of a 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, such as 5G networks, in order to ensure that the wireless network resources can better adapt to the actual business scenarios during the call, RRC reconfiguration has been introduced to modify the RRC connection between the UE and the base station. For example, establishing / modifying / releasing RB (Resource Block), performing cell switching (base station switching), setting / modifying / releasing measurement reports, etc.

[0102] 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 using RRC reconfiguration performed in a 5G network as an example.

[0103] Specifically, in a 5G network, RRC reconfiguration is initiated by the network side (5G base station). That is, the base station proactively sends an RRC reconfiguration message to the corresponding UE, as shown in "RRC Reconfiguration" in Figure 2a.

[0104] For example, the RRC reconfiguration message may carry measurement configurations that instruct the UE to perform measurement operations, configurations of SRS resources for antenna switching modes, configurations of encryption and decryption algorithms used for data packets exchanged with the base station, etc. These are not listed here one by one, 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 messages carrying different configurations, please refer to the existing standard protocols and will not be repeated here.

[0105] 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 feed back 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 "RRC Reconfiguration Complete" shown in Figure 2a. 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 provisions, the UE will execute the RLF (Radio Link Failure, RLF) process, such as releasing the connection with the 5G base station of the current cell, and reselecting the cell, and then performing the RRC connection re-establishment process with the reselected 5G base station, as shown in the "RRC Connection re-establishment" in Figure 2b. 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 the current RRC connection to be abnormal after implementing RRC Connection re-establishment with the UE. Based on the existing standard protocol provisions, the 5G base station will send a BYE message to the UE to end the current call, thereby hanging up the current call.

[0106] 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.

[0107] However, in actual application scenarios, it has been found that 5G base stations in some areas do not fully comply with existing standard protocols when generating RRC reconfiguration messages. This can cause handover failures when UEs perform cell handovers based on RRC reconfiguration messages, leading to call interruptions.

[0108] For better understanding, two specific situations leading to RRC reconfiguration failure are described below with reference to FIG3 and FIG4 .

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

[0110] 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 locally stored 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 already stored locally, and then verify all the obtained contents, such as checking whether these contents match or are compatible. For the sake of convenience of description, the present application directly expresses in the drawings and embodiments as verifying the RRC reconfiguration message.

[0111] Referring to 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.

[0112] Continuing to refer to Figure 3, for example, in the scenario shown in Figure 3, the frequency band corresponding to Cell B is the time division duplexing (TDD) mode, such as the n78 cell with a frequency within 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 within the n1 frequency range.

[0113] Continuing to refer to FIG. 3 , illustratively, 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, core network, and base station corresponding to the called party, that is, while the UE is making a call in Cell A ( S101 ), Cell A may perform an RRC Reconfiguration process ( S102 ) with the UE.

[0114] Continuing to refer to FIG. 3 , illustratively, the RRC Reconfiguration process in S102 may include S102a, S102b, and S102c.

[0115] Exemplarily, S102a is a step in which a base station in Cell A (hereinafter referred to as a cell) sends an RRC reconfiguration message to a 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).

[0116] Exemplarily, S102b is a step in which the UE verifies the content of the RRC reconfiguration message 1. Specifically, the UE verifies whether the information (cells) configured for Cell A in the RRC reconfiguration message 1 are reasonable based on existing standard protocols and attributes of Cell A.

[0117] For example, if the UE successfully verifies RRC reconfiguration message 1, that is, there are no abnormal information elements (or configuration items) in RRC reconfiguration message 1, the UE will perform RRC reconfiguration according to RRC reconfiguration message 1. After completing the RRC reconfiguration, the UE executes S102c. That is, it sends RRC Reconfiguration Complete to Cell A, informing Cell A that the RRC reconfiguration for RRC reconfiguration message 1 is complete.

[0118] For example, if the UE fails to verify RRC reconfiguration message 1, the UE executes RLF, releases the connection with Cell A, and then reselects a cell to camp on. When reselecting a cell to camp on, the UE can select the original cell (i.e., the currently connected cell) or a new cell. The specific processing performed after the verification failure, such as S113 to S115, is not described in detail here.

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

[0120] Continuing to refer to FIG. 3 , illustratively, 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 reporting operation.

[0121] Understandably, RRC reconfiguration is intended to ensure that wireless network resources can better adapt to actual service scenarios during a 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 that triggers the UE to perform an A3 event (the measurement configuration carried in subsequent other RRC reconfiguration messages is used as an example to trigger the UE to perform an A3 event).

[0122] Based on this, the UE will execute S103 according to the measurement configuration, that is, when the UE moves from Cell A to Cell B, when the signal of Cell A gradually weakens and the signal of Cell B gradually strengthens, an A3 measurement report (A3MR) will be generated.

[0123] Continuing to refer to FIG. 3 , illustratively, after generating the A3MR, the UE sends the A3MR to Cell A, ie, executes S104 .

[0124] Continuing to refer to FIG. 3 , illustratively, after receiving the A3MR sent by the UE, Cell A sends an RRC reconfiguration message 2 to the UE to instruct the UE to switch to Cell B, ie, executes S105 .

[0125] It is understandable that the A3MR 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 Cell A 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 Cell B.

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

[0127] It is understandable that 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 of the RRC reconfiguration message 2.

[0128] For example, 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.

[0129] 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.

[0130] For example, if the UE fails to verify RRC reconfiguration message 2, the UE will perform an RLF procedure, such as releasing the connection with the current cell and then reselecting a cell to camp on. When reselecting a cell to camp on, the UE can also select the original cell to camp on or a new cell to camp on. The specific processing performed after the verification failure, such as S113 to S115, is not described in detail here.

[0131] For example, this embodiment takes the case where the UE verifies the content of the RRC reconfiguration message 2 successfully as an example, that is, after the UE receives the RRC reconfiguration message 2 sent by Cell A, it executes S106 as an example.

[0132] Since the result of S106 is that the UE successfully verifies the content of RRC reconfiguration message 2, the UE will also send RRC Reconfiguration Complete to Cell A after camping on Cell B, informing Cell A that the RRC reconfiguration (switching to Cell B) for RRC reconfiguration message 2 is completed, that is, execute S107.

[0133] Continuing to refer to FIG. 3 , illustratively, if the call is still ongoing between the UE and Cell B, Cell B performs an RRC Reconfiguration process with the UE ( S108 ).

[0134] Continuing to refer to FIG. 3 , illustratively, the RRC Reconfiguration process in S108 may include S108a, S108b, S108c, and S108d.

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

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

[0137] 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).

[0138] The configuration of SRS resources can support four modes: beam management, codebook, non-codebook, and antenna switching.

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

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

[0141] In non-codebook mode, the base station measures the SRS to obtain SRI, TPMI, and RI information, and feeds back the SRI to the UE. The PUSCH (Physical Uplink Shared CHannel) selects the same precoding matrix as the SRS (the precoding matrix for the SRS corresponding to the SRI may be selected from the CSI-RS (Channel State Information-Reference Signal) measurement).

[0142] 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 relatively few transmitting antennas, the UE needs to traverse all antennas through antenna switching (which can be understood as the UE transmitting SRS on multiple antennas in turn) to measure the uplink CSI. The base station then 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. Therefore, the FDD system does not support the configuration of SRS resources in antenna switching mode.

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

[0144] Exemplarily, S108b is a step in which the UE verifies the content of the RRC reconfiguration message 3. Specifically, the UE verifies whether the information (cells) configured for Cell B in the RRC reconfiguration message 3 are reasonable based on existing standard protocols and attributes of Cell B.

[0145] As can be seen from the above description, Cell B is a TDD system, which supports the configuration of SRS resources for antenna switching mode. Therefore, the configuration of SRS resources for antenna switching mode carried in RRC Reconfiguration Message 3 is reasonable. Therefore, the UE successfully verifies the content of RRC Reconfiguration Message 3. The UE performs RRC reconfiguration according to RRC Reconfiguration Message 3, for example, configuring SRS resources for antenna switching mode, that is, executing S108c.

[0146] 3 , illustratively, after completing the RRC reconfiguration according to RRC reconfiguration message 3, the UE will execute S108d, that is, send an RRC Reconfiguration Complete message to Cell B, informing Cell B that the RRC reconfiguration according to RRC reconfiguration message 3 has been completed.

[0147] Continuing to refer to FIG. 3 , illustratively, in some implementations, Cell B may further send an RRC reconfiguration message carrying measurement configuration to the UE.

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

[0149] 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.

[0150] For ease of explanation, this embodiment still uses successful verification as an example, meaning that the UE will perform measurement reporting according to the measurement configuration, i.e., execute S109. Specifically, in S109, as the UE moves from Cell B to Cell C, an A3 measurement report (A3MR) is generated when the signal of Cell B gradually weakens and the signal of Cell C gradually strengthens.

[0151] Continuing to refer to FIG. 3 , illustratively, after generating the A3MR, the UE sends the A3MR to Cell B, ie, executes S110 .

[0152] Continuing with Figure 3, illustratively, after Cell B receives the A3MR sent by the UE, it sends RRC Reconfiguration Message 4 to the UE, instructing the UE to switch to Cell C, thereby executing S111. In this embodiment, illustratively, the SRS resource configuration for the antenna switching mode is not removed from RRC Reconfiguration Message 4; that is, the SRS resource configuration for the antenna switching mode is retained. Upon receiving RRC Reconfiguration Message 4 sent by Cell B, the UE also verifies the contents of RRC Reconfiguration Message 4, thereby executing S112.

[0153] As can be seen from the above description, Cell C is an FDD system, which does not support the configuration of SRS resources for antenna switching mode. Therefore, according to existing standard protocols, Cell B should send an RRC reconfiguration message to the UE to remove the configuration of SRS resources for antenna switching mode before RRC reconfiguration message 4, instructing the UE to release the configured SRS resources for antenna switching mode. Alternatively, the information for removing the configuration of SRS resources for antenna switching mode can be directly included in RRC reconfiguration message 4.

[0154] However, in the scenario shown in Figure 3, when Cell B sends RRC reconfiguration message 4 to the UE, it does not include information for removing the configuration of SRS resources for the antenna switching mode. However, the UE configures SRS resources for the antenna switching mode in S108d. The UE's saved configuration of a parameter previously received from Cell B is not deleted by the network according to the protocol. When the UE applies the previously saved configuration of the parameter in Cell B to the Cell C to which it is switching, because Cell C does not support the parameter configuration, the parameter configuration in the UE will be incompatible or mismatched with Cell C, resulting in a failure in the RRC reconfiguration message verification. It should be understood that, in some practical scenarios, the terminal device will verify the information carried in the RRC reconfiguration message (or the content of the message) in combination with the configuration information already saved in the terminal device (the saved configuration information may be from 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 RRC reconfiguration message 4 (the message may include relevant information of Cell C), because Cell C does not support the configuration of the SRS resources of the antenna switching mode already saved in the terminal device, the UE's verification result for RRC reconfiguration message 4 is verification failure.

[0155] Continuing to refer to FIG. 3 , illustratively, 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 a cell, and then reside in the reselected cell.

[0156] Regarding the operation performed by the UE when the RRC reconfiguration message verification fails, reference may be made to existing standard protocols. 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 executes S113 as an example.

[0157] Continuing to refer to Figure 3, illustratively, if the UE chooses to reside in the original cell (i.e., Cell B where the UE resided before the handover), the UE will send an RRC connection re-establishment request (RRC Connection re-establishment Request) message carrying the cause value of the 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, executing S114.

[0158] 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.

[0159] 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 and will not be repeated here.

[0160] For example, 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, that is, 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. The reason field of the BYE message carries the fact that Cell B determined that the reason for the failure to switch from Cell B to Cell C was insufficient bearer resources (Insufficient Bearer Resource), and the corresponding error code is 503, that is, S115.

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

[0162] 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 on the n78 cell. 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 mode 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 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.

[0163] 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 SRS resource configuration of the antenna switching mode incompatible with Cell C mentioned above.

[0164] 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 on this embodiment.

[0165] 4 , for example, a scenario is taken where the UE selects a new cell to camp on when the RRC reconfiguration message verification fails.

[0166] Specifically in this embodiment, still taking the definition of Cell A, Cell B, and Cell C in the embodiment shown in FIG3 as an example, the specific implementation of S201 to S207 can be referred to S101 to S107 in the embodiment shown in FIG3 , and will not be repeated here. The following, in conjunction with S208 to S220 shown in FIG4 , describes the specific processing involved when the UE selects a new cell (e.g., Cell A, which is a new cell relative to Cell B to which the UE has just released its connection and Cell C to which it is attempting to switch) to camp when verification of RRC reconfiguration message 4 fails.

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

[0168] 4 , illustratively, the RRC Reconfiguration process in S208 may include S208a, S208b, S208c, and S208d.

[0169] 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 that carries the configuration of the SRS resources for the antenna switching mode and the configuration for starting the ROHC algorithm. It should be understood that in actual applications, the configuration of the SRS resources for the antenna switching mode and the configuration for starting the ROHC algorithm can be sent to the UE via the same RRC reconfiguration message or via different RRC reconfiguration messages, and this embodiment does not impose any limitation on this.

[0170] Exemplarily, S208b is a step in which the UE verifies the content of the RRC reconfiguration message 3. Specifically, the UE verifies whether the information (cells) configured for Cell B in the RRC reconfiguration message 3 are reasonable based on existing standard protocols and attributes of Cell B.

[0171] Understandably, both the base station and the UE are typically capable of using the ROHC algorithm (a recognized algorithm for ideal data header compression and decompression on wireless links). By default, the UE can be configured to disable the ROHC algorithm (i.e., the UE does not use the ROHC algorithm). Upon receiving an RRC reconfiguration message from the base station that carries a configuration to enable the ROHC algorithm, the UE activates the ROHC algorithm.

[0172] Furthermore, it should be understood that when the base station notifies the UE to enable the ROHC algorithm, it also enables the ROHC algorithm itself. In this way, when the UE resides in the cell where the base station is located, both can use the ROHC algorithm to compress sent data packets and decompress received data packets.

[0173] Furthermore, in this embodiment, Cell B is a TDD system, which supports the configuration of SRS resources for antenna switching mode. Therefore, the inclusion of the SRS resource configuration for antenna switching mode in RRC Reconfiguration Message 3 is reasonable, and the UE successfully verifies the contents of RRC Reconfiguration Message 3. The UE performs RRC reconfiguration based on RRC Reconfiguration Message 3, for example, configuring SRS resources for antenna switching mode, and initiates the ROHC algorithm, i.e., executing S208c.

[0174] 4 , illustratively, after completing the RRC reconfiguration according to RRC reconfiguration message 3, the UE will execute S208d, that is, send an RRC Reconfiguration Complete message to Cell B, informing Cell B that the RRC reconfiguration according to RRC reconfiguration message 3 has been completed.

[0175] Continuing to refer to FIG. 4 , illustratively, in some implementations, Cell B may further send an RRC reconfiguration message carrying measurement configuration to the UE.

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

[0177] 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.

[0178] For ease of description, 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 S209.

[0179] S209: 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 (A3MR) is generated.

[0180] S210: The UE sends an A3MR to Cell B.

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

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

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

[0184] Understandably, when Cell B sends RRC Reconfiguration Message 4 to the UE, it has already exchanged data with Cell C based on the A3MR reported by the UE in S210. Assuming that Cell C also has the ROHC algorithm enabled, RRC Reconfiguration Message 4 does not need to carry the configuration to disable the ROHC algorithm. Therefore, the UE does not disable the ROHC algorithm.

[0185] In addition, regarding the processing logic of the S212 verification process, please refer to S112 in the above embodiment and will not be repeated here.

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

[0187] For specific operations involved in performing RLF, please refer to existing standard protocols.

[0188] Continuing to refer to FIG. 4 , illustratively, if after executing the RLF process, the UE chooses to reside in a new cell (Cell A), the UE will send an RRC Connection re-establishment Request carrying a Reconfiguration failure to Cell A, thereby enabling Cell A and the UE to perform an RRC connection re-establishment process, i.e., executing S214 .

[0189] S214: RRC connection re-establishment process for residing in the new cell.

[0190] Specifically, because 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, informing Cell A that the RRC reconfiguration for RRC Reconfiguration Message 5 is complete. This establishes an RRC connection between the UE and Cell A.

[0191] Continuing with Figure 4 , illustratively, in S208c, after successfully verifying RRC Reconfiguration Message 3, the UE activates the ROHC algorithm according to the ROHC activation configuration carried in RRC Reconfiguration Message 3. However, before camping on Cell A, the UE did not receive the RRC Reconfiguration message from Cell B disabling the ROHC algorithm. Therefore, after camping on Cell A, the UE still activates the ROHC algorithm.

[0192] Based on this, if Cell A does not enable 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 packets based on the ROHC algorithm, i.e., execute S215. Cell A will use a non-ROHC algorithm to compress and decompress the data packets, i.e., execute S216.

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

[0194] 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.

[0195] 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.

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

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

[0198] 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.

[0199] S218: Decompression failed, discarded.

[0200] Understandably, after receiving the RTP packets sent by Cell A, the UE decompresses them using the ROHC algorithm. However, Cell A does not use the ROHC algorithm to compress the RTP packets sent to the UE. Therefore, the UE cannot decompress the RTP packets sent by Cell A, resulting in a decompression failure. The UE will simply discard any RTP packets that fail to be decompressed.

[0201] S219: Decompression failed, discarded.

[0202] Understandably, after receiving the RTP packets sent by the UE, Cell A does not decompress them using the ROHC algorithm. The UE, however, compresses the RTP packets it sends to Cell A using the ROHC algorithm. Therefore, Cell A is unable to decompress the RTP packets sent by the UE, resulting in a decompression failure. Cell A also discards any RTP packets that fail to be decompressed.

[0203] In this case, the UE and Cell A will never receive RTP packets related to the current call from each other. Based on existing standard protocols, if the UE does not receive RTP packets related to the current call within a certain period of time, it will determine that the RTP or RTCP (Real-time Transport Control Protocol) resource of the current call has timed out. In this case, the UE will send a BYE message to Cell A. The reason field of the BYE message will carry RTP / RTCP timeout resource (RTP / RTCP timeout resource), and the corresponding error code is 2, that is, S220.

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

[0205] Because the UE sends a BYE message to release the current call, the call between the UE and Cell A is disconnected. The reason why the UE and Cell A cannot receive the RTP packets sent by each other is not because the UE and Cell A do not send RTP packets at the set time, but because the configuration of the UE and Cell A do not match, for example, one has the ROHC algorithm enabled and the other does not.

[0206] 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 on this embodiment.

[0207] As can be seen from the above description of the scenarios in Figures 3 and 4, the call drops that occur after the UE is triggered to execute the RLF process and reselect a cell to reside in are all caused by the UE's failure to verify the RRC reconfiguration message sent by the network. For example, in one scenario, during the verification of the RRC reconfiguration message, because the RRC reconfiguration message instructs the UE to switch to a specified cell C, and the RRC reconfiguration message does not carry a configuration item for a parameter of cell C (such as information for deleting the configuration of SRS resources for the antenna switching mode), but the UE has a configuration of SRS resources for an antenna switching mode that is incompatible with cell C, this will cause the RRC reconfiguration message to fail verification. 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 in the configuration items, such as the current corresponding values ​​are incompatible with or do not match the cell to be resided, 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, reducing call failures and improving user experience. Alternatively, as in another scenario, during 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 can 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 thus causing the call to be abnormal. In this scenario, some embodiments of the present application provide a method for calls, which aims to enable the terminal device to update the abnormal configuration item 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 is successfully verified, and the call can continue smoothly.

[0208] Specifically, in the method for calls provided in some embodiments of the present application, a method for updating configuration items with abnormalities, a method for updating some configuration items in the RRC reconfiguration message is introduced, that is, when the UE verifies the RRC reconfiguration sent by the currently accessed 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 incompatible configuration items (hereinafter referred to as: compatible function). Furthermore, when it is determined that the function is activated 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 a preset configuration item list, these abnormal configuration items are updated, such as by not taking effect on 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). In this way, the configuration of the abnormal configuration item can be not taken effect (which can also be understood as removing the configuration corresponding to the abnormal configuration item), thereby achieving the effect of ignoring the abnormal configuration item. The configuration of not taking effect on the abnormal configuration item can be understood as ignoring the abnormal configuration item.), or by updating the content of the configuration of the abnormal configuration item in the UE to the content of the configuration item configuration 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.

[0209] It should be noted that the configuration items in the preset configuration item list mentioned in this application are specifically 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.

[0210] In order to better understand the method for making calls provided by the present application, based on the scenarios shown in Figures 3 and 4, the method for making calls provided by an embodiment of the present application is introduced, and the specific implementation scenario is described in conjunction with Figure 5.

[0211] 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.

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

[0213] Accordingly, the updateable configuration items are the aforementioned ignorable parameters.

[0214] In addition, in each embodiment of the present application, an abnormal configuration item is a configuration item in which the value corresponding to the aforementioned parameter is abnormal. For example, when the value corresponding to the first parameter is abnormal, the first configuration item including the first parameter is the abnormal configuration item.

[0215] Based on this premise, in the following embodiments and the accompanying drawings corresponding to the embodiments, determining whether the configuration item with an anomaly is a configuration item in the preset configuration item list (such as S404) is essentially to determine whether the first parameter is the same as any parameter in the parameter list stored in the terminal device when the value corresponding to the first parameter is anomaly. 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 stored in the terminal device, it can be determined that the first parameter is a negligible parameter. That is, the configuration item with an anomaly in the following embodiments is an updateable configuration item.

[0216] 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.

[0217] Referring to Figure 5, S301 to S311 are similar to S201 to S211 in the embodiment described in Figure 4. For details, see the description of S201 to S211 and will not be repeated here. S312 to S319 are the processing logic performed by the UE and the network side after the method for calling provided by this application is introduced.

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

[0219] As can be seen from the description of the above embodiment, if the target base station to be handed over is an FDD system, that is, it does not support the configuration of SRS resources in antenna switching mode, but the UE has configured SRS resources in antenna switching mode, the UE will output a result of RRC reconfiguration message verification failure. Therefore, after introducing the method for call provided by this application, the UE needs to determine in step S312 whether the current cell C is an FDD system and the UE has configured SRS resources in antenna switching mode.

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

[0221] According to the provisions of the existing standard protocol, for the FDD system, the configuration of 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 verify the configuration of the SRS resources in the antenna switching mode, and make the RRC reconfiguration message 4 verification successful if other configurations are compatible.

[0222] For example, in some implementations, the configuration of SRS resources for antenna switching mode may be agreed upon, such as srs_tx_switch = 1 indicating that SRS resources for antenna switching mode are configured. If the compatibility function is enabled, in S317, the UE may locally modify the configuration of SRS resources for antenna switching mode from "1" to "0", i.e., modify srs_tx_switch = 1 to srs_tx_switch = 0.

[0223] The compatibility function being enabled 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.

[0224] Continuing with FIG. 5 , illustratively, after completing S317 , since the configuration items in RRC reconfiguration message 4 do not conform to existing standard protocols for FDD system Cell C, such as the configuration of the SRS resources for antenna switching mode, have been updated to srs_tx_switch = 0 by the UE, meaning that the UE has removed the SRS resources for antenna switching mode, the UE verifies that RRC reconfiguration message 4 is successful. Thus, the UE can switch to Cell C based on the address information corresponding to Cell C in RRC reconfiguration message 4 and remain in Cell C until receiving the next cell switching instruction, i.e., executing S318 .

[0225] As can be seen from the above description, after the UE completes RRC reconfiguration, it sends an RRC Reconfiguration Complete message to the network to inform the network that the UE has completed the RRC reconfiguration. Based on this, after the UE resides in Cell C, the UE also sends an RRC Reconfiguration Complete message to Cell C to inform Cell C that the RRC reconfiguration (switching to Cell C) performed in response to RRC Reconfiguration Message 4 is complete, that is, executing S319.

[0226] For example, when the UE camps on 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.

[0227] For example, if it is determined in S313 that the UE has not enabled the compatibility function, in this case, the UE may be configured to execute the existing cell reselection process according to existing standard protocol provisions.

[0228] Continuing with FIG5 , this embodiment takes as an example a scenario where the UE selects the original cell for camping when the compatibility function is not enabled. S314 to S316 involved in camping on the original cell are similar to S113 to S115 in the embodiment shown in FIG3 . For specific implementation details, see the description of S113 to S115 and will not be repeated here.

[0229] For example, in other implementations, such as when the UE does not enable the compatibility function, the UE selects a new cell, such as Cell A, to reside in. The processing involved in residing in the new cell can be referred to S213 to S220 in the embodiment shown in Figure 4, and will not be repeated here.

[0230] 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 on this embodiment.

[0231] 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 implementation methods, before the UE leaves the factory, the terminal manufacturer may uniformly turn on the compatibility function switch of the UE deployed in a certain area or a certain type of UE based on customization requirements. In this way, for the UE in that area or of that type, 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-mentioned 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.

[0232] For example, in some other implementations, the compatibility function may be enabled by default for all UEs generated by the terminal manufacturer. In this implementation, if 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 and S317 may be executed.

[0233] For example, in some other implementations, an entry for user operation may be provided in the UE, and the user may decide whether to enable the compatibility function according to needs.

[0234] 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 on this embodiment.

[0235] Since the embodiment described in FIG5 is mainly aimed at the problem scenario caused by the configuration of the SRS resources of the antenna switching mode, 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 configuring the preset configuration item list described above in the UE. In this way, when the UE verifies the content of 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-mentioned method 1 or method 2 based on the pre-set updateable configuration items. Then, when the configuration item that caused the abnormality can be updated, the UE updates the abnormal configuration item according to the above-mentioned method 1 or method 2 (which can also be understood as correcting the abnormal configuration item), so that the UE can be unaffected by the abnormal configuration item and can be handed over to the target cell normally. This implementation method is described in detail below with reference to Figure 6.

[0236] 6 , illustratively, 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 ).

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

[0238] 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.

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

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

[0241] Continuing to refer to Figure 6, illustratively, 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.

[0242] It should be noted that the configuration carried by the first RRC reconfiguration message may be for the first cell or may indicate handover 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.

[0243] Continuing with Figure 6 , illustratively, when the first RRC reconfiguration message indicates a handover to the second cell, the UE camps on the second cell according to the first RRC reconfiguration message, i.e., executes S410a. Accordingly, after camping on the second cell, the UE sends an RRC Reconfiguration Complete message to the second cell, i.e., executes S410b. The UE's current call continues in the second cell.

[0244] Continuing with Figure 6 , illustratively, when the first RRC reconfiguration message carries a configuration for the first cell (such as RRC reconfiguration message 3 in the above embodiment), the UE is to configure itself according to the configuration carried in the first RRC reconfiguration message, i.e., execute S410c. In this case, after configuring itself according to the first RRC reconfiguration message, the UE remains in the first cell. Therefore, the UE sends an RRC Reconfiguration Complete message to the first cell, i.e., executes S410d. The UE's current call will continue in the first cell.

[0245] 6 , illustratively, 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 in the preset configuration item list (an updateable configuration item).

[0246] Exemplarily, if the abnormal configuration items (all) are preset updateable configuration items, the UE can further detect whether the compatibility function is turned on, that is, execute S405. Correspondingly, if the compatibility function is turned on, S409 can be executed. On the contrary, if the compatibility 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 case of staying in the original cell as an example, that is, when the compatibility 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.

[0247] 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 repeated here.

[0248] It should be noted that the configuration carried by the first RRC reconfiguration message may be for the first cell or may indicate handover to the second cell (taking Cell C as an example). Therefore, in S409, the UE may perform different operations depending on the cell targeted by the first RRC reconfiguration message, as detailed below.

[0249] Continuing to refer to Figure 6, exemplarily, when the first RRC reconfiguration message carries a 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 a 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 saved in the UE, and the two have the same name but different corresponding values), before receiving the first RRC reconfiguration message, the terminal device has the first configuration item saved, and the first configuration item and the second configuration item are for the same parameter but different parameter values. Then, in the process of verifying the first RRC reconfiguration message, the UE will find that the first configuration item is abnormal (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 RRC Reconfiguration complete message to the first cell, that is, execute S409b. The UE's current call will continue in the first cell.

[0250] For example, in a scenario where method 2 is used to update abnormal configuration items, for example, when the UE switches from Cell A to Cell B, it configures itself according to the configuration of Cell B sent by Cell A. After residing on Cell B, Cell B modifies these already configured configurations and carries them in the first RRC reconfiguration message sent to the UE. This causes some configuration items configured for Cell B in the UE to be incompatible with the configuration carried in the first RRC reconfiguration message. In this case, the UE actually needs 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.

[0251] 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 on this embodiment.

[0252] Continuing with Figure 6 , illustratively, when the first RRC reconfiguration message indicates a handover to the second cell, the UE is to disable the abnormal configuration item, such as by using the aforementioned method 1 to update the abnormal configuration item, so that the first RRC reconfiguration message verification succeeds. The UE then camps on the second cell based on the first RRC reconfiguration message (i.e., executes S409c). Accordingly, after camping on the second cell, the UE sends an RRC Reconfiguration Complete message to the second cell (i.e., executes S409d). The UE's current call will continue in the second cell.

[0253] For example, taking the configuration item with an abnormality as the configuration item for 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 for 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 is not effective (it can also be understood as removing the configuration of the SRS resource of the antenna switching mode), and then the UE can verify that the first RRC reconfiguration message is successful. 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). The UE can modify the value of the configuration item to make the configuration item invalid, so that the first RRC reconfiguration message can ultimately be successfully verified by the UE.

[0254] 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 on this embodiment.

[0255] In addition, it should be noted that, based on the method for call provided in this application, determining whether the abnormal configuration items are preset updateable configuration items, and when it is determined that all the abnormal configuration items are updateable configuration items, the operation of detecting whether the compatible function is enabled can occur when the UE receives any RRC reconfiguration message. The above description is merely an example listed to better understand the technical solution of this embodiment and is not intended to be the sole limitation of this embodiment.

[0256] 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 uses 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 existing standard protocols, the method for making a call provided in the embodiment of the present application is also applicable.

[0257] In addition, it should also 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.

[0258] In order to better understand the technical solution provided by the embodiments of the present application, taking the terminal device as 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 by the embodiments of the present application are explained.

[0259] Before explaining the software structure of a mobile phone, the architectures that can be adopted by the software system of the mobile phone are first explained.

[0260] 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.

[0261] Furthermore, it is understood that the software systems currently used by mainstream terminal devices include, but are not limited to, Windows, Android, and iOS. For ease of explanation, this embodiment of the application uses the layered architecture of the Android system as an example to illustrate the software structure of a mobile phone. The subsequent technical solutions for making calls provided in this embodiment of the application are also applicable to other systems in specific implementations.

[0262] Furthermore, it should be understood that the current layered architecture of mobile phones divides software into several layers, each with clear roles and divisions of labor. Layers communicate with each other via software interfaces. These layers may include, for example, the application layer, the application framework layer, the Android runtime and system libraries, the hardware abstraction layer, the kernel layer, and so on. The following description will only use the layers where the functional modules involved in the method for making a call provided in the embodiments of the present application are located as an example.

[0263] 7, which is a schematic diagram of the software structure and hardware involved in the mobile phone of the embodiment of the present application. In FIG7, from top to bottom are the application layer, application framework layer, kernel layer, and hardware.

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

[0265] Continuing to refer to FIG. 7 , specifically to the technical solution provided in the embodiment of the present application, the application layer may include a phone application, a settings application, a compatible function activation application, and the like.

[0266] Among them, the phone application allows users to initiate call service operations.

[0267] Accordingly, in response to the operation, the mobile phone can establish a media session with the called party based on the mobile communication architecture shown in Figure 1. Regarding the establishment of the media session, please refer to the description of the above-mentioned terminal A and terminal B establishing a media session based on the mobile communication architecture shown in Figure 1, which will not be repeated here.

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

[0269] For example, 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.

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

[0271] For example, in the above embodiment, where the compatibility function can be enabled by the user, the entry for enabling the compatibility function can be integrated into the settings application. In this way, the user does not need to separately install the compatibility function enabling application on the phone, but can enable the compatibility function through the entry provided by the settings application.

[0272] 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 on this embodiment.

[0273] Continuing to refer to FIG. 7 , specifically to 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.

[0274] 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., before establishing a media session and after the media session is established, that is, during a call.

[0275] 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.

[0276] CS Phone is used for calls on the CS (Circuit Switched) network. When IMS services are unavailable (the phone is stuck on 2G / 3G or IMS registration is unsuccessful), you can make calls through CS calls. It can also be used for domain redialing (commonly known as CS redial) when an IMS call fails.

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

[0278] 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 on this embodiment.

[0279] In addition, it is understandable that the kernel layer in the Android system is the layer between hardware and software. Continuing to refer to FIG7 , specifically to the technical solution provided in the embodiment of the present application, the kernel layer may include the Transmission Control Protocol / Internet Protocol STACK (TCP / IP protocol stack).

[0280] TCP / IP is a protocol suite that enables information transmission across multiple networks. Specifically, the TCP / IP stack at the kernel layer primarily serves Internet access and also handles video-related data processing during phone calls.

[0281] Continuing to refer to FIG7 , specifically to the technical solution provided in the embodiment 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, and the like.

[0282] 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 embodiment.

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

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

[0285] 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. 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.

[0286] It should be noted that the 3A module specifically refers to a functional module that integrates three audio algorithms: Acoustic Echo Cancelling (AEC), Active Noise Control (ANS), and Automatic Gain Control (AGC).

[0287] 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.

[0288] Accordingly, data packets received by the antenna from the network are sequentially transmitted through the PHY, MAC, and RLC layers to the PDCP layer for processing. For example, the data packets are decrypted using the ROHC algorithm. The decrypted RTP / RTCP packets are then processed by the IP and TCP / UDP layers before being passed to the RTP / RTCP module for processing and transmission to the ADSP. The ADSP then processes the data provided by the RTP / RTCP module through the decoder, 3A module, and AFE module, extracting playable audio data that is ultimately delivered to the receiver, speaker, or headphones for playback.

[0289] Furthermore, 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 RRC Reconfiguration, RRC Reconfiguration Complete, and RRC Connection re-establishment, is also implemented by the RRC module in the modem.

[0290] This concludes the introduction to the software structure of a mobile phone. It should be understood that the layers and components within each layer shown in FIG7 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, and each layer may include more or fewer components, and this application does not limit this.

[0291] In order to better understand the technical solutions provided by the embodiments of the present application, still taking the terminal device as a mobile phone as an example, refer to Figure 8 to specifically describe the specific structure of the mobile phone and the devices involved in implementing the embodiments of the present application.

[0292] 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.

[0293] 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 antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0294] Specifically in each embodiment of the present application, the base station, such as the gNB mentioned in the above embodiment, sends messages to the mobile phone 100, which is the 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.

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

[0296] 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 technology (NFC), infrared technology (IR), etc. applied on the mobile phone 100.

[0297] 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. This allows the mobile phone 100 to communicate with the network and other devices via mobile communication technology or wireless communication technology.

[0298] 8 , illustratively, 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.

[0299] For example, 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.

[0300] 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 one by one here and this application does not impose any restrictions on this.

[0301] 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.

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

[0303] It should be noted that, in practical applications, mobile phone 100 can implement the technical solutions provided by various embodiments of this application through two processing units, AP 110A and Modem 110B. For example, the AP responds to a call request initiated by a user, invoking call-related services in the application framework layer, as shown in FIG7 , and the corresponding driver in the kernel layer, to pass the call request to the modem. The modem can then interact with the network according to the processing logic involved in the call methods provided by various embodiments of this application. Specific implementation details can be found in the above-mentioned embodiments and will not be repeated here.

[0304] Furthermore, it is also understandable that the controller, a processing unit 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 operation control signals based on instruction opcodes and timing signals to complete the control of instruction fetching and execution.

[0305] 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.

[0306] In addition, the USB interface 130 shown in FIG. 8 is an interface that complies with USB standard specifications, and specifically may be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like.

[0307] The charging management module 140 is configured to receive charging input from a charger. Furthermore, the power management module 141 shown in FIG8 is configured 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 provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160. The wireless communication function of the mobile phone 100 is implemented via antenna 1, antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.

[0308] Furthermore, the mobile phone 100 shown in FIG8 implements display functionality through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that 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 that execute program instructions to generate or modify display information.

[0309] 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 one or N display screens 194 , where N is a positive integer greater than one.

[0310] In addition, the mobile phone 100 can implement a shooting function through the ISP, camera 193, video codec, GPU, display 194, and application processor. Among them, the camera 193 is used to capture still 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.

[0311] 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.

[0312] In addition, FIG8 shows that the external memory interface 120 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 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

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

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

[0315] In addition, the motor 191 shown in FIG. 8 may be, for example, a vibration motor; and the indicator 192 may be an indicator light.

[0316] In addition, the SIM card interface 195 shown in Figure 8 can be used to connect a SIM card or a USIM card. A SIM card can be connected to and disconnected from the mobile phone 100 by inserting or removing it from the SIM card interface 195. The mobile phone 100 can support one 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.

[0317] This concludes the introduction to the hardware structure of the mobile phone 100. It should be understood that the mobile phone 100 shown in FIG8 is merely an example. In a specific implementation, the mobile phone 100 may have more or fewer components than shown in the figure, may combine two or more components, or may have a different component configuration. The various components shown in FIG8 may be implemented in hardware, including one or more signal processing and / or application-specific integrated circuits, software, or a combination of hardware and software.

[0318] 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 an 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 is running 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.

[0319] 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.

[0320] In addition, an embodiment of the present application also 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 a call in the above-mentioned embodiment.

[0321] 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.

[0322] 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 above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above 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, It is 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; 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; 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, 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.

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

3. The method according to claim 1 or 2, It is 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; When the value corresponding to the first parameter is abnormal, 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.

4. The method according to claim 3, It is 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.

5. The method according to claim 1 or 2, It is characterized in that The first information includes information of a 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 the value corresponding to the first parameter is abnormal, 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.

6. The method according to claim 5, It is 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.

7. The method according to claim 5 or 6, It is characterized in that The first cell is a cell of a TDD system, and the second cell is a cell of an FDD system.

8. The method according to claim 7, It is characterized in that The first configuration item is a configuration item of an SRS resource of an antenna switching mode.

9. The method according to any one of claims 6 to 8, It is characterized in that The first value is 1, and the third value is 0.

10. The method according to any one of claims 1 to 9, It is characterized in that The ignoring the abnormal value corresponding to the first parameter includes: When the first parameter is a negligible parameter, ignoring an abnormal value corresponding to the first parameter; 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.

11. The method according to claim 10, It is characterized in that When the first parameter is a negligible parameter, ignoring the abnormal value corresponding to the first parameter includes: When the first parameter is a ignorable parameter and the terminal device supports a compatible function, an abnormal value corresponding to the first parameter is ignored; wherein, the terminal device supporting the compatible function indicates that the terminal device supports ignoring abnormal values ​​corresponding to ignorable parameters.

12. The method according to any one of claims 1 to 11, It is 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 method for making a call, It is 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; 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, the abnormal parameter value corresponding to the parameter is ignored, so that the first RRC reconfiguration message is verified successfully.

14. The method according to claim 13, It is characterized in that The parameter value for ignoring the exception corresponding to the parameter includes: Update the parameter value corresponding to the parameter.

15. A terminal device, It is 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 14.

16. A chip system, It is 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 14.

17. The chip system according to claim 16, It is characterized in that The processor includes a modem.

18. A computer-readable storage medium, It is 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 14.

Images