CN113329522A

CN113329522A - Method for acquiring timer parameter, terminal device and storage medium

Info

Publication number: CN113329522A
Application number: CN202110617832.8A
Authority: CN
Inventors: 张闯德
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-05-31
Filing date: 2021-05-31
Publication date: 2021-08-31
Anticipated expiration: 2041-05-31
Also published as: CN113329522B; WO2022252716A1

Abstract

The embodiment of the invention discloses a method for acquiring timer parameters, a terminal device and a storage medium, which are used for ensuring that the subsequent reestablishment process of the terminal device can be normally executed. The method provided by the embodiment of the invention comprises the following steps: under the conditions that a timer parameter providing radio link failure exists in a radio resource control reconfiguration message and a DAPS scene exists in a dual-activity protocol stack, configuring a first timer according to a first timer value carried by the timer parameter of radio link failure; and configuring a second timer according to a second timer value carried by the timer parameter of the user equipment in the system information block message.

Description

Method for acquiring timer parameter, terminal device and storage medium

Technical Field

The present invention relates to the field of communications, and in particular, to a method for acquiring a timer parameter, a terminal device, and a storage medium.

Background

At present, the Timer parameters (radio link failure-Timer And Constants, rlf-timerarandconstants) carried by the radio link failure Timer parameters are only T310 And T311, but do not have T301. In a Dual Active Protocol Stack (DAPS) scenario and when the network provides rlf-TimerAndConstants in a Radio Resource Control Reconfiguration (rrcrreconfiguration) message, timer T301 is obtained from rlf-TimerAndConstants, but rlf-timerseandconstants do not carry T301, thus making it impossible to obtain the value of timer T301. If the timer T301 has no available value, the reestablishment process of the terminal device may not be completed, and further, a phenomenon of communication connection interruption or even network disconnection may be caused, which affects user experience.

Disclosure of Invention

The embodiment of the invention provides a method for acquiring timer parameters, a terminal device and a storage medium, which are used for ensuring that the subsequent reestablishment process of the terminal device can be normally executed.

A first aspect of the present application provides a method for acquiring a timer parameter, where the method is applied to a terminal device, and the method may include:

under the conditions that a timer parameter providing radio link failure exists in a radio resource control reconfiguration message and a DAPS scene exists in a dual-activity protocol stack, configuring a first timer according to a first timer value carried by the timer parameter of radio link failure;

and configuring a second timer according to a second timer value carried by the timer parameter of the user equipment in the system information block message.

A second aspect of the present application provides a terminal device, which may include:

a processing module, configured to configure a first timer according to a first timer value carried by a timer parameter for providing a radio link failure in a radio resource control reconfiguration message and in a dual activity protocol stack DAPS scenario; and configuring a second timer according to a second timer value carried by the timer parameter of the user equipment in the system information block message.

Yet another aspect of the present application provides a terminal device, which may include:

a memory storing executable program code;

a processor coupled with the memory;

the processor calls the executable program code stored in the memory for performing the method of the first aspect of the application.

Yet another aspect of the embodiments of the present application provides a computer-readable storage medium, comprising instructions, which when executed on a processor, cause the processor to perform the method of the first aspect of the present application.

In yet another aspect, embodiments of the present application disclose a computer program product, which when run on a computer, causes the computer to perform the method of the first aspect of the present application.

In yet another aspect, an application publishing platform is disclosed, which is configured to publish a computer program product, wherein when the computer program product runs on a computer, the computer is caused to perform the method of the first aspect of the present application.

According to the technical scheme, the embodiment of the invention has the following advantages:

in the embodiment of the present application, when a radio resource control reconfiguration message includes a timer parameter providing a radio link failure and is in a dual activity protocol stack DAPS scenario, configuring a first timer according to a first timer value carried by the timer parameter providing the radio link failure; and configuring a second timer according to a second timer value carried by the timer parameter of the user equipment in the system information block message. The technical scheme is to perfect the existing 3GPP scheme, and in a DAPS scenario, when the network device provides the timer parameter of radio link failure in the radio resource control reconfiguration message, the second timer is configured according to a second timer value carried by the timer parameter of the user equipment in the system information block message, so that the possible reestablishment process of the subsequent terminal device can be normally executed.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the embodiments and the drawings used in the description of the prior art, and obviously, the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained according to the drawings.

FIG. 1A is an exemplary diagram of a DAPS scenario;

fig. 1B is a schematic diagram of a DAPS scene acquisition timer method in the prior art;

fig. 2 is a system architecture diagram of a communication system to which an embodiment of the present application is applied;

FIG. 3A is a diagram of an embodiment of a method for obtaining a timer parameter in an embodiment of the present application;

fig. 3B is a schematic diagram illustrating obtaining T301 timer parameters in the embodiment of the present application;

FIG. 4 is a schematic diagram of an embodiment of a terminal device in the embodiment of the present application;

fig. 5 is a schematic diagram of another embodiment of the terminal device in the embodiment of the present application.

Detailed Description

In order to make the technical solutions of the present invention better understood by those skilled in the art, the technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. The embodiments based on the present invention should fall into the protection scope of the present invention.

1. Introduction of 5G network and application scenario

Currently, with the pursuit of high rate, low latency, high speed mobility and the diversity and complexity of the services in future life, the 3rd Generation Partnership Project (3 GPP) international standards organization has begun to develop 5G. The main application scenarios of 5G are: enhanced Mobile Broadband (eMBB), ultra-reliable low latency communications (uRLLC), and massive Machine Type Communication (mMTC).

Among the key characteristics of urrllc are low latency, in which case the connection latency is 1ms or less, and high reliability (99.999%) of high speed mobile (500 KM/H (KM/H)) connections are supported. Typical applications of urrllc include: industrial automation, automatic driving, electric power automation, remote medical operation (operation) and the like, and the application has extremely high potential value and can accelerate the intellectualized pace of the future society.

2. Dual Active Protocol Stack (DAPS) scene introduction

In a conventional 4G Long Term Evolution (LTE) network and a 5G New Radio (NR) R15 network, when a User Equipment (UE) performs a cell handover during a moving process, a connection is usually released from a source cell and then established with a target cell, which is a so-called hard handover. Therefore, uplink and downlink data are transmitted in the source cell before the handover is completed and in the target cell after the handover is completed, which may cause interruption of communication between the UE and the base station for several tens of milliseconds, which is fatal to the application of the 5G urrllc.

Therefore, the 3GPP proposes a new solution to address the communication interruption problem, i.e. Dual Active Protocol Stack (DAPS), i.e. the UE maintains the communication connection with the source cell and the target cell simultaneously, at R16. And in the switching process, the UE receives downlink data at the same time in the source cell and the target cell, the uplink data is transmitted through the source cell before the switching is finished, and the uplink data is transmitted through the target cell after the switching is finished. As shown in fig. 1A, an exemplary diagram of a DAPS scenario is shown.

3. DAPS scene acquisition timer parameters

According to the 3GPP 38.331 protocol, the description of acquiring timer parameters in the current DAPS scenario is as follows:

1> if no Radio link failure-Timer And configuration (rlf-timerandconfiguration) is provided in the Radio Resource Control Reconfiguration (rrcReconfiguration) message;

2> if there is a configured DAPS bearer (bearer);

3> timers T301, T310, T311, and counters N310 and N311, using the value of the corresponding timer carried by ue-time and counters in the System Information Block 1 (SIB 1) message, and the value of the corresponding counter;

2> else (no DAPS bear configured, i.e. non-dual active protocol stack scenario);

3> timers T301, T310, T311, and counters N310 and N311, using the value of the corresponding timer and the value of the corresponding counter carried by ue-timersandcounters in the SIB1 message;

1> else (rlf-TimerAndConstants are provided in the rrcReconfiguration message);

2> if there is configuration DAPS bearer;

3> timer uses the timer value carried by rlf-TimersAndConstations;

3> configuring or reconfiguring the corresponding timer value according to the timer carried by rlf-TimersAndConstations;

3> if timer T310 is running, stop T310;

3> if timer T312 is running, stop T312;

3> reset the counts of N310 and N311.

Wherein, the rrcReconfiguration message is sent to the UE by the network for modifying the network connection parameters. The special Cell configuration (spcellconfiguration) in the Cell group configuration (CellGroupConfig) in the master Cell group (masterCellGroup) in the non-critical extension (nonCriticalExtension) in the rrcReconfiguration message contains rlf-TimerAndConstants, rlf-TimerAndConstants contain the values of timers such as T310, N310, T311, N311, etc. The spCell includes a Primary Cell (PCell) and a Primary Secondary Cell (PSCell).

As follows: is the timer information content in the rrcReconfiguration message.

In addition, a DAPS bear refers to a radio bearer existing in both the source cell and the target cell, and a DARS scenario is represented by a configured DAPS bear.

The SIB1 message is sent by the network to the UE, and is used to carry relevant information such as cell camping parameters and serving cell configuration parameters. The SIB1 includes ue-timersanddates, and ue-timersanddates includes timer information including timers such as T301, T310, N310, T311, and N311.

As follows: is the timer information content in the SIB1 message.

In the prior art scheme, in a DAPS scenario, if a network provides rlf-TimerAndConstants in an rrcReconfiguration message, a timer uses a timer value carried by rlf-timersandcondtimes; if the network does not provide rlf-TimerAndConstants in the rrcReconfiguration message, the timer uses the timer value carried by the ue-TimersAndConstants in the SIB1 message, and a specific processing flow is as shown in fig. 1B, where fig. 1B is a schematic diagram of a method for acquiring a timer in a DAPS scene in a prior art scheme.

According to the above description, the timer values carried by the current rlf-TimersAndContents are only the values of the timers T310, T311, N310, N311, but not the value of T301. According to fig. 1B, in a DAPS scenario and when the network provides rlf-TimerAndConstants in the rrcReconfiguration message, timer T301 is obtained from rlf-TimerAndConstants, but rlf-timersandconsints do not carry T301, thus making it impossible to obtain the value of timer T301.

According to the 3GPP 38.331 protocol, the timer T301 is an indispensable timer in the re-establishment process, and the usage scenario of the timer T301 is as shown in table 1 below:

TABLE 1

After the DAPS handover is completed, due to a change of a network signal, a reestablishment process is easily generated in a cell to which the terminal device is currently accessed, and if the timer T301 has no available value, the reestablishment process may not be completed, which may cause a phenomenon of communication connection interruption or even network disconnection, thereby affecting user experience.

Various embodiments are described in conjunction with network Equipment and terminal Equipment, where the terminal Equipment may also be referred to as User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User device.

The terminal device may be a station (station, ST) in a Wireless Local Area Network (WLAN), and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next generation communication system such as an NR Network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like.

In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.).

In this embodiment, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in city (smart city), a wireless terminal device in smart home (smart home), or the like.

By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

In this embodiment, the network device may be a device for communicating with a mobile device, and the network device may be a network device in an NR network (gNB) or a network device in a PLMN network for future evolution, or a network device in a Non-Terrestrial network (NTN) network, and the like.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a geosynchronous Orbit (GEO) satellite, a High Elliptic Orbit (HEO) satellite, and the like. Alternatively, the network device may be a base station installed on land, water, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, and a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (e.g., a base station), and the cell may belong to a macro base station or a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), Micro cells (Micro cells), Pico cells (Pico cells), Femto cells (Femto cells), and the like, and the small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-rate data transmission services.

Fig. 2 is a diagram illustrating a system architecture of a communication system to which an embodiment of the present application is applied. The communication system may include a network device, which may be a device that communicates with a terminal device (or referred to as a communication terminal, a terminal). A network device may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Fig. 2 exemplarily shows one network device and two terminal devices, and optionally, the communication system may include a plurality of network devices and each network device may include other numbers of terminal devices within the coverage area, which is not limited in this embodiment of the present application. Optionally, the communication system may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a Next Radio (NR) system or a new generation base station (gnnodeb).

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system shown in fig. 2 as an example, the communication device may include a network device and a terminal device having a communication function, and the network device and the terminal device may be specific devices described in this embodiment, which are not described herein again; the communication device may further include other devices in the communication system, such as other network entities like a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

The following further describes the technical solution of the present application by way of an embodiment, as shown in fig. 3A, which is a schematic diagram of an embodiment of a method for acquiring a timer parameter in the embodiment of the present application, and the method may include:

301. and the terminal equipment receives the radio resource control reconfiguration message in the operation process.

Illustratively, the UE receives a radio resource control reconfiguration (rrcReconfiguration) message sent by the network device during operation.

302. The terminal equipment judges whether the timer parameter of the radio link failure is provided in the radio resource control reconfiguration message.

The UE determines whether a timer parameter for radio link failure is provided in the rrcReconfiguration message (rlf-TimerAndConstants).

It will be appreciated that

steps

301 and 302 are optional steps.

303. Under the conditions that a timer parameter providing radio link failure exists in a radio resource control reconfiguration message and a DAPS scene exists in a dual-activity protocol stack, configuring a first timer according to a first timer value carried by the timer parameter of radio link failure; and configuring a second timer according to a second timer value carried by the timer parameter of the user equipment in the system information block message.

That is, it can be understood that, in the case that there is a timer parameter providing a radio link failure in the radio resource control reconfiguration message and in the dual activity protocol stack DAPS scenario, the first timer may use a first timer value carried by the timer parameter providing the radio link failure; the second timer may use a second timer value carried by a timer parameter of the user equipment in the system information block message.

The terminal device is in a DAPS scenario, that is, the terminal device receives a DAPS bearer sent by the network device, where the DAPS bearer may be carried in the radio resource control reconfiguration message. The terminal device being in the DAPS scenario may also be understood as the terminal device being currently in a CONNECTED state (e.g., RRC _ CONNECTED state).

Optionally, the method further includes: under the condition that a radio resource control reconfiguration message contains a timer parameter providing the radio link failure and is in a non-DAPS scene, configuring a first timer according to a first timer value carried by the timer parameter of the radio link failure, or reconfiguring the first timer; that is, it can be understood that the first timer may use a first timer value carried by the timer parameter of the radio link failure, or the first timer may use a reconfigured first timer value; or the like, or, alternatively,

stopping running the first target timer if the first target timer is running; or the like, or, alternatively,

stopping running a second target timer if the second target timer is running;

wherein the first timer comprises the first target timer and the second target timer.

Optionally, the first timer value carried by the timer parameter for radio link failure includes: t310, T311; the second timer value carried by the timer parameter of the user equipment comprises: and T301.

Optionally, the system information block may include SIB 1.

Illustratively, in the rrcReconfiguration message, rlf-TimerAndConstants are provided, and in the case of a DAPS scenario, the first timers T310 and T311 are configured according to corresponding timer values carried by rlf-TimerAndConstants; the second timer T301 is configured according to the corresponding timer value carried by ue-timersanddates in SIB 1.

In the case that rlf-TimerAndConstants are provided in the rrcReconfiguration message and the DAPS scenario is not present, the first timers T310 and T311 may use the corresponding timer values carried by rlf-TimerAndConstants or the reconfigured corresponding timer values; or the like, or, alternatively,

in a case where the first target timer T310 is running, stopping running T310; or the like, or, alternatively,

in the case where the second target timer T312 is running, the running T312 is stopped.

304. Under the condition that the timer parameter of the radio link failure is not provided in the radio resource control reconfiguration message and the radio resource control reconfiguration message is in the DAPS scene, configuring a timer according to a timer value carried by the timer parameter of the user equipment in the system information block message; wherein the timer value carried by the timer parameter of the user equipment comprises a second timer value carried by the timer parameter of the user equipment; the timer includes the first timer and the second timer.

That is, it can be understood that, in the case that the timer parameter of the radio link failure is not provided in the radio resource control reconfiguration message, and in the DAPS scenario, the timer may use the timer value carried by the timer parameter of the user equipment in the system information block message.

Optionally, the method further includes: and under the condition that the timer parameter of the radio link failure is not provided in the radio resource control reconfiguration message and the radio resource control reconfiguration message is in a non-DAPS scene, configuring the timer according to a timer value carried by the timer parameter of the user equipment in the system information block message. That is, it can be understood that the timer may use a timer value carried by a timer parameter of the user equipment in the system information block message.

Optionally, the timer value carried by the timer parameter of the user equipment includes: t301, T310, T311.

Illustratively, in the case where rlf-TimerAndConstants are not provided in the rrcReconfiguration message and in the DAPS scenario, the timers T301, T310, and T311 are configured according to the corresponding timer values carried by the ue-TimersAndConstants.

In the case that the rlf-TimerAndConstants are not provided in the rrcReconfiguration message and in the non-DAPS scenario, the timers T301, T310, and T311 are configured according to the corresponding timer values carried by the ue-TimersAndConstants.

Illustratively, the process of acquiring the new T301 timer in the timer parameter acquiring part in the DAPS scenario is described as follows:

1> if rlf-TimerAndConstants are not provided in the rrcReconfiguration message;

2> if there is configuration DAPS bearer;

1> else (rlf-TimerAndConstants are provided in the rrcReconfiguration message);

2> if there is configuration DAPS bearer;

3> timer uses the timer value carried by rlf-TimersAndConstations;

the 3> T301 timer uses the timer value carried by ue-TimersAndContents in the SIB1 message;

3> if timer T310 is running, stop T310;

3> if timer T312 is running, stop T312;

3> reset the counts of N310 and N311.

Illustratively, as shown in fig. 3B, a schematic diagram of acquiring a T301 timer parameter in the embodiment of the present application is shown. In fig. 3B, the timer includes a first timer and a second timer T301.

In the embodiment of the present application, when a radio resource control reconfiguration message includes a timer parameter providing a radio link failure and is in a dual activity protocol stack DAPS scenario, configuring a first timer according to a first timer value carried by the timer parameter providing the radio link failure; and configuring a second timer according to a second timer value carried by the timer parameter of the user equipment in the system information block message. The technical scheme is to perfect the existing 3GPP scheme, and in a DAPS scenario, when the network device provides the timer parameter of radio link failure in the radio resource control reconfiguration message, the second timer is configured according to a second timer value carried by the timer parameter of the user equipment in the system information block message, so that the possible reestablishment process of the subsequent terminal device can be normally executed. For example: in a DAPS scenario and when the network device provides rlf-TimerAndConstants in the rrcreonfiguration message, the timers T310 and T311, and the counters N310 and N311 use the acquisition method in the prior art scheme, that is, the timer value and the counter value carried by rlf-TimersAndConstants are used; the timer T301 uses the method proposed in the technical solution of the present application, i.e., uses the timer value carried by ue-timer and timers status in the SIB1 message. Therefore, all timers used by the terminal equipment in the reestablishment process can obtain effective values, and normal execution of the UE reestablishment process is guaranteed.

As shown in fig. 4, which is a schematic diagram of an embodiment of a terminal device in the embodiment of the present application, the method may include:

a processing module 401, configured to configure a first timer according to a first timer value carried by a timer parameter of a radio link failure when the radio resource control reconfiguration message includes the timer parameter of the radio link failure and is in a dual activity protocol stack DAPS scenario; and configuring a second timer according to a second timer value carried by the timer parameter of the user equipment in the system information block message.

Optionally, the processing module 401 is further configured to, in the radio resource control reconfiguration message, provide a timer parameter that provides the radio link failure, and configure the first timer according to a first timer value carried by the timer parameter that provides the radio link failure in a non-DAPS scenario, or reconfigure the first timer again; or the like, or, alternatively,

stopping running a second target timer if the second target timer is running;

Optionally, the processing module 401 is further configured to, in the radio resource control reconfiguration message, not provide the timer parameter of the radio link failure, and in the case of the DAPS scenario, configure the timer according to a timer value carried by the timer parameter of the user equipment in the system information block message;

wherein the timer value carried by the timer parameter of the user equipment comprises a second timer value carried by the timer parameter of the user equipment; the timer includes the first timer and the second timer.

Optionally, the processing module 401 is further configured to, in the radio resource control reconfiguration message, not provide the timer parameter of the radio link failure, and in a non-DAPS scenario, configure the timer according to a timer value carried by the timer parameter of the user equipment in the system information block message.

Optionally, the first timer value carried by the timer parameter for radio link failure includes: t310, T311;

the second timer value carried by the timer parameter of the user equipment comprises: and T301.

Optionally, the timer value carried by the timer parameter of the ue further includes: t300 and T319.

Corresponding to at least one method applied to the terminal device, the embodiment of the application further provides one or more terminal devices. The terminal device of the embodiment of the application can implement any one implementation manner of the above methods. As shown in fig. 5, which is a schematic view of another embodiment of the terminal device in the embodiment of the present application, the terminal device is described by taking a mobile phone as an example, and may include: radio Frequency (RF) circuitry 510, memory 520, input unit 530, display unit 540, sensor 550, audio circuitry 560, wireless fidelity (WiFi) module 570, processor 580, and power supply 590. Therein, the radio frequency circuit 510 includes a receiver 514 and a transmitter 512. Those skilled in the art will appreciate that the handset configuration shown in fig. 5 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile phone in detail with reference to fig. 5:

RF circuit 510 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, for processing downlink information of a base station after receiving the downlink information to processor 580; in addition, the data for designing uplink is transmitted to the base station. In general, RF circuit 510 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, RF circuit 510 may also communicate with networks and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to global system for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), etc.

The memory 520 may be used to store software programs and modules, and the processor 580 executes various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 520. The memory 520 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 520 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 530 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 530 may include a touch panel 531 and other input devices 532. The touch panel 531, also called a touch screen, can collect touch operations of a user on or near the touch panel 531 (for example, operations of the user on or near the touch panel 531 by using any suitable object or accessory such as a finger or a stylus pen), and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 531 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor 580, and can receive and execute commands sent by the processor 580. In addition, the touch panel 531 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 530 may include other input devices 532 in addition to the touch panel 531. In particular, other input devices 532 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 540 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 540 may include a display panel 541, and optionally, the display panel 541 may be configured in the form of a Liquid Crystal Display (LCD), an organic light-Emitting diode (OLED), or the like. Further, the touch panel 531 may cover the display panel 541, and when the touch panel 531 detects a touch operation on or near the touch panel 531, the touch panel is transmitted to the processor 580 to determine the type of the touch event, and then the processor 580 provides a corresponding visual output on the display panel 541 according to the type of the touch event. Although the touch panel 531 and the display panel 541 are shown as two separate components in fig. 5 to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 531 and the display panel 541 may be integrated to implement the input and output functions of the mobile phone.

The handset may also include at least one sensor 550, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 541 according to the brightness of ambient light, and the proximity sensor may turn off the display panel 541 and/or the backlight when the mobile phone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

Audio circuitry 560, speaker 561, and microphone 562 may provide an audio interface between a user and a cell phone. The audio circuit 560 may transmit the electrical signal converted from the received audio data to the speaker 561, and convert the electrical signal into a sound signal by the speaker 561 for output; on the other hand, the microphone 562 converts the collected sound signals into electrical signals, which are received by the audio circuit 560 and converted into audio data, which are then processed by the audio data output processor 580, and then passed through the RF circuit 510 to be sent to, for example, another cellular phone, or output to the memory 520 for further processing.

WiFi belongs to short distance wireless transmission technology, and the mobile phone can help the user to send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 570, which provides wireless broadband internet access for the user. Although fig. 5 shows the WiFi module 570, it is understood that it does not belong to the essential constitution of the handset, and can be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 580 is a control center of the mobile phone, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 520 and calling data stored in the memory 520, thereby performing overall monitoring of the mobile phone. Alternatively, processor 580 may include one or more processing units; preferably, the processor 580 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 580.

The handset also includes a power supply 590 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 580 via a power management system, such that the power management system may be used to manage charging, discharging, and power consumption. Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.

In this embodiment of the present application, the processor 580 is configured to, when a radio resource control reconfiguration message includes a timer parameter that provides a radio link failure and is in a dual activity protocol stack DAPS scenario, configure a first timer according to a first timer value carried by the timer parameter that provides the radio link failure; and configuring a second timer according to a second timer value carried by the timer parameter of the user equipment in the system information block message.

Optionally, the processor 580 is further configured to, in the radio resource control reconfiguration message, provide a timer parameter that provides the radio link failure, and in a case that the radio resource control reconfiguration message is in a non-DAPS scenario, configure the first timer according to a first timer value carried by the timer parameter that provides the radio link failure, or reconfigure the first timer; or the like, or, alternatively,

stopping running a second target timer if the second target timer is running;

Optionally, the processor 580 is further configured to, when the timer parameter of the radio link failure is not provided in the radio resource control reconfiguration message and the user equipment is in the DAPS scenario, configure the timer according to a timer value carried by the timer parameter of the user equipment in the system information block message;

Optionally, the processor 580 is further configured to, when the timer parameter of the radio link failure is not provided in the radio resource control reconfiguration message and the ue is in a non-DAPS scenario, configure the timer according to a timer value carried by the timer parameter of the ue in the system information block message.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. A method for acquiring timer parameters is applied to a terminal device, and the method comprises the following steps:

2. The method of claim 1, further comprising:

under the condition that a radio resource control reconfiguration message contains a timer parameter providing the radio link failure and is in a non-DAPS scene, configuring a first timer according to a first timer value carried by the timer parameter of the radio link failure, or reconfiguring the first timer; or the like, or, alternatively,

stopping running a second target timer if the second target timer is running;

3. The method of claim 1, further comprising:

under the condition that the timer parameter of the radio link failure is not provided in the radio resource control reconfiguration message and the radio resource control reconfiguration message is in the DAPS scene, configuring a timer according to a timer value carried by the timer parameter of the user equipment in the system information block message;

4. The method of claim 3, further comprising:

and under the condition that the timer parameter of the radio link failure is not provided in the radio resource control reconfiguration message and the radio resource control reconfiguration message is in a non-DAPS scene, configuring the timer according to a timer value carried by the timer parameter of the user equipment in the system information block message.

5. The method according to any one of claims 1 to 4,

the first timer value carried by the timer parameter for radio link failure comprises: t310, T311;

6. The method of claim 5, wherein the timer value carried by the timer parameter of the UE comprises: t301, T310, T311.

7. The method of claim 6, wherein the timer value carried by the timer parameter of the UE further comprises: t300 and T319.

8. A terminal device, comprising:

9. A terminal device, comprising:

a memory storing executable program code;

a processor coupled with the memory;

the processor calls the executable program code stored in the memory for performing the method of any one of claims 1-7.

10. A computer-readable storage medium comprising instructions that, when executed on a processor, cause the processor to perform the method of any of claims 1-7.