CN109195217B

CN109195217B - Method and device for processing LTE network rejection behavior

Info

Publication number: CN109195217B
Application number: CN201811238856.7A
Authority: CN
Inventors: 李伟清
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2018-10-23
Filing date: 2018-10-23
Publication date: 2021-06-04
Anticipated expiration: 2038-10-23
Also published as: CN109195217A

Abstract

The disclosure relates to the technical field of wireless communication, and in particular relates to a method for processing an LTE network rejection behavior, a device for processing the LTE network rejection behavior, a computer-readable medium, and a wireless communication terminal. The method comprises the following steps: analyzing the received original network rejection information to judge whether the original network rejection information is preset network rejection information or not; when the original network rejection information is the preset network rejection information, replacing the original network rejection information with mapping network rejection information; and processing the mapping network rejection information to cause the terminal equipment to re-register the network. The method and the device can enable the terminal device to obtain more chances of trying to register in the network, and effectively avoid the situation that the terminal device cannot reside in the network due to the original network rejection information.

Description

Method and device for processing LTE network rejection behavior

Technical Field

The disclosure relates to the technical field of wireless communication, and in particular relates to a method for processing an LTE network rejection behavior, a device for processing the LTE network rejection behavior, a computer-readable medium, and a wireless communication terminal.

Background

The fourth Generation mobile communication technology (4G) currently includes TD-LTE and FDD-LTE systems. With the popularization and the improvement of the LTE network, more users choose to use the LTE network for various services.

However, there are some problems in the use process of the LTE network, for example, the user terminal may not use the network in the normal use process of the LTE service, and needs to restart the mobile phone or restart and close the flight mode; even in some cases, the use cannot be resumed by restarting the handset or turning the flight mode on and off. The above situation is mostly caused by network reasons, but users are likely to misunderstand that the terminal device itself has a serious problem. The quality reliability of the terminal equipment is questioned by the user while the user is influenced to use the network service.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The present disclosure is directed to a method for processing an LTE network rejection behavior, an apparatus for processing an LTE network rejection behavior, a computer-readable medium, and a wireless communication terminal, which overcome at least some of the problems of unavailability of an LTE network due to the limitations and disadvantages of the related art.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.

According to a first aspect of the present disclosure, a method for processing LTE network rejection behavior is provided, including:

analyzing the received original network rejection information to judge whether the original network rejection information is preset network rejection information or not;

when the original network rejection information is the preset network rejection information, replacing the original network rejection information with mapping network rejection information;

and processing the mapping network rejection information to cause the terminal equipment to re-register the network.

According to a second aspect of the present disclosure, there is provided an apparatus for processing LTE network rejection behavior, including:

the analysis module is used for analyzing the received original network rejection information so as to judge whether the original network rejection information is preset network rejection information or not;

a replacement module, configured to replace the original network rejection information with mapped network rejection information when the original network rejection information is the preset network rejection information;

and the processing module is used for processing the mapping network rejection information so as to enable the terminal equipment to re-register the network.

According to a third aspect of the present disclosure, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements the above-described processing method of LTE network rejection behavior.

According to a fourth aspect of the present disclosure, there is provided a wireless communication terminal comprising:

one or more processors;

a storage device for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the above-described method of handling LTE network rejection behavior.

In the method for processing the LTE network rejection behavior provided in an embodiment of the present disclosure, when it is determined that the received original network rejection information is the preset network rejection information, the original network rejection information can be replaced with the preset mapping network rejection information, so that the terminal can process the mapping network rejection information. Therefore, the terminal equipment obtains more chances of trying to register in the network, and the situation that the terminal equipment cannot reside in the network and cannot use the network service due to the fact that the original network rejection information is effectively avoided.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

Fig. 1 is a timing diagram schematically illustrating a network side rejecting a terminal device attach request;

fig. 2 is a schematic diagram schematically illustrating a method for processing LTE network rejection behavior in an exemplary embodiment of the disclosure;

fig. 3 is a diagram schematically illustrating an attach request processing method when no location update occurs in an exemplary embodiment of the present disclosure;

fig. 4 is a diagram schematically illustrating an attach request processing method when a location update occurs in an exemplary embodiment of the present disclosure;

fig. 5 is a timing diagram schematically illustrating a method for processing LTE network rejection in an exemplary embodiment of the present disclosure;

fig. 6 is a schematic diagram illustrating a composition of a device for processing LTE network rejection behavior in an exemplary embodiment of the disclosure;

fig. 7 schematically shows a structural diagram of a computer system of a wireless communication device in an exemplary embodiment of the disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The existing LTE network service has some problems and deficiencies in the use process, for example, a user terminal can not use the network in the normal use process of the LTE service, and needs to restart a mobile phone or restart and close a flight mode; even in some cases, the use cannot be resumed by restarting the handset or turning the flight mode on and off. The root cause is that after the terminal device sends the registration request to the network side, the network side rejects the registration request and returns corresponding rejection information to the terminal device. The terminal device performs corresponding processing according to the rejection information and enters an exception handling scenario, and a PS domain (Packet Switch) of the terminal device is invalid, so that the terminal device cannot normally use the data service.

In view of the above drawbacks and deficiencies of the prior art, the exemplary embodiment provides a method for handling LTE network rejection behavior, which may be applied to an intelligent terminal device capable of LTE communication, such as a mobile phone and a tablet computer, and may be applied to a rejection scenario in which the terminal device receives ATTACH rejection (ATTACH REJECT) or tracking area UPDATE rejection (TRACKING AREA UPDATE REJECT) on the network side. Referring to fig. 2, the method for processing the LTE network rejection behavior may include the following steps:

s11, analyzing the received original network rejection information to judge whether the original network rejection information is preset network rejection information;

s12, when the original network rejection information is the preset network rejection information, replacing the original network rejection information with mapping network rejection information;

and S13, processing the mapping network rejection information to cause the terminal device to re-register the network.

In the method for processing the LTE network rejection behavior provided by the present embodiment, when it is determined that the received original network rejection information is the preset network rejection information, the original network rejection information can be replaced with the preset mapping network rejection information, so that the terminal can process the mapping network rejection information. Therefore, the terminal equipment obtains more chances of trying to register in the network, and the situation that the terminal equipment cannot reside in the network and cannot use the network service due to the fact that the original network rejection information is effectively avoided.

Hereinafter, each step of the processing method for the LTE network rejection behavior in the present exemplary embodiment will be described in more detail with reference to the drawings and the embodiments.

Generally, an LTE Core network (EPC) mainly includes: MME (Mobility Management Entity), SGW (Serving Gateway), PGW (PDN Gateway), PCRF (Policy and Charging Rules Function), and other network elements. The MME is responsible for access functions of the user plane, such as mobility management, bearer management, authentication and authentication of the user, and selection of the SGW and the PGW.

When a user uses a data service through a terminal device, for example, before the user uses a mobile phone to surf the internet and browse a web page through a 4G network, the terminal device needs to send an attach request to a network side and register the terminal device in the network when the attach is successful. Or when the terminal equipment is started or the position of the terminal equipment changes and a cell or a tracking area needs to be changed, a new attachment request needs to be sent to the network side.

In the attach process, the terminal device registers the relevant information of the terminal in the network, and establishes a default bearer between the terminal device and a PGW (PDN GateWay), so that the terminal device is online.

Step S11, analyzing the received original network rejection information to determine whether the original network rejection information is a preset network rejection information.

In this exemplary embodiment, in an actual operation process, a User Equipment (UE) is required to register UE information with an Evolved Packet Core (EPC), and only after the registration is successful, the UE may initiate a business, initiate a call, and perform a corresponding paging.

Specifically, referring to fig. 1, when the ue registers an EPS (Evolved Packet System) service with an EPC in PS (Packet Switch) mode, the ue registers the EPS service with an attach procedure and sends an attach request (attach request) to the network side. If the network side can not accept the Attach request, it returns Attach Reject information (Attach Reject) to the terminal, and the Reject information contains an appropriate EMM (EPS Mobility Management ) Cause, i.e. Reject code.

For the terminal device, it may be determined whether the attach rejection information is the preset network rejection information according to the rejection code included in the attach rejection information. The preset network rejection information may include: the terminal is made to invalidate the EPS service and/or non-EPS service until the power is turned off or the rejection of a UICC Card (Universal Integrated Circuit Card) containing a USIM (subscriber identity Card) is removed.

For example, the preset network rejection information includes a rejection code of any one of the following items: #7, evolved packet system EPS service not allowed (EPS services not allowed); #8, both EPS services and non-EPS services are not allowed (EPS services and non-EPS services not allowed); #14, EPS service is not allowed in this PLMN (EPS services not allowed in this PLMN). #11, public land mobile network, PLMN, not allowed (PLMN not allowed); #16, MSC service temporarily unreachable (MSC temporal unreachable); #6, illegal ME (Illegal ME); #10, implicit detached (Implicitly detached), and ESM rejection reason (ESM Reject Cause) value # 28; and #0, the rejection information fed back when the network side processes the user registration is not standardized.

For example, for the application scenario ubiquitous in the global network, after sending a registration request to the core network, a legal terminal device is often rejected by the network side for the reason #7, #8, or # 14. When the network side rejects the terminal device for the reasons, the PS domain of the terminal device is immediately invalid and the LTE network cannot camp on the PS domain only once. In addition, if the user tries to use the LTE network again, the terminal device must be restarted or the card must be plugged in and out. And the user can often recover to use the LTE network after restarting the terminal equipment, which is not consistent with the reason why the network refuses the mobile phone (#7, #8 or # 14). Therefore, when the network is not faulty, the legitimate ue is rejected by the network during one registration, and it is determined that it is unreasonable not to allow the EPS service to be used.

In addition, for the domestic network environment, because the network coverage area of the operator is wide, a plurality of EHPLMNs (local public land mobile networks) may exist in the same operator. For example, 460/00, 460/02, 460/07, and 460/08 all belong to mobile networks. Under the environment of a normal mobile network, the terminal equipment using the service of the operator can normally use the service in the environment of the mobile network. However, the core network does not recognize the new EHPLMN user, so that the terminal device is rejected by the core network for the reason # 11. At this time, the USIM card on the terminal device may be disabled, the terminal device may not use the network service of the operator, and the restart of the terminal device is also invalid.

Further, when the USIM card provided by the home operator uses the roaming service abroad, there may be a case where the terminal device is rejected by the operator legally signed for roaming # 11. The signed PLMN is caused to be written into the FPLMN list of the SIM card, so that the terminal equipment has no service in a roaming place; and no service is available after the terminal equipment is restarted.

In addition, as the deployment range of the LTE network is continuously expanded, a certain number of LTE pseudo base stations also start to appear, which affects the use of normal users. Some of the features that have been identified are: when a legal terminal user is registered in the domestic network environment, the legal terminal user is rejected by the network side for the reason of #10, and the rejection code of the ESM reject cause is # 28; or, when the terminal user registers the network and is rejected by the network side with the non-normative reason #0, it indicates that the terminal may encounter the fake base station when registering the network.

In addition, in an embodiment, when the reject code in the original network reject message is #16, that is, the user terminal fails to request the network side for the joint attach. At this time, the number of times the terminal device is rejected by the network side may also be marked. If the number of times of continuous rejection of the terminal equipment by the network side by the rejection code #16 reaches a preset threshold, for example, setting the threshold as 2, 3 or 4 times; the cell corresponding to the network rejection information may be marked so that the cell may be barred in a subsequent step and no longer attempts to camp on the cell.

Step S12, when the original network rejection information is the preset network rejection information, replacing the original network rejection information with the mapped network rejection information.

In this exemplary embodiment, the mapping network rejection information may include: enabling the terminal to make a limited number of attempts to register for rejection information of the network. Specifically, the mapping network rejection information may be: #15, there is No suitable network in the tracking area (No able cells in tracking area).

If the original rejection information is detected to be the preset network information according to the EMM Cause contained in the original network rejection information, the current rejection information can be replaced by the mapping network rejection information. For example, only the reject code in the original network reject message may be replaced with #15 as described above, and there is no suitable network in the tracking area; thereby obtaining the rejection information of the mapping network at the rear end of the replacement EMM Cause.

Step S13, the mapping network rejection information is processed to re-register.

In this exemplary embodiment, after replacing the original network rejection information with the mapped network rejection information, the network rejection information with the EMM Cause value of #15 may be processed.

Specifically, when network rejection information with a rejection code of #15 is processed, the terminal device needs to set an EPS update status to EU3ROAMING NOT ALLOWED (ROAMING is NOT ALLOWED); and deletes any GUTI (global Unique Temporary UE Identity), TAI (Tracking Area Identity) of the last access registration, and KSI information. In addition, the terminal device needs to reset an attach attempt counter or the like.

In an embodiment of the present disclosure, referring to fig. 2, the step S13 may include:

step S130, it is checked whether the current value of the attach attempt counter is within a preset range.

Specifically, after the terminal device replaces the original network rejection information with the mapped network rejection information, the current attach procedure (attach procedure) is terminated. And reads the current value of the attach attempt counter (attach attempt counter); if the current value of the attachment attempt counter is smaller than the preset value, the value of the counter can be increased, and corresponding processing is performed, for example, whether the terminal device is subjected to location updating is checked. The preset value may be, for example, a value of 3, 4, or 5, and the preset value may be determined according to an existing network protocol, and may also be a value defined by a user, which is not particularly limited in this disclosure.

In an embodiment of the present disclosure, referring to fig. 3, the step S13 may further include:

step S131, detecting whether the terminal equipment has a position updating behavior and leaves a corresponding area of an original TAI list to which the original network rejection information corresponds to the original tracking area;

step S133, if there is no location update behavior, acquiring an original tracking area corresponding to the original network rejection information and an original TAI list to which the original tracking area belongs;

step S134, attempting to send an attach request to other tracking areas in the original TAI list except the original tracking area.

A TA (Tracking Area) may cover one or more cells, and may mark a Tracking Area with TAI (Tracking Area identity). A plurality of TAIs may form a TAI list, and the TAI list may be allocated by an MME (Mobility Management Entity) network element and belongs to a tracking area of the same serving MME.

In an embodiment, when processing the mapping network rejection information, a TA (Tracking Area), i.e., an original Tracking Area, corresponding to the original network rejection information may be extracted first; and an original TAI corresponding to the original tracking area, and an original TAI list corresponding to the original TAI; and acquiring the current position information of the terminal equipment to judge whether the terminal equipment has position change. And if the position of the terminal equipment is not changed or is still located in the area corresponding to the original TAI list, not initiating position updating to the network side. And begins sending an attach request to any of the remaining tracking areas in the original TAI list to attempt to camp on a cell of the tracking area.

Or, the cell under other tracking areas searched by the network search also resides and tries to send the attachment request.

In another embodiment of the present disclosure, referring to fig. 4, the step S13 may further include:

step S132, when the terminal device has left the area corresponding to the original TAI list, the updated location information is notified to the core network to obtain the updated TAI list.

Specifically, after the location information of the terminal device is acquired, if it is determined that the terminal device has a location update, and has left the area range corresponding to the original TAI list and enters a new tracking area, the updated location information may be notified to the core network, so as to acquire a new TAI list corresponding to the location update, and start sending an attach request to any tracking area in the updated TAI list.

In an embodiment, the tracking area in the updated TAI list may be further identified, and it is checked whether there is an original tracking area corresponding to the original network rejection information or an original tracking area corresponding to other original network rejection information in the history. If the original tracking areas exist, the original tracking areas can be deleted from the updated TAI list, or the original tracking areas can be added into a preset forbidden TA list.

In other examples of the present disclosure, when processing is performed for #15, the original tracking area corresponding to the original network rejection information may also be saved to a prohibited TA list.

For example, when processing is performed for #15, the current pattern may be identified. For example, in S1mode, the terminal device may store the current TAI corresponding to the original network rejection information in a prohibited TA list of "prohibited tracking areas for roaming", and enter EMM DEREGISTERED LIMITED SERVICE (canceling EMM registration service) state. The terminal device will search for a suitable cell in different TAs or different LAs of the same PLMN (Public Land Mobile Network).

Referring to fig. 5, in the method provided by the embodiment of the present disclosure, when the terminal device receives the preset network rejection information, the rejection code in the preset network rejection information is replaced with #15, and new network rejection information is generated, so that the terminal device may perform subsequent operations according to the network rejection information including the rejection code #15, and can provide more opportunities for the terminal device to send an attach request to the network side, thereby increasing the probability of successful registration of the terminal device in the network. The situation that the terminal equipment needs to enter and exit the flight mode again or needs to restart the terminal equipment or even cannot use the network due to the fact that the terminal equipment receives the partial rejection code is effectively avoided.

It is to be noted that the above-mentioned figures are only schematic illustrations of the processes involved in the method according to an exemplary embodiment of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

Further, referring to fig. 6, in an embodiment of the present example, there is provided a processing apparatus 60 for LTE network rejection behavior, including: a parsing module 601, a replacing module 602, and a processing module 603. Wherein:

the parsing module 601 may be configured to parse the received original network rejection information, so as to determine whether the original network rejection information is preset network rejection information.

The replacing module 602 may be configured to replace the original network rejection information with mapped network rejection information when it is determined that the original network rejection information is the preset network rejection information.

The processing module 603 may be configured to process the mapping network rejection information for re-registration.

In one example of the disclosure, the preset network rejection information includes any one or more of:

#7, evolved packet system EPS service is not allowed;

#8, neither EPS services nor non-EPS services are allowed;

#14, EPS service is not allowed in this PLMN;

#11, public land mobile network, PLMN, is not allowed;

#6, illegal ME;

#16, MSC service is temporarily unreachable;

#10, implicit detach, and ESM reject cause value # 28;

#0, the rejection information fed back when the network side processes the user registration is not standardized.

In one example of the present disclosure, the mapping network rejection information includes:

#15, there is no suitable network in the tracking area.

In other examples of the disclosure, the processing module may include: a first list acquisition module and a first request sending module (not shown in the figure). Wherein the content of the first and second substances,

the first list obtaining module may be configured to obtain an original tracking area corresponding to the original network rejection information and an original TAI list to which the original tracking area belongs.

The first request sending module may be configured to attempt to send an attach request to a tracking area other than the original tracking area in the original TAI list.

In one example of the present disclosure, the processing module may further include: a location detection module and a second list acquisition module (not shown in the figure). Wherein the content of the first and second substances,

the location detection module may be configured to detect whether the terminal device has a location update behavior and has left a corresponding area of an original TAI list to which an original tracking area corresponding to the original network reject information belongs.

The second list obtaining module may be configured to notify the core network of the updated location information to obtain the updated TAI list when the terminal device has left the area corresponding to the original TAI list.

In one example of the present disclosure, the processing module further comprises: a second request sending module (not shown in the figure).

The second request sending module may be configured to read the updated TAI list and send an attach request to a tracking area in the updated TAI list.

In one example of the present disclosure, the processing module further comprises: tracking area verification module (not shown).

The tracking area verifying module may be configured to, when it is checked that an original tracking area corresponding to original network rejection information exists in the updated TAI list, clear the original tracking area from the updated TAI list.

In one example of the present disclosure, the processing module may further include: a counter check module (not shown).

The counter checking module may be configured to read a current value of an attach attempt counter; and when the current value of the attachment attempt counter is smaller than a preset value, sending an attachment request to a tracking area in the TAI list.

In an example of the present disclosure, the apparatus described above may further include: a forbidden list module (not shown in the figure).

The forbidden list module may be configured to store a tracking area corresponding to the original network rejection information in a forbidden TA list.

The specific details of each module in the processing apparatus 60 for LTE network rejection behavior are already described in detail in the corresponding processing method for LTE network rejection behavior, and therefore are not described herein again.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Fig. 7 illustrates a schematic block diagram of a computer system suitable for use with a wireless communication device to implement an embodiment of the present invention.

It should be noted that the computer system 700 of the electronic device shown in fig. 7 is only an example, and should not bring any limitation to the function and the scope of the application of the embodiment of the present invention.

As shown in fig. 5, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for system operation are also stored. The CPU 701, the ROM702, and the RAM 703 are connected to each other via a bus 704. An Input/Output (I/O) interface 705 is also connected to the bus 704.

The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a Network interface card such as a LAN (Local Area Network) card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.

In particular, according to an embodiment of the present invention, the processes described below with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program executes various functions defined in the system of the present application when executed by a Central Processing Unit (CPU) 701.

It should be noted that the computer readable medium shown in the embodiment of the present invention may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a flash Memory, an optical fiber, a portable Compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present invention may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method as described in the embodiments below. For example, the electronic device may implement the steps shown in fig. 2 to 4.

Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is to be limited only by the terms of the appended claims.

Claims

1. A method for processing LTE network rejection behavior is characterized by comprising the following steps:

the terminal equipment analyzes received original network rejection information sent by a network side to judge whether the original network rejection information is preset network rejection information or not;

when the original network rejection information is the preset network rejection information, replacing the original network rejection information with mapping network rejection information, and terminating an attachment procedure corresponding to the original network rejection information; and identifying the current mode, if in the mode of S1, the terminal equipment stores the current TAI corresponding to the original network rejection information into a forbidden TA list, and enters into a state of canceling EMM registration service;

acquiring an original tracking area corresponding to the original network rejection information and an original TAI list to which the original tracking area belongs; detecting whether the terminal equipment has a position updating behavior or not;

if the position updating behavior does not exist, trying to send an attachment request to other tracking areas except the original tracking area in the original TAI list; or

If the terminal equipment leaves the corresponding area of the original TAI list, the updated position information is notified to a core network to obtain an updated TAI list; reading the updated TAI list, and clearing the original tracking area in the updated TAI list when the updated TAI list is checked to have the original tracking area corresponding to the original network rejection information; and sending an attach request to the tracking area in the updated TAI list; to cause the terminal device to re-register with the network.

2. The method of claim 1,

the preset network rejection information includes: the terminal considers that the EPS service and/or the non-EPS service are invalid until the terminal is shut down or the rejection content of the user identification card is removed;

the mapping network rejection information includes: the terminal is caused to make a limited number of attempts to register the rejected content of the network.

3. The method of claim 1, wherein after obtaining the updated TAI list, the method further comprises:

and when the updated TAI list is checked to have an original tracking area corresponding to the original network rejection information, the original tracking area is eliminated from the updated TAI list.

4. The method of claim 1, wherein before sending an attach request to a tracking area in the TAI list, the method further comprises:

reading a current value of an attach attempt counter;

and when the current value of the attachment attempt counter is smaller than a preset value, sending an attachment request to a tracking area in the TAI list.

5. The method of claim 1, further comprising:

and storing the tracking area corresponding to the original network rejection information into a forbidden TA list.

6. An apparatus for processing LTE network rejection behavior, comprising:

the terminal equipment analyzes received original network rejection information sent by a network side so as to judge whether the original network rejection information is preset network rejection information or not;

a replacing module, configured to replace the original network rejection information with mapped network rejection information and terminate an attachment procedure corresponding to the original network rejection information when the original network rejection information is the preset network rejection information; and identifying the current mode, if in the S1mode, the terminal device stores the current TAI corresponding to the original network rejection information into a forbidden T list, and enters an EMM registration cancellation service state;

the processing module is used for acquiring an original tracking area corresponding to the original network rejection information and an original TAI list to which the original tracking area belongs; detecting whether the terminal equipment has a position updating behavior or not; if the position updating behavior does not exist, trying to send an attachment request to other tracking areas except the original tracking area in the original TAI list; or if the terminal device leaves the corresponding area of the original TAI list, the updated position information is notified to a core network to obtain an updated TAI list; reading the updated TAI list, and clearing the original tracking area in the updated TAI list when the updated TAI list is checked to have the original tracking area corresponding to the original network rejection information; and sending an attach request to the tracking area in the updated TAI list; to cause the terminal device to re-register with the network.

7. The LTE network rejection behavior processing apparatus according to claim 6,

8. The apparatus of claim 6, wherein the processing module further comprises:

and the tracking area checking module is used for clearing the original tracking area in the updated TAI list when the original tracking area corresponding to the original network rejection information exists in the updated TAI list.

9. The apparatus of claim 6, wherein the processing module further comprises:

a counter checking module for reading the current value of the attachment attempt counter; and when the current value of the attachment attempt counter is smaller than a preset value, sending an attachment request to a tracking area in the TAI list.

10. The apparatus of claim 6, further comprising:

and the forbidden list module is used for storing the tracking area corresponding to the original network rejection information into a forbidden TA list.

11. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out a method of handling LTE network rejection behavior according to any one of claims 1 to 5.

12. A wireless communication terminal, comprising:

one or more processors;

storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method of handling LTE network rejection behavior of any of claims 1 to 5.