Communication method, readable medium, terminal device, and chip system

Abstract

Disclosed in the present application are a communication method, a readable medium, a terminal device, and a chip system. The communication method in the present application comprises: a terminal device sending a radio communication link connection request to a first network device in a cell on which the terminal device currently camps, and detecting the number of consecutive abnormalities of a radio communication link within a preset duration; and when the number of consecutive abnormalities is greater than a set abnormality count threshold, sending the radio communication link connection request to a second network device, wherein at least one of a network standard and a cell that correspond to the second network device is different from that which corresponds to the first network device.

Description

Communication method, readable medium, terminal device and chip system

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on January 5, 2024, with application number 202410024288.X and application name “Communication Method, Readable Medium, Terminal Device and Chip System”. The entire contents of the above application are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method, a readable medium, a terminal device, and a chip system. Background Art

[0003] When a user browses the web or performs other wireless communication services 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 cell where it is currently located, so as to establish a wireless communication link with the network device and transmit data with the network device based on the wireless communication link, so that the user can browse the web or perform other activities through the terminal device.

[0004] Taking a radio resource control (RRC) link as an example, during the RRC link establishment process, normal communication with a network device may fail, thereby affecting the communication service of the terminal device. Summary of the Invention

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

[0006] A first aspect of the present application provides a communication method, applied to a terminal device, including: sending a first RRC connection request to a first network device in a first cell, wherein the first network device corresponds to a first network standard; detecting a first RRC link abnormality event corresponding to the first RRC connection request, and determining that the number of RRC link abnormality events generated after the RRC connection request is sent to the first network device within a first time period meets a first switching condition; sending a second RRC connection request to a second network device, wherein at least one of the network standard and cell corresponding to the second network device is different from that of the first network device.

[0007] It can be understood that the terminal device sends a wireless communication link connection request to the network device in the cell it is currently residing in, and detects the number of consecutive wireless communication link anomalies within a preset time period. Furthermore, when the number of consecutive anomalies exceeds a set anomaly threshold, the terminal device can switch at least one of the cell and network standard before establishing a wireless communication link with the network device. This method allows the terminal device to maintain normal communication with the network device even when continuous wireless communication link anomalies occur, thereby maintaining the terminal device's communication services.

[0008] In a possible implementation of the first aspect above, the first duration includes the time when the first RRC link abnormality event occurs.

[0009] In one possible implementation of the first aspect above, the first switching condition includes: the number of RRC link abnormality events occurring within the first time length is greater than the first abnormality number threshold, and the time interval between the RRC link abnormality event occurring within the first time length and the corresponding RRC connection request is less than or equal to the abnormality time threshold, and the time interval between adjacent RRC link abnormality events occurring within the first time length is less than the time interval threshold.

[0010] In a possible implementation of the first aspect above, the second network device corresponds to the second cell and the first network standard, and the method further includes: determining that the number of RRC link abnormality events generated after the RRC connection request is sent to the second network device within the second time period meets the second switching condition; and sending a third RRC connection request to the third network device, wherein the third network device corresponds to the second network standard.

[0011] In one possible implementation of the first aspect above, the second switching condition includes: the number of RRC link abnormal events occurring within the second time length is greater than the second abnormal number threshold, and the time interval between the RRC link abnormal event occurring within the second time length and the corresponding RRC connection request is less than or equal to the abnormal time threshold, and the time interval between adjacent RRC link abnormal events occurring within the second time length is less than the interval time threshold.

[0012] In a possible implementation of the first aspect above, the method further includes: corresponding to sending a third RRC connection request to a third network device, detecting that the network quality corresponding to the third network device is lower than a quality threshold; and sending a fourth RRC connection request to a fourth network device, wherein the fourth network device corresponds to the first network standard.

[0013] In one possible implementation of the first aspect above, the RRC link abnormal 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 wireless link failure; the terminal device detects no data wireless bearer.

[0014] In one possible implementation of the first aspect above, the response message includes at least one of the following: a rejection of the service request message, a rejection of the link establishment message, and a release of the wireless communication link message; and the data-free wireless bearer includes at least one of the following: failure to establish the wireless data bearer and failure to establish the wireless data bearer.

[0015] The second aspect of the present application provides a communication method, applied to a terminal device, including: sending a first RRC connection request at least once in a first cell; the cause value field of the first response message received within a first time length does not include a cause value parameter, wherein the number of first response messages received within the first time length is less than or equal to the number of times the first RRC connection request is sent; and sending a second RRC connection request in the second cell.

[0016] In an embodiment of the present application, if the number of consecutive exceptions is greater than K, the terminal device 100 determines the second cell and sends a second RRC connection request to the second network device. For example, corresponding to the terminal device 100 sending K first RRC connection requests to the first network device 200, the number of consecutive exceptions greater than K may be: the K first response messages received within the first time length are all response messages without parameters. Or for example, corresponding to the terminal device 100 sending M first RRC connection requests to the first network device 200, the number of consecutive exceptions greater than K may be: the K first response messages received within the first time length 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.

[0017] In one possible implementation of the second aspect above, the method also includes: the cause value field not included in the second response messages received in the second time period does not include a cause value parameter, wherein 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; and a third RRC connection request is sent in a third cell.

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

[0019] In a possible implementation of the first aspect above, the method also includes: the time interval between the first response message and the sending of the corresponding first RRC connection request is less than or equal to the abnormal time threshold; the time interval between adjacent first response messages within the first time length is less than the interval time threshold.

[0020] A third aspect of the present application provides a readable medium having instructions stored thereon, which, when executed on a terminal device, causes the terminal device to execute any one of the methods in the first or second aspect above.

[0021] The fourth aspect of the present application provides a terminal device, comprising: 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 one of the methods in the first or second aspects above.

[0022] The fifth aspect of the present application provides a chip system, including a processing circuit and a storage medium, wherein the storage medium stores computer program code; when the computer program code is executed by the processing circuit, any one of the methods in the first or second aspect above is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0024] FIG1 shows a schematic diagram of a communication system according to an embodiment of the present application;

[0025] FIG2 a shows a schematic diagram of an interface of a terminal device when the terminal device cannot communicate normally with a network device according to an embodiment of the present application;

[0026] FIG2 b shows another schematic diagram of an interface of a terminal device when the terminal device cannot communicate normally with a network device according to an embodiment of the present application;

[0027] FIG3 a shows a schematic diagram of an interaction process when an RRC link is abnormal between a terminal device and a network device according to an embodiment of the present application;

[0028] FIG3 b shows a schematic diagram of a process for completing RRC link establishment according to an embodiment of the present application;

[0029] FIG4 a shows a schematic flow chart of a communication method according to an embodiment of the present application;

[0030] FIG4 b shows an interactive schematic diagram of recording the number of consecutive anomalies within a first time period according to an embodiment of the present application;

[0031] FIG4c shows a schematic diagram of a change of a network signal icon according to an embodiment of the present application;

[0032] FIG5 shows a schematic diagram of a process of evaluating the network status of a second network by a terminal device according to an embodiment of the present application;

[0033] FIG6 shows a schematic diagram of an interaction process of an RRC link abnormality between a terminal device and a network device in which an RRC link abnormality occurs when a first network device fails to respond to an RRC connection request of a terminal device within a preset time according to an embodiment of the present application;

[0034] FIG7 shows a schematic diagram of an interaction process of an RRC link abnormality between a terminal device and a network device, in which an RRC link abnormality is a first network device sending a parameter-free service rejection request to a terminal device, according to an embodiment of the present application;

[0035] FIG8 shows a schematic diagram of an interaction process of an RRC link abnormality between a terminal device and a network device, in which an RRC link abnormality is a first network device sending a parameter-free RRC link establishment rejection message to a terminal device, according to an embodiment of the present application;

[0036] FIG9 shows a schematic diagram of an interaction process of an RRC link abnormality between a terminal device and a network device, in which an RRC link abnormality is caused by a first network device sending an RRC link release message without parameters to the terminal device, according to an embodiment of the present application;

[0037] FIG10 shows a schematic diagram of an interaction process of an RRC link abnormality between a terminal device and a network device, wherein the RRC link abnormality is a radio link failure, according to an embodiment of the present application;

[0038] FIG11 shows a schematic diagram of an interaction process between a terminal device and a network device in which an RRC link abnormality is an RRC link abnormality with no data radio bearer according to an embodiment of the present application;

[0039] FIG12 shows a schematic structural diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0041] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and comprehensively described below with reference to the accompanying drawings.

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

[0043] Cell: also known as cellular cell, refers to the area covered by wireless signals in mobile communications.

[0044] Mobile communication networks can adopt a cellular structure, with multiple base stations deployed in different locations. Each base station forms a cell, and each base station is responsible for communication for mobile users within its cell area. To ensure uninterrupted and continuous communication for mobile users, adjacent cells have a certain overlap area, allowing mobile users to switch from one cell to another during communication.

[0045] Specifically, referring to the schematic diagram of the communication system shown in FIG1 , the communication system may include multiple network devices (e.g., base stations): network device 21, network device 22, and network device 23. 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 certain overlapping areas with adjacent cells B and C, respectively.

[0046] The technical solution provided in 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 in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, etc. This application is not limited to this. Figure 1 shows a schematic diagram of a communication system according to an embodiment of the present application. As shown in Figure 1, 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.

[0047] It will be understood that FIG1 only uses one network device corresponding to one cell as an example. In other embodiments, one network device may also correspond to multiple cells. The communication system shown in FIG1 is only an example of a communication system. In other embodiments, the communication system may also include more or fewer terminal devices and network devices than shown. Terminal devices may also be referred to as terminals, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. Terminal devices may be mobile phones, smart TVs, wearable devices, tablet computers, computers with wireless transceiver functions, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. In the embodiment of the present application, the terminal device may further include a relay, or it may be understood that any device capable of performing data communication with a base station may be regarded as a terminal device.

[0048] In the embodiments of the present application, the apparatus for implementing the functions of the terminal device may be the terminal device, or may be an apparatus capable of supporting the terminal device in implementing the functions, such as a chip system, which may be installed in the terminal device. In the embodiments of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. In the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by taking the terminal device as an example in which the apparatus for implementing the functions of the terminal is the terminal device.

[0049] The network equipment may include one or more access network (AN) devices, such as a base station. A base station is a device deployed in an access network to provide wireless communication functions for a terminal. For example, the network equipment may include an evolved base station (NodeB, eNB, or eNodeB) in an LTE system; the network equipment may also include a next-generation node B (gNB or gNodeB) in a fifth-generation mobile communication technology (5G) NR system (also referred to as an NR system); the network equipment may also include a centralized unit (CU) and a distributed unit (DU) in a cloud radio access network (Cloud RAN) system, which is not limited in the embodiments of the present application.

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

[0051] As mentioned above, taking the wireless communication link as an RRC link as an example, when the terminal device performs wireless communication services, the terminal device needs to send an SR request to the network device in the current cell where it resides, and at the same time trigger RRC link establishment, that is, send an RRC connection request (RRCSetupReqest) to the network device to establish a wireless communication link with the network device.

[0052] 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 (RRCRelease) to the terminal device. The RRC link release message is used to indicate that the network device has disconnected the RRC link established with the terminal device.

[0053] In other cases, if the network device has no network resources to allocate to the terminal device, the network device may also send an RRC link release message to the terminal device.

[0054] The RRC link release message typically includes parameters such as a cause value, for example, information about the release of the radio bearer (RB) established during the RRC establishment process, a waiting time, and other parameter information, so that the terminal device can make corresponding processing based on the parameter information. For example, the terminal device can switch to the target cell to establish the RRC link or wait for a period of time before sending an RRC connection request.

[0055] After the established RRC link is disconnected, if the terminal device detects a communication service triggering event again, such as detecting that the user uses a voice call service such as making a call, the user uses a browser to search for content, the user makes a video call, etc., which requires operations such as wireless communication services, it is necessary to send a service request and an RRC connection request to the network device again to re-establish the RRC link.

[0056] However, if an RRC link anomaly occurs during the RRC link establishment process between the terminal device and the network device, and the network device does not respond to the RRC connection request of the terminal device, the terminal device will attempt to send service requests and RRC connection requests to the network device multiple times in the current cell.

[0057] Alternatively, if the network device sends a response message without parameters to the terminal device, the terminal device will attempt to send a service request and an RRC connection request to the network device multiple times in the current cell. Furthermore, if the RRC link cannot be established after the terminal device has sent the service request and the RRC connection request multiple times, the terminal device will not be able to communicate normally with the network device, even though the network quality is high.

[0058] For example, Figure 2a illustrates a schematic diagram of a terminal device interface when the terminal device cannot communicate normally with a network device, according to an embodiment of the present application. As shown in Figure 2a, the user interface 202 of the terminal device 100 displays a "Loading Failed" prompt, but the network signal icon 201 indicates a full network signal. In other words, although the network signal is good (full), the terminal device cannot communicate normally with the network device.

[0059] Figure 2b illustrates another example of a terminal device interface that fails to communicate properly with a network device, according to an embodiment of the present application. As shown in Figure 2b, the user interface 204 of the terminal device 100 displays a chat interface between a user and a contact "XXX." The user's messages "Can't receive your message" and "No network connection" both fail to be sent, but the network signal icon 203 indicates a full network signal. In other words, although the network signal is full, the terminal device cannot communicate properly with the network device.

[0060] It can be understood that the network signal icon 201 and the network signal icon 203 in Figures 2a and 2b are only examples. In other embodiments, when the network signal is good, the network signal icon may also be in other forms. For example, when the signal is full, it is five grids, and the network signal icon in the display interface of the terminal device 100 may be four grids. Or for example, when the signal is full, it is 100%, and the network signal icon in the display interface of the terminal device 100 may be a case where the signal quality threshold is greater than 70%. This application does not specifically limit the display form of the network signal icon when the network signal is good.

[0061] Exemplarily, taking the case where a wireless communication link is abnormal and the network device sends a parameter-free RRC link release message as an example, FIG3a shows a schematic diagram of the interaction process of an abnormal RRC link between a terminal device and a network device according to an embodiment of the present application.

[0062] As shown in Figure 3a, the process includes:

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

[0064] In some embodiments, the terminal device 100 sends a registration request to the first network device 200 in response to a triggering event of first network access (eg, power on).

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

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

[0067] It can be understood that the above steps S301 to S302 are the process of the first network device 200 completing the network stationing.

[0068] S303: The terminal device 100 completes RRC link establishment with the first network device 200.

[0069] In some embodiments, after the terminal device 100 completes registration with the first network device 200, i.e., after receiving a registration permission response from the first network device 200, it triggers an RRC link establishment with the first network device 200, and the link establishment is successful. The RRC link establishment process is specifically described in FIG. 3B below.

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

[0071] 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 is successfully established, 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 that can be allocated 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.

[0072] The cause value field (e.g., ReleaseCause) in the RRC link release message typically includes a cause value parameter so that the terminal device 100 can make corresponding processing based on the cause value parameter. The cause value parameter may include releasing an established signaling radio bearer (SRB) and data radio bearer (DRB), cell reselection priorities, etc.

[0073] The above is a process for disconnecting the RRC link after the RRC link is established normally. The following describes a process for failing to establish the RRC link when an RRC link anomaly occurs in some embodiments.

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

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

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

[0077] 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 an idle state (RRC_IDLE, referred to as idle state).

[0078] S306: The terminal device 100 completes RRC link establishment with the first network device 200.

[0079] In some embodiments, the communication service triggering event triggers RRC link establishment, and the terminal device 100 establishes an RRC link with the first network device 200, and the link establishment is successful. Specifically, the process of completing the RRC link establishment can refer to the above S303 and the related description in Figure 3b below, which will not be repeated here.

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

[0081] In some embodiments, after the terminal device 100 completes the RRC link establishment with the first network device 200, that is, after the first network device 200 receives the RRC link establishment completion message (RRCSetupComplete) sent by the terminal device 100, it agrees to the service request of the terminal device 100 and sends a service request permission to the terminal device 100.

[0082] S308: The first network device 200 sends a parameter-free RRC link release message to the terminal device 100.

[0083] In some embodiments, an RRC link abnormality occurs due to reasons such as the number of terminal devices connected to the network device corresponding to the cell where the terminal device 200 currently resides exceeding a quantity threshold, or the network quality of the network device corresponding to the cell where the terminal device 200 currently resides being poor. The first network device 200 sends a parameter-free RRC link release message to the terminal device 100. In other words, the terminal device 100 is unable to perform corresponding processing based on the parameter information of the received parameter-free RRC link release message, such as switching cells.

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

[0085] In some embodiments, due to receiving the parameter-less RRC link release message sent by the first network device 200, the terminal device 100 is unable to make corresponding processing based on the parameter information of the parameter-less RRC link release message, then the terminal device 100 sends a service request to the first network device 200 again.

[0086] S310: The terminal device 100 completes RRC link establishment with the first network device 200.

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

[0088] S312: The first network device 200 sends a parameter-free RRC link release message to the terminal device 100.

[0089] Specifically, S310 to S312 may refer to the relevant descriptions in S306 to S308 above, and will not be repeated here.

[0090] It can be understood that due to receiving the parameter-free RRC link release message sent by the first network device 200, the terminal device 100 is unable to make corresponding processing based on the parameter information of the parameter-free RRC link release message, such as switching cells, resulting in the terminal device 100 continuing to send 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.

[0091] For example, FIG3b shows a schematic diagram of an RRC link establishment process according to an embodiment of the present application. As shown in FIG3b , the process includes:

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

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

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

[0095] In some embodiments, the network device 200 may determine whether to establish an RRC link based on the network load situation, and if the RRC link is established, send an RRC link establishment message to the terminal device 100.

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

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

[0098] It can be understood that after the terminal device 100 receives the RRC link establishment message sent by the first network device 200, it 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.

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

[0100] In summary, due to abnormal wireless communication links, such as network devices frequently sending parameter-less RRC link release messages, the terminal device cannot make further processing based on the parameter-less RRC link release message, such as switching cells, lowering the network standard, etc., and stays in the initial cell, unable to communicate normally with the network device, thereby affecting the communication service of the terminal device.

[0101] It is understandable that, as previously described, the cause of the wireless communication link abnormality may be that the number of terminal devices connected to the network device corresponding to the cell in which the terminal device is currently residing exceeds a threshold. Alternatively, the cause of the wireless communication link abnormality may be poor network quality of the network device corresponding to the cell in which the terminal device is currently residing. This may result in the network device failing to respond to the terminal device's request within a preset time, or sending a response message without parameters to the terminal device.

[0102] Therefore, an embodiment of the present application provides a communication method, in which no wireless communication link is established between a terminal device and a network device, and the terminal device detects a communication service triggering event, the terminal device sends a wireless communication link connection request to the network device in the cell where it is currently located, and detects the number of consecutive abnormalities of the wireless communication link within a preset time period. In addition, the terminal device can switch cells and switch network formats when the number of consecutive abnormalities is greater than the number of abnormalities threshold, and then establish a wireless communication link with the network device. For example, in some embodiments, the terminal device can first switch cells when the number of consecutive abnormalities is greater than the number of abnormalities threshold. If the wireless communication link still cannot be established after switching the cell, it means that the abnormal problem has not been resolved, and the terminal device can switch the network format, and try to establish a wireless communication link again after switching the network format.

[0103] Specifically, assuming that a terminal device sends a first service request to a first network device in a first cell (i.e., the cell it is currently residing in), and if the number of consecutive abnormal RRC link events detected within a preset time period exceeds a first abnormal number threshold, it can be considered that there is an abnormality in the first network device, for example, the number of terminal devices connected to the first network device exceeds a number threshold. Then, the terminal device will perform a cell handover, that is, determine a second cell and send a second service request to the second network device in the second cell.

[0104] It is understood that the first network device and the second network device correspond to the same network standard. For example, the first network device and the second network device are both gNodeBs, and the corresponding network standard is a 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.

[0105] Furthermore, if the number of consecutive exceptions is greater than the second exception threshold, indicating that the abnormality remains unresolved after the terminal device performs a cell handover, it can be considered that the cause of the abnormality is poor network quality of the second network device, and the terminal device performs a network standard handover, i.e., determines a third cell and sends a third service request to the third network device in the third cell. It is understood that the network standard corresponding to the third network device is lower than the network standard corresponding to the second network device. For example, the second network device is a gNodeB, and the corresponding network standard is a 5G network, while the third network device is an eNodeB, and the corresponding network standard is a 4G network.

[0106] In addition, in some embodiments, the terminal device may also switch the network mode first and then attempt to establish a link when the number of consecutive exceptions is greater than the number of exceptions threshold. If the link establishment is still unsuccessful after switching the network mode, you can try to switch the cell again to attempt to establish a link. For example, assuming 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 exceptions of the RRC link is greater than the first number of exceptions threshold within a preset time length, the terminal device switches the network mode. Furthermore, if the number of consecutive exceptions is greater than the second number of exceptions threshold, the terminal device switches the cell.

[0107] In addition, in some other embodiments, the terminal device may also switch cells before attempting to establish a link when the number of consecutive exceptions exceeds a threshold. If the link establishment is still unsuccessful after switching cells, the terminal device may attempt to switch network devices to establish a link. If the link establishment is still unsuccessful after switching network devices, the terminal device may attempt to switch network standards to establish a link.

[0108] Specifically, assuming that a terminal device sends a first service request to a first network device in a first sub-cell, and detects that the number of consecutive RRC link anomalies exceeds a first anomaly threshold within a preset time period, the terminal device performs a cell handover, i.e., sends the first service request to the first network device in a second sub-cell. It is understood that the second sub-cell and the first sub-cell correspond to the same network device, i.e., the first network device.

[0109] Furthermore, if the number of consecutive exceptions is greater than a second exception threshold, the terminal device performs network device switching, i.e., sends a second service request to the second network device in the third sub-cell. It can be understood that the first network device and the second network device correspond to the same network standard, for example, the first network device and the second network device are both gNodeBs, and the corresponding network standard is a 5G network.

[0110] Furthermore, if the number of consecutive exceptions is greater than a third exception threshold, the terminal device performs network standard switching, i.e., determines a 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 standard corresponding to the third network device is lower than the network standard corresponding to the second network device. For example, the second network device is a gNodeB, and the corresponding network standard is a 5G network, and the third network device is an eNodeB, and the corresponding network standard is a 4G network.

[0111] In addition, in some other embodiments, the terminal device may also switch the network mode and cell at the same time and then attempt to establish a link when the number of consecutive exceptions is greater than the exception threshold. Specifically, assuming that the terminal device sends a service request to the first network device in the first cell, and detects that the number of consecutive exceptions of the RRC link is greater than the fourth exception threshold within a preset time period, the terminal device switches the cell and network mode.

[0112] It can be understood that wireless communication link abnormalities include but are not limited to: the network device fails to respond to the terminal device's wireless path connection request within a preset time, the network device sends a parameter-free response message to the terminal device (such as an RRC link release message, etc.), the wireless link fails, there is no data wireless bearer, etc.

[0113] It is understood that the "parameter-less response message" in the embodiments of the present application means that the response message does not carry a parameter with a cause value, that is, the cause value field of the response message is empty. In addition, the description of the various messages (request and response messages, etc.) for interaction between the terminal device and the network device in this application is only an example and is not the only representation of each message. The description of each response message can also refer to the description in the communication protocol such as the 3rd Generation Partnership Project (3GPP) protocol.

[0114] In some embodiments, the terminal device may implement cell switching in the following manner: setting the first cell as an inaccessible cell (bar cell), and performing cell reselection and switching in cells other than the inaccessible cell.

[0115] In some embodiments, the method of reducing the network standard includes:

[0116] First, disable the first network frequency band or disable the first network capability, for example, disable the NR frequency band or disable the NR capability.

[0117] Secondly, the terminal device disconnects from the first network device, performs a cell search in the second network frequency band, and determines a third cell. Specifically, during the cell search process, the terminal device reads system information of each cell, such as reference signal received power (RSRP), reference signal received quality (RSRQ), and other parameters, prioritizes the searched cells based on the system information of each cell, and selects the cell with the highest priority as the third cell.

[0118] Then, a service request is sent to the third network device in the third cell.

[0119] It will be appreciated that, in the communication method provided in the embodiments of the present application, a terminal device can detect the number of consecutive anomalies in the wireless communication link within a preset time period and perform cell switching and / or downgrade network standards based on the number of consecutive anomalies. This allows the terminal device to communicate normally with the network device even in the event of continuous anomalies in the wireless communication link, thereby maintaining the terminal device's communication services.

[0120] In particular, when the number of consecutive abnormalities is greater than the abnormality threshold, the terminal device first switches cells. If the wireless communication link still cannot be established after switching cells, the network standard is switched again, and the wireless communication link is attempted again after switching the network standard. It can be understood that the terminal device first switches cells and does not lower the network standard, and still attempts to connect to the network device corresponding to the first network standard. If the abnormality problem still cannot be resolved after switching cells, the network standard is lowered to ensure that the user gives priority to using the network with a higher network standard.

[0121] In order to better understand the technical solutions of the embodiments of the present application, some technical solutions of the present application are introduced in detail below, taking RRC link abnormality as an example of wireless communication link abnormality, and taking the solution of first switching the cell and then switching the network mode when the number of consecutive abnormalities of the terminal device is greater than the set threshold as an example.

[0122] Figure 4a shows a flow chart of a communication method according to an embodiment of the present application. It is understood that the execution entity of each step of the process shown in Figure 4a is the terminal device 100. To simplify the description, the execution entity of each step will not be repeated when introducing each step of the process shown in Figure 4a. As shown in Figure 4a, the process includes but is not limited to the following steps:

[0123] S401: In response to a communication service triggering event, sending a first service request to a first network device.

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

[0125] The terminal device detects a communication service triggering event, which may be a user making a voice call using a voice call service, a user opening a browser application to search, a user making a video call through an instant messaging application, etc. In response to the communication service triggering event, the terminal device sends a first service request to the first network device according to the first cell in which it resides.

[0126] In some embodiments, the first cell may be a cell search performed on a first network frequency band (e.g., an NR frequency band) when the terminal device is powered on or a radio link failure occurs, and the cell to be resident is determined. Specifically, during the cell search process, the terminal device reads system information of each cell, such as parameters such as RSRP and RSRQ, and prioritizes the searched cells according to the system information of each cell, with the cell with the highest priority being the first cell.

[0127] It can be understood that at this time, the terminal device 100 has completed the network stationing and has not established an RRC link with the first network device 200, and is in an idle state. For details, please refer to the relevant description of Figure 3a above.

[0128] S402: Detect a first RRC link abnormality event, and record the number of consecutive abnormalities within a first time period.

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

[0130] RRC link abnormal events include, but are not limited to: the first network device fails to 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. The response message may include: RRC link establishment rejection message, RRC link release message, service request rejection message (SRReject), etc.

[0131] In some embodiments, the number of consecutive exceptions within the first duration can be determined in the following manner: if the current RRC link exception is the first RRC link exception, the time when the current RRC link exception occurs is used as the starting time of the first duration, and the number of consecutive exceptions is set to 1. If the second RRC link exception is detected within the first duration, the number of consecutive exceptions is increased by 1, and so on, until the end time of the first duration ends. It is understood that the interval length of the first duration can be a pre-set first duration T1, such as 5 minutes (minute, min), 10 minutes, etc. It is understood that the first duration T1 can be a duration greater than 0.

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

[0133] If it is detected that the time interval between the occurrence time of the RRC link abnormal event and the sending time of the corresponding first service request is greater than the abnormal time threshold, the first RRC link abnormal event will not be recorded as an RRC link abnormal event.

[0134] It is understandable that since there may be a certain delay in the network device responding to the message sent by the terminal device, the RRC link abnormal event can be determined by setting an abnormal time threshold.

[0135] It is understood that the abnormal time threshold can be a pre-set abnormal time threshold T2, such as 2 seconds (s), 5 seconds, etc. It is understood that the abnormal time threshold T2 can be a duration greater than 0 and less than the first duration T1. Specifically, the value range of the abnormal time threshold T2 can be any value between 200 milliseconds and 5000 milliseconds, such as 200 milliseconds, 2000 milliseconds, 3000 milliseconds, etc.

[0136] Exemplarily, this can be achieved by a timer with a preset time length. For example, if the current RRC link abnormality event is the first RRC link abnormality event, a 5-minute timer and counter are started, and the count value of the counter is set to 1. If the second RRC link abnormality event is detected within 5 minutes, the number of consecutive abnormalities is increased by 1, and so on, until the timer expires. The timer can be, for example, a T3517 timer, and this application does not specifically limit the model of the timer.

[0137] In other embodiments, if the terminal device detects that the time interval between two consecutive RRC link abnormality events is greater than the interval time threshold, it indicates that the two RRC link abnormality events may not have occurred consecutively. In other words, there may be a normal RRC link establishment and data transmission process between the two RRC link abnormality events. The terminal device then re-records the number of consecutive abnormalities within the first time period.

[0138] Specifically, it includes: if the current RRC link abnormality event is the i-th RRC link abnormality event, i is an integer greater than 1, and the time interval between the i-th RRC link abnormality event and the i-1-th RRC link abnormality event is determined. If the time interval is less than the interval time threshold, the number of consecutive abnormalities is increased by 1. If the time interval is greater than or equal to the interval time threshold, the i-th RRC link abnormality event is regarded as the first RRC link abnormality. That is, the occurrence time of the current RRC link abnormality event is used as the starting time of the first duration, and the number of consecutive abnormalities is set 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, etc.

[0139] Specifically, the interaction process between the terminal device and the network device during the process of calculating the number of consecutive exceptions within the first time period can refer to the interaction schematic diagram shown in Figure 4b.

[0140] As shown in FIG4B , 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 nth parameter-less RRC link release message to the terminal device 100 is less than or equal to the first duration T1.

[0141] The time interval between the first network device 200 sending the first service request to the terminal device 100 and the first parameter-free RRC link release message 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 second parameter-free RRC link release message to the terminal device 100 is less than or equal to the abnormal time threshold T2. Similarly, the time interval between the first network device 200 sending the nth service request to the terminal device 100 and the nth parameter-free RRC link release message to the terminal device 100 is less than or equal to the abnormal time threshold T2. In other words, 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 parameter-free RRC link release message to the terminal device 100 is less than or equal to the abnormal time threshold T2.

[0142] Furthermore, 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 second parameter-less RRC link release message to the terminal device 100 is less than the interval time threshold T3. In other words, the time interval between two adjacent times when the first network device 200 sends the parameter-less RRC link release message to the terminal device 100 is less than the time interval time threshold T3.

[0143] S403: Determine whether the number of consecutive exceptions is greater than a first exception threshold.

[0144] If the judgment result is no, indicating that the number of consecutive exceptions does not reach the first exception threshold, step S404 is executed to send a service request to the first network device in the first cell.

[0145] In some embodiments, if the judgment result is no, it means that the number of consecutive exceptions reaches the first exception threshold, and the terminal device 100 may still be unable to transmit service data if it continues to stay in the first cell, then step S405 is executed to determine the second cell and send a service request to the second network device.

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

[0147] Optionally, if the number of consecutive exceptions is greater than K, the terminal device 100 determines a second cell and sends a second RRC connection request to the second network device. The value of K can be any integer between 1 and 20. Specifically, the value of K can be 2, 3, 4, 5, 6, 7, 8, 9, etc.

[0148] In some embodiments, corresponding to the terminal device 100 sending K first RRC connection requests to the first network device 200, the number of consecutive exceptions greater than K may be: the K first response messages received within the first time period are all response messages without parameters. It will 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 requests are sent.

[0149] In other embodiments, corresponding to the terminal device 100 sending M first RRC connection requests to the first network device 200, the number of consecutive exceptions greater than K may be: the K first response messages received within the first time period 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. Specifically, the value of M can 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.

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

[0151] It is understood that in some embodiments, different types of RRC link abnormality events can be counted separately. For example, the number of consecutive abnormalities of each type of RRC link abnormality event is recorded separately, and if the number of consecutive abnormalities of any type of RRC link abnormality event is greater than a first abnormality number threshold, the corresponding operation is performed.

[0152] In other embodiments, different types of RRC link abnormality events can be counted together. For example, if the second RRC link abnormality event and the first RRC link abnormality event correspond to different types, the number of consecutive abnormalities is still increased by 1. If the number of consecutive abnormalities of the RRC link abnormality event is greater than the first abnormality threshold, the corresponding operation is performed.

[0153] In other embodiments, some types of RRC link abnormality events can be combined and counted. For example, the cases where the terminal device receives a response message without parameters sent by the network device, such as a rejection of the RRC link establishment message, an RRC link release message, a rejection of the service request message, etc., can be combined and counted.

[0154] Specifically, if the first RRC link abnormality event is that the terminal device receives a parameter-less RRC link release message sent by the network device, and the second RRC link abnormality event is that the terminal device receives a parameter-less RRC link establishment rejection message sent by the network device, the number of consecutive abnormalities will still be increased by 1.

[0155] This application does not impose any specific restrictions on the method of counting the number of consecutive exceptions.

[0156] Optionally, if the number of consecutive anomalies is greater than a first sub-anomaly threshold, the terminal device 100 performs a cell handover. If the number of consecutive anomalies is greater than a second sub-anomaly threshold, the terminal device 100 performs a cell handover again. That is, if the number of consecutive anomalies reaches a set threshold, multiple rounds of cell handovers are performed. It can be understood that multiple rounds of cell handovers are performed to ensure that users use a network with a higher network standard, thereby ensuring the user experience.

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

[0158] The terminal device determines that the number of consecutive exceptions has not reached the first exception threshold, and continues to send the first service request to the first network device in the first cell.

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

[0160] The terminal device determines that the number of consecutive exceptions reaches the first exception threshold, performs cell switching, 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.

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

[0162] In some embodiments, cell switching is achieved by setting a first cell as an inaccessible cell (bar cell), performing cell reselection and switching in cells other than the inaccessible cell, and determining a second cell.

[0163] In other embodiments, the first cell may be set as an inaccessible cell by placing the cell identifier of the first cell in an access blacklist, so that when the terminal device 100 performs cell reselection, the cell in the access blacklist is not selected.

[0164] It can be understood that in the embodiment of the present application, the cell indicated by the cell identifier in the access blacklist is a cell prohibited from access. The cell identifier can be an identifier of the cell or an identifier of the frequency corresponding to the cell.

[0165] In other embodiments, a preset duration of inaccessibility may be set for the first cell. After the preset duration of setting the first cell as inaccessible, the first cell may be set as accessible. This prevents the first cell from being set as inaccessible for a long period of time and allows it to be reselected for access when the signal quality of the first cell improves or resource scheduling is normal, thereby fully utilizing network resources. The preset duration is pre-set, for example, 30 minutes, and may be modified by the network device according to actual needs. This application does not impose any restrictions on the specific value of the preset duration.

[0166] It is understood that if one network device corresponds to one cell, then the second network device corresponding to the second cell and the first network device corresponding to the first cell are different network devices. If one network device corresponds to multiple cells, then the second network device corresponding to the second cell and the first network device corresponding to the first cell can be different network devices or the same network device. This application does not impose specific restrictions on this.

[0167] S406: A second RRC link abnormality event is detected, and the number of consecutive abnormalities within a second time period is recorded.

[0168] After the terminal device performs cell switching, if the second RRC link abnormality event is still detected, the number of consecutive abnormalities within the second time period continues to be recorded.

[0169] RRC link abnormal events include, but are not limited to: the second network device fails to 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. The response message may include: RRC link establishment rejection message, RRC link release message, service request rejection message, etc.

[0170] In some embodiments, the determination of the number of consecutive anomalies within the second time period may refer to the relevant description in the aforementioned step S402.

[0171] The second time duration in step S406 may be the first time duration T1 in the aforementioned step S402 , that is, the number of abnormalities in step S406 may be counted following the aforementioned step S402 .

[0172] Alternatively, in other embodiments, after the terminal device performs a cell handover, if an RRC link abnormality event is still detected, the number of consecutive abnormalities may be re-recorded. That is, the second duration is determined to be the second duration T4, and the number of consecutive abnormalities within the second duration T4 is recorded, and then the number of abnormalities in step S406 is counted from zero. In other words, the second duration T4 may be equal to the above-mentioned first duration T1, or may not be equal to the above-mentioned first duration T1, and this application does not impose any restrictions on this.

[0173] The number of consecutive anomalies recorded within the second time period T4 can refer to the relevant description in the above S402, and the number will not be repeated.

[0174] S407: Determine whether the number of consecutive abnormalities is greater than a second abnormality threshold.

[0175] If the judgment result is no, indicating that the number of consecutive exceptions does not reach the second exception threshold, step S408 is executed to send a second service request to the second network device in the second cell.

[0176] In some embodiments, if the judgment result is no, it means that the number of consecutive exceptions reaches the second exception threshold, and the terminal device may still be unable to transmit service data by continuing to send the second service request to the second network device, then step S409 is executed to determine the third cell and send the third service request to the third network device.

[0177] Optionally, when the number of consecutive exceptions reaches a first exception threshold, the terminal device 100 determines a third cell and sends a third service request to a third network device.

[0178] Optionally, if the number of consecutive exceptions is greater than P, the terminal device 100 determines a third cell and sends a third RRC connection request to the third network device. The value of P can be any integer between 1 and 20. Specifically, the value of P can be 2, 3, 4, 5, 6, 7, 8, 9, etc.

[0179] 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 exceptions greater than P may be: the P second response messages received within the second time period are all response messages without parameters. It will 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 requests are sent.

[0180] 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 exceptions greater than P may be: the P second response messages received within the second time period are all response messages without parameters. Wherein, 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.

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

[0182] It is understood that if, in S406 above, recording the number of consecutive anomalies within the second duration is to continue recording the number of consecutive anomalies within the first duration, then the second anomaly count threshold is greater than the first anomaly count threshold. If, in S406 above, recording the number of consecutive anomalies within the second duration is to re-record the number of consecutive anomalies within the second duration, then the second anomaly count threshold may be equal to the first anomaly count threshold, or may not be equal to the first anomaly count threshold.

[0183] S408: Send a second service request to the second network device in the second cell.

[0184] The terminal device determines that the number of abnormalities has not reached the second abnormality threshold, and continues to send service requests to the second network device in the second cell.

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

[0186] The terminal device determines that the number of abnormalities reaches the second abnormality threshold, and lowers the network standard, that is, sends a third service request to the third network device in the third cell.

[0187] Optionally, when the number of consecutive exceptions reaches a first exception threshold, the terminal device 100 determines a third cell and sends a third service request to a third network device.

[0188] It is understandable that the network standard 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.

[0189] Exemplarily, when the first network device is a gNodeB and the third network device is an eNodeB, as shown in FIG4c , the network signal icon in the display interface of the terminal device 100 may be switched from a 5G icon 40a to a 4G icon 40b.

[0190] Specifically, the method for the terminal device to reduce the network standard includes:

[0191] (1) disabling the first network frequency band or disabling the first network capability, for example, disabling the NR frequency band or disabling the NR capability.

[0192] (2) Disconnecting from the second network device, performing a cell search in the second network frequency band (e.g., TDD band or FDD band), and determining a third cell. Specifically, during the cell search, the terminal device 100 reads system information of each cell, such as parameters such as RSRP and RSRQ, prioritizes the searched cells based on the system information of each cell, and selects the cell with the highest priority as the third cell.

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

[0194] It can be understood that in other embodiments, according to actual needs, the steps shown in Figure 4a above 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 impose any restrictions here.

[0195] In some embodiments, after the terminal device lowers the network standard, it evaluates the network status of the second network, and cancels the lowering of the network standard if a network abnormality occurs.

[0196] It is understood that since sending a service request triggers RRC link establishment, that is, sending a service request simultaneously sends an RRC connection request. Therefore, the first service request in Figure 4a and its 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.

[0197] For example, Figure 5 illustrates a schematic flow chart of a terminal device evaluating the network status of a second network according to an embodiment of the present application. It will be appreciated that each step of the process illustrated in Figure 5 is performed by the terminal device. For simplicity, the following description of the individual steps in the process illustrated in Figure 5 will not be repeated.

[0198] As shown in Figure 5, the process includes:

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

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

[0201] If the judgment result is yes, it indicates 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.

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

[0203] The network abnormality includes but is not limited to: the network signal corresponding to the third network device is lower than the signal threshold, or the RRC link continuous abnormality as shown in FIG4 a occurs.

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

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

[0206] 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. This application does not impose any restrictions on this.

[0207] Specifically, canceling the downgrade of the network standard may include: releasing the disablement of the first network frequency band or the first network capability, etc.

[0208] It is understood that after a network anomaly occurs on the second network, 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, thereby ensuring that the user uses a network of a higher network standard and thus protecting the user's user experience. For example, if a network anomaly occurs on the 4G network, an attempt is made to resume using the 5G network.

[0209] It is understood that in some embodiments, if a network anomaly occurs on the third network device, the terminal device may disconnect from the third network device and establish a communication connection with a fifth network device, where 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 4G, and the network standard corresponding to the fifth network device is 3G. In other words, if a network anomaly occurs on the third network device, the terminal device may continue to execute the process shown in Figure 4a.

[0210] It is understandable that since the network device corresponding to the first network standard has continuously detected RRC link abnormality events during the connection with the network device corresponding to the second network standard, if the service request is resumed to the network device corresponding to the first network, the RRC link abnormality events may still be continuously detected.

[0211] Therefore, after a network anomaly occurs in the second network, the service request is not resumed 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 this method has a higher success rate in completing the RRC link establishment and data transmission.

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

[0213] The terminal device determines that no network abnormality occurs in the second network, and then continues to communicate with the third network device in the third cell.

[0214] In order 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.

[0215] Example 1

[0216] The following takes the RRC link abnormality where the first network device fails to respond to the RRC connection request of the terminal device within a preset time as an example to introduce the interaction process of the RRC link abnormality between the terminal device and the network device.

[0217] Exemplarily, FIG6 shows a schematic diagram of an interaction process of an abnormal RRC link between a terminal device and a network device according to an embodiment of the present application.

[0218] As shown in Figure 6, the process includes:

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

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

[0221] S603: The terminal device 100 completes RRC link establishment with the first network device 200.

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

[0223] Specifically, S601 to S604 may refer to the relevant descriptions in the above S301 to S304, and will not be repeated here.

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

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

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

[0227] The communication service triggering event triggers RRC link establishment. The terminal device 100 sends a first service request to the first network device 200 and sends a first RRC connection request to the first network device 200 at the same time.

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

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

[0230] It can be understood that the expiration of the T300 timer indicates that the first network device 200 has not responded to the first RRC connection request of the terminal device 100 within the preset time.

[0231] S608: The terminal device 100 performs cell switching corresponding to the number of consecutive abnormalities being greater than the first abnormality threshold.

[0232] The terminal device 100 records the number of consecutive exceptions within the first time period, and performs cell switching when the number of consecutive exceptions is greater than the first exception threshold. It can be understood that the number of consecutive exceptions is the number of consecutive times the T300 timer is detected to have timed out.

[0233] In some embodiments, the number of consecutive exceptions may be determined by:

[0234] (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 starting time of the first duration, and the number of consecutive exceptions is set to 1. It is understood that the length of the first duration can be pre-set, for example, 5 minutes.

[0235] (2) If the current T300 timer timeout is the i-th T300 timer timeout, where i is an integer greater than 1, determine the time interval between the i-th T300 timer timeout and the (i-1)-th T300 timer timeout. If the time interval is less than the interval time threshold, add 1 to the number of consecutive exceptions. If the time interval is greater than or equal to the interval time threshold, treat the i-th T300 timer timeout as the first T300 timer timeout, that is, treat the time when the current T300 timer timeout occurs as the starting time of the first duration, and set the number of consecutive exceptions to 1. It will be understood that the interval time threshold can be pre-set, for example, 2s.

[0236] For the specific description of cell switching, please refer to the relevant description in Figure 4a above, and this application will not go into details here.

[0237] S609 to S612 are described below by taking an example of switching a cell, where the cell after switching and the previous cell correspond to the same network device (the first network device 200 ).

[0238] 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 performed in the first cell. In the following S609 to S612, the communication between the terminal device 100 and the first network device 200 is performed in the second cell.

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

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

[0241] If the number of consecutive exceptions is greater than the first exception threshold, the terminal device 100 sends a second service request to the first network device 200 again after performing cell switching.

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

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

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

[0245] S612: The terminal device 100 reduces the network standard when the number of consecutive exceptions is greater than the second exception threshold.

[0246] The terminal device 100 continues to record the number of consecutive exceptions within the first duration. If the number of consecutive exceptions exceeds the second exception threshold, the network standard is downgraded. It is understood that the number of consecutive exceptions is the number of consecutive T300 timer timeouts. The method for continuing to record the number of consecutive exceptions within the first duration can also refer to the aforementioned step S608.

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

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

[0249] Example 2

[0250] The following takes the RRC link abnormality in which the first network device sends a parameter-free service rejection request to the terminal device as an example to introduce the interaction process of the RRC link abnormality between the terminal device and the network device.

[0251] For example, FIG7 shows a schematic diagram of an interaction process for an abnormal RRC link between a terminal device and a network device according to an embodiment of the present application. After the terminal device 100 executes steps S601 to S604 shown in FIG6 above, the interaction process after detecting a communication service triggering event is shown in FIG7, specifically including:

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

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

[0254] In some embodiments, a communication service triggering event triggers RRC link establishment, and the terminal device 100 sends a first service request to the first network device 200 while sending a first RRC connection request to the first network device 200.

[0255] S702: The terminal device 100 completes RRC link establishment with the first network device 200.

[0256] In some embodiments, the communication service triggering event triggers RRC link establishment, and the terminal device 100 performs RRC link establishment with the first network device 200 and completes the establishment. Specifically, the process of completing the RRC link establishment can refer to the relevant description in S303 above, which is not repeated here.

[0257] S703: The first network device 200 sends a first parameter-free service request rejection message to the terminal device 100.

[0258] After the terminal device 100 completes the RRC link establishment with the first network device 200, that is, after the first network device 200 receives the RRC link establishment completion message sent by the terminal device 100, it sends a parameter-free service rejection request to the terminal device 100.

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

[0260] After receiving the first parameter-free service rejection request message sent by the first network device 200, the terminal device 100 determines that the RRC link abnormality event is that the first network device sends a parameter-free service rejection request message to the terminal device.

[0261] S705: The terminal device 100 performs cell switching corresponding to the number of consecutive abnormalities being greater than the first abnormality threshold.

[0262] The terminal device 100 records the number of consecutive exceptions within the first time period, and performs cell switching when the number of consecutive exceptions is greater than the first exception threshold. It can be understood that the number of consecutive exceptions is the number of times the service request is rejected with no parameters.

[0263] It can be understood that in some embodiments, different types of service request rejection messages can be counted separately, for example, the number of consecutive exceptions of each type of service request rejection message (such as SRReject#9, SRReject#10, SRReject#111, etc.) can be recorded separately. If the number of consecutive exceptions of any type of service request rejection message is greater than the first exception number threshold, the corresponding operation is performed.

[0264] In other embodiments, different types of service request rejection messages may be combined and counted. For example, if the second service request rejection message corresponds to a different type than the first service request rejection message, the number of consecutive exceptions is still incremented by 1; if the number of consecutive exceptions exceeds the first exception threshold, the corresponding operation is performed. This application does not impose specific limitations on this.

[0265] Specifically, reference may be made to the relevant description in S608 in FIG6 , and this application will not elaborate on it here.

[0266] S706 to S710 are described below by taking an example of switching a cell, where the cell after switching and the previous cell correspond to the same network device (the first network device 200 ).

[0267] 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 performed in the first cell. In the following S706 to S710, the communication between the terminal device 100 and the first network device 200 is performed in the second cell.

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

[0269] If the number of consecutive exceptions is greater than the first exception threshold, the terminal device 100 sends a second service request to the first network device 200 again after performing cell switching.

[0270] S707: The terminal device 100 completes RRC link establishment with the first network device 200.

[0271] S708: The first network device 200 sends a second parameter-free service request rejection message to the terminal device 100.

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

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

[0274] S710: The terminal device 100 reduces the network standard when the number of consecutive abnormalities is greater than the second abnormality threshold.

[0275] The terminal device 100 continues the first duration of continuous abnormality times, corresponding to the continuous abnormality times being greater than the second abnormality times threshold, and reduces the network mode. It can be understood that the continuous abnormality times are the times of continuously determining the RRC link abnormality event as the parameter-free rejection service request message.

[0276] Specifically, reference may be made to the relevant description in S612 in FIG6 , and this application will not elaborate on it here.

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

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

[0279] Example 3

[0280] The following takes the RRC link abnormality in which the first network device sends a parameter-free RRC link establishment rejection message to the terminal device as an example to introduce the interaction process of the RRC link abnormality between the terminal device and the network device.

[0281] Exemplarily, FIG8 shows a schematic diagram of an interaction process of an abnormal RRC link between a terminal device and a network device according to an embodiment of the present application.

[0282] After the terminal device 100 executes steps S601 to S604 shown in FIG6 , the interaction process after detecting the communication service triggering event is shown in FIG8 , which specifically includes:

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

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

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

[0286] It can be understood that the communication service triggering event triggers RRC link establishment, and the terminal device 100 sends a first service request to the first network device 200 while sending a first RRC connection request to the first network device 200.

[0287] S803: The first network device 200 sends a first parameter-free RRC link establishment rejection message to the terminal device 100.

[0288] After receiving the first RRC connection request sent by the terminal device 100, the first network device 200 sends a first parameter-free RRC link establishment rejection message to the terminal device 100.

[0289] S804: The terminal device 100 determines that the exception is a parameter-free rejection RRC link establishment message.

[0290] After the terminal device 100 receives the first parameter-free RRC link establishment rejection message sent by the first network device 200, it determines that the RRC link abnormality event is that the first network device sends a parameter-free RRC link establishment rejection message to the terminal device.

[0291] S805: The terminal device 100 performs cell switching corresponding to the number of consecutive abnormalities being greater than the first abnormality threshold.

[0292] The terminal device 100 records the number of consecutive exceptions within the first time period, and performs cell switching when the number of consecutive exceptions is greater than the first exception threshold. It can be understood that the number of consecutive exceptions is the number of times the RRC link abnormality event is continuously determined to be a parameter-free rejection RRC link establishment message.

[0293] Specifically, reference may be made to the relevant description in S608 in FIG6 , and this application will not elaborate on it here.

[0294] S806 to S810 are described below by taking an example of switching a cell, where the cell after switching and the previous cell correspond to the same network device (the first network device 200 ).

[0295] 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 performed in the first cell. In the following S806 to S810, the communication between the terminal device 100 and the first network device 200 is performed in the second cell.

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

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

[0298] If the number of consecutive exceptions is greater than the first exception threshold, the terminal device 100 sends a second service request to the first network device 200 again after performing cell switching.

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

[0300] S808: The terminal device 100 determines that the exception is a parameter-free rejection RRC link establishment message.

[0301] S809: The first network device 200 sends a second parameter-free RRC link establishment rejection message to the terminal device 100.

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

[0303] S810: The terminal device 100 reduces the network standard when the number of consecutive abnormalities is greater than the second abnormality threshold.

[0304] The terminal device 100 continues to record the number of consecutive exceptions within the first time period, and corresponding to the number of consecutive exceptions being greater than the second exception threshold, the network standard is lowered. It can be understood that the number of consecutive exceptions is the number of times the RRC link abnormality event is continuously determined to be a parameter-free rejection RRC link establishment message.

[0305] Specifically, reference may be made to the relevant description in S612 in FIG6 , and this application will not elaborate on it here.

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

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

[0308] Example 4

[0309] The following takes the RRC link abnormality in which the first network device sends a parameter-free RRC link release message to the terminal device as an example to introduce the interaction process of the RRC link abnormality between the terminal device and the network device.

[0310] Exemplarily, FIG9 shows a schematic diagram of an interaction process of an abnormal RRC link between a terminal device and a network device according to an embodiment of the present application.

[0311] After the terminal device 100 executes steps S601 to S604 shown in FIG6 , the interaction process after detecting the communication service triggering event is shown in FIG9 , which specifically includes:

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

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

[0314] It can be understood that the communication service triggering event triggers RRC link establishment, and the terminal device 100 sends a first service request to the first network device 200 while sending a first RRC connection request to the first network device 200.

[0315] S902: The terminal device 100 completes RRC link establishment with the first network device 200.

[0316] The communication service triggering event triggers RRC link establishment, and the terminal device 100 performs RRC link establishment with the first network device 200 and completes the establishment. Specifically, the process of completing the RRC link establishment can refer to the relevant description in S303 above, which will not be repeated here.

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

[0318] After the terminal device 100 completes the RRC link establishment with the first network device 200, that is, after the first network device 200 receives the first RRC link establishment completion message sent by the terminal device 100, it sends a first service request permission to the terminal device 100.

[0319] S904: The first network device 200 sends a first parameter-free RRC link release message to the terminal device 100.

[0320] After the first network device 200 sends the first service request permission to the terminal device 100, due to network abnormality, the first parameter-free RRC link release message is sent to the terminal device 100.

[0321] S905: The terminal device 100 determines that the exception is an RRC link release message without parameters.

[0322] After the terminal device 100 receives the first parameter-free RRC link release message sent by the first network device 200, it determines that the RRC link abnormal event is that the first network device sends a parameter-free RRC link release message to the terminal device.

[0323] S906: The terminal device 100 performs cell switching corresponding to the number of consecutive abnormalities being greater than the first abnormality threshold.

[0324] The terminal device 100 records the number of consecutive exceptions within the first time period, and performs cell switching when the number of consecutive exceptions is greater than the first exception threshold. It can be understood that the number of consecutive exceptions is the number of times the RRC link abnormality event is continuously determined to be an RRC link release message without parameters.

[0325] Specifically, reference may be made to the relevant description in S608 in FIG6 , and this application will not elaborate on it here.

[0326] S907 to S912 are described below by taking an example of switching a cell, where the cell after switching and the previous cell correspond to the same network device (first network device 200 ).

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

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

[0329] If the number of consecutive exceptions is greater than the first exception threshold, the terminal device 100 sends a second service request to the first network device 200 again after performing cell switching.

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

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

[0332] S910: The first network device 200 sends a second parameter-free RRC link release message to the terminal device 100.

[0333] S911: The terminal device 100 determines that the exception is a link release message without parameters.

[0334] It can be understood that S907 to S911 can refer to the relevant descriptions in the above S901 to S905, and will not be repeated here.

[0335] S912: The terminal device 100 reduces the network standard in response to the number of consecutive abnormalities being greater than the second abnormality threshold.

[0336] The terminal device 100 continues to record the number of consecutive exceptions within the first time period, and corresponding to the number of consecutive exceptions being greater than the second exception threshold, the network standard is lowered. It can be understood that the number of consecutive exceptions is the number of times the RRC link abnormal event is continuously determined to be an RRC link release message without parameters.

[0337] Specifically, reference may be made to the relevant description in S612 in FIG6 , and this application will not elaborate on it here.

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

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

[0340] Example 5

[0341] The following takes the RRC link abnormality as a wireless link failure as an example to introduce the interaction process of the RRC link abnormality between the terminal device and the network device.

[0342] Exemplarily, FIG10 shows a schematic diagram of an interaction process of an abnormal RRC link between a terminal device and a network device according to an embodiment of the present application.

[0343] After the terminal device 100 executes steps S601 to S604 shown in FIG6 , the interaction process after detecting the communication service triggering event is shown in FIG10 , which specifically includes:

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

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

[0346] It can be understood that the communication service triggering event triggers RRC link establishment, and the terminal device 100 sends a first service request to the first network device 200 while sending a first RRC connection request to the first network device 200.

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

[0348] The communication service triggering event triggers RRC link establishment, and the terminal device 100 performs RRC link establishment with the first network device 200 and completes the establishment. Specifically, the process of completing the RRC link establishment can refer to the relevant description in S303 above, which will not be repeated here.

[0349] S1003: The terminal device 100 determines that the abnormality is a wireless link failure.

[0350] The terminal device 100 detects that the RSRP is less than the receiving power threshold, or is unable to decode physical channels such as the physical downlink shared channel (PDSCH), physical downlink control channel (PDCCH), and physical broadcast channel (PBCH), confirms that the wireless link establishment has failed, and determines that the RRC link abnormal event is a wireless link failure.

[0351] It should be understood that the terminal device 100 will detect whether the wireless link has returned to normal at a fixed frequency, for example, the fixed frequency may be once per second.

[0352] S1004: The terminal device 100 performs cell switching corresponding to the number of consecutive abnormalities being greater than the first abnormality threshold.

[0353] The terminal device 100 records the number of consecutive anomalies within the first time period, and performs cell switching when the number of consecutive anomalies is greater than the first anomaly threshold. It can be understood that the number of consecutive anomalies is the number of times the RRC link anomaly event is continuously determined to be a radio link failure.

[0354] Specifically, reference may be made to the relevant description in S608 in FIG6 , and this application will not elaborate on it here.

[0355] S1005 to S1008 are described below by taking an example of switching a cell, where the cell after switching and the previous cell correspond to the same network device (first network device 200).

[0356] 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 performed in the first cell. In the following S1005 to S1008, the communication between the terminal device 100 and the first network device 200 is performed in the second cell.

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

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

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

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

[0361] It can be understood that S1005 to S1007 can refer to the relevant descriptions in the above S1001 to S1003, and will not be repeated here.

[0362] S1008: The terminal device 100 reduces the network mode in response to the number of consecutive exceptions being greater than a second exception threshold.

[0363] The terminal device 100 continues to record the number of consecutive exceptions within the first time period, and if the number of consecutive exceptions is greater than the second exception threshold, the network standard is downgraded. It can be understood that the number of consecutive exceptions is the number of consecutive wireless link failures.

[0364] Specifically, reference may be made to the relevant description in S612 in FIG6 , and this application will not elaborate on it here.

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

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

[0367] Example 6

[0368] The following takes the RRC link abnormality as a data-free radio bearer as an example to introduce the interaction process of the RRC link abnormality between the terminal device and the network device.

[0369] Exemplarily, FIG11 shows a schematic diagram of an interaction process of an abnormal RRC link between a terminal device and a network device according to an embodiment of the present application.

[0370] After the terminal device 100 executes steps S601 to S604 shown in FIG6 , the interaction process after detecting the communication service triggering event is shown in FIG11 , which specifically includes:

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

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

[0373] It can be understood that the communication service triggering event triggers RRC link establishment, and the terminal device 100 sends a first service request to the first network device 200 while sending a first RRC connection request to the first network device 200.

[0374] 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 an idle state.

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

[0376] The communication service triggering event triggers RRC link establishment, and the terminal device 100 performs RRC link establishment with the first network device 200 and completes the establishment. Specifically, the RRC link establishment process can refer to the relevant description in S303 above, which will not be repeated here.

[0377] S1103: The terminal device 100 determines that the abnormality is that there is no data radio bearer.

[0378] No data radio bearer may include data radio bearer establishment failure and data radio bearer not being established.

[0379] For example, in some embodiments, the terminal device 100 detects a data radio bearer establishment failure, such as failure to receive a service request permission, and determines that the RRC link abnormality event is a data radio bearer establishment failure.

[0380] For another example, in some other embodiments, after receiving the service request permission, the terminal device 100 detects that the signaling radio bearer has been established but the data radio bearer has not been established, and determines that the RRC link abnormality event is that the data radio bearer has not been established.

[0381] It should be understood that the terminal device 100 will detect whether the wireless link has returned to normal at a fixed frequency, for example, the fixed frequency may be once per second.

[0382] S1104: The terminal device 100 performs cell switching corresponding to the number of consecutive abnormalities being greater than the first abnormality threshold.

[0383] The terminal device 100 records the number of consecutive exceptions within the first time period, and performs cell switching when the number of consecutive exceptions is greater than the first exception threshold. It can be understood that the number of consecutive exceptions is the number of times the RRC link abnormality event is continuously determined to be a data-free radio bearer.

[0384] Specifically, reference may be made to the relevant description in S608 in FIG6 , and this application will not elaborate on it here.

[0385] S1105 to S1108 are described below by taking an example of switching a cell, where the cell after switching and the previous cell correspond to the same network device (first network device 200).

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

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

[0388] If the number of consecutive exceptions is greater than the first exception threshold, the terminal device 100 sends a second service request to the first network device 200 again after performing cell switching.

[0389] S1106: The terminal device 100 completes RRC link establishment with the first network device 200.

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

[0391] S1108: The terminal device 100 lowers the network standard when the number of consecutive exceptions is greater than the second exception threshold.

[0392] The terminal device 100 continues to record the number of consecutive exceptions within the first time period, and corresponding to the number of consecutive exceptions being greater than the second exception threshold, the network standard is reduced. It can be understood that the number of consecutive exceptions is the number of times the RRC link abnormality event is continuously determined to be a data-free radio bearer.

[0393] Specifically, reference may be made to the relevant description in S612 in FIG6 , and this application will not elaborate on it here.

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

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

[0396] In summary, the communication method provided by the embodiments of the present application can detect the number of RRC link anomalies within a preset time period and perform cell switching and network standard downgrade operations based on the number of anomalies. This allows the terminal device to communicate normally with the network device even in the event of an RRC link anomaly, thereby maintaining the terminal device's communication services.

[0397] In order to better understand the technical solutions of the embodiments of the present application, the structure of the equipment involved in the present application is introduced below with reference to the accompanying drawings.

[0398] Exemplarily, FIG12 shows a schematic structural diagram of a terminal device 100 according to an embodiment of the present application.

[0399] As shown in Figure 12, 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 button 190, a camera 191, a display screen 192, etc.

[0400] It should be understood that the structures illustrated in the embodiments of the present application do 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 may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0401] The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (AP), a modem processor (Modem), a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor (BP), and / or a neural-network processing unit (NPU), etc. Among them, different processing units can be independent devices or integrated into one or more processors. The processor 110 can be used to execute the communication method provided in the embodiments of the present application.

[0402] The operating system running on the AP can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. The layered architecture can adopt the Android system, the iOS system, or other operating systems, which are not limited in the embodiments of the present application.

[0403] A modem, also known as a baseband processor, can include modules such as the protocol stack and physical layer for cellular communications, implementing functions such as modulation and demodulation, channel encoding and decoding, and source encoding and decoding. 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 dynamically establishes, modifies, and releases connections within the communication network, primarily processing call-related data such as routing, resource allocation, and session management. The CM module dynamically adjusts call paths based on real-time network status and user needs to ensure optimal communication quality and performance. The CC module is primarily responsible for establishing, maintaining, and releasing call connections during communications, potentially involving the processing of various protocols and signaling to ensure a stable and reliable communication link. The NAS module performs operations such as on-network access, enabling communication with network devices. It should be noted that the term "NAS module" is merely an example name and is not intended to be limiting in the present embodiments.

[0404] The modem in the embodiment of the present application can provide cellular communication capabilities. The modem runs on the baseband chip and coprocessor. The terminal device can use the modem to realize a series of cellular communication functions such as sending and receiving text messages, 5G-related functions, making calls, and answering calls.

[0405] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

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

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

[0408] The wireless communication function of the terminal device 100 can be implemented through the wireless communication module 150, the mobile communication module 160, the antenna, the modem processor and the baseband processor.

[0409] The mobile communication module 150 can provide wireless communication solutions including 2G / 3G / 4G / 5G applied on the terminal device 100.

[0410] The wireless communication module 160 can provide wireless communication solutions 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 technology (NFC), infrared technology (IR), etc.

[0411] In some embodiments, the wireless communication technology 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 code division multiple access (TDSCDMA), LTE, NR, BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. In some embodiments, the terminal device 100 communicates with the network device based on the wireless communication module 150, for example, communicates with the network device based on LTE technology, NR technology, etc.

[0412] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals.

[0413] The sensor module 180 may include a pressure sensor, a gyro sensor, an air 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, and the like.

[0414] The terminal device 100 implements the display function through a GPU, a display screen 192, and an application processor.

[0415] Display screen 192 is used to display images, videos, etc. Display screen 192 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or 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, terminal device 100 may include one or N display screens 192, where N is a positive integer greater than 1.

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

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

[0418] The memory 120 can be used to store computer executable program code, which includes instructions. The memory 120 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the terminal device 100 (such as audio data, a phone book, etc.), etc. In addition, the memory 120 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a 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 examples, the processor 110 executes the communication method provided in the embodiment of the present application by running the instructions stored in the memory 120.

[0419] The buttons 190 include a power button, a volume button, etc. The buttons 190 can be mechanical buttons or touch buttons.

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

[0421] In some embodiments, a program product is also provided, which includes instructions. 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.

[0422] In some embodiments, a chip system is also provided, which includes 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, the communication method provided in the embodiment of the present application is implemented.

[0423] The various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can 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 memory and / or storage elements), at least one input device, and at least one output device.

[0424] Program code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices in a known manner. For 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.

[0425] Program code can be implemented with a high-level programming language or an object-oriented programming language to communicate with the processing system. Where necessary, program code can also be implemented in assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0426] 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 temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, instructions may be distributed over a network or through other computer-readable media. Therefore, a machine-readable medium may include any mechanism for storing or transmitting information in a machine (e.g., computer) readable form, including but not limited to floppy disks, optical disks, optical discs, read-only memories (CD-ROMs), magneto-optical disks, read-only memories (ROMs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or a tangible machine-readable memory for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in electrical, optical, acoustic, or other forms of propagation signals. Accordingly, machine-readable media includes any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, a computer).

[0427] In the accompanying 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 order 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. In addition, the inclusion of a structural or method feature in a particular figure does not imply that such feature is required in all embodiments, and in some embodiments, such features may not be included or may be combined with other features.

[0428] It should be noted that the units / modules mentioned in the various device embodiments of the present application are all logical units / modules. Physically, a logical unit / module can be a physical unit / module, or a part of a physical unit / module, or can be implemented as a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important. The combination of functions implemented by these logical units / modules is the key to solving the technical problems raised by this application. In addition, in order to highlight the innovative part of this application, the above-mentioned device embodiments of this application do not introduce units / modules that are not closely related to solving the technical problems raised by this application. This does not mean that other units / modules do not exist in the above-mentioned device embodiments.

[0429] It should be noted that in the examples and description of this patent, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "including a" does not exclude the presence of other identical elements in the process, method, article or device that includes the element.

[0430] Although the present application has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the 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 exception event corresponding to the first RRC connection request, and determining that the number of times of generating an RRC link exception event after sending an 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 the 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 exception event.

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

4. The method according to claim 1, characterized in that The second network device corresponds to a second cell and the first network mode, and the method further includes: determining that the number of times of generating an RRC link exception event after sending an 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, characterized in that, The second handover condition includes: the number of times of generating an RRC link exception event within the second time period is greater than a second exception number threshold, and the time interval between the generated RRC link exception event and the corresponding RRC connection request within the second time period is less than or equal to an exception time threshold, and the time interval between adjacent generated RRC link exception events within the second time period is less than an interval time threshold.

6. The method according to claim 4, wherein further including: 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 exception 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 no 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 no 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, wherein Further includes: The cause value fields that are not included in 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 includes: 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 the instructions are executed on the terminal device, the terminal device executes the method according to any one of claims 1 to 11.

13. A terminal device, characterized in that, Includes: 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, Includes a processing circuit and a storage medium, and 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