Tracking Area Abnormal Handling Method and Device, Communication Device, and Storage Medium

Abstract

Embodiments of the present disclosure provide a method and apparatus for tracking area exception handling, a communication device, and a storage medium. The TA exception handling method executed by a network device may include: in response to determining that a TA exception occurs where the TA where the UE is currently located is outside the RA of the UE, recording the TA exception; and triggering an RA update of the UE based on the existence of the TA exception.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication technology, but is not limited to the field of wireless communication technology, and particularly relates to a method and apparatus for handling abnormal tracking areas (TAs), a communication device, and a storage medium. Background Art

[0002] When a user equipment (UE) initially connects to a network, it sends a registration request to the network, and the network side responds to the registration request. During the registration process, the network side records the registration area (RA) of the UE. Usually, the registration area contains one or more TAs. In some cases, the network side records the RA of the UE in the form of a TA list (TAL).

[0003] As the wireless cell or the UE moves, the UE may enter a new TA, and the new TA is not included in the tracking area identity (TAI) corresponding to the RA, and the UE does not perceive entering the new TA, so it does not initiate a registration update process to update the TA, which results in TA abnormality. Summary of the Invention

[0004] Embodiments of the present disclosure provide a method and apparatus for handling TA abnormality, a communication device, and a storage medium.

[0005] In a first aspect of the embodiments of the present disclosure, a method for handling TA abnormality is provided, which is executed by a network device. The method includes:

[0006] In response to determining that a TA abnormality occurs where the current TA where the UE is located is outside the RA of the UE, record the TA abnormality;

[0007] Based on the existence of the TA abnormality, trigger an RA update of the UE.

[0008] In a second aspect of the embodiments of the present disclosure, a device for handling TA abnormality is provided. The device includes:

[0009] A recording module, configured to record the TA abnormality in response to determining that a TA abnormality occurs where the current TA where the UE is located is outside the RA of the UE;

[0010] A triggering module, configured to trigger an RA update of the UE based on the existence of the TA abnormality.

[0011] In a third aspect of the embodiments of the present disclosure, a communication device is provided, including a processor, a transceiver, a memory, and an executable program stored on the memory and capable of being run by the processor. When the processor runs the executable program, it executes the method for handling TA abnormality provided in the foregoing first aspect.

[0012] In a fourth aspect of the embodiments of the present disclosure, a computer storage medium is provided, which stores an executable program; after being executed by a processor, the executable program can implement the TA exception handling method provided in the first aspect described above.

[0013] After discovering the TA exception of the UE, the technical solution provided by the embodiments of the present disclosure will record the TA exception of the UE. Based on the TA exception, the network side will actively trigger the UE to perform RA update, thereby eliminating the TA exception, and further suppressing the occurrence of exceptions associated with the location TA, such as paging failure caused by the TA exception.

[0014] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings herein are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present invention and used together with the specification to explain the principles of the embodiments of the present invention.

[0016] Figure 1 It is a schematic structural diagram of a wireless communication system shown according to an exemplary embodiment;

[0017] Figure 2 It is a schematic flowchart of a TA exception handling method shown according to an exemplary embodiment;

[0018] Figure 3 It is a schematic diagram of TA handover of a wireless cell shown according to an exemplary embodiment;

[0019] Figure 4 It is a schematic diagram of another TA handover of a wireless cell shown according to an exemplary embodiment;

[0020] Figure 5 It is a schematic flowchart of a TA exception handling method shown according to an exemplary embodiment;

[0021] Figure 6 It is a schematic flowchart of a TA exception handling method shown according to an exemplary embodiment;

[0022] Figure 7 It is a schematic flowchart of a TA exception handling method shown according to an exemplary embodiment;

[0023] Figure 8 It is a schematic flowchart of a TA exception handling method shown according to an exemplary embodiment;

[0024] Figure 9It is a schematic flow chart of a TA exception handling method shown according to an exemplary embodiment;

[0025] Figure 10 It is a schematic flow chart of a TA exception handling method shown according to an exemplary embodiment;

[0026] Figure 11 It is a schematic structural diagram of a TA exception handling device shown according to an exemplary embodiment;

[0027] Figure 12 It is a schematic structural diagram of a TA exception handling device shown according to an exemplary embodiment;

[0028] Figure 13 It is a schematic structural diagram of a UE shown according to an exemplary embodiment;

[0029] Figure 14 It is a schematic structural diagram of a network device shown according to an exemplary embodiment. Detailed implementation manners

[0030] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the embodiments of the present invention. On the contrary, they are only examples of devices and methods consistent with some aspects of the embodiments of the present invention as detailed in the appended claims.

[0031] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments, and are not intended to limit the embodiments of the present disclosure. The singular forms of "a", "an" and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0032] It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to determining".

[0033] Please refer to Figure 1, which shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure. As Figure 1 shown, the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: a plurality of UEs 11 and a plurality of access devices 12.

[0034] Among them, the UE 11 may be a device that provides voice and / or data connectivity to a user. The UE 11 may communicate with one or more core networks via a Radio Access Network (RAN). The UE 11 may be an Internet of Things (IoT) UE, such as a sensor device, a mobile phone (or referred to as a "cellular" phone), and a computer with an IoT UE. For example, it may be a fixed, portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted device. For example, a Station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, or a user equipment (UE). Or, the UE 11 may also be a device of an unmanned aerial vehicle. Or, the UE 11 may also be a vehicle-mounted device. For example, it may be an in-vehicle computer with wireless communication function, or a wireless communication device external to the in-vehicle computer. Or, the UE 11 may also be a roadside device. For example, it may be a street lamp, a traffic signal, or other roadside devices with wireless communication function.

[0035] The access device 12 may be a network-side device in the wireless communication system. Among them, the wireless communication system may be a fourth-generation mobile communication technology (4G) system, also known as the Long Term Evolution (LTE) system; or, the wireless communication system may also be a 5G system, also known as the new radio (NR) system or the 5G NR system. Or, the wireless communication system may also be the next-generation system of the 5G system. Among them, the access network in the 5G system may be referred to as the NG-RAN (New Generation-Radio Access Network, new generation wireless access network). Or, an MTC system.

[0036] Among them, the access device 12 may be an evolved access device (eNB) adopted in a 4G system. Alternatively, the access device 12 may also be an access device (gNB) with a centralized distributed architecture adopted in a 5G system. When the access device 12 adopts a centralized distributed architecture, it generally includes a central unit (CU) and at least two distributed units (DUs). The protocol stacks of the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer are set in the central unit; the Physical (PHY) layer protocol stack is set in the distributed unit. The specific implementation manner of the access device 12 in the embodiments of the present disclosure is not limited.

[0037] A wireless connection may be established between the access device 12 and the UE 11 through a wireless air interface. In different embodiments, the wireless air interface is a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, such as the new air interface; or, the wireless air interface may also be a wireless air interface based on the standard of the next-generation mobile communication network technology of 5G.

[0038] In some embodiments, an E2E (End to End) connection may also be established between UEs 11. For example, scenarios such as V2V (vehicle to vehicle), V2I (vehicle to Infrastructure), and V2P (vehicle to pedestrian) communications in vehicle-to-everything (V2X) communications.

[0039] In some embodiments, the above wireless communication system may further include a network management device 13.

[0040] A plurality of access devices 12 are respectively connected to a network management device 13. Among them, the network management device 13 may be a core network device in a wireless communication system. For example, the network management device 13 may be a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, the network management device may also be other core network devices, such as a Serving GateWay (SGW), a Public Data Network GateWay (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS), etc. The embodiments of the present disclosure do not limit the implementation form of the network management device 13.

[0041] As Figure 2 shown, the embodiments of the present disclosure provide a TA exception handling method, which is executed by a network device. The method includes:

[0042] S110: In response to determining that a TA exception occurs where the TA where the UE is currently located is outside the RA of the UE, record the TA exception;

[0043] S120: Based on the existence of the TA exception, trigger an RA update of the UE.

[0044] The network device here includes but is not limited to core network devices, and the core network device includes but is not limited to an Access Management Function (AMF).

[0045] When the UE registered last time, the RA was recorded on the network side, and the RA includes the TACs of one or more TAs. If the UE changes its location and enters a new TA, and the TA where the UE is currently located is outside the TA within the RA, but the UE does not initiate a registration update process to implement an RA update, it is determined that a TA exception has occurred. Exemplarily, the Unified Data Management (UDM) or AMF on the network side records the RA of the UE. Exemplarily, during the UE's last registration process, the UE and / or the UDM and AMF of the network device record the RA of the UE.

[0046] When the network side determines that such a TA exception occurs, it will record such a TA exception. Exemplarily, network devices such as AMF will record such a TA exception status and form status information of the TA exception status.

[0047] In some embodiments, the UE will send a Non-Access Stratum (NAS) request message. After the access network device (e.g., base station) receives the NAS request message, the base station and other access network devices include the UE's location information (including the TA where the UE is currently located) in the NAS request message and send it to the core network device (e.g., AMF). If the core network device finds that the TA where the UE is located is not within the TA included in the RA recorded on the network side, it determines that the TA is abnormal. When the UE makes a service request or requests to establish a Protocol Data Unit (PDU) session, the core network device receives the NAS request message. After receiving the NAS request message, the core network device enters the NAS processing flow to respond to the NAS request message.

[0048] The NAS request message includes but is not limited to at least one of the following:

[0049] Protocol Data Unit (PDU) session establishment request message;

[0050] Service request message.

[0051] There are many reasons for TA abnormality. The following is a possible reason:

[0052] The cell accessed by the UE (for example, a cell accessed by a satellite) moves to a new TA, and the new TA is not included in the TA included in the RA registered by the UE, resulting in a TA anomaly. If the UE finds that it has entered a new TA, it will actively trigger the registration update process. If the UE does not perceive that it has entered a new TA, it may not actively initiate the registration update process, and directly reach the network side, and the network side equipment discovers this TA anomaly of the UE.

[0053] like Figure 4 As shown, at time T1, the UE is in TA1 and accesses the 5G core network via satellite. The satellite broadcasts multiple TAs (TA1 and TA2) to the UE. The UE completes access registration, and the network generates RA for the UE (including TA1 and other TAs, but excluding TA2). At time T2, the UE moves into TA2. Since the TA broadcast by the satellite to the UE is the same at T1 and T2, the UE does not perceive that its TA has been updated, so the UE will not actively initiate a registration update to update the RA. If the UE initiates a service request at time T2, the gNB will report the UE's current location TA2 to the network side. The network side finds that the UE's current location TA2 is not included in the UE's RA, resulting in an abnormal TA of the UE. Of course, the above is only a simple example of the cause of the UE's TA abnormality. There are many methods for specific implementation, not limited to the above examples.

[0054] Reference Figure 3 and Figure 4 As shown, the satellite can be connected to the core network (CN) of 5G. The radio cell may broadcast one or more TACs for a PLMN, and the UE will determine its TA based on this broadcast information.

[0055] In one case, if the radio cell broadcasts a TAC, the UE will use this TA as its current TA.

[0056] As Figure 3 shown, assume that at time T1, the satellite and the radio cell are at position 1 and mostly covered within TA1, then the possible TAC broadcast may be the TAC of TA1; if the satellite and the radio cell move, for example, as Figure 3 shown, moving from left to right, then the radio cell may cover two TAs (i.e., TA1 and TA2) at a certain moment, or gradually switch from covering TA1 to not covering TA1 and completely covering within TA2. At time T2, when the satellite and the radio cell move into TA2, it will be considered that the current TA of the radio cell is TA2, and the TAC of TA2 may be broadcast to the UE.

[0057] In another case, the radio cell broadcasts multiple TACs at one time. Reference Figure 4 shown, from time T1 to time TA2, since the radio cell covers both TA1 and TA2 at the same time, the satellite and the radio cell will broadcast the TACs of TA1 and TA2 to the UE at the same time. At time T3, when the satellite and the radio cell move to cover TA2 and other TAs on the right side of TA2, the satellite and the radio cell will broadcast the TACs of TA2 and other TAs to the UE.

[0058] Regardless of the above situation, the AMF paging the UE according to the TAC included in the UE's RA. If the AN or RAN may determine the current TA where the UE is located from the RA and page the UE within this TA.

[0059] The UE will initiate a registration update. When the TA where the UE is currently located is not included in its RA, in the registration update process, network devices such as the AMF in the core network will update the UE's RA. The updated TA includes the TA where the UE is currently located and the TAs that the UE may access, so as to facilitate successfully paging the UE subsequently.

[0060] Exemplarily, as Figure 4As shown in the figure, at time T1, if the UE is located in TA1, it accesses the 5G network through the satellite. The satellite and the radio cell broadcast TA1 and TA2 to the UE. The UE determines the TA it is located in according to the broadcast information and completes the registration. As part of the registration process, the AMF generates an RA for the UE (including TA1 and other TAs, but not including TA2). At time T2, the UE moves from TA1 to TA2. Since the satellite and the radio cell continuously broadcast TA1 and TA2 to the UE at times T1 and T2, the UE may not be able to perceive the change in the TA it is located in and will not trigger a registration update to update the RA. However, at time T2, if the UE initiates a service request process, the gNB will report the current TA2 of the UE (obtained by the gNB through measurement) to the AMF. The AMF determines that the current TA2 of the UE is not included in the RA of the UE. At this time, the AMF can determine that the UE has the aforementioned TA anomaly.

[0061] After the base station receives the NAS request message sent by the UE, the base station includes the location information of the UE (including the current TA where the UE is located) in the NAS request message. Exemplarily, the current TA where the UE is located included in the NAS request message can be part of the User Location Information (ULI) in NGAP. If the TA indicated by the ULI is not included in the RA of the UE, a TA anomaly unknown to the UE will occur.

[0062] When there is a TA anomaly, it will trigger the UE to perform an RA update. Exemplarily, a trigger indication is sent to the UE. The trigger indication can be used to instruct the UE to execute the registration update process. In this way, the UE will update the RA through the registration update process. By including the current TA where the UE is located in the RA update, this TA anomaly can be eliminated.

[0063] The network device issues a trigger indication for the registration update process based on the TA anomaly. The indication information is used to indicate the reason for the UE to initiate the registration update process.

[0064] Exemplarily, Figure 5 The following shows a registration process, which may include:

[0065] The access network (AN) or RAN receives the registration request of the UE; the registration request includes: AN parameters, registration type, user subscription permanent identification (SUPI) or fifth generation mobile communication (5G) globally unique temporary user identification (GUTI), user equipment identification (PEI), requesting NSSAI, last visited and available TAI, etc. The registration type indicates whether the UE needs to perform initial registration, mobile registration update, periodic registration update or permanent registration. The last visited TAI can be used to help network devices such as AMF determine the RA of the UE.

[0066] After receiving the registration request, AN or RAN selects AMF for the UE; exemplarily, AN or RAN selects AMF for the UE based on the RAT used to transmit the registration request and the requested NASSAI and other information. If RAN cannot select a suitable AMF for the UE, it sends the AMF configured by RAN or AN to RAN for registration message, that is, selects the AMF configured by RAN or AN as the AMF of the UE.

[0067] Send a registration request to the selected AMF; the registration request is carried by the RAN or AN in the N2 message and sent to the selected AMF. The N2 parameters of the N2 message may include but are not limited to: registration request, identity (ID) of the selected public land mobile network (Public Land Mobile Network, PLMN), location information, cell ID of the cell where the UE is located, and other information.

[0068] If the UE's serving AMF has changed relative to the AMF selected for the last registration, the new AMF shall obtain the UE's SUPI and UE context from the old AMF;

[0069] If the UE does not provide SUCI or the old AMF does not provide SUCI, the new AMF will initiate an ID request procedure to obtain SUCI.

[0070] The new AMF will determine to initiate UE authentication involving an Authentication Server Function (AUSF) for the UE. For example, the new AMF will select an AUSF based on the UE's SUPI or SUCI.

[0071] If the AMF of the UE has switched compared to the previous registration process, or the SUPI provided by the UE does not involve valid context in the AMF, the AMF will select and register with a Unified Data Management (UDM) based on the SUPI. If the AMF does not obtain the UE's subscription data, it will obtain the UE's subscription data from the UDM.

[0072] The new AMF and the PCF interact in the process of establishing or modifying the mobility management (AM) policy;

[0073] If the PDU session containing the registration request is activated, the AMF will send an Nssmf_PDU Session_Update SMContext request to the SMF associated with the PDU session to activate the user plane connection of the PDU session.

[0074] The new AMF sends a registration acceptance message to the UE to indicate that the registration request has been accepted. The registration acceptance message contains information such as RA, mobility restrictions, allowed NASSAI, periodic registration timer indication, etc. If the AMF allocates a new RA, it will send the information of the new RA to the UE. If no new RA is allocated for the UE, the information of the RA will not be carried in the registration acceptance message, and it means that the old RA is still valid.

[0075] The remaining steps of the registration process will not be described one by one here.

[0076] In some embodiments, the S120 may include:

[0077] Periodically determine whether the TA anomaly exists, and if so, trigger the UE to perform RA update based on the existing TA anomaly.

[0078] In other embodiments, the S120 may include:

[0079] Before executing the service process or control process associated with the UE's RA or the TA where it is located, determine whether the TA anomaly exists.

[0080] Exemplarily, the method may further include: when paging the UE, first determine whether the TA anomaly exists. Thus, S120 may include: when determining that the TA anomaly of the UE exists during paging of the UE, trigger the UE to perform RA update. After the UE completes the RA update, the TA anomaly of the UE is removed. Thus, the UE can be paged according to the TA where the UE is located, thereby suppressing the paging failure phenomenon caused by the TA anomaly of the UE.

[0081] As Figure 6 shown, an embodiment of the present disclosure provides a method for handling TA anomalies, which may include:

[0082] S210: In response to determining that there is a TA anomaly, record the TA anomaly of the UE.

[0083] S220: When determining that there is a TA anomaly during paging the corresponding UE, trigger RA update of the UE.

[0084] S230: After the RA update of the UE is completed, page the UE.

[0085] There is a TA anomaly for the UE, and this TA anomaly is recorded on the network side. For example, it is recorded in the AMF. Before determining to page this UE, the AMF first queries whether there is a TA anomaly for the UE to be paged. If there is a TA anomaly, this TA anomaly needs to be eliminated first. When eliminating the TA anomaly, it can be achieved by triggering RA update of the UE. For example, the network side triggering RA update of the UE may include: sending a trigger indication to the UE to indicate that the UE initiates a registration update process. After receiving the trigger indication, the UE will send a registration update request to the network side. By executing the registration update process, the RA of the UE includes the TA where the UE is located, thereby eliminating this TA anomaly.

[0086] As Figure 7 shown, a method for handling TA anomaly according to an embodiment of the present disclosure, which is executed by a network device, may include:

[0087] S310: Receive a NAS request message; wherein, the NAS request message includes location information such as the TA where the UE is currently located.

[0088] S320: According to the NAS request message, determine whether the TA where the UE is currently located is outside the RA of the UE.

[0089] S330: In response to the TA where the UE is currently located being outside the RA, determine that the TA anomaly has occurred.

[0090] The network device may be a network device of the core network such as the AMF.

[0091] After the base station receives the NAS request message sent by the UE, the base station includes the location information of the UE (including location information such as the TA where the UE is currently located) in the NAS request message and sends it to the core network device (for example, the AMF). If the core network device finds that the TA where the UE is located is not within the TA included in the RA recorded on the network side, it determines a TA anomaly. For example, the base station adds the TA where the UE is currently located to the User Location Imformation (ULI) of the UE included in the NAS request message of the UE.

[0092] The method provided by the embodiments of the present disclosure can be executed alone or can be a specific implementation of the foregoing step S110.

[0093] In summary, in the embodiments of the present disclosure, the network device can determine whether the UE has a TA anomaly according to the NAS request message.

[0094] In the embodiments of the present disclosure, the method further includes:

[0095] When a TA anomaly is determined, the NAS request message is still normally responded to. The normal response to the NAS request message here can be: treating the TA anomaly as non-existent and continuing to execute the subsequent steps of the NAS process triggered by the NAS request message.

[0096] In some embodiments, the method further includes:

[0097] Responding to receiving a registration update request initiated by the UE when the TA anomaly is recorded;

[0098] After completing the RA update corresponding to the registration update request, the record of the TA anomaly is removed.

[0099] In addition to the network side triggering the UE to initiate a registration update process (i.e., a type of registration process), the UE may also actively initiate a registration update process.

[0100] Exemplarily, if the UE enters a new TA due to movement and initiates a registration update process, thereby updating the RA of the UE recorded on the network side;

[0101] Exemplarily again, if the UE wants to change the network parameters negotiated with the network side in the previous registration process, it can also be achieved according to the registration update process;

[0102] Exemplarily once more, if the UE is configured with periodic registration updates and the current update time for periodic registration updates is reached, the UE also actively initiates a registration update process to achieve registration update.

[0103] In the embodiments of the present disclosure, when a TA anomaly of the UE is discovered, the TA anomaly is recorded. Before the recorded TA anomaly is eliminated, if a registration update request actively initiated by the UE or a registration update request triggered by the network side is received, the execution of the registration process will be monitored. After the RA update of the UE and / or the network side record is achieved during the execution of the registration process corresponding to the registration update request, the record of this TA anomaly will be removed. If the TA anomaly record of the UE is removed, then when querying the TA anomaly of the UE in S120, it will be found that the UE does not have a TA anomaly.

[0104] Exemplarily, the registration update request includes: the registration update request initiated by the UE upon receiving a TA anomaly trigger; or, the registration update request triggered by the UE's location movement; or, the periodic registration update request initiated by the UE.

[0105] In some embodiments, the network device includes: an AMF.

[0106] As Figure 8 shown, an embodiment of the present disclosure provides a TA anomaly handling method, which is executed by a UE. The method includes:

[0107] S410: Receive a trigger indication sent by the network side based on the TA anomaly of the UE; this trigger indication is used to trigger the UE to execute a registration update process; S420: Perform RA update according to the trigger indication.

[0108] In the embodiments of the present disclosure, the network side includes but is not limited to the core network side.

[0109] The TA anomaly here includes: the TA where the UE is currently located is outside the UE's RA. And this TA anomaly is determined by the network side.

[0110] If the network side discovers a TA anomaly of the UE, it will actively trigger the UE to perform an RA update. The network side will send a trigger indication, and this trigger indication can be: any indication sent by the network side to trigger the UE to initiate a registration update request. Exemplarily, the trigger indication includes but is not limited to a configuration update instruction.

[0111] In some embodiments, the method further includes:

[0112] Send a NAS request message, where after the UE's location information is added to the NAS request message when passing through the access network device, it is used for the core network to determine whether a TA anomaly of the UE has occurred.

[0113] For example, this NAS request message carries a ULI, and this ULI contains location information such as the TA where the UE is located. After the network side receives this NAS request message and finds that the TA included in the NAS request message is not included in the UE's RA, it is considered that a TA anomaly of the UE has occurred. If such a TA anomaly occurs, this TA anomaly will be recorded.

[0114] Before the network side executes a service process or a control process associated with the UE's RA or the TA where it is located, it queries whether there is a TA anomaly of the UE. If it exists, the UE will receive a trigger indication for registration update sent by the network side.

[0115] The UE can initiate a registration update request based on this trigger indication, and update the RA of the UE and / or the network side through the registration update process corresponding to the registration update request, so as to eliminate this TA anomaly.

[0116] In some embodiments, the trigger indication is received before paging the UE. Receiving the trigger indication before the UE is paged is equivalent to being able to eliminate the TA anomaly through RA update, thus ensuring the paging success rate of the UE.

[0117] To solve the TA anomaly of the UE, if the TA anomaly of the UE is detected, the AMF records this TA anomaly while ignoring the detected TA anomaly. After that, if a process of paging the UE occurs, the AMF will trigger the UE to initiate a registration update to solve the TA anomaly. After the TA anomaly is removed, the UE is paged again.

[0118] In this way, this method can not only solve the TA anomaly of the UE, but also has no negative impact on the paging of the UE.

[0119] Exemplarily, when the AMF receives a NAS request message (exemplarily, the NAS request message includes but is not limited to: a PDU establishment request message or a service request message), it can determine whether a TA anomaly has occurred according to the NAS request message. If the AMF detects such a TA anomaly, it will ignore this TA anomaly, record this TA anomaly in the AMF, and continue to respond to this NAS request message, that is, normally execute the NAS process corresponding to the NAS request message.

[0120] The AMF records the TA anomaly. After that, if a registration update initiated by the UE itself, such as the movement of the UE or periodic registration update, occurs and eliminates the TA anomaly, the recorded TA anomaly will be removed from the AMF, otherwise the record of this TA anomaly will continue to be saved in the AMF.

[0121] If it is necessary to page the UE, after the AMF receives the paging message, it determines whether there is a TA anomaly for the UE. If the TA anomaly of the UE is recorded in the AMF, the AMF will trigger the UE to initiate a registration update process. After the registration update process is completed, the AMF will send a paging message based on the updated RA. If the TA anomaly of the UE is not recorded in the AMF, the AMF will page the UE according to the normal process.

[0122] As Figure 9 shown, when the UE accesses the network, a registration process will be initiated, and this registration process will be completed between the UE and the Core Network (CN); the registration process initiated when the UE accesses the network is the initial registration process between the UE and the CN (such as 5G CN).

[0123] If the initial registration is successful, the RA of the UE will be stored in the AMF, and the RA may include one or more TAs.

[0124] Receive a NAS request message (PDU session establishment request message), which carries information indicating the TA where the UE is located by the base station;

[0125] After the AMF receives the NAS request message, it will detect whether there is a TA anomaly. If a TA anomaly occurs, the AMF will ignore this TA anomaly and store the TA anomaly of the UE.

[0126] The AMF and other entities will continue the PDU session establishment process;

[0127] After the PDU session is established, if an emergency service needs to start, the AMF will send a paging message to the UE. Before sending the paging message, the AMF determines whether there is a TA anomaly of the UE;

[0128] If there is such a TA anomaly, the AMF sends a message triggering the registration update process to the UE;

[0129] Upon receiving the message triggering the registration update process, the UE initiates a registration update process to the 5G CN. After the registration update process is completed, the RA of the UE contains the TA where the UE is located;

[0130] The AMF uses the updated RA to page the UE and starts the emergency service.

[0131] As Figure 10 shown, when the UE accesses the network, a registration process will be initiated, and this registration process will be completed between the UE and the 5G core network (CN); the registration initiated when the UE accesses the network can be regarded as an initial registration.

[0132] If the initial registration is successful, the RA of the UE will be stored in the AMF, and the RA may include one or more TAs.

[0133] Receive a NAS request message (PDU session establishment request message), which carries information indicating the TA where the UE is located by the base station;

[0134] After the AMF receives the NAS request message, it will detect whether there is a TA anomaly. If a TA anomaly occurs, the AMF will ignore this TA anomaly and store the TA anomaly of the UE.

[0135] The AMF and other entities will continue the PDU session establishment process;

[0136] After that, a periodic registration update process occurs, and the AMF updates the UE's RA. The updated RA contains the TA where the UE is currently located. After the update is successful, the AMF removes the TA anomaly of the UE.

[0137] After the PDU session is established, if an emergency service needs to start, the AMF determines that there is no TA anomaly for the UE, and then initiates paging for the UE based on the recorded RA to start the emergency service.

[0138] In the embodiments of the present disclosure, when receiving a NAS request message containing the TA indicating the current location of the UE, the TA anomaly of the UE is detected. If a TA anomaly occurs, the AMF will ignore this TA anomaly, record the TA anomaly, and continue to execute the NAS process of the NAS request message.

[0139] After that, due to the movement of the UE or the registration update initiated by the periodic registration update, the TA anomaly of the UE in the AMF will be removed, otherwise it will continue to be stored in the AMF.

[0140] If paging for the UE occurs and the AMF receives a paging message, it is necessary to determine whether there is a TA anomaly for the UE. If the TA anomaly of the UE exists, the AMF will trigger the UE to initiate a registration update process based on the TA anomaly. After the registration update process is completed, the AMF sends a paging message based on the UE's RA. If there is no TA anomaly for the UE in the AMF, the AMF directly pages the UE without triggering the UE to initiate a registration update.

[0141] As Figure 11 shown, the embodiments of the present disclosure provide a TA anomaly handling device, and the device includes:

[0142] A recording module 110, configured to record the TA anomaly in response to determining that a TA anomaly occurs where the TA where the UE is currently located is outside the UE's RA;

[0143] A triggering module 120, configured to trigger an update of the UE's RA based on the existence of the TA anomaly.

[0144] This TA anomaly handling device can be included in a network device, and the network device includes but is not limited to the AMF.

[0145] In some embodiments, the recording module 110 and the triggering module 120 may include program modules; after the program modules are executed by a processor, when it is determined that a TA anomaly occurs where the UE is outside the UE's RA, this TA anomaly can be recorded.

[0146] In some embodiments, the recording module 110 and the triggering module 120 may be software-hardware combined modules; the software-hardware combined modules include, but are not limited to: various programmable arrays; the programmable arrays include, but are not limited to: field programmable arrays and complex programmable arrays.

[0147] In still other embodiments, the recording module 110 and the triggering module 120 may be pure hardware modules; the pure hardware modules include, but are not limited to: application specific integrated circuits.

[0148] In some embodiments, the apparatus further comprises:

[0149] A first determination module, configured to determine whether there is an abnormal TA when paging the UE.

[0150] In some embodiments, the apparatus further comprises:

[0151] A paging module, configured to page the UE after the RA update of the UE is completed.

[0152] In some embodiments, the apparatus further comprises:

[0153] A receiving module, configured to receive a non-access stratum NAS request message; wherein, the NAS request message has information indicating the TA where the UE is currently located;

[0154] A second determination module, configured to determine, according to the NAS request message, whether the TA where the UE is currently located is outside the RA of the UE;

[0155] A third determination module, configured to determine that the TA exception occurs in response to the TA where the UE is currently located being outside the RA.

[0156] In some embodiments, the apparatus further comprises:

[0157] A removing module, configured to, in response to receiving a registration update request initiated by the UE when the TA exception is recorded, remove the record of the TA exception after the RA update corresponding to the registration update request is completed.

[0158] In some embodiments, the registration update request includes:

[0159] The registration update request initiated by the UE upon receiving a TA exception trigger;

[0160] Or,

[0161] The registration update request triggered by the position movement of the UE;

[0162] Or,

[0163] The periodic registration update request initiated by the UE.

[0164] In some embodiments, the network device includes: an Access and Mobility Management Function (AMF).

[0165] As Figure 12 shown, an embodiment of the present disclosure provides a TA exception handling device, which is executed by a UE. The device includes:

[0166] A receiving module 210, configured to receive a trigger indication sent by the network side based on a TA exception of the UE;

[0167] An updating module 220, configured to perform RA update according to the trigger indication.

[0168] In some embodiments, the TA exception here includes: the TA where the UE is currently located is outside the RA of the UE. And this TA exception is determined by the network side.

[0169] The UE can be various types of UEs. For example, it includes but is not limited to: mobile phones, tablet computers, wearable devices, in-vehicle devices, or ground-walking robots or low-altitude flying aircraft, etc.

[0170] In some embodiments, the receiving module 210 and the updating module 220 can be program modules; after being executed by a processor, the program modules can receive the trigger indication sent by the network side and perform RA update based on the trigger indication.

[0171] In still some other embodiments, the receiving module 210 and the updating module 220 can be a software-hardware combined module; the software-hardware combined module includes but is not limited to various programmable arrays; the programmable array can include a Field Programmable Gate Array (FPGA) and / or a Complex Programmable Logic Device (CPLD).

[0172] In some embodiments, the receiving module 210 and the updating module 220 can be pure hardware modules; the pure hardware modules include but are not limited to Application Specific Integrated Circuits (ASICs).

[0173] In some embodiments, the device further includes:

[0174] A message module, configured to send a NAS request message, where after the UE's location information is added to the NAS request message when passing through an access network device, it is used for the core network to determine whether a TA exception of the UE occurs.

[0175] In some embodiments, the trigger indication is received before the UE is paged.

[0176] In one embodiment, the triggering indication may include indication information of TA anomaly. This indication information is used to indicate the reason for triggering the UE to initiate a registration update process.

[0177] Embodiments of the present disclosure provide a communication device, including:

[0178] a memory for storing processor-executable instructions;

[0179] a processor, respectively connected to the memory;

[0180] wherein the processor is configured to execute the TA anomaly handling method provided by any of the foregoing technical solutions.

[0181] The processor may include various types of storage media, which are non-temporary computer storage media and can continue to memorize and store the information thereon after the communication device loses power.

[0182] Here, the communication device includes: a UE and / or a core network device.

[0183] The processor may be connected to the memory through a bus or the like, and is used to read the executable program stored on the memory. For example, at least one of the methods shown as Figure 2 , Figures 5 to 10 shown.

[0184] Figure 13 is a block diagram of a UE 800 shown according to an exemplary embodiment. For example, the UE 800 may be a mobile phone, a computer, a digital broadcast user device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0185] Referring to Figure 13 , the UE 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0186] The processing component 802 generally controls the overall operation of the UE 800, such as operations associated with display, telephone call, data communication, camera operation, and recording operation. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0187] The memory 804 is configured to store various types of data to support the operation of the UE 800. Examples of such data include instructions for any application or method operating on the UE 800, contact data, phone book data, messages, pictures, videos, and the like. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disk.

[0188] The power supply component 806 provides power to various components of the UE 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the UE 800.

[0189] The multimedia component 808 includes a screen that provides an output interface between the UE 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can not only sense the boundaries of the touch or swipe actions but also detect the duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the UE 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

[0190] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC) that is configured to receive external audio signals when the UE 800 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals can be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 further includes a speaker for outputting audio signals.

[0191] The I / O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which can be a keyboard, a click wheel, buttons, etc. These buttons can include, but are not limited to: a home button, a volume button, a power-on button, and a lock button.

[0192] The sensor assembly 814 includes one or more sensors for providing a status assessment of various aspects for the UE 800. For example, the sensor assembly 814 can detect the on / off state of the UE 800, the relative positioning of components, such as the display and keypad of the UE 800. The sensor assembly 814 can also detect a change in the position of the UE 800 or a component of the UE 800, the presence or absence of user contact with the UE 800, the orientation or acceleration / deceleration of the UE 800, and the temperature change of the UE 800. The sensor assembly 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 can further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0193] The communication component 816 is configured to facilitate communication between the UE 800 and other devices in a wired or wireless manner. The UE 800 can access a wireless network based on communication standards, such as WiFi, 2G, or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0194] In an exemplary embodiment, the UE 800 can be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the above method.

[0195] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the above instructions can be executed by the processor 820 of the UE 800 to complete the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0196] As Figure 14 shown, an embodiment of the present disclosure shows a structure of an access device. For example, the network device 900 can be provided as a network-side device. The network device includes, but is not limited to, core network devices.

[0197] Referring to Figure 14 , the network device 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by a memory 932 for storing instructions executable by the processing component 922, such as application programs. The application programs stored in the memory 932 may include one or more modules each corresponding to a set of instructions. In addition, the processing component 922 is configured to execute instructions to perform any of the methods described above for the foregoing application in the network device, for example, as Figure 2 , Figures 5 to 10 the method shown.

[0198] The network device 900 may also include a power component 1926 configured to perform power management of the network device 900, a wired or wireless network interface 950 configured to connect the network device 900 to a network, and an input / output (I / O) interface 958. The network device 900 may operate based on an operating system stored in the memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

[0199] Those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of the present invention and include known common knowledge or conventional technical means in the technical field not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the present invention are pointed out by the following claims.

[0200] It should be understood that the present invention is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present invention is limited only by the appended claims.

Claims

1. A method for handling abnormal tracking area (TA), wherein, Executed by a network device, the method includes: Receiving a non-access stratum (NAS) request message; wherein, the NAS request message includes information of the tracking area (TA) where the user equipment (UE) is currently located; Determining, according to the NAS request message, whether the TA where the UE is currently located is outside the registration area (RA) of the UE; In response to the TA where the UE is currently located being outside the RA, determining that a TA exception has occurred; In response to determining that a TA exception has occurred where the TA where the UE is currently located is outside the RA of the UE, ignoring the TA exception, continuing to execute the NAS procedure triggered by the NAS request message, and recording the TA exception to form exception record information; When paging the UE, determining whether the TA exception exists based on the pre-recorded exception record information; Based on the existence of the TA exception, triggering an RA update of the UE; after the RA update of the UE is completed, paging the UE; The method further includes: In response to receiving a registration update request initiated by the UE when the TA exception is recorded; Monitoring the execution of the registration procedure corresponding to the registration update request; After the RA update corresponding to the registration update request is completed, removing the record of the TA exception; Wherein, the registration update request includes: the registration update request initiated by the UE triggered by the TA exception; or, the registration update request triggered by the location movement of the UE; or, the periodic registration update request initiated by the UE.

2. The method according to claim 1, wherein, The network device includes: an access and mobility management function (AMF).

3. A TA exception handling method, wherein, Executed by a user equipment (UE), the method includes: Sending a NAS request message, wherein, after the location information of the UE is added when the NAS request message passes through an access network device, it is used for the core network to determine whether a TA exception of the UE has occurred; Receiving a trigger indication sent by the network side based on the TA exception of the UE; wherein, the TA exception includes: the TA where the UE is currently located is outside the RA of the UE; the trigger indication is sent by the network side when determining to page the UE and determining that there is a TA exception for the UE to be paged based on the pre-recorded exception record information; according to the trigger indication, performing an RA update; wherein, after the RA update is completed, the network side pages the UE; the exception record information is recorded by the network side when determining that a TA exception has occurred where the TA where the UE is currently located is outside the RA of the UE, and the core network ignores the TA exception when determining that the TA exception has occurred and continues to execute the NAS procedure triggered by the NAS request message; the record of the TA exception is removed after the core network receives the registration update request initiated by the UE and after the RA update corresponding to the registration update request is completed; Wherein, the registration update request includes: the registration update request initiated by the UE triggered by the TA exception; or, the registration update request triggered by the location movement of the UE; or, the periodic registration update request initiated by the UE.

4. A TA exception handling device, wherein, The apparatus is applied to a network device, and the apparatus includes A receiving module, configured to receive a non-access stratum (NAS) request message; wherein, the NAS request message includes information about the tracking area (TA) where the user equipment (UE) is currently located; A second determination module, configured to determine, according to the NAS request message, whether the TA where the UE is currently located is outside the registration area (RA) of the UE; A third determination module, configured to determine that a TA anomaly has occurred in response to the TA where the UE is currently located being outside the RA; A recording module, configured to, in response to determining that a TA anomaly has occurred where the TA where the UE is currently located is outside the RA of the UE, ignore the TA anomaly, continue to execute the NAS procedure triggered by the NAS request message, and record the TA anomaly to form anomaly record information; A first determination module, configured to determine whether the TA anomaly exists when paging the UE; A triggering module, configured to trigger an RA update of the UE based on the existence of the TA anomaly; A paging module, configured to page the UE after the RA update of the UE is completed; A removing module, configured to, in response to receiving a registration update request initiated by the UE when the TA anomaly is recorded, remove the record of the TA anomaly after completing the RA update corresponding to the registration update request; Wherein, the registration update request includes: the registration update request initiated by the UE triggered by the TA anomaly; or, the registration update request triggered by the location movement of the UE; or, the periodic registration update request initiated by the UE.

5. The apparatus according to claim 4, wherein, The network device includes: an access and mobility management function (AMF).

6. A TA exception handling device, wherein, The apparatus is applied to a user equipment (UE), and the apparatus includes: A message module, configured to send a NAS request message, wherein, after the location information of the UE is added to the NAS request message when passing through an access network device, it is used for the core network to determine whether a TA anomaly of the UE has occurred; A receiving module, configured to receive a triggering indication sent by the network side based on the TA anomaly of the UE; wherein, the TA anomaly includes: the TA where the UE is currently located is outside the RA of the UE; the triggering indication is sent by the network side when determining to page the UE and determining that there is a TA anomaly for the UE to be paged based on pre-recorded anomaly record information; an updating module, configured to perform an RA update according to the triggering indication; wherein, the network side pages the UE after the RA update is completed; the anomaly record information is recorded by the network side when determining that a TA anomaly has occurred where the TA where the UE is currently located is outside the registration area (RA) of the UE, and the core network ignores the TA anomaly when determining that the TA anomaly has occurred and continues to execute the NAS procedure triggered by the NAS request message; the record of the TA anomaly is removed after the core network receives the registration update request initiated by the UE and completes the RA update corresponding to the registration update request; Wherein, the registration update request includes: the registration update request initiated by the UE upon receiving an abnormal TA trigger; or, the registration update request triggered by the location movement of the UE; or, the periodic registration update request initiated by the UE.

7. A communication device, comprising a processor, a transceiver, a memory, and an executable program stored on the memory and capable of being run by the processor, wherein, When running the executable program, the processor executes the method provided in any one of claims 1 to 2 or 3.

8. A computer storage medium storing an executable program; after being executed by a processor, the executable program can implement the method provided in any one of claims 1 to 2 or 3.

Images