WO2023000161A1 - 跟踪区异常处理方法及装置、通信设备及存储介质 - Google Patents

跟踪区异常处理方法及装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2023000161A1
WO2023000161A1 PCT/CN2021/107292 CN2021107292W WO2023000161A1 WO 2023000161 A1 WO2023000161 A1 WO 2023000161A1 CN 2021107292 W CN2021107292 W CN 2021107292W WO 2023000161 A1 WO2023000161 A1 WO 2023000161A1
Authority
WO
WIPO (PCT)
Prior art keywords
abnormality
request message
update
registration
amf
Prior art date
Application number
PCT/CN2021/107292
Other languages
English (en)
French (fr)
Inventor
陈栋
沈洋
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2021/107292 priority Critical patent/WO2023000161A1/zh
Priority to CN202180002212.1A priority patent/CN115836537A/zh
Publication of WO2023000161A1 publication Critical patent/WO2023000161A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • the present disclosure relates to but not limited to the technical field of wireless communication, and in particular relates to a tracking area (Tracking Area, TA) exception handling method and device, communication equipment, and a storage medium.
  • TA Tracking Area
  • a user equipment When a user equipment (User Equipment, UE) initially connects to the network, it will send a registration request to the network, and the network side will respond to the registration request.
  • the network side will record the registration area (Registration Area, RA) of the UE, and usually the registration area contains one or more TAs.
  • the network side will record the RA of the UE in the form of a TA list (TA list, TAL).
  • the UE may enter a new TA, but the new TA is not included in the TAI corresponding to the RA, and the UE does not perceive the entry of the new TA, so it will not initiate a registration update process to update the TA, which caused the TA exception.
  • Embodiments of the present disclosure provide a TA exception handling method and device, a communication device, and a storage medium.
  • the first aspect of the embodiments of the present disclosure provides a TA exception handling method, which is executed by a network device, and the method includes:
  • the TA exception occurs, recording the TA exception;
  • an RA update of the UE is triggered.
  • the second aspect of the embodiments of the present disclosure provides a TA exception handling device, wherein the device includes:
  • a recording module configured to record the TA anomaly in response to determining that the TA where the UE is currently located is outside the RA of the UE occurs;
  • the triggering module is configured to trigger the RA update of the UE based on the abnormal existence of the TA.
  • the third aspect of the embodiments of the present disclosure provides a communication device, including a processor, a transceiver, a memory, and an executable program stored on the memory and capable of being run by the processor, wherein the processor runs the executable
  • the program executes the TA exception handling method provided in the aforementioned first aspect.
  • the fourth aspect of the embodiments of the present disclosure provides a computer storage medium, where the computer storage medium stores an executable program; after the executable program is executed by a processor, the TA exception handling method provided by the aforementioned first aspect can be implemented.
  • the technical solution provided by the embodiments of the present disclosure will record the TA abnormality of the UE after discovering the TA abnormality of the UE. Based on the TA abnormality, the network side will actively trigger the UE to perform RA update, thereby eliminating the TA abnormality, and then suppressing the paging failure caused by the TA abnormality Wait for the exception associated with the TA to occur.
  • Fig. 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment
  • Fig. 2 is a schematic flowchart of a TA exception handling method according to an exemplary embodiment
  • Fig. 3 is a schematic diagram of TA switching of a wireless cell according to an exemplary embodiment
  • Fig. 4 is a schematic diagram of TA switching of another wireless cell according to an exemplary embodiment
  • Fig. 5 is a schematic flowchart of a TA exception handling method according to an exemplary embodiment
  • Fig. 6 is a schematic flowchart of a TA exception handling method according to an exemplary embodiment
  • Fig. 7 is a schematic flowchart of a TA exception handling method according to an exemplary embodiment
  • Fig. 8 is a schematic flowchart of a TA exception handling method according to an exemplary embodiment
  • Fig. 9 is a schematic flowchart of a TA exception handling method according to an exemplary embodiment
  • Fig. 10 is a schematic flowchart of a TA exception handling method according to an exemplary embodiment
  • Fig. 11 is a schematic structural diagram of a TA exception handling device according to an exemplary embodiment
  • Fig. 12 is a schematic structural diagram of a TA exception handling device according to an exemplary embodiment
  • Fig. 13 is a schematic structural diagram of a UE according to an exemplary embodiment
  • Fig. 14 is a schematic structural diagram of a network device according to an exemplary embodiment.
  • first, second, third, etc. may use the terms first, second, third, etc. to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of the embodiments of the present disclosure, first information may also be called second information, and similarly, second information may also be called first information.
  • first information may also be called second information
  • second information may also be called first information.
  • the word “if” as used herein may be interpreted as “at” or "when” or "in response to a determination”.
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: several UEs 11 and several access devices 12 .
  • UE11 may be a device that provides voice and/or data connectivity to a user.
  • UE11 can communicate with one or more core networks via a radio access network (Radio Access Network, RAN), and UE11 can be an Internet of Things UE, such as a sensor device, a mobile phone (or called a "cellular" phone) and a device with an Internet of Things
  • RAN Radio Access Network
  • UE11 can be an Internet of Things UE, such as a sensor device, a mobile phone (or called a "cellular" phone) and a device with an Internet of Things
  • the UE's computer for example, may be a fixed, portable, pocket, hand-held, built-in or vehicle-mounted device.
  • UE11 may also be a device of an unmanned aerial vehicle.
  • UE11 may also be a vehicle-mounted device, for example, it may be a trip computer with a wireless communication function, or a wireless communication device connected externally to the trip computer.
  • the UE11 may also be a roadside device, for example, it may be a street lamp, a signal lamp, or other roadside devices with a wireless communication function.
  • the access device 12 may be a network side device in a wireless communication system.
  • the wireless communication system may be a fourth generation mobile communication technology (the 4th generation mobile communication, 4G) system, also known as a Long Term Evolution (LTE) system; or, the wireless communication system may also be a 5G system, Also known as new radio (NR) system or 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network, New Generation Radio Access Network).
  • the MTC system the MTC system.
  • the access device 12 may be an evolved access device (eNB) adopted in a 4G system.
  • the access device 12 may also be an access device (gNB) adopting a centralized and distributed architecture in the 5G system.
  • eNB evolved access device
  • gNB access device
  • the access device 12 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
  • the centralized unit is provided with a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer, radio link layer control protocol (Radio Link Control, RLC) layer, media access control (Media Access Control, MAC) layer protocol stack;
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC media access control
  • a physical (Physical, PHY) layer protocol stack is set in the unit, and the embodiment of the present disclosure does not limit the specific implementation manner of the access device 12 .
  • a wireless connection may be established between the access device 12 and the UE 11 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, such as
  • the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on a technical standard of a next-generation mobile communication network based on 5G.
  • an E2E (End to End, end-to-end) connection can also be established between UE11.
  • V2V vehicle to vehicle, vehicle-to-vehicle
  • V2I vehicle to Infrastructure, vehicle-to-roadside equipment
  • V2P vehicle to pedestrian, vehicle-to-person communication in vehicle to everything (V2X) communication Wait for the scene.
  • the above wireless communication system may further include a network management device 13 .
  • the network management device 13 may be a core network device in the wireless communication system, for example, the network management device 13 may be a mobility management entity (Mobility Management Entity, MME).
  • MME Mobility Management Entity
  • the network management device can also be other core network devices, such as Serving GateWay (SGW), Public Data Network Gateway (Public Data Network GateWay, PGW), policy and charging rule functional unit (Policy and Charging Rules Function, PCRF) or Home Subscriber Server (Home Subscriber Server, HSS), etc.
  • SGW Serving GateWay
  • PGW Public Data Network Gateway
  • PCRF Policy and Charging Rules Function
  • HSS Home Subscriber Server
  • the embodiment of the present disclosure provides a TA exception handling method, which is executed by a network device, and the method includes:
  • S120 Trigger an RA update of the UE based on the abnormal existence of the TA.
  • the network equipment here includes but not limited to core network equipment, and the core network equipment includes but not limited to Access Management Function (Access Management Function, AMF).
  • AMF Access Management Function
  • the UE will record an RA on the network side during the previous registration, and the RA includes TACs of one or more TAs. If the location of the UE changes and enters a new TA, and the current TA of the UE is outside the TA in the RA, but the UE does not initiate the registration update process to implement the RA update, it is determined that a TA abnormality occurs.
  • the unified data management (Unified Data Management, UDM) or AMF on the network side records the RA of the UE.
  • UDM Unified Data Management
  • the UDM and AMF of the UE and/or the network device record the RA of the UE.
  • the network side determines that such TA abnormality occurs, it will record this TA abnormality.
  • a network device such as the AMF will record the abnormal state of the TA, and form state information of the abnormal state of the TA.
  • the UE sends a Non-Access Stratum (Non-Access Stratum, NAS) request message, and after the access network device (for example, a base station) receives the NAS request message, the access network device such as the base station sends the UE's The location information (including the TA where the UE is currently located) is included in the NAS request message and sent to the core network device (for example, AMF). If the core network device finds that the TA where the UE is located is not included in the TA recorded by the network side, it determines that the TA is abnormal.
  • NAS Non-Access Stratum
  • the core network device When the UE makes a service request or requests to establish a protocol data unit (Protocol Data Unit, PDU) session, the core network device receives the NAS request message, and after receiving the NAS request message, the core network device enters the NAS processing flow to perform the NAS request message the response to.
  • PDU Protocol Data Unit
  • the NAS request message includes but is not limited to at least one of the following:
  • Protocol Data Unit Protocol Data Unit (Protocol Data Unit, PDU) session establishment request message
  • the UE accesses a cell (for example, a cell under satellite access)
  • the UE moves to a new TA, but the new TA is not included in the TAs included in the RA registered by the UE, and a TA exception occurs.
  • the UE itself finds that it has entered a new TA, it will actively trigger the registration update process.
  • the UE does not perceive that it has entered a new TA, it may not actively initiate the registration update process, so as to directly reach the network side.
  • the network side device discovers the UE's This TA is abnormal.
  • the UE is at TA1 and accesses the 5G core network through the satellite.
  • the satellite broadcasts multiple TAs (TA1 and TA2) to the UE.
  • the UE completes the access registration, and the network side generates RA for the UE (including TA1 and other TAs, but not including TA2).
  • the UE moves into TA2. Since the TA broadcast by the satellite to the UE is the same at T1 and T2, the UE does not perceive that the TA update has occurred, so the UE will not actively initiate a registration update to update the RA.
  • the gNB will report the UE's current location TA2 to the network side, and the network side finds that the UE's current location TA2 is not included in the UE's RA, which causes the UE's TA to be abnormal.
  • the above is only a simple example of the cause of the TA abnormality of the UE, and there are many methods for specific implementation, which are not limited to the above examples.
  • the satellite can be connected to the 5G core network (Core Network, CN), and the wireless cell may broadcast one or more TACs for a PLMN, and the UE will determine its own TA based on the broadcast information.
  • Core Network Core Network
  • the wireless cell broadcasts a TAC, and the UE regards the TA as its current TA.
  • the possible TAC for broadcasting can be the TAC of TA1; if the satellite and wireless cell move, for example, as shown in Figure 3 Moving from left to right as shown, the wireless cell may simultaneously cover two TAs (TA1 and TA2) at a certain moment, or gradually switch from covering TA1 to not covering TA1 and completely covering TA2.
  • the satellite and the wireless cell move into TA2 it will consider that the TA where the current wireless cell is located is TA2, and may broadcast the TAC of TA2 to the UE.
  • a wireless cell broadcasts multiple TACs at one time.
  • the satellite and the wireless cell will simultaneously broadcast the TACs of TA1 and TA2 to the UE.
  • the satellite and the wireless cell move to cover TA2 and other TAs to the right of TA2, and the satellite and the wireless cell will broadcast the TACs of TA2 and other TAs to the UE.
  • the AMF pages the UE according to the TAC included in the RA of the UE. If the AN or RAN may determine the TA where the UE is currently located from the RA, and page the UE in the TA.
  • the UE will initiate a registration update.
  • the network equipment of the core network such as the AMF will update the RA of the UE.
  • the updated TA includes the current TA of the UE.
  • the UE if at time T1, the UE is located at TA1, and accesses the 5G network through satellites.
  • the satellite and the wireless cell broadcast TA1 and TA2 to the UE, and the UE determines the TA it is in according to the broadcast information, and completes the registration.
  • the AMF generates an RA for the UE (including TA1 and other TAs, but not including TA2).
  • the UE moves from TA1 to TA2. Since the satellite and the wireless cell continue to broadcast TA1 and TA2 to the UE at T1 and T2, the UE may not be able to perceive the change of the TA it is in, and will not trigger a registration update to update RA.
  • the gNB will report the current TA2 of the UE (acquired by the gNB through measurement) to the AMF, and the AMF determines that the TA2 of the UE is not included in the RA of the UE. At this time, the AMF can It is determined that the foregoing TA abnormality has occurred in the UE.
  • the base station After the base station receives the NAS request message sent by the UE, the base station includes the location information of the UE (including the TA where the UE is currently located) in the NAS request message. Part of the location information (User Location Information, ULI). If the TA indicated by the ULI is not included in the RA of the UE, a TA exception unknown to the UE will occur.
  • ULI User Location Information
  • a trigger indication is sent to the UE.
  • the trigger indication can be used to instruct the UE to perform the registration update process, so that the UE will update the RA through the registration update process.
  • This kind of TA anomaly can be eliminated by including the current TA of the UE in the RA update.
  • the network device issues a trigger indication of the registration update process based on the abnormality of the TA.
  • the indication information is used to indicate the reason why the UE initiates the registration update procedure.
  • Figure 5 shows a registration process, which may include:
  • the access network (Access Network, AN) or RAN receives the registration request of the UE; the registration request includes: AN parameters, registration type, user subscription permanent identifier (Subscription Permanent Identifier, SUPI) or fifth-generation mobile communication (5G) global Unique temporary user identifier (Globally Unique Temporary UE Identity, GUTI), user equipment identifier (Permanent Equipment Identifier, PEI), requested NSSAI, last accessed and available TAI, etc.
  • the registration type indicates if the UE needs to perform initial registration, mobile registration update, periodic registration update or permanent registration.
  • the last visited TAI can be used to help network devices such as AMF determine the RA of the UE.
  • the AN or RAN After receiving the registration request, the AN or RAN selects the AMF for the UE; for example, the AN or the RAN selects the AMF for the UE according to information such as the RAT used to transmit the registration request and the requested NASSAI. If the RAN cannot select an appropriate AMF for the UE, it sends the AMF configured by the RAN or the AN to the RAN registration message, that is, selects the AMF configured by the RAN or the AN as the AMF of the UE.
  • the N2 parameter of the N2 message may include, but not limited to: registration request, the identity (Identity, ID) of the selected public land mobile network (Public Land Mobile Network, PLMN), location information, cell ID of the cell where the UE is located, and other information.
  • identity Identity, ID
  • PLMN Public Land Mobile Network
  • the new AMF will obtain the UE's SUPI and UE context from the old AMF;
  • the new AMF will initiate an ID request process to obtain SUCI.
  • the new AMF will determine to initiate UE authentication involving the Authentication Server Function (AUSF) to the UE. For example, the new AMF will select an AUSF based on the UE's SUPI or SUCI.
  • AUSF Authentication Server Function
  • the AMF of the UE If the AMF of the UE has switched compared to the last registration process, or the SUPI provided by the UE does not involve a valid context in the AMF, the AMF will select and register to a unified data management (Unified Data Management, UDM) based on the SUPI. If the AMF does not obtain the subscription data of the UE, it will obtain the subscription data of the UE from the UDM.
  • UDM Unified Data Management
  • AMF mobility management
  • the AMF shall send a Nssmf_PDU Session_Update SM Context request to the SMF associated with the PDU session to activate the user plane connection for the PDU session.
  • the new AMF sends a Registration Accept message to the UE to indicate that the registration request is accepted.
  • the registration acceptance message includes: RA, mobility restriction, allowed NASSAI, periodic registration timer indication and other information. If the AMF allocates a new RA, it sends the information of the new RA to the UE. If no new RA is allocated to the UE, the registration acceptance message will not carry the information of the RA, and indicates that the old RA is still valid.
  • the S120 may include:
  • the S120 may include:
  • the TA Before executing the service flow or control flow associated with the UE's RA or its TA, it is determined whether the TA is abnormal.
  • the method may further include: when paging the UE, first determining whether the TA abnormality exists, so at S120 may include: determining that there is a TA abnormality of the UE when paging the UE, then triggering The UE performs RA update. After the UE completes the RA update, the abnormal TA of the UE is removed, so that the UE can be paged according to the TA where the UE is located, thereby suppressing the paging failure caused by the abnormal TA of the UE.
  • the embodiment of the present disclosure provides a TA exception handling method, which may include:
  • S210 In response to determining that there is a TA abnormality, record the TA abnormality of the UE;
  • S220 Determine that there is a TA abnormality when paging the corresponding UE, and trigger the RA update of the UE;
  • the TA abnormality is recorded on the network side. For example, it is recorded in the AMF.
  • the AMF first checks whether the UE to be paged has a TA abnormality. If there is a TA abnormality, it needs to be eliminated first.
  • This kind of TA anomaly can be achieved by triggering the RA update of the UE when eliminating the TA anomaly.
  • triggering the RA update of the UE by the network side may include: sending a trigger indication to the UE, instructing the UE to initiate a registration update procedure. After receiving the trigger indication, the UE will send a registration update request to the network side.
  • the RA of the UE includes the TA where the UE is located, thereby eliminating this TA anomaly.
  • a TA exception handling method in an embodiment of the present disclosure is executed by a network device and may include:
  • S310 Receive a NAS request message; wherein, the NAS request message includes location information such as the TA where the UE is currently located;
  • S320 According to the NAS request message, determine whether the TA where the UE is currently located is outside the RA of the UE;
  • the network device may be a network device of a core network such as an AMF.
  • the base station After the base station receives the NAS request message sent by the UE, the base station includes the location information of the UE (including location information such as the TA where the UE is currently located) in the NAS request message and sends it to the core network device (for example, AMF). If the core network device finds that the TA where the UE is located is not included in the TA recorded by the network side, it determines that the TA is abnormal. For example, the base station adds the TA where the UE is currently located in the UE's User Location Information (User Location Information, ULI) contained in the UE's NAS request message.
  • ULI User Location Information
  • the method provided by the embodiment of the present disclosure may be executed alone, or may be a specific implementation of the aforementioned step S110.
  • the network device can determine whether the UE has TA abnormality according to the NAS request message.
  • the method further includes:
  • responding to the NAS request message as usual may be: assuming that the TA abnormality does not exist, continue to execute the subsequent steps of the NAS process triggered by the NAS request message.
  • the method also includes:
  • the record of the abnormal TA is removed.
  • the UE may also actively initiate a registration update process.
  • the RA of the UE recorded on the network side is updated
  • the UE wants to change the network parameters negotiated with the network side in the previous registration process, it can also be implemented according to the registration update process;
  • the UE when the update time of periodic registration update is reached, the UE also actively initiates a registration update process, so as to realize the registration update.
  • the TA abnormality is recorded. If the recorded TA exception is not eliminated, the registration update request initiated by the UE or triggered by the network side is received, the execution of the registration process will be monitored, and the registration process corresponding to the registration update request is completed. After the RA recorded by the UE and/or the network side is updated, the abnormal TA record will be removed. If the UE's TA abnormality record is removed, when the UE's TA abnormality is inquired in S120, it will be found that there is no TA abnormality in the UE.
  • the registration update request includes: the UE receives the registration update request initiated by a TA abnormal trigger; or,
  • the registration update request triggered by the location movement of the UE; or, the periodic registration update request initiated by the UE.
  • the network device includes: AMF.
  • an embodiment of the present disclosure provides a TA exception handling method, which is executed by the UE, and the method includes:
  • S410 Receive a trigger indication sent by the network side based on the TA abnormality of the UE; the trigger indication is used to trigger the UE to perform a registration update process; S420: Perform RA update according to the trigger indication.
  • the network side includes but not limited to the core network side.
  • the TA exception here includes: the TA where the UE is currently located is outside the RA of the UE. And the TA abnormality is determined by the network side.
  • the network side finds that the TA of the UE is abnormal, it will actively trigger the UE to update the RA.
  • the network side will issue a trigger indication, and the trigger indication may be: any indication issued by the network side to trigger the UE to initiate a registration update request.
  • the trigger instruction includes but not limited to a configuration update instruction.
  • the method also includes:
  • the NAS request message carries a ULI, and the ULI includes location information such as the TA where the UE is located.
  • the network side finds that the TA included in the NAS request message is not included in the RA of the UE, and considers that the TA of the UE is abnormal. If such a TA abnormality occurs, the TA abnormality will be recorded.
  • the network side Before the network side executes the service process or control process associated with the UE's RA or its TA, it checks whether the UE's TA is abnormal. If so, the UE will receive a registration update trigger indication sent by the network side.
  • the UE can initiate a registration update request according to the trigger indication, and update the RA of the UE and/or the network side through the registration update process corresponding to the registration update request, so as to eliminate this TA anomaly.
  • the trigger indication is received prior to paging the UE.
  • the trigger indication is received before the UE is paged, which means that the TA anomaly can be eliminated through RA update, thereby ensuring the paging success rate of the UE.
  • the AMF In order to solve the UE's TA anomaly, if the UE's TA anomaly is detected, the AMF records this TA anomaly while ignoring the detected TA anomaly. After that, if the process of paging the UE occurs, the AMF will trigger the UE to initiate a registration update to resolve the TA exception. After the TA is removed after being abnormal, the UE is paged again.
  • this method can not only solve the TA abnormality of the UE, but also have no negative impact on the paging of the UE.
  • the AMF when the AMF receives a NAS request message (example, the NAS request message includes but not limited to: a PDU establishment request message or a service request message), it may determine whether TA abnormality occurs according to the NAS request message. If the AMF detects this TA anomaly, it will ignore the TA anomaly, record the TA anomaly in the AMF, and continue to respond to the NAS request message, that is, execute the NAS process corresponding to the NAS request message as usual.
  • a NAS request message includes but not limited to: a PDU establishment request message or a service request message
  • AMF records TA abnormalities. After that, if the registration update initiated by the UE due to UE movement or periodic registration update occurs, and the TA exception is eliminated, the recorded TA exception will be removed from the AMF, otherwise the record of this TA exception will continue to be saved in AMF.
  • the AMF determines whether the UE has TA exception. If the TA of the UE is abnormal recorded in the AMF, the AMF will trigger the UE to initiate a registration update procedure. After the registration update process is completed, the AMF will send a paging message based on the updated RA. If the AMF does not record the TA exception of the UE, the AMF will page the UE according to the normal procedure.
  • a registration process will be initiated, and the registration process will be completed between the UE and the core network (Core Network, CN); the registration process initiated when the UE accesses the network is between the UE and the CN (e.g. 5G CN) initial registration process.
  • Core Network CN
  • the registration process initiated when the UE accesses the network is between the UE and the CN (e.g. 5G CN) initial registration process.
  • the UE's RA will be stored in the AMF, and the RA may include one or more TAs.
  • the NAS request message carries the information that the base station indicates the TA where the UE is located;
  • the AMF After receiving the NAS request message, the AMF will detect whether there is any TA abnormality. If a TA anomaly occurs, the AMF shall ignore such TA anomaly and shall store the TA anomaly for the UE.
  • the AMF After the PDU session is established, if an emergency service needs to be started, the AMF will send a paging message to the UE. Before sending the paging message, the AMF judges whether there is an abnormal TA of the UE;
  • the AMF sends a message triggering the registration update process to the UE;
  • the UE Upon receiving the message triggering the registration update process, the UE initiates a registration update process to the 5G CN.
  • the RA of the UE includes the TA where the UE is located;
  • the AMF uses the updated RA to page the UE and activate the emergency service.
  • the UE when the UE accesses the network, it will initiate a registration process, which will be completed between the UE and the 5G core network (Core Network, CN); the registration initiated when the UE accesses the network can be considered as Initial registration.
  • the 5G core network Core Network, CN
  • the UE's RA will be stored in the AMF, and the RA may include one or more TAs.
  • the NAS request message carries the information that the base station indicates the TA where the UE is located;
  • the AMF After receiving the NAS request message, the AMF will detect whether there is any TA abnormality. If a TA anomaly occurs, the AMF shall ignore such TA anomaly and shall store the TA anomaly for the UE.
  • the AMF updates the RA of the UE, and the updated RA includes the TA where the UE is currently located.
  • the AMF removes the TA exception of the UE.
  • the AMF judges that there is no TA abnormality of the UE, it will initiate paging to the UE based on the recorded RA, and start the emergency service.
  • the TA abnormality of the UE when receiving the NAS request message containing the TA indicating the current location of the UE, the TA abnormality of the UE is detected. If the TA abnormality occurs, the AMF will ignore the TA abnormality and record the TA abnormality, and The NAS process for the NAS request message will continue.
  • the TA abnormality of the UE in the AMF will be removed, otherwise it will continue to be stored in the AMF.
  • the AMF If the UE is paged, when the AMF receives the paging message, it needs to determine whether the TA of the UE is abnormal. If the TA of the UE is abnormal, the AMF will trigger the UE to initiate a registration update process based on the TA abnormality. After the registration update process is completed, the AMF sends a paging message based on the RA of the UE. If there is no TA exception of the UE in the AMF, the AMF directly pages the UE without triggering the UE to initiate a registration update.
  • an embodiment of the present disclosure provides a TA exception handling device, which includes:
  • the recording module 110 is configured to record the TA abnormality in response to determining that the TA where the UE is currently located is outside the RA of the UE occurs;
  • the triggering module 120 is configured to trigger an RA update of the UE based on the abnormal existence of the TA.
  • the TA exception processing apparatus may be included in network equipment, and the network equipment includes but not limited to AMF.
  • the recording module 110 and the triggering module 120 may include a program module; after the program module is executed by the processor, when it is determined that the UE is outside the RA of the UE, the TA exception may be recorded.
  • the recording module 110 and the trigger module 120 can be a combination of hardware and software; the combination of hardware and software includes but is not limited to: various programmable arrays; the programmable array includes but is not limited to: field Programmable arrays and complex programmable arrays.
  • the recording module 110 and the triggering module 120 can be pure hardware modules; the pure hardware modules include but not limited to: application specific integrated circuits.
  • the device also includes:
  • the first determining module is configured to determine whether the TA abnormality exists when the UE is paged.
  • the device also includes:
  • the paging module is configured to page the UE after the RA update of the UE is completed.
  • the device also includes:
  • a receiving module configured to receive a non-access stratum NAS request message; wherein the NAS request message has information indicating the TA where the UE is currently located;
  • the second determination module is configured to determine whether the TA where the UE is currently located is outside the RA of the UE according to the NAS request message;
  • the third determining module is configured to determine that the TA abnormality occurs in response to the fact that the TA where the UE is currently located is outside the RA.
  • the device also includes:
  • the removal module is configured to, in response to receiving the registration update request initiated by the UE when the TA abnormality is recorded, remove the record of the TA abnormality after completing the RA update corresponding to the registration update request.
  • the registration update request includes:
  • the UE receives the registration update request initiated by TA abnormal trigger
  • the registration update request triggered by the location movement of the UE
  • a periodic registration update request initiated by the UE is a periodic registration update request initiated by the UE.
  • the network device includes: an access management function (AMF).
  • AMF access management function
  • an embodiment of the present disclosure provides a TA exception handling device, which is executed by the UE, and the device includes:
  • the receiving module 210 is configured to receive a trigger indication sent by the network side based on the TA abnormality of the UE;
  • the update module 220 is configured to perform RA update according to the trigger indication.
  • the TA abnormality here includes: the TA where the UE is currently located is outside the RA of the UE. And the TA abnormality is determined by the network side.
  • the UE may be various types of UEs, for example, including but not limited to: a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, or a robot capable of walking on the ground or a low-altitude flying aircraft.
  • the receiving module 210 and the updating module 220 may be program modules; after the program module is executed by the processor, it can receive a trigger instruction issued by the network side, and perform RA update based on the trigger instruction.
  • the receiving module 210 and the updating module 220 can be soft and hard combination modules; the soft and hard combination modules include but are not limited to various programmable arrays; the programmable arrays can include field programmable arrays and/or complex programmable arrays.
  • the receiving module 210 and the updating module 220 may be pure hardware modules; the pure hardware modules include but not limited to ASICs.
  • the device also includes:
  • a message module configured to send a NAS request message, wherein the NAS request message is used for the core network to determine whether the TA abnormality of the UE occurs after adding the location information of the UE to the NAS request message when passing through the access network device .
  • the trigger indication is received before the UE is paged.
  • the trigger indication may include indication information of TA abnormality.
  • the indication information is used to indicate the reason for triggering the UE to initiate the registration update procedure.
  • An embodiment of the present disclosure provides a communication device, including:
  • memory for storing processor-executable instructions
  • the processor is configured to implement any of the foregoing technical solutions to provide a TA exception handling method.
  • the processor may include various types of storage media, which are non-transitory computer storage media, and can continue to memorize and store information thereon after the communication device is powered off.
  • the communication device includes: UE and/or core network device.
  • the processor may be connected to the memory through a bus or the like, and used to read the executable program stored on the memory, for example, at least one of the methods shown in FIG. 2 and FIGS. 5 to 10 .
  • Fig. 13 is a block diagram of a UE 800 according to an exemplary embodiment.
  • UE 800 may be a mobile phone, computer, digital broadcast user equipment, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.
  • UE 800 may include one or more of the following components: processing component 802, memory 804, power supply component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and communication component 816 .
  • Processing component 802 generally controls the overall operations of UE 800, such as those associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method.
  • processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components.
  • processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802 .
  • the memory 804 is configured to store various types of data to support operations at the UE 800 . Examples of such data include instructions for any application or method operating on UE800, contact data, phonebook data, messages, pictures, videos, etc.
  • the memory 804 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Magnetic or Optical Disk Magnetic Disk
  • the power supply component 806 provides power to various components of the UE 800 .
  • Power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for UE 800 .
  • the multimedia component 808 includes a screen providing an output interface between the UE 800 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the UE800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.
  • the audio component 810 is configured to output and/or input audio signals.
  • the audio component 810 includes a microphone (MIC), which is configured to receive an external audio signal when the UE 800 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. Received audio signals may be further stored in memory 804 or sent via communication component 816 .
  • the audio component 810 also includes a speaker for outputting audio signals.
  • the I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.
  • Sensor component 814 includes one or more sensors for providing various aspects of status assessment for UE 800 .
  • the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and the keypad of the UE800, the sensor component 814 can also detect the position change of the UE800 or a component of the UE800, and the user and Presence or absence of UE800 contact, UE800 orientation or acceleration/deceleration and temperature change of UE800.
  • Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact.
  • Sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communications between UE 800 and other devices.
  • the UE800 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication.
  • NFC near field communication
  • the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID Radio Frequency Identification
  • IrDA Infrared Data Association
  • UWB Ultra Wide Band
  • Bluetooth Bluetooth
  • UE 800 may be powered by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gates Arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic implementations for performing the methods described above.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gates Arrays
  • controllers microcontrollers, microprocessors or other electronic implementations for performing the methods described above.
  • non-transitory computer-readable storage medium including instructions, such as the memory 804 including instructions, which can be executed by the processor 820 of the UE 800 to complete the above method.
  • the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
  • an embodiment of the present disclosure shows a structure of an access device.
  • the network device 900 may be provided as a network side device.
  • the network equipment includes but not limited to core network equipment.
  • network device 900 includes processing component 922 , which further includes one or more processors, and a memory resource represented by memory 932 for storing instructions executable by processing component 922 , such as application programs.
  • the application program stored in memory 932 may include one or more modules each corresponding to a set of instructions.
  • the processing component 922 is configured to execute instructions to perform any of the aforementioned methods applied to the network device, for example, the methods shown in FIG. 2 , FIG. 5 to FIG. 10 .
  • Network device 900 may also include a power supply component 926 configured to perform power management of network device 900, a wired or wireless network interface 950 configured to connect network device 900 to a network, and an input-output (I/O) interface 958 .
  • the network device 900 can operate based on an operating system stored in the memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例提供一种跟踪区异常处理方法及装置、通信设备及存储介质。由网络设备执行的TA异常处理方法可包括：响应于确定发生UE当前所处TA位于所述UE的RA外的TA异常，记录所述TA异常；基于所述TA异常存在，触发所述UE的RA更新。

Description

跟踪区异常处理方法及装置、通信设备及存储介质 技术领域
本公开涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及一种跟踪区(Tracking Area，TA)异常处理方法及装置、通信设备及存储介质。
背景技术
用户设备(User Equipment，UE)在初始连接到网络时，会向网络发送注册请求，网络侧会响应注册请求。在注册的过程中，网络侧会记录UE的注册区(Registration Area，RA)，通常注册区包含一个或多个TA。在一些情况下，网络侧会会以TA列表(TA list，TAL)的方式记录UE的RA。
随着无线小区或UE的移动，UE可能进入了新的TA，而该新的TA不包含在RA所对应的TAI内，且UE并未感知进入所述新的TA，因此不会发起注册更新流程以更新TA，这就导致了TA异常。
发明内容
本公开实施例提供一种TA异常处理方法及装置、通信设备及存储介质。
本公开实施例第一方面提供一种TA异常处理方法，由网络设备执行，所述方法包括：
响应于确定发生UE当前所处TA位于所述UE的RA外的TA异常，记录所述TA异常；
基于所述TA异常存在，触发所述UE的RA更新。
本公开实施例第二方面提供一种TA异常处理装置，其中，所述装置包括：
记录模块，被配置为响应于确定发生UE当前所处TA位于所述UE的RA外的TA异常，记录所述TA异常；
触发模块，被配置为基于所述TA异常存在，触发所述UE的RA更新。
本公开实施例第三方面提供一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如前述第一方面提供的TA异常处理方法。
本公开实施例第四方面提供一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现前述的第一方面提供的TA异常处理方法。
本公开实施例提供的技术方案发现UE的TA异常之后，会记录UE的TA异常，基于TA异常，网络侧会主动触发UE进行RA更新，从而消除TA异常，进而抑制TA异常导致的寻呼失败等与所在TA关联的异常发生。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开 实施例。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明实施例，并与说明书一起用于解释本发明实施例的原理。
图1是根据一示例性实施例示出的一种无线通信系统的结构示意图；
图2是根据一示例性实施例示出的一种TA异常处理方法的流程示意图；
图3是根据一示例性实施例示出的一种无线小区的TA切换的示意图；
图4是根据一示例性实施例示出的另一种无线小区的TA切换的示意图；
图5是根据一示例性实施例示出的一种TA异常处理方法的流程示意图；
图6是根据一示例性实施例示出的一种TA异常处理方法的流程示意图；
图7是根据一示例性实施例示出的一种TA异常处理方法的流程示意图；
图8是根据一示例性实施例示出的一种TA异常处理方法的流程示意图；
图9是根据一示例性实施例示出的一种TA异常处理方法的流程示意图；
图10是根据一示例性实施例示出的一种TA异常处理方法的流程示意图；
图11是根据一示例性实施例示出的一种TA异常处理装置的结构示意图；
图12是根据一示例性实施例示出的一种TA异常处理装置的结构示意图；
图13是根据一示例性实施例示出的一种UE的结构示意图；
图14是根据一示例性实施例示出的一种网络设备的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”、“”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于 确定”。
请参考图1，其示出了本公开实施例提供的一种无线通信系统的结构示意图。如图1所示，无线通信系统是基于蜂窝移动通信技术的通信系统，该无线通信系统可以包括：若干个UE11以及若干个接入设备12。
其中，UE11可以是指向用户提供语音和/或数据连通性的设备。UE11可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，UE11可以是物联网UE，如传感器设备、移动电话(或称为“蜂窝”电话)和具有物联网UE的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)、移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程UE(remote terminal)、接入UE(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户UE(user equipment，UE)。或者，UE11也可以是无人飞行器的设备。或者，UE11也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线通信设备。或者，UE11也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
接入设备12可以是无线通信系统中的网络侧设备。其中，该无线通信系统可以是第四代移动通信技术(the 4th generation mobile communication，4G)系统，又称长期演进(Long Term Evolution，LTE)系统；或者，该无线通信系统也可以是5G系统，又称新空口(new radio，NR)系统或5G NR系统。或者，该无线通信系统也可以是5G系统的再下一代系统。其中，5G系统中的接入网可以称为NG-RAN(New Generation-Radio Access Network，新一代无线接入网)。或者，MTC系统。
其中，接入设备12可以是4G系统中采用的演进型接入设备(eNB)。或者，接入设备12也可以是5G系统中采用集中分布式架构的接入设备(gNB)。当接入设备12采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对接入设备12的具体实现方式不加以限定。
接入设备12和UE11之间可以通过无线空口建立无线连接。在不同的实施方式中，该无线空口是基于第四代移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中，UE11之间还可以建立E2E(End to End，端到端)连接。比如车联网通信(vehicle to everything，V2X)中的V2V(vehicle to vehicle，车对车)通信、V2I(vehicle to Infrastructure，车对路边设备)通信和V2P(vehicle to pedestrian，车对人)通信等场景。
在一些实施例中，上述无线通信系统还可以包含网络管理设备13。
若干个接入设备12分别与网络管理设备13相连。其中，网络管理设备13可以是无线通信系统 中的核心网设备，比如，该网络管理设备13可以是演进的数据分组核心网(Evolved Packet Core，EPC)中的移动性管理实体(Mobility Management Entity，MME)。或者，该网络管理设备也可以是其它的核心网设备，比如服务网关(Serving GateWay，SGW)、公用数据网网关(Public Data Network GateWay，PGW)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)或者归属签约用户服务器(Home Subscriber Server，HSS)等。对于网络管理设备13的实现形态，本公开实施例不做限定。
如图2所示，本公开实施例提供一种TA异常处理方法，由网络设备执行，所述方法包括：
S110：响应于确定发生UE当前所处TA位于所述UE的RA外的TA异常，记录所述TA异常；
S120：基于所述TA异常存在，触发所述UE的RA更新。
此处的网络设备包括但不限于核心网设备，该核心网络设备包括但不限于接入管理功能(Access Management Function，AMF)。
UE在前一次注册时会在网络侧记录有RA，而RA包括一个或多个TA的TAC。若UE发生位置变化，进入新的TA，而UE当前所处TA位于RA内的TA外，但UE并没有发起注册更新流程实现RA更新，则确定发生TA异常。示例性地，网络侧的统一数据管理(Unified Data Management，UDM)或AMF记录有UE的RA。示例性地，在UE的上一次注册过程中，UE和/或网络设备的UDM和AMF记录有UE的RA。
网络侧确定发生这种TA异常，则会记录这种TA异常。示例性地，AMF等网络设备会记录这种TA异常状态，并形成TA异常状态的状态信息。
在一些实施例中，UE会发送非接入层(Non-Access Stratum，NAS)请求消息，接入网设备(例如，基站)接收到该NAS请求消息后，基站等接入网设备将UE的位置信息(包含UE当前所在的TA)包含在NAS请求消息中发送给核心网设备(例如，AMF)。核心网设备若发现UE所在TA不在网络侧记录的RA包含的TA内，则确定TA异常。UE在进行业务请求或者请求建立协议数据单元(Protocol Data Unit，PDU)会话时，核心网设备收到NAS请求消息，核心网设备接收到NAS请求消息之后进入到NAS处理流程，以进行NAS请求消息的响应。
该NAS请求消息包括但不限于以下至少之一：
协议数据单元(Protocol Data Unit，PDU)会话建立请求消息；
服务请求消息。
导致TA异常发生的原因有多种，以下提供一种可能的原因：
UE接入的小区(例如，卫星接入下的小区)，UE移动到了新的TA，而该新的TA不包含在UE注册的RA包含的TA内，则产生了TA异常。若UE自身发现已经进入了新的TA，则会主动触发注册更新流程，若UE未感知到自身进入到了新的TA可能就没有主动发起注册更新流程，从而直达网络侧，网络侧设备发现UE的这种TA异常。
如图4所示，在T1时间，UE处于TA1，通过卫星接入5G核心网络，卫星向UE广播多个TA(TA1和TA2)，UE完成接入注册，网络侧为UE产生RA(包括TA1及其他TA，但不包括TA2)。 在T2时间，UE移动进入TA2，由于在T1和T2，卫星向UE广播的TA相同，因此UE并不感知自己发生了TA更新，因此UE不会主动发起注册更新以更新RA。如果在T2时间，UE发起了业务请求，gNB会将UE当前所处位置TA2上报给网络侧，网络侧发现UE当前所处位置TA2并不包含在UE的RA内，从而导致UE的TA异常。当然以上仅是对UE的TA异常导致原因简单举例，具体实现时具有多种方法，不限于上述举例。
参考图3和图4所示，卫星可以连接到5G的核心网(Core Network，CN)，无线小区针对一个PLMN可能广播一个或多个TAC，且UE会根据这些广播的信息确定自身的TA。
在一种情况下，无线小区广播了一个TAC，则UE会将该TA作为自身当前所在TA。
如图3所示，假设在T1时刻，卫星和无线小区在位置1且大部分覆盖在TA1内，则广播可能的TAC可为TA1的TAC；若卫星和无线小区移动，例如，如图3所示的从左向右移动，则该无线小区可以能在某一个时刻同时覆盖两个TA即(TA1和TA2)，或者，逐步从覆盖TA1切换到不覆盖TA1且完全覆盖在TA2上。在T2时刻，卫星和无线小区移动到TA2内，会认为当前无线小区所在TA为TA2，可能会将TA2的TAC广播给UE。
在另一种情况下，无线小区一次性会广播多个TAC。参考图4所示，在T1时刻到TA2时刻，由于无线小区同时覆盖在TA1和TA2上，卫星和无线小区会同时将TA1和TA2的TAC广播给UE。到了T3时刻，卫星和无线小区移动到覆盖TA2和TA2右边的其他TA，则卫星和无线小区会向UE广播TA2和其他TA的TAC。
不管上述那种情形，AMF都是按照UE的RA包含的TAC来寻呼UE。如果AN或者RAN可能将从RA中确定出UE当前所在TA，并在该TA内寻呼UE。
UE会发起注册更新，当UE当前所处的TA不包含在其RA内时，在注册更新流程中，AMF等核心网的网络设备会更新UE的RA，更新后的TA包括UE当前所处的TA和UE可能会接入的TA，如此，方便后续能够成功寻呼到UE。
示例性地，如图4所示，如果T1时刻，UE位于TA1，通过卫星接入5G网络。卫星和无线小区向UE广播TA1和TA2，UE根据广播信息确定自己所处的TA，完成注册，作为注册过程的一部分，AMF为UE产生RA(包括TA1和其他TA，但不包括TA2)。T2时刻，UE发生移动，从TA1移动至TA2，由于T1和T2时刻，卫星和无线小区向UE持续广播TA1和TA2，因此UE可能无法感知到所处的TA变化，不会触发注册更新以更新RA。但T2时刻，如果UE发起服务请求过程，gNB会将UE当前所处的TA2(gNB通过测量获取)上报给AMF，AMF确定UE当前所处的TA2不包含在UE的RA内，此时AMF可以确定UE发生了前述的TA异常。
基站接收到UE发送的NAS请求消息后，基站将UE的位置信息(包含UE当前所在的TA)包含在NAS请求消息中示例性地，该NAS请求消息中包含UE当前所在TA可以作为NGAP中用户位置信息(User Location Information，ULI)的一部分。如果ULI指示的TA并不包含在UE的RA中，则会出现了UE不知晓的TA异常。
在TA异常存在时，会触发UE进行RA更新。示例性地，向UE发送触发指示。该触发指示可 用于指示UE执行注册更新流程，如此，UE将通过注册更新流程更新所述RA。通过RA更新包含UE当前所在TA就能够消除这种TA异常。
网络设备基于TA异常下发注册更新流程的触发指示。该指示信息用于指示UE发起注册更新流程的原因。
示例性地，图5所示为一个注册流程，可包括：
接入网(Access Network，AN)或者RAN接收UE的注册请求；所述注册请求包括：AN参数、注册类型、用户签约永久标识(Subscription Permanent Identifier，SUPI)或者第五代移动通信(5G)全球唯一临时用户标识(Globally Unique Temporary UE Identity，GUTI)、用户设备标识(Permanent Equipment Identifier，PEI)、请求地NSSAI、最后访问的且可用的TAI等。注册类型指示了如果UE是需要进行初始化注册、移动注册更新、周期性注册更新或者永久注册。最后访问的TAI可用于帮助AMF等网络设备确定UE的RA。
AN或者RAN接收到注册请求之后，为UE选择AMF；示例性地，AN或者RAN根据传输注册请求使用的RAT和请求的NASSAI等信息，为UE选择AMF。如果RAN不能为UE选择一个合适的AMF，向RAN注册消息发送RAN或者AN配置的AMF，即选择RAN或者AN配置的AMF作为UE的AMF。
将注册请求发送给选择的AMF；该注册请求是被RAN或者AN携带在N2消息中发送给选择的AMF的。该N2消息的N2参数可包括但不限于：注册请求、选择的公共陆地移动网络(Public Land Mobile Network，PLMN)的标识(Identity，ID)、位置信息、UE所在小区的小区ID等信息。
如果UE的服务AMF相对于上一次注册选择的AMF有发生变化，则新的AMF将从旧的AMF获取UE的SUPI和UE的上下文；
如果UE没有提供SUCI或者旧的AMF没有提供SUCI，新的AMF将发起ID请求流程来获取SUCI。
新的AMF会确定出对UE发起涉及认证服务器功能(Authentication Server Function，AUSF)的UE认证。例如，新的AMF将基于UE的SUPI或者SUCI选择一个AUSF。
如果相对于上一次注册流程，UE的AMF有切换，或者UE提供的SUPI不涉及到AMF中的有效上下文，AMF将基于SUPI选择并注册到一个统一数据管理(Unified Data Management，UDM)。如果AMF没有获取到UE的订阅数据，则将从UDM获取UE的订阅数据。
新的AMF与PCF之间交互关于移动管理(AM)策略的建立或修改的流程；
如果包含注册请求的PDU会话被激活，AMF将发送Nssmf_PDU Session_Update SM Context请求到与PDU会话关联的SMF，以激活PDU会话的用户面连接。
新的AMF发送一个注册接受消息给UE，以指示注册请求被接受了。该注册接受消息包含：RA、移动性限制、允许使用的NASSAI、周期性注册定时器指示等信息。如果AMF分配有新的RA，则将新的RA的信息发送给UE。如果没有为UE分配新的RA，则注册接受消息中将不会携带的RA的信息，且表示旧的RA依然有效。
剩余的注册流程的步骤在此就不再一一描述了。
在一些实施例中，所述S120可包括：
周期性确定所述TA异常是否存在，若存在则基于存在的TA异常触发UE进行RA更新。
在另一些实施例中，所述S120可包括：
在执行与UE的RA或者所在TA关联的业务流程或者控制流程之前，确定是否存在所述TA异常。
示例性地，所述方法还可包括：在寻呼所述UE时，首先确定所述TA异常是否存在，如此在S120可包括：在寻呼该UE时确定存在该UE的TA异常，则触发该UE进行RA更新。在UE完成RA更新之后，UE的TA异常去除，如此可根据UE所处的TA寻呼该UE，从而抑制因为UE的TA异常导致的寻呼失败现象。
如图6所示，本公开实施例提供一种TA异常处理方法，可包括：
S210：响应于确定存在TA异常，记录UE的TA异常；
S220：在寻呼对应UE时确定存在TA异常，触发所述UE的RA更新；
S230：在所述UE的RA更新完成之后，寻呼所述UE。
UE存在TA异常，该TA异常被记录在网络侧，例如，记录在AMF中，AMF在确定寻呼该UE之前，先查询待寻呼的UE是否存在TA异常，若存在TA异常需要先消除这种TA异常，在消除TA异常时可以通过触发UE的RA更新来实现。例如，网络侧触发UE的RA更新可包括：向UE发送触发指示，指示UE发起注册更新流程。UE接收到触发指示之后，会向网络侧发送注册更新请求，通过注册更新流程的执行，使UE的RA包含UE所处的TA，从而消除这种TA异常。
如图7所示，本公开实施例一种TA异常处理方法，由网络设备执行，可包括：
S310：接收NAS请求消息；其中，所述NAS请求消息包含了UE当前所处的TA等位置信息；
S320：根据所述NAS请求消息，确定所述UE当前所处的TA是否位于所述UE的RA外；
S330：响应于所述UE当前所处的TA位于所述RA外，确定发生所述TA异常。
该网络设备可为AMF等核心网的网络设备。
基站接收到UE发送的NAS请求消息后，基站将UE的位置信息(包含UE当前所在的TA等位置信息)包含在NAS请求消息中发送给核心网设备(例如，AMF)。核心网设备若发现UE所在TA不在网络侧记录的RA包含的TA内，则确定TA异常。例如，基站在UE的NAS请求消息包含的该UE的用户位置信息(User Location Imformation，ULI)中添加UE当前所在TA。
本公开实施例提供的方法，可以单独执行，也可以是前述步骤S110的一种具体实现。
总之，在本公开实施例中网络设备可以根据NAS请求消息确定出UE是否具有TA异常。
在本公开实施例中，所述方法还包括：
在确定出TA异常时，还会照常响应所述NAS请求消息。此处的照常响应所述NAS请求消息可为：当作所述TA异常不存在，继续执行NAS请求消息触发的NAS流程的后续步骤。
在一些实施例中，所述方法还包括：
响应于记录有所述TA异常时接收到所述UE发起的注册更新请求；
在完成对应于所述注册更新请求的RA更新后，去除所述TA异常的记录。
除了网络侧触发UE发起注册更新流程(即注册流程的一种)，UE可能也会主动发起注册更新流程。
示例性地，若UE由于移动进入到新的TA时发起注册更新流程，从而更新网络侧记录的UE的RA；
又示例性地，若UE想要更改在前一次注册流程中与网络侧协商的网络参数，同样可以根据注册更新流程来实现；
再示例性地，若UE配置有周期性注册更新，当前达到周期性注册更新的更新时刻，则UE同样主动发起注册更新流程，从而实现注册更新。
在本公开实施例中，在发现UE的TA异常时，记录有TA异常。若记录的TA异常未消除之前，接收到UE主动发起的注册更新请求或者基于网络侧触发发起的注册更新请求，将监控注册流程的执行，在完成注册更新请求对应的注册流程执行过程中实现了UE和/或网络侧记录的RA更新之后，就会去除这种TA异常的记录。若UE的TA异常记录被去除之后，则在S120中查询UE的TA异常时，就会发现UE不存在TA异常。
示例性地，所述注册更新请求包括：所述UE接收到TA异常触发发起的所述注册更新请求；或，
所述UE的位置移动触发的所述注册更新请求；或，所述UE发起的周期性注册更新请求。
在一些实施例中，所述网络设备包括：AMF。
如图8所示，本公开实施例提供一种TA异常处理方法，由UE执行，所述方法包括：
S410：接收网络侧基于所述UE的TA异常发送的触发指示；该触发指示，用于触发UE执行注册更新流程；S420：根据所述触发指示，进行RA更新。
在本公开实施例中，该网络侧包括但不限于核心网侧。
此处的TA异常包括：UE当前所处TA位于UE的RA外。且该TA异常是由网络侧确定的。
若网络侧发现UE的TA异常，则会主动触发UE进行RA更新。网络侧会下发触发指示，该触发指示可为：网络侧下发的触发UE发起注册更新请求的任意指示。示例性地，所述触发指示包括但不限于配置更新指令。
在一些实施例中，所述方法还包括：
发送NAS请求消息，其中，所述NAS请求消息在经过接入网设备时加入所述UE的位置信息之后，用于供所述核心网确定是否发生所述UE的TA异常。
例如，该NAS请求消息携带有ULI，该ULI包含了UE所在TA等位置信息。网络侧接收到该NAS请求消息之后发现NAS请求消息包含的TA不包含在UE的RA中，则认为发生UE的TA异常。若发生这种TA异常会记录这种TA异常。
网络侧在执行与UE的RA或者所在TA关联的业务流程或者控制流程之前，查询该UE的TA异常是否存在若存在，则UE会接收到网络侧发送的注册更新的触发指示。
UE可以根据这种触发指示发起注册更新请求，通过注册更新请求对应的注册更新流程进行UE和/或网络侧的RA的更新，从而消除这种TA异常。
在一些实施例中，所述触发指示是在寻呼所述UE之前接收的。触发指示在UE被寻呼之前接收，相当于可以通过RA更新消除TA异常，从而确保UE的寻呼成功率。
为了解决UE的TA异常，如果UE的TA异常被检测到，AMF在忽略检测到的TA异常的同时，记录这种TA异常。在这之后，如果发生寻呼UE的过程，AMF会触发UE发起注册更新来解决TA异常。在TA异常之后被移除之后，再寻呼UE。
如此，采用这种方式不仅可以解决UE的TA异常，同时对UE的寻呼无负面影响。
示例性地，当AMF接收到NAS请求消息(示例性地，该NAS请求消息包括但不限于：PDU建立请求消息或者服务请求消息)时，可以根据NAS请求消息确定是否发生TA异常。如果AMF检测到这种TA异常，会忽略这种TA异常，并将这种TA异常记录在AMF中，并继续响应该NAS请求消息，即照常执行NAS请求消息对应的NAS流程。
AMF记录TA异常。在这之后，如果由于UE的移动或者周期性注册更新等UE主动发起的注册更新发生，并消除了TA异常，则记录的TA异常将从AMF中移出，否则这种TA异常的记录会继续保存在AMF中。
如果需要寻呼UE，AMF接收到寻呼消息之后，确定所述UE是否存在TA异常。如果在AMF中记录有该UE的TA异常，则AMF会触发UE发起注册更新流程。在注册更新流程完成之后，AMF将基于更新后的RA发送寻呼消息。若AMF中没有记录UE的TA异常，则AMF会按照常规流程寻呼UE。
如图9所示，当UE接入到网络时将发起注册流程，该注册流程将在UE和核心网(Core Network，CN)之间完成；UE接入网络时发起的注册流程为UE和CN(例如5G CN)之间的初始注册流程。
如果初始注册成功，UE的RA将被存储在AMF中，该RA可包括一个或多个TA。
接收NAS请求消息(PDU会话建立请求消息)，该NAS请求消息携带有基站指示UE所在TA的信息；
AMF接收到该NAS请求消息之后，会检测是否有发生的TA异常。如果TA异常发生，AMF将忽略这种TA异常，且将存储所述UE的TA异常。
AMF和其他实体将继续PDU会话建立流程；
在PDU会话建立后，如果一个紧急服务需要开始，AMF将会向UE发送寻呼消息。在发送寻呼消息之前，AMF判断是否存在所述UE的TA异常；
若存在所述TA异常，AMF向UE发送触发注册更新流程的消息；
收到所述触发注册更新流程的消息，UE向5G CN发起注册更新流程。在注册更新流程完成之后，UE的RA包含UE所在的TA；
AMF使用更新后的RA寻呼UE，开启紧急服务。
如图10所示，当UE接入到网络时将发起注册流程，该注册流程将在UE和5G核心网络(Core  Network，CN)之间完成；UE接入到网络时发起的注册可以认为是初始注册。
如果初始注册成功，UE的RA将被存储在AMF中，该RA可包括一个或多个TA。
接收NAS请求消息(PDU会话建立请求消息)，该NAS请求消息携带有基站指示UE所在TA的信息；
AMF接收到该NAS请求消息之后，会检测是否有发生的TA异常。如果TA异常发生，AMF将忽略这种TA异常，且将存储所述UE的TA异常。
AMF和其他实体将继续PDU会话建立流程；
在这之后，发生周期性注册更新流程，AMF更新UE的RA,更新后的RA包含了UE当前所在的TA。更新成功后，AMF移除所述UE的TA异常。
在PDU会话建立后，如果一个紧急服务需要开始，AMF判断不存在该UE的TA异常，则基于记录的RA向UE发起寻呼，开始所述紧急服务。
在本公开实施例中，当接收到包含指示UE当前位置的TA的NAS请求消息时，检测UE的TA异常，如果发生TA异常，AMF将忽略这种TA异常，并记录所述TA异常，并将继续执行NAS请求消息的NAS流程。
在这之后，由于UE的移动或者周期性注册更新发起的注册更新发生，AMF中的所述UE的TA异常会被去除，否则将继续保存在AMF中。
如果寻呼UE发生，AMF接收到寻呼消息时，需要确定所述UE的TA异常是否存在。如果UE的TA异常存在，则AMF将基于所述TA异常触发UE发起注册更新流程。在注册更新流程完成之后，AMF基于UE的RA发送寻呼消息。如果AMF中未存在所述UE的TA异常，则AMF在不触发UE发起注册更新的情况下直接寻呼UE。
如图11所示，本公开实施例提供一种TA异常处理装置，所述装置包括：
记录模块110，被配置为响应于确定发生UE当前所处TA位于所述UE的RA外的TA异常，记录所述TA异常；
触发模块120，被配置为基于所述TA异常存在，触发所述UE的RA更新。
该TA异常处理装置可包含在网络设备中，该网络设备包括但不限于AMF。
在一些实施例中，记录模块110和触发模块120可包括程序模块；所述程序模块被处理器执行之后，可以在确定出UE位于UE的RA外的TA异常时，记录下该TA异常。
在一些实施例中，所述记录模块110和触发模块120可为软硬结合模块；所述软硬结合模块包括但不限于：各种可编程阵列；所述可编程阵列包括但不限于：现场可编程阵列和复杂可编程阵列。
在还有一些实施例中，所述记录模块110和触发模块120可为纯硬件模块；所述纯硬件模块包括但不限于：专用集成电路。
在一些实施例中，所述装置还包括：
第一确定模块，被配置为在寻呼所述UE时确定所述TA异常是否存在。
在一些实施例中，所述装置还包括：
寻呼模块，被配置为在所述UE的RA更新完成之后，寻呼所述UE。
在一些实施例中，所述装置还包括：
接收模块，被配置为接收非接入层NAS请求消息；其中，所述NAS请求消息具有指示所述UE当前所处的TA的信息；
第二确定模块，被配置为根据所述NAS请求消息，确定所述UE当前所处的TA是否位于所述UE的RA外；
第三确定模块，被配置为响应于所述UE当前所处的TA位于所述RA外，确定发生所述TA异常。
在一些实施例中，所述装置还包括：
去除模块，被配置为响应于记录有所述TA异常时接收到所述UE发起的注册更新请求，在完成对应于所述注册更新请求的RA更新后，去除所述TA异常的记录。
在一些实施例中，所述注册更新请求包括：
所述UE接收到TA异常触发发起的所述注册更新请求；
或，
所述UE的位置移动触发的所述注册更新请求；
或，
所述UE发起的周期性注册更新请求。
在一些实施例中，所述网络设备包括：接入管理功能AMF。
如图12所示，本公开实施例提供一种TA异常处理装置，其中，由UE执行，所述装置包括：
接收模块210，被配置为接收网络侧基于所述UE的TA异常发送的触发指示；
更新模块220，被配置为根据所述触发指示，进行RA更新。
在一些实施例中，此处的TA异常包括：UE当前所处TA位于UE的RA外。且该TA异常是由网络侧确定的。
该UE可以为各种类型的UE，例如，包括但不限于：手机、平板电脑、可穿戴式设备、车载设备或者可地面行走的机器人或者低空飞行的飞行器等。
在一些实施例中，所述接收模块210和所述更新模块220可为程序模块；所述程序模块被处理器执行之后，能够接收网络侧下发的触发指示，并基于触发指示进行RA更新。
在还有一些实施例中，所述接收模块210和更新模块220可为软硬结合模块；所述软硬结合模块包括但不限于各种可编程阵列；所述可编程阵列可包括现场可编程阵列和/或复杂可编程阵列。
在一些实施例中，所述接收模块210和所述更新模块220可为纯硬件模块；所述纯硬件模块包括但不限于专用集成电路。
在一些实施例中，所述装置还包括：
消息模块，被配置为发送NAS请求消息，其中，所述NAS请求消息在经过接入网设备时加入 所述UE的位置信息之后，用于供所述核心网确定是否发生所述UE的TA异常。
在一些实施例中，所述触发指示为在所述UE的被寻呼之前接收的。
在一个实施例中，所述触发指示可包含TA异常的指示信息。该指示信息，用于指示触发UE发起注册更新流程的原因。
本公开实施例提供一种通信设备，包括：
用于存储处理器可执行指令的存储器；
处理器，分别存储器连接；
其中，处理器被配置为执行前述任意技术方案提供TA异常处理方法。
处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存储介质，在通信设备掉电之后能够继续记忆存储其上的信息。
这里，所述通信设备包括：UE和/或核心网设备。
所述处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序，例如，如图2、图5至10所示的方法的至少其中之一。
图13是根据一示例性实施例示出的一种UE800的框图。例如，UE 800可以是移动电话，计算机，数字广播用户设备，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图13，UE800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制UE800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在UE800的操作。这些数据的示例包括用于在UE800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为UE800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为UE800生成、管理和分配电力相关联的组件。
多媒体组件808包括在所述UE800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸 面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当UE800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当UE800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为UE800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如所述组件为UE800的显示器和小键盘，传感器组件814还可以检测UE800或UE800一个组件的位置改变，用户与UE800接触的存在或不存在，UE800方位或加速/减速和UE800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于UE800和其他设备之间有线或无线方式的通信。UE800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，UE800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由UE800的处理器820执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
如图14所示，本公开一实施例示出一种接入设备的结构。例如，网络设备900可以被提供为一网络侧设备。该网络设备包括但不限于核心网设备。
参照图14，网络设备900包括处理组件922，其进一步包括一个或多个处理器，以及由存储器932所代表的存储器资源，用于存储可由处理组件922的执行的指令，例如应用程序。存储器932 中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件922被配置为执行指令，以执行上述方法前述应用在所述网络设备的任意方法，例如，如图2、图5至图10所示方法。
网络设备900还可以包括一个电源组件926被配置为执行网络设备900的电源管理，一个有线或无线网络接口950被配置为将网络设备900连接到网络，和一个输入输出(I/O)接口958。网络设备900可以操作基于存储在存储器932的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (20)

  1. 一种跟踪区TA异常处理方法，其中，由网络设备执行，所述方法包括：
    响应于确定发生UE当前所处TA位于所述UE的RA外的TA异常，记录所述TA异常；
    基于所述TA异常存在，触发所述UE的RA更新。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    在寻呼所述UE时确定所述TA异常是否存在。
  3. 根据权利要求1或2所述的方法，其中，所述方法还包括：
    在所述UE的RA更新完成之后，寻呼所述UE。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    接收非接入层NAS请求消息；其中，所述NAS请求消息包含所述UE当前所处的TA的信息；
    根据所述NAS请求消息，确定所述UE当前所处的TA是否位于所述UE的RA外；
    响应于所述UE当前所处的TA位于所述RA外，确定发生所述TA异常。
  5. 根据权利要求1至4任一项所述的方法，其中，所述方法还包括：
    响应于记录有所述TA异常时接收到所述UE发起的注册更新请求；
    在完成对应于所述注册更新请求的RA更新后，去除所述TA异常的记录。
  6. 根据权要求5所述的方法，其中，所述注册更新请求包括：
    所述UE接收到TA异常触发发起的所述注册更新请求；
    或，
    所述UE的位置移动触发的所述注册更新请求；
    或，
    所述UE发起的周期性注册更新请求。
  7. 根据权利要求1至6任一项所述的方法，其中，所述网络设备包括：接入管理功能AMF。
  8. 一种TA异常处理方法，其中，由用户设备UE执行，所述方法包括：
    接收网络侧基于所述UE的TA异常发送的触发指示；其中，所述TA异常包括：所述UE当前所处的TA处于所述UE的RA外；
    根据所述触发指示，进行RA更新。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    发送NAS请求消息，其中，所述NAS请求消息在经过接入网设备时加入所述UE的位置信息之后，用于供所述核心网确定是否发生所述UE的TA异常。
  10. 一种TA异常处理装置，其中，所述装置包括
    记录模块，被配置为响应于确定发生UE当前所处TA位于所述UE的RA外的TA异常，记录所述TA异常；
    触发模块，被配置为基于所述TA异常存在，触发所述UE的RA更新。
  11. 根据权利要求10所述的装置，其中，所述装置还包括：
    第一确定模块，被配置为在寻呼所述UE时确定所述TA异常是否存在。
  12. 根据权利要求10或11所述的装置，其中，所述装置还包括：
    寻呼模块，被配置为在所述UE的RA更新完成之后，寻呼所述UE。
  13. 根据权利要求10所述的装置，其中，所述装置还包括：
    接收模块，被配置为接收非接入层NAS请求消息；其中，所述NAS请求消息包含所述UE当前所处的TA的信息；
    第二确定模块，被配置为根据所述NAS请求消息，确定所述UE当前所处的TA是否位于所述UE的RA外；
    第三确定模块，被配置为响应于所述UE当前所处的TA位于所述RA外，确定发生所述TA异常。
  14. 根据权利要求10至13任一项所述的装置，其中，所述装置还包括：
    去除模块，被配置为响应于记录有所述TA异常时接收到所述UE发起的注册更新请求，在完成对应于所述注册更新请求的RA更新后，去除所述TA异常的记录。
  15. 根据权要求14所述的装置，其中，所述注册更新请求包括：
    所述UE接收到TA异常触发发起的所述注册更新请求；
    或，
    所述UE的位置移动触发的所述注册更新请求；
    或，
    所述UE发起的周期性注册更新请求。
  16. 根据权利要求10至15任一项所述的装置，其中，所述网络设备包括：接入管理功能AMF。
  17. 一种TA异常处理装置，其中，由用户设备UE执行，所述装置包括：
    接收模块，被配置为接收网络侧基于所述UE的TA异常发送的触发指示；其中，所述TA异常包括：所述UE当前所处的TA处于所述UE的RA外；
    更新模块，被配置为根据所述触发指示，进行RA更新。
  18. 根据权利要求17所述的装置，其中，所述装置还包括：
    消息模块，被配置为发送NAS请求消息，其中，所述NAS请求消息在经过接入网设备时加入所述UE的位置信息之后，用于供核心网确定是否发生所述UE的TA异常。
  19. 一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如权利要求1至7或8至9任一项提供的方法。
  20. 一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现如权利要求1至7或8至9任一项提供的方法。
PCT/CN2021/107292 2021-07-20 2021-07-20 跟踪区异常处理方法及装置、通信设备及存储介质 WO2023000161A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/107292 WO2023000161A1 (zh) 2021-07-20 2021-07-20 跟踪区异常处理方法及装置、通信设备及存储介质
CN202180002212.1A CN115836537A (zh) 2021-07-20 2021-07-20 跟踪区异常处理方法及装置、通信设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/107292 WO2023000161A1 (zh) 2021-07-20 2021-07-20 跟踪区异常处理方法及装置、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023000161A1 true WO2023000161A1 (zh) 2023-01-26

Family

ID=84979692

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/107292 WO2023000161A1 (zh) 2021-07-20 2021-07-20 跟踪区异常处理方法及装置、通信设备及存储介质

Country Status (2)

Country Link
CN (1) CN115836537A (zh)
WO (1) WO2023000161A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170816A (zh) * 2006-10-24 2008-04-30 华为技术有限公司 注册区动态更新同步的方法及系统
EP3402234A1 (en) * 2017-01-16 2018-11-14 LG Electronics Inc. -1- Method for updating ue configuration in wireless communication system and apparatus for same

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170816A (zh) * 2006-10-24 2008-04-30 华为技术有限公司 注册区动态更新同步的方法及系统
EP3402234A1 (en) * 2017-01-16 2018-11-14 LG Electronics Inc. -1- Method for updating ue configuration in wireless communication system and apparatus for same

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION, TELIASONERA: "Enhanced procedure for non-EPS services recovery during periodic TAU", 3GPP DRAFT; C1-140166-P-TO-C-ENHANCED-24301-C30-V1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Guangzhou; 20140120 - 20140124, 19 January 2014 (2014-01-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050730852 *

Also Published As

Publication number Publication date
CN115836537A (zh) 2023-03-21

Similar Documents

Publication Publication Date Title
WO2021223239A1 (zh) 发送寻呼消息的方法、装置、通信设备及存储介质
WO2023029051A1 (zh) 寻呼监听的方法、装置、通信设备及存储介质
WO2020248140A1 (zh) 跟踪区更新方法及装置、通信设备及存储介质
WO2021159256A1 (zh) 一种寻呼处理方法、装置、通信设备及存储介质
WO2022141162A1 (zh) 一种通信方法、装置、通信设备和存储介质
WO2024168862A1 (zh) 接入控制方法、装置、通信设备及存储介质
WO2023065091A1 (zh) 寻呼过滤规则确定方法及装置、通信设备及存储介质
WO2023000161A1 (zh) 跟踪区异常处理方法及装置、通信设备及存储介质
WO2022141639A1 (zh) 小区重选的方法、装置、通信设备及存储介质
WO2023070326A1 (zh) Ta信息处理方法及装置、通信设备及存储介质
WO2023000154A1 (zh) 跟踪区异常处理方法及装置、通信设备及存储介质
WO2023240643A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2024060028A1 (zh) 信息处理方法以及装置、通信设备及存储介质
WO2023240641A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2023245665A1 (zh) 接入处理方法、装置、通信设备及存储介质
WO2023216206A1 (zh) 无线传输的方法、装置、通信设备及存储介质
WO2023164837A1 (zh) 定时器控制方法及装置、通信设备及存储介质
WO2024207347A1 (zh) 信息传输方法、装置及存储介质
WO2024031480A1 (zh) 网络接入方法、装置及存储介质
WO2023133894A1 (zh) Ue通信控制方法及装置、通信设备及存储介质
WO2023077526A1 (zh) 接入模式切换方法及装置、通信设备及存储介质
WO2024000124A1 (zh) 寻呼协商方法、装置、通信设备及存储介质
WO2023082104A1 (zh) 一种触发ue测量的方法、装置、通信设备及存储介质
WO2024138474A1 (zh) 寻呼方法、装置、通信设备及存储介质
WO2023178573A1 (zh) 信息处理方法及装置、通信设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21950427

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21950427

Country of ref document: EP

Kind code of ref document: A1