CN115568011A

CN115568011A - Method for user equipment to initiate IMS registration and corresponding user equipment

Info

Publication number: CN115568011A
Application number: CN202210116441.2A
Authority: CN
Inventors: 陈拴锋; 孙敏; 张忠理
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-02-07
Filing date: 2022-02-07
Publication date: 2023-01-03
Anticipated expiration: 2042-02-07
Also published as: WO2023147754A1; CN115568011B

Abstract

The application provides a method for user equipment to initiate IMS registration and corresponding user equipment. The method comprises the following steps: initiating registration to the IMS; receiving a registration failure response message from the IMS; updating IMS registration failure times according to the registration failure response message, and starting a monitoring timer; receiving a registration failure response message for re-registration from the IMS after re-registration is initiated to the IMS each time from the start of the monitoring timer to the expiration of the monitoring timer; updating the number of times of IMS registration failure according to the registration failure response message aiming at the re-registration; disabling the IMS capability of the user equipment when the number of IMS registration failures exceeds a preset threshold before expiration of the monitoring timer.

Description

Method for user equipment to initiate IMS registration and corresponding user equipment

Technical Field

The present invention relates to the field of wireless communications, and in particular, to a method for a User Equipment (UE) to initiate Internet protocol Multimedia Subsystem (IMS) registration and a corresponding UE.

Background

Starting from Long Time Evolution (LTE), a Voice implementation scheme is proposed in which Voice services are carried over an IP network through an IMS, that is, a Voice over LTE (Voice over LTE) technology. In a 5G (which may also be referred to as New Radio (NR)) wireless communication system, a manner of continuing to carry Voice traffic over an IP network is proposed, and Voice traffic, that is, a VoNR (Voice over NR) technology, is implemented through a 5G network and an IMS. After the UE successfully registers on the IMS, the UE can realize the voice service through the technologies.

However, when the UE initiates an IMS registration, the IMS may not respond to the IMS registration request sent thereto by the UE due to a network abnormality, or the IMS may feed back a Session Initiation Protocol (SIP) error code (e.g., 403 message, 480 message, etc.) to the UE due to a network abnormality. In this case, the UE may reinitiate IMS registration, but registration will not succeed due to network anomaly. Currently, the communication system does not limit the number of times the UE re-initiates IMS registration, and therefore, the UE may frequently initiate IMS registration, which may increase power consumption of the UE.

Furthermore, after the UE receives 403 the message, the UE can initiate IMS registration again after a period of time. This state of the UE may be referred to as an IMS registration restriction state. After the IMS registration procedure is completed, the UE enters an idle state, and the network generally releases Radio Resource Control (RRC) connection for the UE. However, when the network is abnormal, the network does not release the RRC connection or releases the RRC slowly. To facilitate the release of the RRC connection, the UE may actively initiate a Tracking Area Update (TAU). However, the UE actively initiating a TAU may cause the UE to escape from the IMS registration limited state. The escaped UE will initiate IMS registration again and then receive 403 the message and initiate TAU since the network does not release RRC connection or the speed of releasing RRC is slow. Such an infinite number of cycles may increase the power consumption of the UE.

In addition, for a Dual Sim Dual Standby (DSDS) mobile phone, frequent initiation of IMS registration by the secondary card may cause the secondary card to frequently occupy the resources of the primary card, thereby affecting the internet access experience of the primary card.

Disclosure of Invention

In order to overcome the above drawbacks, the present application provides a method for a UE to initiate an IMS registration and a corresponding user equipment.

One aspect of the embodiments of the present application provides a method for a user equipment to initiate an internet protocol multimedia subsystem IMS registration, including: initiating a registration with the IMS; receiving a registration failure response message from the IMS; updating IMS registration failure times according to the registration failure response message, and starting a monitoring timer; receiving a registration failure response message for re-registration from the IMS after re-registration is initiated to the IMS each time from the start of the monitoring timer to the expiration of the monitoring timer; updating the IMS registration failure times according to the registration failure response message aiming at the re-registration; disabling an IMS capability of the user equipment when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires.

According to an example of the present application, wherein initiating registration with the IMS comprises: sending an IMS registration request to the IMS, and starting a first timer; wherein receiving a registration failure response message from the IMS comprises: receiving a registration failure response message from the IMS before expiration of the first timer.

According to an example of the present application, when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires, the method further includes: clearing the IMS registration failure times; the supervision timer is terminated.

According to an example of the present application, the method further comprises: when the user equipment receives a user instruction before the monitoring timer expires to perform at least one of: and when the mobile terminal is started, restarted, exits from the flight mode or is plugged and unplugged in a hot mode, the mobile terminal initiates re-registration to the IMS.

According to an example of the present application, wherein disabling IMS capabilities of the user equipment comprises: starting a third timer and disabling IMS capabilities of the user equipment before expiration of the third timer.

According to an example of the present application, the method further comprises: when a public land mobile network of the user equipment changes before the third timer expires, or a tracking area of the user equipment is updated, or the user equipment receives a user instruction to perform at least one of: and when the mobile terminal is started, restarted, exits from the flight mode or is hot plugged and unplugged, terminating the third timer and starting the IMS (IP multimedia subsystem) capability of the user equipment.

According to an example of the present application, the method further comprises: when the public land mobile network of the user equipment is not changed before the third timer expires, or the tracking area of the user equipment is not updated, or the user equipment does not receive a user instruction to perform at least one of: and when the mobile terminal is started, restarted, exits from a flight mode or is hot plugged and unplugged, starting the IMS capability of the user equipment after the third timer expires.

According to an example of the present application, wherein updating the number of IMS registration failures according to the registration failure response message, starting the monitoring timer comprises: updating IMS registration failure times corresponding to the type of the registration failure response message according to the type of the registration failure response message, and starting a monitoring timer corresponding to the type of the registration failure response message; wherein updating the number of IMS registration failures according to the registration failure response message for re-registration comprises: updating the IMS registration failure times corresponding to the type of the registration failure response message according to the type of the registration failure response message aiming at the re-registration; wherein disabling IMS capability of the user equipment when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires comprises: and when the IMS registration failure times corresponding to any monitoring timer exceeds a preset threshold before the monitoring timer corresponding to the type of any registration failure response message expires, forbidding the IMS capability of the user equipment.

According to an example of the present application, when the number of IMS registration failures corresponding to any monitoring timer exceeds a preset threshold before any monitoring timer expires, the method further includes: clearing the number of times of IMS registration failure; the respective watchdog timer is terminated.

According to an example of the present application, the registration failure response message is a session initiation protocol, SIP, error code, and the type of the registration failure response message is a type of the SIP error code, and the type of the SIP error code includes at least one of: SIP 403 messages, SIP 404 messages, SIP 408 messages, SIP 480 messages, SIP 503 messages, SIP 504 messages.

Another aspect of the embodiments of the present application provides a method for a user equipment to initiate an internet protocol multimedia subsystem IMS registration, including: initiating registration to the IMS and starting a first timer; determining a registration failure result for the registration, wherein the registration failure result includes that the user equipment receives a registration failure response message before the first timer expires, or that the user equipment does not receive a registration failure response message or a registration normal response message before the first timer expires; updating IMS registration failure times according to the registration failure result aiming at the registration, and starting a monitoring timer; determining a registration failure result for re-registration after re-registration is initiated to the IMS each time from the start of the monitoring timer to the expiration of the monitoring timer; updating the IMS registration failure times according to the registration failure result aiming at the re-registration; disabling an IMS capability of the user equipment when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires.

Another aspect of an embodiment of the present application provides a user equipment, including: a memory for storing computer program code, the computer program code comprising computer instructions; and a processor for causing the user equipment to perform the above method when the computer instructions are executed.

By the method and the user equipment, power consumption increase caused by frequent IMS registration initiation of the UE can be avoided, resources of the main card are prevented from being frequently preempted by the auxiliary card due to frequent IMS registration initiation of the auxiliary card, internet surfing experience of the main card is prevented from being influenced, and the like.

Drawings

The above and other objects, features and advantages of the present application will become more apparent from the detailed description when taken in conjunction with the accompanying drawings. The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the application. The same reference numbers will be used throughout the drawings to refer to the same or like elements, features, and structures, wherein:

fig. 1 is a schematic diagram of a wireless communication system in which embodiments of the present application may be applied;

fig. 2A is a schematic diagram illustrating a user interface of a UE before performing IMS registration or after IMS registration fails according to an embodiment of the present application;

FIG. 2B is a diagram illustrating a user interface after a UE successfully registers with an IMS in accordance with an embodiment of the present application;

fig. 3 is a schematic diagram of a hardware structure of a UE according to an embodiment of the present application;

fig. 4 is a flowchart illustrating a method for suppressing frequent IMS registration initiation by a UE according to an embodiment of the present application;

fig. 5 is another flowchart illustrating a method for suppressing frequent IMS registration initiation by a UE according to an embodiment of the present application;

fig. 6 is a schematic flowchart of a method for suppressing frequent IMS registration initiation by a UE according to an embodiment of the present application;

fig. 7 is another flowchart illustrating a method for suppressing frequent IMS registration initiation by a UE according to an embodiment of the present application.

Detailed Description

The terms "first," "second," and "third," etc. in the description and claims of the present application and the description of the drawings are used for distinguishing between different objects and not for limiting a particular order.

In the embodiments of the present application, the words "exemplary" or "such as" are used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "such as" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The terminology used in the description of the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application, which will be described in detail below with reference to the accompanying drawings.

First, a wireless communication system in which the embodiments of the present application can be applied is described with reference to fig. 1. Fig. 1 is a schematic diagram of a wireless communication system in which embodiments of the present application may be applied. The wireless communication system may be LTE, or may be a 5G wireless communication system, or a new communication system that appears in the future development of wireless communication, or the like. As long as the wireless communication system adopts IMS as a voice implementation scheme, the wireless communication system may apply the embodiments of the present application.

As shown in fig. 1, the wireless communication system 100 includes a UE 101, an access network device 102 that provides an LTE network for the UE 101, an access network device 103 that provides a 5G network for the UE 101, a core network device 104, and an IP Multimedia Subsystem (IMS) 105.

The IMS 105 may include a Proxy-Call Session Control Function (P-CSCF) entity, an Interrogating-Call Session Control Function (I-CSCF), a Serving-Call Session Control Function (S-CSCF) entity, and a Home Subscriber Server (HSS).

The P-CSCF entity is the first point of attachment of the access network to the IMS, and all session messages originating from and terminating at IMS-capable UEs are forwarded through the P-CSCF entity. The P-CSCF entity is operable to forward an IMS registration request from the UE to the S-CSCF entity and to forward a registration response message to the UE.

The I-CSCF entity may connect the S-CSCF entity and the P-CSCF entity for providing the UE with access to the home network. During IMS registration, the P-CSCF entity may forward an IMS registration request from the UE to the I-CSCF entity, which may query an HSS in the IMS to select an S-CSCF entity for the UE. In the calling process, a calling message destined for an IMS network is firstly routed to an I-CSCF, an I-CSCF entity can inquire the address information of an S-CSCF entity registered by a user for UE through an HSS in the IMS, and then the message is routed to the S-CSCF.

The S-CSCF entity is the control core of the IMS and provides functions of session control, registration and the like for the UE. And the S-CSCF entity is used for receiving the IMS registration request forwarded by the P-CSCF entity and carrying out authentication on the UE by matching with the HSS. And after the S-CSCF determines that the authentication is passed, the subscription information of the UE is acquired from the HSS. And the S-CSCF entity is also used for connecting with each application server based on the ISC interface, and triggering the application servers to execute operation, and routing the request of the UE to the corresponding application servers.

The HSS is used to store all user and service related data such as user identity, subscription information, access information, etc.

It should be understood that although the wireless communication system 100 shown in fig. 1 includes only one UE 101, one access network device 102, and one access network device 103, the wireless communication system 100 may include more UEs and/or more access network devices. In addition, the wireless communication system 100 may also include an access network device that provides a 2G/3G network for the UE 101.

The UE 101 may generate an IMS registration request when an event such as power-on, reboot, exit from flight mode, hot-plug card, or IMS registration failure occurs. The UE 101 may then send the IMS registration request to a P-CSCF entity in the IMS 105 through the access network and the core network. The UE 101 may also receive a registration response message from the IMS 105 through the core network and the access network.

For example, the IMS registration request may be an initial registration request. The initial registration request may include user information, terminal capability information, and the like.

The registration response message may be a registration normal response message, for example, a 401 message specified in the SIP interface protocol. The 401 message may include authentication information for requesting the UE to authenticate. The SIP interface protocol may be, for example, the Request For Comments (RFC) 3261 protocol.

The registration response message may also be a registration failure response message, such as a SIP error code. For example, the SIP error code may be a 403 message (i.e., indicating a prohibition), a 404 message (i.e., indicating that no user is found), a 408 message (i.e., indicating a request timeout), a 480 message (i.e., indicating temporary unavailability), a 503 message (i.e., indicating that a service is unavailable), a 504 message (i.e., indicating a server timeout), etc., as specified in the SIP interface protocol.

In the embodiment of the present application, when the UE 101 does not receive the registration response message, or when the UE 101 receives a registration failure response message (e.g., a SIP error code) from the IMS, it indicates that the UE 101 has not successfully registered the IMS. In addition, when the UE 101 receives the registration normal response message, it indicates that the IMS registration procedure is normal. Thereafter, the UE 101 may send a challenge (challenge) registration request to the IMS. The challenge registration request may include authentication information. Accordingly, the IMS may send a SIP 200OK message to the UE indicating that the IMS registration is successful. The UE may then conduct voice traffic.

Fig. 2A and fig. 2B are combined to describe a schematic diagram of a user interface before IMS registration is performed by a UE or after IMS registration fails and a schematic diagram of a user interface after IMS registration is successfully performed by the UE according to an embodiment of the present application. Fig. 2A is a schematic diagram illustrating a user interface of a UE before performing IMS registration or after IMS registration fails according to an embodiment of the present application. As shown in fig. 2A, before the UE performs IMS registration or when the IMS registration fails, the user interface of the UE does not display the successful IMS registration flag. Fig. 2B is a diagram illustrating a user interface after the UE successfully registers with the IMS according to an embodiment of the present application. As shown in fig. 2B, after the UE successfully registers the IMS, the user interface of the UE displays an indication that the IMS registration is successful. The flag may be HD (High Definition), voLTE, or VoNR, for example.

In the embodiment of the present application, when the UE does not successfully register to the IMS, the UE may reinitiate IMS registration. However, the UE does not initiate IMS registration an unlimited number of times. Specifically, the embodiment of the present application provides a method for suppressing a UE from frequently initiating an IMS registration. In the method, the UE may monitor whether a number of IMS registration failures reaches a threshold before a monitoring timer expires. When the number of IMS registration failures reaches a threshold before the monitoring timer expires, the UE may turn off IMS capabilities for a period of time and initiate IMS registration after the period of time. By the method, the power consumption increase caused by the fact that the UE frequently initiates the IMS registration can be avoided, the problem that the auxiliary card frequently occupies the resources of the main card due to the fact that the auxiliary card frequently initiates the IMS registration is avoided, and the influence on the internet surfing experience of the main card is avoided.

In the present embodiment, the UE 101 may be any terminal capable of talking to another terminal through a wireless communication network (e.g., a 5G network) and IMS. The UE 101 may have a Subscriber Identity Module (SIM) card interface for inserting the SIM card into the UE 101 and for making a call with another terminal through the SIM card. Alternatively, the UE 101 may talk to another terminal through an embedded SIM (eSIM) card. The UE 101 may be a mobile phone, a tablet computer, a computer with wireless transceiving function, a virtual reality device, an augmented reality device, a wireless device in industrial control, a wireless device in unmanned driving, a wireless device in telemedicine, a wireless device in smart grid, a wireless device in transportation safety, a wireless device in smart city, a wireless device in smart home, and the like.

FIG. 3 is a diagram illustrating a hardware structure of the UE 101 according to an embodiment of the present application. As shown in fig. 3, the UE 101 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a SIM card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the structure illustrated in FIG. 3 does not constitute a specific limitation on the UE 101. In another embodiment of the application, the UE 101 may include more or fewer components than illustrated, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units. For example, the Processor 110 may include an Application Processor (AP), a Modem (Modem), a Graphics Processor (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband Processor, and/or a Neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated in one or more processors.

The charging management module 140 is configured to receive charging input from a charger. The charger can be a wireless charger or a wired charger.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives an input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like.

The wireless communication function of the UE 101 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the UE 101 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc. applied on the UE 101.

The Wireless Communication module 160 may provide solutions for Wireless Communication applied to the UE 101, including Wireless Local Area Networks (WLANs) (e.g., wi-Fi Networks), bluetooth (bluetooth, BT), global Navigation Satellite System (GNSS), frequency Modulation (FM), near Field Communication (NFC), infrared, and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, in examples where the wireless communication module 160 provides bluetooth communication, the wireless communication module 160 may specifically be a bluetooth chip. The bluetooth chip may include one or more memories, one or more processors, and the like. The processor in the bluetooth chip can perform operations such as frequency modulation, filtering, operation, and judgment on the electromagnetic wave received by the antenna 2, and convert the processed signal into electromagnetic wave to be radiated by the antenna 2, that is, the processor 110 is not needed for processing.

The wireless communication module 160 or the processor 110 may perform the steps performed by the UE 101 in the method provided in the embodiment of the present application, which may specifically refer to the related description of the UE 101 in fig. 4 to 7, and are not described herein again.

The UE 101 implements display functions via the GPU, display screen 194, application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor.

The display screen 194 is used to display images or videos, etc. A series of Graphical User Interfaces (GUIs) may be displayed on the display screen 194 of the UE 101.

The UE 101 may implement the capture function through the ISP, camera 193, video codec, GPU, display screen 194, application processor, and the like.

The camera 193 is used to capture still images or video.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the storage capabilities of the UE 101.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications of the UE 101 and data processing by executing instructions stored in the internal memory 121.

The UE 101 can implement audio functions such as music playing, sound recording, etc. through the audio module 170, the speaker 170A, the headphones 170B, the microphone 170C, the headset interface 170D, and the application processor, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into the SIM card interface 195 or extracted from the SIM card interface 195 to make contact with and separate from the UE 101. The UE 101 may support 1 or N SIM card interfaces, with N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The SIM card interface 195 is also compatible with external memory cards. The UE 101 interacts with the network through the SIM card to implement functions such as communication and data communication.

On top of the above components, operating systems such as the hong meng operating system, the iOS operating system, the android operating system, the windows operating system, etc. run. Applications may be installed and run on the operating system. In other embodiments, there may be multiple operating systems running within the UE 101.

A method for suppressing a UE from frequently initiating IMS registration in case of a failure of the UE to register for IMS according to an embodiment of the present application will be described below with reference to fig. 4 to 6.

Fig. 4 is directed to a scenario in which the UE initiates IMS registration but does not receive a registration response message from the IMS. Fig. 4 is a flowchart illustrating a method 400 for suppressing frequent IMS registration initiation by a UE according to an embodiment of the present application. In the flow of fig. 4, the UE counts the number of IMS registration failures based on not receiving a registration response message from the IMS. The method 400 is performed by a UE and may include steps S401 to S413.

In step S401, the UE initiates IMS registration and starts a first timer.

For example, the UE initiating an IMS registration may be the UE sending an IMS registration request to the IMS through the access network and the core network. The IMS registration request may be the initial registration request described above.

The duration of the first timer may be a first preset duration, for example 128 seconds. The first timer is used for the UE to determine whether the registration response message is received within the first preset duration.

In step S402, the UE determines whether a registration response message is received before the first timer expires.

For example, the registration response message may be the registration normal response message described above, such as the SIP 401 message. The registration response message may also be a registration failure response message as described above, such as a SIP error code.

When the UE determines that the registration response message is received before the first timer expires, and the registration response message is a registration normal response message, the UE may perform step S403. When the UE determines that the registration response message is received before the first timer expires and the registration response message is a registration failure response message, the UE may return to perform step S401. When the UE determines that the registration response message is not received before the expiration of the first timer, the UE may perform step S404.

In step S403, the UE may send a challenge (challenge) registration request to the IMS according to a conventional IMS registration procedure. The challenge registration request may include authentication information. Accordingly, the IMS may send a SIP 200OK message to the UE indicating that the IMS registration is successful. Thereafter, the UE may conduct voice traffic. For example, the voice traffic may include incoming calls, outgoing calls, and the like.

In step S404, the UE updates the IMS registration failure number.

For example, the UE may increase the number of IMS registration failures by one.

In step S405, the UE determines whether the second timer is started. The second timer may be the supervision timer described above. The duration of the second timer may be a second preset duration, such as 600 seconds.

It should be understood that the UE may perform step S404 and then step S405, or perform step S405 and then step S404.

When the UE determines that the second timer is not started, the UE may perform step S406 and then perform step S407. When the UE determines that the second timer is started, the UE may directly perform step S407.

In step S406, the UE starts a second timer.

In step S407, the UE determines whether the first type trigger event occurs before the second timer expires.

The first type of trigger event may be used to trigger the UE to prematurely terminate the second timer before the second timer expires. For example, the first type of trigger event may include an event that the number of IMS registration failures reaches a threshold, IMS registration succeeds, power on, reboot, exit from airplane mode, or hot plug and unplug card. The reason why the IMS registration success event is generated may be that, when the UE determines in step S402 that the registration normal response message is not received before the first timer expires, the UE re-initiates IMS registration and the UE receives the registration normal response message from the IMS.

It should be understood that the events such as successful IMS registration, power-on, restart, exit from airplane mode, hot card insertion, etc. belong to active triggering events, and do not depend on the execution of steps S402 to S406.

It should be understood that the threshold described herein may be a preset positive integer, such as 4. The threshold is associated with a duration of the second timer. For example, the longer the duration of the second timer, the larger the threshold. Alternatively, the shorter the duration of the second timer, the smaller the threshold.

When the UE determines that the first type triggering event occurs before the second timer expires, the UE may perform step S408. When the UE determines that the first type triggering event does not occur before the second timer expires, the UE may initiate IMS registration again before the second timer expires, i.e., perform step S401. Alternatively, when the UE determines that the first type triggering event does not occur before the second timer expires, the UE may perform step S409 and then step S401 when the second timer expires. It should be understood that if the UE is able to determine that the first type of triggering event has not occurred before the second timer expires, then it indicates that the second timer has expired and is automatically terminated.

In step S408, the UE clears the IMS registration failure number and terminates the second timer.

For example, the UE may terminate the second timer by any method of terminating the timer. For example, the UE may clear the timer identification of the second timer to terminate the second timer.

In step S409, the UE clears the IMS registration failure number. After step S409, the UE may return to performing step S401.

After step S408, the UE may perform step S410, or may end the method 400, or may return to performing step S401. Specifically, in case that the first type of triggering event is that the number of IMS registration failures reaches a threshold, after step S408, the UE may perform step S410. In case the first type of triggering event is successful IMS registration, after step S408, the UE may end the method 400. In an example where the first type of trigger event is a power-on event, a reboot event, an exit from an airplane mode event, a hot-plug card event, etc., after step S408, the UE may return to performing step S401.

In step S410, the UE starts a third timer and disables the IMS capability before the third timer expires.

The duration of the third timer may be a third preset duration, for example 1800 seconds.

The UE disabling the IMS capability may be the UE turning off the IMS capability. For example, the UE may turn off the VoLTE switch or turn off the VoNR switch.

After step S410, the UE may perform step S411. In step S411, the UE determines whether a second type of trigger event occurs before the third timer expires.

The second type of triggering event may be used to trigger the UE to prematurely terminate the third timer before the third timer expires. For example, the second type of trigger event may include a power-on event, a restart event, an exit from an airplane mode event, a hot plug card event, a Public Land Mobile Network (PLMN) change event, a Tracking Area Update (TAU) event, and the like. Compared with the first type of trigger event, the second type of trigger event does not include that the number of times of IMS registration failure reaches a threshold value and IMS registration succeeds, and may include PLMN change and TAU.

When the UE determines that the second type of trigger event occurs before the third timer expires, the UE may perform step S412. When the UE determines that the second type of trigger event does not occur before the third timer expires, the UE may perform step S413.

In step S412, the UE terminates the third timer and enables IMS capabilities.

For example, the UE may terminate the third timer by any method of terminating a timer. For example, the UE may clear the timer flag of the third timer to terminate the third timer.

Further, the UE-enabled IMS capability may be to open a VoLTE switch or to open a VoNR switch.

After step S412, the UE may return to performing step S401.

In step S413, the UE enables the IMS capability after the third timer expires. The UE enables IMS capability in a similar manner as step S412.

Fig. 5 is directed to a scenario in which the UE initiates an IMS registration but receives a registration response failure message (e.g., a SIP error code) from the IMS. Fig. 5 is a flowchart illustrating a method 500 for suppressing frequent IMS registration initiation by a UE according to an embodiment of the present application. In the flow of fig. 5, the UE counts the number of IMS registration failures based on the SIP error code received from the IMS. The method 500 is performed by a UE and may include steps S501 to S512.

In step S501, the UE initiates IMS registration and starts a first timer. This step is similar to step S401 in fig. 4, and is not described again here.

In step S502, the UE receives a SIP error code from the IMS before the first timer expires.

For example, the SIP error code may be the 403 message (i.e., indicating barring), the 404 message (i.e., indicating no user is found), the 408 message (i.e., indicating request timeout), the 480 message (i.e., indicating temporary unavailability), the 503 message (i.e., indicating service unavailability), or the 504 message (i.e., indicating server timeout) described above, etc.

Then, the UE may perform steps S503 to S512. Steps S503 to S512 are similar to steps S404 to S413 in fig. 4, and are not described herein again.

In addition, in the embodiment of the present application, there are a plurality of SIP error codes, and each of them indicates a different meaning. According to an example of the embodiment of the present application, the UE may count the number of IMS registration failures for a specific SIP error code. For example, the UE may determine whether the received SIP error code is a specific SIP error code. And when the received SIP error code is the specific SIP error code, the UE counts the number of IMS registration failures according to the received SIP error code. When the received SIP error code is not a specific SIP error code, the UE does not count the number of IMS registration failures according to the received SIP error code.

It should be understood that the above-described "specific SIP error code" may include one or more SIP error codes, which is not limited by the embodiment of the present application.

For example, in an example in which the specific SIP error code includes the 403 message, when the UE receives one SIP error code, the UE parses the received SIP error code and determines whether the received SIP error code is the 403 message. When the received SIP error code is the 403 message, the UE updates the number of IMS registration failures, for example, adds one to the number of IMS registration failures. When the received SIP error code is not the 403 message, the UE does not update the number of IMS registration failures, e.g., does not increment the number of IMS registration failures by one.

For example, in an example in which the specific SIP error code includes 403 messages and 480 messages, when the UE receives one SIP error code, the UE parses the received SIP error code and determines whether the received SIP error code is a 403 message or a 480 message. When the received SIP error code is a 403 message or a 480 message, the UE updates the number of IMS registration failures, for example, increments the number of IMS registration failures by one. When the received SIP error code is neither a 403 nor a 480 message, the UE does not update the IMS registration failure number, e.g., does not increment the IMS registration failure number by one.

Further, according to an example of an embodiment of the present application, the UE may count the number of IMS registration failures for various SIP error codes, respectively, and set second timers corresponding to the various SIP error codes, respectively. For these second timers, the UE may prematurely terminate all second timers when a corresponding trigger event of the first type occurs before any of the second timers expires.

In this example, the UE may also set the same or different first type of trigger event for each second timer. For example, in the case that the first type of triggering event is that the number of IMS registration failures reaches a threshold, the UE may set the same or different threshold for each second timer.

A specific example is given below in connection with fig. 6. Fig. 6 is a flowchart illustrating a method 600 for suppressing frequent IMS registration initiation by a UE according to an embodiment of the present application. The method 600 is performed by a UE and may include steps S601 to S616.

In step S601, the UE initiates IMS registration and starts a first timer. This step is similar to step S501 above and will not be described herein again.

In step S602, the UE receives a SIP error code from the IMS before the first timer expires. This step is similar to step S502 above and will not be described herein again.

In case that the SIP error code is the 403 message, the UE may perform steps S603 to S605. In case the SIP error code is the 404 message, the UE may perform steps S606 to S608. In case that the SIP error code is the 480 message, the UE may perform steps S609 to S611.

In step S603, the UE updates the number of IMS registration failures corresponding to the 403 message. This step is similar to step S503 above and will not be described herein again.

Then, in step S604, the UE determines whether the second timer corresponding to the 403 message is started. When the UE determines that the second timer is not started, the UE may start the second timer and then perform step S605 (this case is not shown in fig. 6). When the UE determines that the second timer is started, the UE may directly perform step S605 (this case is already shown in fig. 6).

In step S605, the UE determines whether the first type trigger event occurs before the second timer expires. This step is similar to step S506 above and will not be described herein again.

Steps S606 to S608 are similar to steps S603 to S605, and are not described herein again.

Steps S609 to S611 are similar to steps S603 to S605, and are not described herein again.

When the determination result of any one of step S605, step S608, and step S611 is yes, the UE may perform step S612.

In step S612, the UE clears all IMS registration failure times, and terminates all second timers. Specifically, the UE clears the number of IMS registration failures corresponding to the 403 message, the number of IMS registration failures corresponding to the 404 message, and the number of IMS registration failures corresponding to the 480 message. And, the UE terminates the second timer corresponding to the 403 message, terminates the second timer corresponding to the 404 message, and terminates the second timer corresponding to the 480 message.

In the embodiment of the present application, the respective second timers are independent of each other. When a certain second timer is due earlier than other second timers and the first type of trigger event does not occur before the expiration, the UE may clear the IMS registration failure times corresponding to the second timer, and then initiate the IMS registration again, that is, similar to the step S409 and then step S401 in fig. 4. This does not affect other second timers, e.g., the UE does not prematurely terminate the other second timers when the second timer has expired first and no triggering event of the first type has occurred before the expiration. Then, the UE may perform steps S613 to S616. Steps S613 to S616 are similar to steps S509 to S512, and are not described herein again.

It should be understood that although the UE counts the number of IMS registration failures only for the 403 message, 404 message, 480 message and sets the second timer corresponding to the 403 message, 404 message, 480 message respectively in the method 600 shown in fig. 6, the UE may also count the number of IMS registration failures for other SIP error codes (e.g., 503 message, 504 message, etc.) and set the second timer corresponding to the other SIP error codes.

The durations of the second timers corresponding to the respective SIP error codes may be the same or different. In an example where the duration of each second timer is different, for example, the duration of the second timer corresponding to the 403 message may be 10 seconds, the duration of the second timer corresponding to the 404 message may be 8 seconds, and the duration of the second timer corresponding to the 480 message may be 12 seconds.

In addition, the first type of trigger event for each second timer may be the same or different. Fig. 6 shows an example in which the first type of trigger event is the same for each second timer. In an example where the first type of trigger event for each second timer is different, the threshold for each second timer may be different, assuming that the first type of trigger event is that the number of IMS registration failures reaches the threshold. For example, the threshold for the second timer corresponding to the 403 message may be 5 times, the threshold for the second timer corresponding to the 404 message may be 4 times, and the threshold for the second timer corresponding to the 480 message may be 6 times.

In the method 400 shown in fig. 4, the UE counts the number of IMS registration failures based on not receiving a registration response message from the IMS. In the method 500 shown in fig. 5 and the method 600 shown in fig. 6, the UE counts the number of IMS registration failures based on the SIP error code received from the IMS. However, during the repeated IMS registration initiation by the UE, the IMS registration failure may be manifested as the UE not receiving a registration response message from the IMS, or may be manifested as the UE receiving a SIP error code from the IMS. According to an example of the embodiment of the present application, the UE may count the number of IMS registration failures based on the absence of the registration response message received from the IMS and the SIP error code received from the IMS. For example, when the UE initiates IMS registration for the first time, the IMS registration failure is represented by the UE not receiving a registration response message from the IMS, and the UE may add one to the number of IMS registration failures. When the UE initiates IMS registration for the second time, the IMS registration failure is represented by that the UE receives an SIP error code from the IMS, and then the UE may also add one to the number of IMS registration failure times.

A specific example is given below in conjunction with fig. 7. Fig. 7 is a flowchart illustrating a method 700 for suppressing a UE from frequently initiating an IMS registration according to an embodiment of the present application. The method 700 is performed by a UE and may include steps S701 through S713.

In step S701, the UE initiates IMS registration and starts a first timer. This step is similar to step S401 in fig. 4, and is not described again here.

In step S702, the UE determines whether a registration response message is received before the first timer expires.

When the UE determines that the registration response message is received before the first timer expires, and the registration response message is a registration normal response message, the UE may perform step S703. When the UE determines that the registration response message is received before the first timer expires, and the registration response message is a registration failure response message, the UE may perform step S704. When the UE determines that the registration response message is not received before the first timer expires, the UE may perform step S704.

It should be understood that, when the UE determines that the registration response message is received before the first timer expires, and the registration response message is a registration failure response message, the UE may further return to perform step S701, that is, the UE may initiate IMS registration again (not shown in the figure).

In step S703, the UE may send a challenge (challenge) registration request to the IMS according to a conventional IMS registration procedure. Accordingly, the IMS may send a SIP 200OK message to the UE indicating that the IMS registration is successful. Thereafter, the UE may conduct voice traffic.

In step S704, the UE updates the IMS registration failure number.

In the embodiment of the present application, if the UE does not receive the registration response message before the first timer expires, the UE may update the IMS registration failure times, or if the UE receives the registration failure response message before the first timer expires, the UE may also update the IMS registration failure times.

Then, the UE may perform steps S705 to S713. Steps S705 to S713 are similar to steps S405 to S413 in fig. 4, respectively, and are not described herein again.

In the embodiment of the present application, the registration failure result of the UE initiating registration with the IMS includes two types, that is, a registration failure response message (a registration failure response message, for example, a SIP 403 message, a SIP 404 message, a SIP 408 message, a SIP 480 message, a SIP 503 message, a SIP 504 message, etc.) is received by the UE before the first timer expires, and a registration response message (a registration failure response message or a registration normal response message) is not received by the UE before the first timer expires. When the registration failure result of the UE initiating registration with the IMS is that the UE does not receive a registration response message before the first timer expires, the UE may equate such registration failure result with the registration failure result that the UE received the registration failure response message and that the message is a SIP 408 message (i.e., indicating a request timeout).

An embodiment of the present application further provides a computer-readable storage medium, which includes instructions, and when the instructions are executed on an electronic device, the electronic device is caused to execute the relevant method steps of the UE in fig. 4 to 7, so as to implement the method in the foregoing embodiment.

Embodiments of the present application further provide a computer program product containing instructions, which when run on an electronic device, cause the electronic device to perform the relevant method steps of the UE in fig. 4 to 7, so as to implement the method in the foregoing embodiments.

An embodiment of the present application further provides a terminal, where the terminal includes a processor and a memory, where the memory is configured to store computer program codes, and the computer program codes include computer instructions, and when the processor executes the computer instructions, the terminal executes the relevant method steps of the UE in fig. 4 to 7, so as to implement the method in the foregoing embodiment. The terminal may be an integrated circuit IC or a system on chip SOC. The integrated circuit can be a general integrated circuit, a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC).

By the method, the terminal, the computer program product and the computer readable storage medium of the embodiment of the application, the power consumption increase caused by the frequent initiation of the IMS registration by the UE can be avoided, the resources of the main card are prevented from being frequently preempted by the auxiliary card due to the frequent initiation of the IMS registration by the auxiliary card, and the influence on the internet surfing experience of the main card is avoided.

In the several embodiments provided in the present application, 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 modules or units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple 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 application 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 may be implemented in the form of hardware, or may also be implemented in the 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 embodiment essentially or partially contributes to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute all or part of the steps of the method described in the embodiments. And the aforementioned storage medium includes: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for a user equipment to initiate an internetworking protocol multimedia subsystem, IMS, registration, comprising:

initiating a registration with the IMS;

receiving a registration failure response message from the IMS;

updating IMS registration failure times according to the registration failure response message, and starting a monitoring timer;

receiving a registration failure response message for re-registration from the IMS after re-registration is initiated to the IMS each time from the start of the monitoring timer to the expiration of the monitoring timer;

updating the IMS registration failure times according to the registration failure response message aiming at the re-registration;

disabling an IMS capability of the user equipment when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires.

2. The method of claim 1, wherein the first and second light sources are selected from the group consisting of a red light source, a green light source, and a blue light source,

wherein initiating registration with the IMS comprises:

sending an IMS registration request to the IMS, and starting a first timer;

wherein receiving a registration failure response message from the IMS comprises:

receiving a registration failure response message from the IMS before expiration of the first timer.

3. The method of claim 1, when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires, the method further comprising:

clearing the IMS registration failure times;

the supervision timer is terminated.

4. The method of claim 1, further comprising:

when the user equipment receives a user instruction before the monitoring timer expires to perform at least one of: and when the mobile terminal is started, restarted, exits from the flight mode or is plugged and unplugged in a hot mode, the mobile terminal initiates re-registration to the IMS.

5. The method of any of claims 1 to 4, wherein disabling IMS capabilities of the user equipment comprises:

starting a third timer and disabling IMS capabilities of the user equipment before expiration of the third timer.

6. The method of claim 5, further comprising:

when a public land mobile network of the user equipment changes before the third timer expires, or a tracking area of the user equipment is updated, or the user equipment receives a user instruction to perform at least one of: and when the user equipment is started, restarted, exits from the flight mode or is plugged in and unplugged from the card in a hot mode, the third timer is terminated, and the IMS capability of the user equipment is started.

7. The method of claim 5, further comprising:

when the public land mobile network of the user equipment is not changed before the third timer expires, or the tracking area of the user equipment is not updated, or the user equipment does not receive a user instruction to perform at least one of: and starting the IMS capability of the user equipment after the third timer expires when starting, restarting, exiting the flight mode or hot plugging and unplugging the card.

8. The method of claim 1, wherein the first and second light sources are selected from the group consisting of a red light source, a green light source, and a blue light source,

wherein updating the number of times of IMS registration failure according to the registration failure response message, and starting the monitoring timer comprises:

updating IMS registration failure times corresponding to the type of the registration failure response message according to the type of the registration failure response message, and starting a monitoring timer corresponding to the type of the registration failure response message;

wherein updating the number of IMS registration failures according to the registration failure response message for re-registration comprises:

updating the IMS registration failure times corresponding to the type of the registration failure response message according to the type of the registration failure response message aiming at the re-registration;

wherein disabling IMS capabilities of the user equipment when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires comprises:

and when the IMS registration failure times corresponding to any monitoring timer exceed a preset threshold before any monitoring timer expires, forbidding the IMS capability of the user equipment.

9. The method according to claim 8, when the number of IMS registration failures corresponding to any one of the monitoring timers before the expiration of the any one of the monitoring timers exceeds a preset threshold, the method further comprising:

clearing the number of times of IMS registration failure;

the respective watchdog timer is terminated.

10. The method of claim 8, wherein the registration failure response message is a Session Initiation Protocol (SIP) error code, the type of the registration failure response message is a type of SIP error code, the type of SIP error code comprises at least one of: SIP 403 messages, SIP 404 messages, SIP 408 messages, SIP 480 messages, SIP 503 messages, SIP 504 messages.

11. A method for a user equipment to initiate an internetworking protocol multimedia subsystem, IMS, registration, comprising:

initiating registration to the IMS and starting a first timer;

determining a registration failure result for the registration, wherein the registration failure result includes that the user equipment receives a registration failure response message before the first timer expires, or that the user equipment does not receive a registration failure response message or a registration normal response message before the first timer expires;

updating the IMS registration failure times according to the registration failure result aiming at the registration, and starting a monitoring timer;

determining a registration failure result for re-registration after re-registration is initiated to the IMS each time from the start of the monitoring timer to the expiration of the monitoring timer;

updating the IMS registration failure times according to the registration failure result aiming at the re-registration;

12. A user equipment, comprising:

a memory for storing computer program code, the computer program code comprising computer instructions; and

a processor for causing the user equipment to perform the method of any one of claims 1 to 11 when the computer instructions are executed.