WO2019228103A1 - Network attachment control method and device, and mobile terminal - Google Patents

Abstract

The present invention relates to the technical field of mobile communications, and provides a network attachment control method and device, and a mobile terminal. Regarding the network attachment control method and device, and the mobile terminal provided in embodiments of the present application, the method comprises: in a present attachment process, if a detachment message sent by a target network is received, checking whether the cause of an attachment failure is a PTI conflict; and if yes, re-initiating a next attachment process, so that a mobile terminal completes a network attachment process. Therefore, cases where a mobile terminal is unable to attach to a target network due to transaction identifier conflicts are reduced, thereby improving the communication experience of a user using a mobile network.

Description

Network attachment control method, device and mobile terminal [Technical Field]

The present invention relates to the field of mobile communication technology, and in particular, to a network attachment control method, device, and mobile terminal.

【Background technique】

When the mobile terminal is turned on, restarted, or switched from the flight mode to the normal working mode, the mobile terminal needs to search for a target network that can be connected for network attachment. After the network is attached, the mobile terminal can communicate normally.

At present, in the process of network attachment of a mobile terminal, the mobile terminal sends an attachment request to the target network. The attachment request carries a PTI (Procedure Transaction ID, transaction ID) identifier, which is used to identify a transaction in the attachment process. To avoid network attachment conflicts, the PTI identifier carried in the attachment request is PTI1. If the mobile terminal does not receive the attach response returned by the target network within the set waiting period during the network attachment process, the mobile terminal will resend the attach request, and the PTI identifier carried in the attached request sent this time is PTI2. At this time, if the target network happens to send an attach response to the attach request corresponding to PTI1 to the mobile terminal. The mobile terminal ignores the attach response because the PTI does not match, and the target network also ignores the reattachment request sent by the mobile terminal because of the PTI mismatch, eventually causing the target network to remove the bearer and send a detach message to the mobile terminal. After receiving the detach message sent by the target network, the mobile terminal will disable the network attachment function and no longer attempt network attachment. As a result, the mobile terminal will not attempt 4G attachment again, and will not reattach 4G until the network search is restarted (airplane mode is turned off or restart trigger). The internet.

[Summary of the Invention]

In view of this, an object of the embodiments of the present invention is to provide a network attachment control method, device, and mobile terminal, so as to reduce the phenomenon that the mobile terminal cannot attach to the target network due to the conflict of the attachment process, and improve the communication experience of the user using the mobile network.

In order to achieve the foregoing objective, the technical solutions adopted by the embodiments of the present invention are as follows:

In a first aspect, an embodiment of the present invention provides a network attachment control method, which is applied to a mobile terminal. The method includes:

During the current attachment process, if a detach message is received from the target network, check whether the cause of the attachment failure is a PTI conflict with the transaction identifier;

If yes, re-initiate the next round of attachment process; among them, the PTI carried by the attachment request in each round of attachment process is sequentially increased from the initial value.

In a preferred embodiment of the present invention, the method further includes:

When the mobile terminal receives an attach response during the current attach process, it checks whether the PTI carried in the attach response is the same as the PTI carried in the last attach request sent;

If they are different, the reason for the record attachment failure is the conflict of transaction identifier PTI.

In a preferred embodiment of the present invention, the reason why the record attachment fails is the step of conflicting transaction identifier PTIs, including:

The preset PTI matching identifier is set to a first specified value; wherein the initial value of the PTI matching identifier is a second specified value.

In a preferred embodiment of the present invention, the method further includes:

When the next attach process is re-initiated, the PTI matching identifier is set to the second specified value.

In a preferred embodiment of the present invention, the method further includes:

When the next attachment process is re-initiated, the cause of the attachment failure is cleared.

In a second aspect, an embodiment of the present invention provides a network attachment device applied to a mobile terminal, where the device includes:

A cause determination module is used to check whether the cause of the attachment failure is a PTI conflict in the transaction identifier if a detach message is received from the target network during the current attachment process;

Attachment update module is used to re-initiate the next round of attachment process if the cause of the attachment failure is the transaction identifier PTI conflict; among them, the PTI carried by the attachment request in each round of attachment process is sequentially increased from the initial value.

In a preferred embodiment of the present invention, the device further includes:

A recording module, configured to check whether the PTI carried by the attachment response is the same as the PTI carried by the most recent attachment request sent when the mobile terminal receives an attachment response during the current round of attachment; if they are different, record the The reason is that the transaction ID PTI conflicts.

In a preferred embodiment of the present invention, the recording module is further configured to:

The preset PTI matching identifier is set to a first specified value; wherein the initial value of the PTI matching identifier is a second specified value.

In a third aspect, an embodiment of the present invention provides a mobile terminal. In a possible design, the structure of the mobile terminal includes a processor and a memory, where the memory is configured to store a program that supports the processor to perform the foregoing method, and the processor is configured to execute the program stored in the memory. .

In a fourth aspect, an embodiment of the present invention provides a machine-readable storage medium for storing computer software instructions used by the network attachment device.

Compared with the prior art, the network attachment control method, device, and mobile terminal provided in the embodiments of the present invention, during the current round of attachment process, if a detach message sent by the target network is received, it is checked whether the cause of the attachment failure is a PTI conflict . If the cause of the attachment failure is a PTI conflict, the next round of attachment process is re-initiated to enable the mobile terminal to complete the network attachment process. Therefore, the phenomenon that the mobile terminal cannot be attached to the target network due to the conflict of transaction identifiers can be reduced, and the communication experience of the user using the mobile network can be improved.

In order to make the foregoing objects, features, and advantages of the present invention more comprehensible, preferred embodiments are described below in detail with reference to the accompanying drawings, as follows.

[Brief Description of the Drawings]

In order to explain the technical solution of the embodiments of the present invention more clearly, the drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention, and therefore are not It should be regarded as a limitation on the scope. For those of ordinary skill in the art, other related drawings can be obtained according to these drawings without paying creative work.

FIG. 1 is a flowchart of a network attachment control method according to an embodiment of the present invention;

2 is a flowchart of a network attachment control method according to another embodiment of the present invention;

3 is a flowchart of interaction between a mobile terminal and a target network during a network attachment process according to an embodiment of the present invention;

4 is a structural block diagram of a network attachment control device according to an embodiment of the present invention;

5 is a structural block diagram of a network attachment control apparatus according to another embodiment of the present invention;

FIG. 6 is a structural block diagram of a mobile terminal according to an embodiment of the present invention.

【Detailed ways】

In the following, the technical solutions in the embodiments of the present invention will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. The components of embodiments of the invention, generally described and illustrated in the figures herein, can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts fall within the protection scope of the present invention.

At present, during the process of network attachment of mobile terminals such as mobile phones, the mobile terminal may disable the network attachment function due to the mismatch of transaction identifiers, fail to connect to the network, and reduce the communication experience of users using the mobile network. Based on this, embodiments of the present invention provide a network attachment control method, device, and mobile terminal to reduce the inability of the mobile terminal to attach to the target network due to the conflict of transaction identifiers, and improve the user's communication experience using the mobile network.

The embodiments of the present invention will be described in detail below with reference to the drawings.

FIG. 1 shows a flowchart of a network attachment control method according to an embodiment of the present invention. The method can be applied to a mobile terminal, such as a mobile phone, a handheld computer, a sales terminal, a vehicle-mounted computer, and a smart wearable device. As shown in Figure 1, the method includes the following steps:

In step S102, if a detach message sent by the target network is received during the current attach process, it is checked whether the cause of the attach failure is a transaction identifier PTI conflict; if so, step S106 is performed; if not, step S104 is performed.

When the mobile terminal needs network attachment, the mobile terminal searches for a connectable target network. After the target network is determined, the mobile terminal initiates a round of attach process to the target network. This round of attach process may include one or more attach requests, each attach request carrying a PTI used to identify the current attach transaction. The attach response returned by the target network also carries its own PTI, which is used to identify the attach request corresponding to the attach response.

After sending the attachment request to the target network, if the mobile terminal has not received the attachment response returned by the target network for a set period of time, or the PTI of the received attachment response is not consistent with the PTI of the last attachment request sent by the mobile terminal, Send attachment request repeatedly. Until the mobile terminal receives the detach message sent by the target network and completes a round of attach process.

In the prior art, after completing a round of attachment process, the mobile terminal will disable the network attachment function. This operation will cause the mobile terminal to fail to register for 4G services. It will not reattach 4G until it switches to restarting the search network (turning off the flight mode or restart trigger) . In the embodiment of the present invention, when the mobile terminal receives an attachment response (the attachment response carries a PTI and a default bearer) during the current round of attachment, it is checked whether the PTI carried in the attachment response and the PTI carried in the most recently sent attachment request. the same. If they are the same, activate the default bearer according to the attachment response to complete the network attachment; if they are different, record the cause of the attachment failure as a PTI conflict, and continue to send attachment requests repeatedly. For example, the code corresponding to the cause of the attachment failure may be recorded at a specified location in the memory. For example, if the code corresponding to the attachment failure caused by the PTI conflict is 05, the code 05 is written to the specified location in the memory. If a detach message sent by the target network is received, it is determined whether the cause of the attachment failure is a PTI conflict based on the record at the specified location. It can be understood that the number of sending attachment requests and the cause of each attachment failure can also be recorded in the form of a table. If the detach message sent by the target network is received and the cause of the attachment failure is at least one PTI conflict, it can be determined that the cause of the attachment failure is a PTI conflict.

Step S104 is performed according to the related technology.

If the cause of the attachment failure is not a PTI conflict, the network attachment function can be disabled according to the existing rules, and no attachment request is sent.

Step S106: Re-initiate the next attach process. Among them, the PTI carried in the attach request during each round of attaching processes are sequentially increased from the initial value.

If the cause of the attachment failure is a PTI conflict, the network attachment function will not be disabled, but the next attachment process will be reinitiated. The transaction identifier carried in the first attachment request in the new round of attachment process will still be the initial value PTI1, which The transaction ID carried by each subsequent attach request is incremented in turn.

When re-initiating the next attachment process, the cause of the attachment failure is cleared. For example, if the code 05 corresponding to the cause of the attachment failure is recorded in a specified position in the memory, the code 05 is cleared, and the content stored in the specified position in the memory is restored to the initial state 00. If the number of attachment requests sent and the reason for each attachment failure are recorded in the form of a form, the content recorded in the form is cleared to form a blank form provided with only a header.

In the above network attachment control method, if a detach message sent by the target network is received during the current attachment process, it is checked whether the cause of the attachment failure is a PTI conflict. If the cause of the attachment failure is a PTI conflict, the next round of attachment process is re-initiated to enable the mobile terminal to complete the network attachment process. Therefore, the phenomenon that the mobile terminal cannot attach to the target network (such as the 4G network or the 5G network) due to the conflict of the transaction identifiers can be reduced, and the communication experience of the user using the mobile network can be improved.

In order to facilitate understanding, the following describes a network attachment control method provided by an embodiment of the present invention through a specific application example. As shown in Figure 2, the method includes the following steps:

Step S202: The mobile terminal receives an attach response during the current attach process.

When the mobile terminal is turned on, restarted, or switched from flight mode to normal working mode, network attachment is required. Only after the mobile terminal completes the network attachment can the services provided by the mobile network be used. For example, after the mobile terminal is turned on, it will search for connectable networks. If several connectable networks are found, you can select one of them as the target network. The target network can be understood as a radio access network, including a radio network controller and a cell base station. After determining the target network, the mobile terminal first sends an attachment request to the target network. For example, a mobile terminal sends a network attachment request to a cell base station. In order to avoid network attachment conflicts, the attachment request carries a transaction identifier, which is used to identify a transaction during the network attachment process. For example, the first attachment request sent by a mobile terminal carries a transaction identifier. PTI1.

After the target network receives the first attachment request sent by the mobile terminal, it performs mutual authentication with the mobile terminal, NAS (Non-access Stratum, non-access stratum) security negotiation, and ESM (EPSSession Management, enhanced session management) information. Send. In the above process, the information interaction between the mobile terminal and the target network all carries PTI1.

During the above attachment process, the mobile terminal will record all information interacting with the target network, including PTI1, which is called the first attachment information. After completing the above process, the mobile terminal waits for the attach response returned by the target network. If the mobile terminal does not receive an attach response within the set time, it will resend the attach request.

If the mobile terminal sends a new attach request, that is, a second attach request, the second attach request carries a transaction identifier PTI2. The mobile terminal correspondingly saves the second attachment information, including PTI2. The second attachment information covers the above-mentioned first attachment information. Therefore, the transaction identifier corresponding to the network attachment recorded by the mobile terminal at this time is PTI2. At this time, if the mobile terminal receives the attach response returned by the target network, it will perform the following step S204.

In step S204, it is checked whether the PTI carried in the attachment response is the same as the PTI carried in the last attachment request sent; if yes, step S206 is performed; if not, step S208 is performed.

When the attachment response returned by the target network is received, the PTI carried in the attachment response is extracted, and the extracted PTI is compared with the PTI recorded by the mobile terminal. The PTI recorded by the mobile terminal is the PTI carried by the latest attachment request sent by the mobile terminal.

In step S206, the network attachment is completed according to the attachment response.

If the PTI carried by the attach response is the same as the PTI recorded by the mobile terminal, the default bearer activation operation is performed according to the attach response to complete the network attachment.

Step S208: Set the preset PTI matching identifier to the first specified value.

The PTI matching identifier is set in advance. For example, the PTI matching identifier can be set when the mobile terminal is initialized or the network attachment process is started, and the initial value of the PTI matching identifier is set to the second specified value. The second specified value may be 0. For example, when the mobile terminal is powered on and initialized, the PTI matching flag pti_miss = 0 is set.

If the PTI carried by the received attachment response is different from the PTI recorded by the mobile terminal, the preset PTI matching identifier is set to the first specified value to record that the cause of the attachment failure is a PTI conflict. The first specified value may be 1. For example, when a PTI conflict is detected, the PTI match flag pti_miss = 1 is set.

For example, following the above description, after sending the second attachment request, the mobile terminal receives the attachment response returned by the target network, and extracts the transaction identifier PTI1 carried by the attachment response, and PTI1 is inconsistent with the transaction identifier PTI2 recorded by the mobile terminal. , The mobile terminal will set the PTI matching identifier pti_miss = 1.

In step S210, the attach request is repeatedly sent until a detach message is received from the target network.

The step of repeatedly sending the attach request may be located before step S208, or after step S208, or performed simultaneously with step S208. When a new attach request is sent, the PTI carried by the new attach request is incremented on the basis of the PTI carried by the last sent attachment request. That is, the PTI carried in the first attachment request sent by the mobile terminal during each attachment process is the initial value (such as PTI1), and thereafter the PTI carried by each attachment request is sequentially increased from the initial value, such as the second attachment The PTI carried in the request is PTI2, the PTI carried in the third attach request is PTI3, and so on.

In step S212, it is detected whether the PTI matching identifier is the first specified value; if so, step S216 is performed; if not, step S214 is performed.

If a detach message is received from the target network, the network attach function will not be disabled directly. Instead, it is first detected whether the PTI matching identifier is the first specified value. When the first specified value is 1, if pti_miss = 1 is detected, it can be determined that the cause of the attachment failure is a PTI conflict; if pti_miss = 0 is detected, it can be determined that the cause of the attachment failure is not a PTI conflict.

Considering that during the network attachment process, the detach message sent by the target network carries the detach type identifier. Currently, the more commonly used detach type identifiers mainly include allow reattach (0x1), prohibit reattach (0x2) and IMSI (InternationalMobileSubscriberIdentificationNumber , International Mobile Subscriber Identity) to detach (0x3). Wherein, if the detach type identifier in the detach message is 0x1, it indicates that the cause of the detach is a temporary abnormality, and the mobile terminal may send an attach request again to reconnect to the target network. If the detach type identifier in the detach message is 0x2, it indicates that the target network prohibits the mobile terminal from sending the attach request again due to a network-side reason or other reasons (such as a PTI conflict). If the detach type identifier in the detach message is 0x3, it indicates that the cause of the detach is the IMSI code abnormality, for example, the IMSI code fails authentication.

Optionally, in order to save energy consumption, the mobile terminal does not need to detect whether the PTI matching identifier is the first specified value each time it receives the detach message. The mobile terminal may detect whether the PTI match identifier is the first specified value only when the detach type identifier in the received detach message is 0x2.

Step S214 is performed according to the related technology.

Step S216: Set the PTI matching identifier to the second specified value.

In step S218, the next attachment process is re-initiated.

If the PTI match identifier is the second specified value, the network attachment function can be disabled according to the existing rules, and no attachment request is sent. If the PTI matching identifier is the first specified value, the network attachment function is not disabled, but the PTI matching identifier is set to the second specified value, and the next round of attaching process is re-initiated. For example, if pti_miss = 1 is detected, then pti_miss = 0 is set and the next attach process is re-initiated. The transaction identifier carried by the first attach request in the new attach process is still the initial value PTI1. The transaction identifier carried by the attached request is incremented in turn.

The sequence of the above steps S206 and S208 may be reversed.

Optionally, if the number of rounds for initiating the attachment process reaches a set number of rounds, the network attachment function may be disabled and a new round of attachment process may not be initiated to save power of the mobile terminal.

In the above network attachment control method, during the current attachment process, if the mobile terminal receives an attachment response, it will check whether the PTI carried in the attachment response is the same as the PTI carried in the last attachment request sent. If they are different, match the preset PTI. The flag is set to the first specified value, and the attach request is repeatedly sent. When receiving the detach message sent by the target network, check whether the PTI match identifier is the first specified value. If it is, it indicates that the cause of the attachment failure is a PTI conflict, then re-initiate the next round of attach process so that the mobile terminal can complete the network. Attach process. Therefore, the phenomenon that the mobile terminal cannot be attached to the target network due to the conflict of transaction identifiers can be reduced, and the communication experience of the user using the mobile network can be improved.

FIG. 3 shows a flowchart of interaction between a mobile terminal and a target network during a network attachment process according to an embodiment of the present invention. As shown in FIG. 3, the network attachment process of the mobile terminal includes the following steps:

(1) After the mobile terminal determines the target network, it sends an attachment request to the target network. The attachment request carries information such as a transaction identifier PTI1 and a user identifier.

(2) After receiving the attach request, the target network performs mutual authentication with the mobile terminal. The target network determines the identity of the mobile terminal by using the mobile terminal's user identification and other information, and sends the target network's network identification and other information to the mobile terminal. Enables the mobile terminal to determine the identity of the target network.

(3) NAS security negotiation and ESM information transmission are conducted between the target network and the mobile terminal, and agreement on communication security protocols and data formats followed by the communication process between the two parties is stipulated.

(4) The target network assigns a temporary identification and IP address to the mobile terminal, creates communication context information, and generates a default bearer, and sends an attachment response containing the default bearer to the mobile terminal. During this period, the mobile terminal will wait for the target network to return the attach response. If the mobile terminal does not receive the attach response returned by the target network within the prescribed first set time period. The mobile terminal will resend the attach request, and the second attach request carries the transaction identifier PTI2.

(5) After the mobile terminal resends the network attachment request, if the target network returns an attachment response to the mobile terminal, the transaction identifier carried by the attachment response is PTI1. The mobile terminal receives the attach response. After comparison, it is determined that the transaction identifier PTI1 of the attachment response is inconsistent with the transaction identifier PTI2 of the latest attachment request sent, the cause of the attachment failure is recorded as a PTI conflict, and a new attachment request is resent.

(6) If the mobile terminal receives the detach message sent by the target network, determine whether the cause of the attachment failure is a PTI conflict; if so, start a new round of attachment requests to enable the mobile terminal to complete the network attachment process. The transaction identifier carried in the first attachment request in the new round of attachment process is still PTI1.

It should be noted that the same or similar parts between the foregoing method embodiments are not repeatedly described, and reference may be made to each other.

An embodiment of the present invention further provides a network attachment control device corresponding to the foregoing method embodiment, which is applied to a mobile terminal. As shown in Figure 4, the device includes:

A cause determination module 41 is configured to check whether the cause of the attachment failure is a transaction identifier PTI conflict if a detach message sent by the target network is received during the current attachment process;

A request update module 42 is used to re-initiate the next round of attach process if the cause of the attach failure is a transaction identifier PTI conflict; wherein the PTI carried by the attach request in each round of attach process is sequentially increased from the initial value.

Optionally, as shown in FIG. 5, the above device may further include a recording module 51.

A recording module 51 is used to check whether the PTI carried by the attachment response is the same as the PTI carried by the most recently sent attachment request when the mobile terminal receives the attachment response during the current attachment process; if the PTI carried by the latest attachment request is different, the reason for recording the attachment failure is a transaction Identifies a PTI conflict.

The recording module 51 may be further configured to: set a preset PTI matching identifier to a first specified value; wherein the initial value of the PTI matching identifier is a second specified value.

The recording module 51 may be further configured to: clear the cause of the attachment failure when re-initiating the next attachment process. Alternatively, when the next attach process is re-initiated, the PTI matching identifier is set to the second specified value.

In the above-mentioned network attachment control device provided by the embodiment of the present invention, during the current round of attachment process, if a detach message sent by the target network is received, it is checked whether the cause of the attachment failure is a PTI conflict. If the cause of the attachment failure is a PTI conflict, the next round of attachment process is re-initiated to enable the mobile terminal to complete the network attachment process. Therefore, the phenomenon that the mobile terminal cannot be attached to the target network due to the conflict of transaction identifiers can be reduced, and the communication experience of the user using the mobile network can be improved.

The implementation principle and technical effect of the network attachment control device provided in this embodiment are the same as those of the foregoing method embodiments. For a brief description, the parts not mentioned in the device embodiments can refer to the corresponding content in the foregoing method embodiments. . The network attachment device has a function of realizing the behavior of the above network attachment control method. The functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

Corresponding to the above embodiments, an embodiment of the present invention further provides a mobile terminal. The mobile terminal may be a terminal device such as a mobile phone, a tablet computer, a Point of Sale (POS), a vehicle-mounted computer, and a smart wearable device.

FIG. 6 shows a structural block diagram of a mobile terminal according to an embodiment of the present invention. As shown in FIG. 6, for convenience of explanation, only the parts related to the embodiment of the present invention are shown, and specific technical details are not disclosed, please refer to the method part of the embodiment of the present invention. The mobile terminal 100 includes: a radio frequency (RF) circuit 110, a memory 120, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a wireless fidelity (WiFi) module 170, a processor 180, And power supply 190 and other components. Those skilled in the art can understand that the structure of the mobile terminal 100 shown in FIG. 6 does not constitute a limitation on the mobile terminal 100, and may include more or fewer components than shown in the figure, or combine some components, or different components. Layout.

Each component of the mobile terminal 100 is specifically described below with reference to FIG. 6:

The RF circuit 110 may be used for receiving and sending signals during the process of receiving and sending information or during a call. In particular, the downlink information of the base station is received and processed by the processor 180; in addition, the uplink data of the design is sent to the base station. Generally, the RF circuit 110 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuit 110 can also communicate with a network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including, but not limited to, Global System of Mobile (GSM), General Packet Radio Service (GPRS), and Code Division Multiple Access Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), E-mail, Short Messaging Service (SMS), etc. Although FIG. 6 shows the RF circuit 110, it can be understood that it does not belong to the necessary configuration of the mobile terminal 100, and can be omitted as needed without changing the essence of the invention.

The memory 120 may be used to store software programs and modules, such as the network attachment control method and program instructions / modules corresponding to the devices in the embodiments of the present invention. The processor 180 executes the mobile terminal 100 by running the software programs and modules stored in the memory 120. Various functional applications and data processing, such as the network attachment control method provided by the embodiment of the present invention. The memory 120 may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), etc .; the storage data area may store data according to The mobile terminal 100 uses the created data (such as audio data, phonebook, etc.) and the like. In addition, the memory 120 may include a high-speed random access memory, and may further include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.

The input unit 130 may be configured to receive inputted numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal 100. Specifically, the input unit 130 may include a touch panel 131 and other input devices 132. The touch panel 131, also known as a touch screen, can collect user's touch operations on or near it (for example, the user uses a finger, a stylus or any suitable object or accessory on the touch panel 131 or near the touch panel 131. Operation), and drive the corresponding connection device according to a preset program. Optionally, the touch panel 131 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch position, and detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into contact coordinates, and sends it It is given to the processor 180, and can receive the command sent by the processor 180 and execute it. In addition, various types such as resistive, capacitive, infrared, and surface acoustic wave can be used to implement the touch panel 131. In addition to the touch panel 131, the input unit 130 may further include other input devices 132. Specifically, the other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 140 may be configured to display information input by the user or information provided to the user and various menus of the mobile terminal 100. The display unit 140 may include a display panel 141. Optionally, the display panel 141 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an organic light emitting diode (Organic Light-Emitting Diode, OLED), and the like. Further, the touch panel 131 may cover the display panel 141. When the touch panel 131 detects a touch operation on or near the touch panel 131, the touch panel 131 transmits the touch operation to the processor 180 to determine the type of the touch event. Type to do processing. Although in FIG. 6, the touch panel 131 and the display panel 141 are implemented as two independent components to implement the input and input functions of the mobile terminal 100, in some embodiments, the touch panel 131 and the display panel 141 may be used. Integrated to implement the input and output functions of the mobile terminal 100.

The mobile terminal 100 may further include at least one sensor 150, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor may adjust the brightness of the display panel 141 according to the brightness of the ambient light. The proximity sensor may close the display panel 141 when the mobile terminal 100 moves to the ear. And / or backlight. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when it is stationary. , Related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc. As for the mobile terminal 100, other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. I will not repeat them here.

The audio circuit 160, the speaker 161, and the microphone 162 may provide an audio interface between the user and the mobile terminal 100. The audio circuit 160 may transmit the received electrical data converted electric signal to the speaker 161, and the speaker 161 converts it into a sound signal for output. On the other hand, the microphone 162 converts the collected sound signal into an electric signal, and the audio circuit 160 After receiving, it is converted into audio data, and then the audio data output processor 180 is processed and then sent to, for example, another mobile terminal 100 via the RF circuit 110, or the audio data is output to the memory 120 for further processing.

WiFi is a short-range wireless transmission technology. The mobile terminal 100 can help users send and receive emails, browse web pages, and access streaming media through the WiFi module 170. It provides users with wireless broadband Internet access.

The processor 180 is a control center of the mobile terminal 100, and connects various parts of the entire mobile terminal 100 by using various interfaces and lines, and runs or executes software programs and / or modules stored in the memory 120 and calls stored in the memory 120 To perform various functions of the mobile terminal 100 and process the data, thereby performing overall monitoring of the mobile terminal 100. Optionally, the processor 180 may include one or more processing units; optionally, the processor 180 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and an application program. Etc., the modem processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 180.

The mobile terminal 100 also includes a power source 190 (such as a battery) for supplying power to various components. Optionally, the power source can be logically connected to the processor 180 through a power management system, thereby implementing management of charging, discharging, and power consumption management through the power management system. Features.

It can be understood that the structure shown in FIG. 6 is only schematic, and the mobile terminal 100 may further include more or fewer components than those shown in FIG. 6, or have a different configuration from that shown in FIG. 6. The components shown in FIG. 6 can be implemented by hardware, software, or a combination thereof.

Further, an embodiment of the present invention further provides a machine-readable storage medium that stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions cause The processor implements the network attachment control method described above.

It should be noted that the foregoing embodiments are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments are not described repeatedly. See each other.

The network attachment control method, device and mobile terminal provided by the embodiments of the present invention have the same technical characteristics, can also solve the same technical problems, and achieve the same technical effect.

It should be noted that in this article, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or operations The existence of any such actual relationship or order cannot be understood as indicating or implying relative importance. Moreover, the terms "including", "comprising", or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or device that includes a series of elements includes not only those elements but also those that are not explicitly listed Or other elements inherent to such a process, method, article, or device. Without more restrictions, the elements defined by the sentence "including a ..." do not exclude the existence of other identical elements in the process, method, article, or equipment that includes the elements.

The above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention. It should be noted that similar reference numerals and letters indicate similar items in the following drawings, so once an item is defined in one drawing, it need not be further defined and explained in subsequent drawings.

The above are only specific embodiments of the present invention, but the scope of protection of the present invention is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present invention. It should be covered by the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

The embodiment of the invention also discloses:

A1. A network attachment control method applied to a mobile terminal, the method comprising:

During the current attachment process, if a detach message is received from the target network, check whether the cause of the attachment failure is a PTI conflict in the transaction identifier;

If yes, re-initiate the next round of attachment process; among them, the PTI carried by the attachment request in each round of attachment process is sequentially increased from the initial value.

A2. The method according to A1, further comprising:

When the mobile terminal receives an attach response during the current attach process, it checks whether the PTI carried in the attach response is the same as the PTI carried in the last attach request sent;

If they are different, the reason for the record attachment failure is the conflict of transaction identifier PTI.

A3. The method according to A2, wherein the reason why the record attachment fails is a step of conflicting transaction identifier PTIs, including:

The preset PTI matching identifier is set to a first specified value; wherein the initial value of the PTI matching identifier is a second specified value.

A4. The method according to A3, further comprising:

When the next attach process is re-initiated, the PTI matching identifier is set to the second specified value.

A5. The method according to A2, further comprising:

When the next attachment process is re-initiated, the cause of the attachment failure is cleared.

A6. According to the method of A1, the detachment type identifier carried in the detachment message sent by the target network is forbidden to attach again.

B7. A network attachment device applied to a mobile terminal, the device comprising:

A cause determination module is used to check whether the cause of the attachment failure is a PTI conflict in the transaction identifier if a detach message is received from the target network during the current attachment process;

A request update module is used to re-initiate the next round of attachment process if the cause of the attachment failure is a conflict of transaction identifier PTI; among them, the PTI carried by the attachment request in each round of attachment process is sequentially increased from the initial value.

B8. The device according to B7, further comprising:

A recording module, configured to check whether the PTI carried by the attachment response is the same as the PTI carried by the most recent attachment request sent when the mobile terminal receives an attachment response during the current round of attachment; if they are different, record the The reason is that the transaction ID PTI conflicts.

B9. The device according to B8, the recording module is further configured to:

The preset PTI matching identifier is set to a first specified value; wherein the initial value of the PTI matching identifier is a second specified value.

B10. The device according to B9, the recording module is further configured to:

When the next attach process is re-initiated, the PTI matching identifier is set to the second specified value.

B11. The device according to B8, the recording module is further configured to:

When the next attachment process is re-initiated, the cause of the attachment failure is cleared.

C12. A mobile terminal, comprising a memory and a processor, where the memory is configured to store a program that supports a processor to execute the method of any of A1 to A6, and the processor is configured to execute the memory. Stored programs.

D13. A machine-readable storage medium storing computer software instructions for use in the apparatus of any one of B7 to B11.

Claims (20)

A network attachment control method, which is applied to a mobile terminal, and the method includes: During the current attachment process, if a detach message is received from the target network, check whether the cause of the attachment failure is a PTI conflict with the transaction identifier; If yes, re-initiate the next round of attachment process; among them, the PTI carried by the attachment request in each round of attachment process is sequentially increased from the initial value. The method of claim 1, further comprising: When the mobile terminal receives an attach response during the current attach process, it checks whether the PTI carried in the attach response is the same as the PTI carried in the last attach request sent; If they are different, the reason for the record attachment failure is the conflict of transaction identifier PTI. The method according to claim 2, wherein the reason why the record attachment fails is the step of conflicting transaction identifier PTIs, comprising: The preset PTI matching identifier is set to a first specified value; wherein the initial value of the PTI matching identifier is a second specified value. The method according to claim 3, wherein the method further comprises: When the next attachment process is re-initiated, the PTI matching identifier is set to the second specified value. The method according to claim 2, wherein the method further comprises: When the next attachment process is re-initiated, the cause of the attachment failure is cleared. The method according to claim 2, wherein the reason why the record attachment fails is the step of conflicting transaction identifier PTIs, comprising: The reason why the attachment failure is recorded in the specified position in the memory is that the transaction identifier PTI conflicts. The method according to claim 2, wherein the checking whether the cause of the attachment failure is a transaction identifier PTI conflict comprises: Traverse the reasons for each attachment failure recorded during the current attachment process; If the cause of the attachment failure recorded at least once is a PTI conflict, it is determined that the cause of the attachment failure is a PTI conflict. The method according to claim 1, wherein the detachment type identifier carried in the detachment message sent by the target network is forbidden to attach again. The method according to claim 8, wherein if the detach message sent by the target network is received, checking whether the cause of the attachment failure is a transaction identifier PTI conflict comprises: If a detach message sent by the target network is received, detecting whether the detach type identifier in the detach message is the forbidden re-attach; If yes, check whether the cause of the attachment failure is a conflict of transaction identifier PTI. The method according to claim 1, wherein, if it is, re-initiating a next round of attachment process comprises: If yes, check whether the number of rounds to initiate the attachment process reaches the set number of rounds; If the set number of rounds is not reached, the next round of attachment process is re-initiated. A network attachment device, which is applied to a mobile terminal, and the device includes: A cause determination module is used to check whether the cause of the attachment failure is a PTI conflict in the transaction identifier if a detach message is received from the target network during the current attachment process; A request update module is used to re-initiate the next round of attachment process if the cause of the attachment failure is a conflict of transaction identifier PTI; among them, the PTI carried by the attachment request in each round of attachment process is sequentially increased from the initial value. The apparatus according to claim 11, wherein the apparatus further comprises: A recording module, configured to check whether the PTI carried by the attachment response is the same as the PTI carried by the most recent attachment request sent when the mobile terminal receives an attachment response during the current round of attachment; if they are different, record the The reason is that the transaction ID PTI conflicts. The device according to claim 12, wherein the recording module is further configured to: set a preset PTI matching identifier to a first specified value; wherein the initial value of the PTI matching identifier is a second specified value. The apparatus according to claim 12, wherein the recording module is further configured to: when re-initiating the next round of attachment process, clear the cause of the attachment failure; and / or, when re-initiating the next round of attachment process, The PTI matching identifier is set to the second specified value. The device according to claim 12, wherein the recording module is specifically configured to: record the cause of the attachment failure at a specified location in the memory as a conflict of transaction identifier PTI. The apparatus according to claim 11, wherein the cause determination module is specifically configured to: Traverse the reasons for each attachment failure recorded during the current attachment process; If the cause of the attachment failure recorded at least once is a PTI conflict, it is determined that the cause of the attachment failure is a PTI conflict. The apparatus according to claim 11, wherein the cause determination module is specifically configured to: If a detachment message sent by the target network is received, detecting whether the detachment type identifier in the detachment message is forbidden to reattach; If yes, check whether the cause of the attachment failure is a conflict of transaction identifier PTI. The apparatus according to claim 11, wherein the request update module is specifically configured to: If the cause of the attachment failure is a conflict in the transaction identifier PTI, check whether the number of rounds to initiate the attachment process reaches the set number of rounds; If the set number of rounds is not reached, the next round of attachment process is re-initiated. A mobile terminal comprising a memory and a processor, where the memory is configured to store a program that supports a processor to execute the method of any one of claims 1 to 10, and the processor is configured to execute the Program stored in memory. A machine-readable storage medium storing computer software instructions for use in the apparatus of any one of claims 11 to 18.

Images