Method and apparatus for processing tracking area anomaly, communication device, and storage medium
AssigneeBeijing Xiaomi Mobile Software Co., Ltd.
InventorsDong Chen, Yang Shen
Life of this patent
Estimating the term…
Abstract
A method, apparatus and computer readable medium for processing a tracking area anomaly in a wireless communication system. The tracking area anomaly is processed by: recording, in response to determining that the TA anomaly in which a TA where user equipment (UE) is currently positioned is located outside a registration area (RA) of the UE occurs, the TA anomaly. Then triggering an RA update for the UE in response to the TA anomaly.
Claims18
A method for processing a tracking area (TA) anomaly, executed by a network device and comprising:
- receiving a non-access stratum (NAS) request message, wherein the NAS request message encompasses information of the TA where user equipment (UE) is currently positioned;
- determining whether the TA where the UE is currently positioned is located outside a registration area (RA) of the UE according to the NAS request message;
- determining that a TA anomaly occurs in response to determining that the TA where the UE is currently positioned is located outside the RA;
- neglecting, in response to determining that the TA anomaly that the TA where the UE is currently positioned is located outside the RA of the UE occurs, the TA anomaly, and continuing performing a NAS flow of the NAS request message;
- recording the TA anomaly and forming state information of a TA anomaly state;
- determining, based on the state information of the TA anomaly state, whether the TA anomaly exists when paging the UE;
- triggering an RA update of the UE in response to the TA anomaly;
- and
- paging the UE after the RA update of the UE is completed,
- wherein the method further comprises:
- receiving a registration update request initiated by the UE in response to a record of the TA anomaly existing;
- monitoring an execution of a registration flow corresponding to the registration update request;
- and
- removing the record of the TA anomaly after the RA update corresponding to the registration update request is completed, and
- wherein the registration update request comprises:
- the registration update request initiated in a case where the UE receives the triggering of the TA anomaly;
- a registration update request triggered by location movement of the UE;
- or
- a periodic registration update request initiated by the UE.
A method for processing a tracking area (TA) anomaly, executed by user equipment (UE) and comprising:
- sending a non-access stratum (NAS) request message, wherein the NAS request message, after being added with location information of the UE at a time of passing through an access network device, is configured for a core network to determine whether the TA anomaly of the UE occurs;
- receiving a triggering indication sent by a network side based on the TA anomaly of the UE, wherein the TA anomaly comprises:
- a TA where the UE is currently positioned is located outside a registration area (RA) of the UE, and
- the triggering indication is sent by the network side when it determines to page the UE and determines, based on state information of a TA anomaly state, that the UE to be paged has the TA anomaly;
- and
- performing an RA update according to the triggering indication,
- wherein the network side pages the UE after the RA update is completed, the state information is recorded by the network side when it determines, based on the NAS request message, that the TA anomaly that the TA where the UE is currently positioned is located outside the RA of the UE occurs,
- wherein the core network, when determining that the TA anomaly occurs, neglects the TA anomaly and continues performing a NAS flow triggered by the NAS request message, and a record of the TA anomaly is removed after the core network receives a registration update request initiated by the UE and completes the RA update corresponding to the registration update request, and
- wherein the registration update request comprises:
- the registration update request initiated in a case where the UE receives the triggering indication of the TA anomaly,
- a registration update request triggered by location movement of the UE, or
- a periodic registration update request initiated by the UE.
A communication device, comprising:
- one or more processors;
- a transceiver;
- a memory;
- and
- an executable program stored in the memory and runnable by the one or more processors,
- wherein the one or more processors are collectively configured to:
- receive a non-access stratum (NAS) request message, wherein the NAS request message encompasses information of a tracking area (TA) where user equipment (UE) is currently positioned,
- determine whether the TA where the UE is currently positioned is located outside a registration area (RA) of the UE according to the NAS request message,
- determine that a TA anomaly occurs in response to determining that the TA where the UE is currently positioned is located outside the RA,
- neglect, in response to determining that the TA anomaly that the TA where the UE is currently positioned is located outside the (RA) of the UE occurs, the TA anomaly, and continue performing a NAS flow of the NAS request message,
- record the TA anomaly and forming state information of a TA anomaly state,
- determine, based on the state information of the TA anomaly state, whether the TA anomaly exists when paging the UE,
- trigger an RA update of the UE in response to the TA anomaly, and
- page the UE after the RA update of the UE is completed,
- wherein the one or more processors are further collectively configured to:
- receive a registration update request initiated by the UE in response to a record of the TA anomaly existing,
- monitor an execution of a registration flow corresponding to the registration update request, and
- remove the record of the TA anomaly after the RA update corresponding to the registration update request is completed, and
- wherein the registration update request comprises:
- the registration update request initiated in a case where the UE receives the trigger of the TA anomaly,
- a registration update request triggered by location movement of the UE, or
- a periodic registration update request initiated by the UE.
Dependencies are inferred from the claim text.