WO2023147754A1

WO2023147754A1 - Method for user equipment to initiate ims registration and corresponding user equipment

Info

Publication number: WO2023147754A1
Application number: PCT/CN2023/070882
Authority: WO
Inventors: 陈拴锋; 孙敏; 张忠理
Original assignee: 荣耀终端有限公司
Priority date: 2022-02-07
Filing date: 2023-01-06
Publication date: 2023-08-10
Also published as: CN115568011A; CN115568011B

Abstract

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

Description

A method for user equipment to initiate IMS registration and corresponding user equipment

This application claims the priority of the Chinese patent application with the application number 202210116441.2 and the title of the invention "a method for user equipment to initiate IMS registration and corresponding user equipment" submitted to the State Intellectual Property Office of China on February 07, 2022 , the entire contents of which are incorporated in this application by reference.

technical field

The present application relates to the field of wireless communication, and specifically relates to a method for a user equipment (User Equipment, UE) to initiate an Internet-protocol Multimedia Subsystem (Internet-protocol Multimedia Subsystem, IMS) registration and a corresponding user equipment.

Background technique

Starting from the long-term evolution technology (Long Time Evolution, LTE), a voice implementation solution for carrying voice services on the IP network through IMS is proposed, that is, VoLTE (Voice over LTE) technology. In the 5G (also called New Radio (NR)) wireless communication system, a method of continuing to carry voice services on the IP network is proposed, and the voice service is realized through the 5G network and IMS, that is, VoNR (Voice over NR) technology. After the UE successfully registers on the IMS, it can implement voice services through these technologies.

However, when the UE initiates IMS registration, the IMS may not be able to respond to the IMS registration request sent by the UE due to a network anomaly, or the IMS may feed back a Session Initiation Protocol (Session Initiation Protocol, SIP) error code (such as , 403 message, 480 message, etc.). In this situation, the UE can re-initiate the IMS registration, but the registration will not be successful due to network abnormality. Currently, the communication system does not limit the number of times the UE re-initiates IMS registration. Therefore, the UE may frequently initiate IMS registration, which will increase the power consumption of the UE.

In addition, after the UE receives the 403 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 restricted state. In addition, after the IMS registration process ends, the UE enters an idle state, and usually the network releases a radio resource control (Radio Resource Control, RRC) connection for the UE. However, when the network is abnormal, the network does not release the RRC connection or the speed of releasing the RRC is slow. In order to facilitate the release of the RRC connection, the UE can actively initiate a Tracking Area Update (TAU). However, the UE actively initiates the TAU to cause the UE to escape from the IMS registration restriction state. The escaped UE will initiate IMS registration again, then receive a 403 message, and initiate a TAU because the network does not release the RRC connection or the speed of releasing the RRC is slow. Such infinite cycles will increase the power consumption of the UE.

In addition, for Dual Sim Dual Standby (DSDS) mobile phones, frequent initiation of IMS registration by the secondary card will cause the secondary card to frequently seize the resources of the primary card, thus affecting the online experience of the primary card.

Contents of the invention

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

An aspect of the embodiments of the present application provides a method for a user equipment to initiate a registration with an Inter-Network Interconnection Protocol Multimedia Subsystem IMS, including: initiating registration with the IMS; receiving a registration failure response message from the IMS; according to the The registration failure response message updates the number of IMS registration failures, and starts a monitoring timer; from the start of the monitoring timer to the expiration of the monitoring timer, after each re-registration is initiated to the IMS, a response to A registration failure response message for re-registration; update the number of IMS registration failures according to the registration failure response message for re-registration; when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires, disable the The IMS capability of the user equipment.

According to an example of the present application, initiating registration to the IMS includes: sending an IMS registration request to the IMS, and starting a first timer; receiving a registration failure response message from the IMS includes: at the first timing Receive a registration failure response message from the IMS before the device expires.

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 number of IMS registration failures; terminating the monitoring timer device.

According to an example of the present application, the method further includes: when the user equipment receives a user instruction to perform at least one of the following operations before the monitoring timer expires: power on, restart, exit the airplane mode, or hot-swap a card , initiate re-registration to the IMS.

According to an example of the present application, disabling the IMS capability of the user equipment includes: starting a third timer, and disabling the IMS capability of the user equipment before the third timer expires.

According to an example of the present application, the method further includes: when the public land mobile network of the user equipment is changed before the third timer expires, or the tracking area of the user equipment is updated, or the user equipment receives When receiving an instruction from the user to perform at least one of the following operations: when starting up, restarting, exiting the airplane mode, or hot-swapping a card, terminate the third timer and enable the IMS capability of the user equipment.

According to an example of the present application, the method further includes: 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 When the device does not receive a user instruction to perform at least one of the following operations: when starting up, restarting, exiting the airplane mode, or hot-swapping a card, enable the IMS capability of the user device after the third timer expires.

According to an example of the present application, where the number of IMS registration failures is updated according to the registration failure response message, starting the monitoring timer includes: updating the IMS registration corresponding to the type of the registration failure response message according to the type of the registration failure response message failure times, and start a monitoring timer corresponding to the type of the registration failure response message; where updating the IMS registration failure times according to the registration failure response message for re-registration includes: according to the type of the registration failure response message for re-registration Updating the number of IMS registration failures corresponding to the type of the registration failure response message; wherein when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires, disabling the IMS capability of the user equipment includes: when When the number of IMS registration failures corresponding to any monitoring timer exceeds a preset threshold before the monitoring timer corresponding to the type of any registration failure response message expires, the IMS capability of the user equipment is disabled.

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 IMS registration failures to zero; terminating each Watchdog timer.

According to an example of the present application, 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, and the type of the SIP error code includes at least one of the following: SIP 403 message, SIP 404 message, SIP 408 message, SIP 480 message, SIP 503 message, SIP 504 message.

Another aspect of the embodiments of the present application provides a method for a user equipment to initiate a registration with an Inter-Network Interconnection Protocol Multimedia Subsystem IMS, including: initiating registration with the IMS, and starting a first timer; registration failure result, wherein the registration failure result includes that the user equipment receives a registration failure response message before the first timer expires, or the user equipment does not receive a registration failure response message before the first timer expires Receive a registration failure response message or a normal registration response message; update the number of IMS registration failures according to the registration failure result for the registration, and start the monitoring timer; from the start of the monitoring timer to before the expiration of the monitoring timer, every After initiating re-registration to the IMS for the first time, determine the registration failure result for re-registration; update the number of IMS registration failures according to the registration failure result for re-registration; when the IMS registration fails before the monitoring timer expires When the number of times exceeds the preset threshold, the IMS capability of the user equipment is disabled.

Another aspect of the embodiments of the present application provides a user equipment, including: a memory for storing computer program codes, the computer program codes including computer instructions; and a processor for making the The user equipment executes the above method.

Through the method and user equipment of the embodiment of the present application, it is possible to avoid the increase of power consumption caused by the UE frequently initiating IMS registration, avoid the secondary card frequently preempting the resources of the primary card due to the frequent initiation of IMS registration by the secondary card, and avoid affecting the primary card. The online experience of the card, etc.

Description of drawings

The above and other purposes, features and advantages of the present application will become more apparent through specific descriptions in conjunction with the accompanying drawings. The accompanying drawings are incorporated in and constitute a part of this specification, and together with the specification, serve to explain the principles of the application. In the drawings, like drawing reference numerals refer to like or similar elements, features, and structures, wherein:

FIG. 1 is a schematic diagram of a wireless communication system in which an embodiment of the present application can be applied;

FIG. 2A shows a schematic diagram of a user interface of a UE before IMS registration or IMS registration failure according to an embodiment of the present application;

FIG. 2B shows a schematic diagram of a user interface after the UE successfully registers with the IMS according to 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 schematic flowchart of a method for suppressing frequent initiation of IMS registration by a UE according to an embodiment of the present application;

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

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

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

Detailed ways

The terms "first", "second" and "third" in the specification, claims and description of the drawings of this application are used to distinguish different objects, rather than to limit a specific order.

In the embodiments of the present application, words such as "exemplary" or "for example" are used for example, illustration or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application shall not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner.

The terms used in the embodiments of the application are only used to explain the specific embodiments of the application, and are not intended to limit the application. The embodiments of the application will be described in detail below in conjunction with 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 the embodiments of the present application can be applied. The wireless communication system may be LTE, or a 5G wireless communication system, or a new communication system that will appear in future wireless communication development. As long as the wireless communication system adopts IMS as a voice implementation solution, the wireless communication system can apply the embodiments of the present application.

As shown in Figure 1, a wireless communication system 100 includes a UE 101, an access network device 102 providing an LTE network for the UE 101, an access network device 103 providing 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 Inquiry Call Session Control Function (Interrogating-Call Session Control Function, I-CSCF), a Serving-Call Session Control Function (Serving-Call Session Control Function, S-CSCF) entity, and home subscriber server (Home Subscriber Server, HSS).

The P-CSCF entity is the first connection point from the access network to the IMS, and all session messages initiated from and terminated by the IMS-capable UE must be forwarded through the P-CSCF entity. The P-CSCF entity can be used to forward the IMS registration request from the UE to the S-CSCF entity, and forward the registration response message to the UE.

The I-CSCF entity can be connected to the S-CSCF entity and the P-CSCF entity, and is used to provide the entrance to the home network for the UE. During the IMS registration process, the P-CSCF entity can forward the IMS registration request from the UE to the I-CSCF entity, and the I-CSCF entity can query the HSS in the IMS, and select an S-CSCF entity for the UE. During the call process, the call message to the IMS network is first routed to the I-CSCF, and the I-CSCF entity can query the address information of the S-CSCF entity registered by the user for the UE through the HSS in the IMS, and then route the message to S-CSCF.

The S-CSCF entity is the control core of the IMS, providing functions such as session control and registration for the UE. The S-CSCF entity is used to receive the IMS registration request forwarded by the P-CSCF entity, and cooperate with the HSS to authenticate the UE. After the S-CSCF determines that the authentication is passed, it obtains the subscription information of the UE from the HSS. The S-CSCF entity is also used to connect with each application server based on the ISC interface, and the S-CSCF entity is also used to trigger the application server to perform an operation, and route the request of the UE to the corresponding application server.

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

It should be understood that although the wireless communication system 100 shown in FIG. 1 only includes 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 interfaces. network access equipment. 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 can generate an IMS registration request when events such as power-on, restart, exit from airplane mode, hot-plug card, or IMS registration failure occur. Then, the UE 101 can send the IMS registration request to the P-CSCF entity in the IMS 105 through the access network and the core network. The UE 101 can also receive a registration response message from the IMS 105 through the core network and the access network.

For example, an 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 normal registration response message, for example, a 401 message specified in the SIP interface protocol. The 401 message may include authentication information, and is used to require the UE to perform authentication. The SIP interface protocol may be, for example, a request for comments (Request For Comments, RFC) 3261 protocol.

In addition, the registration response message may also be a registration failure response message, such as a SIP error code. For example, the SIP error code can be a 403 message (that is, prohibition), a 404 message (that is, the user cannot be found), a 408 message (that is, the request is timed out), a 480 message (that is, the temporary unavailable) specified in the SIP interface protocol. ), 503 message (that is, the service is unavailable), 504 message (that is, the server timed out), etc.

In this embodiment of the application, when the UE 101 does not receive a registration response message, or when the UE 101 receives a registration failure response message (for example, a SIP error code) from the IMS, it indicates that the UE 101 has not successfully registered with the IMS. In addition, when UE 101 receives the registration normal response message, it indicates that the IMS registration process is normal. Thereafter, UE 101 may send a challenging registration request to the IMS. The challenge registration request may include authentication information. Correspondingly, the IMS can send a SIP 200 OK message to the UE to indicate that the IMS registration is successful. Then, the UE can perform voice services.

A schematic diagram of a user interface of a UE before IMS registration or IMS registration failure and a user interface of a UE after successful IMS registration according to an embodiment of the present application will be described below with reference to FIG. 2A and FIG. 2B . Fig. 2A shows a schematic diagram of a user interface of a UE before IMS registration or IMS registration failure 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 will not display the sign of successful IMS registration. Fig. 2B shows a schematic diagram of 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 with the IMS, the user interface of the UE displays a sign indicating that the IMS registration is successful. The flag may be, for example, HD (High Definition, high definition), or VoLTE, or VoNR, and the like.

In this embodiment of the application, when the UE fails to register with the IMS, the UE may re-initiate the IMS registration. However, the UE will not initiate IMS registration an unlimited number of times. Specifically, the embodiment of the present application proposes a method for preventing the UE from frequently initiating IMS registration. In this method, the UE may monitor whether the number of IMS registration failures reaches a threshold before the monitoring timer expires. When the number of IMS registration failures reaches the threshold before the monitoring timer expires, the UE may disable the IMS capability for a period of time, and initiate IMS registration after the period of time. Through the method of the embodiment of this application, it is possible to avoid the increase of power consumption caused by the UE frequently initiating IMS registration, avoid the secondary card frequently preempting the resources of the primary card due to the frequent initiation of IMS registration by the secondary card, and avoid affecting the Internet access of the primary card experience etc.

In this embodiment of the application, UE 101 may be any terminal capable of talking with another terminal through a wireless communication network (for example, a 5G network) and IMS. The UE 101 may have a Subscriber Identification Module (Subscriber Identification Module, SIM) card interface so that the SIM card is inserted into the UE 101, and the SIM card is used to communicate with another terminal. Alternatively, the UE 101 can communicate with another terminal through an embedded SIM (embedded SIM, eSIM) card. UE 101 can be mobile phone, tablet computer, computer with wireless transceiver function, virtual reality device, augmented reality device, wireless device in industrial control, wireless device in unmanned driving, wireless device in telemedicine, wireless device in smart grid Wireless devices, wireless devices in transportation security, wireless devices in smart cities, wireless devices in smart homes, etc.

FIG. 3 is a schematic diagram of a hardware structure of UE 101 according to an embodiment of the present application. As shown in FIG. 3, UE 101 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (universal serial bus, USB) interface 130, charging management module 140, power management module 141, battery 142, Antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, Display screen 194, and SIM card interface 195 etc. The sensor module 180 may include a pressure sensor 180A, a gyro 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, bone conduction sensor 180M, etc.

It can be understood that the structure shown in FIG. 3 does not constitute a specific limitation on UE 101. In another embodiment of the present application, the UE 101 may include more or fewer components than shown, or combine certain components, or separate certain components, or arrange different components. The illustrated components may be realized 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 (Application Processor, AP), a modem (Modem), a graphics processor (Graphics Processing Unit, GPU), an image signal processor (Image Signal Processor, ISP), a controller, a video encoder A decoder, a digital signal processor (Digital Signal Processor, DSP), a baseband processor, and/or a neural network processor (Neural-network Processing Unit, NPU), etc. The different processing units can be independent devices or integrated in one or more processors.

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

The power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 . The power management module 141 receives the input of the battery 142 and/or the charging management module 140 to supply power for the processor 110 , the internal memory 121 , the display screen 194 , the camera 193 and the wireless communication module 160 .

The wireless communication function of UE 101 can be realized by antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem and baseband processor, etc.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in UE 101 can be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the UE 101.

The wireless communication module 160 can provide wireless local area network (Wireless Local Area Networks, WLAN) (such as Wi-Fi network), Bluetooth (Blue Tooth, BT), global navigation satellite system (Global Navigation Satellite System, GNSS) applied on UE 101. ), frequency modulation (Frequency Modulation, FM), near field communication technology (Near Field Communication, NFC), infrared technology and other wireless communication solutions. 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 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate and amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, in an example 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, calculation, and judgment on the electromagnetic waves received via the antenna 2, and convert the processed signals into electromagnetic waves and radiate them through the antenna 2, that is, without the processor 110 for processing.

The wireless communication module 160 or the processor 110 may execute the steps performed by the UE 101 in the method proposed in the embodiment of the present application. For details, please refer to the relevant description of the UE 101 in FIGS. 4-7 , which will not be repeated here.

The UE 101 realizes the display function through the GPU, the display screen 194 and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor.

The display screen 194 is used to display images or videos and the like. A series of Graphical User Interfaces (Graphical User Interface, GUI) can be displayed on the display screen 194 of the UE 101.

The UE 101 can realize the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor.

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, so as to expand the storage capacity of the UE 101.

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

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

The SIM card interface 195 is used for connecting a SIM card. The SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to realize contact and separation with the UE 101. UE 101 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 195 can support Nano SIM card, Micro SIM card, 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. UE 101 interacts with the network through the SIM card to realize functions such as calling and data communication.

On the above components, there are operating systems running, such as Hongmeng operating system, iOS operating system, Android operating system, Windows operating system and so on. Applications can be installed and run on this operating system. In other embodiments, there may be multiple operating systems running in the UE 101.

The method for suppressing the UE from frequently initiating IMS registration according to the embodiment of the present application will be described below in conjunction with FIG. 4 to FIG. 6 when the UE fails to register with the IMS.

Figure 4 is directed to the scenario where the UE initiates IMS registration but does not receive a registration response message from the IMS. Fig. 4 is a schematic flowchart of a method 400 for suppressing frequent initiation of IMS registration by a UE according to an embodiment of the present application. In the process 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 executed by the UE, and may include steps S401 to S413.

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

For example, the IMS registration initiated by the UE may be that the UE sends 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, such as 128 seconds. The first timer is used by the UE to determine whether a registration response message is received within the first preset time period.

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 a SIP 401 message. The registration response message may also be the registration failure response message 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 normal registration 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 step S401. When the UE determines that no registration response message is received before the first timer expires, the UE may execute step S404.

In step S403, the UE may send a challenging registration request to the IMS according to a conventional IMS registration process. The challenge registration request may include authentication information. Correspondingly, the IMS can send a SIP 200 OK message to the UE to indicate that the IMS registration is successful. Afterwards, the UE can perform voice services. For example, the voice service may include incoming calls, outgoing calls, and so on.

In step S404, the UE updates the number of IMS registration failures.

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 watchdog 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 first perform step S404 and then perform step S405, or first perform step S405 and then perform step S404.

When the UE determines that the second timer is not started, the UE may first 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 of trigger event occurs before the second timer expires.

The first type of trigger event may be used to trigger the UE to terminate the second timer in advance before the second timer expires. For example, the first type of triggering events may include events such as the number of IMS registration failures reaching a threshold, IMS registration success, power-on, restart, exiting the airplane mode, or hot-swapping a card. The cause of the IMS registration success event may be that after 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 receives the registration normal response message from the IMS.

It should be understood that events such as successful IMS registration, booting, restarting, exiting the airplane mode, and hot-swapping cards are active triggering events, which do not depend on the execution of steps S402 to S406.

It should be understood that the threshold described here may be a preset positive integer, such as 4. The threshold is associated with the 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 of triggering event occurs before the second timer expires, the UE may execute step S408. When the UE determines that the first type of triggering event does not occur before the second timer expires, the UE may initiate IMS registration again before the second timer expires, that is, perform step S401. Alternatively, when the UE determines that the first type of triggering event does not occur before the second timer expires, the UE may first perform step S409 and then perform step S401 when the second timer expires. It should be understood that if the UE can determine that the first type of triggering event does not occur before the second timer expires, it indicates that the second timer has expired and is automatically terminated.

In step S408, the UE clears the number of IMS registration failures to zero, and terminates the second timer.

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

In step S409, the UE clears the number of IMS registration failures to zero. After step S409, the UE may return to step S401.

After step S408, the UE may execute step S410, or may end the method 400, or may return to execute step S401. Specifically, in the 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 execute step S410. In the case that the first type of trigger event is IMS registration success, after step S408, the UE may end the method 400. In the example where the first type of triggering event is an event such as power-on, restart, exiting the airplane mode, hot-swapping card, etc., after step S408, the UE may return to execute 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, such as 1800 seconds.

The disabling of the IMS capability by the UE may be that the UE disables 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 the second type of triggering event occurs before the third timer expires.

The second type of triggering event may be used to trigger the UE to terminate the third timer in advance before the third timer expires. For example, the second type of trigger events may include events such as power-on, restart, exit from airplane mode, hot-swap card, public land mobile network (Public Land Mobile Network, PLMN) change, tracking area update (Tracking Area Update, TAU) and other events. Compared with the first type of trigger event, the second type of trigger event does not include IMS registration failure times reaching the threshold and IMS registration success, but may include PLMN change and TAU.

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

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

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

In addition, enabling the IMS capability of the UE may be turning on the VoLTE switch or turning on the VoNR switch.

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

In step S413, the UE enables the IMS capability after the third timer expires. The manner in which the UE enables the IMS capability is similar to step S412.

FIG. 5 is directed to the scenario where the UE initiates IMS registration but receives a registration response failure message (such as a SIP error code) from the IMS. Fig. 5 is a schematic flowchart of a method 500 for suppressing frequent initiation of IMS registration by a UE according to an embodiment of the present application. In the process 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 executed by the 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 will not be repeated 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 can be the 403 message described above (that is, forbidden), the 404 message (that is, the user cannot be found), the 408 message (that is, the request timed out), the 480 message (that is, the temporary unavailable), 503 message (that is, the service is unavailable), or 504 message (that is, the server timed out), etc.

Then, the UE may perform step S503 to step S512. Step S503 to step S512 are respectively similar to step S404 to step S413 in FIG. 4 , and will not be repeated here.

In addition, in the embodiment of the present application, there are many kinds of SIP error codes, each of which represents 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. When the received SIP error code is a specific SIP error code, the UE counts the times 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 will not count the number of IMS registration failures according to the received SIP error code.

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

For example, in an example where the specific SIP error code includes a 403 message, when the UE receives a SIP error code, the UE parses the received SIP error code and determines whether the received SIP error code is a 403 message. When the received SIP error code is a 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 a 403 message, the UE does not update the number of IMS registration failures, for example, does not add one to the number of IMS registration failures.

For example, in the example where the specific SIP error code includes a 403 message and a 480 message, when the UE receives a SIP error code, the UE parses the received SIP error code, and judges whether the received SIP error code is a 403 message or 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, adds one to the number of IMS registration failures. When the received SIP error code is neither a 403 message nor a 480 message, the UE does not update the number of IMS registration failures, for example, does not add one to the number of IMS registration failures.

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

In this example, the UE may also set the same or different first-type trigger events for each second timer. For example, in a situation where 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 thresholds for each second timer.

A specific example is given below in conjunction with FIG. 6 . Fig. 6 is a schematic flowchart of a method 600 for suppressing frequent initiation of IMS registration by a UE according to an embodiment of the present application. The method 600 is executed by the 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 repeated here.

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 repeated here.

In the case that the SIP error code is a 403 message, the UE may perform steps S603 to S605. In the case that the SIP error code is a 404 message, the UE may perform steps S606 to S608. In the case that the SIP error code is a 480 message, the UE may perform step S609 to step 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 repeated here.

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 first start the second timer and then perform step S605 (this situation is not shown in FIG. 6 ). When the UE determines that the second timer is started, the UE may directly perform step S605 (this situation has been shown in FIG. 6 ).

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

Steps S606 to S608 are similar to steps S603 to S605 and will not be repeated here.

Steps S609 to S611 are similar to steps S603 to S605 , and will not be repeated here.

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

In step S612, the UE clears all IMS registration failure times and terminates all second timers. Specifically, the UE clears the IMS registration failure times corresponding to the 403 message, the IMS registration failure times corresponding to the 404 message, and the IMS registration failure times 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, each second timer is independent of each other. When a certain second timer expires earlier than other second timers and the first type of trigger event does not occur before the expiration, the UE may clear the number of IMS registration failures corresponding to the second timer to zero, and then Initiating the IMS registration again is similar to first performing step S409 in FIG. 4 and then performing step S401. This will not affect other second timers, for example, when the second timer expires first and the first type of trigger event does not occur before the expiration, the UE will not terminate other second timers in advance. Then, the UE may perform step S613 to step S616. Steps S613 to S616 are similar to steps S509 to S512 above, and will not be repeated here.

It should be understood that although in the method 600 shown in FIG. 6 , the UE only counts the number of IMS registration failures for the 403 message, 404 message, and 480 message, and sets the second timer corresponding to the 403 message, 404 message, and 480 message respectively, but The UE may also count IMS registration failure times for other SIP error codes (for example, 503 messages or 504 messages, etc.), and set a second timer corresponding to the other SIP error codes.

In addition, 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, and the duration of the second timer corresponding to the 404 message may be 8 seconds , the duration of the second timer corresponding to the 480 message may be 12 seconds.

In addition, the first type of trigger events for each second timer may be the same or different. FIG. 6 shows an example in which the first type of trigger events for each second timer are the same. In an example where the first type of triggering event for each second timer is different, assuming that the first type of triggering event is that the number of IMS registration failures reaches a threshold, then the threshold for each second timer may be different. For example, the threshold for the second timer corresponding to the 403 message can be 5 times, the threshold for the second timer corresponding to the 404 message can be 4 times, and the threshold for the second timer corresponding to the 480 message can 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 process of the UE repeatedly initiating IMS registration, IMS registration failure may be manifested as the UE not receiving a registration response message from the IMS, or 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 not receiving a registration response message from the IMS and a SIP error code received from the IMS. For example, when the UE initiates IMS registration for the first time, if the IMS registration failure means that the UE does not receive a registration response message from the IMS, the UE may add one to the number of IMS registration failures. When the UE initiates IMS registration for the second time, if the IMS registration failure is represented by the UE receiving a SIP error code from the IMS, the UE may also increase the number of IMS registration failures by one.

A specific example is given below in conjunction with FIG. 7 . Fig. 7 is a schematic flowchart of a method 700 for suppressing frequent initiation of IMS registration by a UE according to an embodiment of the present application. The method 700 is executed by the UE, and may include steps S701 to 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 will not be repeated 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 normal registration 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 no registration response message is 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 return to step S701, that is, the UE may initiate IMS registration again (not shown in the figure) Shows).

In step S703, the UE may send a challenging registration request to the IMS according to a conventional IMS registration procedure. Correspondingly, the IMS can send a SIP 200 OK message to the UE to indicate that the IMS registration is successful. Afterwards, the UE can perform voice services.

In step S704, the UE updates the number of IMS registration failures.

In this embodiment of the application, if the UE does not receive the registration response message before the first timer expires, the UE will update the number of IMS registration failures, or if the registration failure response message is received before the first timer expires, the UE will Update the number of IMS registration failures.

Then, the UE may perform step S705 to step S713. Step S705 to step S713 are respectively similar to step S405 to step S413 in FIG. 4 , and will not be repeated here.

In this embodiment of the application, the registration failure results of the UE initiating registration with the IMS include two types, namely, that the UE receives a registration failure response message before the first timer expires (a registration failure response message such as a SIP 403 message, a SIP 404 message , SIP 408 message, SIP 480 message, SIP 503 message, SIP 504 message, etc.), and the UE does not receive a registration response message (registration failure response message or registration normal response message) before the expiration of the first timer. 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 expiration of the first timer, the UE may equate the registration failure result with the fact that the UE has received a registration failure response message and the message is a SIP 408 message (that is, indicating that the request timed out) is the registration failure result.

The embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium includes instructions, and when the above-mentioned instructions are run on the electronic device, the electronic device is made to execute the relevant method steps of the UE in Figure 4-7 , to implement the method in the above embodiment.

The embodiment of the present application also provides a computer program product containing instructions. When the computer program product is run on the electronic device, the electronic device is made to execute the relevant method steps of the UE in FIG. 4-7, so as to realize the Methods.

The embodiment of the present application also provides a terminal, the terminal includes a processor and a memory, the memory is used to store computer program code, the computer program code includes computer instructions, when the processor executes the computer instructions , the terminal executes the relevant method steps of the UE in FIG. 4-7, so as to implement the method in the foregoing embodiment. The terminal can be an integrated circuit IC or a system-on-chip SOC. The integrated circuit may be a general integrated circuit, a field programmable gate array FPGA, or an application specific integrated circuit ASIC.

Through the method, terminal, computer program product, and computer-readable storage medium of the embodiments of the present application, it is possible to avoid the increase of power consumption caused by the UE frequently initiating IMS registration, and avoid the frequent IMS registration of the secondary card due to the secondary card frequently initiating IMS registration. Seize the resources of the main card to avoid affecting the online experience of the main card.

In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium In, several instructions are included to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor execute all or part of the steps of the method described in each embodiment. The aforementioned storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk, and other various media capable of storing program codes.

The above is only a specific implementation of the application, but the protection scope of the application is not limited thereto, and any changes or replacements within the technical scope disclosed in the application should be covered within the protection scope of the application . Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method for a user equipment to initiate an IMS IMS registration, comprising:

Initiate registration with the IMS;

receiving a registration failure response message from the IMS;

Updating the number of IMS registration failures according to the registration failure response message, and starting a monitoring timer;

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

Updating the IMS registration failure times according to the registration failure response message for re-registration;

When the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires, disable the IMS capability of the user equipment.
The method of claim 1, wherein initiating registration with the IMS comprises:

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

Wherein receiving the registration failure response message from the IMS includes:

A registration failure response message is received from the IMS before the first timer expires.
The method according to claim 1, when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires, the method further comprises:

Clear the number of IMS registration failures;

The watchdog timer is terminated.
The method of claim 1, further comprising:

When the user equipment receives a user instruction to perform at least one of the following operations before the monitoring timer expires: power on, restart, exit the airplane mode, or hot-swap a card, initiate re-registration to the IMS.
The method according to any one of claims 1 to 4, wherein disabling the IMS capability of the user equipment comprises:

A third timer is started, and the IMS capability of the user equipment is disabled before the third timer expires.
The method of claim 5, further comprising:

When the public land mobile network of the user equipment is changed before the third timer expires, or the tracking area of the user equipment is updated, or the user equipment receives a user instruction to perform at least one of the following operations: power on, When restarting, exiting the airplane mode, or hot-swapping a card, terminate the third timer and enable the IMS capability of the user equipment.
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 the following operations : When starting up, restarting, exiting the airplane mode, or hot-swapping a card, enabling the IMS capability of the user equipment after the third timer expires.
The method according to claim 1, wherein updating the number of IMS registration failures according to the registration failure response message, and starting a monitoring timer comprises:

updating the number of IMS registration failures 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 IMS registration failure times according to the registration failure response message for re-registration includes:

Updating the number of IMS registration failures corresponding to the type of the registration failure response message according to the type of the registration failure response message for re-registration;

Wherein, when the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires, disabling the IMS capability of the user equipment includes:

When the number of IMS registration failures corresponding to any monitoring timer exceeds a preset threshold before any monitoring timer expires, the IMS capability of the user equipment is disabled.
The method according to claim 8, when the number of IMS registration failures corresponding to any monitoring timer exceeds a preset threshold before any monitoring timer expires, the method further comprises:

Clear the number of failed registrations for each IMS;

Terminates each watchdog timer.
The method according to 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, and the type of the SIP error code includes at least one of the following : SIP 403 message, SIP 404 message, SIP 408 message, SIP 480 message, SIP 503 message, SIP 504 message.
A method for a user equipment to initiate an IMS IMS registration, comprising:

initiate registration to the IMS, and start 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 the user equipment receives a registration failure response message within the first timer No registration failure response message or registration normal response message is received before the expiration date;

Updating the number of IMS registration failures according to the registration failure result for the registration, and starting a monitoring timer;

From the start of the monitoring timer to before the expiration of the monitoring timer, after each re-registration is initiated to the IMS, determine a registration failure result for re-registration;

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

When the number of IMS registration failures exceeds a preset threshold before the monitoring timer expires, disable the IMS capability of the user equipment.
A user equipment, comprising:

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

A processor, configured to cause the user equipment to execute the method according to any one of claims 1 to 11 when the computer instructions are executed.