Tracking area exception handling method and apparatus, communication device, and storage medium

Abstract

Embodiments of the present disclosure provide a TA exception handling method and device, a communication device and a storage medium. The TA exception handling method performed by a network device can include: receiving a non-access stratum (NAS) request message; in response to determining, according to the NAS request message, that a TA exception occurs in which a TA where a UE currently locates is outside a registration area (RA) of the UE, determining subsequent processing according to TA exception handling decision information.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of wireless communication, and more particularly, to a tracking area (TA) exception handling method and apparatus, a communication device, and a storage medium. BACKGROUND

[0002] When a user equipment (UE) initially connects to a network, the UE sends a registration request to the network, and the network side responds to the registration request. During the registration process, the network side generates and records the registration area (RA) of the UE, which usually 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 and the UE move, the UE can enter a new TA that is not included in the TAL 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, resulting in a TA exception. SUMMARY

[0004] Embodiments of the present disclosure provide a TA exception handling method and apparatus, an information processing method and apparatus, a communication device, and a storage medium.

[0005] A first aspect of embodiments of the present disclosure provides a TA exception handling method, performed by a network device, and the method comprises:

[0006] receiving a non-access stratum (NAS) request message;

[0007] In response to determining, according to the NAS request message, that a TA exception occurs in which the UE currently located TA is located outside the RA of the UE, determining subsequent processing according to TA exception handling decision information.

[0008] A second aspect of embodiments of the present disclosure provides a TA exception handling method, performed by a UE, and the method comprises:

[0009] sending a registration update request based on a network side triggering of a TA exception of the UE, wherein the registration update request is used at least to update the RA of the UE.

[0010] A third aspect of embodiments of the present disclosure provides a TA exception handling apparatus, and the apparatus comprises:

[0011] a first receiving module configured to receive a NAS request message;

[0012] The determining module is configured to determine, in response to the NAS request message, that a TA abnormality occurs in which a TA in which the UE currently locates is outside a registration area (RA) of the UE, and determine subsequent processing according to TA abnormality processing decision information.

[0013] The fourth aspect of the embodiments of the present disclosure provides a TA abnormality processing apparatus, and the apparatus comprises:

[0014] The first sending module is configured to send a registration update request based on triggering of the TA abnormality of the UE by the network side, and the registration update request is used at least for updating the RA of the UE.

[0015] The fifth aspect of the embodiments of the present disclosure provides a communication device, comprising a processor, a transceiver, a memory, and an executable program stored on the memory and capable of being executed by the processor, wherein the processor executes the executable program to perform the TA abnormality processing method provided in the first aspect or the second aspect.

[0016] The sixth aspect of the embodiments of the present disclosure provides a computer storage medium, which stores an executable program; the executable program is executed by a processor to implement the TA abnormality processing method provided in the first aspect or the second aspect.

[0017] The technical solution provided by the embodiments of the present disclosure can determine a subsequent processing step suitable for the current situation according to TA abnormality decision information after discovering the TA abnormality based on the NAS request message sent by the UE, thereby ensuring timely response to the NAS request message in the case of needing to respond to the NAS request message in a timely manner, and eliminating the TA abnormality in a timely manner in the case of needing to remove the TA abnormality in a timely manner.

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

[0019] The accompanying drawings, which are incorporated into and form part of the specification, illustrate the embodiments consistent with the present disclosure and, together with the specification, serve to explain the principles of the embodiments of the present disclosure.

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

[0021] Figure 2 is a flowchart of a TA abnormality processing method according to an exemplary embodiment;

[0022] Figure 3 is a schematic diagram of TA switching of a wireless cell according to an exemplary embodiment.

[0023] Figure 4 is a schematic diagram showing another TA switching of a wireless cell according to an exemplary embodiment;

[0024] Figure 5 is a flowchart illustrating a method for handling TA exceptions according to an exemplary embodiment;

[0025] Figure 6 is a flowchart illustrating a method for handling TA exceptions according to an exemplary embodiment;

[0026] Figure 7 is a flowchart illustrating a method for handling TA exceptions according to an exemplary embodiment;

[0027] Figure 8 is a flowchart illustrating a method for handling TA exceptions according to an exemplary embodiment;

[0028] Figure 9 is a flowchart illustrating a method for handling TA exceptions according to an exemplary embodiment;

[0029] Figure 10 is a flowchart illustrating a method for handling TA exceptions according to an exemplary embodiment;

[0030] Figure 11 is a structural diagram of a TA exception handling device according to an exemplary embodiment;

[0031] Figure 12 is a structural diagram of a TA exception handling device according to an exemplary embodiment;

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

[0033] Figure 14 The figure is a schematic diagram showing the structure of a network device according to an exemplary embodiment. DETAILED DESCRIPTION

[0034] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible implementations consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with certain aspects of the present invention, as detailed in the appended claims.

[0035] The terminology used in the disclosure of the embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting thereof. The use of the terms "a" and "an" and "the" and "said" herein is intended to include the plural, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0036] It is to be understood that, although the terms first, second, third, etc. can be used herein to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one piece of information from another. For example, a first information can also be termed a second information, and similarly, a second information can also be termed a first information without departing from the scope of the disclosure. The word "if' as used herein can be interpreted to mean "when" or "upon" or "in response to determining" depending on the context.

[0037] Reference is made to Figure 1 which shows a structure diagram of a wireless communication system provided by the embodiments of the disclosure. As shown in Figure 1 , the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system can include a plurality of UEs 11 and a plurality of access devices 12.

[0038] The UE 11 can be a device that provides voice and / or data connectivity to a user. The UE 11 can be a machine-to-machine UE, such as a sensor device, a mobile telephone (also known as a "cellular" telephone), and a computer with a machine-to-machine UE, e.g., a fixed, portable, pocket, handheld, computer-embedded, or car-mounted device. For example, the UE 11 can be a Station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote UE, an access UE, a user terminal, a user agent, a user device, or a user equipment (UE). Alternatively, the UE 11 can be a device of an unmanned aerial vehicle. Alternatively, the UE 11 can be a vehicle-mounted device, e.g., a car-mounted device with wireless communication function, or a wireless communication device externally connected to a car-mounted device. Alternatively, the UE 11 can be a roadside device, e.g., a street lamp, a signal lamp, or other roadside device with wireless communication function.

[0039] The access device 12 can be a network-side device in a wireless communication system. The wireless communication system can be a 4th generation mobile communication (4G) system, also known as a Long Term Evolution (LTE) system. Alternatively, the wireless communication system can be a 5G system, also known as a new radio (NR) system or a 5G NR system. Alternatively, the wireless communication system can be a further next generation system of the 5G system. In the 5G system, the access network can be referred to as a New Generation-Radio Access Network (NG-RAN). Alternatively, the wireless communication system can be an MTC system.

[0040] The access device 12 can be an evolved access device (eNB) used in a 4G system. Alternatively, the access device 12 can also be an access device (gNB) using a centralized and distributed architecture in a 5G system. When the access device 12 uses a centralized and distributed architecture, it usually includes a central unit (CU) and at least two distributed units (DUs). The central unit is provided with a protocol stack of a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer; the distributed unit is provided with a physical (PHY) layer protocol stack, and the specific implementation of the access device 12 is not limited in the embodiments of the present disclosure.

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

[0042] In some embodiments, the UEs 11 can also establish an E2E (End to End) connection. For example, V2V (vehicle to vehicle) communication, V2I (vehicle to infrastructure) communication, and V2P (vehicle to pedestrian) communication in vehicle to everything (V2X) communication and the like.

[0043] In some embodiments, the wireless communication system described above can also include a network management device 13.

[0044] A plurality of access devices 12 are connected to a network management device 13 respectively. The network management device 13 can be a core network device in a wireless communication system, for example, the network management device 13 can be a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, the network management device can 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 implementation form of the network management device 13 is not limited in the embodiments of the present disclosure.

[0045] As shown in Figure 2 The embodiments of the present disclosure provide a TA abnormality processing method, wherein the method is executed by a network device, and the method comprises the following steps:

[0046] S110: receiving a NAS request message;

[0047] S120: in response to determining that a TA abnormality occurs in which a TA where a UE currently locates is outside a RA of the UE according to the NAS request message, determining subsequent processing according to TA abnormality processing decision information.

[0048] The network device herein includes but is not limited to a core network device, and the core network device includes but is not limited to an Access Management Function (AMF).

[0049] When the UE performs a service request or a Protocol Data Unit (PDU) session request, the UE sends a NAS request message to the core network.

[0050] In some embodiments, the NAS request message contains a TA where the UE currently locates.

[0051] If the network device receives the NAS request message and finds that the TA contained in the NAS request message is not contained in the TA corresponding to the RA, it can be considered that the UE has a TA abnormality.

[0052] There are various reasons for the occurrence of TA abnormality, and one possible reason is provided as follows:

[0053] If a UE moves to a new TA in a cell it accesses (e.g., a cell accessed by satellite), and the new TA is not included in the TAs included in the RA in which the UE is registered, a TA anomaly occurs. If the UE discovers that it has entered a new TA, it will proactively trigger the registration update process. If the UE does not perceive that it has entered a new TA, it may not proactively initiate the registration update process, and the information will be directly transmitted to the network side, where the network side equipment will discover the UE's TA anomaly.

[0054] For example, 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 an RA for the UE (including TA1 and other TAs, but not TA2). At time T2, the UE moves into TA2. Because the satellite broadcasts the same TA to the UE at T1 and T2, the UE is unaware of the TA update and does not proactively initiate a registration update to update the RA. If the UE initiates a service request at time T2, the gNB reports the UE's current location, TA2, to the network. The network discovers that the UE's current location, TA2, is not included in the UE's RA, resulting in an abnormal TA for the UE. Of course, the above is just a simple example of the causes of UE TA abnormalities. There are many specific implementation methods, not limited to the above examples.

[0055] refer to Figure 3 and Figure 4 As shown, the satellite can be connected to the 5G core network (CN). The satellite and the wireless cell may broadcast one or more TAs for a PLMN, and the UE will determine its own TA based on the broadcast information.

[0056] In one case, the wireless cell broadcasts a TA, and the UE takes the TA as its current TA.

[0057] like Figure 3 As shown, assuming that at time T1, the satellite and the wireless cell are at position 1 and most of them are covered in TA1, the broadcast message contains TA1; if the satellite and the wireless cell move, for example, Figure 3 As shown, moving from left to right, the radio cell may simultaneously cover both TAs (TA1 and TA2) at a given moment, or gradually switch from covering TA1 to not covering TA1 and completely covering TA2. At time T2, the satellite and radio cell move into TA2, and the current TA of the radio cell is considered to be TA2, and TA2 is broadcast to the UE.

[0058] In another case, a wireless cell may broadcast multiple TAs at once. Figure 4As shown in the figure, from time T1 to time TA2, because the wireless cell covers both TA1 and TA2, the satellite and wireless cell broadcast TA1 and TA2 to the UE at the same time. At time T3, the satellite and wireless cell move to cover TA2 and other TAs to the right of TA2. The satellite and wireless cell then broadcast TA2 and other TAs to the UE.

[0059] Regardless of the above situation, the AMF will page the UE according to the TA included in the UE's RA. If possible, the AN or RAN will determine the TA where the UE is currently located from the RA and page the UE in that TA.

[0060] The UE will initiate a registration update. When the TA in which the UE is currently located is not included in its RA, during the registration update process, the network equipment of the core network such as the AMF will update the RA of the UE. The updated TA includes the TA in which the UE is currently located and the TA that the UE may access, so that the UE can be successfully paged in the future.

[0061] For example, Figure 4 As shown in the figure, at time T1, the UE is located in TA1 and accesses the 5G network via satellite. The satellite and radio cell broadcast TA1 and TA2 to the UE. The UE determines its TA based on the broadcast information and completes registration. As part of the registration process, the AMF generates an RA for the UE (including TA1 and other TAs, but not TA2). At time T2, the UE moves from TA1 to TA2. Because the satellite and radio cell continue to broadcast TA1 and TA2 to the UE at times T1 and T2, the UE may not be aware of the change in its TA 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 reports the UE's current TA2 (obtained by the gNB through measurement) to the AMF. The AMF determines that the UE's current TA2 is not included in the UE's RA. At this point, the AMF can determine that the UE has experienced the aforementioned TA anomaly.

[0062] After receiving the NAS request message from the UE, the base station includes the UE's location information (including the TA the UE is currently in) in the NAS request message. For example, the TA the UE is currently in included in the NAS request message can be used as part of the User Location Information (ULI) in NGAP. If the TA indicated by the ULI is not included in the UE's RA, a TA anomaly that the UE is unaware of occurs.

[0063] When the UE sends the NAS request message, the NAS request message contains the TA where the UE is currently located. Exemplarily, the TA where the UE is currently located is indicated in the NAS request message as part of the user location information (ULI) in the NGAP. If the TA indicated by the ULI is not included in the RA of the UE, a TA anomaly unknown to the UE occurs.

[0064] In the embodiments of the present disclosure, when the network device determines that the UE has a TA anomaly, the subsequent processing for the TA anomaly is determined according to the TA anomaly processing decision information. In this way, the subsequent processing of the TA anomaly suitable for the current scenario can be determined, so that the TA anomaly meets the current demand.

[0065] The TA anomaly decision information can be any information that can be used to determine how to perform the subsequent step or how to process the TA anomaly after the TA anomaly is found.

[0066] In one embodiment, the TA anomaly decision information includes but is not limited to information associated with the NAS request message, information related to the attributes of the UE, and / or registration update period information of the UE.

[0067] The information associated with the NAS request message can be used to determine the service latency requirement and / or the latency requirement for responding to the currently received NAS request message and / or the UE location accuracy requirement.

[0068] The information associated with the attributes of the UE can be used to determine the communication service latency requirement and / or the Quality of Service (QoS).

[0069] The registration update information configured for the UE can indicate whether the UE is configured with a periodic registration update. If the UE is configured with a periodic registration update, whether to wait for the periodic registration update to update the RA or to trigger the UE to perform a registration update on the network side to update the RA of the UE can be determined according to the time interval between the update time of the next periodic registration update and the time when the TA anomaly is determined.

[0070] In summary, the TA anomaly processing decision information can be any information that can be used to determine how to perform the subsequent processing step of the TA anomaly, and the specific information is not limited herein.

[0071] In some embodiments, the subsequent processing includes at least one of the following:

[0072] ignoring the TA anomaly and responding to the NAS request message;

[0073] rejecting the NAS request message and triggering the UE to initiate a registration update to update the RA;

[0074] responding to the NAS request message, and triggering the UE to initiate a registration update to update the RA after the responding to the NAS request message is completed.

[0075] In some embodiments, the network device such as the AMF determines that the TA is abnormal, but considers that the response to the current NAS request message is irrelevant to the TA where the UE is located, and that the UE is close to the update time of the registration period, and the registration period of the UE will also trigger the UE to update the stored TA, so that the current TA abnormality processing is not needed, and the TA abnormality processing can be ignored to continue the subsequent steps of responding to the NAS request message, and the TA abnormality is removed by means of the periodic registration update of the UE, thereby reducing the interaction introduced by the network side actively triggering the UE to perform the registration update.

[0076] In some embodiments, according to the TA abnormality processing decision information, it can be found that the response to the current NAS request message can have a great correlation with the TA where the UE is located, so the NAS request message can be rejected first, and the UE is triggered to actively initiate a registration update, and the RA is updated through the registration update. After the RA update is completed, the response to the NAS request message is performed.

[0077] In another embodiment, considering that the response to the NAS request message can be irrelevant to the TA where the UE is located, and that the update time of the registration period of the UE is far away, the UE is actively triggered to perform a registration update after the response to the NAS request message to update the RA of the UE, considering the problems caused by the TA abnormality.

[0078] In some embodiments, the method further comprises:

[0079] temporarily storing the NAS request message, triggering the UE to initiate a registration update to update the RA, and responding to the temporarily stored NAS request message after the RA is updated, so that the TA abnormality processing is completed before the response to the NAS request message, and the UE does not need to resend the NAS request message, and the delay caused by resending the NAS request message is reduced.

[0080] The specific processing method can be determined by the network device such as the AMF, and the specific decision method has many kinds, which will not be illustrated here.

[0081] In some embodiments, the rejecting the NAS request message comprises:

[0082] sending a rejection message of the NAS request message to the UE, wherein the rejection message contains a rejection reason; and the rejection reason indicates the TA abnormality.

[0083] If the UE's TA is abnormal, the network side sends a rejection message to the UE. In the embodiments of the present disclosure, in order to inform the UE of the rejection reason, the rejection message carries a cause indication indicating the TA abnormality and / or the registration update. For example, the rejection message includes a rejection code or a cause value indicating the rejection reason. When the rejection code or the cause value is a specific value, it indicates the TA abnormality and / or the registration update.

[0084] In some embodiments, when the rejection message carries the rejection reason indicating the TA abnormality, the UE reinitiates the registration update procedure, thereby realizing the RA update. Therefore, the rejection reason indicating the TA abnormality is used to trigger the UE to initiate the registration update to update the RA of the UE.

[0085] In some embodiments, after the network side sends the rejection message, a trigger indication triggering the UE to initiate the registration update procedure can also be sent. In the embodiments of the present disclosure, the rejection reason of the rejection message triggers the UE to initiate the registration update, which reduces the NAS signaling interaction between the network side and the UE, and has the characteristics of simple interaction procedure and small signaling overhead.

[0086] In some embodiments, the method further includes at least one of the following:

[0087] In response to determining that the registration update request of the UE is received when the RA update of the UE is triggered, the triggering of the registration update is stopped;

[0088] In response to determining that the update moment of the registration update period of the UE is the moment when the RA update of the UE is triggered, the triggering of the registration update is stopped.

[0089] If it is determined that the UE's TA is abnormal based on the NAS request message and the UE is triggered to perform the RA update, it is found that the registration update request of the UE is received, the triggering is not needed, and therefore the triggering of the registration update can be stopped, that is, the trigger indication sent to the UE is stopped.

[0090] If it is determined that the UE is abnormal based on the NAS request message and the update moment of the registration update period of the UE is reached, it is obvious that the UE does not need to be triggered, and the UE itself will initiate the registration update request because the registration update period is reached, and therefore the triggering of the UE to perform the registration update can be stopped, that is, at least the trigger instruction sent to the UE can be stopped.

[0091] In the embodiments of the present disclosure, the registration update procedure triggered by the registration update request of the UE. It is worth noting that the registration update procedure is the same as the registration procedure, but the parameters carried in the messages transmitted in the initial registration procedure and the registration update procedure can be different.

[0092] Figure 5 The figure shows a registration procedure, which can include:

[0093] The Access Network (AN) or RAN receives a registration request from the UE; the registration request includes: AN parameters, registration type, Subscription Permanent Identifier (SUPI) or 5th Generation (5G) Globally Unique Temporary UE Identity (GUTI), Permanent Equipment Identifier (PEI), requested NSSAI, last visited and available TA, etc. The registration type indicates whether the UE is required to perform initial registration, mobile registration update, periodic registration update, or permanent registration. The last visited TA can be used to help the network device such as the AMF determine the RA of the UE.

[0094] After the AN or RAN receives the registration request, the AN or RAN selects an AMF for the UE; for example, the AN or RAN selects an AMF for the UE according to information such as the RAT used to transmit the registration request and the requested NSSAI. If the RAN cannot select a suitable AMF for the UE, the RAN registers the message with the AMF configured by the RAN or the AN, i.e., selects the AMF configured by the RAN or the AN as the AMF of the UE.

[0095] The registration request is sent to the selected AMF; the registration request is sent to the selected AMF by the RAN or the AN in an N2 message. The N2 parameters of the N2 message can include, but are not limited to: the registration request, the identity (Identity, ID) of the selected Public Land Mobile Network (PLMN), location information, the cell ID of the cell where the UE is located, and other information.

[0096] If the serving AMF of the UE has changed with respect to the AMF selected in the last registration, the new AMF will obtain the SUPI of the UE and the context of the UE from the old AMF.

[0097] 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.

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

[0099] If the AMF of the UE has a handover relative to the last registration procedure, or the SUPI provided by the UE does not refer to a valid context in the AMF, the AMF will select and register to a Unified Data Management (UDM) based on the SUPI. If the AMF does not obtain the subscription data of the UE, the AMF will obtain the subscription data of the UE from the UDM.

[0100] A new procedure of interaction between a new AMF and a PCF for establishment or modification of an Access and Mobility (AM) policy;

[0101] 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.

[0102] The new AMF sends a registration accept message to the UE to indicate that the registration request is accepted. The registration accept message contains information such as RA, mobility restriction, allowed NSSAI, periodic registration timer indication, etc. If the AMF allocates a new RA, the information of the new RA is sent to the UE. If no new RA is allocated for the UE, no information of the RA will be carried in the registration accept message, and it indicates that the old RA is still valid.

[0103] The remaining steps of the registration procedure are not described here.

[0104] The triggering of the above registration procedure further includes at least one of the following:

[0105] Registration update triggered by UE moving into a TA outside the RA, regardless of whether the UE is in a connected state or a non-connected state, when the UE moves into a TA outside the RA, the above registration procedure is performed to realize RA update. The non-connected state can include at least an idle state and / or an inactive state.

[0106] Registration update triggered by parameter update, when the UE needs to update its own capability or update the protocol parameters negotiated in the registration procedure, regardless of whether the UE moves into a new TA, the UE can actively initiate a registration request to realize RA update through the above registration update.

[0107] Periodic registration update, based on a predefined inactivity time, after a predefined inactivity time, a registration update is initiated to realize registration update.

[0108] As shown in FIG. 8, the embodiment of the present disclosure provides a TA exception handling method, which can include: Figure 6

[0109] ​S210: determining the response tolerance delay and / or service delay requirement and / or UE location accuracy requirement of the NAS request message according to the TA abnormality handling decision information when determining the TA abnormality of the UE;

[0110] S220: determining the subsequent handling according to the response tolerance delay and / or service delay requirement and / or UE location accuracy requirement.

[0111] The subsequent handling herein includes at least one of the following:

[0112] ignoring the TA abnormality and responding to the NAS request message without TA abnormality;

[0113] responding to the NAS request message and triggering the UE to initiate registration update to eliminate the TA abnormality after responding to the NAS request message;

[0114] rejecting the NAS request message and carrying the TA abnormality or registration update rejection reason in the rejection message of the NAS request message;

[0115] suspending the NAS request message and triggering the UE to initiate registration update, and resuming the response of the suspended NAS request message after completing the registration update. Suspending the NAS request message includes temporarily storing the NAS request message.

[0116] For example, the response tolerance delay and / or service delay requirement and / or UE location accuracy requirement of the NAS request message are determined according to any one of the TA abnormality handling decision information. If the delay allowed for the current NAS request message response is relatively large or the service delay requirement is low, it is indicated that even if the response of the current NAS request message is delayed or even if the response of the NAS request message is rejected first, the RA update is completed, it is insensitive to the user or service. If the delay allowed for the current NAS request message response is small or the service delay requirement is high, i.e., the delay sensitivity of the NAS request message is strong, the NAS request message needs to be responded to preferentially, and the TA abnormality can be processed after the response of the NAS request message or not processed temporarily.

[0117] If it is determined according to the TA abnormality decision information that the response process of the NAS request message or the service requirement for the UE location accuracy is very high, for example, the UE location accuracy is higher than a preset threshold, or it is estimated that the current UE location accuracy cannot meet the requirement of the response process of the NAS request message or the requirement of the user location for the service, it is considered that the TA abnormality elimination process needs to be performed first, and the response of the suspended NAS request message can be performed after the TA abnormality elimination process.

[0118] In some embodiments, the S120 can include one of the following:

[0119] In response to the response tolerance delay satisfying the first condition, the NAS request message is ignored and the UE is triggered to perform a registration update.

[0120] In response to the response tolerance delay satisfying the first condition, the NAS request message is ignored and the UE is triggered to perform a registration update.

[0121] In response to the response tolerance delay not satisfying the first condition, the NAS request message is rejected and a rejection cause indicating a TA exception or a registration update is carried in the rejection message of the NAS request message to trigger the UE to initiate a registration update to update the RA, and after the RA is updated, the UE re-sends the NAS request message and the NAS request message is responded to.

[0122] In response to the response tolerance delay not satisfying the first condition, the UE is triggered to initiate a registration update to update the RA, and after the RA is updated, the stored NAS request message is responded to.

[0123] In response to the response to the NAS request message meeting a second condition on the location accuracy requirement of the UE, the NAS request message is ignored and the UE is triggered to perform a registration update.

[0124] In response to the response to the NAS request message meeting a second condition on the location accuracy requirement of the UE, the NAS request message is ignored and the UE is triggered to perform a registration update.

[0125] In response to the response to the NAS request message not meeting a second condition on the location accuracy requirement of the UE, the NAS request message is rejected and a rejection cause indicating a TA exception or a registration update is carried in the rejection message of the NAS request message to trigger the UE to initiate a registration update to update the RA, and after the RA is updated, the UE re-sends the NAS request message and the NAS request message is responded to.

[0126] In response to the response to the NAS request message not meeting a second condition on the location accuracy requirement of the UE, the UE is triggered to initiate a registration update to update the RA, and after the RA is updated, the stored NAS request message is responded to.

[0127] The registration update of the UE is triggered by sending a configuration update command to the UE. The configuration update command is a trigger indication.

[0128] In some embodiments, in response to the response tolerance delay satisfying the first condition, the NAS request message is ignored and the UE is triggered to perform a registration update.

[0129] In response to the response tolerance delay or the service delay meeting the first condition and the time interval between the moment of discovering the TA exception and the next update moment of the periodic update of the UE being less than a preset threshold, the TA exception is ignored to continue responding to the NAS request message.

[0130] The response to the NAS request message is continued in response to the response tolerance delay or the service delay meeting the first condition, and the UE is triggered to perform the registration update after responding to the NAS request message.

[0131] In response to the response tolerance delay or the service delay meeting the first condition and the time interval between the moment of discovering the TA exception and the next update moment of the periodic update of the UE being not less than a preset threshold, the NAS request message is continued to be responded to, and the UE is triggered to perform the registration update after responding to the NAS request message.

[0132] The response tolerance delay meeting the first condition includes but is not limited to at least one of the following:

[0133] The response tolerance delay is less than a preset time threshold.

[0134] The response tolerance delay is less than a time required for the UE registration update process.

[0135] The service delay is less than a preset time threshold.

[0136] The service delay is less than a time required for the UE registration update process.

[0137] The service delay meeting the first condition here is the delay defined by the service delay requirement in any of the foregoing examples.

[0138] The response tolerance delay not meeting the first condition includes but is not limited to at least one of the following:

[0139] The response tolerance delay is not less than a preset time threshold.

[0140] The response tolerance delay is not less than a time required for the UE registration update process.

[0141] The service delay is not less than a preset time threshold.

[0142] The service delay is not less than a time required for the UE registration update process.

[0143] The first condition here is that the response tolerance delay and / or the service delay requirement corresponding to the service delay is less than a preset time threshold, or the response tolerance delay and / or the service delay requirement corresponding to the service delay is less than a time required for the UE registration update process.

[0144] The response to the NAS request message meets a second condition in terms of the location accuracy requirement of the UE, including:

[0145] The response to the NAS request message requires the location accuracy of the UE to reach a preset accuracy.

[0146] The response to the NAS request message requires the location accuracy of the UE to meet a second condition, comprising:

[0147] The response to the NAS request message does not involve the location information of the UE.

[0148] And / or

[0149] The response to the NAS request message involves the location information of the UE, but requires the accuracy of the location information of the UE to be lower than a preset accuracy.

[0150] The second condition here is that the response to the NAS request message requires the location accuracy of the UE to reach a preset accuracy, or the response to the NAS request message does not involve the location information of the UE.

[0151] In some embodiments, whether the network device of the core network such as the AMF first buffers the NAS request message that needs to be responded to, continues to respond after completing the RA update, or waits for the UE to re-initiate the NAS request message for response after completing the RA update, can be determined according to whether the network device of the core network such as the AMF has the capability of buffering the NAS request message, or can be determined according to whether the UE has enabled the buffering service of the NAS request message.

[0152] In other embodiments, whether the network device of the core network such as the AMF first buffers the NAS request message that needs to be responded to, continues to respond after completing the RA update, or waits for the UE to re-initiate the NAS request message for response can be further subdivided into the response tolerance delay of the NAS request message. If the response tolerance delay does not meet the first condition and meets a third condition, the network device can first buffer the NAS request message that needs to be responded to, and only respond to the NAS request message after triggering the UE to complete the registration update. The tolerance delay corresponding to the third condition is greater than the tolerance delay corresponding to the first condition.

[0153] In some embodiments, the response tolerance delay of the NAS request message and the requirement for the location accuracy of the UE may need to be considered at the same time, and the way to process the TA anomaly of the UE is comprehensively determined.

[0154] In some embodiments, the TA anomaly processing decision information comprises at least one of the following:

[0155] The device type information of the UE;

[0156] The service type involved in the NAS request message;

[0157] A data network name (DNN) related to the NAS request message;

[0158] Network slice information related to the NAS request message;

[0159] Network slice information to which the UE is subscribed;

[0160] An operator operation policy associated with the UE.

[0161] For example, different types of UEs have different types of services or different QoSs for communication. Therefore, the device type information of the UE can be used as the TA abnormality processing information to determine the subsequent processing operation when the TA abnormality is found.

[0162] The service type related to the NAS request message can be determined by the service carried by the connection established by the NAS request message interaction.

[0163] Some service types allow a small response delay, and some service types allow a large response delay. For example, if the service type related to the NAS request message belongs to ultra reliable and low latency communication (URLLC), the allowed response delay of the NAS request message is very small. If the service type related to the NAS request belongs to enhanced mobile broadband (eMBB), the allowed response delay of the NAS request message is larger than the delay allowed by the URLLC service. Therefore, for the two types of services of URLLC and eMBB, different TA abnormality processing can be used when the TA abnormality is found.

[0164] Different DNNs involve different QoSs, and different QoSs correspond to different tolerable delays.

[0165] The network slice information includes but is not limited to:

[0166] Single network slice selection assistance information (S-NSSAI);

[0167] NSSAI;

[0168] Type information of the network slice.

[0169] Different network slices can provide different QoS services such as different delays, different bandwidths, etc.

[0170] In some embodiments, certain NAS request messages sent by the UE are related to network slices, and therefore network slice information associated with the NAS request message can be determined.

[0171] In some embodiments, an operator (e.g., a communication operator or an application operator) provides different communication services to different users. For example, some users are Very Important Person (VIP) services or non-VIP services, or VIP services can be divided into different levels, and different operator operation strategies can be used for different types of users (corresponding to different UEs). If the operator operation strategy indicates rate priority, the NAS request message needs to be responded to in priority.

[0172] Therefore, in the embodiments of the present disclosure, one or more of the TA exception handling decision information is selected to select a subsequent processing suitable for the current situation, so that appropriate subsequent processing is performed after the TA exception is found, which not only ensures that the NAS request message meets the expected QoS, but also timely eliminates the TA exception as necessary, thereby reducing various problems caused by the existence of the TA exception. For example, UE paging failure caused by the TA exception.

[0173] In some embodiments, the NAS request message includes at least one of the following:

[0174] A PDU session establishment request message;

[0175] A service request message.

[0176] Of course, the above is only an example, and in specific implementation, the NAS request message includes but is not limited to the PDU session establishment request and the service request, etc.

[0177] As shown in FIG. 10, the embodiments of the present disclosure provide a TA exception handling method, executed by a user equipment (UE), and the method includes: Figure 7 S310: Based on a trigger of a TA exception of the UE on a network side, a registration update request is sent, wherein the registration update request is at least used to update a RA of the UE.

[0178] In the embodiments of the present disclosure, the UE receives the trigger of the TA exception of the UE sent by the network side, initiates a registration update based on the trigger, and updates the RA of the UE through the registration update, thereby eliminating the RA exception.

[0179] The trigger can be a trigger of an access network device on the network side, or a trigger of a core network side.

[0180]

[0181] ​Exemplarily, the UE will receive a trigger indication sent by the network side based on the TA anomaly of the UE. After receiving the trigger indication, the UE sends a registration update request to update the registration.

[0182] It is worth noting that the registration update request here can include the aforementioned registration request. The initial registration procedure can be used for registration update.

[0183] The TA anomaly here includes that the TA where the UE currently locates is outside the RA of the UE. The TA anomaly is determined by the network side. The TA anomaly of the UE can be an anomaly detected by the network side in various cases. For example, according to the TA where the UE currently locates carried by the NAS request message, the network side finds that the TA where the UE currently locates is outside the RA of the UE, and considers that the TA anomaly occurs.

[0184] In some embodiments, the method comprises:

[0185] sending a NAS request message; wherein the NAS request message, after being added with the location information of the UE when passing through the access network device, is used for the core network to determine whether the UE has the TA anomaly.

[0186] The NAS request message here includes but is not limited to a PDU session establishment request message and / or a service request message.

[0187] The network device (for example, AMF) of the core network determines that the UE has the TA anomaly based on the TA where the UE currently locates carried by the NAS request message and the RA of the UE recorded by the network device.

[0188] In some embodiments, the method further comprises:

[0189] receiving a rejection message of the NAS request message;

[0190] The rejection message contains a rejection reason indicating the TA anomaly, and the UE sends the registration update request according to the rejection reason.

[0191] If the network side device determines to solve the TA anomaly after rejecting the NAS request message, the UE will receive a rejection message sent by the network side, and the rejection message generally carries a rejection reason. If the NAS request message is rejected due to the TA anomaly of the UE, the rejection reason of the rejection message will indicate the TA anomaly.

[0192] In some embodiments, when receiving the rejection message, the UE will also receive an additional trigger indication, and after receiving the trigger indication, initiates a registration procedure to update the RA.

[0193] In the embodiments of the present disclosure, the rejection reason indicates TA abnormality, and the rejection reason indicating TA abnormality triggers the UE to initiate a registration update request, thereby achieving RA update.

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

[0195] receiving a trigger indication.

[0196] In one embodiment, the trigger indication can be sent before the NAS request message is responded to, or sent at the same time or after the NAS request message is rejected.

[0197] In one embodiment, the trigger indication can include: indication information indicating TA abnormality, the indication information being used to inform the UE that the reason for initiating registration update is TA abnormality.

[0198] In another embodiment, the trigger indication is used to trigger the UE to send the registration update request, and is sent after the NAS request message is responded to.

[0199] If the trigger indication is updated after the NAS request message of the UE is responded to, the UE will first receive the NAS response before receiving the trigger indication, and first ensure that the service involved in the NAS request message is provided, thereby ensuring the latency of the service involved in the NAS request message.

[0200] In the embodiments of the present disclosure, the UE will also initiate a registration update process based on TA update caused by its own mobility to achieve RA update, and will also perform RA update at the update time according to the registration periodic update, or will initiate RA update when the UE needs to update the parameters negotiated in the registration process. In the registration process initiated for these reasons, RA update is also performed synchronously.

[0201] After the network device discovers TA abnormality, the network device can have the following processing methods for TA abnormality:

[0202] Method 1: The network device discovers TA abnormality of the UE, and operates as if the UE is still in its RA, for example, normally responds to the NAS request message of the UE. However, the UE can discover at some time that the TA of the cell it accesses is not in its own RA, and will initiate registration update to update the RA, or the UE can also perform periodic registration update. Therefore, the network side can ignore the RA abnormality after discovering the RA abnormality

[0203] Manner 2: After the network device such as AMF discovers the TA anomaly, if the TA where the UE currently locates is the TA that allows the UE to access, the AMF instructs the UE to perform the registration update. The 5GC instructs the UE to perform the registration update by means of rejection of the NAS request message, and the rejection cause is achieved by indicating the registration update or the TA anomaly. Once the registration update is completed, the UE re-sends the NAS request message, which is equivalent to restarting the NAS procedure.

[0204] Manner 3: After the network device such as AMF discovers the TA anomaly, if the TA where the UE currently locates is the TA that allows the UE to access, the AMF continues to perform the NAS procedure (i.e., continues to respond to the NAS request message). The AMF sends a configuration update command to the UE, which can instruct the UE to perform the registration update. The configuration update command can be sent after the AMF discovers the TA anomaly. The configuration update command is one of the aforementioned trigger indications.

[0205] The configuration update command can include the trigger indication provided in any of the foregoing embodiments.

[0206] To ensure that the operation of the network device such as AMF on the TA anomaly is appropriate, in the embodiments of the present disclosure, when selecting the subsequent operation, the AMF determines which manner to use for the TA processing according to the type of terminal, the type of service, S-NSSAI, NSSAI, DNN, or operator operation policy and the like.

[0207] In the above-mentioned scheme 2 and scheme 3, when the AMF instructs the UE to perform the registration update, the registration update request sent by the UE is received or the update time of the periodic registration update of the UE is reached, the instruction of the UE to perform the registration update is stopped, and it is determined that the TA anomaly is eliminated.

[0208] The following takes the NAS request message as the PDU session establishment request as an example. As shown in FIG. 8, the network device such as AMF can handle the TA anomaly as follows. Figure 8

[0209] The network device such as AMF receives the PDU session establishment request message from the UE;

[0210] The AMF and the UDM interact with the UE subscription information, for example, the AMF sends the UE subscription information request to the UDM, and receives the response from the UDM, wherein the response message includes the UE subscription information. The UE subscription information includes the subscription slice information NSSAI of the UE, the data network DNN of the subscription, the type of UE, and the like;

[0211] ​The AMF determines TA abnormality processing; for example, if the TA in which the UE is located included in the PDU session establishment request is not a TA in which the UE is prohibited from accessing, and the TA in which the UE is currently located is outside the RA of the UE, it is determined that TA abnormality occurs. Then, according to the type of the UE, the S-NSSAI, the DNN requested by the UE, and other information, the delay requirement of the service corresponding to the PDU session and whether the precise location information of the UE is required are determined. If the service is not sensitive to delay and the requirement for the location accuracy of the UE is low, the TA abnormality can be ignored first, and the PDU session establishment request process is continued.

[0212] The AMF interacts with other network functions (NFs) such as SMF to complete the remaining PDU session establishment process.

[0213] For example, a text message, voice message, or video message initiated by an instant communication application such as a satellite application can not require the precise location information of the UE, but the precise location of the UE can be required based on the service of the positioning application.

[0214] For another example, a text message sent by an instant communication application such as a satellite application or a short message sent by a short message application can be low in delay sensitivity, but a direct dialing telephone call can be high in delay sensitivity.

[0215] Hereinafter, taking a NAS request message as an example, it is shown in Figure 9 that the network device such as the AMF can process the TA abnormality as follows:

[0216] The AN or RAN (i.e., (R)AN as shown in Figure 9 receives the service request message from the UE; the UE initiates the service request process through a NAS message. The NAS message can include a service request message sent by the UE to the AMF, and the service request message is carried in an RRC message to the AN or RAN. After receiving the RRC message, the AN or RAN sends the NAS message to the AMF.

[0217] After receiving the service request message, the AN or RAN sends an N2 message to the AMF; the N2 message can carry the location information of the UE, i.e., the TA in which the UE is currently located.

[0218] After receiving the N2 message, the AMF finds that the TA is abnormal, and determines the TA abnormality processing.

[0219] If the TA where the UE is currently located is not the TA where the UE is forbidden to access, the AMF can further determine the latency requirement of the service and the location accuracy requirement of the UE according to the device type, S-NASSAI, DNN, service type, and operator operation policy of the UE, and determine how to perform the TA exception handling. For example, if the service is not sensitive to latency, but the location of the UE needs to be determined by the AMF, the AMF determines to first perform a response to the NAS request message, and after the response to the NAS request message, triggers the UE to perform a registration update to update the RA of the UE.

[0220] The AMF continues to respond to the service request message, for example, the AMF responds to the service request message by interacting with information of other NFs.

[0221] After the response to the service request message is completed, the AMF sends a configuration update command to the UE, which will trigger the UE to perform a registration update.

[0222] The UE initiates a registration update.

[0223] The following takes the NAS request message as the service request message, as shown in Figure 10 The network device such as the AMF can handle the TA exception as follows:

[0224] The AN or RAN (i.e., (R)AN as shown in Figure 10 receives the service request message from the UE; the UE initiates a service request procedure through a NAS message. The NAS message can include a service request message sent by the UE to the AMF, which is submitted to the AN or RAN in an RRC message. After receiving the RRC message, the AN or RAN sends the NAS message to the AMF.

[0225] The AN or RAN sends an N2 message containing the service request message and the location information of the UE to the AMF. The location information contains the TA where the UE is currently located. After receiving the N2 message from the AN or RAN, the AMF determines whether a TA exception occurs, for example, the TA where the UE is currently located is outside the TA contained in the RA, which indicates that a TA exception occurs. If a TA exception occurs, how to handle the TA exception is determined according to at least one of the UE type, S-NASSI, DNN, and operator policy information.

[0226] Exemplarily, the AMF can send a rejection message rejecting the service request message. The rejection message will trigger the UE to initiate a registration update.

[0227] After receiving the trigger indication of the registration update, the UE initiates a registration procedure so that the RA recorded by the AMF contains the TA where the UE is currently located.

[0228] If the registration update procedure is completed, the UE re-sends the service request message.

[0229] As shown in Figure 11 The TA abnormality processing apparatus provided by the embodiments of the present disclosure comprises:

[0230] The first receiving module 110 is configured to receive a NAS request message.

[0231] The determining module 120 is configured to determine, in response to the TA abnormality occurring that the TA where the UE currently locates is outside the registration area (RA) of the UE according to the NAS request message, subsequent processing according to TA abnormality processing decision information.

[0232] The TA abnormality processing apparatus provided by the embodiments of the present disclosure can be applied to or contained in a network device.

[0233] In some embodiments, the first receiving module 110 and the determining module 120 can be program modules; after the program modules are executed by a processor, the NAS request message receiving and the subsequent processing according to the TA abnormality decision information when the TA abnormality occurs can be realized.

[0234] In other embodiments, the first receiving module 110 and the determining module 120 can be soft and hard combined modules; the soft and hard combined modules include but are not limited to various programmable arrays; the programmable arrays include but are not limited to field programmable arrays and / or complex programmable arrays.

[0235] In still other embodiments, the first receiving module 110 and the determining module 120 can be pure hardware modules; the pure hardware modules include but are not limited to application specific integrated circuits.

[0236] In some embodiments, the subsequent processing comprises at least one of the following:

[0237] ignoring the TA abnormality and responding to the NAS request message;

[0238] rejecting the NAS request message and triggering the UE to initiate registration update to update the RA;

[0239] responding to the NAS request message and triggering the UE to initiate registration update to update the RA after the NAS request message response is completed.

[0240] In some embodiments, the rejecting the NAS request message comprises:

[0241] sending a rejection message of the NAS request message to the UE, wherein the rejection message contains a rejection reason; the rejection reason indicates the TA abnormality.

[0242] In some embodiments, the rejection cause indicating TA exception is used to trigger the UE to initiate a registration update to update the RA of the UE.

[0243] In some embodiments, the apparatus further comprises a stopping module configured to perform at least one of:

[0244] stopping the triggering of the registration update in response to determining that the registration update request of the UE is received when the RA update of the UE is triggered;

[0245] stopping the triggering of the registration update in response to determining that the time of triggering the RA update of the UE is the update time of the registration update period of the UE.

[0246] In some embodiments, the determining module 120 is configured to perform at least one of:

[0247] determining the response tolerance delay and / or UE location accuracy requirement of the NAS request message according to the TA exception handling decision information;

[0248] determining the subsequent processing according to the response tolerance delay and / or UE location accuracy requirement.

[0249] In some embodiments, the TA exception handling decision information comprises at least one of:

[0250] device type information of the UE;

[0251] service type related to the NAS request message;

[0252] DNN related to the NAS request message;

[0253] network slice information related to the NAS request message;

[0254] network slice information to which the UE is subscribed;

[0255] operator operation policy associated with the UE.

[0256] In some embodiments, the NAS request message comprises at least one of:

[0257] a protocol data unit (PDU) session establishment request;

[0258] a service request.

[0259] As shown in Figure 12 Embodiments of the present disclosure provide a TA exception handling apparatus, which comprises:

[0260] The first sending module 210 is configured to send a registration update request based on a network-side trigger of TA abnormality of the UE, wherein the registration update request is used at least for updating the RA of the UE.

[0261] In some embodiments, the first sending module 210 can be a program module; after the program module is executed by the processor, the program module can send the registration update request based on the network-side trigger of the TA abnormality of the UE.

[0262] In some other embodiments, the first sending module 210 can be a soft and hard combined module; the soft and hard combined module includes but is not limited to various programmable arrays; the programmable array includes but is not limited to a field programmable array and / or a complex programmable array.

[0263] In some other embodiments, the first sending module 210 can be a pure hardware module; the pure hardware module includes but is not limited to an application specific integrated circuit.

[0264] Here, the TA abnormality includes that the UE currently located TA is located outside the RA of the UE, and the TA abnormality is determined by the network side.

[0265] In some embodiments, the apparatus further includes:

[0266] The second sending module is configured to send a NAS request message; wherein the NAS request message can be used to determine whether the UE has the TA abnormality.

[0267] In some embodiments, the apparatus further includes:

[0268] The second receiving module is configured to receive a rejection message of the NAS request message;

[0269] The rejection message contains a rejection reason indicating the TA abnormality, and the UE sends the registration update request.

[0270] In some embodiments, the apparatus further includes:

[0271] The third receiving module is configured to receive a trigger indication, wherein the trigger indication is used to trigger the UE to send the registration update request, and is sent after the NAS request message is responded.

[0272] The present disclosure provides a communication device, including:

[0273] A memory for storing processor-executable instructions;

[0274] A processor connected to the memory respectively;

[0275] The processor is configured to perform the TA exception handling method provided in any of the preceding technical solutions.

[0276] The processor can include various types of storage media that are non-transitory computer storage media that continue to store information even after power is turned off from the communication device.

[0277] Here, the communication device includes a UE or a network device.

[0278] The processor can be connected with the memory through a bus or the like, for reading an executable program stored on the memory, for example, as shown in Figure 2 、 Figures 5 to 10 at least one of the methods.

[0279] Figure 13 is a block diagram of a UE 800 according to an exemplary embodiment. The UE 800 can be, for example, 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, or the like.

[0280] Referring to Figure 13 , the UE 800 can include one or more of the following components: a processing component 802, a memory component 804, a power supply 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.

[0281] The processing component 802 usually controls overall operations of the UE 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 can include one or more processors 820 to execute instructions to complete all or part of steps of the above methods. In addition, the processing component 802 can include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0282] The memory 804 is configured to store various types of data to support operations of the UE 800. Examples of these data include instructions for any application or method operating on the UE 800, contact data, phonebook data, messages, pictures, videos, and the like. The memory 804 can be implemented by any type of volatile or non-volatile storage devices 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 storage, flash memory, magnetic disk or optical disk.

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

[0284] The multimedia component 808 includes a screen providing an output interface between the UE 800 and a user. In some embodiments, the screen can 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 a user. The touch panel includes one or more touch sensors to sense touch, swiping, and gestures on the touch panel. The touch sensors can not only sense a boundary of a touching or swiping action, but also detect duration and pressure related to the touching or swiping action. 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 and rear cameras can be a fixed optical lens system or have a focal length and optical zoom capability.

[0285] 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 also includes a speaker for outputting audio signals.

[0286] The I / O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which can be a keyboard, a click wheel, a button, and the like. The buttons can include, but are not limited to, a home button, a volume button, a start button, and a lock button.

[0287] The sensor assembly 814 includes one or more sensors for providing various aspects of the status assessment of the UE 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the UE 800. The sensor assembly 814 can also detect changes 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 changes in the temperature of the UE 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0288] The communication component 816 is configured to facilitate wired or wireless communication between the UE 800 and other devices. The UE 800 can access a wireless network based on a communication standard, 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 also 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.

[0289] In an exemplary embodiment, UE800 may 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 to perform the above methods.

[0290] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is further provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the UE 800 to perform 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, an optical data storage device, etc.

[0291] like Figure 14 As 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 communication device can be the aforementioned UE and / or network device.

[0292] Reference Figure 14 The network device 900 includes a processing component 922, which further includes one or more processors, and a memory resource represented by a memory 932 for storing instructions executable by the processing component 922, such as applications. The applications 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 aforementioned methods applied to the network device, such as Figure 2 、 Figures 5 to 5 , the method shown in 10.

[0293] The network device 900 may also include a power supply component 926 configured to perform power management for 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 Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0294] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0295] It should be understood that the present invention is not limited to the exact construction 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 invention is limited only by the appended claims.

Claims

1. A tracking area TA exception handling method, wherein: Executed by a network device, the method includes: Receive a non-access stratum NAS request message; In response to the NAS request message, determining that a TA exception occurs in which the TA currently located by the UE is outside the registration area RA of the UE, and determining subsequent processing according to the TA exception processing decision information; Determining subsequent processing according to the TA exception processing decision information includes: Determining a response tolerance delay, a service delay requirement, and / or a UE location accuracy requirement for the NAS request message according to the TA exception handling decision information; The subsequent processing is determined according to the response tolerance delay, service delay requirement and / or UE location accuracy requirement.

2. The method according to claim 1, wherein The subsequent processing includes at least one of the following: Ignore the TA exception and respond to the NAS request message; rejecting the NAS request message, and triggering the UE to initiate a registration update to update the RA; Respond to the NAS request message, and trigger the UE to initiate a registration update to update the RA after the NAS request message response is completed.

3. The method according to claim 2, wherein: The rejecting the NAS request message includes: Sending a rejection message of the NAS request message to the UE, wherein the rejection message includes a rejection reason; the rejection reason indicates that the TA is abnormal.

4. The method according to claim 3, wherein: The rejection reason indicating TA abnormality is used to trigger the UE to initiate a registration update to update the RA of the UE.

5. The method according to claim 2, wherein: The method further comprises at least one of the following: In response to receiving a registration update request from the UE when determining to trigger an RA update for the UE, stopping triggering the registration update; In response to determining that the RA update time for triggering the UE is the update time of the registration update period of the UE, the triggering of the registration update is stopped.

6. The method according to claim 1, wherein The TA exception handling decision information includes at least one of the following: Device type information of the UE; The service type involved in the NAS request message; The data network name DNN involved in the NAS request message; Network slice information involved in the NAS request message; Network slice information subscribed by the UE; The operator operation policy associated with the UE.

7. The method according to any one of claims 1 to 6, wherein: The NAS request message includes at least one of the following: Protocol Data Unit PDU session establishment request message; Service request message.

8. A TA exception handling method, executed by a user equipment (UE), comprising: Sending a registration update request based on a triggering of a TA abnormality of the UE by the network side, wherein the registration update request is used to at least update the RA of the UE, wherein the TA abnormality includes: the TA currently located by the UE is outside the RA of the UE; The method further comprises: Sending a NAS request message; wherein, the NAS request message, after adding the location information of the UE when passing through the access network device, is used to determine whether the UE has the TA abnormality; the response tolerance delay and / or service delay requirement and / or UE location accuracy requirement of the NAS request message is used by the network side to determine subsequent processing when the TA abnormality occurs.

9. The method according to claim 8, wherein The method further comprises: receiving a rejection message of the NAS request message; The rejection message includes a rejection reason indicating that the TA is abnormal, and the UE sends the registration update request based on the rejection reason.

10. The method according to claim 8, wherein The method further comprises: A trigger indication is received, wherein the trigger indication is used to trigger the UE to send the registration update request and is sent after the NAS request message is responded to.

11. A TA abnormality handling device, wherein: The device comprises: A first receiving module is configured to receive a NAS request message; a determining module configured to, in response to the NAS request message, determine that a TA exception occurs in which the TA currently located by the UE is outside the registration area RA of the UE, and determine subsequent processing according to the TA exception processing decision information; The determination module is further configured to determine the response tolerance delay, service delay requirement and / or UE location accuracy requirement of the NAS request message according to the TA exception handling decision information; and determine the subsequent processing according to the response tolerance delay, service delay requirement and / or UE location accuracy requirement.

12. The device according to claim 11, wherein The subsequent processing includes at least one of the following: Ignore the TA exception and respond to the NAS request message; rejecting the NAS request message, and triggering the UE to initiate a registration update to update the RA; Respond to the NAS request message, and trigger the UE to initiate a registration update to update the RA after the NAS request message response is completed.

13. The device according to claim 12, wherein The rejecting the NAS request message includes: Sending a rejection message of the NAS request message to the UE, wherein the rejection message includes a rejection reason; the rejection reason indicates that the TA is abnormal.

14. The device according to claim 13, wherein The rejection reason indicating TA abnormality is used to trigger the UE to initiate a registration update to update the RA of the UE.

15. The device according to claim 12, wherein The apparatus further includes a stopping module configured to perform at least one of the following: In response to receiving a registration update request from the UE when determining to trigger an RA update for the UE, stopping triggering the registration update; In response to determining that the RA update time for triggering the UE is the update time of the registration update period of the UE, the triggering of the registration update is stopped.

16. The device according to claim 11, wherein The TA exception handling decision information includes at least one of the following: Device type information of the UE; The service type involved in the NAS request message; The data network name DNN involved in the NAS request message; Network slice information involved in the NAS request message; Network slice information subscribed by the UE; The operator operation policy associated with the UE.

17. The device according to any one of claims 11 to 16, wherein The NAS request message includes at least one of the following: Protocol Data Unit PDU session establishment request message; Service request message.

18. A TA exception handling device, applied to a UE, comprising: A first sending module is configured to send a registration update request based on a network side triggering a TA abnormality of the UE, wherein the registration update request is at least used to update the RA of the UE, wherein the TA abnormality includes: the TA currently located by the UE is outside the RA of the UE; The second sending module is configured to send a NAS request message; wherein, the NAS request message is added with the location information of the UE when passing through the access network device, and is used to determine whether the UE has the TA abnormality; the response tolerance delay and / or service delay requirement and / or UE location accuracy requirement of the NAS request message are used by the network side to determine subsequent processing when the TA abnormality occurs.

19. The device according to claim 18, wherein The device further comprises: a second receiving module, configured to receive a rejection message of the NAS request message; The rejection message includes a rejection reason indicating that the TA is abnormal, and the UE sends the registration update request based on the rejection reason.

20. The apparatus according to claim 18, wherein The device further comprises: The third receiving module is configured to receive a trigger indication, wherein the trigger indication is used to trigger the UE to send the registration update request and is sent after the NAS request message is responded to.

21. A communication device comprising a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being run by the processor, wherein: When the processor runs the executable program, the method provided in any one of claims 1 to 7 or 8 to 10 is performed.

22. 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 7, or 8 to 10.

Images