Paging message processing method and device

Abstract

The invention provides a paging message processing method and device. The method comprises the following steps: a terminal in a radio resource control RRC idle state establishes a first RRC connection with network side equipment; the terminal and the network side equipment enter an RRC connection state after establishing the first RRC connection; the terminal in the RRC connection state performs a call through the first RRC connection; in a call process, a terminal receives a first Paging message sent by a network side device, the first Paging message comprises a paging record list pagingRecurdList field, the pagingRecurdList field carries a first temporary identifier of the terminal, and the first Paging message pages the terminal through the first temporary identifier of the terminal; and the terminal does not respond to the first Paging message and continues the call through the first RRC connection. Therefore, after receiving the first Paging message for paging the terminal, the terminal which is in the RRC Connected state and performs the call can continue the currently performed call, so that the current call drop caused by responding to the first Paging message is prevented, and the success rate of the call and the user experience are improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a paging message processing method and device. Background Art

[0002] When a user is using a terminal to make a call, if the terminal receives a paging message, the user will find that the current call will be automatically hung up, which reduces the success rate of the call and affects the user experience. Summary of the invention

[0003] The present application provides a paging message processing method and device to improve the call success rate and user experience. Some embodiments of the present application provide the following technical solutions:

[0004] In the first aspect, an embodiment of the present application provides a paging message processing method, the method comprising: a terminal in a radio resource control RRC idle state establishes a first RRC connection with a network side device; the terminal enters an RRC connection Connected state after establishing the first RRC connection with the network side device; the terminal in the RRC Connected state makes a call through the first RRC connection; during the call, the terminal receives a first paging message sent by the network side device, the first Paging message includes a paging record list pagingRecordList field, the pagingRecordList field carries a first temporary identifier of the terminal, and the first Paging message pages the terminal through the first temporary identifier of the terminal; the terminal does not respond to the first Paging message, and continues the call through the first RRC connection. Thus, after receiving the first Paging message paging itself, the terminal in the RRC Connected state and in the middle of a call can continue the current call, thereby preventing the current call from being dropped due to responding to the first Paging message, and improving the call success rate and user experience. Because a terminal in the RRC Connected state and in the middle of a call can continue the ongoing call after receiving the first Paging message paging itself, the terminal interface (such as the call interface) can display the call in progress, and the user can continue the call through the terminal, thereby improving the user experience.

[0005] In a possible implementation, the method also includes: before the terminal establishes a first RRC connection with the network side device, the terminal in the RRC Idle state receives a second paging message sent by the network side device, the second Paging message includes a paging record list pagingRecordList field, the pagingRecordList field carries the second temporary identifier of the terminal, and the second Paging message pages the terminal through the second temporary identifier of the terminal; the terminal responds to the second Paging message. The second temporary identifier may be the same as or different from the first temporary identifier. After receiving the second Paging message paging itself, the terminal in the RRC Idle state may respond to the second Paging message to establish a first RRC connection with the network side device. After completing the first RRC connection, the terminal switches from the RRC Idle state to the RRC Connected state, and the terminal may make a call through the first RRC connection.

[0006] In a possible implementation manner, the terminal responding to the second Paging message includes: the terminal sending an RRC connection request to a network side device to establish a first RRC connection.

[0007] In a possible implementation, the method further includes: during a call, the terminal receives a third paging message sent by a network side device, the third paging message includes at least one of a system information change systemInfoModification field, an earthquake and tsunami warning system notification indication etws-indication field, and a public warning system notification indication cmas-Indication field, the systemInfoModification field carries the changed system information, the etws-indication field carries the earthquake and tsunami warning system etws notification, the cmas-Indication field carries the public warning system cmas notification, and the third paging message is used to notify the terminal of at least one of a change in system information, receiving an etws notification, and receiving a cmas notification; the terminal responds to the third paging message. Thus, when a terminal in an RRC Connected state and making a call receives a third paging message carrying a notification, such as a notification of a change in system information, an etws notification, and a cmas notification, the terminal will respond to the third paging message and promptly process the notification carried in the third paging message. In one possible case, the terminal responding to the third Paging message may cause the call conducted through the first RRC connection to be affected, such as the ongoing call may be interrupted or automatically hung up or there may be a short period of silence.

[0008] In one implementation, after a terminal in the RRC Connected state and in a call receives a third Paging message carrying a notification, the terminal responds to the third Paging message and the current call may be automatically disconnected. The terminal interface will then display that the call is over and the user will sense that the call has been dropped.

[0009] In one possible implementation, the terminal does not respond to the first Paging message, including: the terminal does not release the RRC resources corresponding to the first RRC connection, does not switch from the RRC Connected state to the RRC Idle state, does not send a request to trigger re-establishment of the RRC connection to the network side device, and does not send an RRC connection request to the network side device.

[0010] In this embodiment, a terminal in the RRC Connected state and in a call may perform at least one of the following operations in response to the Paging message after receiving a Paging message for paging itself: releasing the RRC resources corresponding to the RRC connection used for the call, switching from the RRC Connected state to the RRC Idle state, sending a request to trigger re-establishment of the RRC connection to the network side device, or sending an RRC connection request to the network side device. These operations will cause the ongoing call of the terminal to be automatically hung up. However, for a terminal in the RRC Connected state and in a call, before receiving the first Paging message for paging itself, both the uplink call and the downlink call are normal. The terminal in the RRC Connected state does not need to perform these operations, that is, it is not necessary to perform the process of releasing the radio control resources (i.e., local release) and re-establishing the RRC connection to synchronize the state with the network side device. After the terminal performs the local release, the terminal switches from the RRC Connected state to the RRC Idle state, and the process of re-establishing the RRC connection includes sending a request to trigger re-establishment of the RRC connection to the network side device and sending an RRC connection request to the network side device. Therefore, after receiving the first Paging message for paging itself, a terminal in the RRCConnected state and in a call can reduce (or even stop) executing operations such as local release and re-establishing the RRC connection, thereby reducing call drops caused by these operations and improving the call success rate and user experience.

[0011] In one possible implementation, the terminal responds to the third Paging message including at least one of the following: the terminal releases the RRC resources corresponding to the first RRC connection, the terminal switches from the RRC Connected state to the RRC Idle state, the terminal sends a request to trigger re-establishment of the RRC connection to the network side device, or the terminal sends an RRC connection request to the network side device.

[0012] In a possible implementation, the terminal does not respond to the first Paging message including: when the call success rate of the terminal is greater than a threshold value, and / or the voice data reception and transmission on the Internet Protocol Multimedia Subsystem dedicated bearer is normal within a first preset time period before receiving the first Paging message, the terminal does not respond to the first Paging message; the call success rate of the terminal is used to indicate the probability that the call of the terminal is not automatically disconnected after the terminal receives the first Paging message sent by the network side device under the first scenario within the historical time period, and the terminal does not respond to the first Paging message, the first scenario being that the terminal is in the RRC Connected state and is in the process of making a call through the network side device.

[0013] Among them, the Internet Protocol Multimedia Subsystem dedicated bearer is an IMS dedicated bearer allocated by the network side device to the terminal for carrying voice services, and voice data is sent and received through the IMS dedicated bearer, such as the DRB#3 allocated by the LTE base station to the terminal as described below, and the DRB#2 allocated by the NR base station to the terminal as described below. The first preset time period can be X seconds as described below, and X is greater than or equal to 1. In this embodiment, the terminal can pre-set a preset condition for not responding to the first paging message. The preset condition can be that the call success rate of the terminal is greater than a threshold, or that the voice data on the Internet Protocol Multimedia Subsystem dedicated bearer is normal in the first preset time period before receiving the first Paging message, or that the call success rate of the terminal is greater than a threshold and the voice data on the Internet Protocol Multimedia Subsystem dedicated bearer is normal in the first preset time period before receiving the first Paging message. In this way, the terminal in the RRC Connected state and making a call does not respond to the first Paging message when it receives the first Paging message paging itself and meets the preset condition. Because the call success rate of the terminal is greater than the threshold, and / or the voice data reception and transmission on the Internet Protocol Multimedia Subsystem dedicated bearer is normal within the first preset time period before receiving the first Paging message, which enables the terminal to make a call as normally as possible. Therefore, when the terminal meets these conditions, not responding to the first Paging message can ensure the normal progress of the call, thereby improving the call success rate and user experience.

[0014] In some examples, normal voice data reception and transmission on the Internet Protocol Multimedia Subsystem dedicated bearer may mean that a terminal in the RRC Connected state can send voice data to the other party through the network side device, and that the terminal in the RRC Connected state can receive voice data from the other party sent by the network side device.

[0015] In some examples, the terminal may set an initial value for the call success rate in advance. When the terminal in the RRCConnected state receives the first Paging message for paging itself for the first time, the terminal may use the initial value of the call success rate to determine whether to not respond to the first Paging message, and monitor whether the call is disconnected due to a network abnormality when not responding to the first Paging message, so as to update the call success rate based on whether the call is disconnected due to a network abnormality.

[0016] In some examples, a terminal in the RRC Connected state may not respond to the first Paging message directly after receiving the first Paging message for paging itself. After the call success rate is calculated, if the terminal receives the first Paging message sent by the network side device for paging the terminal, the call success rate value is used to decide whether to respond to the first Paging message. That is, the call success rate of the terminal is calculated by the call situation after not responding to the first Paging message in the historical time period under the first scenario. The call success rate of the terminal is used to represent the probability that the call of the terminal is not automatically hung up after the terminal receives the first Paging message sent by the network side device in the first scenario in the historical time period, and the terminal does not respond to the first Paging message. The first scenario is that the terminal is in the RRC Connected state and is in the process of making a call through the network side device.

[0017] In a possible implementation, after the terminal does not respond to the first Paging message, the method further includes: detecting whether the voice data transmission and reception on the Internet Protocol Multimedia Subsystem dedicated bearer is normal after the first Paging message is not responded to, and / or whether the call continued through the network side device after the first Paging message is not responded to is automatically hung up due to network abnormality; if the voice data transmission and reception is normal, and / or the call is not automatically hung up due to network abnormality, after the terminal receives the first Paging message sent by the network side device again, the terminal does not respond to the first Paging message received again; if the voice data transmission and reception is abnormal, and / or the call is automatically hung up due to network abnormality, after the terminal receives the first Paging message sent by the network side device again, the terminal responds to the first Paging message received again; wherein the first Paging message received again is the first Paging message sent again by the network side device during the process of the terminal being in the RRC Connected state and continuing the call through the network side device, or the first Paging message sent by the network side device during the process of the terminal being in the RRC Connected state and making the next call through the network side device.

[0018] Among them, the abnormal voice data transmission and reception situation may refer to that the terminal in the RRC Connected state cannot send voice data to the call partner through the network side device, and the terminal in the RRC Connected state does not receive the voice data of the call partner sent by the network side device. After the terminal does not respond to the first Paging message, the terminal can monitor the voice data transmission and reception situation on the dedicated bearer of the Internet Protocol Multimedia Subsystem and / or the call continued through the network side device, so as to decide whether to respond to the first Paging message according to the monitoring result after receiving the first Paging message again. For example, after not responding to the first Paging message, if the voice data transmission and reception situation is normal, and / or the call is not automatically hung up due to network abnormality, after the terminal receives the first Paging message sent by the network side device again, the terminal does not respond to the first Paging message received again; and if the voice data transmission and reception situation is abnormal, and / or the call is automatically hung up due to network abnormality, after the terminal receives the first Paging message sent by the network side device again, the terminal responds to the first Paging message received again, so as to ensure the normal conduct of the call as much as possible when there is no need to respond to the first Paging message, and can respond in time when it is necessary to respond to the first Paging message.

[0019] In one possible implementation, detecting whether the voice data reception and transmission on the dedicated bearer of the Internet Protocol Multimedia Subsystem is normal after not responding to the first Paging message, and / or whether the call continued through the network side device after not responding to the first Paging message is automatically hung up due to a network abnormality includes: detecting whether the voice data reception and transmission on the dedicated bearer of the Internet Protocol Multimedia Subsystem is normal within a second preset time period after not responding to the first Paging message, and / or whether the call continued through the network side device after not responding to the first Paging message is automatically hung up due to a network abnormality within a third preset time period.

[0020] In some examples, the second preset time period may be the following t1 seconds, t1 may be greater than or equal to 1, and the third preset time period may be the following t seconds, t may be greater than or equal to 1. If the voice data is sent and received normally within the second preset time period, and / or the call is not automatically disconnected due to network abnormality within the third time period, it means that the terminal can maintain the normal call without responding to the first Paging message, and the terminal's non-response to the first Paging message is effective (which can be understood as bringing benefits to the current call); if the voice data is sent and received abnormally within the second preset time period, and / or the call is automatically disconnected due to network abnormality within the third time period, it is considered that non-response to the first Paging message is invalid (which can be understood as not bringing benefits to the current call), and thus, the terminal can decide whether to respond to the first Paging message when receiving the first Paging message sent by the network side device for paging the terminal again, based on whether non-response to the first Paging message brings benefits to the current call. Optionally, the terminal can decide whether not to respond to the first Paging message based on the time interval of receiving the first Paging message again. If the time interval between not responding to the first Paging message and receiving the first Paging message again is short, the possibility of the capability of the network side device changing in a short period of time is small. The accuracy is improved by deciding whether to respond to the first Paging message based on the capability of the network side device in a short period of time.

[0021] In a possible implementation, the starting point of any time period in the second preset time period and the third preset time period is any time point when the terminal receives the first Paging message, when the terminal determines that the first temporary identifier carried in the first Paging message matches the first temporary identifier pre-assigned to the terminal, and when the terminal does not respond to the first Paging message, and the end point of any time period in the second preset time period and the third preset time period is a time point after not responding to the first Paging message.

[0022] In a possible implementation, after the terminal does not respond to the first Paging message, the method also includes: if the voice data reception and transmission on the Internet Protocol Multimedia Subsystem dedicated bearer of the terminal is normal after the terminal does not respond to the first Paging message, and / or the call continued through the network side device after the terminal does not respond to the first Paging message is not automatically hung up due to network abnormalities, the terminal increases the value of the call success rate; if the voice data reception and transmission on the Internet Protocol Multimedia Subsystem dedicated bearer of the terminal does not respond to the first Paging message is abnormal, and / or the call continued through the network side device after the terminal does not respond to the first Paging message is automatically hung up due to network abnormalities, the terminal reduces the value of the call success rate.

[0023] In some examples, the terminal may start a timer without responding to the first Paging message; for example, the timer may be started after not responding to the first Paging message. The terminal may also set a preset duration corresponding to the timer, and in the process of determining whether the voice data reception and transmission is normal and / or whether the call is automatically disconnected due to a network abnormality, determine the processing of the call success rate value in combination with whether the timer timing is greater than the preset duration. For example, in one method, after determining that the voice data reception and transmission situation within a unit time (such as one second) is normal and / or the call is not automatically hung up due to a network abnormality, further determine whether the timer timing is greater than a preset duration. If the timer timing is greater than the preset duration, determine that the timer timing has timed out, and combine the judgment and increase the value of the call success rate; if the timer timing is less than the preset duration, continue to determine whether the voice data reception and transmission situation within a unit time (such as one second) is normal and / or whether the call is automatically hung up due to a network abnormality, and the timer continues to count; if it is determined that the voice data reception and transmission situation within a unit time (such as one second) is abnormal and / or the call is automatically hung up due to a network abnormality, reduce the value of the call success rate to improve the accuracy of the call success rate.

[0024] In one possible implementation, the method also includes at least one of the following: the first temporary identifier and / or the second temporary identifier is a temporary mobile user identifier for system architecture evolution; or, the network side device is a long term evolution base station, and the request that triggers re-establishing the RRC connection is a tracking area update request message; or, the network side device is a new wireless / new air interface base station, and the request that triggers re-establishing the RRC connection is a registration request.

[0025] In a second aspect, the present application provides a terminal, which includes: one or more processors and a memory; the memory is used to store computer program code, the computer program code includes computer instructions, and when the one or more processors execute the computer instructions, the terminal executes the above-mentioned paging message processing method.

[0026] In a third aspect, the present application provides a chip system, which is applied to a terminal. The chip system includes at least one processor and an interface, and the interface is used to receive instructions and transmit them to at least one processor; at least one processor runs the instructions so that the terminal executes the above-mentioned paging message processing method. Among them, the chip system can be a modem processor (Modem), or a system on chip (System on Chip, Soc) including a Modem, and the above-mentioned paging message processing method can be implemented by a Modem. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 A signaling diagram for UE processing of Paging messages provided in an embodiment of the present application;

[0028] Figure 2 Another signaling diagram for UE processing of Paging message provided in an embodiment of the present application;

[0029] Figure 3 A signaling diagram for processing a Paging message provided in an embodiment of the present application;

[0030] Figure 4 A message structure diagram of a Paging message provided in an embodiment of the present application;

[0031] Figure 5 Another message structure diagram of the Paging message provided in the embodiment of the present application;

[0032] Figure 6 A signaling diagram for Paging message processing in an LTE network provided in an embodiment of the present application;

[0033] Figure 7 A signaling diagram for Paging message processing in an NR network provided in an embodiment of the present application;

[0034] Figure 8 A schematic diagram of a code for a UE to re-establish an RRC connection after receiving a Paging message provided in an embodiment of the present application;

[0035] Fig. 9 A code diagram of an RRC connection request provided in an embodiment of the present application;

[0036] Fig.10 A schematic diagram of a code for abnormal call hang-up provided in an embodiment of the present application;

[0037] Fig.11 A signaling diagram of a paging message processing method provided in an embodiment of the present application;

[0038] Fig.12 Another signaling diagram of the paging message processing method provided in an embodiment of the present application;

[0039] Fig.13 Another signaling diagram of the paging message processing method provided in the embodiment of the present application;

[0040] Fig.14 Another signaling diagram of the paging message processing method provided in the embodiment of the present application;

[0041] Fig.15 A hardware structure diagram of a terminal provided in an embodiment of the present application;

[0042] Fig.16 A software architecture diagram of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to be used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "one", "a kind", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the embodiments of the present application, "one or more" refers to one, two or more; "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist; for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0044] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear at different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0045] The multiple involved in the embodiments of the present application means greater than or equal to two. It should be noted that in the description of the embodiments of the present application, the words "first", "second", etc. are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order.

[0046] Figure 1 The figure shows an example of a terminal (ie, UE) in a radio resource control connected state (RRC Connected state) receiving a paging message sent by a network side device (such as a base station) in a call scenario. Figure 1 In the example, UE1 and UE2 are in the RRC Connected state, and UE1 and UE2 are communicating through the base station. During the communication process, at least one of UE1 and UE2 can receive a Paging message sent by the base station, such as Figure 1 UE1 receives a Paging message sent by the base station. After receiving the Paging message, UE1 determines that the Paging message is a message for paging UE1, then UE1 responds to the Paging message, and the response to the Paging message includes at least one item: releasing RRC resources, switching from the RRC Connected state to the RRC Idle state, sending a request to the base station to trigger re-establishment of the RRC connection, or sending an RRC connection request to the base station, and the UE1 interface displays that the call is over. As a result, after a UE in the RRC Connected state and in the process of a call receives a Paging message paging itself, the call is automatically hung up, thereby reducing the success rate of the call and affecting the user experience.

[0047] Some embodiments of the present application provide a paging message processing method, wherein a UE in an RRC Connected state and in a call process may not respond to a paging message after receiving a paging message for itself, so as to improve the call success rate and user experience. Figure 2 As shown, UE1 and UE2 in the RRC Connected state have a call through the base station. During the call, UE1 receives a Paging message sent by the base station for paging UE1, and UE1 does not respond to the Paging message. The response to the Paging message includes: not releasing RRC resources, not switching from the RRC Connected state to the RRC Idle state, not sending a request to trigger re-establishing the RRC connection to the base station, and not sending an RRC connection request to the base station. In addition, the interface of UE1 shows that the call is in progress, reducing the call termination caused by Paging messages, thereby improving the call success rate and user experience.

[0048] For ease of understanding, several terms and related technologies involved in some embodiments of the present application are briefly introduced below.

[0049] 1. Radio resource control (RRC) state: RRC states include: connected state and idle state. The connected state (RRC Connected state, also called RRC Connected state or connected state) may refer to the establishment of an RRC connection between a terminal (i.e., UE) and an access network device (such as a base station). When the UE is in the RRC Connected state, the connection between the UE and the access network device, and the connection between the access network device and the core network device have been established. If there is data to be transmitted, it can be completed directly through the established connection.

[0050] Idle state (RRC Idle state, also called RRC Idle state or idle state): It may mean that the RRC connection between the UE and the access network device is not established. When the UE is in the RRC Idle state, if there is data to be transmitted, the RRC connection between the UE and the access network device must be established before data transmission can be performed. The UE in the RRC Idle state has the following characteristics (taking the Long Term Evolution (LTE) network as an example):

[0051] (1) The base station (e.g., eNodeB) does not know whether the UE exists;

[0052] (2) There is no RRC connection between the UE and the eNodeB;

[0053] (3) The UE has been assigned a unique identifier in the Tracking Area (TA) where it is located;

[0054] (4) The UE has registered with the Mobility Management Entity (MME) and a context exists in the MME;

[0055] (5) There is no non-access stratum (NAS) layer signaling connection between the UE and the core network equipment.

[0056] 2. Paging is the process of searching for UE initiated by the network side. The triggering condition of paging may be that the network side device has signaling or data to send to the UE. The network side device includes the access network device and the core network device. When the UE is in the RRC Idle state, the signaling or data may be sent by the core network device. If the UE is in the RRC Idle state and there is no connection between the UE and the network side device, the network side device cannot send signaling or data to the UE, and the network side device does not know the location of the UE. Therefore, in the scenario where the UE is in the RRC Idle state and the network side device (such as the core network device) sends signaling or data to the UE, the network side device performs a paging through the Paging message to notify the UE that there is signaling or data to be sent to the UE. After receiving the Paging message, the UE actively establishes a connection with the network side device (such as the access network device), so that the UE enters the RRC Connected state, so that data can be sent and received between the UE and the network side device.

[0057] The paging process is as follows: Figure 3As shown, the MME sends a Paging message to a base station (such as an eNodeB). The Paging message carries a Tracking Area List (TAL) message. At least one Tracking Area Code (TAC) is recorded in the TAL. A TAC is used to identify a Tracking Area (TA). A TA includes one or more cells. The UE can reside in a cell of a TA. The eNodeB sends a Paging message to the UE in all cells belonging to the TA through a logical channel (such as a Paging Control Channel (PCCH)) according to the TA identified by the TAC in the TAL message to page the UE. The Paging message includes a domain indicating the source of the paging and a UE identifier. After receiving the Paging message and determining that the UE identifier carried in the Paging message matches its own identifier, the UE responds to the Paging message. The UE can establish an RRC connection with the eNodeB, and the UE switches from the RRC Idle state to the RRC Connected state. Among them, when the UE is in the RRC Idle state, the UE identity carried in the Paging message that triggers the UE to establish an RRC connection can be encapsulated in the paging record list (pagingRecordList) field, and the UE identity can be a system architecture evolved temporary mobile user identity (SAE-TMSI, System Architecture Evolved-Temporary Mobile Subscriber Identity, referred to as s-TMSI), and the s-TMSI can be the above-mentioned second temporary identity. For the Paging message sent by the MME to the eNodeB, please refer to Section 9.1.6 of 36.413. For the processing flow after the eNodeB receives the Paging message, please refer to Section 8.5 of 36.413, and for the Paging message sent by the eNodeB, please refer to Section 6.2.2 of 36.331. For the processing flow after the UE receives the Paging message, please refer to Section 5.3.2 of 36.331.

[0058] The functions of the Paging message include any of the following: (1) sending a call request to a UE in the RRC Idle state; for a UE in the RRC Connected state, the network-side device knows which base station the UE is connected to, so if there is an incoming call, there is no need to page it through a Paging message, and an invite message can be directly sent; (2) notifying UEs in the RRC Idle and RRC Connected states that system information has changed; (3) notifying the UE to start receiving Earthquake and Tsunami Warning System (ETMS) notifications, which include ETWS primary notifications and / or ETWS secondary notifications; (4) notifying the UE to start receiving Commercial Mobile Alert System (CMAS) notifications.

[0059] The message structure of the Paging message in the LTE network is as follows Figure 4 As shown in the figure, the pagingRecordList field is used to record the UE being paged, the system information change (systemInfoModification) field is used to indicate that the system message has changed, the earthquake and tsunami warning system notification indication (etws-Indicatiom) field is used to indicate an ETWS primary notification and / or ETWS secondary notification, and the public warning system notification indication (cmas-Indication) field is used to indicate a CMAS notification. The message structure of the Paging message in the new wireless / new air interface (New Radio, NR) network is as follows Figure 5 As shown, the pagingRecordList field is used to record the paged UE.

[0060] From the above Figure 4 and Figure 5It can be seen from the Paging message shown that for a UE in the RRC Connected state in the LTE network, the UE can perceive the notification of system message changes by receiving a Paging message. For a UE in the RRC Connected state in the NR network, system message changes are not notified by a Paging message, but are indicated by a short message (short message indicator is 10 or 11). Therefore, for a UE in the RRC Connected state, the network side device theoretically will not page the UE by sending a Paging message. However, in actual applications, the network side device will page the UE by sending a Paging message. When the UE in the RRC Connected state receives the Paging message, it believes that the state between the UE and the network side device is out of sync. Then, the UE in the RRC Connected state will local release (release the RRC connection) after receiving the Paging message, and then re-establish the RRC connection.

[0061] An example is that in a call scenario (such as the caller ringing, the called party ringing, the call being established, or the call in progress), the UE in the RRC Connected state, whether located in the NR network or the LTE network, after receiving the Paging message for paging the UE, the UE in the RRC Connected state responds to the Paging message for local release, and then re-initiates registration access to re-establish the RRC connection. However, after research, the applicant found that if the UE re-establishes the RRC connection during the call, the network side device is unlikely to reconfigure the IP Multimedia Subsystem (IP Multimedia Subsystem, IMS) dedicated bearer (i.e. 5qi=1 / QCI=1) for the UE to carry voice services, resulting in the call of the UE in the RRC Connected state being automatically hung up by the network side device with a reason value of 503 BYE\Cancel (ended), resulting in the current call of the UE in the RRC Connected state being automatically hung up (which can be understood as the current call being dropped), thereby reducing the success rate of the call and affecting the user experience. Among them, a dropped call can be an abnormal termination of a call due to some abnormal reason during the call.

[0062] In fact, for a UE in the RRC Connected state, before receiving a Paging message for paging the UE to trigger the UE to perform local release, both uplink and downlink calls are normal. The UE in the RRC Connected state does not need to perform local release and re-execute the RRC establishment process to synchronize the status with the network side device.

[0063] In conjunction with the accompanying drawings, the following describes the process of a UE in the RRC Connected state receiving a Paging message for paging the UE in a call scenario. Figure 6 , which shows that a UE in the RRC Connected state is located in an LTE network and makes a call through an LTE base station. During the call, the processing flow after receiving the Paging message, in which the LTE base station in different steps can be the same base station, can include the following steps:

[0064] S11. The UE in the RRC Connected state obtains the pre-allocated s-TMSI and data radio bearer (DRB). The s-TMSI is used to distinguish the UE. After the UE registers with the core network through the LTE base station, the UE establishes an RRC connection with the LTE base station and enters the RRC Connected state. During the registration process, the s-TMSI is allocated to the UE through the LTE base station, such as s-TMSI=ABCDEF. And during the registration process, the DRB is allocated to the UE. For example, two DRBs are allocated to the UE, which are respectively recorded as DRB#1 and DRB#2, where DRB#1 represents the data service bearer and DRB#2 represents the IMS default bearer. The IMS default bearer is used to carry the IMS signaling service. After the registration is completed, the s-TMSI and / or DRB allocated to the UE may change. After the change occurs, the LTE base station sends the changed s-TMSI and / or DRB to the UE.

[0065] If there is data or signaling interaction between the UE and the core network within the preset time length of the UE entering the RRC Connected state, the LTE base station will not release the RRC connection between the UE and the core network, thereby placing the UE in the RRC Connected state; if there is no data or signaling interaction between the UE and the core network within the preset time length of registration to the core network, the LTE base station releases the RRC connection between the UE and the UE, thereby placing the UE in the RRC Idle state. The preset time length can be pre-set in the LTE base station, and the value of the preset time length is not limited. After the UE is in the RRC Idle state, the network side device can trigger the UE to establish an RRC connection through a Paging message. After the RRC connection is established, the UE switches from the RRC Idle state to the RRC Connected state.

[0066] S12. The UE in the RRC Connected state makes a call through the LTE base station. During the call establishment process, DRB#3 is allocated to the UE in the RRC Connected state through the LTE base station. In this embodiment, DRB#3 represents an IMS dedicated bearer, which is used to carry voice services. The three DRBs DRB#1, DRB#2, and DRB#3 are only examples. This embodiment does not limit the DRB and the type of service carried by each DRB. Among them, a call refers to a voice call, such as when the UE, as the calling party, initiates a call to the called party through a telephone application; if the UE, as the called party, receives the call from the calling party through the telephone application.

[0067] The UE in the RRC Connected state can make a call through the RRC connection established with the LTE base station, and the RRC connection can be the above-mentioned first RRC connection.

[0068] S13. During the call, the LTE base station sends a Paging message to the UE in the RRC Connected state. The pagingRecordList field of the Paging message carries the UE identifier. For example, in this embodiment, the pagingRecordList field carries the s-TMSI, and the s-TMSI=ABCDEF, so as to page the UE whose s-TMSI is ABCDEF through the Paging message. The s-TMSI carried in the pagingRecordList field can be the above-mentioned first temporary identifier.

[0069] S14. After the UE in the RRC Connected state determines that the s-TMSI in the Paging message matches the s-TMSI pre-allocated to the UE, the UE performs local release, and the UE switches from the RRC Connected state to the RRC Idle state. Because the UE is in the RRC Connected state, after receiving the Paging message and determining that the s-TMSI in the Paging message matches the s-TMSI pre-allocated to the UE, the UE may think that the Paging message paging itself is received because the state of itself and the network-side device is not synchronized. Therefore, after receiving the Paging message paging itself, the UE can perform local release, so that the UE switches from the RRC Connected state to the RRC Idle state. Then the UE starts to re-establish the RRC connection to synchronize the state with the network-side device, but when the UE performs local release, the UE is in the process of making a call, and the local release will cause the call to be silent. Among them, local release can be the release of the RRC resources corresponding to the RRC connection being used to make the call.

[0070] S15. The UE in the RRC Idle state attempts to send a Tracking Area Update (TAU) request (TAU request) message to the LTE base station to trigger the re-establishment of the RRC connection. The modem processor (Modem) of the UE in the RRC Idle state generates a TAU request message in the Non-Access Stratum (NAS) layer, and the TAU request message is sent from the NAS layer to the RRC layer of the Modem. After receiving the TAU request message, the RRC layer sends an RRC connection request to the LTE base station to re-establish the RRC connection.

[0071] S16. The UE in the RRC Idle state sends an RRC connection request (RRCConnectionRequest) to the LTE base station.

[0072] S17. The LTE base station sends an RRC connection establishment (RRCConnectionSetup) message to the UE.

[0073] S18. The UE sends an RRC connection setup complete (RRCConnectionSetupComplete) message to the LTE base station, and the UE completes the RRC connection setup again. When the UE sends an RRCConnectionSetupComplete message to the LTE base station, the RRCConnectionSetupComplete message may carry a TAU request message to complete the sending of the TAU request message, or after the UE sends an RRCConnectionSetupComplete message to the LTE base station, the UE sends a TAUrequest message to the LTE base station. Figure 6 In the RRCConnectionSetupComplete message, the TAU request message can be carried.

[0074] One thing that needs to be explained is that from the perspective of the LTE base station, when the UE sends an RRC connection request to the LTE base station, the UE enters the RRC Connected state, but from the perspective of the core network device, when the UE sends an RRC connection request to the LTE base station, the UE is in the RRC Idle state. After the UE sends an RRC establishment completion message to the LTE base station, from the perspective of the LTE base station and the core network device, the UE enters the RRC Connected state.

[0075] S19. The LTE base station sends an RRC connection reconfiguration (RRCConnectionReconfiguration) message to the UE in the RRC Connected state. The message may carry the DRB allocated to the UE, such as the DRB allocated to the UE carried in the drb-ToAddModList field of the message. In this embodiment, the drb-ToAddModList field carries DRB#1 and DRB#2, that is, two DRBs are allocated to the UE in the RRC Connected state, DRB#1 represents the data service bearer, and DRB#2 represents the IMS default bearer.

[0076] S110. The UE in the RRC Connected state sends an RRC connection reconfiguration complete (RRCConnectionReconfigurationComplete) message to the LTE base station.

[0077] S111. The LTE base station sends a tracking area update accept (TAU accept) message to the UE in the RRC Connected state.

[0078] S112. The LTE base station sends a call end (IMS_SIP_BYE) request message to the UE in the RRC Connected state. The IMS_SIP_BYE message carries a call end reason value of 503. The reason for generating the 503 reason value is insufficient bearer resources, which is mainly caused by the fact that no IMS dedicated bearer is allocated for carrying voice services.

[0079] S113. The UE in the RRC Connected state sends a call end (IMS_SIP_BYE / OK) message to the LTE base station to end the call.

[0080] S114. The interface of the UE in the RRC Connected state displays that the call is ended, and the user senses that the call is dropped.

[0081] Figure 7 The figure shows a process in which a UE in an RRC Connected state is located in an NR network and makes a call through an NR base station. During the call, a Paging message for paging the UE is received. In the process, the NR base station in different steps may be the same base station, and the following steps may be included:

[0082] S21. The UE in the RRC Connected state obtains the pre-allocated s-TMSI and DRB, such as s-TMSI = ABCDEF. The NR base station allocates a DRB for the UE, denoted as DRB#1. DRB#1 represents the IMS default bearer.

[0083] S22. The UE in the RRC Connected state establishes a call through the NR base station. During the call establishment process, DRB#2 is allocated to the UE in the RRC Connected state through the NR base station, where DRB#2 represents the IMS dedicated bearer, and DRB#1 and DRB#2 are only examples. The UE in the RRC Connected state can make a call through the RRC connection established with the NR base station, and the RRC connection can be the above-mentioned first RRC connection.

[0084] S23. When the UE in the RRC Connected state is making the call, the NR base station sends a Paging message to the UE in the RRC Connected state. The pagingRecordList field of the Paging message carries the UE identifier, such as s-TMSI=ABCDEF. The s-TMSI can be the above-mentioned first temporary identifier.

[0085] S24. After determining that the s-TMSI in the Paging message matches the s-TMSI pre-allocated to the UE, the UE in the RRC Connected state performs local release, and the UE switches from the RRC Connected state to the RRC Idle state.

[0086] S25. The UE in the RRC Idle state attempts to send a registration request to the NR base station, carrying mod reg updating in the reg_type field of the Registration request to trigger the re-establishment of the RRC connection.

[0087] S26. The UE in the RRC Idle state sends an RRC connection request (RRC Setup Req) to the NR base station.

[0088] S27. NR base station UE sends an RRC connection establishment (RRC Setup) message.

[0089] S28. The UE sends an RRC Setup Complete message to the NR base station. At this point, the UE re-completes the RRC setup and enters the RRC Connected state. The RRC Setup Complete message may carry a Registration request, or the UE sends a Registration request to the NR base station after sending the RRC Setup Complete message.

[0090] S29. The NR base station sends an RRC connection reconfiguration (RRCReconfiguration) message to the UE in the RRC Connected state. The message may carry the DRB allocated to the UE in the RRC Connected state, such as carrying the DRB allocated to the UE in the drb-ToAddModList field of the message. In this embodiment, the drb-ToAddModList field carries DRB#1, that is, a DRB is allocated to the UE in the RRC Connected state, and DRB#1 represents the IMS default bearer.

[0091] S210. The UE in the RRC Connected state sends an RRC connection reconfiguration complete (RRCConfiguration Complete) message to the NR base station.

[0092] S211. The NR base station sends a Registration accept message to the UE in the RRC Connected state. In some examples, step S25 is an example of triggering the re - establishment of an RRC connection, and this step is an optional step. Correspondingly, step S211 is also optional.

[0093] S212. The NR base station sends a SERVICE_UNAVAILABLE message to the UE in the RRC Connected state. The message carries text (or warning) = "Media Bearer Lost" to indicate the loss of media bearer resources, mainly because no IMS dedicated bearer for carrying voice services is allocated.

[0094] S213. The UE in the RRC Connected state sends an IMS_SIP_ACK message to the NR base station to end the call.

[0095] S214. The interface of the UE in the RRC Connected state shows that the call has ended, and at this time, the user perceives that the call has dropped.

[0096] The processing of the UE in the RRC Connected state after receiving the Paging message for paging this UE is described from a code perspective. As Figure 8 shown, after receiving the Paging message sent by the LTE base station for paging this UE, the re - establishment of the RRC connection, resource re - configuration, and feedback of IMS signaling, etc. In Figure 8 MS is the UE, BS is the base station, BS>>>MS means the base station sends a message to the UE, and BS<<<MS means the UE sends a message to the base station; Fig. 9 shows that the reason carried in the RRC connection request for re - establishing the RRC connection can be mt - Access (mobile terminated access). Mt - Access is an example of the reason for re - establishing the RRC connection. The reasons for re - establishing the RRC connection can also be mo signaling (mobile originated signaling), mo - VoiceCall (mobile originated voice call), mo - Data (mobile originated data), etc.; Fig.10 shows that the reason for the call drop is due to Insufficient Bearer Resource.

[0097] In summary, in a call scenario, a UE in the RRC Connected state, whether in an NR network or an LTE network, will be locally released after receiving a Paging message for paging the UE, and then reestablish the RRC connection. However, during the process of reestablishing the RRC connection, the network-side device did not reconfigure the IMS dedicated bearer for the UE to carry voice services, and the UE's call was dropped by the network-side device with a 503 reason value BYE\Cancel, resulting in a call drop, thereby reducing the call success rate and user experience.

[0098] Some embodiments of the present application provide a paging message processing method, for a UE in an RRCConnected state in a call scenario, after receiving a Paging message for paging the UE, the UE does not respond (prohibit response / reject response) to the Paging. Because the UE does not respond to the Paging message after receiving the Paging message for paging itself, the UE can reduce the execution of local release and re-establishment of RRC connection and other operations, reduce the call drops caused by these operations, and thus improve the call success rate and user experience.

[0099] The following takes an example of a UE in an RRC Connected state making a call through an LTE base station to illustrate the paging message processing method provided in an embodiment of the present application. In the paging message processing method, the LTE base station in different steps may be the same base station. Fig.11 A signaling diagram of a paging message processing method provided in an embodiment of the present application is shown, which may include the following steps:

[0100] S31 to S32 are the same as steps S11 to S12, and will not be repeated here.

[0101] S33. The LTE base station sends a Paging message to the UE in the RRC Connected state. The pagingRecordList field of the Paging message carries the UE identifier, such as the pagingRecordList field carries the s-TMSI, and s-TMSI=ABCDEF, so as to page the UE whose s-TMSI is ABCDEF through the Paging message. For the convenience of description, the Paging message that appears below may refer to the Paging message in step S33, that is, the Paging message used to page the UE whose s-TMSI is ABCDEF.

[0102] S34. After determining that the s-TMSI in the Paging message matches the s-TMSI pre-assigned to the UE, the UE in the RRC Connected state ignores the Paging message and continues the call through the LTE base station. Ignoring the Paging message here means not responding (forbidding response / rejecting response) to the Paging message.

[0103] Among them, the UE in the RRC Connected state does not respond to the Paging message, which may mean that the UE does not perform local release after receiving the Paging message, does not enter the RRC Idle state, does not send an RRC connection establishment request to the base station, and does not send a request to trigger re-establishment of the RRC connection to the base station.

[0104] For a UE in the RRC Connected state, if there is an incoming call, the network side equipment (core network equipment and base station) does not need to page the UE in the RRC Connected state through a Paging message, and can directly send an invite message to the UE in the RRC Connected state. However, the applicant has found through research that when the UE is in the RRC Connected state and is making a call through an LTE base station, the network side equipment will send a Paging message to the UE in the RRC Connected state to page the UE. After receiving the Paging message, the UE in the RRC Connected state believes that the state between itself and the network side equipment may be out of sync. The UE in the RRC Connected state performs local release and re-establishes the RRC connection, etc. The network side equipment will not restore the IMS dedicated bearer for the voice service and send a bye / cancel message, resulting in a dropped call before the Paging message is received.

[0105] However, when the UE is in the RRC Connected state and is making a call through the LTE base station, before receiving the Paging message for paging the UE, both the uplink and downlink calls are normal. When the UE is in the RRC Connected state and is making a call, it is not necessary for the UE to perform local release and re-establish RRC connection processes after receiving the Paging message. Therefore, in some embodiments provided in the present application, when the UE is in the RRC Connected state and is making a call, if the UE receives a Paging message carrying the UE's s-TMSI to paging the UE, the UE does not respond to the Paging message, so that the UE can continue the current call, thereby preventing the current call from being dropped due to responding to the Paging message, thereby improving the call success rate and user experience.

[0106] In addition, some embodiments provided in the present application may add a preset condition, and do not respond to the Paging message when the preset condition is met.

[0107] In an example, during a call, a UE in an RRC Connected state detects and records the voice data reception and transmission within a first preset time period. If a Paging message (i.e., a Paging message of non-ETWS primary notification and / or ETWSsecondary notification / CMAS notification / SI system information) is received, and the voice data reception and transmission within a first preset time period (e.g., X seconds, X is greater than or equal to 1) before receiving the Paging message is normal, the UE may not respond to the Paging message.

[0108] As an optional operation, after the UE does not respond to the Paging message, the UE can detect and record the voice data reception and transmission situation within a second preset time period (such as t1 seconds, t1 is greater than or equal to 1). If the voice data reception and transmission are normal within the second preset time period, it means that the non-response to the Paging message is valid, and the UE can maintain the normal call without responding to the Paging message. If the voice data reception and transmission are abnormal within the second preset time period, it is considered that the non-response to the Paging message is invalid. When the UE is in the RRC Connected state and receives the Paging message sent by the same LTE base station again, the UE can respond to the Paging message; wherein, the time interval between the non-response to the Paging message and the re-receiving of the Paging message can be less than the preset time, and the preset time can be N seconds, N is greater than or equal to 1. That is, the time interval between the non-response to the Paging message and the re-receiving of the Paging message is short, and the possibility of changes in the voice data reception and transmission situation within a short time is small. Therefore, the UE may receive the Paging message again when the voice data reception and transmission are abnormal. Then, the UE can respond to the Paging message, re-establish the RRC connection with the LTE base station, and make the data reception and transmission normal by re-establishing the RRC connection. Fig.12 As shown, another signaling diagram of the paging message processing method provided in an embodiment of the present application is shown, which may include the following steps:

[0109] S41 to S42 are the same as steps S11 to S12, and will not be repeated here.

[0110] S43, the UE in the RRC Connected state detects and records the sending and receiving status of DRB#3 every second. DRB#3 is an IMS dedicated bearer, which is used to carry voice services. The sending and receiving status of DRB#3 is recorded to record the sending and receiving status of voice data on the IMS dedicated bearer.

[0111] S44. The LTE base station sends a Paging message to the UE in the RRC Connected state.

[0112] S45. The UE in the RRC Connected state determines that the s-TMSI in the Paging message matches the s-TMSI pre-allocated to the UE.

[0113] S46. The UE in the RRC Connected state determines whether the transceiver status of DRB#3 is normal within the first preset time period (such as X seconds) before receiving the Paging message. If the transceiver status of DRB#3 is normal, execute step S47; if the transceiver status of DRB#3 is abnormal, execute step S413. The normal transceiver status of DRB#3 may mean that the UE in the RRC Connected state sends voice data to the call partner through the LTE base station, and the UE in the RRC Connected state can receive the voice data of the call partner sent by the LTE base station. The abnormal transceiver status of DRB#3 may mean that the UE in the RRC Connected state cannot send voice data to the call partner through the LTE base station, and / or the UE in the RRC Connected state does not receive the voice data of the call partner sent by the LTE base station.

[0114] S47. The UE in the RRC Connected state does not respond to the Paging message and continues the call through the LTE base station.

[0115] S48. The UE in the RRC Connected state determines whether the sending and receiving of DRB#3 is abnormal within the second preset time period (such as t1 seconds) after not responding to the Paging message. If yes, execute step S49, if not, execute step S410. The starting point of the second preset time period after not responding to the Paging message may be when the Paging message is received, when the s-TMSI match is determined, or when it is determined not to respond to the Paging message, etc. The end point of the second preset time period after not responding to the Paging message may be a time point after not responding to the Paging message.

[0116] S49. The UE in the RRC Connected state determines that ignoring the Paging message is invalid. The UE receives the Paging message sent by the LTE base station for paging the UE again, and can decide whether to not respond to the Paging message according to the time interval for receiving the Paging message again. Among them, receiving the Paging message sent by the LTE for paging the UE again can be: the UE is in the RRC Connected state and receives the Paging message sent by the LTE base station for paging the UE again during the process of continuing the call through the LTE base station, or the UE is in the RRC Connected state and receives the Paging message sent by the LTE base station for paging the UE during the next call through the LTE base station.

[0117] S410: The UE in the RRC Connected state determines that ignoring the Paging message is effective. The UE in the RRC Connected state may continue not to respond to the Paging message when receiving the Paging message sent by the LTE base station for paging the UE again.

[0118] S411. The UE in the RRC Connected state performs local release, and the UE switches from the RRC Connected state to the RRC Idle state.

[0119] S412, the UE in the RRC Idle state re-establishes an RRC connection (RRCConnection establishment) with the LTE base station, and the process can refer to steps S15 to S18.

[0120] S413 to S417: The same as steps S18 to S112, and will not be repeated here.

[0121] Therefore, during a call, if the voice data transmission and reception in the first preset time period before receiving the Paging message is normal for the UE in the RRC Connected state, the UE may not respond to the Paging message, so as to continue the current call under the premise that the UE can normally transmit and receive voice data, avoid the current call drop caused by responding to the Paging message, and improve the success rate of the call. The UE can detect and record the voice data transmission and reception in the second preset time period. If the voice data transmission and reception in the second preset time period is normal, it means that the UE can maintain the normal call without responding to the Paging message, and the UE's non-response to the Paging message is effective (which can be understood as bringing benefits to the current call); if the voice data transmission and reception in the second preset time period is abnormal, it is considered that the non-response to the Paging message is invalid (which can be understood as not bringing benefits to the current call). Therefore, the UE can decide whether to respond to the Paging message when receiving the Paging message sent by the LTE base station for paging the UE again according to whether the non-response to the Paging message brings benefits to the current call. Optionally, the UE can decide whether not to respond to the Paging message based on the time interval of receiving the Paging message again. If the time interval between not responding to the Paging message and receiving the Paging message again is short, the possibility of the capability of the LTE base station changing in a short period of time is small. The accuracy is improved by deciding whether to respond to the Paging message based on the capability of the LTE base station in a short period of time.

[0122] Fig.13 Another signaling diagram of the paging message processing method provided in the embodiment of the present application is shown. Fig.13 The paging message processing method shown takes the call success rate being greater than a threshold as a preset condition for not responding to the Paging message, and may include the following steps:

[0123] S51 to S53 are the same as steps S11 to S13, and will not be repeated here.

[0124] S54: The UE in the RRC Connected state determines that the s-TMSI in the Paging message matches the s-TMSI pre-allocated to the UE.

[0125] S55. The UE in the RRC Connected state determines whether the value of the call success rate is greater than a threshold value. If it is greater than the threshold value, step S56 is executed. If it is less than or equal to the threshold value, step S510 is executed. The call success rate is the proportion or number of times that the UE in the RRC Connected state can successfully complete the call after the UE does not respond to the Paging message for paging the UE during the call process. The value of the threshold value is not limited in this embodiment.

[0126] The UE may set an initial value for the call success rate in advance. When the UE in the RRC Connected state receives the Paging message for the first time, the UE may use the initial value of the call success rate to determine whether to not respond to the Paging message, and monitor whether the call is disconnected due to a network abnormality when the UE does not respond to the Paging message, so as to update the call success rate according to whether the call is disconnected due to a network abnormality. Alternatively, the UE in the RRC Connected state may directly not respond to the Paging message after receiving the Paging message (i.e., skip step S55). After calculating the call success rate, if the UE receives the Paging message sent by the LTE base station for paging the UE, step S55 is executed to decide whether to not respond to the Paging message based on the call success rate.

[0127] S56. The UE in the RRC Connected state does not respond to the Paging message and continues the call through the LTE base station.

[0128] S57. The UE in the RRC Connected state determines whether the call is disconnected due to a network abnormality after not responding to the Paging message. If yes, execute step S58; if not, execute step S59. In some examples, the UE can determine whether the call is disconnected due to a network abnormality within a third preset time period (such as t seconds) after not responding to the Paging message. Among them, the starting point of the third preset time period after not responding to the Paging message can be when the Paging message is received, when it is determined that the s-TMSI matches, or when it is determined not to respond to the Paging message, etc. The end point of the third preset time period after not responding to the Paging message can be a time point after not responding to the Paging message.

[0129] S58. The UE in the RRC Connected state reduces the value of the call success rate, such as the value of the call success rate minus a preset value.

[0130] S59. The UE in the RRC Connected state increases the value of the call success rate, such as increasing the value of the call success rate by a preset value.

[0131] S510 to S516: are the same as steps S411 to S417, and are not repeated here.

[0132] In this embodiment, the value of the call success rate is greater than the threshold value, indicating that when the UE in the RRC Connected state does not respond to the Paging message, the probability of the UE successfully completing the call is relatively high. Therefore, when the UE is in the RRC Connected state and is making a call through the LTE base station, if the value of the call success rate is greater than the threshold value when the UE receives the Paging message sent by the LTE base station for paging the UE, the UE can successfully complete the call without responding to the Paging message, thereby improving the call success rate by not responding to the Paging message. Optionally, after not responding to the Paging message, the UE can continue to monitor the call status of the call to update the call success rate based on whether the call is hung up due to network abnormalities, so that the call success rate can be updated in real time according to the call status, ensuring the accuracy of the call success rate, and thus controlling the UE's processing of the Paging message based on a more accurate call success rate.

[0133] Fig.14 Another signaling diagram of the paging message processing method provided in the embodiment of the present application is shown. Fig.14 The paging processing method shown is to combine the call success rate and the voice data receiving and sending situation to control whether to respond to the Paging message, which may include the following steps:

[0134] S61 to S65 are the same as steps S41 to S45 and will not be described again here.

[0135] S66. The UE in the RRC Connected state determines whether the sending and receiving of DRB#3 is normal and whether the value of the call success rate is greater than the threshold value within the first preset time period (such as X seconds) before receiving the Paging message. If the sending and receiving of DRB#3 is normal and the value of the call success rate is greater than the threshold value, execute step S67; if the sending and receiving of DRB#3 is abnormal and / or the value of the call success rate is not greater than the threshold value, execute step S613.

[0136] S67: The UE in the RRC Connected state does not respond to the Paging message and continues the call through the LTE base station.

[0137] S68, the UE in the RRC Connected state starts the timer. The timer can be started after receiving the Paging message, after determining that the s-TMSI matches, or after determining in step S66 that the sending and receiving of DRB#3 is normal and the value of the call success rate is greater than the threshold, etc. This embodiment does not limit the timing of starting the timer T1.

[0138] S69. The UE in the RRC Connected state detects and records the sending and receiving status of DRB#3 every second after the timer is started.

[0139] S610. The UE in the RRC Connected state determines whether the sending and receiving conditions of DRB#3 per second are abnormal after not responding to the Paging message and whether the call is disconnected due to a network abnormality. If the sending and receiving conditions are normal and the call is not disconnected due to a network abnormality, execute step S611; if the sending and receiving conditions are abnormal and / or the call is disconnected due to a network abnormality, execute step S612.

[0140] S611. The UE in the RRC Connected state determines whether the timer has timed out. If not, the process returns to step S69. If not, the process proceeds to step S612. Whether the timer has timed out may be whether the timer has timed out longer than a preset duration. If it has timed out longer than a preset duration, the timer has timed out. Otherwise, the timer has not timed out.

[0141] S612. The UE in the RRC Connected state counts the value of the call success rate. If the sending and receiving situation is abnormal and / or the call is disconnected due to a network abnormality, the UE may reduce the value of the call success rate; if the sending and receiving situation is normal and the call is not disconnected due to a network abnormality, the UE may increase the value of the call success rate.

[0142] S613 to S619: are the same as steps S411 to S417, and will not be repeated here.

[0143] In this embodiment, during a call of a UE in the RRC Connected state, if the sending and receiving conditions in the first preset time period before receiving the Paging message are normal and the call success rate is greater than the threshold, it means that the UE can successfully complete the call without responding to the Paging message, thereby controlling the call by combining the call success rate and the sending and receiving conditions of DRB#3 to improve the call success rate. Optionally, after not responding to the Paging message, the UE can continue to monitor the call status and the sending and receiving conditions of DRB#3 to update the call success rate according to whether the call is hung up due to network abnormalities and whether the sending and receiving conditions of DRB#3 are normal, so that the call success rate can be updated in real time according to the call status, ensuring the accuracy of the call success rate, and thus controlling the UE's processing of the Paging message according to a more accurate call success rate.

[0144] One point that needs to be explained here is that during a call, a UE in the RRC Connected state receives a Paging message sent by an LTE base station. The Paging message includes at least one of the systemInfoModification field, the etws-indication field, and the cmas-Indication field. The systemInfoModification field carries the changed system information, the etws-indication field carries the etws notification, and the cmas-Indication field carries the cmas notification. The Paging message is used to notify the UE that the system information has changed, receive at least one of the etws notification and the cmas notification; then the UE responds to the Paging message. The UE responding to the Paging message will cause the call conducted through the RRC connection to be affected. The response to the Paging message includes at least one of the following: the UE releases the RRC resources corresponding to the first RRC connection, the UE switches from the RRC Connected state to the RRC Idle state, the UE sends a request to the LTE base station to trigger the re-establishment of the RRC connection, or the UE sends an RRC connection request to the LTE base station. The first RRC connection can be an RRC connection established between the UE and the LTE base station for the call.

[0145] In some embodiments, the terminal may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a notebook computer, an ultra-mobile personal computer (UMPC), a handheld computer, a netbook, a personal digital assistant (PDA), a wearable electronic device, a smart watch, etc. The specific form of the terminal is not particularly limited in the embodiments of the present application.

[0146] A hardware structure of a terminal such as Fig.15 As shown, it may include: a processor, an external memory interface, an internal memory, a Universal Serial Bus (USB) interface, a charging management module, a power management module, a battery, an antenna 1, an antenna 2, a mobile communication module, a wireless communication module, a sensor module, a button, a motor, an indicator, a camera, a display screen, and a SIM card slot, etc. The audio module may include a speaker, a receiver, a microphone, an earphone interface, etc., and the sensor module may include a pressure sensor, a gyroscope 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, etc.

[0147] It is to be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the terminal. In other embodiments, the terminal may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0148] The processor may include one or more processing units, for example, the processor may include an application processor (AP), a modem (also called a baseband processor), a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. The processor is the nerve center and command center of the terminal. The controller may generate an operation control signal according to the instruction opcode and timing signal to complete the control of fetching and executing instructions.

[0149] The wireless communication function of the terminal can be implemented through antenna 1, antenna 2, mobile communication module, wireless communication module, and Modem, etc. In some embodiments, the antenna 1 of the terminal is coupled with the mobile communication module, and the antenna 2 is coupled with the wireless communication module, so that the terminal can communicate with the network side device and other terminals through wireless communication technology.

[0150] In addition, operating systems are running on the above components, such as the iOS operating system developed by Apple, the Android open source operating system developed by Google, and the Windows operating system developed by Microsoft.

[0151] The operating system of the terminal can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to illustrate the hardware and software structure of the terminal. It should be noted that although the embodiment of the present application is illustrated by taking the Android system as an example, its basic principle is also applicable to terminals based on operating systems such as iOS or Windows.

[0152] Fig.16 It is a software structure diagram of the terminal. The software structure adopts a layered architecture, which divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. Taking the Android system, the Android system running on the AP as an example, in some embodiments, the Android system is divided into five layers, from top to bottom, namely, the application layer, the application framework layer (Framework), the Android runtime (Android runtime) and the system library, the hardware abstraction layer (HAL) and the system kernel layer (Kernel).

[0153] Among them, the application layer may include a series of application packages. Application packages may include camera, gallery, calendar, call, map, WLAN, Bluetooth, music, video, short message and other APPs. The application layer may also include system UI (system UI). System UI is used to display the terminal interface, such as displaying the signal icon corresponding to the SIM card, displaying the call interface, etc. The application framework layer provides an application programming interface (Application Programming Interface, API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions. For example, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc. The phone manager is used to provide call functions for the terminal, such as management of call status (including connecting, hanging up, etc.). The phone manager is in Fig.14The application framework layer may also include a Radio Interface Layer (RIL), and a modem processor (Modem) may exchange information with the telephony through the RIL.

[0154] The modem can include NAS layer, RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control Layer (MAC) layer and Physical (PHY) layer. The RRC layer can decide whether to respond to the Paging message. The modem can interact with the base station through the antenna.

[0155] In addition, some embodiments of the present application provide a terminal, which includes: one or more processors and a memory; the memory is used to store computer program code, and the computer program code includes computer instructions. When the one or more processors execute the computer instructions, the terminal executes the above-mentioned paging message processing method.

[0156] Some embodiments of the present application provide a chip system, which is applied to a terminal. The chip system includes at least one processor and an interface, and the interface is used to receive instructions and transmit them to at least one processor; at least one processor runs the instructions so that the terminal executes the above-mentioned paging message processing method. Among them, the chip system can be a modem, or a system on chip (System on Chip, Soc) including a modem, and the above-mentioned paging message processing method can be implemented by a modem.

Claims

1. A paging message processing method, characterized in that: The method comprises: The terminal in the radio resource control RRC idle state establishes a first RRC connection with the network side device; After the terminal establishes the first RRC connection with the network side device, it enters the RRC connection Connected state; The terminal in the RRC Connected state conducts a call through the first RRC connection; During the call, the terminal receives a first paging message sent by the network side device, the first paging message includes a paging record list pagingRecordList field, the pagingRecordList field carries a first temporary identifier of the terminal, and the first paging message pages the terminal through the first temporary identifier of the terminal; The terminal does not respond to the first Paging message and continues the call through the first RRC connection.

2. The method according to claim 1, characterized in that The method further comprises: Before the terminal establishes the first RRC connection with the network side device, the terminal in the RRC Idle state receives a second paging message sent by the network side device, the second Paging message includes a paging record list pagingRecordList field, the pagingRecordList field carries the second temporary identifier of the terminal, and the second Paging message pages the terminal through the second temporary identifier of the terminal; The terminal responds to the second Paging message.

3. The method according to claim 2, characterized in that The terminal responding to the second Paging message includes: the terminal sending an RRC connection request to the network side device to establish the first RRC connection.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: During the call, the terminal receives a third paging message sent by the network side device, the third paging message includes at least one of a system information change systemInfoModification field, an earthquake and tsunami early warning system notification indication etws-indication field, and a public warning system notification indication cmas-Indication field, the systemInfoModification field carries the changed system information, the etws-indication field carries the earthquake and tsunami early warning system etws notification, and the cmas-Indication field carries the public warning system cmas notification, and the third paging message is used to notify the terminal that the system information has changed, receive at least one of the etws notification and the cmas notification; The terminal responds to the third Paging message.

5. The method according to claim 4, characterized in that The terminal responds to the third Paging message, causing the call conducted through the first RRC connection to be affected.

6. The method according to any one of claims 1 to 5, characterized in that The terminal not responding to the first Paging message includes: The terminal does not release the RRC resources corresponding to the first RRC connection, does not switch from the RRC Connected state to the RRC Idle state, does not send a request to trigger re-establishment of the RRC connection to the network side device, and does not send an RRC connection request to the network side device.

7. The method according to claim 4 or 5, characterized in that: The terminal responds to the third Paging message by including at least one of the following: The terminal releases the RRC resources corresponding to the first RRC connection, the terminal switches from the RRC Connected state to the RRC Idle state, the terminal sends a request to the network side device to trigger re-establishment of the RRC connection, or the terminal sends an RRC connection request to the network side device.

8. The method according to any one of claims 1 to 7, characterized in that The terminal not responding to the first Paging message includes: When the call success rate of the terminal is greater than a threshold value, and / or the voice data reception and transmission on the Internet Protocol Multimedia Subsystem dedicated bearer is normal within a first preset time period before receiving the first Paging message, the terminal does not respond to the first Paging message; the call success rate of the terminal is used to indicate the probability that the call of the terminal is not automatically hung up after the terminal receives the first Paging message sent by the network side device under a first scenario within a historical time period, and the terminal does not respond to the first Paging message, wherein the first scenario is that the terminal is in the RRC Connected state and is in the process of making a call through the network side device.

9. The method according to any one of claims 1 to 8, characterized in that After the terminal does not respond to the first Paging message, the method further includes: Detecting whether the voice data transmission and reception on the dedicated bearer of the Internet Protocol Multimedia Subsystem is normal after not responding to the first Paging message, and / or whether the call continued through the network side device after not responding to the first Paging message is automatically hung up due to network abnormality; If the voice data transmission and reception is normal, and / or the call is not automatically disconnected due to a network abnormality, after the terminal receives the first Paging message sent by the network side device again, the terminal does not respond to the first Paging message received again; If the voice data receiving and sending situation is abnormal, and / or the call is automatically disconnected due to network abnormality, after the terminal receives the first Paging message sent by the network side device again, the terminal responds to the first Paging message received again; Among them, the first Paging message received again is the first Paging message sent again by the network side device when the terminal is in the RRC Connected state and continues the call through the network side device, or the first Paging message sent by the network side device when the terminal is in the RRC Connected state and makes the next call through the network side device.

10. The method according to claim 9, characterized in that The detecting whether the voice data transmission and reception on the dedicated bearer of the Internet Protocol Multimedia Subsystem is normal after the first Paging message is not responded, and / or whether the call continued through the network side device is automatically hung up due to network abnormality after the first Paging message is not responded includes: Detect whether the voice data reception and transmission on the Internet Protocol Multimedia Subsystem dedicated bearer is normal within a second preset time period after not responding to the first Paging message, and / or whether the call continued through the network side device after not responding to the first Paging message is automatically hung up due to network abnormalities within a third preset time period.

11. The method according to claim 10, characterized in that The starting point of any time period of the second preset time period and the third preset time period is any time point when the terminal receives the first Paging message, when the terminal determines that the first temporary identifier carried in the first Paging message matches the first temporary identifier pre-assigned to the terminal, and when the terminal does not respond to the first Paging message, and the end point of any time period of the second preset time period and the third preset time period is a time point after not responding to the first Paging message.

12. The method according to any one of claims 1 to 11, characterized in that After the terminal does not respond to the first Paging message, the method further includes: If the voice data transmission and reception on the dedicated bearer of the Internet Protocol Multimedia Subsystem is normal after the terminal does not respond to the first Paging message, and / or the call continued through the network side device after the terminal does not respond to the first Paging message is not automatically hung up due to network abnormality, the terminal increases the value of the call success rate; If the voice data reception and transmission situation on the Internet Protocol Multimedia Subsystem dedicated bearer is abnormal after the terminal does not respond to the first Paging message, and / or the call continued through the network side device is automatically hung up due to network abnormality after the terminal does not respond to the first Paging message, the terminal reduces the value of the call success rate.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises at least one of the following: The first temporary identifier and / or the second temporary identifier is a temporary mobile user identifier for system architecture evolution; or, The network side device is a long term evolution base station, and the request to trigger re-establishment of the RRC connection is a tracking area update request message; or, The network side device is a new wireless / new air interface base station, and the request that triggers re-establishment of the RRC connection is a registration request.

14. A terminal, characterized in that: The terminal comprises: one or more processors and memory; The memory is used to store computer program codes, where the computer program codes include computer instructions. When the one or more processors execute the computer instructions, the terminal executes the paging message processing method according to any one of claims 1 to 13.

15. A chip system, applied to a terminal, characterized in that: The chip system includes at least one processor and an interface, wherein the interface is used to receive instructions and transmit them to the at least one processor; the at least one processor runs the instructions so that the terminal executes the paging message processing method as described in any one of claims 1 to 13.

Images