Communication method, readable medium, terminal equipment and chip system

Abstract

The invention relates to the technical field of communication, and discloses a communication method, a readable medium, terminal equipment and a chip system. The communication method in the application comprises the following steps: the terminal device sends a wireless communication link connection request to the network device in a currently resident cell, and detects the number of continuous abnormities of a wireless communication link within a preset duration; moreover, the terminal equipment can switch at least one of the cells and the network types when the number of continuous exceptions is greater than the set threshold value of the number of exceptions, and then establish a wireless communication link with the network equipment. By means of the method, even if the wireless communication link is continuously abnormal, the terminal equipment can normally communicate with the network equipment, so that the communication service of the terminal equipment is maintained.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and particularly to a communication method, a readable medium, a terminal device, and a chip system. Background Art

[0002] When a user performs wireless communication services such as browsing the web through a terminal device (such as a mobile phone), the terminal device needs to send a service request (ServiceRequest) and a wireless communication link connection request to the network device (such as a base station) corresponding to the currently camped cell, in order to establish a wireless communication link with the network device and perform data transmission with the network device based on the wireless communication link, so that the user can perform activities such as web browsing through the terminal device.

[0003] Taking the radio resource control (RRC) link as an example, during the RRC link establishment process, a situation where normal communication with the network device cannot be established may occur, thereby affecting the communication services of the terminal device. Summary of the Invention

[0004] The purpose of this application is to provide a communication method, a readable medium, a terminal device, and a chip system.

[0005] The first aspect of this application provides a communication method, which is applied to a terminal device and includes: sending a first RRC connection request to a first network device of a first cell, where the first network device corresponds to a first network mode; detecting a first RRC link abnormal event corresponding to the first RRC connection request, and determining that the number of times of generating the RRC link abnormal event after sending the RRC connection request to the first network device within a first duration meets a first handover condition; sending a second RRC connection request to a second network device, where at least one of the network mode and the cell corresponding to the second network device is different from that of the first network device.

[0006] It can be understood that the terminal device sends a wireless communication link connection request to the network device in the currently camped cell, and detects the continuous abnormal times of the wireless communication link within a preset duration. And the terminal device can perform at least one of switching the cell and switching the network mode when the continuous abnormal times are greater than the set abnormal times threshold, and then establish a wireless communication link with the network device. Through this method, even when the wireless communication link has continuous abnormalities, the terminal device can still communicate with the network device normally, thereby maintaining the communication services of the terminal device.

[0007] In a possible implementation of the above first aspect, the first duration includes the occurrence time of the first RRC link abnormal event.

[0008] In a possible implementation of the foregoing first aspect, the first handover condition includes: the number of RRC link abnormal events occurring within a first duration is greater than a first abnormal number threshold, and the time interval between an RRC link abnormal event occurring within the first duration and the corresponding RRC connection request is less than or equal to an abnormal time threshold, and the time interval between adjacent RRC link abnormal events occurring within the first duration is less than a time interval threshold.

[0009] In a possible implementation of the foregoing first aspect, the second network device corresponds to a second cell and a first network mode, and the method further includes: determining that the number of RRC link abnormal events occurring after sending an RRC connection request to the second network device within a second duration satisfies a second handover condition; sending a third RRC connection request to a third network device, where the third network device corresponds to the second network mode.

[0010] In a possible implementation of the foregoing first aspect, the second handover condition includes: the number of RRC link abnormal events occurring within a second duration is greater than a second abnormal number threshold, and the time interval between an RRC link abnormal event occurring within the second duration and the corresponding RRC connection request is less than or equal to an abnormal time threshold, and the time interval between adjacent RRC link abnormal events occurring within the second duration is less than an interval time threshold.

[0011] In a possible implementation of the foregoing first aspect, the method further includes: after corresponding to sending a third RRC connection request to the third network device, detecting that the network quality corresponding to the third network device is lower than a quality threshold; sending a fourth RRC connection request to a fourth network device, where the fourth network device corresponds to the first network mode.

[0012] In a possible implementation of the foregoing first aspect, the RRC link abnormal event includes at least one of the following: the terminal device does not receive a response message to an RRC connection request within a preset time; the terminal device receives a response message without parameters; the terminal device detects a radio link failure; the terminal device detects no data radio bearer.

[0013] In a possible implementation of the foregoing first aspect, the response message includes at least one of the following: a reject service request message, a reject link establishment message, a release radio communication link message; and the no data radio bearer includes at least one of the following: a radio data bearer establishment failure, a radio data bearer not established.

[0014] A second aspect of the present application provides a communication method applied to a terminal device, including: sending at least one first RRC connection request in a first cell; the cause value field of the first response messages received within a first duration does not include a cause value parameter, where the number of first response messages received within the first duration is less than or equal to the number of times of sending the first RRC connection request; sending a second RRC connection request in a second cell.

[0015] In an embodiment of the present application, when the number of consecutive anomalies is greater than K, the terminal device 100 determines a second cell and sends a second RRC connection request to a second network device. For example, corresponding to the terminal device 100 sending K times of first RRC connection requests to the first network device 200, the number of consecutive anomalies being greater than K may be: the K first response messages received within the first duration are all response messages without parameters. Or for example, corresponding to the terminal device 100 sending M times of first RRC connection requests to the first network device 200, the number of consecutive anomalies being greater than K may be: the K first response messages received within the first duration are all response messages without parameters. Wherein, K is less than M, and the value range of M can be any integer within 2 to 25.

[0016] In a possible implementation of the above second aspect, the method further includes: the cause value fields of the second response messages received within a second duration do not include a cause value parameter, where the number of second response messages received within the second duration is less than or equal to the number of times of sending the second RRC connection request; sending a third RRC connection request in a third cell.

[0017] In an embodiment of the present application, when the number of consecutive anomalies is greater than P, the terminal device 100 determines a third cell and sends a third RRC connection request to a third network device. For example, corresponding to the terminal device 100 sending P times of second RRC connection requests to the first network device 200, the number of consecutive anomalies being greater than P may be: the P second response messages received within the second duration are all response messages without parameters. Or for example, corresponding to the terminal device 100 sending Q times of second RRC connection requests to the first network device 200, the number of consecutive anomalies being greater than P may be: the P second response messages received within the second duration are all response messages without parameters.

[0018] In a possible implementation of the above first aspect, the method further includes: the time interval between the first response message and the corresponding first RRC connection request sent is less than or equal to an anomaly time threshold; the time interval between adjacent first response messages within the first duration is less than an interval time threshold.

[0019] The third aspect of the present application provides a readable medium, on which instructions are stored, and when the instructions are executed on a terminal device, the terminal device is caused to execute any of the methods in the first aspect or the second aspect above.

[0020] The fourth aspect of the present application provides a terminal device, including: a memory for storing instructions executed by one or more processors of the terminal device; and a processor, which is one of the processors of the terminal device, for executing the instructions stored in the memory to implement any of the methods in the first aspect or the second aspect above.

[0021] The fifth aspect of the present application provides a chip system, including a processing circuit and a storage medium, in which computer program code is stored; when the computer program code is executed by the processing circuit, any of the methods in the first aspect or the second aspect above is implemented. Description of the Drawings

[0022] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required for use in the description of the specific embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0023] Figure 1 The schematic diagram of a communication system is shown according to an embodiment of the present application;

[0024] Figure 2a The schematic diagram of the interface of a terminal device when the terminal device cannot communicate normally with a network device is shown according to an embodiment of the present application;

[0025] Figure 2b The schematic diagram of the interface of another terminal device when the terminal device cannot communicate normally with a network device is shown according to an embodiment of the present application;

[0026] Figure 3a The schematic diagram of the interaction process when the RRC link between a terminal device and a network device is abnormal is shown according to an embodiment of the present application;

[0027] Figure 3b The schematic diagram of the process of completing RRC link establishment is shown according to an embodiment of the present application;

[0028] Figure 4a The schematic diagram of the process of a communication method is shown according to an embodiment of the present application;

[0029] Figure 4b The interaction schematic diagram of recording the number of consecutive anomalies within the first duration is shown according to an embodiment of the present application;

[0030] Figure 4c An embodiment according to the present application shows a schematic diagram of the change of a network signal icon;

[0031] Figure 5 An embodiment according to the present application shows a schematic flowchart of the network state evaluation of a second network by a terminal device;

[0032] Figure 6 An embodiment according to the present application shows a schematic interaction flowchart of an RRC link exception where a first network device fails to respond to an RRC connection request from a terminal device within a preset time;

[0033] Figure 7 An embodiment according to the present application shows a schematic interaction flowchart of an RRC link exception where a first network device sends a rejection service request without parameters to a terminal device;

[0034] Figure 8 An embodiment according to the present application shows a schematic interaction flowchart of an RRC link exception where a first network device sends a rejection RRC connection establishment message without parameters to a terminal device;

[0035] Figure 9 An embodiment according to the present application shows a schematic interaction flowchart of an RRC link exception where a first network device sends an RRC link release message without parameters to a terminal device;

[0036] Figure 10 An embodiment according to the present application shows a schematic interaction flowchart of an RRC link exception where the RRC link exception is a radio link failure;

[0037] Figure 11 An embodiment according to the present application shows a schematic interaction flowchart of an RRC link exception where the RRC link exception is a non-data radio bearer;

[0038] Figure 12 An embodiment according to the present application shows a schematic diagram of the structure of a terminal device. Detailed implementation manners

[0039] Illustrative embodiments of the present application include, but are not limited to, a communication method, a readable medium, a terminal device, and a chip system.

[0040] To make the objectives, technical solutions, and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and elaborately described below with reference to the accompanying drawings.

[0041] First, some terms in this application are explained to facilitate understanding by those skilled in the art.

[0042] Cell: Also known as a cellular cell, it refers to the area covered by a wireless signal in mobile communication.

[0043] A mobile communication network can adopt a cellular structure, that is, multiple base stations are erected at different locations. Each base station forms a cell, and each base station is responsible for the communication of mobile users within its cell area. To ensure that mobile users can obtain uninterrupted and continuous communication, adjacent cells are provided with a certain overlapping area, so that mobile users can switch from one cell to another during the communication process.

[0044] Specifically, referring to the schematic diagram of the communication system as Figure 1 shown, the communication system may include multiple network devices (such as base stations): network device 21, network device 22, and network device 23. Among them, network device 21 corresponds to cell A, network device 22 corresponds to cell B, and network device 23 corresponds to cell C. Cell A has a certain overlapping area with adjacent cell B and cell C respectively.

[0045] The technical solution provided by this application can be applied to various communication systems, such as: the fifth-generation (5G) mobile communication system or new radio access technology (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), etc. The technical solution provided by this application can also be applied to future communication systems, such as the sixth-generation mobile communication system, etc. This application does not make any limitations in this regard. Figure 1 According to an embodiment of the present application, a schematic diagram of a communication system is shown, as Figure 1 shown, the communication system may include: a terminal device 10 and multiple network devices: network device 21, network device 22, and network device 23. Among them, network device 21 corresponds to cell A, network device 22 corresponds to cell B, and network device 23 corresponds to cell C.

[0046] It can be understood that Figure 1 only one network device corresponding to one cell is taken as an example. In some other embodiments, one network device may also correspond to multiple cells. Figure 1The communication system shown is only an example of a communication system. In other embodiments, the communication system may further include more or fewer terminal devices and network devices than shown. A terminal device may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a mobile phone, smart TV, wearable device, tablet computer (Pad), computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, and so on. In the embodiments of the present application, the terminal device may further include a relay, or it can be understood that any device capable of communicating data with the base station can be regarded as a terminal device.

[0047] In the embodiments of the present application, the device for implementing the functions of the terminal device may be the terminal device itself, or a device capable of supporting the terminal device to implement such functions, such as a chip system, and this device may be installed in the terminal device. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. In the embodiments of the present application, taking the device for implementing the functions of the terminal as the terminal device as an example, the technical solutions provided in the embodiments of the present application are described.

[0048] The network device may include one or more access network (AN) devices, such as a base station, which is a device deployed in the access network to provide wireless communication functions for terminals. For example, the network device may include an evolved NodeB (NodeB or eNB or eNodeB, evolutional NodeB) in the LTE system; the network device may also include a next generation node B (gNB or gNodeB) in the 5th generation (5G) New Radio (NR) system (also simply referred to as the NR system); the network device may further include a centralized unit (CU) and a distributed unit (DU) in a cloud radio access network (Cloud RAN) system. The embodiments of the present application do not limit this.

[0049] In the embodiments of the present application, the device for implementing the functions of the network device may be the network device or a device capable of supporting the network device to implement such functions, such as a chip system, and this device may be installed in the network device. In the embodiments of the present application, taking the device for implementing the functions of the network device being the network device as an example, the technical solutions provided by the embodiments of the present application are described.

[0050] As described above, taking the RRC link as an example of the wireless communication link, when the terminal device conducts wireless communication services, the terminal device needs to send an SR request to the network device in the currently camped cell, and at the same time trigger the establishment of the RRC link, that is, send an RRC connection request (RRC Setup Request) to the network device to establish a wireless communication link with the network device.

[0051] After the network device and the terminal device complete the establishment of the RRC link, in some cases, if the network device detects that there is no data transmission between the terminal device and the network device within a preset time (for example, the transmission of service data has been completed), in order to save resources and reduce power consumption, the network device will disconnect the established RRC link and send an RRC link release message (RRC Release) to the terminal device. Among them, the RRC link release message is used to indicate that the network device has disconnected the RRC link established with the terminal device.

[0052] In other cases, if the network device has no network resources available for allocation to the terminal device, the network device will also send an RRC link release message to the terminal device.

[0053] Among them, the RRC connection release message usually includes parameters such as a cause value, for example, parameters such as releasing a radio bearer (RB) established during the RRC establishment process and a waiting time, so that the terminal device can perform corresponding processing based on the parameter information. For example, the terminal device can switch to a target cell to establish an RRC connection or wait for a period of time before sending an RRC connection request, etc.

[0054] After the established RRC connection is disconnected, if the terminal device detects a communication service trigger event again, for example, detecting that the user uses a voice call service such as making a phone call, the user uses a browser to search for content, the user's operation of making a video call, etc., which requires an operation for a wireless communication service, it is necessary to send a service request and an RRC connection request to the network device again to establish an RRC connection again.

[0055] However, during the RRC connection establishment process between the terminal device and the network device, if there is an RRC connection abnormality and the network device does not respond to the RRC connection request of the terminal device, the terminal device will repeatedly attempt to send a service request and an RRC connection request to the network device in the current cell.

[0056] Or, if the network device sends a parameterless response message or the like to the terminal device, the terminal device will repeatedly attempt to send a service request and an RRC connection request to the network device in the current cell. And after the terminal device repeatedly sends a service request and an RRC connection request, if the RRC connection still cannot be established, although the network quality is high, the terminal device cannot communicate with the network device normally.

[0057] Exemplarily, Figure 2a According to an embodiment of the present application, a schematic diagram of the interface of a terminal device when the terminal device cannot communicate with the network device normally is shown. As Figure 2a shown, a prompt message of "loading failed" is displayed in the user interface 202 of the terminal device 100, but the network signal icon 201 shows that the network signal is full. That is, although the network signal is good (full), the terminal device cannot communicate with the network device normally.

[0058] Figure 2b According to an embodiment of the present application, another schematic diagram of the interface of a terminal device when the terminal device cannot communicate with the network device normally is shown. As Figure 2b shown, a chat interface between the user and the contact "XXX" is displayed in the user interface 204 of the terminal device 100, and the messages "can't receive your message" and "no network" sent by the user both fail to be sent, but the network signal icon 203 shows that the network signal is full. That is, although the network signal is full, the terminal device cannot communicate with the network device normally.

[0059] It can be understood that Figure 2a and Figure 2b the network signal icons 201 and 203 in Figure 2a and Figure 2b are only examples. In some other embodiments, when the network signal is good, the network signal icon can also be in other forms. For example, when the signal is full, it can be five grids, and the network signal icon in the display interface of the terminal device 100 can be four grids. Or for another example, when the signal is full, it is 100%, and the network signal icon in the display interface of the terminal device 100 can be a situation greater than the signal quality threshold, such as 70%. The present application does not make specific limitations on the display form of the network signal icon when the network signal is good.

[0060] Exemplarily, taking the abnormal radio communication link as an example where the network device sends an RRC link release message without parameters Figure 3a According to the embodiments of the present application, a schematic diagram of the interaction process of the RRC link abnormality between the terminal device and the network device is shown.

[0061] As Figure 3a shown, this process includes:

[0062] S301: The terminal device 100 sends a registration request (RegistrationRequesst) to the first network device 200.

[0063] In some embodiments, the terminal device 100 sends a registration request to the first network device 200 in response to a trigger event for the first time to access the network (such as power-on).

[0064] S302: The first network device 200 sends a registration permission response (RegistrationAccept) to the terminal device 100.

[0065] In some embodiments, after receiving the registration request sent by the terminal device 100, the first network device 200 sends a registration permission response to the terminal device 100 in response to the registration request.

[0066] It can be understood that the above steps S301 to S302 are the process for the first network device 200 to complete camping on the network.

[0067] S303: The terminal device 100 and the first network device 200 complete RRC link establishment.

[0068] In some embodiments, after the terminal device 100 completes registration with the first network device 200, that is, after receiving the registration permission response sent by the first network device 200, it triggers RRC link establishment with the first network device 200 and the link establishment is successful. For the specific process of completing RRC link establishment, reference can be made to the following Figure 3b .

[0069] S304: The first network device 200 sends an RRC link release message to the terminal device 100.

[0070] For example, if the first network device 200 detects that there is no data transmission between the terminal device 100 and the first network device 200 within a preset time after the link establishment is successful, the first network device 200 sends an RRC link release message to the terminal device 100 to disconnect the established RRC link. Alternatively, if the first network device 200 detects that there are no network resources available for allocation to the terminal device 100, the first network device 200 also sends an RRC link release message to the terminal device 100 to disconnect the established RRC link.

[0071] Among them, the cause value field (such as ReleaseCause) in the RRC link release message usually includes cause value parameters, so that the terminal device 100 can make corresponding processing based on the cause value parameters. Among them, the cause value parameters can include releasing the established signalling radio bearer (SRB) and data radio bearer (DRB), cellReselectionPriorities, etc.

[0072] The above is the process of establishing and then disconnecting the RRC link normally. Next, the process of the RRC link being abnormal and resulting in the failure of RRC link establishment in some embodiments will be introduced.

[0073] S305: The terminal device 100 sends a service request to the first network device 200.

[0074] In some embodiments, the terminal device 100 sends a service request to the first network device 200 in response to a communication service trigger event, such as a user using a voice call service such as making a phone call, a user opening a browser application to search, a user making a video call through an instant messaging application, etc.

[0075] In some embodiments, when the communication service trigger event triggers RRC link establishment, while sending a service request to the first network device 200, the terminal device 100 also sends an RRC connection request to the first network device 200.

[0076] It can be understood that at this time, the terminal device 100 has not established an RRC link with the first network device 200 and is in the idle state (RRC_IDLE, simply referred to as the idle state).

[0077] S306: The terminal device 100 and the first network device 200 complete RRC link establishment.

[0078] In some embodiments, a communication service triggering event triggers an RRC connection establishment. The terminal device 100 establishes an RRC connection with the first network device 200, and the connection establishment is successful. Specifically, for the process of completing the RRC connection establishment, reference can be made to the above S303 and the relevant descriptions below Figure 3b and will not be elaborated here.

[0079] S307: The first network device 200 sends a service request grant (SRAccept) to the terminal device 100.

[0080] In some embodiments, after the terminal device 100 and the first network device 200 complete the RRC connection establishment, that is, after the first network device 200 receives the RRC connection establishment complete message (RRCSetupComplete) sent by the terminal device 100, the first network device 200 agrees to the service request of the terminal device 100 and sends a service request grant to the terminal device 100.

[0081] S308: The first network device 200 sends an RRC link release message without parameters to the terminal device 100.

[0082] In some embodiments, due to the number of terminal devices connected to the network device corresponding to the cell where the terminal device 200 currently camps exceeding the number threshold, or the poor network quality of the network device corresponding to the cell where the terminal device 200 currently camps, etc., the RRC link is abnormal. The first network device 200 sends an RRC link release message without parameters to the terminal device 100. That is, the terminal device 100 cannot make corresponding processing according to the parameter information of the received RRC link release message without parameters, such as switching cells, etc.

[0083] S309: The terminal device 100 sends a service request to the first network device 200.

[0084] In some embodiments, since the terminal device 100 receives the RRC link release message without parameters sent by the first network device 200 and cannot make corresponding processing according to the parameter information of the RRC link release message without parameters, the terminal device 100 sends a service request to the first network device 200 again.

[0085] S310: The terminal device 100 and the first network device 200 complete the RRC connection establishment.

[0086] S311: The first network device 200 sends a service request grant to the terminal device 100.

[0087] S312: The first network device 200 sends an RRC link release message without parameters to the terminal device 100.

[0088] Specifically, S310 to S312 may refer to the relevant descriptions in the above S306 to S308, which will not be elaborated here.

[0089] It can be understood that since the terminal device 100 receives the parameterless RRC link release message sent by the first network device 200, the terminal device 100 cannot perform corresponding processing according to the parameter information of the parameterless RRC link release message, such as switching cells, resulting in the terminal device 100 continuously sending service requests to the first network device 200 in the initial cell, that is, repeating the above S309 to S312 until the RRC link is successfully established, and then transmitting communication service data with the first network device 200 through the established RRC link.

[0090] Exemplarily, Figure 3b According to an embodiment of the present application, a schematic diagram of the RRC link establishment process is shown. As Figure 3b shown, the process includes:

[0091] S320: The terminal device 100 sends an RRC connection request to the first network device 200.

[0092] In some embodiments, the RRC connection request includes service indication information, and the service indication information includes one or more parameters of network access technology (such as APN), network layer address (such as PDP address), or service type corresponding to the service initiated by the terminal device 100 (such as voice call service).

[0093] S321: The first network device 200 sends an RRC link establishment message (RRCSetup) to the terminal device 100.

[0094] In some embodiments, the network device 200 may determine whether to establish an RRC link according to the network load situation. If an RRC link is to be established, an RRC link establishment message is sent to the terminal device 100.

[0095] It can be understood that in some other embodiments, if the RRC link is not to be established, the first network device 200 sends a message rejecting the RRC link establishment (RRCReject) to the terminal device 100.

[0096] S322: The terminal device 100 sends an RRC link establishment completion message to the first network device 200.

[0097] It can be understood that after receiving the RRC link establishment message sent by the first network device 200, the terminal device 100 completes the establishment of the RRC link with the first network device 200 and sends an RRC link establishment completion message to the first network device 200.

[0098] In some embodiments, during the establishment process of the RRC link, the establishment of the message radio bearer and the data radio bearer of the virtual channel message is completed. It can be understood that the message radio bearer is used to transmit messages between the terminal device 100 and the first network device 200, such as RRC link establishment messages; the data radio bearer is used to transmit data such as service data.

[0099] In summary, due to abnormal wireless communication links, for example, the network device frequently sends RRC link release messages without parameters, the terminal device cannot perform further processing based on the RRC link release message without parameters, such as switching cells, reducing the network mode, etc., and stays in the initial cell, unable to communicate normally with the network device, thereby affecting the communication services of the terminal device.

[0100] It can be understood that, as described above, the reason for the abnormal wireless communication link may be that the number of terminal devices connected to the network device corresponding to the cell where the terminal device currently resides exceeds the number threshold. Or, the reason for the abnormal wireless communication link may also be that the network quality of the network device corresponding to the cell where the terminal device currently resides is poor, etc. As a result, the network device does not respond to the request of the terminal device within the preset time, or the network device sends a response message without parameters to the terminal device, etc.

[0101] Therefore, the embodiments of the present application provide a communication method. When there is no established wireless communication link between the terminal device and the network device, and the terminal device detects a communication service trigger event, the terminal device sends a wireless communication link connection request to the network device in the currently resident cell, and detects the continuous abnormal number of the wireless communication link within a preset duration. And when the continuous abnormal number is greater than the abnormal number threshold, the terminal device can perform at least one of switching cells and switching network modes, and then establish a wireless communication link with the network device. For example, in some embodiments, when the continuous abnormal number is greater than the abnormal number threshold, the terminal device can first switch cells. If a wireless communication link still cannot be established after switching cells, it means that the abnormal problem has not been solved yet, and the terminal device can perform a network mode switch, and then try to establish a wireless communication link again after switching the network mode.

[0102] Specifically, assume that the terminal device sends a first service request to the first network device in the first cell (i.e., the currently resident cell). If the continuous abnormal number of RRC link abnormal events detected within the preset duration is greater than the first abnormal number threshold, it can be considered that the first network device is abnormal, for example, the number of terminal devices already connected to the first network device exceeds the number threshold. Furthermore, the terminal device will perform a cell switch, that is, determine the second cell and send a second service request to the second network device in the second cell.

[0103] It can be understood that the network modes corresponding to the first network device and the second network device are the same. For example, both the first network device and the second network device are gNodeBs, and the corresponding network mode is the 5G network. The first cell and the second cell can correspond to the same network device, that is, the first network device and the second network device are the same network device. The first cell and the second cell can also correspond to different network devices.

[0104] Furthermore, if the number of consecutive anomalies is greater than the second anomaly threshold, it indicates that the anomaly problem has not been resolved after the terminal device switches cells. Then, it can be considered that the cause of the anomaly is the poor network quality of the second network device, and the terminal device switches the network mode, that is, determines the third cell and sends a third service request to the third network device in the third cell. It can be understood that the network mode corresponding to the third network device is lower than the network mode corresponding to the second network device. For example, the second network device is a gNodeB, and the corresponding network mode is the 5G network, and the third network device is an eNodeB, and the corresponding network mode is the 4G network.

[0105] In addition, in some embodiments, the terminal device can also attempt to establish a link after switching the network mode when the number of consecutive anomalies is greater than the anomaly threshold. If the link establishment is still unsuccessful after switching the network mode, the terminal device can then attempt to switch cells to establish a link. For example, assume that the terminal device sends a first service request to the first network device in the first cell and detects that the number of consecutive anomalies of the RRC link is greater than the first anomaly threshold within a preset time duration, and the terminal device switches the network mode. Furthermore, if the number of consecutive anomalies is greater than the second anomaly threshold, the terminal device switches cells.

[0106] In addition, in some other embodiments, the terminal device can also attempt to establish a link after switching cells when the number of consecutive anomalies is greater than the anomaly threshold. If the link establishment is still unsuccessful after switching cells, the terminal device can then attempt to switch network devices to establish a link. If the link establishment is still unsuccessful after switching network devices, the terminal device can then attempt to switch the network mode to establish a link.

[0107] Specifically, assume that the terminal device sends a first service request to the first network device in the first sub-cell and detects that the number of consecutive anomalies of the RRC link is greater than the first anomaly threshold within a preset time duration. The terminal device switches cells, that is, sends a first service request to the first network device in the second sub-cell. It can be understood that the second sub-cell and the first sub-cell correspond to the same network device, that is, the first network device.

[0108] Further, if the number of consecutive anomalies is greater than the second anomaly number threshold, the terminal device performs a network device handover, that is, it sends a second service request to the second network device in the third sub-cell. It can be understood that the network modes corresponding to the first network device and the second network device are the same. For example, both the first network device and the second network device are gNodeBs, and the corresponding network mode is the 5G network.

[0109] Further, if the number of consecutive anomalies is greater than the third anomaly number threshold, the terminal device performs a network mode handover, that is, it determines the fourth sub-cell and sends a third service request to the third network device in the fourth sub-cell. It can be understood that the network mode corresponding to the third network device is lower than the network mode corresponding to the second network device. For example, the second network device is a gNodeB, the corresponding network mode is the 5G network, and the third network device is an eNodeB, and the corresponding network mode is the 4G network.

[0110] In addition, in some other embodiments, the terminal device can also perform a link establishment attempt after simultaneously switching the network mode and the cell when the number of consecutive anomalies is greater than the anomaly number threshold. Specifically, assume that the terminal device sends a service request to the first network device in the first cell, and within a preset time period, it detects that the number of consecutive anomalies of the RRC link is greater than the fourth anomaly number threshold, and the terminal device performs a handover of the cell and the network mode.

[0111] It can be understood that the wireless communication link anomalies include but are not limited to: the network device does not respond to the wireless access connection request of the terminal device within a preset time, the network device sends a response message without parameters (such as an RRC link release message, etc.), a wireless link failure, no data radio bearer, etc.

[0112] It can be understood that the "response message without parameters" in the embodiments of the present application means that the response message does not carry a parameter of the cause value, that is, the cause value field of the response message is empty. And in the present application, the description of each message (request and response message, etc.) for the interaction between the terminal device and the network device is only an example and does not serve as the only representation form of each message. The description of each response message can also refer to the description in communication protocols such as the 3rd generation partnership project (3GPP) protocol.

[0113] In some embodiments, the terminal device can implement cell handover in the following manner: set the first cell as an inaccessible cell (bar cell), and perform cell reselection and handover in the cells other than the inaccessible cell.

[0114] In some embodiments, the methods for reducing the network mode include:

[0115] First, disable the first network band or the first network capability. For example, disable the NR band or the NR capability.

[0116] Second, disconnect from the first network device, perform cell search in the second network band, and determine the third cell. Specifically, during the cell search process, the terminal device reads the system information of each cell, such as parameters like reference signal received power (RSRP) and reference signal received quality (RSRQ). Based on the system information of each cell, the searched cells are sorted by priority, and the cell with the highest priority is taken as the third cell.

[0117] Then, send a service request to the third network device in the third cell.

[0118] It can be understood that in the communication method provided by the embodiments of the present application, the terminal device can detect the number of consecutive anomalies of the wireless communication link within a preset duration, and perform cell handover and / or operation of reducing the network mode based on the number of consecutive anomalies. So that even when the wireless communication link has consecutive anomalies, the terminal device can still communicate with the network device normally, thereby maintaining the communication service of the terminal device.

[0119] Specifically, when the number of consecutive anomalies of the terminal device is greater than the anomaly number threshold, the cell is switched first. If the wireless communication link still cannot be established after switching the cell, the network mode is then switched, and an attempt is made to establish the wireless communication link again after switching the network mode. It can be understood that when the terminal device switches the cell first, it does not reduce the network mode and still attempts to connect to the network device corresponding to the first network mode. When the anomaly problem still cannot be solved after switching the cell, the network mode is reduced, which can ensure that the user preferentially uses the network of the higher network mode.

[0120] To better understand the technical solutions of the embodiments of the present application, taking the RRC link anomaly as an example of the wireless communication link anomaly, and taking the solution that when the number of consecutive anomalies of the terminal device is greater than the set threshold, the cell is switched first and then the network mode is switched as an example, some technical solutions of the present application will be introduced in detail below.

[0121] Figure 4a According to the embodiments of the present application, a flowchart of a communication method is shown. It can be understood that Figure 4a The execution subject of each step of the shown process is the terminal device 100. For the sake of simplicity of description, the execution subject of each step will not be repeatedly described below when introducing Figure 4a each step of the shown process. As Figure 4a shown, the process includes but is not limited to the following steps:

[0122] S401: In response to a communication service trigger event, send a first service request to a first network device.

[0123] Optionally, the terminal device may send the first service request to the first network device in a first cell.

[0124] The communication service trigger event detected by the terminal device may be that the user makes a voice call using the voice call service, the user opens a browser application to search, the user makes a video call through an instant messaging application, and so on. In response to the communication service trigger event, the terminal device sends a first service request to the first network device according to the first cell where it camps.

[0125] In some embodiments, the first cell may be a cell that the terminal device camps on after performing cell search in a first network frequency band (such as the NR frequency band) when the terminal device powers on or a radio link failure occurs. Specifically, during the cell search process, the terminal device reads the system information of each cell, such as parameters like RSRP and RSRQ, sorts the searched cells according to the system information of each cell, and takes the cell with the highest priority as the first cell.

[0126] It can be understood that at this time, the terminal device 100 has completed network registration and has not established an RRC link with the first network device 200, and is in the idle state. Specifically, reference may also be made to the relevant description above. Figure 3a of the relevant description.

[0127] S402: Detect a first RRC link abnormal event and record the number of consecutive abnormal occurrences within a first duration.

[0128] For example, the terminal device determines whether an RRC link abnormal situation occurs based on the response message sent by the first network device. If an RRC link abnormal situation occurs, it is recorded as one RRC link abnormal event.

[0129] Among them, the RRC link abnormal event includes but is not limited to: the first network device does not respond to the RRC connection request of the terminal device within a preset time, or the first network device sends a response message without parameters to the terminal device, radio link failure, no data radio bearer, etc. Among them, the response message may include: reject RRC connection establishment message, RRC link release message, reject service request message (SRReject), and so on.

[0130] In some embodiments, the number of consecutive anomalies within the first time period can be determined as follows: If the current RRC link anomaly is the first RRC link anomaly, the time when the current RRC link anomaly occurs is taken as the start time of the first time period, and the number of consecutive anomalies is set to 1. If a second RRC link anomaly is detected within the first time period, the number of consecutive anomalies is incremented by 1, and so on, until the end time of the first time period to end the counting. It can be understood that the interval length of the first time period can be a preset first time period T1, such as 5 minutes (min), 10 min, etc. It can be understood that the first time period T1 can be a time period greater than 0.

[0131] In some other embodiments, if a first RRC link anomaly event is detected within the anomaly time threshold for the terminal device to send a first service request, it is recorded as an RRC link anomaly event. That is, if the time interval between the occurrence time of the first RRC link anomaly event and the sending time of the corresponding first service request is less than or equal to the anomaly time threshold, the first RRC link anomaly event is recorded as an RRC link anomaly event.

[0132] If the time interval between the occurrence time of the detected RRC link anomaly event and the sending time of the corresponding first service request is greater than the anomaly time threshold, the first RRC link anomaly event is not recorded as an RRC link anomaly event.

[0133] It can be understood that since there may be a certain delay in the network device's response to the message sent by the terminal device, the RRC link anomaly event can be determined by setting the anomaly time threshold.

[0134] It can be understood that the anomaly time threshold can be a preset anomaly time threshold T2, such as 2 seconds (s), 5 s, etc. It can be understood that the anomaly time threshold T2 can be a time period greater than 0 and less than the first time period T1. Specifically, the value range of the anomaly time threshold T2 can be any value between 200 milliseconds and 5000 milliseconds, for example, 200 milliseconds, 2000 milliseconds, 3000 milliseconds, etc.

[0135] Exemplarily, it can be implemented by a timer with a preset time length. For example, if the current RRC link anomaly event is the first RRC link anomaly event, a 5 min timer and a counter are started, and the count value of the counter is set to 1. If a second RRC link anomaly event is detected within 5 min, the number of consecutive anomalies is incremented by 1, and so on, until the timer ends its timing. Among them, the timer can be, for example, a T3517 timer, and the present application does not make a specific limitation on the model of the timer.

[0136] In some other embodiments, if the time interval between the occurrence times of two consecutive RRC link abnormal events detected by the terminal device is greater than the interval time threshold, it indicates that these two RRC link abnormal events may not occur consecutively. That is to say, there may be a normal RRC connection establishment and data transmission process between these two RRC link abnormal events. Then the terminal device re - records the number of consecutive abnormalities within the first duration.

[0137] Specifically, it includes: If the current RRC link abnormal event is the i - th RRC link abnormal event, where i is an integer greater than 1, determine the time interval between the i - th RRC link abnormal event and the (i - 1) - th RRC link abnormal event. If the time interval is less than the interval time threshold, then increment the number of consecutive abnormalities by 1. If the time interval is greater than or equal to the interval time threshold, then regard the i - th RRC link abnormal event as the first RRC link abnormal event. That is, take the occurrence time of the current RRC link abnormal event as the start time of the first duration, and set the number of consecutive abnormalities to 1. It can be understood that the interval time threshold can be a pre - set interval time threshold T3, such as 1s, 2s, etc. Specifically, the value range of the interval time threshold T3 can be any value between 200 milliseconds and 2000 milliseconds. For example, 200 milliseconds, 1000 milliseconds, 1500 milliseconds, and so on.

[0138] Specifically, the interaction process between the terminal device and the network device during the calculation of the number of consecutive abnormalities within the first duration can refer to Figure 4b the interaction schematic diagram shown.

[0139] As Figure 4b shown, the time interval between the first network device 200 sending the first parameter - less RRC link release message to the terminal device 100 and the first network device 200 sending the n - th parameter - less RRC link release message to the terminal device 100 is less than or equal to the first duration T1.

[0140] The time interval between the first network device 200 sending the first service request to the terminal device 100 and the first network device 200 sending the first RRC link release message without parameters to the terminal device 100 is less than or equal to the abnormal time threshold T2. The time interval between the first network device 200 sending the second service request to the terminal device 100 and the first network device 200 sending the second RRC link release message without parameters to the terminal device 100 is less than or equal to the abnormal time threshold T2. And so on, the time interval between the first network device 200 sending the nth service request to the terminal device 100 and the first network device 200 sending the nth RRC link release message without parameters to the terminal device 100 is less than or equal to the abnormal time threshold T2. That is to say, the time interval between the first network device 200 sending each service request to the terminal device 100 and the first network device 200 sending each RRC link release message without parameters to the terminal device 100 is less than or equal to the abnormal time threshold T2.

[0141] Moreover, the time interval between the first network device 200 sending the first RRC link release message without parameters to the terminal device 100 and the first network device 200 sending the second RRC link release message without parameters to the terminal device 100 is less than the interval time threshold T3. That is to say, the time interval between two adjacent times when the first network device 200 sends an RRC link release message without parameters to the terminal device 100 is less than the time interval threshold T3.

[0142] S403: Determine whether the number of consecutive anomalies is greater than the first anomaly count threshold.

[0143] If the judgment result is no, indicating that the number of consecutive anomalies has not reached the first anomaly count threshold, then execute step S404 to send a service request to the first network device in the first cell.

[0144] In some embodiments, if the judgment result is no, indicating that the number of consecutive anomalies has reached the first anomaly count threshold, and the terminal device 100 may still be unable to transmit service data while continuing to camp on the first cell, then execute step S405 to determine the second cell and send a service request to the second network device.

[0145] Optionally, when the number of consecutive anomalies reaches the first anomaly count threshold, the terminal device 100 determines the second cell and sends a second service request to the second network device.

[0146] Optionally, when the number of consecutive anomalies is greater than K, the terminal device 100 determines the second cell and sends a second RRC connection request to the second network device. Among them, the value range of K can be any integer within 1 to 20. Specifically, the value of K can be 2, 3, 4, 5, 6, 7, 8, 9, etc.

[0147] In some embodiments, corresponding to the terminal device 100 sending the first RRC connection request to the first network device 200 for K times, the consecutive abnormal times being greater than K may be: all K first response messages received within the first time period are response messages without parameters. It can be understood that the number of first response messages received within the first time period is equal to the number of times the first RRC connection request is sent.

[0148] In other embodiments, corresponding to the terminal device 100 sending the first RRC connection request to the first network device 200 for M times, the consecutive abnormal times being greater than K may be: all K first response messages received within the first time period are response messages without parameters. Wherein, K is less than M, and the value range of M may be any integer within 2 to 25. Specifically, the value of M may be 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, etc. It can be understood that the number of first response messages received within the first time period is less than the number of times the first RRC connection request is sent.

[0149] It can be understood that the first response message is a response message without parameters.

[0150] It can be understood that in some embodiments, different types of RRC link abnormal events can be counted separately. For example, the consecutive abnormal times of each type of RRC link abnormal event are recorded respectively. If the consecutive abnormal times of any type of RRC link abnormal event are greater than the first abnormal times threshold, corresponding operations are performed.

[0151] In other embodiments, different types of RRC link abnormal events can be counted together. For example, if the types corresponding to the second RRC link abnormal event and the first RRC link abnormal event are different, the consecutive abnormal times are still incremented by 1. If the consecutive abnormal times of the RRC link abnormal event are greater than the first abnormal times threshold, corresponding operations are performed.

[0152] In other embodiments, some types of RRC link abnormal events can be counted together. For example, the situations where the terminal device receives response messages without parameters sent by the network device, such as rejecting RRC connection establishment messages, RRC link release messages, rejecting service request messages, etc., are counted together.

[0153] Specifically, if the first RRC link abnormal event is that the terminal device receives an RRC link release message without parameters sent by the network device, and the second RRC link abnormal event is that the terminal device receives a rejected RRC connection establishment message without parameters sent by the network device, the consecutive abnormal times are still incremented by 1.

[0154] This application does not make specific restrictions on the counting method of consecutive abnormal times.

[0155] Optionally, when the number of consecutive anomalies is greater than the first sub-anomaly number threshold, the terminal device 100 performs a cell handover. When the number of consecutive anomalies is greater than the second sub-anomaly number threshold, the terminal device 100 performs a cell handover again. That is, when the number of consecutive anomalies reaches the set threshold, multiple rounds of cell handovers are performed. It can be understood that multiple rounds of cell handovers are performed to ensure that the user uses a network with a higher network mode, thereby guaranteeing the user experience.

[0156] S404: Send a first service request to the first network device in the first cell.

[0157] The terminal device determines that the number of consecutive anomalies has not reached the first anomaly number threshold and continues to send a first service request to the first network device in the first cell.

[0158] S405: Determine a second cell and send a second service request to the second network device.

[0159] The terminal device determines that the number of consecutive anomalies has reached the first anomaly number threshold, performs a cell handover, that is, determines a second cell and sends a service request to the second network device. It can be understood that the second network device corresponds to the second cell.

[0160] Optionally, when the number of consecutive anomalies reaches the first anomaly number threshold, the terminal device 100 determines a second cell and sends a second service request to the second network device.

[0161] In some embodiments, cell handover is implemented in the following manner: Set the first cell as an inaccessible cell (bar cell), perform cell reselection and handover within the cells other than the inaccessible cell, and determine the second cell.

[0162] In other embodiments, the method of setting the first cell as an inaccessible cell may be to place the cell identifier of the first cell in the access blacklist. When the terminal device 100 performs cell reselection, it does not select the cell in the access blacklist.

[0163] It can be understood that in the embodiments of the present application, the cell indicated by the cell identifier in the access blacklist is a prohibited access cell. The cell identifier may be the identifier of the cell or the identifier of the frequency point corresponding to the cell.

[0164] In some other embodiments, a preset duration for the first cell to be an inaccessibile cell may also be set. After the preset duration since the first cell is set as an inaccessibile cell, the first cell is set as an accessible cell. In this way, the first cell is not set as an inaccessibile cell for a long time, and can be re-selected for access when the signal quality of the first cell improves or the resource scheduling is normal, so as to make full use of network resources. The preset duration is pre-set, for example, 30 min, and the preset duration can be modified by the network device according to actual needs. The present application does not limit the specific value of the preset duration.

[0165] It can be understood that if a network device corresponds to one cell, the second network device corresponding to the second cell and the first network device corresponding to the first cell are different network devices. If a network device corresponds to multiple cells, the second network device corresponding to the second cell and the first network device corresponding to the first cell may be different network devices or the same network device. The present application does not make specific limitations on this.

[0166] S406: Detect a second RRC link abnormal event and record the consecutive abnormal times within the second duration.

[0167] After the terminal device performs cell handover, if a second RRC link abnormal event is still detected, continue to record the consecutive abnormal times within the second duration.

[0168] Among them, the RRC link abnormal event includes but is not limited to: the second network device does not respond to the RRC connection request of the terminal device within a preset time, or the second network device sends a response message without parameters to the terminal device, radio link failure, no data radio bearer, etc. Among them, the response message may include: reject RRC connection establishment message, RRC link release message, reject service request message, etc.

[0169] In some embodiments, the determination of the consecutive abnormal times within the second duration may refer to the relevant description in the foregoing step S402.

[0170] Among them, the second duration in step S406 may be the first duration T1 in the foregoing step S402, that is, the abnormal times in step S406 can be counted following the above step S402.

[0171] Alternatively, in some other embodiments, after the terminal device performs cell handover, if an RRC link abnormal event is still detected, the consecutive abnormal times may also be re-recorded. That is, determine that the second duration is the second duration T4, and record the consecutive abnormal times within the second duration T4. Furthermore, the abnormal times in step S406 are counted starting from zero. That is to say, the second duration T4 may be equal to the above first duration T1 or may not be equal to the above first duration T1. The present application does not make limitations on this.

[0172] Among them, the number of consecutive anomalies recorded within the second time period T4 can refer to the relevant description in S402 above, and the number will not be elaborated.

[0173] S407: Determine whether the number of consecutive anomalies is greater than the second anomaly count threshold.

[0174] If the judgment result is negative, indicating that the number of consecutive anomalies has not reached the second anomaly count threshold, then execute step S408 to send a second service request to the second network device in the second cell.

[0175] In some embodiments, if the judgment result is negative, indicating that the number of consecutive anomalies has reached the second anomaly count threshold, and it may still be impossible to transmit service data when the terminal device continues to send a second service request to the second network device, then execute step S409 to determine the third cell and send a third service request to the third network device.

[0176] Optionally, when the number of consecutive anomalies reaches the first anomaly count threshold, the terminal device 100 determines the third cell and sends a third service request to the third network device.

[0177] Optionally, when the number of consecutive anomalies is greater than P, the terminal device 100 determines the third cell and sends a third RRC connection request to the third network device. Among them, the value range of P can be any integer within 1 to 20. Specifically, the value of P can be 2, 3, 4, 5, 6, 7, 8, 9, etc.

[0178] In some embodiments, corresponding to the terminal device 100 sending P second RRC connection requests to the first network device 200, the number of consecutive anomalies being greater than P can be: all P second response messages received within the second time period are response messages without parameters. It can be understood that the number of second response messages received within the second time period is equal to the number of times the second RRC connection request is sent.

[0179] In other embodiments, corresponding to the terminal device 100 sending Q second RRC connection requests to the first network device 200, the number of consecutive anomalies being greater than P can be: all P second response messages received within the second time period are response messages without parameters. Among them, P is less than Q, and the value range of Q can be any integer within 2 to 25. Specifically, the value of Q can be 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, etc. It can be understood that the number of second response messages received within the second time period is less than the number of times the second RRC connection request is sent.

[0180] It can be understood that the second response message is a response message without parameters.

[0181] It can be understood that if in the above S406, the number of consecutive anomalies within the second time period is recorded as continuing to record the number of consecutive anomalies within the first time period, then the second anomaly count threshold is greater than the first anomaly count threshold. If in the above S406, the number of consecutive anomalies within the second time period is recorded as re - recording the number of consecutive anomalies within the second time period, then the second anomaly count threshold can be equal to the first anomaly count threshold or can be not equal to the first anomaly count threshold.

[0182] S408: Send a second service request from the second cell to the second network device.

[0183] The terminal device determines that the number of anomalies has not reached the second anomaly count threshold and continues to send service requests to the second network device in the second cell.

[0184] S409: Determine a third cell and send a third service request to the third network device.

[0185] The terminal device determines that the number of anomalies has reached the second anomaly count threshold, reduces the network mode, that is, sends a third service request to the third network device in the third cell.

[0186] Optionally, when the number of consecutive anomalies reaches the first anomaly count threshold, the terminal device 100 determines a third cell and sends a third service request to the third network device.

[0187] It can be understood that the network mode of the third network device is lower than that of the first network device. For example, the first network device is a gNodeB and the third network device is an eNodeB.

[0188] Exemplarily, when the first network device is a gNodeB and the third network device is an eNodeB, as Figure 4c shown, the network signal icon on the display interface of the terminal device 100 can be switched from the 5G icon 40a to the 4G icon 40b.

[0189] Specifically, the method for the terminal device to reduce the network mode includes:

[0190] (1) Disable the first network band or disable the first network capability. For example, disable the NR band or disable the NR capability.

[0191] (2) Disconnect the connection with the second network device, perform cell search in the second network band (such as the TDD band or the FDD band), and determine the third cell. Specifically, the terminal device 100 reads the system information of each cell during the cell search process, such as parameters like RSRP and RSRQ, sorts the searched cells according to the system information of each cell, and takes the cell with the highest priority as the third cell.

[0192] (3) Sending a service request to a third network device in the third cell.

[0193] It can be understood that in other embodiments, according to actual needs, the above Figure 4a The steps shown can be combined, deleted or replaced with other steps that are conducive to achieving the purpose of this application. For example, the above step S402 can be split into two steps, and this application does not limit this.

[0194] In some embodiments, after the terminal device lowers the network standard, the network status of the second network is evaluated. If a network abnormality occurs, the lowering of the network standard is cancelled.

[0195] It can be understood that since sending a service request will trigger RRC link establishment, that is, sending a service request will also send an RRC connection request. Figure 4a The first service request in the description may also be a first RRC connection request, the second service request may also be a second RRC connection request, and the third service request may also be a third RRC connection request. This application does not limit this.

[0196] For example, Figure 5 According to an embodiment of the present application, a schematic diagram of a process of evaluating the network status of a second network by a terminal device is shown. It can be understood that Figure 5 Each step of the process shown in the figure is performed by the terminal device. Figure 5 The execution entities of each step will not be described repeatedly in the steps of the process shown.

[0197] like Figure 5 As shown, the process includes:

[0198] S501: Send a third service request to a third network device in a third cell.

[0199] S502: Determine whether a network anomaly occurs.

[0200] If the judgment result is yes, it means that a network abnormality occurs in the third network device, and then step S503 is executed to release the disabling of the first network frequency band or the first network capability, and resume sending the first service request to the network device corresponding to the first network.

[0201] In some embodiments, if the judgment result is no, indicating that the third network device has no network abnormality, step S504 is executed to communicate with the third network device in the third cell.

[0202] Among them, network abnormalities include but are not limited to: the network signal corresponding to the third network device is lower than the signal threshold, or the following occurs: Figure 4a The RRC link shown is continuously abnormal.

[0203] S503: Unbanning the first network frequency band or the first network capability, and resuming sending the first service request to the network device corresponding to the first network.

[0204] After the terminal device determines that a network anomaly occurs in the second network, in order to ensure the user's online experience, the reduction of the network standard is cancelled, that is, the first service request is resumed to the fourth network device corresponding to the first network.

[0205] It can be understood that the fourth network device corresponds to the first network standard, and can be the same as the first network device or the second network device, or can be other network devices corresponding to the first network standard, and this application does not impose any restrictions on this.

[0206] Specifically, canceling the reduction of the network standard may include: releasing the disabling of the first network frequency band or the first network capability, etc.

[0207] It can be understood that after the second network has a network anomaly, the first service request is sent to the fourth network device corresponding to the first network, so that the user can resume using the network of the first network standard, so as to ensure that the user uses a network of a higher network standard, thereby ensuring the user's experience. For example, if the 4G network has a network anomaly, try to resume the use of the 5G network.

[0208] It can be understood that in some embodiments, if the third network device has a network anomaly, the terminal device can also disconnect the communication connection with the third network device and establish a communication connection with the fifth network device, and the network standard corresponding to the fifth network device is lower than the network standard corresponding to the third network device. For example, the network standard corresponding to the third network device is a 4G network, and the network standard corresponding to the fifth network device is a 3G network. In other words, if the third network device has a network anomaly, the terminal device can also continue to execute Figure 4a The process shown.

[0209] It can be understood that since the network device corresponding to the first network standard has continuously detected the abnormal RRC link event before connecting to the network device corresponding to the second network standard, if the service request is restored to the network device corresponding to the first network, the abnormal RRC link event may still be continuously detected.

[0210] Therefore, after a network anomaly occurs in the second network, the service request is not restored to the network device corresponding to the first network, but an attempt is made to establish a communication connection with the network device corresponding to the third network standard. It can be understood that through this method, the success rate of completing the RRC link establishment and data transmission is higher.

[0211] S504: Communicate with a third network device in a third cell.

[0212] If the terminal device determines that there is no network anomaly in the second network, it continues to communicate with the third network device in the third cell.

[0213] To better understand the technical solutions of the embodiments of the present application, the interaction processes corresponding to different types of RCC link anomalies are introduced below with reference to the accompanying drawings.

[0214] Embodiment 1

[0215] Taking the RRC link anomaly that the first network device does not respond to the RRC connection request of the terminal device within a preset time as an example, the interaction process of the RRC link anomaly between the terminal device and the network device is introduced below.

[0216] Exemplarily, Figure 6 According to the embodiments of the present application, a schematic diagram of the interaction process of the RRC link anomaly between the terminal device and the network device is shown.

[0217] As Figure 6 shown, the process includes:

[0218] S601: The terminal device 100 sends a registration request to the first network device 200 to the first first network device 2000.

[0219] S602: The first network device 200 sends a registration permission response to the terminal device 100.

[0220] S603: The terminal device 100 and the first network device 200 complete the RRC link establishment.

[0221] S604: The first network device 200 sends an RRC link release message to the terminal device 100.

[0222] Specifically, S601 to S604 can refer to the relevant descriptions in S301 to S304 above and will not be elaborated here.

[0223] S605: The terminal device 100 sends a first service request to the first network device 200.

[0224] The terminal device 100 sends a first service request to the first network device 200 in response to a communication service trigger event, such as a user using a voice call service, a user opening a browser application for searching, a user making a video call through an instant messaging application, etc.

[0225] S606: The terminal device 100 sends a first RRC connection request to the first network device 200.

[0226] The communication service triggering event triggers the RRC connection establishment. While the terminal device 100 sends a first service request to the first network device 200, it also sends a first RRC connection request to the first network device 200.

[0227] S607: The terminal device 100 determines that the exception is the timeout of the T300 timer.

[0228] It can be understood that the T300 timer is a timer started by the terminal device 100 when the terminal device 100 sends a first RRC connection request to the first network device 200, and the timer is a timer with a preset time. If the terminal device 100 receives a first RRC link establishment message or a first RRC connection establishment rejection message sent by the first network device 200 within the preset time, the T300 timer is turned off.

[0229] It can be understood that the timeout of the T300 timer indicates that the first network device 200 does not respond to the first RRC connection request of the terminal device 100 within the preset time.

[0230] S608: The terminal device 100 performs a cell handover corresponding to the continuous exception count being greater than the first exception count threshold.

[0231] The terminal device 100 records the continuous exception count within the first duration. Corresponding to the continuous exception count being greater than the first exception count threshold, a cell handover is performed. It can be understood that the continuous exception count is the number of times the T300 timer timeout is continuously detected.

[0232] In some embodiments, the continuous exception count can be determined in the following manner:

[0233] (1) If the current T300 timer timeout is the first T300 timer timeout, the time when the current T300 timer timeout occurs is used as the start time of the first duration, and the continuous exception count is set to 1. It can be understood that the length of the first duration can be preset, for example, 5 min.

[0234] (2) If the current T300 timer timeout is the i-th T300 timer timeout, where i is an integer greater than 1, the time interval between the i-th T300 timer timeout and the (i - 1)-th T300 timer timeout is determined. If the time interval is less than the interval time threshold, the continuous exception count is incremented by 1. If the time interval is greater than or equal to the interval time threshold, the i-th T300 timer timeout is used as the first T300 timer timeout, that is, the time when the current T300 timer timeout occurs is used as the start time of the first duration, and the continuous exception count is set to 1. It can be understood that the interval time threshold can be preset, for example, 2 s.

[0235] For specific descriptions related to the cell handover, reference can be made to the above Figure 4aFor the relevant descriptions in [reference], they will not be elaborated in this application.

[0236] Taking the example of cell handover where the handover target cell and the previous cell are served by the same network device (the first network device 200), S609 to S612 will be described below.

[0237] It can be understood that in the above S601 to S608, the interaction between the terminal device 100 and the first network device 200 is carried out in the first cell. In the following S609 to S612, the communication between the terminal device 100 and the first network device 200 is carried out in the second cell.

[0238] S609: The terminal device 100 sends a second service request to the first network device 200.

[0239] S610: The terminal device 100 sends a second RRC connection request to the first network device 200.

[0240] Corresponding to the case where the consecutive abnormal times are greater than the first abnormal time threshold, after the terminal device 100 performs cell handover, it sends a second service request to the first network device 200 again.

[0241] It can be understood that when the terminal device 100 sends a second service request to the first network device 200, it also sends a second RRC connection request to the first network device 200.

[0242] S611: The terminal device 100 determines that the abnormality is the timeout of the T300 timer.

[0243] It can be understood that S609 to S611 can refer to the relevant descriptions in the above S605 to S607, and will not be elaborated here.

[0244] S612: When the consecutive abnormal times of the terminal device 100 are greater than the second abnormal time threshold, it reduces the network mode.

[0245] The terminal device 100 continues to record the consecutive abnormal times within the first duration. When the consecutive abnormal times are greater than the second abnormal time threshold, it reduces the network mode. It can be understood that the consecutive abnormal times are the number of times when the timeout of the T300 timer is continuously detected. The method of continuing to record the consecutive abnormal times within the first duration can also refer to the previous step S608.

[0246] S613: The terminal device 100 sends a third service request to the second network device 300.

[0247] It can be understood that the network mode corresponding to the second network device 300 is lower than that corresponding to the first network device 200.

[0248] Embodiment 2

[0249] Taking the case where the RRC link is abnormal and the first network device sends a rejection service request without parameters to the terminal device as an example, the interaction process between the terminal device and the network device when the RRC link is abnormal is introduced.

[0250] Exemplarily, Figure 7 According to an embodiment of the present application, a schematic diagram of the interaction process between a terminal device and a network device when the RRC link is abnormal is shown. After the terminal device 100 executes the above Figure 6 shown steps S601 to S604, the interaction process after detecting a communication service trigger event is as Figure 7 shown, specifically including:

[0251] S701: The terminal device 100 sends a first service request to the first network device 200.

[0252] In response to the communication service trigger event, the terminal device 100 sends a first service request to the first network device 200.

[0253] In some embodiments, the communication service trigger event triggers RRC link establishment. When the terminal device 100 sends a first service request to the first network device 200, it also sends a first RRC connection request to the first network device 200.

[0254] S702: The terminal device 100 and the first network device 200 complete RRC link establishment.

[0255] In some embodiments, the communication service trigger event triggers RRC link establishment. The terminal device 100 and the first network device 200 perform RRC link establishment and complete it. Specifically, the process of completing RRC link establishment can refer to the relevant description in S303 above and will not be elaborated here.

[0256] S703: The first network device 200 sends a first rejection service request message without parameters to the terminal device 100.

[0257] After the terminal device 100 and the first network device 200 complete RRC link establishment, that is, after the first network device 200 receives the RRC link establishment completion message sent by the terminal device 100, it sends a rejection service request without parameters to the terminal device 100.

[0258] S704: The terminal device 100 determines that the exception is a rejection service request message without parameters.

[0259] After the terminal device 100 receives the first rejection service request message without parameters sent by the first network device 200, it determines that the RRC link exception event is that the first network device sends a rejection service request message without parameters to the terminal device.

[0260] S705: The terminal device 100 performs a cell handover corresponding to the number of consecutive anomalies being greater than the first anomaly number threshold.

[0261] The terminal device 100 records the number of consecutive anomalies within the first duration, and performs a cell handover corresponding to the number of consecutive anomalies being greater than the first anomaly number threshold. It can be understood that the number of consecutive anomalies is the number of times of continuously determining that the anomaly is a parameterless rejected service request.

[0262] It can be understood that in some embodiments, different types of rejected service request messages can be counted separately. For example, the number of consecutive anomalies of each type of rejected service request message (such as SRReject#9, SRReject#10, SRReject#111, etc.) is recorded respectively. If the number of consecutive anomalies of any type of rejected service request message is greater than the first anomaly number threshold, the corresponding operation is executed.

[0263] In some other embodiments, different types of rejected service request messages can be counted together. For example, if the types corresponding to the second rejected service request message and the first rejected service request message are different, the number of consecutive anomalies is still incremented by 1; if the number of consecutive anomalies is greater than the first anomaly number threshold, the corresponding operation is executed. This application does not make specific restrictions on this.

[0264] Specifically, reference can be made to the relevant description in S608 above Figure 6 and this application will not elaborate here.

[0265] The following takes the example of switching cells, and the cell after the handover and the previous cell corresponding to the same network device (the first network device 200) to describe S706 to S710.

[0266] It can be understood that in the above S701 to S705, the interaction between the terminal device 100 and the first network device 200 is carried out in the first cell. In the following S706 to S710, the communication between the terminal device 100 and the first network device 200 is carried out in the second cell.

[0267] S706: The terminal device 100 sends a second service request to the first network device 200.

[0268] Corresponding to the number of consecutive anomalies being greater than the first anomaly number threshold, after the terminal device 100 performs a cell handover, it sends a second service request to the first network device 200 again.

[0269] S707: The terminal device 100 and the first network device 200 complete the RRC connection establishment.

[0270] S708: The first network device 200 sends a second parameterless rejected service request message to the terminal device 100.

[0271] S709: The terminal device 100 determines that the exception is a reject service request message without parameters.

[0272] It can be understood that S706 to S709 can refer to the relevant descriptions in the above S701 to S704, and will not be elaborated here.

[0273] S710: When the consecutive exception count of the terminal device 100 is greater than the second exception count threshold, the network mode is reduced.

[0274] The terminal device 100 continues to count the consecutive exception count within the first duration. When the consecutive exception count is greater than the second exception count threshold, the network mode is reduced. It can be understood that the consecutive exception count is the number of times that the RRC link exception event is continuously determined to be a reject service request message without parameters.

[0275] Specifically, reference can be made to the relevant description in S612 above Figure 6 in this application, and will not be elaborated here.

[0276] S711: The terminal device 100 sends a third service request to the second network device 300.

[0277] It can be understood that the network mode corresponding to the second network device 300 is lower than the network mode corresponding to the first network device 200.

[0278] Embodiment 3

[0279] Taking the RRC link exception as an example where the first network device sends a reject RRC connection establishment message without parameters to the terminal device, the interaction process of the RRC link exception between the terminal device and the network device is introduced below.

[0280] Exemplarily, Figure 8 According to the embodiment of the present application, a schematic diagram of the interaction process of the RRC link exception between the terminal device and the network device is shown.

[0281] After the terminal device 100 executes the steps S601 to S604 shown above Figure 6 the interaction process after detecting the communication service trigger event is as shown in Figure 8 shown below, and specifically includes:

[0282] S801: The terminal device 100 sends a first service request to the first network device 200.

[0283] S802: The terminal device 100 sends a first RRC connection request to the first network device 200.

[0284] In response to the communication service trigger event, the terminal device 100 sends a first service request to the first network device 200.

[0285] It can be understood that when the communication service triggering event triggers the RRC connection establishment, while the terminal device 100 sends a first service request to the first network device 200, it also sends a first RRC connection request to the first network device 200.

[0286] S803: The first network device 200 sends a first parameterless rejection RRC connection establishment message to the terminal device 100.

[0287] After receiving the first RRC connection request sent by the terminal device 100, the first network device 200 sends a first parameterless rejection RRC connection establishment message to the terminal device 100.

[0288] S804: The terminal device 100 determines that the exception is a first parameterless rejection RRC connection establishment message.

[0289] After receiving the first parameterless rejection RRC connection establishment message sent by the first network device 200, the terminal device 100 determines that the RRC link exception event is that the first network device sends a first parameterless rejection RRC connection establishment message to the terminal device.

[0290] S805: When the continuous exception times of the terminal device 100 are greater than the first exception times threshold, the terminal device 100 performs a cell handover.

[0291] The terminal device 100 records the continuous exception times within the first duration. When the continuous exception times are greater than the first exception times threshold, the terminal device 100 performs a cell handover. It can be understood that the continuous exception times are the number of times that the RRC link exception event is continuously determined to be a first parameterless rejection RRC connection establishment message.

[0292] Specifically, reference can be made to the relevant description in S608 above. This application will not elaborate here. Figure 6 in S608 above, and this application will not elaborate here.

[0293] Next, taking the case of switching cells and the cell after switching and the previous cell corresponding to the same network device (the first network device 200) as an example, S806 to S810 will be described.

[0294] It can be understood that in the above S801 to S805, the interaction between the terminal device 100 and the first network device 200 is carried out in the first cell. In the following S806 to S810, the communication between the terminal device 100 and the first network device 200 is carried out in the second cell.

[0295] S806: The terminal device 100 sends a second service request to the first network device 200.

[0296] S807: The terminal device 100 sends a second RRC connection request to the first network device 200.

[0297] If the number of consecutive anomalies is greater than the first anomaly count threshold, after the terminal device 100 performs a cell handover, it sends a second service request to the first network device 200 again.

[0298] It can be understood that when the terminal device 100 sends a service request to the first network device 200, it sends an RRC connection request to the first network device 200 at the same time.

[0299] S808: The terminal device 100 determines that the anomaly is a parameterless rejection of the RRC connection establishment message.

[0300] S809: The first network device 200 sends a second parameterless rejection of the RRC connection establishment message to the terminal device 100.

[0301] It can be understood that S806 to S809 can refer to the relevant descriptions in the above S801 to S804, and will not be elaborated here.

[0302] S810: When the number of consecutive anomalies of the terminal device 100 is greater than the second anomaly count threshold, it reduces the network mode.

[0303] The terminal device 100 continues to record the number of consecutive anomalies within the first duration. When the number of consecutive anomalies is greater than the second anomaly count threshold, it reduces the network mode. It can be understood that the number of consecutive anomalies is the number of times that the RRC link anomaly event is determined to be a parameterless rejection of the RRC connection establishment message continuously.

[0304] Specifically, it can refer to the relevant description in S612 above Figure 6 in this application, and will not be elaborated here.

[0305] S811: The terminal device 100 sends a third service request to the second network device 300.

[0306] It can be understood that the network mode corresponding to the second network device 300 is lower than the network mode corresponding to the first network device 200.

[0307] Embodiment 4

[0308] Taking the RRC link anomaly as an example that the first network device sends a parameterless RRC link release message to the terminal device, the interaction process of the RRC link anomaly between the terminal device and the network device is introduced below.

[0309] Exemplarily, Figure 9 According to an embodiment of the present application, a schematic diagram of the interaction process of the RRC link anomaly between the terminal device and the network device is shown.

[0310] After the terminal device 100 executes the steps S601 to S604 shown above Figure 6 the interaction process after detecting the communication service trigger event is as followsFigure 9 As shown in the figure, specifically including:

[0311] S901: The terminal device 100 sends a first service request to the first network device 200.

[0312] In response to a communication service triggering event, the terminal device 100 sends a first service request to the first network device 200.

[0313] It can be understood that the communication service triggering event triggers RRC connection establishment. When the terminal device 100 sends a first service request to the first network device 200, it also sends a first RRC connection request to the first network device 200.

[0314] S902: The terminal device 100 and the first network device 200 complete RRC connection establishment.

[0315] The communication service triggering event triggers RRC connection establishment. The terminal device 100 and the first network device 200 perform RRC connection establishment and complete it. Specifically, the process of completing RRC connection establishment can refer to the relevant description in S303 above and will not be elaborated here.

[0316] S903: The first network device 200 sends a first service request permission to the terminal device 100.

[0317] After the terminal device 100 and the first network device 200 complete RRC connection establishment, that is, after the first network device 200 receives the first RRC connection establishment completion message sent by the terminal device 100, it sends a first service request permission to the terminal device 100.

[0318] S904: The first network device 200 sends a first parameterless RRC link release message to the terminal device 100.

[0319] After the first network device 200 sends a first service request permission to the terminal device 100, due to network anomalies, it sends a first parameterless RRC link release message to the terminal device 100.

[0320] S905: The terminal device 100 determines that the anomaly is a parameterless RRC link release message.

[0321] After the terminal device 100 receives the first parameterless RRC link release message sent by the first network device 200, it determines that the RRC link anomaly event is that the first network device sends a parameterless RRC link release message to the terminal device.

[0322] S906: When the consecutive anomaly count of the terminal device 100 is greater than the first anomaly count threshold, it performs cell handover.

[0323] The terminal device 100 records the number of consecutive anomalies within the first duration. Corresponding to the number of consecutive anomalies being greater than the first anomaly count threshold, a cell handover is performed. It can be understood that the number of consecutive anomalies is the number of times that the RRC link anomaly event is continuously determined to be an RRC link release message without parameters.

[0324] Specifically, reference can be made to the relevant description in S608 above. This application will not elaborate here. Figure 6 in the relevant description in S608 above. This application will not elaborate here.

[0325] Below, taking the example of switching cells and the cell after switching and the previous cell corresponding to the same network device (the first network device 200), S907 to S912 will be described.

[0326] It can be understood that in the above S901 to S906, the interaction between the terminal device 100 and the first network device 200 is carried out in the first cell. In the following S907 to S912, the communication between the terminal device 100 and the first network device 200 is carried out in the second cell.

[0327] S907: The terminal device 100 sends a second service request to the first network device 200.

[0328] Corresponding to the number of consecutive anomalies being greater than the first anomaly count threshold, after the terminal device 100 performs a cell handover, it sends a second service request to the first network device 200 again.

[0329] S908: The terminal device 100 completes RRC connection establishment with the first network device 200.

[0330] S909: The first network device 200 sends a second service request permission to the terminal device 100.

[0331] S910: The first network device 200 sends a second RRC link release message without parameters to the terminal device 100.

[0332] S911: The terminal device 100 determines that the anomaly is an RRC link release message without parameters.

[0333] It can be understood that S907 to S911 can refer to the relevant description in the above S901 to S905, and will not be elaborated here.

[0334] S912: The terminal device 100 reduces the network mode corresponding to the number of consecutive anomalies being greater than the second anomaly count threshold.

[0335] The terminal device 100 continues to record the number of consecutive anomalies within the first duration. Corresponding to the number of consecutive anomalies being greater than the second anomaly count threshold, the network mode is reduced. It can be understood that the number of consecutive anomalies is the number of times that the RRC link anomaly event is continuously determined to be an RRC link release message without parameters.

[0336] Specifically, reference can be made to the relevant description in S612 above, which will not be elaborated herein. Figure 6 in S612, which will not be elaborated herein.

[0337] S913: The terminal device 100 sends a third service request to the second network device 300.

[0338] It can be understood that the network mode corresponding to the second network device 300 is lower than that corresponding to the first network device 200.

[0339] Embodiment 5

[0340] Taking the RRC link anomaly as an example of radio link failure, the interaction process between the terminal device and the network device for RRC link anomaly is introduced below.

[0341] Exemplarily, Figure 10 According to an embodiment of the present application, a schematic diagram of an interaction process between a terminal device and a network device for RRC link anomaly is shown.

[0342] After the terminal device 100 executes the steps S601 to S604 shown above, Figure 6 the interaction process after detecting a communication service trigger event is as shown in Figure 10 the following, specifically including:

[0343] S1001: The terminal device 100 sends a first service request to the first network device 200.

[0344] In response to a communication service trigger event, the terminal device 100 sends a first service request to the first network device 200.

[0345] It can be understood that the communication service trigger event triggers RRC connection establishment. When the terminal device 100 sends a first service request to the first network device 200, it also sends a first RRC connection request to the first network device 200.

[0346] S1002: The terminal device 100 completes RRC connection establishment with the first network device 200.

[0347] The communication service trigger event triggers RRC connection establishment. The terminal device 100 establishes an RRC connection with the first network device 200 and completes the establishment. Specifically, the process of completing RRC connection establishment can refer to the relevant description in S303 above, which will not be elaborated herein.

[0348] S1003: The terminal device 100 determines that the anomaly is a radio link failure.

[0349] The terminal device 100 detects that the RSRP is less than the received power threshold, or is unable to decode physical downlink shared channels (PDSCH), physical downlink control channels (PDCCH), physical broadcast channels (PBCH) and other physical channels, confirms that the radio link establishment fails, and determines that the RRC link abnormal event is a radio link failure.

[0350] It should be understood that the terminal device 100 will detect whether the radio link returns to normal at a fixed frequency. For example, the fixed frequency can be once per second.

[0351] S1004: When the continuous abnormal times corresponding to the terminal device 100 are greater than the first abnormal times threshold, the terminal device 100 performs a cell handover.

[0352] The terminal device 100 records the continuous abnormal times within the first duration. When the continuous abnormal times are greater than the first abnormal times threshold, the terminal device 100 performs a cell handover. It can be understood that the continuous abnormal times are the number of times when the RRC link abnormal event is continuously determined to be a radio link failure.

[0353] Specifically, reference can be made to the relevant description in S608 above Figure 6 and this application will not elaborate here.

[0354] Below, taking the case of switching cells and the cell after switching and the previous cell corresponding to the same network device (the first network device 200) as an example, S1005 to S1008 will be described.

[0355] It can be understood that in the above S1001 to S1004, the interaction between the terminal device 100 and the first network device 200 is carried out in the first cell. In the following S1005 to S1008, the communication between the terminal device 100 and the first network device 200 is carried out in the second cell.

[0356] S1005: The terminal device 100 sends a second service request to the first network device 200.

[0357] Due to the radio link failure, the terminal device 100 sends a second service request to the first network device 200.

[0358] S1006: The terminal device 100 completes the RRC connection establishment with the first network device 200.

[0359] S1007: The terminal device 100 determines that the abnormality is a radio link failure.

[0360] It can be understood that S1005 to S1007 can refer to the relevant description in the above S1001 to S1003, and will not be elaborated here.

[0361] S1008: When the consecutive abnormal times corresponding to the terminal device 100 are greater than the second abnormal time threshold, the network mode is reduced.

[0362] The terminal device 100 continues to record the consecutive abnormal times within the first duration. When the consecutive abnormal times are greater than the second abnormal time threshold, the network mode is reduced. It can be understood that the consecutive abnormal times are the number of consecutive determinations of radio link failures.

[0363] Specifically, reference can be made to the relevant description in S612 above. This application will not elaborate here. Figure 6 in S612 above, and this application will not elaborate here.

[0364] S1009: The terminal device 100 sends a third service request to the second network device 300.

[0365] It can be understood that the network mode corresponding to the second network device 300 is lower than the network mode corresponding to the first network device 200.

[0366] Embodiment Six

[0367] Taking the RRC link anomaly as an example of a data-less radio bearer, the interaction process between the terminal device and the network device for RRC link anomalies is introduced below.

[0368] Exemplarily, Figure 11 According to the embodiments of the present application, a schematic diagram of the interaction process between a terminal device and a network device for RRC link anomalies is shown.

[0369] After the terminal device 100 executes the steps S601 to S604 shown above, the interaction process after detecting a communication service trigger event is as Figure 6 shown below, and specifically includes: Figure 11 shown below, and specifically includes:

[0370] S1101: The terminal device 100 sends a first service request to the first network device 200.

[0371] In response to a communication service trigger event, the terminal device 100 sends a first service request to the first network device 200.

[0372] It can be understood that the communication service trigger event triggers RRC connection establishment. When the terminal device 100 sends a first service request to the first network device 200, it also sends a first RRC connection request to the first network device 200.

[0373] It can be understood that at this time, the terminal device 100 has not established an RRC link with the first network device 200 and is in the idle state.

[0374] S1102: The terminal device 100 completes RRC connection establishment with the first network device 200.

[0375] The communication service trigger event triggers the RRC connection establishment. The terminal device 100 establishes an RRC connection with the first network device 200 and completes the establishment. Specifically, the process of RRC connection establishment can refer to the relevant description in S303 above and will not be elaborated here.

[0376] S1103: The terminal device 100 determines that the exception is no data radio bearer.

[0377] The no data radio bearer can include the failure of data radio bearer establishment and the non - establishment of data radio bearer, etc.

[0378] For example, in some embodiments, the terminal device 100 detects that the data radio bearer establishment fails, for example, it does not receive the service request permission, and determines that the RRC link exception event is the failure of data radio bearer establishment.

[0379] Again, for example, in some other embodiments, after the terminal device 100 receives the service request permission, it detects that the signaling radio bearer has been established but the data radio bearer has not been established, and determines that the RRC link exception event is the non - establishment of data radio bearer.

[0380] It should be understood that the terminal device 100 detects whether the wireless link returns to normal at a fixed frequency. For example, the fixed frequency can be once per second.

[0381] S1104: When the consecutive exception times of the terminal device 100 are greater than the first exception times threshold, the terminal device 100 performs a cell handover.

[0382] The terminal device 100 records the consecutive exception times within the first duration. When the consecutive exception times are greater than the first exception times threshold, it performs a cell handover. It can be understood that the consecutive exception times are the number of times that the RRC link exception event is determined to be no data radio bearer continuously.

[0383] Specifically, it can refer to the relevant description in S608 above Figure 6 and will not be elaborated in this application.

[0384] The following takes the case of switching cells, and the cell after switching and the previous cell correspond to the same network device (the first network device 200) as an example to describe S1105 to S1108.

[0385] It can be understood that in S1101 to S1104 above, the interaction between the terminal device 100 and the first network device 200 is carried out in the first cell. In S1105 to S1108 below, the communication between the terminal device 100 and the first network device 200 is carried out in the second cell.

[0386] S1105: The terminal device 100 sends a second service request to the first network device 200.

[0387] If the number of consecutive anomalies is greater than the first anomaly count threshold, after the terminal device 100 performs a cell handover, it sends a second service request to the first network device 200 again.

[0388] S1106: The terminal device 100 and the first network device 200 complete the RRC connection establishment.

[0389] S1107: The terminal device 100 determines that the anomaly is a failure in establishing a data radio bearer. It can be understood that S1105 to S1107 can refer to the relevant descriptions in the above S1101 to S1103, and will not be elaborated here.

[0390] S1108: When the number of consecutive anomalies of the terminal device 100 is greater than the second anomaly count threshold, the network mode is lowered.

[0391] The terminal device 100 continues to record the number of consecutive anomalies within the first duration. When the number of consecutive anomalies is greater than the second anomaly count threshold, the network mode is lowered. It can be understood that the number of consecutive anomalies is the number of times that the RRC link anomaly event is determined to be without a data radio bearer continuously.

[0392] Specifically, it can refer to the relevant description in S612 above Figure 6 in this application, and will not be elaborated here.

[0393] S1109: The terminal device 100 sends a third service request to the second network device 300.

[0394] It can be understood that the network mode corresponding to the second network device 300 is lower than the network mode corresponding to the first network device 200.

[0395] In summary, the communication method provided by the embodiments of this application can detect the number of RRC link anomalies within a preset duration, and perform operations such as cell handover and lowering the network mode based on the number of anomalies. So that, even in the case of an RRC link anomaly, the terminal device can communicate with the network device normally, and further maintain the communication service of the terminal device.

[0396] To better understand the technical solution of the embodiments of this application, the structure of the devices involved in this application is introduced below with reference to the accompanying drawings.

[0397] Exemplarily, Figure 12 According to the embodiments of this application, a schematic structural diagram of a terminal device 100 is shown.

[0398] As Figure 12As shown, the terminal device 100 may include a processor 110, a memory 120, an interface module 130, a power module 140, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, a key 190, a camera 191, a display screen 192, etc.

[0399] It can be understood that the structure schematically shown in the embodiments of the present application does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0400] 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 processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors. The processor 110 may be used to execute the communication method provided in the embodiments of the present application.

[0401] The operating system running on the AP may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. The layered architecture may adopt the Android system, the iOS system, or other operating systems, and the embodiments of the present application do not limit this.

[0402] A Modem can also be referred to as a baseband processor (BP). Modules such as a protocol stack for cellular communication and a physical layer for cellular communication can be included in the Modem, which can implement functions such as modulation and demodulation, channel encoding and decoding, and source encoding and decoding. Among them, the cellular protocol stack can include a connection management (CM) module, a call control (CC) module, and a network attached storage (NAS) module. The CM module can dynamically establish, modify, and release connections in a communication network and can mainly process call-related data, such as routing, resource allocation, and session management. The CM module can dynamically adjust the call path according to the real-time network status and user requirements to ensure the best communication quality and performance. The CC module is mainly responsible for establishing, maintaining, and releasing call connections during communication and can involve the processing of various protocols and signaling to ensure the stability and reliability of the communication link. The NAS module can perform operations such as camping on the network to achieve communication with network devices. It should be noted that the NAS module is only an example name, and the embodiments of this application do not limit this.

[0403] The Modem in the embodiments of this application can provide cellular communication capabilities. The Modem runs on a baseband chip and a coprocessor, and the terminal device can implement a series of cellular communication functions such as sending and receiving text messages, 5G-related functions, making calls, and answering calls through the Modem.

[0404] A memory can also be set in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can save the instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can directly call it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0405] The interface module 130 may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0406] The power module 140 is connected to the processor 110 to supply power to the processor 110, the memory 120, the camera 191, the display screen 192, the mobile communication module 160, etc.

[0407] The wireless communication function of the terminal device 100 can be implemented by the wireless communication module 150, the mobile communication module 160, the antenna, the modulation and demodulation processor, and the baseband processor, etc.

[0408] The mobile communication module 150 can provide solutions for wireless communications such as 2G / 3G / 4G / 5G applied to the terminal device 100.

[0409] The wireless communication module 160 can provide solutions for wireless communications applied to the terminal device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc.

[0410] In some embodiments, wireless communication technologies may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Synchronous Code Division Multiple Access (TDSCDMA), LTE, NR, Bluetooth (BT), Global Navigation Satellite System (GNSS), Wireless Local Area Network (WLAN), Near Field Communication (NFC), Frequency Modulation (FM), and / or Infrared (IR) technology, etc. In some embodiments, the terminal device 100 communicates with the network device based on the wireless communication module 150. For example, it communicates with the network device based on LTE technology, NR technology, etc.

[0411] The audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals.

[0412] The sensor module 180 may include a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

[0413] The terminal device 100 realizes the display function through a Graphics Processing Unit (GPU), the display screen 192, and an application processor, etc.

[0414] The display screen 192 is used to display images, videos, etc. The display screen 192 includes a display panel. The display panel can adopt a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), an Active-Matrix Organic Light Emitting Diode (AMOLED), a Flexible Light-Emitting Diode (FLED), a Quantum Dot Light Emitting Diode (QLED), etc. In some embodiments, the terminal device 100 may include one or N display screens 192, where N is a positive integer greater than 1.

[0415] The terminal device 100 can implement the shooting function through the ISP, camera 191, video codec, GPU, display screen 192, application processor, etc.

[0416] The camera 191 is used to capture still images or videos. In some embodiments, the terminal device 100 may include one or N cameras 191, where N is a positive integer greater than 1.

[0417] The memory 120 can be used to store computer-executable program code, and the executable program code includes instructions. The memory 120 may include a program storage area and a data storage area. Among them, the program storage area can store the operating system, application programs required for at least one function (such as the sound playback function, image playback function, etc.). The data storage area can store the data created during the use of the terminal device 100 (such as audio data, phone book, etc.). In addition, the memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the terminal device 100 by running the instructions stored in the memory 120 and / or the instructions stored in the memory provided in the processor. In some implementation instances, the processor 110 executes the communication method provided in the embodiments of the present application by running the instructions stored in the memory 120.

[0418] The button 190 includes a power-on button, volume button, etc. The button 190 can be a mechanical button or a touch button.

[0419] In some embodiments, a computer-readable storage medium is also provided. The computer-readable storage medium stores at least one instruction, at least one segment of program, code set or instruction set, and the at least one instruction, at least one segment of program, code set or instruction set is loaded and executed by the processor to implement the communication methods provided in the above various method embodiments.

[0420] In some embodiments, a program product is also provided. The program product includes instructions, and when the instructions are executed by an electronic device, the electronic device can implement the communication method provided in the embodiments of the present application.

[0421] In some embodiments, a chip system is also provided. The chip system includes a processing circuit and a storage medium, and the storage medium stores computer program code; when the computer program code is executed by the processing circuit, the communication method provided in the embodiments of the present application is implemented.

[0422] Embodiments of the mechanisms disclosed in this application may be implemented in hardware, software, firmware, or a combination of these implementation methods. Embodiments of this application may be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memories and / or storage elements), at least one input device, and at least one output device.

[0423] The program code can be applied to the input instructions to perform the various functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0424] The program code can be implemented in a high-level procedural language or an object-oriented programming language in order to communicate with the processing system. When needed, the program code can also be implemented in assembly language or machine language. In fact, the mechanisms described in this application are not limited to the scope of any particular programming language. In any case, the language can be a compiled language or an interpreted language.

[0425] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more transient or non-transitory machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or via other computer-readable media. Thus, machine-readable media may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to, floppy disks, optical disks, optical discs, CD-ROMs, magneto-optical disks, read only memory (ROM), random access memory (RAM), erasable programmable read only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic or optical cards, flash memory, or tangible machine-readable memories for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) in electrical, optical, acoustic, or other forms via the Internet. Thus, machine-readable media include any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0426] In the drawings, some structural or method features may be shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or ordering may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Additionally, the inclusion of a structural or method feature in a particular figure does not imply that such a feature is required in all embodiments, and in some embodiments, these features may not be included or may be combined with other features.

[0427] It should be noted that each unit / module mentioned in the device embodiments of this application is a logical unit / module. Physically, a logical unit / module may be a physical unit / module, may be a part of a physical unit / module, or may also be implemented as a combination of multiple physical units / module. The physical implementation manner of these logical units / module themselves is not the most important. The combination of the functions implemented by these logical units / module is the key to solving the technical problems proposed in this application. In addition, in order to highlight the innovative part of this application, the above device embodiments of this application do not introduce units / modules that are not closely related to solving the technical problems proposed in this application, which does not mean that there are no other units / modules in the above device embodiments.

[0428] It should be noted that in the examples and the specification of this patent, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one" does not exclude the presence of additional identical elements in the process, method, article or device comprising the said element.

[0429] Although this application has been illustrated and described by reference to certain preferred embodiments thereof, those of ordinary skill in the art should understand that various changes may be made thereto in form and detail without departing from the spirit and scope of this application.

Claims

1. A communication method, applied to a terminal device, characterized in that, including: sending a first RRC connection request to a first network device in a first cell, where the first network device corresponds to a first network mode; detecting a first RRC link anomaly event corresponding to the first RRC connection request, and determining that the number of RRC link anomaly events generated after sending the RRC connection request to the first network device within a first time period meets a first handover condition; sending a second RRC connection request to a second network device, where at least one of the network mode and cell corresponding to the second network device is different from those of the first network device.

2. The method according to claim 1, characterized in that, The first time period includes the occurrence time of the first RRC link anomaly event.

3. The method according to claim 1, wherein The first handover condition includes: the number of RRC link anomaly events occurring within the first time period is greater than a first anomaly number threshold, and the time interval between the RRC link anomaly event occurring within the first time period and the corresponding RRC connection request is less than or equal to an anomaly time threshold, and the time interval between adjacent RRC link anomaly events occurring within the first time period is less than a time interval threshold.

4. The method according to claim 1, wherein The second network device corresponds to a second cell and the first network mode, and the method further includes: determining that the number of RRC link anomaly events generated after sending the RRC connection request to the second network device within a second time period meets a second handover condition; sending a third RRC connection request to a third network device, where the third network device corresponds to the second network mode.

5. The method according to claim 4, wherein The second handover condition includes: the number of RRC link anomaly events occurring within the second time period is greater than a second anomaly number threshold, and the time interval between the RRC link anomaly event occurring within the second time period and the corresponding RRC connection request is less than or equal to an anomaly time threshold, and the time interval between adjacent RRC link anomaly events occurring within the second time period is less than an interval time threshold.

6. The method according to claim 4, wherein It further includes: corresponding to after sending the third RRC connection request to the third network device, detecting that the network quality corresponding to the third network device is lower than a quality threshold; sending a fourth RRC connection request to a fourth network device, where the fourth network device corresponds to the first network mode.

7. The method according to claim 1, wherein The RRC link anomaly event includes at least one of the following: the terminal device does not receive a response message to the RRC connection request within a preset time; the terminal device receives a response message without parameters; the terminal device detects a radio link failure; the terminal device detects a non-data radio bearer.

8. The method according to claim 7, wherein the response message includes at least one of the following: a reject service request message, a reject link establishment message, a release radio communication link message; and the non-data radio bearer includes at least one of the following: a radio data bearer establishment failure, a radio data bearer not established.

9. A communication method, applied to a terminal device, characterized in that, including: sending at least one first RRC connection request in the first cell; The cause value fields of the first response messages received within the first time period do not include the cause value parameter, where the number of first response messages received within the first time period is less than or equal to the number of times the first RRC connection request is sent; Send a second RRC connection request in the second cell.

10. The method according to claim 9, characterized in that, Further included: The cause value fields that are not included in any of the second response messages received within the second time period do not include the cause value parameter, where the number of second response messages received within the second time period is less than or equal to the number of times the second RRC connection request is sent; Send a third RRC connection request in the third cell.

11. The method according to claim 9 or 10, characterized in that, Further included: The time interval between the first response message and the corresponding first RRC connection request sent is less than or equal to the abnormal time threshold; The time interval between adjacent first response messages within the first time period is less than the interval time threshold.

12. A readable medium, characterized in that, Instructions are stored on the readable medium, and when executed on the terminal device, the instructions cause the terminal device to execute the method according to any one of claims 1 to 11.

13. A terminal device, characterized in that, Including: A memory for storing instructions executed by one or more processors of the terminal device, and A processor, which is one of the processors of the terminal device, for executing the method according to any one of claims 1 to 11.

14. A chip system, characterized in that, Including a processing circuit and a storage medium, where computer program code is stored in the storage medium; when the computer program code is executed by the processing circuit, the method according to any one of claims 1 to 11 is implemented.

Images