Paging message processing method and apparatus

Abstract

The present application provides a paging message processing method and apparatus. The method comprises: a terminal in a radio resource control (RRC) idle state establishes a first RRC connection with a network side device; after establishing the first RRC connection with the network side device, the terminal enters an RRC connected state; the terminal in the RRC connected state performs a call by means of the first RRC connection; during the call, the terminal receives a first paging message sent by the network side device, the first paging message comprising a pagingRecordList field, the pagingRecordList field carrying a first temporary identifier of the terminal, and the first paging message paging the terminal by means of the first temporary identifier of the terminal; the terminal does not respond to the first paging message, and continues performing the call by means of the first RRC connection. Therefore, after the terminal which is in the RRC connected state and which is performing a call receives the first paging message for paging said terminal, the current ongoing call can be continued, preventing the current call from being dropped due to responding to the first paging message, improving a calling success rate and user experience.

Description

Paging message processing method and device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on July 31, 2023, with application number 2023109603681 and invention name “Paging Message Processing Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

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

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

[0004] Summary of the Invention

[0005] This application provides a paging message processing method and apparatus to improve call success rate and user experience. Some embodiments of this application provide the following technical solutions:

[0006] In a 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; after the terminal establishes the first RRC connection with the network-side device, the terminal enters an RRC connection connected state; 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, thereby improving the call success rate and user experience. Because a terminal in the RRCConnected 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.

[0007] In a possible implementation, the method further 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.

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

[0009] In one 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 including at least one of a system information change (systemInfoModification) field, an earthquake and tsunami early warning system (ETWS) notification indication (ETWS) field, and a public warning system (CMAS) notification indication (CMAS) field, the systemInfoModification field carrying the changed system information, the etws-indication field carrying the earthquake and tsunami early warning system (ETWS) notification, and the cmas-indication field carrying the public warning system (CMAS) notification, the third paging message being used to notify the terminal of at least one of a system information change, receipt of an etws notification, and receipt of a CMAS notification; and the terminal responding to the third paging message. Thus, upon receiving the third paging message carrying a notification, such as at least one of a system information change notification, an etws notification, and a CMAS notification, a terminal in an RRC Connected state and engaged in a call will respond to the third paging message and promptly process the notification carried in the third paging message. In one possible case, the terminal's response to the third Paging message may affect the call conducted through the first RRC connection. For example, the ongoing call may be interrupted or automatically hung up, or there may be a short period of silence.

[0010] 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 may automatically hang up the ongoing call after responding to the third Paging message. The terminal interface will then display that the call is over, and the user will perceive that the call has been dropped.

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

[0012] In this embodiment, a terminal in the RRC Connected state and in a call, after receiving a Paging message for paging itself, may perform at least one of the following operations in response to the Paging message: releasing 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 the network device to trigger re-establishing an RRC connection, or sending an RRC connection request to the network device. These operations will cause the terminal's ongoing call to be automatically terminated. However, for a terminal in the RRC Connected state and in a call, both uplink and downlink calls are normal before receiving the first Paging message for paging itself. The terminal in the RRC Connected state does not need to perform these operations, namely, it does not need to perform the process of releasing radio control resources (i.e., local release) and re-establishing the RRC connection to synchronize state with the network device. After the terminal performs the local release, the terminal switches from the RRC Connected state to the RRC Idle state. The process of re-establishing the RRC connection includes sending a request to the network device to trigger re-establishing an RRC connection and sending an RRC connection request to the network device. Therefore, after receiving the first Paging message for paging itself, a terminal in the RRC Connected 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.

[0013] In one possible implementation, the terminal's response to the third Paging message includes 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 the re-establishment of the RRC connection, or the terminal sends an RRC connection request to the network side device.

[0014] In one 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, 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 in a first scenario within a 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.

[0015] The Internet Protocol Multimedia Subsystem dedicated bearer is an IMS dedicated bearer allocated by a network-side device to a terminal for carrying voice services. Voice data is sent and received over this IMS dedicated bearer, such as DRB#3 allocated by an LTE base station to a terminal as described below, or DRB#2 allocated by an NR base station to a terminal as described below. The first preset time period can be X seconds, where 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 terminal's call success rate is greater than a threshold, or that voice data transmission and reception on the Internet Protocol Multimedia Subsystem dedicated bearer is normal within the first preset time period before receiving the first paging message, or that the terminal's call success rate is greater than a threshold and that voice data transmission and reception on the Internet Protocol Multimedia Subsystem dedicated bearer is normal within the first preset time period before receiving the first paging message. In this way, a terminal in the RRC Connected state and in a call will not respond to the first paging message when it receives the first paging message paging itself and the preset condition is met. 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, the terminal can make the call as normally as possible, so 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.

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

[0017] In some examples, the terminal can set an initial value for the call success rate in advance. When the terminal in the RRC Connected state receives the first Paging message for paging itself for the first time, it uses the initial value of the call success rate to determine whether to respond to the first Paging message, and monitors whether the call is hung up due to a network abnormality when not responding to the first Paging message, so as to update the call success rate according to whether the call is hung up due to a network abnormality.

[0018] In some examples, a terminal in an RRC Connected state may not respond to the first Paging message directly after receiving the first Paging message for paging itself. After calculating the call success rate, if the terminal receives the first Paging message sent by the network-side device for paging the terminal, the value of the call success rate 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 terminal's call is not automatically hung up after the terminal receives the first Paging message sent by the network-side device in the first scenario during 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.

[0019] In one 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 disconnected due to a 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 transmission and reception is abnormal, and / or the call is automatically disconnected due to a 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 while the terminal is in an RRC Connected state and continues a call through the network-side device, or the first Paging message sent by the network-side device while the terminal is in an RRC Connected state and makes a next call through the network-side device.

[0020] The abnormal voice data transmission and reception situation may refer to the terminal in the RRC Connected state being unable to send voice data to the call partner through the network-side device, or the terminal in the RRC Connected state not receiving voice data from the call partner sent by the network-side device. After the terminal does not respond to the first Paging message, the terminal may monitor the voice data transmission and reception situation on the dedicated bearer of the Internet Protocol Multimedia Subsystem and / or the call continuing through the network-side device, and then decide whether to respond to the first Paging message based on the monitoring results 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 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. However, if the voice data transmission and reception situation is abnormal and / or the call is automatically disconnected due to a 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 that the call proceeds normally when responding to the first Paging message is not required, and to respond to the first Paging message in a timely manner when responding to the first Paging message is required.

[0021] In one possible implementation, 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 a network abnormality includes: detecting whether the voice data transmission and reception 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.

[0022] In some examples, the second preset time period may be t1 seconds as follows, where t1 may be greater than or equal to 1, and the third preset time period may be t seconds as follows, where t may be greater than or equal to 1. If voice data is sent and received normally within the second preset time period, and / or the call is not automatically disconnected due to a network abnormality within the third time period, it indicates that the terminal can maintain the normal progress of the call without responding to the first Paging message, and the terminal's non-response to the first Paging message is valid (which can be understood as bringing benefits to the current call); if voice data is sent and received abnormally within the second preset time period, and / or the call is automatically disconnected due to a 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 bringing no benefits to the current call). Therefore, the terminal may decide whether to respond to the first Paging message when receiving the first Paging message sent by the network side device to page 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.

[0023] In one 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.

[0024] In one possible implementation, after the terminal does not respond to the first Paging message, the method further 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 abnormality, 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 abnormality, the terminal reduces the value of the call success rate.

[0025] In some examples, the terminal may start a timer if it does not respond to the first Paging message; for example, the timer may be started after the terminal does not respond to the first Paging message. Furthermore, the terminal may set a preset duration for the timer. When determining whether voice data transmission and reception are normal and / or whether the call was automatically disconnected due to a network anomaly, the terminal may determine the processing of the call success rate based on whether the timer count exceeds the preset duration. For example, one method is to further determine whether the voice data reception and transmission situation is normal within a unit time (such as one second) and / or the call is not automatically hung up due to a network abnormality, and then further determine whether the timer timing is greater than a preset time. If the timer timing is greater than the preset time, 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 time, continue to determine whether the voice data reception and transmission situation is normal within a unit time (such as one second) 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 is abnormal within a unit time (such as one second) 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.

[0026] 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 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 to trigger re-establishment of the RRC connection is a registration request.

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

[0028] In a third aspect, the present application provides a chip system for use in a terminal. The chip system includes at least one processor and an interface, wherein the interface is configured to receive instructions and transmit them to the at least one processor; the at least one processor executes the instructions so that the terminal executes the aforementioned paging message processing method. The chip system may be a modem processor or a system on chip (SoC) including a modem, and the aforementioned paging message processing method may be implemented by a modem. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG1 is a signaling diagram of a UE processing a Paging message according to an embodiment of the present application;

[0030] FIG2 is another signaling diagram of UE processing of a Paging message according to an embodiment of the present application;

[0031] FIG3 is a signaling diagram of a Paging message processing according to an embodiment of the present application;

[0032] FIG4 is a message structure diagram of a Paging message provided in an embodiment of the present application;

[0033] FIG5 is another message structure diagram of a Paging message provided in an embodiment of the present application;

[0034] FIG6 is a signaling diagram of Paging message processing in an LTE network provided by an embodiment of the present application;

[0035] FIG7 is a signaling diagram of Paging message processing in an NR network provided by an embodiment of the present application;

[0036] FIG8 is a schematic diagram of a code for a UE to re-establish an RRC connection after receiving a Paging message according to an embodiment of the present application;

[0037] FIG9 is a schematic diagram of a code for an RRC connection request provided in an embodiment of the present application;

[0038] FIG10 is a schematic diagram of a code for abnormal call hang-up provided in an embodiment of the present application;

[0039] FIG11 is a signaling diagram of a paging message processing method provided in an embodiment of the present application;

[0040] FIG12 is another signaling diagram of a paging message processing method provided in an embodiment of the present application;

[0041] FIG13 is another signaling diagram of a paging message processing method according to an embodiment of the present application;

[0042] FIG14 is another signaling diagram of a paging message processing method according to an embodiment of the present application;

[0043] FIG15 is a hardware structure diagram of a terminal provided in an embodiment of the present application;

[0044] FIG16 is a software architecture diagram of the terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] 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 limiting of the present application. As used in the specification and appended claims of the present application, the singular expressions "one", "a kind of", "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 associated objects, indicating that three relationships may exist; for example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship.

[0046] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0047] 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" and "second" are only used for the purpose of distinguishing the description and cannot be understood as indicating or implying relative importance or order.

[0048] Figure 1 shows an example of a terminal (i.e., 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. In Figure 1, UE1 and UE2 are respectively in the RRC Connected state, and UE1 and UE2 are talking through the base station. During the call, at least one of UE1 and UE2 can receive a Paging message sent by the base station, such as UE1 receiving a Paging message sent by the base station in Figure 1. After receiving the Paging message, UE1 determines that the Paging message is a message for paging UE1, and UE1 responds to the Paging message. The response to the Paging message includes at least one of: releasing RRC resources, switching from the RRC Connected state to the RRC Idle state, sending a request to the base station to trigger the 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, a UE in the RRC Connected state and in the process of a call automatically hangs up the call after receiving a Paging message paging itself, thereby reducing the success rate of the call and affecting the user experience.

[0049] Some embodiments of the present application provide a paging message processing method, in which a UE in an RRC Connected state and in the process of a call may not respond to the Paging message after receiving a Paging message for paging itself, so as to improve the success rate of the call and the user experience. As shown in Figure 2, UE1 and UE2 in the RRC Connected state are talking through a 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. Responding 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 the base station to trigger the re-establishment of the RRC connection, and not sending an RRC connection request to the base station, and the interface of UE1 displays that the call is in progress, reducing the call termination caused by the Paging message, thereby improving the success rate of the call and the user experience.

[0050] For ease of understanding, the following briefly introduces several terms and related technologies involved in some embodiments of the present application.

[0051] 1. Radio Resource Control (RRC) State: RRC states include connected and idle states. The connected state (RRC Connected state, also known as RRC Connected state or connected state) refers to an established RRC connection between a terminal (i.e., UE) and an access network device (e.g., a base station). When the UE is in the RRC Connected state, both the connection between the UE and the access network device and the connection between the access network device and the core network device are established. Any data transmission can be accomplished directly over the established connections.

[0052] Idle state (RRC Idle state, also known as RRC Idle state or idle state): This 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, an RRC connection must be established between the UE and the access network device before data transmission can be carried out. A UE in the RRC Idle state has the following characteristics (taking the Long Term Evolution (LTE) network as an example):

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

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

[0055] (3) The UE has been assigned a unique identifier within its Tracking Area (TA).

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

[0057] (5) There is no Non-Access Stratum (NAS) layer signaling connection between the UE and the core network equipment.

[0058] 2. Paging is the process of searching for UE initiated by the network side. The trigger 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 no connection is established 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 a 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.

[0059] Among them, the paging process is shown in Figure 3. The MME sends a Paging message to the base station (such as 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 the Paging Control Channel (PCCH)) based on the TA identified by the TAC in the TAL message to page the UE. The Paging message includes a field indicating the paging source and the 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 identifier carried in the Paging message that triggers the UE to establish an RRC connection can be encapsulated in the paging record list (pagingRecordList) field. The UE identifier can be a System Architecture Evolved-Temporary Mobile Subscriber Identity (SAE-TMSI, System Architecture Evolved-Temporary Mobile Subscriber Identity, abbreviated as s-TMSI), and the s-TMSI can be the above-mentioned second temporary identifier. 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. 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.

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

[0061] Figure 4 shows the structure of the Paging message in LTE networks. The pagingRecordList field is used to record the UE being paged, the systemInfoModification field is used to indicate changes in system information, the etws-Indication field is used to indicate an ETWS primary notification and / or ETWSsecondary notification, and the cmas-Indication field is used to indicate a CMAS notification. Figure 5 shows the structure of the Paging message in New Radio (NR) networks. The pagingRecordList field is used to record the UE being paged.

[0062] As can be seen from the Paging messages shown in Figures 4 and 5 above, for a UE in the RRC Connected state on an LTE network, the UE can perceive notifications of system message changes by receiving Paging messages. For a UE in the RRC Connected state on an NR network, system message changes are not notified via Paging messages, 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 does 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. Therefore, the UE in the RRC Connected state will locally release (release the RRC connection) after receiving the Paging message, and then re-establish the RRC connection.

[0063] As an example, in a call scenario (such as the caller is ringing, the called party is ringing, the call is being established, or the call is in progress), the UE in the RRC Connected state, whether it is 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 likely not to reconfigure the IP Multimedia Subsystem (IMS) dedicated bearer for the UE to carry voice services (i.e., 5qi=1 / QCI=1), 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.

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

[0065] The following figures illustrate the process of a UE in the RRC Connected state receiving a Paging message for paging the UE in a call scenario. Referring to Figure 6, it illustrates the process of a UE in the RRC Connected state conducting a call via an LTE base station in an LTE network and receiving the Paging message during the call. In this process, the LTE base station in different steps may be the same base station, and the following steps may be included:

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

[0067] If there is data or signaling interaction between the UE and the core network within the preset time period when the UE enters 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 period when the UE is registered with the core network, the LTE base station will release the RRC connection between the UE and the core network, thereby placing the UE in the RRC Idle state. The preset time period can be pre-set in the LTE base station, and the value of the preset time period 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.

[0068] 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 services 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.

[0069] 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 first RRC connection mentioned above.

[0070] 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 s-TMSI = ABCDEF, so that the UE with the s-TMSI of ABCDEF is paged through the Paging message. The s-TMSI carried in the pagingRecordList field can be the above-mentioned first temporary identifier.

[0071] 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, it performs a 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, when the UE receives the Paging message and determines 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 its status is not synchronized with that of the network-side device. Therefore, when the UE receives the Paging message paging itself, the UE can perform a local release, so that the UE switches from the RRC Connected state to the RRC Idle state. The UE then starts to re-establish the RRC connection to synchronize the status with the network-side device. However, when the UE performs the local release, the UE is in the process of making a call, and the local release will cause the call to be silent. The local release can be the release of the RRC resources corresponding to the RRC connection being used to make the call.

[0072] S15. The UE in the RRC Idle state attempts to send a Tracking Area Update (TAU) request message to the LTE base station to trigger the re-establishment of the RRC connection. The modem of the UE in the RRC Idle state generates a TAU request message at the Non-Access Stratum (NAS) layer. 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.

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

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

[0075] S18. The UE sends an RRCConnectionSetupComplete message to the LTE base station, thereby re-establishing the RRC connection. When the UE sends the 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. Alternatively, after the UE sends the RRCConnectionSetupComplete message to the LTE base station, the UE sends a TAU request message to the LTE base station. In Figure 6, the RRCConnectionSetupComplete message may carry a TAU request message.

[0076] It should be noted 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. However, from the perspective of the core network equipment, when the UE sends the RRC Connection Request to the LTE base station, the UE is in the RRC Idle state. After the UE sends an RRC Setup Complete message to the LTE base station, the UE enters the RRC Connected state from the perspective of the LTE base station and the core network equipment.

[0077] S19. The LTE base station sends an RRC Connection Reconfiguration 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.

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

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

[0080] 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, mainly because no IMS dedicated bearer is allocated to carry voice services.

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

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

[0083] Figure 7 shows a process flow in which a UE in the RRC Connected state is in an NR network and is making a call through an NR base station. During the call, a Paging message for paging the UE is received. In this process, the NR base station in different steps may be the same base station, and the process may include the following steps:

[0084] S21. The UE in the RRC Connected state obtains the pre-allocated s-TMSI and DRB. For example, if s-TMSI = ABCDEF, the NR base station allocates a DRB for the UE, which is recorded as DRB#1. DRB#1 represents the IMS default bearer.

[0085] 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 an 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 first RRC connection mentioned above.

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

[0087] 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 a local release, and the UE switches from the RRC Connected state to the RRC Idle state.

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

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

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

[0091] 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 may send a Registration request to the NR base station after sending the RRC Setup Complete message.

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

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

[0094] 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 the RRC connection, and this step is an optional step. Correspondingly, step S211 is also optional.

[0095] 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 voice services is allocated.

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

[0097] S214. The interface of the UE in the RRC Connected state shows that the call ends, and at this time, the user perceives that the call drops.

[0098] The processing of the UE in the RRC Connected state after receiving the Paging message for paging the UE is described from a code perspective. As shown in Figure 8, after receiving the Paging message sent by the LTE base station for paging the UE, the RRC connection is re - established, resources are re - configured, and feedback of IMS signaling, etc. In Figure 8, MS is the UE, BS is the base station, BS>>>MS indicates that the base station sends a message to the UE, and BS<<<MS indicates that the UE sends a message to the base station; Figure 9 shows that the reason for re - establishing the RRC connection carried in the RRC connection request can be mt - Access (mobile terminated access), and 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 (signaling access), mo - VoiceCall (voice call access), mo - Data (data access), etc.; Figure 10 shows that the reason for the call drop is due to Insufficient Bearer Resource.

[0099] In summary, in a call scenario, a UE in the RRC Connected state, regardless of whether it is located on an NR or LTE network, will locally release after receiving a Paging message to paging the UE and then re-establish the RRC connection. However, during the RRC connection re-establishment process, the network device does not reconfigure the IMS dedicated bearer for voice services for the UE. The UE's call is then terminated by the network device with a cause value of 503, BYE\Cancel, resulting in a dropped call, which reduces the call success rate and user experience.

[0100] Some embodiments of the present application provide a paging message processing method for a UE in the RRC Connected state during a call. Upon receiving a paging message intended for paging the UE, the UE does not respond (forbids responding / rejects responding) to the paging message. Because the UE does not respond to the paging message intended for paging itself, it can reduce the number of operations such as local release and RRC connection reestablishment, thereby reducing call drops caused by these operations and improving call success rates and user experience.

[0101] The following uses an example of a UE in the RRC Connected state making a call through an LTE base station to illustrate the paging message processing method provided by the embodiment of the present application. In this paging message processing method, the LTE base station in different steps can be the same base station. Figure 11 shows a signaling diagram of the paging message processing method provided by the embodiment of the present application, which may include the following steps:

[0102] S31 to S32 are the same as steps S11 to S12 and are not described again here.

[0103] 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. For example, the pagingRecordList field carries the s-TMSI, and s-TMSI = ABCDEF. This Paging message is used to page the UE whose s-TMSI is ABCDEF. For ease 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.

[0104] S34. After determining that the s-TMSI in the Paging message matches the pre-assigned s-TMSI of 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 to (forbidding response / rejecting response to) the Paging message.

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

[0106] 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 (invite) message to the UE in the RRC Connected state. However, the applicant 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 call drop before receiving the Paging message.

[0107] 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 page the UE, the UE does not respond to the Paging message, so that the UE can continue the current call, prevent the current call from being dropped due to responding to the Paging message, and improve the call success rate and user experience.

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

[0109] In one 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 ETWS secondary 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.

[0110] As an optional operation, after the UE does not respond to the Paging message, the UE may detect and record the voice data transmission and reception status within a second preset time period (e.g., t1 seconds, where t1 is greater than or equal to 1). If the voice data transmission and reception are normal within the second preset time period, it is considered 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 transmission and reception are abnormal within the second preset time period, the non-response to the Paging message is considered invalid. When the UE is in the RRC Connected state and receives a Paging message sent by the same LTE base station again, the UE may respond to the Paging message. The time interval between the non-response to the Paging message and the subsequent receipt of the Paging message may be less than a preset time, which may be N seconds, where N is greater than or equal to 1. That is, the time interval between the non-response to the Paging message and the subsequent receipt of the Paging message is short, and the voice data transmission and reception status is less likely to change within a short period of time. Therefore, the UE may receive a Paging message again when the voice data transmission and reception is abnormal. In this case, the UE may respond to the Paging message and re-establish an RRC connection with the LTE base station. By re-establishing the RRC connection, data transmission and reception can be normal. As shown in FIG12 , 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:

[0111] S41 to S42 are the same as steps S11 to S12 and are not described again here.

[0112] S43. The UE in the RRC Connected state detects and records the transmission and reception of DRB#3 every second. DRB#3 is an IMS dedicated bearer used to carry voice services. By recording the transmission and reception of DRB#3, the voice data transmission and reception status on the IMS dedicated bearer is recorded.

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

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

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

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

[0117] 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 (e.g., t1 seconds) after not responding to the Paging message. If so, 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.

[0118] 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 based on the time interval for receiving the Paging message again. 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.

[0119] 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 it receives the Paging message sent by the LTE base station again for paging the UE.

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

[0121] S412: The UE in the RRC Idle state re-establishes an RRC connection (RRCConnection establishment) with the LTE base station. The process may refer to steps S15 to S18.

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

[0123] Thus, during a call, if the voice data transmission and reception of a UE in the RRC Connected state is normal within a first preset time period before receiving a Paging message, the UE may not respond to the Paging message, so as to continue the current call while the UE can normally transmit and receive voice data, thereby avoiding the current call drop caused by responding to the Paging message and improving the call success rate. The UE may detect and record the voice data transmission and reception within a second preset time period. If the voice data transmission and reception is normal within the second preset time period, 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 is abnormal within the second preset time period, 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 it receives a Paging message sent by the LTE base station for paging the UE again based on whether not responding 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 for 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.

[0124] FIG13 shows another signaling diagram of a paging message processing method provided in an embodiment of the present application. The paging message processing method shown in FIG13 uses a call success rate greater than a threshold as a preset condition for not responding to a Paging message, and may include the following steps:

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

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

[0127] S55. The UE in the RRC Connected state determines whether the call success rate is greater than a threshold. If so, step S56 is executed; if less than or equal to the threshold, step S510 is executed. The call success rate is the ratio or number of times that a UE in the RRC Connected state can successfully complete a call without responding to a paging message for paging the UE. The value of the threshold is not limited in this embodiment.

[0128] 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, and the call success rate is used to decide whether to not respond to the Paging message.

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

[0130] 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 so, 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. 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 the s-TMSI match is determined, 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.

[0131] S58. The UE in the RRC Connected state reduces the value of the call success rate, for example, the value of the call success rate minus a preset value.

[0132] S59: The UE in the RRC Connected state increases the value of the call success rate, for example, by increasing the value of the call success rate by a preset value.

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

[0134] 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 in the process of 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 a network abnormality, 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.

[0135] FIG14 shows another signaling diagram of a paging message processing method provided in an embodiment of the present application. The paging processing method shown in FIG14 combines the call success rate and the voice data transmission and reception status to control whether to respond to the Paging message, and may include the following steps:

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

[0137] S66. The UE in the RRC Connected state determines whether the transmission and reception of DRB#3 is normal and whether the call success rate is greater than the threshold value within the first preset time period (e.g., X seconds) before receiving the Paging message. If the transmission and reception of DRB#3 is normal and the call success rate is greater than the threshold value, step S67 is executed. If the transmission and reception of DRB#3 is abnormal and / or the call success rate is not greater than the threshold value, step S613 is executed.

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

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

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

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

[0142] 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 returns to step S612. Whether the timer has timed out may be determined by determining whether the timer has timed out longer than a preset duration. If so, the timer has timed out. Otherwise, the timer has not timed out.

[0143] S612. The UE in the RRC Connected state collects statistics on the call success rate. If the transmission and reception conditions are abnormal and / or the call is disconnected due to a network abnormality, the UE may reduce the call success rate; if the transmission and reception conditions are normal and the call is not disconnected due to a network abnormality, the UE may increase the call success rate.

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

[0145] In this embodiment, during a call of a UE in an RRC Connected state, if the transceiver status in the first preset time period before receiving a Paging message is normal and the call success rate is greater than a threshold value, it indicates that the UE can successfully complete the call without responding to the Paging message, thereby controlling the call and improving the call success rate by combining the call success rate and the transceiver status of DRB#3. Optionally, after not responding to the Paging message, the UE can continue to monitor the call status and the transceiver status of DRB#3 to update the call success rate based on whether the call is disconnected due to a network abnormality and whether the transceiver status of DRB#3 is 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 based on a more accurate call success rate.

[0146] One point worth noting 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 following fields: 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 of at least one of a change in system information, receipt of an etws notification, and receipt of a cmas notification. The UE then responds to the Paging message. The UE's response to the Paging message affects the call conducted via the RRC connection. Responding to the Paging message includes at least one of the following: the UE releasing the RRC resources corresponding to the first RRC connection, the UE switching from the RRC Connected state to the RRC Idle state, the UE sending a request to the LTE base station to trigger reestablishment of the RRC connection, or the UE sending an RRC connection request to the LTE base station. The first RRC connection may be the RRC connection established between the UE and the LTE base station for conducting the call.

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

[0148] A hardware structure of a terminal is shown in FIG15 , and may include: a processor, an external memory interface, internal memory, a Universal Serial Bus (USB) interface, a charging management module, a power management module, a battery, antenna 1, antenna 2, a mobile communication module, a wireless communication module, a sensor module, buttons, a motor, an indicator, a camera, a display, and a SIM card slot. The audio module may include a speaker, a receiver, a microphone, and a headphone jack, 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, and a bone conduction sensor.

[0149] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on the terminal. In other embodiments, the terminal may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0150] The processor may include one or more processing units, for example, the processor may include an application processor (AP), a modem processor (also known as 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 operation control signals based on instruction opcodes and timing signals to complete the control of instruction fetching and execution.

[0151] The wireless communication function of the terminal can be implemented through antenna 1, antenna 2, a mobile communication module, a wireless communication module, and a modem. In some embodiments, antenna 1 of the terminal is coupled to the mobile communication module, and antenna 2 is coupled to the wireless communication module, so that the terminal can communicate with network-side devices and other terminals through wireless communication technology.

[0152] In addition, operating systems run 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.

[0153] The terminal's operating system can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. The embodiments of this application take the Android system with a layered architecture as an example to illustrate the hardware and software structure of the terminal. It should be noted that although the embodiments of this application are described using the Android system as an example, its basic principles are also applicable to terminals based on operating systems such as iOS or Windows.

[0154] Figure 16 is a block diagram of the terminal's software architecture. The software structure employs a layered architecture, which divides the software into several layers, each with distinct roles and responsibilities. Layers communicate with each other via software interfaces. Taking the Android system running on an AP as an example, in some embodiments, the Android system is divided into five layers: from top to bottom, the application layer, the application framework layer (Framework), the Android runtime (Android runtime) and system libraries, the hardware abstraction layer (HAL), and the system kernel layer (Kernel).

[0155] The application layer can include a series of application packages. These packages may include apps such as camera, gallery, calendar, call, map, WLAN, Bluetooth, music, video, and short messaging. The application layer may also include the system UI (system UI), which is used to display the terminal interface, such as the signal icon corresponding to the SIM card and the call interface. The application framework layer provides the application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions. For example, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc. The phone manager is used to provide terminal call functions, such as call status management (including connecting and ending calls). The phone manager is represented by the telephony in Figure 14. The application framework layer may also include the radio interface layer (RIL), through which the modem processor (modem) can exchange information with the telephony.

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

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

[0158] Some embodiments of the present application provide a chip system, applied to a terminal, comprising at least one processor and an interface, the interface being configured to receive instructions and transmit them to the at least one processor; the at least one processor executing the instructions causes the terminal to execute the aforementioned paging message processing method. The chip system may be a modem, or a system on a chip (SoC) including a modem, and the aforementioned paging message processing method may be implemented by the 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, and the terminal disconnects from the RRC Connected The state is switched to the RRC Idle state, the terminal sends a request to the network side device to trigger re-establishing 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