Patent Application
20240381285
The disclosure relates to but is not limited to, the technical field of radio communication, abstract communication device, and a storage medium.
When being initially connected to a network, user equipment (UE) sends a registration request to the network, and a network side makes a response to the registration request. In a registration process, the network side records a registration area (RA) of the UE, which typically encompasses one or more tracking areas (TAs). The network side records the RA of the UE in a form of a TA list (TAL) in some cases.
A method and apparatus for processing a tracking area (TA) anomaly, a communication device, and a storage medium are provided in examples of the disclosure.
In a first aspect, a method for processing a TA anomaly is provided in an example of the disclosure. The method is executed by a network device and includes:
In a second aspect, a method for processing a TA anomaly is provided in an example of the disclosure. The method is executed by a user equipment (UE) and includes:
In a third aspect, apparatus for processing a TA anomaly is provided in an example of the disclosure. The apparatus includes:
In a fourth aspect, apparatus for processing a TA anomaly is provided in an example of the disclosure. The apparatus includes:
In a fifth aspect, a communication device is provided in an example of the disclosure. The communication device includes a processor, a transceiver, a memory, and an executable program stored in the memory and runnable by the processor, where the processor executes the method for processing a TA anomaly in the first foregoing aspect when running the executable program.
In a sixth aspect, a computer storage medium is provided in an example of the disclosure. The computer storage medium stores an executable instruction, where the executable instruction implements the method for processing a TA anomaly in the first foregoing aspect when executed by a processor.
It should be understood that the above general description and the following detailed description are merely illustrative and explanatory and cannot limit the examples of the disclosure.
The accompanying drawings are incorporated in the description as a constituent part of the description here, illustrate examples conforming to the disclosure, and serve to explain the principles of the examples of the disclosure along with the description.
Examples will be described in detail here and are illustratively shown in the accompanying drawings. When the following description relates to the accompanying drawings, the same numbers in different accompanying drawings denote the same or similar elements unless otherwise indicated. The embodiments described in the following examples do not denote all embodiments consistent with the examples of the disclosure. On the contrary, they are merely instances of apparatuses and methods consistent with some aspects in the examples of the disclosure, as recited in the appended claims.
The terms used in the examples of the disclosure are merely to describe the specific examples, instead of limiting the examples of the disclosure. The singular forms such as “a,” “an,” and “this” used in the examples of the disclosure and the appended claims are also intended to include the plural forms, unless otherwise clearly stated in the context. It should also be understood that the term “and/or” used here means and encompasses one or any or all possible combinations of a plurality of associated items listed.
It should be understood that although the terms first, second, third, etc. may be employed in the examples of the disclosure to describe various information, these pieces of information should not be limited to this. These terms are merely used to distinguish between the same type of information. For example, first information can also be referred to as second information, and similarly, second information can also be referred to as first information, without departing from the scope of the examples of the disclosure. The word “if,” as used here, can be interpreted as “at the time of,” “when,” or “in response to determining,” depending on the context.
As a radio cell or the UE moves, the UE may enter a new TA. However, the new TA is not encompassed in the TAL corresponding to the RA, and the UE does not sense that the UE has entered the new TA. Consequently, a registration update process for updating the TA will not be initiated, leading to a TA anomaly.
With reference to
The user equipment 11 may be a device providing voice and/or data connectivity for a user. The UE 11 may communicate with one or more core networks via a radio access network (RAN). The UE 11 may be Internet of Things user equipment, such as a sensor device, a mobile phone (or referred to as a “cellular” phone), and a computer with Internet of Things user equipment, for example, stationary, portable, pocket, handheld, intra-computer, or vehicle-mounted apparatuses. For example, the UE 11 may be a station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, remote terminal, an access terminal, a user terminal, a user agent, a user device, or user equipment (UE). Alternatively, the UE 11 may also be an unmanned aerial vehicle. Alternatively, the UE 11 may also be a vehicle-mounted device, for example, an electronic control unit having a radio communication function, or a radio communication device externally connected to the electronic control unit. Alternatively, the UE 11 may also be a roadside device, for example, a street lamp, a signal lamp, etc. having a radio communication function.
The access device 12 may be a network side device in the radio communication system. The radio communication system may be a 4th generation mobile communication (4G) system, which is also called a long term evolution (LTE) system. Alternatively, the radio communication system may also be a 5th generation mobile communication (5G) system, which is also called a new radio (NR) system or a 5G NR system. Alternatively, the radio communication system may also be a next generation system following the 5G system. An access network in the 5G system may be called a new generation-radio access network (NG-RAN), or a machine-type communication (MTC) system.
The access device 12 may be an evolved access device employed in the 4G system, such as an eNB (evolved node B). Alternatively, the access device 12 may also be an access device employing a central-distributed architecture in the 5G system, such as a gNB (generation node B). When employing the central-distributed architecture, the access device 12 typically 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 protocol stack of a physical (PHY) layer. Particular embodiments of the access device 12 are not limited in the examples of the disclosure.
A radio connection may be established between the access device 12 and the UE 11 through a wireless radio. In different embodiments, the wireless radio is a wireless radio based on a standard of the 4th generation mobile communication (4G) or a standard of the 5th generation mobile communication (5G), and is a new radio, for example. Alternatively, the wireless radio may also be a wireless radio based on a standard of a next generation mobile communication following 5G.
In some examples, an end to end (E2E) connection may also be constructed between the UE 11. For example, scenarios such as vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, and vehicle to pedestrian (V2P) communication in vehicle to everything (V2X) communication are provided.
In some examples, the radio communication system above may further encompass a network management device 13.
Several access devices 12 are individually connected to the network management device 13. The network management device 13 may be a core network device in the radio communication system. For example, the network management device 13 may be a mobility management entity (MME) in an evolved packet core (EPC). Alternatively, the network management device may also be another core network device, 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). An implementation form of the network management device 13 is not limited in the examples of the disclosure.
As shown in
The network device here includes, but is not limited to, a core network device. The core network device includes, but is not limited to, an access management function (AMF).
The UE may have the RA recorded on a network side at previous registration. The RA includes a tracking area code (TAC) of one or more TAs. If the UE changes a location and enters a new TA, the TA where the UE is currently positioned is located outside the TAs in the RA, but the UE does not initiate a registration update procedure realizing the RA update. Thus, it is determined that the TA anomaly occurs. Illustratively, unified data management (UDM) or the AMF on the network side possesses a record of the RA of the UE. Illustratively, in a previous registration process of the UE, the UE and/or the UDM and the AMF of the network device possess a record of the RA of the UE.
After determining that such a TA anomaly occurs, the network side records the TA anomaly. Illustratively, the network device such as the AMF records such a TA anomaly state and forms state information of a TA anomaly state.
In some examples, the UE sends a non-access stratum (NAS) request message. After receiving the NAS request message, an access network device (for example, a base station) enables location information (encompassing the TA where the UE is currently positioned) of the UE to be encompassed in the NAS request message and sends a resulting NAS request message to the core network device (for example, the AMF). If finding that the TA where the UE is positioned is not located within TAs encompassed in the RA recorded by the network side, the core network device determines the TA anomaly. When the UE performs a service request or requests to construct a protocol data unit (PDU) session, the core network device receives the NAS request message and enters a NAS processing flow to respond to the NAS request message after receiving the NAS request message.
The NAS request message includes, but is not limited to, at least one of the following:
A variety of causes may lead to TA abnormalities, and one possible cause is provided below:
If the UE has accessed a cell (for example, a cell accessed through a satellite) and moves to a new TA, but the new TA is not encompassed within the TAs encompassed in the RA registered by the UE, the TA anomaly is generated. If finding that it has entered the new TA, the UE actively triggers the registration update procedure. If the UE does not sensed that it has entered the new
TA, the UE may not actively initiate the registration update procedure, so as to directly reach the network side. The network side device finds such a TA anomaly of the UE.
As shown in
With reference to
In one case, the radio cell broadcasts one TAC, and the UE takes the TA as the TA where the UE is currently positioned.
As shown in
In another case, the radio cell may broadcast a plurality of TACs at a time. With reference to
In either of the above cases, the AMF pages the UE according to TAC encompassed in the RA of the UE. If an access network (AN) or the radio access network (RAN) may determine the TA where the UE is currently positioned from the RA, the UE is paged within this TA.
The UE initiates a registration update. When the TA where the UE is currently positioned is not encompassed in the RA of the UE, the network device of the core network, such as the AMF updates the RA of the UE in the registration update procedure. An updated TA includes the TA where the UE is currently positioned and the TA that the UE may access. In this way, the UE can be successfully paged in a later stage.
Illustratively, as shown in
After receiving the NAS request message sent by the UE, the base station enables the location information (encompassing the TA where the UE is currently positioned) of the UE to be encompassed in the NAS request message. Illustratively, the TA where the UE is currently positioned encompassed in the NAS request message may be used as part of user location information (ULI) in a next generation application protocol (NGAP). If the TA indicated by the ULI is not encompassed in the RA of the UE, a TA anomaly unknown to the UE may occur.
When the TA anomaly exists, the UE is triggered to perform the RA update. Illustratively, a triggering indication is sent to the UE. The triggering indication may be configured to instruct the UE to perform the registration update procedure. In this way, the UE updates the RA through the registration update procedure. Such a TA anomaly can be removed through the RA update that encompasses the TA where the UE is currently positioned.
The network device issues the triggering indication of the registration update procedure based on the TA anomaly. The triggering indication is configured to indicate a cause why the UE initiates the registration update procedure.
Illustratively,
The access network (AN) or the RAN receives a registration request of the UE, where the registration request includes: an AN parameter, a registration type, a subscription permanent identifier (SUPI), or a globally unique temporary UE identity (GUTI) of the fifth mobile communication (5G), a permanent equipment identifier (PEI), a requested single network slice selection assistance information (NSSAI), a last accessed and available tracking area identity (TAI), etc. The registration type indicates initialization registration, a mobile registration update, a periodic registration update, or permanent registration that the UE may be required to perform. The last accessed TA1 may be configured to assist in determining the RA of the UE by the network device such as the AMF.
After receiving the registration request, the AN or the RAN selects the AMF for the UE. Illustratively, the AN or the RAN selects the AMF for the UE according to information such as a radio access technology (RAT) used for transferring the registration request and the requested NSSAI. If the RAN fails to select one suitable AMF for the UE, the AMF configured in the RAN or the AN is sent to an RAN registration message, i.e., the AMF configured in the RAN or the AN is selected as the AMF of the UE.
The registration request is sent to the AMF selected. The RAN or the AN enables the registration request to be carried in an N2 message, so as to send the registration request to the AMF selected. An N2 parameter of the N2 message may include, but is not limited to, a registration request, an identity (ID) of a public land mobile network (PLMN) selected, location information, and a cell ID of a cell where the UE is positioned, etc.
If a serving AMF of the UE changes relative to the AMF selected for previous registration, a new AMF acquires the SUPI of the UE and a context of the UE from an old AMF.
If the UE does not provide a subscription concealed identifier (SUCI) or the old AMF does not provide an SUCI, the new AMF initiates an ID request flow to obtain the SUCI.
The new AMF determines that UE authentication involving an authentication server function (AUSF) is initiated for the UE. For example, the new AMF selects one AUSF based on the SUPI or the SUCI of the UE.
If the AMF of the UE is switched relative to the previous registration flow, or the SUPI provided by the UE does not relate to an effective context in the AMF, the AMF selects and registers with a unified data management (UDM) based on the SUPI. If the AMF does not acquire subscription data of the UE, the subscription data of the UE is acquired from the UDM.
The new AMF interacts with a point coordination function (PCF) for a flow for constructing or modifying an access and mobility management (AM) policy.
If a PDU session encompassing the registration request is activated, the AMF sends an Nssmf_PDU Session_Update SM Context request to a session management function (SMF) associated with the PDU session, so as to activate user plane connectivity for the PDU session.
The new AMF sends a registration acception message to the UE, indicating that the registration request is accepted. The registration acception message includes the RA, mobility restriction, NASSAI allowed to be used, periodic registration timer indication, etc. If a new RA is allocated by the AMF, information of the new RA is sent to the UE. If no new RA is allocated to the UE, no information of the RA is carried in the registration acception message, indicating that an old RA is still effective.
Remaining steps of the registration flow will not be described in sequence here.
In some examples, S120 may include:
In some other examples, S120 may include:
Illustratively, the method may further include: firstly, whether the TA anomaly exists is determined when paging the UE. In this way, S120 may include: the UE is triggered to perform the RA update in response to determining that the TA anomaly of the UE exists when paging the UE. After the UE completes the RA update, the TA anomaly of the UE is removed. In this way, the UE may be paged according to the TA where the UE is positioned, so that a paging failure phenomenon caused by the TA anomaly of the UE is suppressed.
As shown in
If the TA anomaly exists in the UE, the TA anomaly is recorded at the network side, for example, in the AMF. Before determining to page the UE, the AMF firstly queries whether the TA anomaly exists in the UE to be paged. If yes, the TA anomaly is required to be removed firstly. The TA anomaly may be removed by triggering the RA update of the UE. For example, the RA update of the UE triggered by the network side may include: a triggering indication is sent to the UE, so as to instruct the UE to initiate a registration update procedure. After receiving the triggering indication, the UE sends a registration update request to the network side. Through the execution of the registration update procedure, the RA of the UE encompasses the TA where the UE is positioned, so as to remove such a TA anomaly.
As shown in
The network device may be a network device of a core network such as an AMF.
After receiving the NAS request message sent by the UE, a base station enables location information (encompassing the TA where the UE is currently positioned) of the UE to be encompassed in the NAS request message and sends a resulting NAS request message to a core network device (for example, the AMF). If finding that the TA where the UE is positioned is not located within TAs encompassed in the RA recorded by the network side, the core network device determines the TA anomaly. For example, the base station adds the TA where the UE is currently positioned to the user location information (ULI) of the UE encompassed in the NAS request message of the UE.
The method according to the example of the disclosure may be executed alone or may be specific implementation of the foregoing S110.
In conclusion, in the example of the disclosure, the network device may determine whether the TA anomaly exists in the UE according to the NAS request message.
In the example of the disclosure, the method further includes:
In some examples, the method further includes:
Except for the condition that the network side triggers the UE to initiate the registration update procedure (i.e., one type of registration flow), the UE may also actively initiate the registration update procedure.
Illustratively, if the UE initiates the registration update procedure after moving into a new TA, the RA of the UE recorded by the network side is updated.
Further illustratively, the UE may also change network parameters negotiated with the network side in a previous registration flow according to the registration update procedure.
Further illustratively, if the UE is configured with a periodic registration update, when an update time of the periodic registration update is reached currently, the UE also actively initiates the registration update procedure, so as to realize the registration update.
In the example of the disclosure, when being found, the TA anomaly of the UE is recorded. If the registration update request initiated by the UE actively or the registration update request initiated through triggering by the network side is received before the TA anomaly recorded is removed, execution of the registration flow is monitored. The record of such a TA anomaly is removed after the RA recorded by the UE and/or the network side is updated in a registration flow execution process corresponding to the registration update request. If the record of the TA anomaly of the UE is removed, when the TA anomaly of the UE is queried in S120, it is found that no TA anomaly exists in the UE.
Illustratively, the registration update request includes: the registration update request initiated when the UE receives the triggering of the TA anomaly; alternatively, a registration update request triggered by location movement of the UE; and alternatively, a periodic registration update request initiated by the UE.
In some examples, the network device includes: the AMF.
As shown in
In the example of the disclosure, the network side includes, but is not limited to, a core network side.
The TA anomaly here includes: a condition that a TA where the UE is currently positioned is located outside an RA of the UE. The TA anomaly is determined by the network side.
If finding that the TA anomaly of the UE, the network side actively triggers the UE to perform the RA update. The network side issues the triggering indication. The triggering indication may be any indication issued by the network side for triggering the UE to initiate a registration update request. Illustratively, the triggering indication includes, but is not limited to, a configuration update instruction.
In some examples, the method further includes:
a NAS request message is sent, where the NAS request message, after being added with location information of the UE at the time of passing through an access network device, is configured for a core network to determine whether the TA anomaly of the UE occurs.
For example, ULI is carried in the NAS request message. The ULI encompasses location information of the TA where the UE is positioned, etc. After receiving the NAS request message, if finding that the TA encompassed in the NAS request message is not encompassed in the RA of the UE, the network side deems that the TA anomaly of the UE occurs. Such a TA anomaly is recorded if occurring.
Before executing a service flow or control flow associated with the RA of the UE or the TA where the UE is positioned, the network side queries whether the TA anomaly of the UE exists. If yes, the UE receives the triggering indication sent by the network side for a registration update.
The UE may initiate a registration update request according to such a triggering indication and update the RA of the UE and/or the network side through a registration update procedure corresponding to the registration update request, so as to remove such a TA anomaly.
In some examples, the triggering indication is received before the UE is paged. The triggering indication is received before the UE is paged, which is equivalent to removal of the TA anomaly through the RA update. Thus, a UE paging success rate is ensured.
In order to solve the TA anomaly of the UE, if the TA anomaly of the UE is detected, the AMF records such a TA anomaly while neglecting the TA anomaly detected. After that, if a UE paging flow occurs, the AMF triggers the UE to initiate the registration update, so as to resolve the TA anomaly. After the TA anomaly is removed, the UE is repaged.
In this way, through such a method, no negative impact is generated on UE paging while the TA anomaly of the UE can be solved.
Illustratively, when the AMF receives the NAS request message (illustratively, the NAS request message includes, but is not limited to, a PDU establishment request message or a service request message), whether the TA anomaly occurs may be determined according to the NAS request message. If detecting such a TA anomaly, the AMF neglects the TA anomaly, records the TA anomaly in the AMF, and continues responding to the NAS request message, i.e., executes a NAS flow corresponding to the NAS request message as usual.
The AMF records the TA anomaly. After that, if the registration update initiated by the UE actively occurs owing to movement of the UE or the periodic registration update, and the TA anomaly is removed, the TA anomaly recorded is removed from the AMF, otherwise, a record of such a TA anomaly continues being stored in the AMF.
If the UE is required to be paged, the AMF determines whether the TA anomaly exists in the UE after receiving a paging message. If the TA anomaly of the UE is recorded in the AMF, the AMF triggers the UE to initiate the registration update procedure. After the registration update procedure is completed, the AMF sends the paging messages based on an updated RA. If no TA anomaly of the UE is recorded in the AMF, the AMF pages the UE according to a conventional flow.
As shown in
If the initial registration succeeds, an RA of the UE is stored in an AMF. The RA may include one or more TAs.
A NAS request message (a PDU session establishment request message) is received. The NAS request message carries information through which a base station indicates a TA where the UE is positioned.
After receiving the NAS request message, the AMF detects whether a TA anomaly occurs. If the TA anomaly occurs, the AMF neglects such a TA anomaly and stores the TA anomaly of the UE.
The AMF and other entities continue to perform a PDU session establishment flow.
After a PDU session is constructed, the AMF sends a paging message to the UE if an emergency service is required to start. Before sending the paging message, the AMF determines whether the TA anomaly of the UE exists.
If the TA anomaly exists, the AMF sends a message triggering a registration update procedure to the UE.
After receiving the message triggering the registration update procedure, the UE initiates the registration update procedure to the 5G CN. After the registration update procedure is completed, the RA of the UE encompasses the TA where the UE is positioned.
The AMF pages the UE through the updated RA, so as to start the emergency service.
As shown in
If the initial registration succeeds, an RA of the UE is stored in an AMF. The RA may include one or more TAs.
A NAS request message (a PDU session establishment request message) is received. The NAS request message carries information through which a base station indicates a TA where the UE is positioned.
After receiving the NAS request message, the AMF detects whether a TA anomaly occurs. If the TA anomaly occurs, the AMF neglects such a TA anomaly and stores the TA anomaly of the UE.
The AMF and other entities continue to perform a PDU session establishment flow.
After that, a periodic registration update procedure occurs. The AMF updates the RA of the UE. An updated RA encompasses the TA where the UE is currently positioned. After an update succeeds, the AMF removes the TA anomaly of the UE.
After a PDU session is constructed, if an emergency service is required to start, and the AMF determines that no TA anomaly of the UE exists, the AMF initiates paging to the UE based on the RA recorded, so as to start the emergency service.
In the example of the disclosure, when the NAS request message encompassing the TA indicating a current location of the UE is received, the TA anomaly of the UE is detected. If the TA anomaly occurs, the AMF neglects such a TA anomaly, records the TA anomaly, and continues performing a NAS flow of the NAS request message.
After this, if a registration update is initiated owing to the movement of the UE or a periodic registration update occurs, the TA anomaly of the UE is removed from the AMF. Otherwise, the TA anomaly continues to be stored in the AMF.
If the UE is paged, the AMF is required to determine whether the TA anomaly of the UE exists when receiving a paging message. If the TA anomaly of the UE exists, the AMF triggers the UE to initiate a registration update procedure based on the TA anomaly. After the registration update procedure is completed, the AMF sends the paging message based on the RA of the UE. If no TA anomaly of the UE exists in the AMF, the AMF pages the UE directly without triggering the UE to initiate a registration update.
As shown in
a recording module 110 configured to record, in response to determining that the TA anomaly that a TA where UE is currently positioned is located outside an RA of the UE occurs, the TA anomaly; and
The apparatus for processing a TA anomaly may be encompassed in a network device. The network device includes, but is not limited to, an AMF.
In some examples, the recording module 110 and the triggering module 120 may be program modules. After being executed by a processor, the program modules may record, in response to determining the TA anomaly that the UE is located outside the RA of the UE, the TA anomaly.
In some examples, the recording module 110 and the triggering module 120 may be hardware-software combined modules. The hardware-software combined modules include, but are not limited to, various programmable arrays. The programmable arrays include, but are not limited to, field programmable arrays and complex programmable arrays.
In some other examples, the recording module 110 and the triggering module 120 may be pure hardware modules. The pure hardware modules include, but are not limited to, application-specific integrated circuits.
In some examples, the apparatus further includes:
a first determination module configured to determine whether the TA anomaly exists when the UE is paged.
In some examples, the apparatus further includes:
In some examples, the apparatus further includes:
In some examples, the apparatus further includes:
In some examples, the registration update request includes:
In some examples, the network device includes: an access management function (AMF).
As shown in
In some examples, the TA anomaly here includes: a condition that a TA where the UE is currently positioned is located outside an RA of the UE. The TA anomaly is determined by the network side.
The UE may be of various types, for example, including, but not limited to, a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, a robot capable of walking on the ground, or an aircraft flying at a low altitude.
In some examples, the reception module 210 and the update module 220 may be program modules. After being executed by a processor, the program modules are capable of receiving a triggering indication issued by the network side and performing the RA update based on the triggering indication.
In some other examples, the reception module 210 and the update module 220 may be hardware-software combined modules. The hardware-software combined modules include, but are not limited to, various programmable arrays. The programmable arrays include, but are not limited to, field programmable arrays and complex programmable arrays.
In some examples, the reception module 210 and the update module 220 may be pure hardware modules. The pure hardware modules include, but are not limited to, application-specific integrated circuits.
In some examples, the apparatus further includes:
In some examples, the triggering indication is received before the UE is paged.
In an example, the triggering indication may encompass indication information of the TA anomaly. The indication information is configured to indicate a cause to trigger the UE to initiate a registration update procedure.
A communication device is provided in an example of the disclosure. The communication device includes:
The memory may include various types of storage media. The storage media are non-transitory computer storage media that can continue remembering information stored after the communication device is powered off.
The communication device includes: UE and a core network device.
The processor may be connected to the memory through a bus, etc., and configured to read an executable program stored in the memory, for example, at least one of the methods shown in
With reference to
Typically, the processing component 802 controls an overall operation of the UE 800, such as operations associated with display, telephone calls, data communication, a camera operation, and a recording operation. The processing component 802 may include one or more processors 820 to execute instructions, so as to complete all or some of the steps of the above method. In addition, the processing component 802 may include one or more modules, so as to facilitate interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module, so as to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data, so as to support the operations at the UE 800. Examples of these data include instructions of any application or method operated on the UE 800, contact data, phonebook data, messages, pictures, videos, etc. The memory 804 may be implemented through any type of volatile or non-volatile storage devices or a combination of them, such as a static random access memory (SRAM), an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a programmable read-only memory (PROM), a read-only memory (ROM), a magnetic memory, a flash memory, a magnetic disk or an optical disk.
The power source component 806 provides power for various components of the UE 800. The power source component 806 may include a power source management system, one or more power sources, and other components associated with power generation, management, and distribution for the UE 800.
The multimedia component 808 includes a screen that provides an output interface between the UE 800 and a user. In some examples, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If including the touch panel, the screen may be implemented as a touch screen, so as to receive an input signal from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. Except for sensing a boundary of a touch or swipe action, the touch sensor may also measure duration and a pressure associated with a touch or swipe operation. In some examples, the multimedia component 808 includes a front-facing camera and/or a rear-facing camera. When the UE 800 is in an operation mode, such as a photographing mode or a video mode, the front-facing camera and/or the rear-facing camera may receive external multimedia data. Each of the front-facing camera and the rear-facing camera may be a fixed optical lens system or have a focal length and an optical zoom capacity.
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 audio signals received may be further stored in the memory 804 or sent via the communication component 816. In some examples, the audio component 810 further includes a speaker configured to output the audio signals.
The I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module. The peripheral interface module above may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
The sensor component 814 includes one or more sensors configured to provide state assessments of various aspects of the UE 800. For example, the sensor component 814 may detect an on/off state of the UE 800 and relative locating of the components. For example, the components are a display and a keypad of the UE 800. The sensor component 814 may also detect a change in location of the UE 800 or one component of the UE 800, presence or absence of contact between the user and the UE 800, orientation or acceleration/deceleration of the UE 800, and a change in temperature of the UE 800. The sensor component 814 may include a proximity sensor configured to detect presence of a nearby object in the absence of any physical contact. The sensor component 814 may further include light sensors, such as a complementary metal-oxide-semiconductor transistor (CMOS) or a charge coupled device (CCD) image sensor configured to be used in imaging application. In some examples, the sensor component 814 may further include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate wired or wireless communication between the UE 800 and other devices. The UE 800 may access a radio network based on a communication standard, for example, wireless fidelity (WiFi), 2G, or 3G, or a combination of them. In an example, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an example, the communication component 816 further includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented on the basis of a radio frequency identification (RFID) technology, an infrared data association (IrDA) technology, an ultra wide band (UWB) technology, a Bluetooth (BT) technology, etc.
In the example, the UE 800 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 elements configured to execute the method above.
A non-transitory computer-readable storage medium including an instruction, such as a memory 804 including an instruction, is further provided in an example, where the instruction above may be executed by the processor 820 of the UE 800, so as to complete the method above. For example, the non-transitory computer-readable storage medium may be an ROM, a random access memory (RAM), a compact disk read-only memory (CD-ROM), a magnetic tape, a floppy disc, an optical data storage device, etc.
As shown in
With reference to
The network device 900 may further include a power source component 926 configured to execute power source management of the network device 900, a wired or wireless network interface 950 configured to connect the network device 900 to a network, and an input/output (I/O) interface 958. The network device 900 may operate based on an operating system stored in the memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.
Other embodiments of the disclosure will readily occur to those skilled in the art upon consideration of the description and practice of the invention disclosed here. The disclosure is intended to cover any variations, uses, or adaptive changes of the disclosure that follow the general principles of the disclosure and include common general knowledge or customary technical means in the art not disclosed in the disclosure. The description and the examples are merely deemed illustrative, and the true scope and spirit of the disclosure are indicated by the following claims.
It should be understood that the disclosure is not limited to the precise structure that has been described above and shown in the accompanying drawings, and that various modifications and changes can be made without departing from the scope of the disclosure. The scope of the disclosure is merely limited by the appended claims.
In a first aspect, a method for processing a TA anomaly is provided in an example of the disclosure. The method is executed by a network device and includes:
In an embodiment, further including:
In an embodiment, further including:
In an embodiment, further including:
In an embodiment, further including:
In an embodiment, where the registration update request includes:
In an embodiment, where the network device includes: an access management function (AMF).
In a second aspect, a method for processing a TA anomaly is provided in an example of the disclosure. The method is executed by a user equipment (UE) and includes:
In an embodiment, further including:
In a third aspect, apparatus for processing a TA anomaly is provided in an example of the disclosure. The apparatus includes:
In an embodiment, further including:
In an embodiment, further including:
In an embodiment, further including:
In an embodiment, further including:
In an embodiment, where the registration update request includes:
In an embodiment, where the network device includes an access management function (AMF).
In a fourth aspect, apparatus for processing a TA anomaly is provided in an example of the disclosure. The apparatus includes:
In an embodiment, further including:
In a fifth aspect, a communication device is provided in an example of the disclosure. The communication device includes a processor, a transceiver, a memory, and an executable program stored in the memory and runnable by the processor, where the processor executes the method for processing a TA anomaly in the first foregoing aspect when running the executable program.
In a sixth aspect, a computer storage medium is provided in an example of the disclosure. The computer storage medium stores an executable instruction, where the executable instruction implements the method for processing a TA anomaly in the first foregoing aspect when executed by a processor.
In the technical solutions according to the examples of the disclosure, after being found, the TA anomaly of the UE is recorded; and a network side actively triggers the UE to perform the RA update based on the TA anomaly. Accordingly, the TA anomaly is removed, so that abnormalities associated with the TA where the UE is positioned, such as a paging failure caused by the TA anomaly, are suppressed.
The present application is a U.S. National Stage of International Application No. PCT/CN2021/107292, filed on PCT Jul. 20, 2021, the contents of all of which are incorporated herein by reference in their entireties for all purposes.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2021/107292 | 7/20/2021 | WO |
