Terminal registration method, device, electronic device and computer-readable storage medium

Abstract

The present application provides a terminal registration method, apparatus, electronic device, and computer-readable storage medium. Among them, the method includes: monitoring an event of failure in registering a Standalone (SA) cell or a Non-Standalone (NSA) cell by the terminal; in response to the failure event being a first trigger event, adding the SA cell to a prohibited registration list and triggering a timer to start timing; during the timing of the timer, detecting a target behavior event, and adjusting the timing of the timer according to the target behavior event; when the timing of the adjusted timer ends, removing the SA cell from the prohibited registration list so that the terminal can register the SA cell again. In the present application, when the terminal fails to register the SA cell, the SA cell is added to the prohibited registration list, and the timing of the timer is continuously adjusted to avoid the terminal from frequently registering the SA, thereby improving the stability and reliability of the terminal's network attachment.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a terminal registration method, apparatus, electronic device, and computer-readable storage medium. Background Art

[0002] With the development and maturity of 5G (5th Generation Mobile Communication Technology), the deployment of 5G Standalone (SA) and 5G Non-Standalone (NSA) has become increasingly perfect. Correspondingly, in order to enjoy higher and faster network services, when the network deployment is complete, the user's SIM card needs to be contracted with the SA network so that the SIM card can be normally registered to the SA network. If the SIM card is not contracted with the SA network, that is, in the case of not supporting the SA network, the 5G terminal will preferentially search for the SA network. If the SIM card does not support the SA network, it will be rejected by the SA network.

[0003] However, every time the terminal is powered on or re-enters the service area from the no-service area, it will preferentially search for the SA network according to the 5G device mode priority, resulting in frequent searching for the SA network, causing slow network attachment and affecting the normal use of the terminal. Summary of the Invention

[0004] This application aims to at least solve one of the technical problems in the related art to some extent.

[0005] To this end, this application proposes a terminal registration method, apparatus, electronic device, and computer-readable storage medium to avoid frequent registration of the SA by the terminal and improve the stability and reliability of the terminal's network attachment.

[0006] The first aspect embodiment of this application proposes a terminal registration method, including:

[0007] Monitoring an event that the terminal fails to register with a Standalone (SA) cell or a Non-Standalone (NSA) cell;

[0008] In response to the event being a first trigger event, adding the SA cell to a prohibited registration list and triggering a timer to start timing;

[0009] During the timing of the timer, detecting a target behavior event;

[0010] Adjusting the timing of the timer according to the target behavior event;

[0011] When the adjusted timer timing ends, removing the SA cell from the prohibited registration list to enable the terminal to register with the SA cell again.

[0012] In a second aspect embodiment of the present application, a terminal registration device is proposed, including:

[0013] A monitoring module, configured to monitor an event of failure in registering a Standalone (SA) cell or a Non-Standalone (NSA) cell by a terminal;

[0014] An adding module, configured to, in response to the event being a first trigger event, add the SA cell to a prohibited registration list and trigger a timer to start timing;

[0015] A detecting module, configured to detect a target behavior event during the timing of the timer;

[0016] An adjusting module, configured to adjust the timing of the timer according to the target behavior event;

[0017] A removing module, configured to remove the SA cell from the prohibited registration list when the timing of the adjusted timer ends, so that the terminal can register the SA cell again.

[0018] In a third aspect embodiment of the present application, an electronic device is proposed, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the terminal registration method described in the foregoing first aspect is implemented.

[0019] In a fourth aspect embodiment of the present application, a non-transitory computer-readable storage medium is proposed, on which a computer program is stored. When the computer program is executed by a processor, the terminal registration method described in the foregoing first aspect is implemented.

[0020] In a fifth aspect embodiment of the present application, a computer program product is proposed. When the instructions in the computer program product are executed by a processor, the terminal registration method described in the foregoing first aspect is implemented.

[0021] The technical solutions provided by the embodiments of the present application have the following beneficial effects:

[0022] Monitor an event of failure in registering a Standalone (SA) cell or a Non-Standalone (NSA) cell by a terminal. In response to the event being a first trigger event, add the SA cell to a prohibited registration list and trigger a timer to start timing. During the timing of the timer, detect a target behavior event, adjust the timing of the timer according to the target behavior event, and remove the SA cell from the prohibited registration list when the timing of the adjusted timer ends, so that the terminal can register the SA cell again. In the present application, when the terminal fails to register the SA cell, the SA cell is added to the prohibited registration list and the timing of the timer is continuously adjusted, avoiding the terminal from frequently registering the SA cell and improving the stability and reliability of the terminal's network attachment.

[0023] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of embodiments in conjunction with the accompanying drawings, in which:

[0025] Figure 1 is a schematic flowchart of a terminal registration method provided for an embodiment of the present application;

[0026] Figure 2 is a schematic flowchart of another terminal registration method provided for an embodiment of the present application;

[0027] Figure 3 is a schematic flowchart of another terminal registration method provided for an embodiment of the present application;

[0028] Figure 4 is a schematic flowchart of another terminal registration method provided for an embodiment of the present application

[0029] Figure 5 is a schematic structural diagram of a terminal registration device provided for an embodiment of the present application;

[0030] Figure 6 shows a block diagram of an exemplary electronic device suitable for implementing the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0031] Embodiments of the present application will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present application and should not be construed as limiting the present application.

[0032] The terminal registration method, device, electronic device, and computer-readable storage medium according to the embodiments of the present application will be described below with reference to the accompanying drawings.

[0033] Figure 1 is a schematic flowchart of a terminal registration method provided for an embodiment of the present application.

[0034] As Figure 1 shown, the method includes the following steps:

[0035] Step 101, monitor an event of failure in registering a terminal with a Standalone (SA) cell or a Non-Standalone (NSA) cell.

[0036] Among them, SA (Standalone) and NSA (Non-Standalone) are two 5G networking modes.

[0037] Step 102: In response to the event being the first trigger event, add the SA cell to the prohibited registration list and trigger the timer to start timing.

[0038] In this embodiment, the terminal monitors in real time or at regular intervals the event of failed registration of the SA cell or NSA cell. When the terminal detects the event of failed registration of the SA cell or NSA cell, it determines whether the registration failure event is the first trigger event. Among them, the first trigger event is the event of failed registration of the SA cell caused by the terminal, and the first trigger event is used to trigger the addition of the SA cell to the prohibited registration list and trigger the timer to start timing. For example, since some operators corresponding to the SA cell require the SIM card of the terminal to deregister from the SA cell, when the terminal that has not registered the SA cell inserts the card and camps on the network for the first time, the situation of failed registration of the SA cell will occur. Therefore, the first trigger event is the first card insertion operation when the terminal has not registered the SA cell.

[0039] In this embodiment, after adding the SA cell to the prohibited registration list, the timer is triggered to start timing. Among them, the timing duration of the timer can be set to the initial value of N hours, where N is a natural number greater than 0. That is to say, within the timing time of the timer, for example, within 12 hours, the terminal will not register the SA cell again, avoiding the situation that when the terminal has not subscribed to the SA cell, it frequently registers the SA cell and performs a full-band search when registering the SA cell, which takes a long time and each registration ends in failure, resulting in the mobile phone being unable to camp on the network normally and improving the stability of camping on the network.

[0040] Step 103: During the timing of the timer, detect the target behavior event.

[0041] Among them, the target behavior event is an event generated in response to an operation performed by the user on the terminal side or a terminal system exception. For example, operations such as setting the terminal to enter the flight mode, inserting / removing the card, restarting, subsystem abnormal restart, and other abnormal logics are target behavior events.

[0042] For example, during the timing of the timer, if the user sets the terminal to enter the flight mode, the target behavior event is the terminal entering the flight mode.

[0043] Step 104: Adjust the timing of the timer according to the target behavior event.

[0044] In an embodiment of the present application, the weight coefficient corresponding to the target behavior event is queried. The weight coefficient is inversely proportional to the timing duration corresponding to adding the SA cell to the prohibited registration list, that is, the larger the weight coefficient, the shorter the timing duration, and the smaller the weight coefficient, the longer the timing duration. Thus, the corresponding relationship between the weight coefficient of the target behavior event and the timing duration can be established in advance. It can be understood that for each weight coefficient, there is a corresponding timing duration. For example, when the weight coefficient is a, the corresponding timing duration is x, and when the weight coefficient is b, the corresponding timing duration is y. Furthermore, according to the corresponding relationship between the weight coefficient of the target behavior event and the timing duration, the timing duration corresponding to the weight coefficient can be determined. Then, according to the queried timing duration corresponding to the target behavior event, the set timing duration of the timer is adjusted, realizing the adjustment of the timer timing duration according to different target behavior events, and improving the flexibility of the timing duration setting.

[0045] Step 105, when the timing of the adjusted timer ends, remove the SA cell from the prohibited registration list to enable the terminal to register the SA cell again.

[0046] In an embodiment of the present application, when the timing of the adjusted timer ends, remove the SA cell from the prohibited registration list to allow the terminal to register the SA cell again, enabling the terminal to have the opportunity to try to register the SA cell again, realizing that the terminal can register the SA cell after signing the contract with the operator for SA at the set time, and improving the reliability.

[0047] In the terminal registration method of this embodiment, in response to the first trigger event that the terminal fails to register the stand-alone networking SA cell, add the SA cell to the prohibited registration list and trigger the timer to start timing. During the timing of the timer, detect the target behavior event, and adjust the timing of the timer according to the target behavior event. When the timing of the adjusted timer ends, remove the SA cell from the prohibited registration list to allow the terminal to register the SA cell again. In this application, when the terminal fails to register the SA cell, add the SA cell to the prohibited registration list and continuously adjust the timing of the timer to avoid the terminal registering the SA frequently, improving the stability and reliability of the terminal's network attachment.

[0048] Based on the previous embodiment, this embodiment provides another terminal registration method, specifically illustrating how to adjust the timing of the timer according to different target behavior events, improving the flexibility and meeting the requirements in different scenarios. Figure 2 It is a schematic flowchart of another terminal registration method provided by an embodiment of the present application.

[0049] As Figure 2 shown, the above step 103 includes the following steps:

[0050] Step 201, within a set statistical period, count the second execution times of the target behavior events.

[0051] Among them, the second execution times refer to the number of times each target behavior event is executed within the set statistical period.

[0052] In the embodiments of the present application, the set statistical period can be flexibly set according to the requirements of the scenario, which is not limited in the embodiments of the present application. For example, the set statistical period is 1 day or 1 week. Within the set statistical period, count the second execution times of the target behavior events. Among them, the second execution times of the target behavior events are used to determine the weight coefficients corresponding to the target behavior events.

[0053] It should be noted that for different target behavior events, within the set statistical period, the second execution times of each target behavior event can be counted. Among them, the second execution times of each target behavior event are used to determine the weight coefficients corresponding to the corresponding target behavior events.

[0054] Step 202, according to the second execution times, adjust the standard coefficients corresponding to the target behavior events to obtain the weight coefficients corresponding to the target behavior events.

[0055] In this embodiment, each target behavior event has a corresponding standard coefficient of weight. As an implementation manner, the standard coefficient can be a value randomly set in advance. For example, the standard coefficients of each target behavior event are all m. As another implementation manner, the standard coefficient can be set in advance according to the historical execution times of each target behavior event. That is to say, during the execution process, the execution times of the target behavior events will change in different time periods, and the change in the execution times reflects the change in the weight coefficients of the target behavior events. Therefore, it is necessary to adjust the standard coefficients according to the second execution times of the corresponding target behavior events in the set statistical period to obtain the weight coefficients corresponding to the target behavior events, so as to improve the accuracy of the weight coefficients corresponding to the target behavior events.

[0056] For example, the standard coefficients corresponding to each target behavior event are shown in Table 1.

[0057] Target behavior event Standard coefficient Flight operation a Insertion and extraction card operation b Restart operation c Subsystem abnormal restart d Other abnormal logics e

[0058] Among them, the standard coefficients a - e increase. The smaller the standard coefficient, the longer the duration of the SA cell in the prohibited registration list. That is to say, the longer the duration for which the terminal will not re-register the SA cell, avoiding frequent SA cell registration.

[0059] It should be noted that the various target behavior events and the corresponding standard coefficients shown in Table 1 are only examples. In different scenarios, the target behavior events can be different, and the corresponding standard coefficients can also be different, which does not constitute a limitation to this embodiment.

[0060] In this embodiment, in order to improve the accuracy of the target behavior events corresponding to the terminal, the user terminal behavior can be statistically analyzed, that is, the second execution times of each target behavior event are statistically analyzed, and the standard coefficients are dynamically adjusted according to the second execution times to obtain the weight coefficients corresponding to each target behavior event, and the corresponding relationship between the weight coefficients and the timing durations is adjusted to improve the accuracy of adjusting the timer duration according to the target behavior events subsequently.

[0061] For example, if the number of restart operations of User A during the statistical period is much larger than the number of flight operations, that is, the second execution times of the restart operations statistically obtained are much larger than the second execution times of the flight operations, then the standard coefficient of the flight operation is increased to obtain the weight coefficient of the flight operation, and the standard coefficient of the restart operation is decreased to obtain the weight coefficient of the restart operation.

[0062] Step 203, query the weight coefficient corresponding to the target behavior event.

[0063] Step 204, adjust the timing duration of the timer according to the weight coefficient and the first execution times of the target behavior event during the timing process.

[0064] Among them, there is a corresponding relationship between the weight coefficient and the timing duration of the timer. The weight coefficient is inversely proportional to the timing duration of the timer, that is, the smaller the weight coefficient, the longer the timing duration of the timer, that is, the longer the duration of the SA cell in the prohibited list.

[0065] In the above embodiment, it is illustrated that, as an implementation method, according to the weight coefficient of the target behavior event, the corresponding timing duration of the timer can be determined. Since the timer is currently counting down according to the timing duration determined by the first trigger event, after detecting the target behavior event, it is necessary to adjust the timing duration of the timer according to the timing duration corresponding to the weight coefficient of the target behavior event, realizing the adjustment of the timing duration of the timer based on the target behavior event.

[0066] In an actual scenario, within the timing duration, the number of times the target behavior event is executed by the terminal is different. To improve the accuracy of timing duration adjustment, it is also necessary to count the first execution times of the target behavior event within the timing duration. Thus, in another implementation manner of the embodiments of the present application, according to the first execution times of the target behavior event during the timing process, it is determined whether the SA cell needs to be removed from the prohibited registration list, and the timing duration of the timer is adjusted according to the weight coefficient of the target behavior event. In one scenario, when the target behavior event is detected, if the first execution times of the target behavior event during the timing process is less than or equal to the set threshold, it indicates that the user executes the target behavior event less frequently. Then, the SA cell is removed from the prohibited registration list, so that the terminal can register the SA cell again, and the timing duration of the timer is reset according to the weight coefficient corresponding to the target behavior event. For example, the target behavior event is card insertion / removal, the set threshold is 2 times. When the first execution times of the target behavior event is detected as 1 time, since the user executes the card insertion / removal operation less frequently, that is, the terminal has been in the card-inserted state all the time. When it is detected that the user executes the card insertion / removal once, the SA cell can be removed from the prohibited registration list, so that the terminal can register the SA cell again. If the registration fails, the timing duration of the timer is reset according to the weight coefficient corresponding to the card insertion / removal, which can avoid frequent registration of the SA cell. In another scenario, when the target behavior event is detected, if the first execution times of the target behavior event during the timing process is greater than the set threshold, it indicates that the user executes the target behavior event more frequently. Then, when the target behavior event is detected currently, the SA cell is not removed from the prohibited registration list, and the timing duration of the timer is adjusted according to the weight coefficient of the target behavior event. As an implementation manner, the timing duration of the timer is extended, that is, on the basis of the set timing duration of the timer, the timing duration corresponding to the weight coefficient of the target behavior event is superimposed to extend the timing duration of the timer and avoid the terminal from frequently registering the SA cell.

[0067] In the terminal registration method of this embodiment, in response to a first trigger event of the terminal failing to register an independent networking SA cell, the SA cell is added to the prohibited registration list, and a timer is triggered to start timing. During the timing of the timer, a target behavior event is detected, and according to the target behavior event, the timing of the timer is adjusted. When the adjusted timer expires, the SA cell is removed from the prohibited registration list to allow the terminal to register the SA cell again. In this application, when the terminal fails to register the SA cell, the SA cell is added to the prohibited registration list, and the timing of the timer is continuously adjusted to avoid abnormal phenomena such as slow terminal network attachment, network disconnection, and loss of Voice over Long-Term Evolution (VOLTE) caused by the terminal frequently registering the SA. At the same time, it also ensures that the terminal has the opportunity to attempt to register the SA, improving the stability and reliability of the terminal network attachment, and improving the experience of the terminal network attachment in the SA network.

[0068] Based on the above embodiment, this embodiment provides another terminal registration method. Figure 3 It is a schematic flowchart of another terminal registration method provided by the embodiment of the present application. As Figure 3 shown, after step 104, the method includes the following steps:

[0069] Step 301, monitor the SA signal quality of the SA cell registered by the terminal.

[0070] As an implementation manner, the SA signal quality is indicated by the signal-to-noise ratio of the SA.

[0071] Step 302, in the case where the SA signal quality is lower than the threshold, perform a heterogeneous radio access technology (RAT) network handover.

[0072] In this embodiment, during the process of a terminal registering for an SA cell, the terminal may be in the boundary area of the SA cell, or the terminal moves from an SA cell with better SA signal quality to an SA cell with worse SA signal quality. In some service scenarios with high requirements for network quality and strong real-time performance, such as a call scenario, a game scenario, or a live streaming scenario, if the SA signal quality is lower than a threshold, where the threshold can be determined according to the average value of the signal-to-noise ratio when the terminal experiences a radio link failure (RLF), for example, if the threshold is -10 dB, then the terminal will experience a radio link failure (RLF), which affects the normal transmission of the terminal's data services. For example, there will be lags during playing games or live streaming, or the call is not smooth, etc. Therefore, in this application, the SA signal quality of the SA cell registered by the terminal is monitored. As an implementation method, the signal-to-noise ratio (SNR) of the SA cell recorded in the terminal database is obtained. Among them, the SA signal quality is indicated by the signal-to-noise ratio. The higher the signal-to-noise ratio, the higher the SA signal quality; the lower the signal-to-noise ratio, the worse the SA signal quality. According to the corresponding relationship that the signal-to-noise ratio and the SA signal quality are inversely proportional, the SA signal quality of the registered SA cell is determined. Furthermore, in the case where the SA signal quality is lower than the threshold, a heterogeneous radio access technology (RAT) network handover is performed. For example, in one scenario, the SA signal quality is poor, while the long term evolution (LTE) signal quality is good, then the network of the terminal is switched to the RAT network of LTE. Furthermore, if the signal quality of the non-standalone (NSA) network is higher than the threshold, the secondary cell group (SCG) can be continued to be added, and the terminal is registered to the NSA cell. After successful registration, the corresponding services of the above service scenarios are continued to avoid the problem of disconnection. Similarly, the above process is also applicable to the NSA network, and the principle is the same, which will not be elaborated in this embodiment.

[0073] It should be noted that, in one scenario, the method of this embodiment is also applicable to the dual connectivity (EUTRA-NR Dual Connection, ENDC) mode, that is, when the signal quality of the dual connectivity mode is lower than the threshold, the secondary cell group (SCG) is disconnected, and then the terminal is registered to the SA cell; in another scenario, when the signal quality is lower than the threshold in the long term evolution (LTE) mode, the terminal can be switched to other RAT networks, such as a 3G network or a 4G network.

[0074] In the terminal registration method of this embodiment, after the SA cell is removed from the prohibited registration list to allow the terminal to register for the SA cell again, frequent registration to the SA network is avoided, and the stability and reliability of the terminal on the network are improved. Furthermore, the SA signal quality of the SA cell registered by the terminal can be monitored. When the SA signal quality is lower than the threshold, heterogeneous wireless network RAT network switching is performed, thereby improving the stability of data or call quality under the SA network and improving user experience.

[0075] Based on the above embodiment, this embodiment provides another implementation of the terminal registration method. Figure 4 A flowchart of another terminal registration method provided in an embodiment of the present application.

[0076] like Figure 4 As shown, the method may further include the following steps:

[0077] Step 401: monitoring an event in which a terminal fails to register with a standalone (SA) cell or a non-standalone (NSA) cell.

[0078] Step 402: In response to the event that the terminal fails to register an SA cell or a non-standalone networking NSA cell, which is a second triggering event, the number of occurrences of the second triggering event is counted.

[0079] The second triggering event is a registration failure event caused by a network-side device. For example, a terminal modem subsystem anomaly or other logical anomaly may be caused by an abnormal network parameter configuration. As an implementation method, in response to a terminal failing to register an SA cell or a non-standalone (NSA) cell, the second triggering event is determined. Based on the cause of the registration failure caused by the network-side device, a corresponding type tag is added to the second triggering event, the number of added type tags is counted, and the number of occurrences of the second triggering event corresponding to each type tag is determined. Specifically, a type tag is added to the second triggering event corresponding to a terminal failing to register an SA cell or a non-standalone (NSA) cell. The type tag indicates the cause of the registration failure corresponding to the second triggering event, for example, the cause of the registration failure is caused by a modem subsystem anomaly when the terminal is registering an SA cell, or the cause of the registration failure is caused by a modem subsystem anomaly when the terminal is registering an NSA cell. Furthermore, the number of occurrences of the second triggering event corresponding to the failure to register an SA cell or the number of occurrences of the second triggering event corresponding to the failure to register an NSA cell is determined based on the type tags.

[0080] Step 403: When the number of occurrences is greater than the set number threshold, the terminal is prohibited from registering the SA cell or the NSA cell.

[0081] It should be noted that the terminal contains multiple subsystems. The subsystem of the modem is related to the registration of SA. When performing SA or NSA registration, it may cause abnormalities in the modem subsystem. In this embodiment, when the terminal fails to register for an SA cell, the second trigger event is an abnormality in the modem subsystem, or when the terminal registers for an NSA cell, the second trigger event is an abnormality in the modem subsystem. For example, the subsystem abnormality is repeated restart. Wherein, when the second trigger event is other situations, the principle is the same and is not limited in this embodiment. In the first implementation manner of this embodiment, within a set time, if the terminal fails to register for an SA cell due to an abnormality in the modem subsystem, the occurrence times of the second trigger event corresponding to the terminal's failure to register for an SA cell are counted. When the occurrence times of the second trigger event are greater than the set number threshold, the terminal is prohibited from registering for an SA cell to avoid the repeated occurrence of the second trigger event and improve the stability of terminal communication. When the occurrence times of the second trigger event are less than or equal to the set number threshold, the terminal performs SA cell registration.

[0082] In the second implementation manner of this embodiment, within a set time, if the terminal fails to register for a non-standalone networking (NSA) cell due to a subsystem abnormality, the occurrence times of the second trigger event corresponding to the terminal's failure to register for an NSA cell are counted. When the occurrence times of the second trigger event are greater than the set number threshold, the terminal is prohibited from registering for an NSA cell to avoid the repeated occurrence of the second trigger event and improve the stability of terminal communication. When the occurrence times of the second trigger event are less than or equal to the set number threshold, the terminal performs NSA cell registration.

[0083] Step 404, obtain the cell information of the LTE cell where the terminal is located.

[0084] Step 405, when it is monitored according to the cell information that the terminal moves out of the LTE cell, allow the terminal to register for an SA cell or an NSA cell.

[0085] In this embodiment, when the terminal is prohibited from registering for an SA cell or the terminal is prohibited from registering for an NSA cell, the terminal can be controlled to register for an LTE cell with a larger coverage area to achieve normal data communication. At the same time, after registering for the LTE cell, the terminal can be closed from registering for the SA cell, that is, the SA cell is added to the prohibited registration list of the terminal, avoiding the situation where the terminal cannot be used normally due to the repeated occurrence of the second trigger event, such as subsystem abnormality, when registering for the SA cell, and enabling the terminal to be used normally.

[0086] Further, the information of the LTE cell recorded in the terminal database can be obtained. The LTE cell information includes the frequency point corresponding to the cell or the identification information of the cell, etc. The LTE cell information is used to determine the corresponding LTE cell. When it is monitored according to the cell information that the terminal moves out of the LTE cell, the terminal is allowed to register for the SA cell or the NSA cell, meeting the requirement for the terminal to register for the SA cell or the NSA cell.

[0087] In the terminal registration method of this embodiment, in response to the event that the terminal fails to register for the SA cell or the non-standalone networking (NSA) cell, if the event is the second trigger event, the occurrence times of the second trigger event are counted. When the occurrence times are greater than the set number threshold, the terminal is prohibited from registering for the SA cell or the NSA cell to avoid the repeated occurrence of the second trigger event and improve the stability of terminal communication. And when the terminal cannot register for the SA cell or the NSA cell, it registers for the LTE cell, improving the stability of terminal communication. Further, when it is monitored according to the cell information that the terminal moves out of the LTE cell, the terminal is allowed to register for the SA cell or the NSA cell, meeting the requirement for the terminal to register for the SA cell or the NSA cell.

[0088] To implement the above embodiment, the present application also proposes a terminal registration device.

[0089] Figure 5 It is a schematic structural diagram of a terminal registration device provided by an embodiment of the present application.

[0090] As Figure 5 shown, the device includes:

[0091] A monitoring module 51, configured to monitor the event that the terminal fails to register for the standalone networking (SA) cell or the non-standalone networking (NSA) cell.

[0092] An adding module 52, configured to, in response to the event being the first trigger event, add the SA cell to the prohibited registration list and trigger the timer to start timing.

[0093] A detecting module 53, configured to detect the target behavior event during the timing of the timer.

[0094] An adjusting module 54, configured to adjust the timing of the timer according to the target behavior event.

[0095] A removing module 55, configured to remove the SA cell from the prohibited registration list when the timing of the adjusted timer ends, so that the terminal can register for the SA cell again.

[0096] Further, as a possible implementation manner, the adjusting module 54 is specifically configured to:

[0097] Query the weight coefficient corresponding to the target behavior event;

[0098] Adjust the timing duration of the timer according to the weight coefficient and the first execution count of the target behavior event during the timing process.

[0099] As a possible implementation, the adjustment module 54 is further configured to:

[0100] During a set statistical period, count the second execution count of the target behavior event;

[0101] Adjust the standard coefficient corresponding to the target behavior event according to the second execution count to obtain the weight coefficient corresponding to the target behavior event.

[0102] As a possible implementation, the device further includes:

[0103] A monitoring module, configured to monitor the SA signal quality of the SA cell registered by the terminal;

[0104] A switching module, configured to perform heterogeneous radio access technology (RAT) network switching when the SA signal quality is lower than a threshold.

[0105] As a possible implementation, the device further includes:

[0106] A statistics module, configured to count the occurrence count of the second trigger event in response to an event that the terminal fails to register for an SA cell or a non-standalone NSA cell being the second trigger event;

[0107] A prohibition module, configured to prohibit the terminal from registering for an SA cell or an NSA cell when the occurrence count is greater than a set count threshold.

[0108] As a possible implementation, the device further includes:

[0109] An acquisition module, configured to acquire the cell information of the LTE cell where the terminal is located;

[0110] A registration module, configured to control the terminal to register for an SA cell or an NSA cell when it is monitored according to the cell information that the terminal moves out of the LTE cell.

[0111] As a possible implementation, the first trigger event is a registration failure event caused by the terminal; the second trigger event is a registration failure event caused by a network-side device.

[0112] As a possible implementation, the statistics module is further configured to:

[0113] The event of the terminal failing to register for a Standalone (SA) cell or a Non-Standalone (NSA) cell is the second trigger event. According to the cause of the registration failure caused by the network-side device, a corresponding type tag is added to the second trigger event;

[0114] Count the number of the added type tags to determine the occurrence times of the second trigger event corresponding to each type tag.

[0115] As a possible implementation, the statistics module is further configured to

[0116] When the occurrence times are greater than the set times threshold, prohibit the terminal from registering for an SA cell or an NSA cell according to the type tag corresponding to the occurrence times.

[0117] It should be noted that the foregoing explanation of the method embodiment also applies to the device of this embodiment, and will not be repeated here.

[0118] In the terminal registration device of this embodiment, the event of the terminal failing to register for a Standalone (SA) cell or a Non-Standalone (NSA) cell is the first trigger event. The SA cell is added to the prohibited registration list, and a timer is triggered to start timing. During the timing of the timer, a target behavior event is detected. According to the target behavior event, the timing of the timer is adjusted. When the adjusted timer timing ends, the SA cell is removed from the prohibited registration list, so that the terminal can register for the SA cell again. In this application, when the terminal fails to register for the SA cell, the SA cell is added to the prohibited registration list, and the timing duration of the timer is continuously adjusted according to the target behavior event, avoiding the terminal from frequently registering for the SA, and improving the stability and reliability of the terminal's network attachment.

[0119] To implement the above embodiment, this embodiment provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the terminal registration method described in the foregoing method embodiment is implemented.

[0120] To implement the above embodiment, this embodiment provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the terminal registration method described in the foregoing method embodiment is implemented.

[0121] To implement the above embodiment, this embodiment provides a computer program product. When the instructions in the computer program product are executed by a processor, the terminal registration method described in the foregoing method embodiment is implemented.

[0122] Figure 6A block diagram of an exemplary electronic device suitable for implementing the embodiments of the present application is shown. Figure 6 The displayed electronic device 12 is merely an example and should not impose any limitation on the functions and scope of use of the embodiments of the present application.

[0123] As Figure 6 shown, the electronic device 12 is presented in the form of a general-purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 connecting different system components (including the memory 28 and the processing unit 16).

[0124] The bus 18 represents one or more of several types of bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. By way of example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnection (PCI) bus.

[0125] The electronic device 12 typically includes a variety of computer system-readable media. These media can be any available media that can be accessed by the electronic device 12, including volatile and non-volatile media, removable and non-removable media.

[0126] The memory 28 may include computer system-readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, a storage system 34 may be used for reading and writing non-removable, non-volatile magnetic media ( Figure 6 not shown, commonly referred to as a "hard disk drive"). Although Figure 6Not shown in the figure, a disk drive for reading and writing a removable non-volatile disk (such as a "floppy disk") and an optical disk drive for reading and writing a removable non-volatile optical disk (such as: Compact Disc Read Only Memory; hereinafter referred to as: CD-ROM), Digital Video Disc Read Only Memory; hereinafter referred to as: DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 through one or more data medium interfaces. The memory 28 may include at least one program product having a set (such as at least one) of program modules configured to perform the functions of the embodiments of the present application.

[0127] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment. The program modules 42 generally perform the functions and / or methods in the embodiments described in the present application.

[0128] The electronic device 12 may also communicate with one or more external devices 14 (such as a keyboard, a pointing device, a display 24, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 12, and / or communicate with any device that enables the electronic device 12 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication may be carried out through the input / output (I / O) interface 22. In addition, the electronic device 12 may also communicate with one or more networks (such as a Local Area Network; hereinafter referred to as: LAN, a Wide Area Network; hereinafter referred to as: WAN) and / or a public network, such as the Internet) through the network adapter 20. As shown in the figure, the network adapter 20 communicates with other modules of the electronic device 12 through the bus 18. It should be understood that although not shown in the figure, other hardware and / or software modules may be used in combination with the electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0129] The processing unit 16 executes various functional applications and data processing by running the programs stored in the memory 28, such as implementing the methods mentioned in the foregoing embodiments.

[0130] In the description of this specification, the descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of this application. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0131] In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be construed as indicating or implying relative importance or implicitly indicating the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of such features. In the description of this application, "a plurality" means at least two, such as two, three, etc., unless otherwise specifically defined.

[0132] Any process or method description, whether in a flowchart or otherwise described herein, can be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a customized logic function or process, and the scope of the preferred embodiments of this application includes additional implementations, where the functions may be executed in a manner that is not shown or discussed, including substantially simultaneously according to the functions involved or in a reverse order, which should be understood by those skilled in the art to which the embodiments of this application pertain.

[0133] Logic and / or steps represented in a flowchart or otherwise described herein can, for example, be considered as a definitional sequence list of executable instructions for implementing logical functions, which can be embodied specifically in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, a system including a processor, or other systems that can fetch instructions from and execute instructions of the instruction execution system, apparatus, or device. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or other suitable medium on which the program can be printed, as the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpretation, or otherwise processing as appropriate, and then stored in a computer memory.

[0134] It should be understood that various parts of the present application can be implemented by hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0135] Those of ordinary skill in the art of this technology can understand that all or part of the steps carried by the method of the above-described embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0136] In addition, each functional unit in various embodiments of the present application may be integrated into one processing module, or each unit may exist physically alone, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0137] The above-mentioned storage medium may be a read-only memory, a magnetic disk, an optical disc, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present application. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

Claims

1. A terminal registration method, characterized in that, Including the following steps: Monitoring the event that the terminal fails to register with a Standalone (SA) cell or a Non-Standalone (NSA) cell; In response to the event being a first trigger event, adding the SA cell to a prohibited registration list and triggering a timer to start timing; wherein, the first trigger event is a registration failure event caused by the terminal; During the timing of the timer, detecting a target behavior event; wherein, the target behavior event is an event generated in response to an operation performed on the terminal side or an abnormality in the terminal system; Adjusting the timing of the timer according to the target behavior event; When the adjusted timer expires, removing the SA cell from the prohibited registration list to enable the terminal to register with the SA cell again.

2. The method according to claim 1, wherein The adjusting the timing of the timer according to the target behavior event includes: Querying the weight coefficient corresponding to the target behavior event; Adjusting the timing duration of the timer according to the weight coefficient and the first execution count of the target behavior event during the timing process.

3. The method according to claim 2, wherein Before querying the weight coefficient corresponding to the target behavior event, it further includes: During a set statistical period, counting the second execution count of the target behavior event; Adjusting the standard coefficient corresponding to the target behavior event according to the second execution count to obtain the weight coefficient corresponding to the target behavior event.

4. The method according to claim 1, wherein After removing the SA cell from the prohibited registration list to enable the terminal to register with the SA cell again, it further includes: Monitoring the SA signal quality of the SA cell registered by the terminal; Performing a Radio Access Technology (RAT) network handover to a heterogeneous wireless network when the SA signal quality is lower than a threshold.

5. The method according to claim 1, characterized in that, The method further includes: In response to the event that the terminal fails to register with an SA cell or an NSA cell being a second trigger event, counting the occurrence times of the second trigger event; wherein, the second trigger event is a registration failure event caused by a network-side device; When the occurrence times are greater than a set number threshold, prohibiting the terminal from registering with an SA cell or an NSA cell.

6. The method according to claim 5, wherein After prohibiting the terminal from registering with an SA cell or an NSA cell, it further includes: Obtaining the cell information of the LTE cell where the terminal is located; When it is monitored according to the cell information that the terminal moves out of the LTE cell, controlling the terminal to register with an SA cell or an NSA cell.

7. The method according to claim 5 or 6, characterized in that, The counting the occurrence times of the second trigger event in response to the event that the terminal fails to register with an SA cell or an NSA cell being a second trigger event includes: In response to the event that the terminal fails to register with an SA cell or an NSA cell being the second trigger event, adding a corresponding type label to the second trigger event according to the registration failure reason caused by the network-side device; Counting the number of the added type labels to determine the occurrence times of the second trigger event corresponding to each type label.

8. The method according to claim 7, wherein The prohibiting the terminal from registering with an SA cell or an NSA cell when the occurrence times are greater than a set number threshold includes: When the occurrence times are greater than the set occurrence threshold, prohibit the terminal from registering for an SA cell or an NSA cell according to the type tag corresponding to the occurrence times.

9. A terminal registration device, characterized in that, It includes: A monitoring module, configured to monitor an event that the terminal fails to register for a Standalone (SA) cell or a Non-Standalone (NSA) cell; An adding module, configured to, in response to the event being a first trigger event, add the SA cell to a prohibited registration list and trigger a timer to start timing; wherein, the first trigger event is a registration failure event caused by the terminal; A detecting module, configured to detect a target behavior event during the timing of the timer; wherein, the target behavior event is an event generated in response to an operation performed on the terminal side or a terminal system exception; An adjusting module, configured to adjust the timing of the timer according to the target behavior event; A removing module, configured to remove the SA cell from the prohibited registration list when the adjusted timer expires, so that the terminal can register for the SA cell again.

10. The device according to claim 9, characterized in that, The adjusting module is configured to: Query the weight coefficient corresponding to the target behavior event; Adjust the timing duration of the timer according to the weight coefficient and the first execution times of the target behavior event during the timing process.

11. The device according to claim 10, characterized in that, The adjusting module is further configured to: Count the second execution times of the target behavior event within a set statistical period; Adjust the standard coefficient corresponding to the target behavior event according to the second execution times to obtain the weight coefficient corresponding to the target behavior event.

12. The device according to claim 9, characterized in that, The device further includes: A monitoring module, configured to monitor the SA signal quality of the SA cell registered by the terminal; A switching module, configured to perform a Radio Access Technology (RAT) network handover when the SA signal quality is lower than a threshold.

13. The device according to claim 9, wherein The device further includes: A counting module, configured to count the occurrence times of a second trigger event in response to the terminal failing to register for an SA cell or an NSA cell; wherein, the second trigger event is a registration failure event caused by a network-side device; A prohibiting module, configured to prohibit the terminal from registering for an SA cell or an NSA cell when the occurrence times are greater than a set occurrence threshold.

14. The device according to claim 13, characterized in that, The device further includes: An obtaining module, configured to obtain the cell information of the LTE cell where the terminal is located; A registration module, configured to allow the terminal to register for an SA cell or an NSA cell when it is monitored according to the cell information that the terminal moves out of the LTE cell.

15. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the method described in any one of claims 1-8 is implemented.

16. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, the method described in any one of claims 1-8 is implemented.

Images