Optimized user equipment capabilities signaling including recovery from database failure

Abstract

Methods and apparatus for UE capability communication are provided, including computer application products. In some exemplary embodiments, an apparatus may be provided comprising: receiving, at least: receiving from a UE capability management function a message including a first restart counter value indicating a restart of the UE capability management function; in response to receiving the first restart counter value, blocking one or more legacy UE capability identifiers associated with a second restart counter value associated with a state prior to the restart of the UE capability management function; and transmitting the first restart counter value indicating the restart of the UE capability management function. Related systems, methods, and articles of art are also described.

Description

Including optimized user equipment capabilities communication technologies for database fault recovery. The subject matter described in this article is related to wireless. In a cellular system, a User Equipment (UE) can provide capability information to the network, such as the UE's capabilities, including its capabilities for the Radio Access Network (RAN). The size of the UE's capability information can become significant over time. However, 3GPP is pursuing a work project on optimizing the UE's radio capability signaling in Release 16 (for example, see 800025, FS_RACS, “Study on optimizations on UE radio capability signaling” and 800097, FS_RACS_RAN, “Study on optimizations on UE radio capability signaling – NR / E-UTRA Aspects”). Methods and devices for communicating the capabilities of user devices, including computer program products. In some exemplary embodiments, a device may be provided including at least one processor and at least one memory, the at least one memory including computer code, the at least one memory and the computer code being configured to cause the at least one processor to cause the device to at least: receive from a user equipment capability management function a message including a first restart counter value, the first restart counter value indicating a restart of the user equipment capability management function; in response to receiving the first restart counter value, prevent one or more legacy user equipment capability identifiers associated with a second restart counter value, the second restart counter value being associated with a state prior to the restart of the user equipment capability management function; and send the first restart counter value indicating the restart of the user equipment capability management function. In some variations, one or more features disclosed herein may be optionally included in any feasible combination, including the following features: The first restart counter value may be stored. When the device receives a registration request including a user equipment capability identifier associated with the second restart counter value, and / or when verifying one or more user equipment capability identifiers stored for a registered user equipment, the device may compare the second restart counter value with the first restart counter value to determine whether the second restart counter value matches the first restart counter value. A message may be sent to the radio access network to trigger the retrieval of user equipment capability information for a user equipment. This message may be sent when the device does not have a user equipment capability identifier associated with the second restart counter value in its cache. A new user equipment capability identifier may be assigned to the user equipment and associated with the user equipment capability information including at least one radio capability, wherein the new user equipment capability identifier may be associated with the first restart counter value. The assigned new UE capability identifier can be sent to the UE in a registration acceptance message, a configuration update message, a global unique temporary identifier reassignment command message, and / or a non-access layer signaling message. A new UE capability identifier and / or the first restart counter value can be sent to a radio access network to enable the radio access network to block the use of one or more old UE capability identifiers associated with the second restart counter value. The UE capability identifier associated with the first restart counter value and / or the first restart counter can be stored. The new UE capability identifier and / or the first restart counter value can be sent to a radio access network via an N2 interface or an S1 interface message. Context information, including the old UE radio capability identifier associated with the second restart counter value, can be sent to one or more UEs. The first restart counter value, indicating the restart of the UE capability management function, can be sent to the radio access network. The device may be included in a core network node, an access and mobility management function, and / or a mobility management entity, or the device may include the core network node, the access and mobility management function, and / or the mobility management entity. In some exemplary embodiments, an apparatus may be provided including at least one processor and at least one memory, the at least one memory including computer code, the at least one memory and the computer code being configured by the at least one processor to cause the apparatus to at least: receive a first user device capability identifier associated with a first restart counter value indicating a restart of one of the user device capability management functions; associate the first user device capability identifier with at least one user device capability; and store the first restart counter value and / or the first user device capability identifier associated with the at least one user device capability. In some variations, one or more features disclosed herein may be optionally included in any feasible combination, including the following features: A registration request, including a first user equipment capability identifier associated with the first restart counter value, may be sent to a core network via a radio access network. The first restart counter value may indicate that one of the user equipment capability management functions is near a restart, compared to a second restart counter value associated with the device and a second user equipment capability identifier. In response to the received first user equipment capability identifier, the use of the second user equipment capability identifier may be blocked. The blocking of the second user equipment capability identifier may include deleting the second user equipment capability identifier. After receiving the first user equipment capability identifier associated with the first restart counter value, one or more user equipment capability identifiers associated with the second restart counter value may be cached, and the cache may include the corresponding user equipment capability information. The first user equipment capability identifier associated with the first restart counter value can be received via a registration acceptance message, a configuration update message, a globally unique temporary identifier reallocation command message, and / or an access control layer signaling message. The first user equipment capability identifier can be transmitted to a radio access network. The device may be included in a user equipment, or the device may include the user equipment. Depending on the desired configuration, the above-described forms and features can be implemented in systems, devices, methods, and / or articles. Details of one or more variations of the subject matter described herein are presented in the accompanying drawings and the following description. The features and advantages of the subject matter described herein will become apparent from this description and drawings, and from the claims. As mentioned above, User Equipment (UE) can provide UE capability information to the network. As the size of this UE capability information increases, it can lead to inefficiencies, including wasted storage resources, wasted spectrum, and similar issues. 3GPP is proposing a solution that provides a centralized node, such as a UE Capability Management Function (UCMF), to allocate a UE radio capability ID (also known as a UE capability ID). The UE radio capability ID represents the UE's capabilities, including its radio capabilities for the RAN. This UE radio capability ID can be provided to the UE by the network and / or the UCMF, which stores the UE radio capability ID for the UE. Alternatively, a mapping of the UE radio capability ID to the associated UE capability information can be cached in the network, such as in a core network node, radio access node, and / or similar. The UE can then send the UE radio capability ID to the network in one or more messages. For example, in a 5G system, the UE can then send its radio capability ID to the network in one or more registration messages. In an EPS (Evolved Encapsulation System), the UE can then send its radio capability ID to the network in one or more attachment messages (and / or tracking area update messages). In either case, the network detects the UE's capability information (based on the UE's radio capability ID), including the UE's radio capabilities (e.g., supported radio access technologies, RF parameters, supported bands, etc.), and can obtain the UE's complete set of radio capabilities without the network triggering a UE capability information query procedure (thus saving on radio communication). However, the use of centralized nodes such as UCMF can cause problems related to failures, such as hardware failures, software failures, data loss or corruption, and / or other issues requiring a reboot or other recovery methods. For example, if UCMF fails and some, but not all, of the corresponding data for UE capability information, such as the mapping from each UE radio capability ID to the corresponding UE capability information (which includes the UE's radio capabilities), is lost, the failure could cause a problem in a Publicly Mobile Network (PLMN) because the PLMN cannot recover from the failure. This is because UEs may have outdated UE radio capability IDs, and the RAN and core network may be caching outdated UE radio capability IDs and their mapped UE capability information. One solution to the problem after UCMF recovery is to indicate (e.g., signal, transmit, notify, etc.) the recovery of UCMF to the Access and Mobility Management Function (AMF) in the 5G system or to the Mobility Management Entity (MME) in the EPS. Furthermore, this solution can also indicate to a UE that the use of a UE radio capability ID stored in the UE should be prevented (e.g., erasure, deletion, clearing, ignoring, clearing, marking or indicating not to use, marking or indicating that the ID is obsolete, etc.), as this ID is obsolete and may no longer be suitable for network use after the failure. The use of obsolete UE radio capability IDs may cause problems for the PLMN, as it is unknown whether the UE's stored UE radio capability ID was assigned before or after a UCMF failure. In short, after a UCMF failure and reboot, the PLMN does not know whether the UE radio capability ID provided by the UE is the ID from before the failure (and therefore an obsolete and / or inactive or invalid ID) or the ID from after recovery (and therefore an obsolete and / or active or valid ID). Therefore, this method has a drawback: the UE must be informed (that it received a UE radio capability ID before the failure) to prevent the use of its "obsolete" UE radio capability ID, and the network cannot determine whether the UE is using an "obsolete" UE radio capability ID. Thus, it is necessary to determine the timing of assigning the UE capability ID (e.g., before or after UCMF recovery). In some exemplary embodiments, the UE radio capability ID may be associated with an indicator indicating that the UCMF has been restarted. This indicator may take the form of a counter for the UCMF (hereinafter referred to as the "restart counter value") in the PLMN. For example, a field of the UE radio capability ID may include the restart counter value. This restart counter value may indicate whether the current UE radio capability ID is an old ID (for example, associated with the pre-failure state of the UCMF and therefore not associated with the latest value of the restart counter) or a new UE radio capability ID (for example, associated with a restored state of the UCMF and / or the latest value of the restart counter). The restart counter value may be transmitted separately from the UE radio capability ID, rather than being included as a field in the UE radio capability ID. In some exemplary embodiments, the restart counter value may be transmitted and stored together with the UE radio capability ID. According to some exemplary embodiments, when the UCMF recovers after a fault, the UCMF may indicate a value to a core network node for a restart counter. This value may be another restart counter value (e.g., a "new restart counter value") indicating that the UCMF's restart counter value has changed, such as after recovery from a fault. In some exemplary embodiments, the UCMF may indicate this new restart counter value to one or more core network nodes proactively (e.g., without an explicit request from one or more core network nodes) or upon request or contact from one or more core network nodes. For example, the UCMF may include a restart counter value in response to a core network node message, such as a request message and / or the like. In some exemplary embodiments, one or more core network nodes may indicate the new restart counter value to one or more RAN nodes in contact with the core network node. The core network node (which receives a new restart counter) may provide the new restart counter to the RAN proactively (via a message) or in a response message to a request from a RAN node. In some exemplary embodiments, the use of some, but not all, of the stored UE radio capability IDs and corresponding legacy mappings (associated with legacy, UCMF pre-failure, and / or recovery) may be blocked at the UE, radio access network, core network nodes, and other nodes. Within the network, the RAN and core network may maintain cached "stale" UE radio capability IDs for handling any existing registered UEs (which may be using stale UE radio capability IDs until the UE radio capability IDs expire in the cache according to the caching policy). When a network, such as a core network node or similar entity, receives a UE radio capability ID from a UE, the network can compare the restart counter value provided by the UE (which may be included in or provided together with the UE radio capability ID) with the restart counter value provided by the latest UCMF. The UE radio capability ID, including the restart counter value, can be received in a 5G system registration message or in one of the attachment (or tracking area update) messages in 4G / LTE / EPS. If there is a mismatch between the restart counter value provided by the UE and the restart counter value provided by the latest UCMF, the network may be unable to use (e.g., may block) the UE radio capability ID received from the UE, unlike any available mapping of this UE radio capability ID (which may be received from the UE) to UE capability information that it might retrieve from its cache. This mismatch signals to the network node that the UE is using an obsolete UE radio capability ID. If a mismatch in the restart counter value is detected and / or the core network does not store an old or obsolete restart counter value for the UE radio capability ID provided by the UE in its cache of the UE radio capability ID to UE capability information mapping relationship, the network can obtain the UE's UE capability information. For this purpose, the network can then (for example, via a UE capability information query) request, receive, and / or retrieve the UE's capability information from the UE. However, if the core network caches old or obsolete UE radio capability IDs provided by the UE, the core network can use new radio capability IDs mapped to these cached values ​​in the UE capability information (which correspond to the old or obsolete UE radio capability IDs received from the UE). In a query or cached state, once the core network has a current set of UE capability information for the UE, the core network can request the UCMF to assign a new UE radio capability ID to that set of UE capability information. "New" here means that the UE radio capability ID is more recent in time than the old or obsolete UE capability ID assigned by the UCMF after one of the UCMF restarts and / or before the failure and / or recovery. The network can map and cache the new UE radio capability ID associated with the new restart counter value in the UE capability information (e.g., including, mapping, etc.) of the UCMF. The network can then indicate the new UE radio capability ID (associated with the new restart counter value) to the UE in a registration acceptance message in the 5G system, or, if applicable, in an attached acceptance or tracking area update acceptance message in the EPS. Alternatively, the new UE radio capability ID (associated with the new restart counter value) can be transmitted to the UE in a UE configuration update message in the 5G system, in a Global Unique Temporary Identifier (GUTI) reallocation command message in the EPS, and / or in other types of non-accessible stratum signaling messages initiated from the core network and received by the UE in the 5G system and / or the EPS. The UE can store the restart counter value assigned by the UCMF and the UE radio capability ID (in cases where the restart counter value is not part of the UE radio capability ID itself) together as part of the UE radio capability ID set for the PLMN. If a UE has other UE radio capability IDs for another set of UE capabilities previously communicated by the UE, and these other UE radio capability IDs are associated with older UCMF restart counter values, the UE may continue to store UE radio function IDs associated with older UCMF restart counter values, which relate to other potential UE radio configurations that can be communicated in the future, based on a local cache policy that considers these values ​​to be obsolete. One operator objective may be to minimize the number of times UE capability information is retrieved from the UE via the air interface, so if these UE radio capability IDs related to other radio configurations remain in the UE, it is desirable that the network can also store and be able to decode these IDs for future communication. However, obsolete UE radio capability IDs (e.g., those associated with older UCMF restart counters) can be removed from the cache / storage in both the UE and the network, with priority over those associated with current UCMF restart counters. This process occurs by repeatedly restarting the UCMF counter each time a UE uses a counter that is not currently in use, indicating the UE's radio capability ID. Alternatively, it can be achieved by updating the AMF / MME for UEs that have UE radio capability IDs in the UE context within the AMF / MME. These UE radio capability IDs are stale IDs even before these UEs contact the AMF and MME via registration / mobility management or other non-access stratum signaling messages. Over time, the UCMF's UE radio function ID database (each of these UE radio function IDs is associated with related UE capability information) can be repopulated for the UE. Moreover, this can be restored after a UCMF failure and recovery. Before providing additional explanations regarding the UCMF restart counter value according to some exemplary embodiments, one example of a portion of a 5G wireless network 100 is illustrated with reference to FIG1A. FIG1A illustrates one example of a network 100 according to some exemplary embodiments. Network 100 may incorporate 5G technology, as well as other types of radio technologies. Network 100 may include one or more user equipment (UEs), such as a UE 150A configured to wirelessly couple to at least one radio access network, such as a 5G radio access network (RAN) 152 served by a radio access point, such as a 5G base station, an LTE base station (eNB), a wireless LAN access point, a local base station, and / or other types of radio access points. When accessing a network, the UE may access the network's radio access network. Network 100 may include a core network, which may include an Access and Mobility Management Function (AMF) 154, a Working Phase Management Function (SMF) 156, a User Plane Function (UPF) 158, a Network Exposure Function (NEF) 166, an Application Function (AF) 172, and the like. In the example of Figure 1A, devices 152 to 164 may be associated with a Visited Public Mobile Network (VPLMN) 166. The UPF may interface with a Data Network (DN) 196. The AMF 178 may interface with a User Data Management Function (UDM) in a Local Public Mobile Network (HPLMN) 170. In the example of Figure 1A, according to some exemplary embodiments, the network includes a UCMF 199, which includes a counter 198 configured to provide a restart counter value. The UCMF may be a core network node, and the UCMF may interface to an AMF 154, NEF 166, AF 172, and / or other nodes. Figure 1A also illustrates service interfaces such as N1, N2, N6, etc. The architecture, nodes (including AMF, SMF, and other devices shown in Figure 1A), and service interfaces can be defined according to a standard such as 3GPP TS 23.501, but other standards and proprietary interfaces may be used. Some nodes of network 100 can be implemented as dedicated, physical devices, while other components can be virtualized. For example, a core network node such as AMF or SMF can be hosted on a dedicated machine, or it can be hosted on a virtual machine (for example, running on a computer or other type of physical data processor), and dynamically realized with other virtualized core network node functions. Furthermore, although Figure 1A illustrates a certain number of nodes (e.g., a single RAN, AMF, etc.), other numbers of nodes can still be implemented. Moreover, although Figure 1A illustrates a single access network and a single local network, other numbers of access and / or local networks can still be included. Figure 1B illustrates one example of an EPS network 199 implementation based on some exemplary embodiments. Figure 1B illustrates UCMF 199, which interfaces with a Service Capability Exposure Function (SCEF) 188, an Application Function (AF) 172, and a Mobility Management Entity (MME) 176. Network 199 also includes a UE 150A, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 174, a Service Gateway (S-GW) 180, a Packet Gateway (PGW) 178, and a Home Subscriber Server (HSS) 182. Figure 2 illustrates an example of a procedure 200 used in conjunction with the restart counter value of UCMF, based on some exemplary embodiments. At 210, according to some exemplary embodiments, UCMF 199 may reset the UCMF restart counter 198, which generates a new restart counter value to indicate that the UCMF has recovered after a fault. The fault and recovery may be a total or partial fault related to hardware, software, data loss, or some other reason that creates a need for a restart of the UCMF (e.g., an interruption during UCMF operation or corruption of UE radio capability IDs or mapping information). In the example of Figure 2, the priority, old, obsolete counter value "x" is incremented by 1 ("+1") to indicate the new restart counter value. Therefore, a network node or UE may be able to determine that a UE radio capability ID including the priority restart counter value "x" represents an "obsolete" UE radio capability ID that should not be used. In some exemplary embodiments, the restart counter value is stored in a persistent UCMF persistent memory so that the value of the restart counter is incremented upon recovery after a fault. At 220 , according to some illustrative embodiments, UCMF 199 may inform another node, such as AMF 154, of a new restart counter value. In response to restarting the counter at 210, the UCMF may notify the AMF of the new restart counter value by sending a message. Based on this disclosure, it is understood that any AMF (which may receive a restart counter from the UCMF in a prospective manner as shown in Figure 2) may have been in contact with the UCMF at least once and may at that time obtain a first value of the UCMF restart counter for the UCMF and may have signed these notifications from the UCMF (or this may be assembled as an automatic signature in the UCMF at any time when the AMF first contacts the UCMF). Alternatively or in addition, a new value of the restart counter may be provided in a response message for one request from the UCMF (e.g., a request for assigning a new UE radio capability ID to the UE, or a request for parsing a UE radio capability ID that the UE has provided to the AMF in a registered request message). At 230 , according to some illustrative embodiments, a network node such as AMF 154 may prevent the use of one or more old, stale UE radio capability IDs and may store new restart counter values ​​received at 220 . The AMF may receive the New Restart Counter value and (for example, based on a comparison made with a storage prior to the failure and recovery of the UCMF) determine that the UCMF has reset the counter 198 (for example, due to a failure and recovery). In this way, the AMF may prevent the use of (for example, erase, delete, clear, ignore, clear, mark or indicate not to be used, mark or indicate ID stale, etc.) some if not all of the old UE radio capability IDs associated with the old, stale restart counter values ​​of UCMF (and / or any associated mapped UE capability information). For example, the AMF may delete these old UE radio capability IDs, or alternatively, together with the mapped UE capability information, cache these old UE radio capability IDs and indicate that the IDs are stale IDs. The cache cache may allow the reassignment of UE capability information to a new UE radio capability ID, which can reduce the need to request the full capability information set of its UE from the UE via a one-UE capability query message. In the FIG. As described above, the AMF may store the value of the new restart counter received at 220 . At 240, according to some exemplary embodiments, a network node such as AMF 154 may send a new restart counter value to RAN 152. For example, the AMF may send a new restart counter value of UCMF (which is "x+1" in this example) to the RAN as part of an AMF configuration update message so as to update the RAN with the new restart counter value of UCMF. At 250, according to some exemplary embodiments, RAN 152 may prevent the use of one or more old, obsolete UE radio capability IDs and may store them in the new restart counter value received at 240. As in the AMF situation at 230, RAN 152 may cache these old UE radio capability IDs along with mapped UE capability information and indicate that these IDs are obsolete. In this way, for UEs that are registered, connected, and continue to use old values ​​in their RAN network, the old UE radio capability IDs can be retrieved from the cache if needed in the RAN. Returning to the aforementioned example where the new restart counter value is x+1 and the stored restart counter is x, the RAN may delete one or more UE radio capability IDs that include or are associated with a restart counter value less than x+1, or for UEs that are still registered and connected and continue to use old values ​​in their RAN network, their cached values ​​will remain obsolete if these IDs are still needed in the RAN. As described above, the RAN may store the new restart counter value x+1 received at 220. At 260, according to some exemplary embodiments, UE 150A may send a message to the network including a UE radio capability ID, which further includes a restart counter value. For example, UE 150A may send a registration request to AMF 154. The registration request may include the UE radio capability ID, which includes a restart counter value, which is x in the example of Figure 2. In response, AMF may (for example, based on a comparison with one stored in UCMF before the failure and recovery) determine that the UE has an obsolete UE radio capability ID, since the new restart counter is x+1 in this example. In such a situation and / or when AMF no longer caches the obsolete UE radio capability ID, AMF may send a message to RAN to retrieve the UE's capability information. At 270, according to some exemplary embodiments, AMF 154 may send a message, such as an initial bridging request message, to RAN 152 to trigger RAN to query information related to the UE's capabilities. For example, an initial bridging request may include an indication, such as no UE radio capability ID and / or no capability. When received at RAN, this indication may trigger RAN to initiate a UE capability query procedure to obtain information about the UE's capabilities. At 280, according to some exemplary embodiments, a UE capability query occurs. For example, RAN 152 may send a UE capability query message to UE 150A. This message represents a network request to the UE to provide the UE's capability information, and in particular the UE's network, including RAN capability information. In response to the UE capability query message, the UE can respond to the RAN with the UE capability information. At 290, according to some exemplary embodiments, RAN 152 may provide UE capability information, including the UE’s radio capabilities, to AMF 154 via the N2 interface. At 299, according to some exemplary embodiments, a new UE radio capability ID can be assigned to the UE. The assigned new UE radio capability ID can be mapped to the capability information communicated by the UE at 290, or to UE capabilities retrieved from the cache (e.g., UE capability information that is still valid but mapped to an old, obsolete UE radio capability ID). Now, the AMF has the current UE capability information, and the AMF can request the UCMF to provide a UE radio capability ID for the UE's capability information, such as the UE's radio capabilities. When the UCMF returns this value to the AMF, the AMF provides this new UE radio capability ID value to the UE in a registration acceptance message (associated with a new UCMF restart counter that is "x+1" in this example). Alternatively, the UE radio capability ID (including or along with the new UCMF restart counter value) can be transmitted to the UE in a UE configuration update message in a 5G system, or in other types of non-accessible stratum signaling messages initiated from the core network and received by the UE in a 5GS. The AMF can also provide the RAN with this new value for the UE radio capability ID (including or together with the new UCMF restart counter value, which is "x+1" in this example) in a UE context update or initial context setup request context message as specified in 3GPP TS 23.501 and 3GPP TS 38.413. When the UE receives a UE radio capability ID (which may be associated with a new UCMF restart counter), the UE may retain (it may be subject to a caching policy that considers these IDs to be stale IDs) other UE radio capability IDs stored for the PLMN for other radio configurations using older restart counter values. Therefore, if the network also caches stale values, the UE can still point these IDs to the network when it changes its radio configuration (one purpose here may be to minimize the need to trigger UE radio capability query 280). Figure 3 illustrates an example of a procedure 300 for processing a restart counter value of a UCMF, based on some exemplary embodiments. At 302, according to some exemplary embodiments, a network node such as AMF 154 may receive a message from a UCMF 199 including a restart counter value. A network node such as AMF may determine that when it receives the UCMF message including the restart counter value, the UCMF has recovered from a failure or some other type of event that requires the deletion of older UE radio function IDs or that such IDs are marked as obsolete in its cache. According to some exemplary embodiments, in response to receiving a restart counter value, a network node such as AMF 154 may at 304 block the use of one or more old UE radio capability IDs (for example, by deleting them, marking them as obsolete IDs, and / or storing such IDs in a cache). Furthermore, according to some exemplary embodiments, the network node may at 306 store the new restart counter value received at 230 as described above. According to some exemplary embodiments, a network node such as AMF 154 may send the new restart counter value of UCMF to other nodes, such as RAN 152, at 308. For example, as part of an AMF configuration update, the AMF may send the new restart counter value of UCMF to the RAN (or other nodes including the UE). According to some exemplary embodiments, at 310, a network node such as AMF 154 may receive a registration request including a restart counter value. For example, the AMF may receive a UE radio capability ID, which includes a restart counter value with a value x. Thus, the AMF may (for example, based on a mismatch or comparison with one stored in the UCMF prior to failure and recovery) determine that the UE has an obsolete UE radio capability ID, since the new restart counter is x+1 in this instance. When the UE capability is determined to be obsolete based on the restart counter value as described above, this may trigger the AMF to send a message to RAN 152 at 312 to retrieve the UE's capability information. However, if the AMF stores the obsolete UE radio capability ID value (which is associated with the received, obsolete restart counter value) and the UE radio capability information mapped to that ID in a cache, the AMF may not need to trigger the retrieval of the radio capability from the UE, but the AMF may instead use the cached UE capability information (e.g., radio capabilities). At 314, a network node such as AMF 154, if having triggered UE capability retrieval at 312, can receive UE capability information, including the UE's radio capabilities, via the N2 interface. At 316, a network node such as AMF 154 can assign a new UE radio capability ID to the UE, as described above at 299. This assignment, for example, may include requesting the UCMF to provide a UE radio capability ID corresponding to the current set of UE capabilities (e.g., the UE's radio capabilities) and sending it to the UE in a registration acceptance message. Alternatively, the UE radio capability ID, including or associated with a new UCMF restart counter value, can be transmitted in a UE configuration update message in a 5G system, or in other types of non-accessible stratum signaling messages initiated from the core network and received by the UE in a 5G system. If the UE receives a UE radio capability ID with a new restart counter, the UE can prevent the use of the corresponding UE radio capability ID with the old UCMF restart counter. However, if these IDs need to be communicated when the UE changes its radio configuration and the network cache caches these old values, the UE can still retain any other UE radio capability IDs for other UEs with old restart counters (thus avoiding the need to trigger UE capability retrieval from the AMF), and understand that the UE cache policy may consider these IDs to be obsolete IDs. Figure 4 illustrates another example of a procedure 400 for processing a restart counter value of a UCMF, based on some exemplary embodiments. At 405, according to some exemplary embodiments, UE 150A may send a registration request to AMF 154 including one of a restart counter values. According to some exemplary embodiments, when the restart counter value sent by the UE is an outdated value and the AMF does not cache the UE radio capability ID value sent by the UE that includes or is associated with this outdated UCMF restart counter, the UE may receive a request from the network at 410 to provide UE capability information. For example, UE 150A may receive a UE capability query message from RAN 152, which triggers the UE to respond at 412 by providing the network (e.g., RAN, AMF, etc.) with the UE's current UE capability information, including radio capabilities. Furthermore, when the restart counter value is stale, the UE can, at 415, receive another UE radio capability ID mapped to the UE capability information provided at 412 from the AMF in a registration acceptance message (or in a UE configuration update message in a 5G system, or in other non-access stratum signaling messages initiated from the core network and received by the UE in a 5G system). For example, this other UE radio capability ID may include a new UE radio capability ID, which includes or is associated with the new restart counter generated after restoration as described above at 210. At 420, the UE can store the new UE radio capability ID mapped to the UE capability information (which includes the new restart counter) and erase the corresponding old UE radio capability ID value. As mentioned above, the UE can retain other UE radio capability IDs for other UE radio configurations with old restart counter values. In some exemplary embodiments, when the AMF detects an outdated UE radio capability ID value in the UE context (the AMF stores the UE context for one of the registered UEs), the AMF can proactively update the UE with a new UE radio capability ID using a UE configuration update message in the 5G system (5GS), or in a GUTI reallocation command message in the EPS, and / or in some other type of non-accessible stratum signaling message initiated from the core network and received by the UE in the 5GS and / or EPS, without waiting for the next UE registration. Figure 5 illustrates a block diagram of a network node 500 according to some exemplary embodiments. The network node 500 can be configured to provide one or more network-side functions, such as a base station (e.g., RAN 152), AMF 154, UCMF 199, and / or other network nodes. According to some exemplary embodiments, network node 500 may include a network interface 502, a processor 520, and a memory 504. Network interface 502 may include wired and / or wireless transceivers to enable access to other nodes, including base stations, devices 152 to 180, the Internet, and / or other nodes. Memory 504 may include electrically and / or non-electrically dependent memory containing code that, when executed by at least one processor 520, provides the program disclosed herein for network nodes (see, for example, 200, 300, and / or the like). For example, network node may be configured to receive, from at least one user equipment capability management function, a message including a first restart counter value indicating a restart of the user equipment capability management function. A network node may also respond to receiving the first restart counter value by blocking one or more legacy user equipment capability identifiers associated with a second restart counter value, which is associated with a pre-restart state of the user equipment capability management function. The network node may also send the first restart counter value indicating the restart of the user equipment capability management function. The network node may also be configured to provide one or more of the following: When the network node receives a registration request including a user equipment capability identifier associated with the second restart counter value, and / or when verifying one or more user equipment capability identifiers stored for a registered user equipment, the network node may compare the second restart counter value with the first restart counter value to determine whether the second restart counter value matches the first restart counter value. A message may be sent to the radio access network to trigger the retrieval of user equipment capability information for a user equipment. This message may be sent when the network node does not have a user equipment capability identifier associated with the second restart counter value in its cache. A new VIP capability identifier associated with VIP capability information including at least one radio capability can be assigned to the VIP, wherein the new VIP capability identifier may be associated with the first restart counter value. The assigned new VIP capability identifier can be sent to the VIP in a registration acceptance message, a configuration update message, a global unique temporary identifier reallocation command message, and / or a non-access layer signaling message. A new VIP capability identifier and / or the first restart counter value can be sent to a radio access network to enable the radio access network to block the use of one or more old VIP capability identifiers associated with the second restart counter value. The VIP capability identifier associated with the first restart counter value and / or the first restart counter can be stored. The new VIP capability identifier and / or the first restart counter value can be sent to a radio access network via an N2 interface or an S1 interface message.The system can send context information, including a legacy user equipment radio capability identifier associated with the second restart counter value, to one or more user equipments. It can also send the first restart counter value, indicating the restart of the user equipment capability management function, to the radio access network. Figure 6 illustrates a block diagram of a device 10 according to some exemplary embodiments. Device 10 may represent a user device, such as user device 150A to 150C. Device 10 or a portion thereof may be implemented in other network nodes, including base stations / WLAN access points and other network nodes (e.g., devices 152 to 184). Device 10 may include at least one antenna 12 communicating with transmitter 14 and receiver 16. Alternatively, the transmitting and receiving antennas may be separate. Device 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitters and receivers, and to control the functionality of the device. Processor 20 may be configured to control the functionality of the transmitters and receivers by activating control signals via electrical leads connected to the transmitters and receivers. Similarly, processor 20 may be configured to control other components of device 10 by activating control signals via electrical leads connecting processor 20 to other components such as a display or a memory. Processor 20 may be implemented in various ways, including circuitry, at least one processing core, one or more microprocessors with accompanying digital signal processors, processors without accompanying digital signal processors, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (e.g., an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and / or the like), or some combination thereof. Therefore, although processor 20 is illustrated as a single processor in FIG. 6, it may still include a plurality of processors or processing cores in some exemplary embodiments. Device 10 may be capable of operating using one or more air interface standards, communication protocols, modulation types, access types, and / or similar technologies. Signals sent and received by processor 20 may include communication information, based on an air interface standard applicable to cellular systems and / or any number of different wired or wireless network technologies, including but not limited to Wi-Fi, Wireless Local Access Network (WLAN) technologies such as IEEE 802.11, 802.16, 802.3, ADSL, DOCSIS, and / or similar technologies. Additionally, these signals may include voice data, user-generated data, user-requested data, and / or similar data. For example, device 10 and / or one of its cellular modems may be capable of operating according to various first-generation (1G), second-generation (2G or 2.5G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), Internet Protocol Multimedia Subsystem (IMS) protocols (e.g., Session Initiation Protocol (SIP)) and / or similar protocols. For example, device 10 may be capable of operating according to 2G radio communication protocols IS-136, Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSMA), GSM, IS-95, Code Division Multiple Access (CDMA), and / or similar protocols. Additionally, for example, device 10 may be capable of operating according to 2.5G radio communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and / or similar protocols. Furthermore, for example, device 10 may be capable of operating according to 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and / or similar protocols. Device 10 may also be capable of operating according to 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or similar protocols. Additionally, for example, device 10 may be capable of operating according to 4G wireless communication protocols such as LTE-Advanced, 5G, and / or similar protocols, as well as similar wireless communication protocols that may be developed subsequently. It is understood that processor 20 may include circuitry for implementing the audio / video and logic functions of device 10. For example, processor 20 may include a digital signal processor, a microprocessor, an analog-to-digital converter, a digital-to-analog converter, and / or similar devices. The control and signal processing functions of device 10 may be distributed among these devices according to their respective capabilities. Processor 20 may also include an internal voice codec (VC) 20a, an internal data modem (DM) 20b, and / or similar devices. Furthermore, processor 20 may include functions for operating one or more software programs, which may be stored in memory. Generally, processor 20 and the stored software instructions can be combined to cause device 10 to operate. For example, processor 20 may be capable of operating a multithreaded application, such as a web browser. This connection allows device 10 to transmit and receive network content, such as location-based content, according to a protocol, such as Wireless Application Protocol, WAP, Hypertext Transfer Protocol, HTTP, and / or similar protocols. Device 10 may also include a user interface, such as an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and / or the like, operably coupled to processor 20. As described above, display 28 may include a touch-sensitive display, in which a user can select, input values, and / or the like via touch and / or gestures. Processor 20 may also include a user interface circuitry configured to control at least some functions of one or more components of the user interface, such as at least some functions of speaker 24, ringer 22, microphone 26, display 28, and / or similar components. The processor 20 and / or the user interface circuitry including the processor 20 may be configured to control one or more functions of one or more components of the user interface through computer program instructions, such as software and / or firmware, stored in memory accessible to the processor 20, such as electrically soluble memory 40, non-electrically soluble memory 42, and / or similar memory. The device 10 may include a battery for powering various circuits associated with the mobile terminal, for example, circuitry for providing mechanical vibration as a detectable output. The user input interface includes means that allow the device 20 to receive data, such as a keypad 30 (which may be a virtual keyboard displayed on the display 28 or an externally coupled keyboard), and / or other input devices. As shown in Figure 6, device 10 may also include one or more mechanisms for sharing and / or obtaining data. For example, device 10 may include a short-range radio frequency (RF) transceiver and / or interrogator 64, thus enabling sharing and / or obtaining data from electronic devices using RF technology. Device 10 may include other short-range transceivers, such as an infrared (IR) transceiver 66, using Bluetooth. TM Bluetooth is one of the wireless technology operations. TM (BT) transceiver 68, a wireless universal serial bus (USB) transceiver 70, a Bluetooth TMLow-power transceivers, ZigBee transceivers, ANT transceivers, cellular inter-device transceivers, wireless LAN transceivers, and / or any other short-range radio technologies. Device 10, and especially short-range transceivers, may be capable of transmitting data to and / or receiving data from electronic devices within its vicinity, such as those within 10 meters. Device 10, including Wi-Fi or wireless LAN-connected modems, may also be capable of transmitting and / or receiving data from electronic devices according to various wireless network technologies, including 6LoWpan, Wi-Fi, Wi-Fi Low Power, WLAN technologies, such as IEEE 802.11, IEEE 802.15, IEEE 802.16, and / or similar technologies. Device 10 may include memory, such as a Subscriber Identity Module (SIM) 38, a Removable Subscriber Identity Module (R-UIM), an eUICC, a UICC, and / or similar memory, which can store information elements related to a mobile user. In addition to the SIM, device 10 may also include other removable and / or fixed memory. Device 10 may include electrically dependent memory 40 and / or non-electrically dependent memory 42. For example, electrically dependent memory 40 may include random access memory (RAM) containing dynamic and / or static RAM, on-chip or off-chip cache memory, and / or similar electrically dependent memory. Embeddable and / or removable non-electrically dependent memory 42 may, for example, include read-only memory, flash memory, magnetic storage devices such as hard drives, floppy disk drives, magnetic tapes, optical drives and / or media, non-electrically dependent random access memory (NVRAM), and / or similar non-electrically dependent memory. Similar to electrically dependent memory 40, non-electrically dependent memory 42 may include a cache for temporarily storing data. At least a portion of electrically dependent and / or non-electrically dependent memory may be embedded in processor 20. Such memory may store one or more software programs, instructions, information files, data, and / or similar entities that the device may use to perform one or more of the operations disclosed herein, such as receiving a first user equipment capability identifier associated with a first restart counter value indicating a restart of one of the user equipment capability management functions; associating the first user equipment capability identifier with at least one user equipment capability; and storing the first restart counter value and / or the first user equipment capability identifier associated with the at least one user equipment capability. Alternatively or additionally, the device may be configured to perform the operations disclosed herein with respect to base stations / WLAN access points and network nodes including UEs. Such memories may contain an identifier capable of uniquely identifying one of the devices 10, such as an International Mobile Equipment Identity (IMEI) code. In an exemplary embodiment, the processor 20 may use computer code stored in memory 40 and / or 42 to assemble to provide the operations disclosed herein for the UE, such as receiving a first user equipment capability identifier associated with a first restart counter value indicating a restart of one of the user equipment capability management functions; associating the first user equipment capability identifier with at least one user equipment capability; and storing the first restart counter value and / or the first user equipment capability identifier associated with the at least one user equipment capability. Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. For example, the software, application logic, and / or hardware may reside on memory 40, control device 20, or electronic components. In some exemplary embodiments, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, a "computer-readable medium" can be any non-transitory medium that may contain, store, transmit, propagate, or deliver instructions for use by or in conjunction with an instruction execution system, device, or apparatus, such as a computer or data processor circuit system. Figure 6 illustrates an example where a computer-readable medium may include a non-transitory computer-readable storage medium, which may be any medium that may contain or store instructions for use by or in conjunction with an instruction execution system, device, or apparatus, such as a computer. The technical effects of one or more exemplary embodiments disclosed herein may be improved communication and do not limit the scope, interpretation, or application of the claims described below in any way. Depending on the desired configuration, the contents described herein may be specifically implemented in systems, devices, methods, and / or articles. For example, the base station and user equipment (or one or more components thereof) and / or programs described herein may be implemented using one or more of the following: a processor that executes program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field-programmable gate array (FPGA), and / or a combination thereof. These various implementations may include implementations in one or more computer programs that are executable and / or interpretable on a programmable system, which includes at least one programmable processor, which may be a special-purpose processor or a general-purpose processor, coupled to receive and transmit data and instructions to a storage system, at least one input device, and at least one output device. These computer programs (also referred to as programs, software, software applications, applications, components, code, or symbolic code) include machine instructions for a programmable processor and may be implemented using a high-level procedural and / or object-oriented programming language, and / or a compositional / machine language. As used herein, the term "computer-readable media" means any computer program product, machine-readable medium, computer-readable storage medium, device, and / or apparatus (e.g., magnetic disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions. Similarly, this document also describes systems that may include a processor and a memory coupled to that processor. The memory may include one or more programs that cause the processor to perform one or more of the operations described herein. As will be understood from the foregoing discussion, the present invention may be embodied in various other embodiments, including but not limited to the following: 1. A device comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause the device to perform at least the following actions by the at least one processor: receiving from a user device capability management function a message including a first restart counter value, the first restart counter value indicating a restart of the user device capability management function; in response to receiving the first restart counter value, preventing one or more old user device capability identifiers associated with a second restart counter value, the second restart counter value being associated with a state prior to the restart of the user device capability management function; and sending the first restart counter value indicating the restart of the user device capability management function. 2. The device of embodiment 1, wherein the device is further configured to at least store the first restart counter value. 3. A device of any of Embodiments 1 to 2, wherein when the device receives a registration request including a user equipment capability identifier associated with the second restart counter value, and / or when verifying one or more user equipment capability identifiers stored for a registered user equipment, the device further compares at least the second restart counter value with the first restart counter value to determine whether the second restart counter value matches the first restart counter value. 4. A device of any of Embodiments 1 to 3, wherein the device further sends at least a message to the radio access network to trigger the retrieval of user equipment capability information for a user equipment. 5. A device of Embodiment 4, wherein the device sends the message when its cache does not include a user equipment capability identifier associated with the second restart counter value. 6. A device of any of Embodiments 1 to 5, wherein the device further assigns at least one new user equipment capability identifier associated with user equipment capability information including at least one radio capability to a user equipment, wherein the new user equipment capability identifier is associated with the first restart counter value. 7. The device of embodiment 6, wherein the assigned new UE capability identifier is sent to the UE in a registration acceptance message, a configuration update message, a global unique temporary identifier reassignment command message, and / or a non-access layer signaling message. 8. The device of any of embodiments 1 to 7, wherein the device further causes the device to send at least a new UE capability identifier and / or the first restart counter value to a radio access network, so that the radio access network can prevent the use of one or more old UE capability identifiers associated with the second restart counter value, and / or causes the device to store at least the UE capability identifier associated with the first restart counter value and / or the first restart counter.9. The device of embodiment 8, further comprising sending the new user equipment capability identifier and / or the first restart counter value to a radio access network via at least an N2 interface or an S1 interface message. 10. The device of any of embodiments 1 to 9, further comprising sending context information to at least one or more user equipments, the context information including the old user equipment radio capability identifier associated with the second restart counter value. 11. The device of any of embodiments 1 to 10, wherein the first restart counter value indicating the restart of the user equipment capability management function is sent to the radio access network. 12. The device of any of embodiments 1 to 11, wherein the device is included in a core network node, an access and mobility management function, and / or a mobility management entity, or the device includes the core network node, the access and mobility management function, and / or the mobility management entity. 13. An apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to cause the apparatus to perform at least the following actions by the at least one processor: receiving a first user equipment capability identifier associated with a first restart counter value indicating a restart of one of the user equipment capability management functions; associating the first user equipment capability identifier with at least one user equipment capability; and storing the first restart counter value and / or the first user equipment capability identifier associated with the at least one user equipment capability. 14. The apparatus of embodiment 13, further comprising causing the apparatus to send a registration request to a core network via at least one radio access network, the registration request including the first user equipment capability identifier associated with the first restart counter value. 15. The apparatus of any of embodiments 13 to 15, wherein the first restart counter value indicates a more recent restart of one of the user equipment capability management functions compared to a second restart counter value associated with a second user equipment capability identifier for the apparatus. 16. The device of embodiment 16, further comprising, at least in response to the received first user equipment capability identifier, preventing the use of the second user equipment capability identifier. 17. The device of embodiment 17, wherein the blocking of the second user equipment capability identifier includes deleting the second user equipment capability identifier. 18. The device of any of embodiments 13 to 17, further comprising, at least after receiving the first user equipment capability identifier associated with the first restart counter value, cacheing one or more user equipment capability identifiers associated with the second restart counter value, the cache including corresponding user equipment capability information.19. A device of any of Embodiments 13 to 18, wherein the first user equipment capability identifier associated with the first restart counter value is received via a registration acceptance message, a configuration update message, a global unique temporary identifier reallocation command message, and / or an access control layer signaling message. 20. A device of any of Embodiments 13 to 19, wherein the first user equipment capability identifier is transmitted to a radio access network. 21. A device of any of Embodiments 13 to 20, wherein a user equipment includes the device, or the device includes the user equipment. 22. A method comprising: receiving from a user equipment capability management function a message including a first restart counter value, the first restart counter value indicating a restart of the user equipment capability management function; in response to receiving the first restart counter value, blocking one or more old user equipment capability identifiers associated with a second restart counter value, the second restart counter value being associated with a pre-restart state of the user equipment capability management function; and transmitting the first restart counter value indicating the restart of the user equipment capability management function. 23. The method of embodiment 22, further comprising: storing the first restart counter value. 24. The method of any of embodiments 22 to 23, further comprising: when receiving a registration request including a user equipment capability identifier associated with the second restart counter value, and / or when verifying one or more user equipment capability identifiers stored for the registered user equipment, comparing the second restart counter value with the first restart counter value to determine whether the second restart counter value matches the first restart counter value. 25. The method of any of embodiments 22 to 24, further comprising: sending a message to the radio access network to trigger the retrieval of user equipment capability information for a user equipment. 26. The method of embodiment 25, wherein the message is sent when a cache does not include a user equipment capability identifier associated with the second restart counter value. 27. The method of any of Embodiments 22 to 26, further comprising: assigning a new user equipment capability identifier to a user equipment and associating it with user equipment capability information including at least one radio capability, wherein the new user equipment capability identifier is associated with the first restart counter value. 28. The method of Embodiment 27, wherein the assigned new user equipment capability identifier is sent to the user equipment in a registration acceptance message, a configuration update message, a global unique temporary identifier reallocation command message, and / or an accessless stratum signaling message.29. The method of any of Embodiments 22 to 28, further comprising: sending a new user equipment capability identifier and / or the first restart counter value to a radio access network, such that the radio access network can prevent the use of the one or more legacy user equipment capability identifiers associated with the second restart counter value, and / or being ordered to store at least the user equipment capability identifiers associated with the first restart counter value and / or the first restart counter. 30. The method of Embodiment 29, further comprising: sending the new user equipment capability identifier and / or the first restart counter value to a radio access network via an N2 interface or an S1 interface message. 31. The method of any of Embodiments 22 to 30, further comprising: sending context information to one or more user equipments, the context information including the legacy user equipment radio capability identifiers associated with the second restart counter value. 32. The method of any of Embodiments 22 to 31, wherein the first restart counter value indicating the restart of the user equipment capability management function is transmitted toward the radio access network. 33. A method comprising: receiving a first user equipment capability identifier associated with a first restart counter value indicating a restart of one of the user equipment capability management functions; associating the first user equipment capability identifier with at least one user equipment capability; and storing the first restart counter value associated with the at least one user equipment capability and / or the first user equipment capability identifier. 34. The method of Embodiment 33, further comprising causing the device to send a registration request to a core network via at least one radio access network, the registration request including the first user equipment capability identifier associated with the first restart counter value. 35. The method of any of Embodiments 33 to 34, wherein the first restart counter value indicates a more recent restart of one of the user equipment capability management functions compared to a second restart counter value associated with a second user equipment capability identifier for the device. 36. The method of embodiment 35, further comprising: in response to the received first user equipment capability identifier, blocking the use of the second user equipment capability identifier. 37. The method of embodiment 36, wherein blocking the second user equipment capability identifier includes deleting the second user equipment capability identifier. 38. The method of any of embodiments 33 to 37, further comprising: after receiving the first user equipment capability identifier associated with the first restart counter value, caching one or more user equipment capability identifiers associated with the second restart counter value, the cache including corresponding user equipment capability information.39. The method of any of Embodiments 33 to 38, wherein the first user equipment capability identifier associated with the first restart counter value is received via a registration acceptance message, a configuration update message, a global unique temporary identifier reallocation command message, and / or a non-access stratum signaling message. 40. The method of any of Embodiments 33 to 39, wherein the first user equipment capability identifier is transmitted to a radio access network. 41. An apparatus comprising: means for receiving a message including a first restart counter value from a user equipment capability management function, the first restart counter value indicating a restart of the user equipment capability management function; means for blocking one or more old user equipment capability identifiers associated with a second restart counter value, the second restart counter value being associated with a state prior to the restart of the user equipment capability management function; and means for transmitting the first restart counter value indicating the restart of the user equipment capability management function. 42. The apparatus of Embodiment 41, wherein the apparatus includes means for performing any of Embodiments 23 to 32. 43. An apparatus comprising: means for receiving a first user device capability identifier associated with a first restart counter value indicating a restart of one of the user device capability management functions; means for associating the first user device capability identifier with at least one user device capability; and means for storing the first restart counter value and / or the first user device capability identifier associated with the at least one user device capability. 44. The apparatus of embodiment 43, wherein the apparatus includes means for performing any of embodiments 34 to 40. 45. A non-transitory computer-readable storage medium including program code that, when executed, causes operations including: receiving a message from a user device capability management function including a first restart counter value indicating a restart of one of the user device capability management functions; in response to receiving the first restart counter value, preventing one or more old user device capability identifiers associated with a second restart counter value associated with a state prior to the restart of one of the user device capability management functions; and transmitting the first restart counter value indicating the restart of the user device capability management function. 46. ​​A non-transitory computer-readable storage medium including program code that, when executed, causes operations comprising: receiving a first user device capability identifier associated with a first restart counter value indicating a restart of one of the user device capability management functions; associating the first user device capability identifier with at least one user device capability; and storing the first restart counter value and / or the first user device capability identifier associated with the at least one user device capability. While some variations have been described in detail above, other modifications or additions are still possible. In particular, further features and / or variations may be provided in addition to those mentioned herein. Furthermore, the above embodiments are applicable to various combinations and sub-combinations of the disclosed features, and / or combinations and sub-combinations of several further features disclosed above. Other embodiments are within the scope of the following claims. Depending on the desired outcome, the different functions discussed herein may be performed in a different order and / or in parallel. Furthermore, depending on the desired outcome, one or more of the aforementioned functions may be selected or combined. While some embodiments are described in the independent claims, other embodiments include other combinations of features from the described embodiments and / or appendices with features from the independent claims, not only the combinations explicitly described in the claims. It is also noted herein that although illustrative embodiments are described above, these descriptions should not be viewed with a limiting concept. Rather, several variations and modifications may be made without departing from the scope of some embodiments as defined in the appended claims. Other embodiments may fall within the scope of the following claims. The term "based on" includes "at least based on". Unless otherwise indicated, the use of the term "such as" means "for example". 10: Device; 12: Antenna; 14: Transmitter; 16: Receiver; 20, 504, 520: Processor; 20a: Internal Voice Programmer; 20b: Internal Data Modem; 22: Ringer; 24: Speaker; 26: Microphone; 28: Display; 30: Keypad; 38: User Identity Module; 40: Electron-dependent Memory; 42: Non-electronic Memory; 64: Short-range Radio Frequency (RF) Transceiver and / or Interrogator; 66: Infrared (IR) Transceiver; 68: Bluetooth. TM (BT) Transceiver 70: Wireless Universal Serial Bus (USB) Transceiver 100: 5G Wireless Network 150A: UE 152: 5G Radio Access Network 154: Access and Mobility Management Functions 156: Operational Phase Management Functions 158: User Plane Functions 166: Network Exposure Functions 170: Local Public Mobile Network 172: Application Functions 174: Evolved UMTS Terrestrial Radio Access Network 176: Mobility Management Entity 178: Enclosure Gateway 180: Service Gateway 182: Home Subscriber Server 188: Service Capability Exposure Functions 196: Data Network 198: Counter 199: EPS Network 200, 300, 400: Procedures 210~290, 299, 302~316, 405~420: Steps 500: Network Nodes 502: Network Interface In the diagram, Figure 1A illustrates an example of a portion of a 5G system according to some exemplary embodiments; Figure 1B illustrates an example of a portion of an evolutionary sealing system, based on some exemplary embodiments; Figure 2 illustrates an example of a process flow for handling and recovering from UCMF faults, based on some exemplary embodiments; Figure 3 illustrates an example of a processing flow for processing a restart counter value from the perspective of a network node, based on some exemplary embodiments; Figure 4 illustrates another example of a processing flow for processing a restart counter value from the viewpoint of a user device, based on some exemplary embodiments; Figure 5 illustrates an example of a network node based on some exemplary embodiments; and Figure 6 illustrates an example of a device according to some exemplary embodiments. In the diagram, the similarity label is used to refer to items that are the same or similar. 100:5G wireless network 150A:UE 152: 5G Radio Access Network 154: Access and Mobility Management Functions 156: Work Phase Management Function 158: User plane function 166: Online Exposure Function 170: Local Public Mobile Network 172: Application Functions 178: Sealing Gate 196: Data Network 198: Counter 199: EPS Network

Claims

1. A user equipment comprising: means for receiving a registration acceptance message or a configuration update message, wherein, The registration acceptance message indicates that a registration request previously provided by the user equipment to a network element of a communication system has been accepted by the communication system. The configuration update message includes an instruction for configuration information regarding communication between the user equipment and the network element of the communication system. The received registration acceptance message or configuration update message includes a first user equipment capability identifier associated with at least one user equipment capability, wherein the first user equipment capability identifier is associated with a first value. Means are provided for storing the first user equipment capability identifier associated with the at least one user equipment capability and the first value in a cache of the user equipment. Means are provided for receiving a subsequent configuration update message, which includes a second user equipment capability identifier associated with one or more user equipment capabilities, wherein the second user equipment capability identifier is associated with a second value. Means are also provided for determining whether the first user equipment capability identifier is obsolete or no longer valid based on a comparison between the first value and the second value.

2. The user equipment as claimed in claim 1, further comprising: means for removing the first user equipment capability identifier from the cache prior to removing the second user equipment capability identifier from the cache based on determining that the first user equipment capability identifier is obsolete or no longer valid.

3. The user equipment as claimed in claim 1 or 2, further comprising: means for removing the first user equipment capability identifier from the cache based on a determination that the first user equipment capability identifier is obsolete or no longer valid.

4. The user equipment as claimed in claim 1 or 2, further comprising: means for continuing to use the first user equipment capability identifier until the first user equipment capability identifier is removed from the cache.

5. The user equipment as claimed in claim 1 or 2, further comprising: means for sending a subsequent registration request, including the first user equipment capability identifier or the second user equipment capability identifier, to a core network via a radio access network.

6. The user equipment as described in claim 1 or 2, wherein, One or both of the first user equipment capability identifier and the second user equipment capability identifier include a user equipment radio capability identifier assigned by the network.

7. The user equipment as described in claim 1 or 2, wherein: The means for receiving is configured to receive at least one of the registration acceptance message, the configuration update message, or the subsequent configuration update message from the Access and Mobility Management Function (AMF) of one of the communication systems.

8. The user equipment as described in claim 1 or 2, wherein, The network element includes one or more of an Access and Mobility Management Function (AMF) or a User Equipment Capability Management Function (UCMF).

9. The user equipment as claimed in claim 1 or 2, further comprising: means for storing the second user equipment capability identifier in the cache of the user equipment based on a determination that the first user equipment capability identifier is obsolete or no longer valid.

10. The user equipment as claimed in claim 1 or 2, further comprising: means for determining that the first user equipment capability identifier should not be used based on the determination that the first user equipment capability identifier is obsolete or no longer valid.

11. A method for communication, comprising: receiving a registration acceptance message or a configuration update message at a user equipment, wherein, The registration acceptance message indicates that a registration request previously provided by the user equipment to a network element of a communication system has been accepted by the communication system. The configuration update message includes an instruction for configuration information regarding communication between the user equipment and the network element of the communication system. The received registration acceptance message or configuration update message includes a first user equipment capability identifier associated with at least one user equipment capability, wherein the first user equipment capability identifier is associated with a first value. The first user equipment capability identifier associated with the at least one user equipment capability and the first value is stored in a cache of the user equipment. A subsequent configuration update message is received at the user equipment, the subsequent configuration update message including a second user equipment capability identifier associated with one or more user equipment capabilities, wherein the second user equipment capability identifier is associated with a second value. The first user equipment capability identifier is determined to be obsolete or invalid based on a comparison between the first value and the second value.

12. The method of claim 11, further comprising: removing the first user equipment capability identifier from the cache prior to removing the second user equipment capability identifier from the cache based on determining that the first user equipment capability identifier is obsolete or no longer valid.

13. The method as described in claim 11 or 12, further comprising: removing the first user equipment capability identifier from the cache based on the determination that the first user equipment capability identifier is obsolete or no longer valid.

14. The method as described in claim 11 or 12, further comprising: continuing to use the first user equipment capability identifier until the first user equipment capability identifier is removed from the cache.

15. The method as described in claim 11 or 12, further comprising: sending a subsequent registration request, including the first user equipment capability identifier or the second user equipment capability identifier, to a core network via a radio access network.

16. The method as described in claim 11 or 12, wherein, One or both of the first user equipment capability identifier and the second user equipment capability identifier include a user equipment radio capability identifier assigned by the network.

17. The method as described in claim 11 or 12, further comprising: receiving at least one of the registration acceptance message, the configuration update message, or the subsequent configuration update message from an Access and Mobility Management Function (AMF) of one of the communication systems.

18. The method as described in claim 11 or 12, wherein, The network element includes one or more of an Access and Mobility Management Function (AMF) or a User Equipment Capability Management Function (UCMF).

19. The method of claim 11 or 12, further comprising: storing the second user equipment capability identifier in the cache of the user equipment based on determining that the first user equipment capability identifier is obsolete or no longer valid.

20. The method as described in claim 11 or 12, further comprising: determining that the first user equipment capability identifier should not be used based on the determination that the first user equipment capability identifier is obsolete or no longer valid.

21. A non-transitory computer-readable medium containing instructions that, when executed by a user device, cause the user device to at least: receive a registration acceptance message or a configuration update message, wherein, The registration acceptance message indicates that a registration request previously provided by the user equipment to a network element of a communication system has been accepted by the communication system. The configuration update message includes an instruction for configuration information regarding communication between the user equipment and the network element of the communication system. The received registration acceptance message or configuration update message includes a first user equipment capability identifier associated with at least one user equipment capability, wherein the first user equipment capability identifier is associated with a first value. The first user equipment capability identifier associated with the at least one user equipment capability and the first value is stored in a cache of the user equipment. A subsequent configuration update message is received, which includes a second user equipment capability identifier associated with one or more user equipment capabilities, wherein the second user equipment capability identifier is associated with a second value. The first user equipment capability identifier is determined to be obsolete or invalid based on a comparison between the first value and the second value.

Images