Optimized user equipment capability signaling including recovery from database failures

Abstract

Methods and apparatus for UE capability signaling are provided, including computer program products. In some example embodiments, an apparatus may be provided, the apparatus including being caused to at least: receive a message from a user equipment capability management function, the message including a first restart counter value indicating a restart of the user equipment capability management function; in response to receiving the first restart counter value, inhibit 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 send the first restart counter value indicating a restart of the user equipment capability management function. Related systems, methods, and articles of manufacture are also described.

Description

Technical Field

[0001] The subject matter described herein relates to wireless. Background Art

[0002] In a cellular system, a user equipment (UE) may provide capability information to the network, such as the capabilities of the UE, including its capabilities for a radio access network (RAN). The size of the UE capability information may become significant over time. However, in 3GPP, work items are being advanced on optimization of UE radio capability signaling in rel-16 (see, e.g., 800025, FS_RACS, "Study on optimization of UE radio capability signaling" and 800097, FS_RACS_RAN, "Study on optimization of UE radio capability signaling - NR / E-UTRA aspects"). Summary of the invention

[0003] Methods and apparatus for user equipment capability signaling are provided, the methods and apparatus including computer program products.

[0004] In some example embodiments, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to at least: receive a message from a user equipment capability management function, the message comprising a first restart counter value indicating a restart of the user equipment capability management function; in response to receiving the first restart counter value, prohibit 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 send the first restart counter value indicating a restart of the user equipment capability management function.

[0005] In some variants, one or more features disclosed herein including the following features may be optionally included in any feasible combination. A first restart counter value may be stored. When a device receives a registration request including a user equipment capability identifier associated with a second restart counter value, and / or when checking against 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 a radio access network to trigger the acquisition of user equipment capability information for a user equipment. When the device does not include a user equipment capability identifier associated with the second restart counter value in its cache, the message may be sent. A new user equipment capability identifier associated with user equipment capability information including at least one radio capability may be assigned to the user equipment, wherein the new user equipment capability identifier may be associated with the first restart counter value. In a registration acceptance message, a configuration update message, a globally unique temporary identifier reallocation command message, and / or a non-access layer signaling message, the assigned new user equipment capability identifier may be sent to the user equipment. The new user equipment capability identifier and / or the first restart counter value may be sent to the radio network so that the radio access network can prohibit the use of one or more old user equipment capability identifiers associated with the second restart counter value. The user equipment capability identifier and / or the first restart counter associated with the first restart counter value may be stored. The new user equipment capability identifier and / or the first restart counter value may be sent to the radio access network via an N2 interface or an S1 interface message. Context information including the old user equipment radio capability identifier associated with the second restart counter value may be sent toward one or more user equipments. The first restart counter value indicating the restart of the user equipment capability management function may be sent toward 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 include a core network node, an access and mobility management function and / or a mobility management entity.

[0006] In some example embodiments, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to at least: receive a first user equipment capability identifier associated with a first restart counter value indicating a restart of a user equipment capability management function; associate the first user equipment capability identifier with at least one user equipment capability; and store the first restart counter value and / or the first user equipment capability identifier associated with the at least one user equipment capability.

[0007] In some variants, one or more features disclosed herein including the following features may be optionally included in any feasible combination. A registration request including a first user equipment capability identifier associated with a first restart counter value may be sent to a core network via a radio access network. When compared with a second restart counter value associated with a second user equipment capability identifier for a device, the first restart counter value may indicate a recent restart of a user equipment capability management function. In response to the received first user equipment capability identifier, the use of the second user equipment capability identifier may be prohibited. The prohibition of the second user equipment capability identifier may include deleting the second user equipment capability identifier. One or more user equipment capability identifiers associated with the second restart counter value may be cached after receiving the first user equipment capability identifier associated with the first restart counter value, and the cache may include corresponding user equipment capability information. The first user equipment capability identifier associated with the first restart counter value may be received via a registration accept message, a configuration update message, a globally unique temporary identifier reallocation command message, and / or a non-access layer signaling message. The first user equipment capability identifier may be sent to the radio access network. The device may be included in a user equipment or include a user equipment.

[0008] The above aspects and features can be implemented in systems, devices, methods and / or articles according to the desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the following description. The features and advantages of the subject matter described herein will be apparent from the description and drawings and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In the accompanying drawings,

[0010] Figure 1A depicts an example of a portion of a 5G system according to some example embodiments;

[0011] Figure 1B depicts an example of a portion of an evolved packet system according to some example embodiments;

[0012] Figure 2 depicts an example of a process flow for handling UCMF failure and recovery according to some example embodiments;

[0013] Figure 3 depicts an example of a process flow for handling restart counter values ​​from the perspective of a network node in accordance with some example embodiments;

[0014] Figure 4 depicts another example of a process flow for handling a restart counter value from the perspective of a user device in accordance with some example embodiments;

[0015] Figure 5 depicts an example of a network node according to some example embodiments; and

[0016] Figure 6 An example of an apparatus according to some example embodiments is depicted.

[0017] In the drawings, the same reference numbers are used to refer to the same or similar items. DETAILED DESCRIPTION

[0018] As described above, a user equipment (UE) may provide UE capability information to the network, which may cause inefficiencies, including wasting storage resources, wasting spectrum, etc. as the size of the UE capability information increases. 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 referred to as a UE capability ID). The UE radio capability ID represents the capabilities of the UE, including the UE radio capabilities relative to the RAN. The UE radio capability ID may be provided to the UE by the network and / or the UCMF, which stores the UE radio capability ID for the UE. The mapping of the UE radio capability ID to the associated UE capability information may also be cached in the network, such as in a core network node, a radio access node, etc. Subsequently, the UE radio capability ID may be sent by the UE to the network in one or more messages. For example, in a 5G system, the UE radio capability ID may then be sent by the UE to the network in one or more registration messages, while in EPS (Evolved Packet System), the UE radio capability ID may then be sent by the UE to the network in one or more attachment messages (and / or tracking area update messages). In either case, the network is aware (based on the UE radio capability ID) of the UE's capability information, which includes the UE's radio capabilities (e.g., supported radio access technologies, radio frequency parameters, supported frequency bands, etc.), without the network having to trigger a UE capability information query procedure to obtain the complete set of the UE's radio capabilities (thereby saving signaling over the radio).

[0019] However, the use of a centralized node such as a UCMF may cause problems with failures, such as hardware failures, software failures, data loss or corruption, and / or other problems requiring a restart or other type of recovery. For example, if the UCMF fails and there is a corresponding data loss of some (if not all) UE capability information, such as a mapping from each UE radio capability ID to corresponding UE capability information (which includes the UE's radio capabilities), the failure may cause problems in a public land mobile network (PLMN) because the PLMN may not be able to recover from the failure, since the UE may have a stale UE radio capability ID, and the RAN and core network may also cache the stale UE radio capability ID and the mapped UE capability information.

[0020] After the UCMF recovers from the failure, the solution to the problem is to indicate (e.g., signal, send, inform, etc.) the recovery of the UCMF to the access and mobility management function (AMF) in the 5G system or the mobility management entity (MME) in the EPS. In addition, the solution may also indicate to the UE that the UE radio capability ID stored at the UE is prohibited from being used (e.g., erased, deleted, flushed, ignored, cleared, marked or indicated not to be used, marked or indicated that the ID is invalid, etc.), which may no longer be suitable for use with the network after the failure due to the ID invalidation. The use of the invalid UE radio capability ID may cause problems for the PLMN, which does not know whether the stored UE radio capability ID of the UE has been assigned before the UCMF failure or after the UCMF recovery. In short, after the UCMF failure and restart, the PLMN does not know whether the UE radio capability ID provided by the UE is before the failure (and therefore invalid and / or no longer active or valid) or after the recovery (and therefore invalid and / or active or valid). Therefore, the disadvantage of this approach is that the UE needs to be informed (it has received the UE radio capability ID before the failure) that the use of its "invalid" UE radio capability ID is prohibited, and the network cannot determine whether the UE is using the "invalid" UE radio capability ID. Therefore, it is necessary to determine at which time the UE capability ID is assigned (for example, before UCMF recovery or after UCMF recovery).

[0021] In some example embodiments, the UE radio capability ID may be associated with an indicator to indicate that the UCMF has been restarted. The indicator may take the form of a counter (hereinafter referred to as a "restart counter value") of the UCMF in the PLMN. For example, a field of the UE radio capability ID may include a restart counter value. The restart counter value may indicate whether the current UE radio capability ID is invalid (e.g., 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 (e.g., associated with the post-recovery state of the UCMF and / or the latest value of the restart counter). The restart counter value may be sent separately from the UE radio capability ID, rather than including the restart counter value as a field in the UE radio capability ID. In some example embodiments, the restart counter value may be sent and stored together with the UE radio capability ID.

[0022] According to some example embodiments, when the UCMF recovers after a failure, the UCMF may indicate the value of the restart counter to the core network node. The value may be another restart counter value (e.g., a "new restart counter value") to indicate that the restart counter value of the UCMF has changed, such as after recovery from a failure. In some example embodiments, the UCMF may actively indicate the new restart counter value to one or more core network nodes (e.g., in the absence of an explicit request from one or more core network nodes) or when requested or contacted by 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, etc.). In some example embodiments, one or more core network nodes may indicate the new restart counter value to one or more RAN nodes contacted by the core network node. The core network node (which receives the new restart counter) may actively provide the new restart counter to the RAN (via a message) or in a response message to a request from a RAN node.

[0023] In some example embodiments, some (if not all) of the stored UE radio capability IDs and corresponding old mappings (associated with old, pre-UCMF failures and / or recovery) may be disabled for use at UEs, radio access networks, core network nodes, and other nodes. In the network, the RAN and core network may keep "invalidated" UE radio capability IDs cached for use in handling any existing registered UEs (which may use the invalidated UE radio capability IDs until the UE radio capability IDs are out of cache according to the cache policy).

[0024] When a network such as a core network node receives a UE radio capability ID from a UE, the network may compare the restart counter value provided by the UE (which is included in or provided 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 may be received in a 5G system registration message or an attach (or tracking area update) message 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 UE radio capability ID received from the UE may not be used by the network (e.g., prohibited, etc.), except that any available mapping of the UE radio capability ID (which is received from the UE) to the UE capability information may be obtained from its cache. The mismatch signals to the network node that the UE is using an invalid UE radio capability ID.

[0025] If a mismatch of the restart counter value is detected and / or the core network does not store the old invalid restart counter value of the UE radio capability ID provided by the UE in its cache of UE radio capability ID to UE capability information mapping, the network can obtain UE capability information for the UE. To this end, the network can then request, receive and / or obtain the UE capability information from the UE (e.g., via UE capability information query). However, if the core network caches the old invalid UE radio capability ID provided by the UE, the core network can use the new radio capability ID mapped to these cached values ​​of the UE capability information (which corresponds to the old invalid UE radio capability ID received from the UE). In the case of query or cache, once the core network has a current UE capability information set for the UE, the core network can request the UCMF to assign a new UE radio capability ID to the UE capability information set. The "new" here indicates that the UE radio capability ID is updated in time than the old invalid UE capability assigned by the UCMF after the UCMF restart and / or before the failure and / or recovery.

[0026] The network may map and cache the new UE radio capability ID of the UCMF associated with (e.g., including, mapped to, etc.) the new restart counter value to the UE capability information for the UE. The network may then indicate the new UE radio capability ID (which is associated with the new restart counter value) to the UE in a registration accept message in the 5G system or (as applicable) in an attach accept or tracking area update accept message in the EPS. Alternatively, the new UE radio capability ID (which is associated with the new restart counter value) may be transmitted to the UE in a UE configuration update message in the 5G system, a global unique temporary identifier (GUTI) reallocation command message in the EPS, and / or other types of non-access stratum signaling messages initiated from the core network and received by the UE in the 5G system and / or EPS. The UE may store the restart counter value assigned by the UCMF together with the UE radio capability ID (in the case where the restart counter value is not part of the UE radio capability ID itself) as part of the UE radio capability ID set for the PLMN. If the UE has other UE radio capability IDs of another UE capability set that the UE previously signaled, and the other UE radio capability IDs are associated with older UCMF restart counter values, the UE may keep storing the UE radio capability IDs associated with older UCMF restart counter values, which are associated with other potential UE radio configurations that the UE may signal in the future, based on a local caching strategy that considers these to be invalid values. An operator's goal may include minimizing the time to obtain UE capability information from the UE over the air interface, so if these UE radio capability IDs associated with other radio configurations are retained in the UE, these IDs may be signaled in the future, with the expectation that the network may also store these IDs and be able to interpret them. However, in the UE and the network, invalid UE radio capability IDs (e.g., those associated with old UCMF restart counters) may be removed from the cache / storage with priority relative to invalid UE radio capability IDs associated with the current UCMF restart counter. By repeating this process which occurs each time a UE indicates that it has a UE radio capability ID that is not current for the UCMF restart counter, or by AMF / MME updating UEs that have UE radio capability IDs that are invalid in their UE context in the AMF / MME even before these UEs contact the AMF and MME through registration / mobility management or other non-access stratum signaling messages, the UCMF's database of UE radio capability IDs (each of which is associated with associated UE capability information) can be repopulated for UEs over time. And, this can enable repair after failure and recovery of the UCMF.

[0027] Before providing additional description about the restart counter value of the UCMF according to some example embodiments, Figure 1AAn example of a portion of a 5G wireless network 100 is described. Figure 1A An example of a network 100 is depicted in accordance with some example embodiments. The network 100 may include 5G technology as well as other types of radio technologies.

[0028] The network 100 may include one or more user equipment (UE), 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 wireless access point, such as a 5G base station, an LTE base station (eNB), a wireless local area network access point, a home base station, and / or other types of wireless access points. When accessing the network, the UE may access the radio access network of the network.

[0029] The network 100 may include a core network, which may include an access and mobility management function (AMF) 154, a session management function (SMF) 156, a user plane function (UPF) 158, a network exposure function (NEF) 166, an application function (AF) 182, etc. Figure 1A In the example of , devices 152 to 164 may be associated with a visited public land 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 home public land mobile network (HPLMN) 170.

[0030] exist Figure 1A In the example of , according to some example embodiments, the network includes UCMF 199, which includes counter 198 configured to provide a restart counter value. UCMF can be a core network node, and UCMF can also interface with AMF154, NEF 166, AF 172 and / or other nodes.

[0031] Figure 1A It also depicts service interfaces such as N1, N2, N6, etc. Architecture, nodes (including AMF, SMF, and Figure 1A Other devices depicted) and service interfaces may be defined according to standards such as 3GPP TS 23.501, although other standards and proprietary interfaces may also be used.

[0032] Some nodes of network 100 may be implemented as dedicated physical devices, while other elements may be virtualized. For example, a core network node such as AMF, SMF, etc. may be hosted on a dedicated machine, or it may be hosted on a virtual machine (which executes on, for example, a computer or other type of physical data processor) and dynamically instantiated with other virtualized core network node functions. In addition, although Figure 1AA certain number of nodes are described (e.g., a single RAN, AMF, etc.), but other numbers of each node may also be implemented. Figure 1A A single visited network and a single home network are depicted, but other numbers of visited and / or home networks may also be included.

[0033] Figure 1B An example of an EPS network 199 implementation is depicted in accordance with some example embodiments. Figure 1B Depicted is UCMF 199, which interfaces to a service capability exposure function (SCEF) 188, an application function (AS) 172, and a mobility management entity (MME) 176. Network 199 also includes UE 150A, an evolved UMTS terrestrial radio access network (E-UTRAN) 174, a serving gateway (S-GW) 180, a packet gateway (PGW) 178, and a home subscriber server (HSS) 182.

[0034] Figure 2 An example of a process 200 for use with a restart counter value of a UCMF is depicted in accordance with some example embodiments.

[0035] At 210, according to some example embodiments, UCMF 199 may reset the restart counter 198 of the UCMF, which generates a new restart counter value to indicate that the UCMF has recovered after the failure. The failure and recovery may be a complete failure or a partial failure related to hardware, software, data loss, or some other reason that requires restarting the UCMF (e.g., an interruption in UCMF operation or corruption of UE radio capability ID or mapping information). Figure 2 In the example of FIG. 1 , the previous old failure counter value “x” is incremented by 1 (“+1”) to indicate the new restart counter value. Therefore, the network node or UE can determine that the UE radio capability ID including the previous restart counter value of “x” represents a “failed” UE radio capability ID that should not be used. In some example embodiments, the restart counter value is stored in a persistent manner in the UCMF persistent memory so that the restart counter value can be incremented upon recovery after a failure.

[0036] At 220, according to some example embodiments, UCMF 199 may notify another node (such as AMF 154) of the new restart counter value. In response to resetting the counter at 210, UCMF may notify AMF of the new restart counter value by sending a message. Based on the present disclosure, it will be appreciated that any AMF (which may be in Figure 2The AMF may have contacted the UCMF at least once and may have obtained the first value of the UCMF restart counter for the UCMF at that time, and may also subscribe to these notifications from the UCMF (or this may be configured in the UCMF to be an automatic subscription any time the AMF first contacts the UCMF). Alternatively or additionally, the new value of the restart counter may be provided in a response message to a request from the UCMF (e.g., a request to assign a new UE radio capability ID to the UE, or a request to resolve a UE radio capability ID that the UE has provided in a registration request message to the AMF).

[0037] At 230, according to some example embodiments, a network node such as the AMF 154 may prohibit the use of one or more old, (multiple) invalid UE radio capability IDs, and may store the new restart counter value received at 220. The AMF may receive the new restart counter value and determine (e.g., based on a comparison with what was stored before the failure and recovery of the UCMF) that the UCMF has reset the counter 198 (e.g., due to the failure and recovery). In this way, the AMF may prohibit the use of (e.g., erase, delete, flush, ignore, clear, mark or indicate non-use, mark or indicate ID invalid, etc.) some (if not all) of the old UE radio capability IDs associated with the old invalid restart counter value of the UCMF (and / or any associated mapped UE capability information). For example, the AMF may delete these old UE radio capability IDs, or alternatively, cache these old UE radio capability IDs together with the mapped UE capability information, which has an indication that they are invalid. Caching may allow UE capability information to be reassigned to new UE radio capability IDs, which may reduce the need to request their full set of UE capability information from UEs via UE capability query messages. Figure 2 In the example of , the new restart counter value is x+1, while the stored restart counter is x, so there is a mismatch, and the AMF may then delete or cache any UE radio capability ID included with or associated with the older stored restart counter of x due to failure. As described above, the AMF may store the new restart counter value received at 220.

[0038] At 240, according to some example embodiments, a network node such as AMF 154 may send a new restart counter value to RAN 152. For example, the AMF may send the new restart counter value of the UCMF ("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 the UCMF.

[0039] At 250, according to some example embodiments, the RAN 152 may prohibit the use of one or more old and invalid UE radio capability IDs and may store the new restart counter value received at 240. As in the case of the AMF at 230, the RAN 152 may cache these old UE radio capability IDs together with the UE capability information with a mapping indicating that they are invalid. In this way, if an old UE radio capability ID is needed in the RAN for a UE that is registered, connected, and continues to use the old value in its RAN context, the old UE radio capability ID can be retrieved from the cache. Returning to the previous example where the new restart counter value is x + 1 and the stored restart counter is x, the RAN may delete the restart counter value <x + 1 or one or more UE radio capability IDs associated with the restart counter value <x + 1, or, if these IDs are still needed in the RAN for the UE that is still registered and connected, cache them as invalid values and keep using the old value in its RAN context. As described above, the RAN may store the new restart counter value x + 1 received at 220.

[0040] At 260, according to some example embodiments, the UE 150A may send a message to the network that includes a UE radio capability ID that also includes a restart counter value. For example, the UE 150A may send a registration request to the AMF 154. The registration request may include a UE radio capability ID that includes a restart counter value, which is x in the Figure 2 example. In response, the AMF may determine (e.g., based on a comparison with what was stored before the failure and recovery of the UCMF) that the UE has an invalid UE radio capability ID because the new restart counter is x + 1 in this example. When this is the case and / or the AMF no longer caches the invalid UE radio capability ID, the AMF may send a message to the RAN to obtain the UE's capability information.

[0041] At 270, according to some example embodiments, the AMF 154 may send a message (such as an initial context establishment request message) to the RAN 152 to trigger the RAN to query the UE's capability information. For example, the initial context upgrade request may include an indication, such as no UE radio capability ID and / or no capability. When received at the RAN, this indication may trigger the RAN to initiate a UE capability query process to obtain information about the UE's capabilities.

[0042] At 280, according to some example embodiments, a UE capability query occurs. For example, RAN 152 may send a UE capability query message to UE 150A. The message represents a network request to the UE to provide capability information of the UE, and in particular the network of the UE including RAN capability information. In response to the UE capability query message, the UE may respond to the RAN with the UE capability information.

[0043] At 290, according to some example embodiments, the RAN 152 may provide UE capability information including the radio capabilities of the UE to the AMF 154 via the N2 interface.

[0044] At 299, in accordance with some example embodiments, the UE may be assigned a new UE radio capability ID. The assigned new UE radio capability ID may be mapped to the UE capability information signaled at 290 or to the UE capabilities obtained from a cache (e.g., UE capability information that is still valid but mapped to an old invalidated UE radio capability ID). Because the AMF has current UE capability information, the AMF may request the UCMF to provide the UE radio capability ID of the UE's capability information, such as the UE's radio capabilities. When the UCMF returns the value to the AMF, the AMF provides the new UE radio capability ID value to the UE in a registration accept message (associated with a new UCMF restart counter, which in this example is "x+1"). Alternatively, the UE radio capability ID (including or together with the new UCMF restart counter value) may be transmitted to the UE in a UE configuration update message in a 5G system or other types of non-access stratum signaling messages initiated from the core network and received by the UE in the 5GS. In addition, the AMF may provide this new value of the UE radio capability ID to the RAN in a UE context update or initial context setup request context message as specified in 3GPP TS 23.501 and 3GPP TS 38.413 (including or together with the new UCMF restart counter value, which is "x+1" in this example). When the UE receives the UE radio capability ID (which may be associated with the new UCMF restart counter), the UE may retain (which may be subject to a caching policy that may consider these to be stale IDs) its other UE radio capability IDs stored for the PLMN for other radio configurations with older restart counter values, so that in the event that the network also caches stale values, the UE may still indicate these to the network when the UE changes the radio configuration (here the intention is to minimize the need to trigger the UE radio capability query 280).

[0045] Figure 3 An example of a process 300 for processing a restart counter value of a UCMF is depicted, according to some example embodiments.

[0046] At 302, according to some example embodiments, a network node such as AMF 154 may receive a message including a restart counter value from UCMF 199. 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 deleting older UE radio capability IDs or marking them as invalid in its cache.

[0047] According to some example embodiments, in response to receiving the restart counter value, a network node such as AMF 154 may prohibit the use of one or more old UE radio capability IDs (e.g., delete, mark them as invalid and / or keep them in a cache) at 304. In addition, according to some example embodiments, the network node may store at 306 the new restart counter value received at 230 as described above.

[0048] According to some example embodiments, a network node such as AMF 154 may send the new restart counter value of the UCMF to other nodes such as RAN 152 at 308. For example, the AMF may send the new restart counter value of the UCMF to the RAN (or other nodes including the UE) as part of an AMF configuration update.

[0049] At 310, according to some example embodiments, 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 including a restart counter value having a value of x. In this way, the AMF may determine (e.g., based on a mismatch or comparison with a value stored before the failure and recovery of the UCMF) that the UE has a failed UE radio capability ID because the new restart counter is x+1 in this example. When the UE capability failure is determined based on the restart counter value as described above, this may trigger the AMF to send a message to the RAN 152 at 312 to obtain the UE's capability information. However, if the AMF stores the failed UE radio capability ID value (which is associated with the received failed restart counter value) and the UE radio capability information mapped to the ID in a cache, the AMF may not need to trigger the acquisition of radio capabilities from the UE, and the AMF may use the cached UE capability information (e.g., radio capabilities).

[0050] At 314, if a network node such as AMF 154 has triggered UE capability acquisition at 312, it may receive UE capability information including the UE's radio capabilities via the N2 interface. At 316, a network node such as AMF 154 may assign a new UE radio capability ID to the UE, as described above at 299. The assignment may include requesting the UCMF to provide a UE radio capability ID corresponding to a current set of UE capabilities (e.g., the UE's radio capabilities) and sent to the UE, for example, in a registration accept message. Alternatively, the UE radio capability ID including the new UCMF restart counter value or associated with the new UCMF restart counter value may be transmitted in a UE configuration update message in the 5G system or other types of non-access stratum signaling messages initiated from the core network and received by the UE in the 5G system. If the UE receives a UE radio capability ID with a new restart counter, the UE may prohibit the use of the corresponding UE radio capability ID with the old UCMF restart counter. However, with the understanding that the UE caching policy may consider any other UE radio capability IDs of other UE radio configurations with old restart counters to be invalid IDs, the UE may still retain any other UE radio capability IDs of other UE radio configurations with old restart counters in case any other UE radio capability IDs of other UE radio configurations with old restart counters need to be signaled when the UE changes radio configuration and the network caches these old values ​​(thereby avoiding the need to trigger UE capability acquisition from the AMF).

[0051] Figure 4 Another example of a process 400 for processing a restart counter value of a UCMF is depicted in accordance with some example embodiments.

[0052] At 405, according to some example embodiments, UE 150A may send a registration request including a restart counter value towards AMF 154.

[0053] According to some example embodiments, when the restart counter value sent by the UE is invalid and the AMF does not cache the UE radio capability ID value sent by the UE including the invalid UCMF restart counter or associated with the invalid UCMF restart counter, the UE may receive a request from the network to provide UE capability information at 410. For example, UE 150A may receive a UE capability query message from RAN 152, which triggers the UE to respond by providing the current UE capability information of the UE including the radio capability to the network (e.g., RAN, AMF, etc.) at 412.

[0054] And when the restart counter value is invalid, at 415, the UE may receive another UE radio capability ID mapped to the UE capability information provided at 412 in a registration acceptance message from the AMF (or in a UE configuration update message in a 5G system, or in other non-access layer signaling messages initiated from the core network and received by the UE in the 5G system). For example, as described above at 210, the other UE radio capability ID may include a new UE radio capability ID that includes a new restart counter generated after recovery or is associated with a new restart counter. At 420, the UE may store the new UE radio capability ID (which includes the new restart counter) mapped to the UE capability information and erase the corresponding old UE radio capability ID value. As described above, the UE may retain other UE radio capability IDs for other UE radio configurations with old restart counter values.

[0055] In some exemplary embodiments, when the AMF detects an invalid UE radio capability ID value in the UE context (stored by the AMF for an already registered UE), the AMF may proactively update the UE with the new UE radio capability ID using a UE configuration update message in the 5G system (5GS) or a GUTI reallocation command message in the EPS, and / or some other type of non-access stratum signaling message initiated from the core network in the 5GS and / or EPS and received by the UE, without waiting for the next UE registration.

[0056] Figure 5 A block diagram of a network node 500 is depicted according to some example embodiments. The network node 500 may be configured to provide one or more network-side functions, such as a base station (eg, RAN 152), AMF 154, UCMF 199, and / or other network nodes.

[0057] According to some example embodiments, the network node 500 may include a network interface 502, a processor 520, and a memory 504. The network interface 502 may include a wired and / or wireless transceiver to enable access to other nodes, including base stations, devices 152 to 180, the Internet, and / or other nodes. The memory 504 may include a volatile and / or non-volatile memory including a program code, which, when executed by at least one processor 520, provides, among other things, the processes disclosed herein with respect to the network node (see, for example, processes 200, 300, etc.). For example, the network node may be configured to receive at least a message from a user equipment capability management function including a first restart counter value indicating a restart of the user equipment capability management function. In response to receiving the first restart counter value, the network node may also prohibit 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. The network node may also send a first restart counter value indicating a restart of the user equipment capability management function. The network node may also be configured to provide one or more of the following operations. When the network node receives a registration request including a user equipment capability identifier associated with a second restart counter value, and / or when checking for 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 acquisition of user equipment capability information for the user equipment. The message may be sent when the network node does not include the user equipment capability identifier associated with the second restart counter value in its cache. A new user equipment capability identifier associated with user equipment capability information including at least one radio capability may be assigned to the user equipment, wherein the new user equipment capability identifier may be associated with the first restart counter value. The assigned new user equipment capability identifier may be sent to the user equipment in a registration acceptance message, a configuration update message, a globally unique temporary identifier reallocation command message, and / or a non-access layer signaling message. The new user equipment capability identifier and / or the first restart counter value may be sent to the radio access network so that the radio access network can prohibit the use of one or more old user equipment capability identifiers associated with the second restart counter value. The user equipment capability identifier and / or the first restart counter associated with the first restart counter value may be stored. The new user equipment capability identifier and / or the first restart counter value may be sent to the radio access network via an N2 interface or an S1 interface message. Context information including the old user equipment radio capability identifier associated with the second restart counter value may be sent toward one or more user equipments. The first restart counter value indicating a restart of the user equipment capability management function may be sent to the radio access network.

[0058] Figure 6 A block diagram of an apparatus 10 is illustrated according to some example embodiments.

[0059] The apparatus 10 may represent a user equipment, such as user equipment 150A to 150C. The apparatus 10 or parts thereof may be implemented in other network nodes including base stations / WLAN access points and other network nodes (eg, devices 152 to 184).

[0060] The device 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively, the transmitting and receiving antennas may be separate. The device 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the functions of the device. The processor 20 may be configured to control the functions of the transmitter and receiver by causing control signaling to the transmitter and receiver via electrical leads. Similarly, the processor 20 may be configured to control other elements of the device 10 by causing control signaling via electrical leads connecting the processor 20 to other elements such as a display or memory. For example, the processor 20 may be implemented in various ways, including circuit systems, at least one processing core, (multiple) one or more microprocessors with an accompanying digital signal processor, one or more processors without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuit systems, one or more computers, various other processing elements including integrated circuits (e.g., application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc.), or some combination thereof. Therefore, although in Figure 6 2 is illustrated as a single processor, but in some example embodiments, processor 20 may include multiple processors or processing cores.

[0061] The apparatus 10 is capable of operating using one or more air interface standards, communication protocols, modulation types, access types, etc. The signals sent and received by the processor 20 may include signaling information in accordance with the air interface standard of the applicable cellular system, and / or any number of different wired or wireless networking technologies, including but not limited to Wi-Fi, wireless local access network (WLAN) technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, etc. In addition, these signals may include voice data, user-generated data, user-requested data, etc.

[0062] For example, the device 10 and / or the cellular modem therein can operate according to various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third generation (3G) communication protocols, fourth generation (4G) communication protocols, fifth generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), etc. For example, the device 10 can operate according to 2G wireless communication protocols IS-136, Time Division Multiple Access TDMA, Global System for Mobile Communications GSM, IS-95, Code Division Multiple Access CDMA, etc. In addition, for example, the device 10 can operate according to 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), etc. In addition, for example, the device 10 can operate 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), etc. The device 10 may additionally be capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), etc. Additionally, for example, the device 10 may be capable of operating in accordance with 4G wireless communication protocols such as Advanced LTE, 5G, etc., and similar wireless communication protocols that may be subsequently developed.

[0063] It will be appreciated that the processor 20 may include circuitry for implementing the audio / video and logic functions of the device 10. For example, the processor 20 may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, etc. The control and signal processing functions of the device 10 may be allocated between these devices according to their respective capabilities. The processor 20 may additionally include an internal voice coder (VC) 20a, an internal data modem (DM) 20b, etc. In addition, the processor 20 may include functionality to operate one or more software programs that may be stored in a memory. Typically, the processor 20 and the stored software instructions may be configured to cause the device 10 to perform actions. For example, the processor 20 is capable of operating a connection program, such as a web browser. The connectivity process may allow the device 10 to send and receive web content such as location-based content according to protocols such as wireless application protocol, WAP, hypertext transfer protocol, HTTP, etc.

[0064] The device 10 may also include a user interface, including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, etc., which may be operably coupled to the processor 20. As described above, the display 28 may include a touch-sensitive display, where a user may touch and / or gesture to make selections, input values, etc. The processor 20 may also include a user interface circuit configured to control at least some functions of one or more elements of the user interface, such as the speaker 24, the ringer 22, the microphone 26, the display 28, etc. The processor 20 and / or the user interface circuit system including the processor 20 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions (e.g., software and / or firmware) stored on a memory accessible to the processor 20 (e.g., volatile memory 40, non-volatile memory 42, etc.). The device 10 may include a battery for powering various circuits associated with the mobile terminal, such as a circuit that provides mechanical vibration as a detectable output. The user input interface may include devices that allow the apparatus 20 to receive data, such as a keypad 30 (which may be a virtual keyboard presented on the display 28 or an externally coupled keyboard) and / or other input devices.

[0065] like Figure 6 As shown, the device 10 may also include one or more mechanisms for sharing and / or obtaining data. For example, the device 10 may include a short-range radio frequency (RF) transceiver and / or interrogator 64, so that data can be shared with and / or obtained from electronic devices based on RF technology. The device 10 may include other short-range transceivers, such as infrared (IR) transceivers 66, Bluetooth TM Bluetooth™ (BT) transceiver 68, wireless universal serial bus (USB) transceiver 70, Bluetooth TM Low energy transceiver, ZigBee transceiver, ANT transceiver, cellular device-to-device transceiver, wireless local area link transceiver and / or any other short-range radio technology. The device 10, and in particular the short-range transceiver, is capable of sending data to and / or receiving data from electronic devices near the device (e.g., such as within 10 meters). The device 10 including a Wi-Fi or wireless local area networking modem is also capable of sending and / or receiving data to and from electronic devices according to various wireless networking technologies (including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN technologies such as IEEE 802.11 technology, IEEE 802.15 technology, IEEE 802.16 technology, etc.).

[0066] The device 10 may include a memory (such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, a UICC, etc.) that may store information elements related to a mobile subscriber. In addition to the SIM, the device 10 may include other removable and / or fixed memory. The device 10 may include a volatile memory 40 and / or a non-volatile memory 42. For example, the volatile memory 40 may include a random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, etc. The non-volatile memory 42, which may be embedded and / or removable, may include, for example, a read-only memory, flash memory, a magnetic storage device such as a hard disk, a floppy disk drive, a tape, an optical drive and / or a medium, a non-volatile random access memory (NVRAM), etc. Similar to the volatile memory 40, the non-volatile memory 42 may include a cache area for temporarily storing data. At least a portion of the volatile and / or non-volatile memory may be embedded in the processor 20. The memory may store one or more software programs, instructions, pieces of information, data, etc., which may be used by the apparatus to perform operations disclosed herein, such as receiving a first user equipment capability identifier associated with a first restart counter value indicating a restart of a user equipment capability management function; 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 at least one user equipment capability. Alternatively or additionally, the apparatus may be configured to cause operations disclosed herein with respect to a base station / WLAN access point and a network node including a UE.

[0067] The memory may include an identifier capable of uniquely identifying the apparatus 10, such as an International Mobile Equipment Identity (IMEI) code. The memory may include an identifier capable of uniquely identifying the device 10, such as an International Mobile Equipment Identity (IMEI) code. In an example embodiment, the processor 20 may be configured using computer code stored in the memory 40 and / or 42 to provide operations disclosed herein with respect to the UE, such as receiving a first user equipment capability identifier associated with a first restart counter value indicating a restart of a user equipment capability management function; 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 at least one user equipment capability.

[0068] Some embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside, for example, on the memory 40, the control device 20, or an electronic component. In some example 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" may be any non-transitory medium that is capable of containing, storing, communicating, propagating, or transmitting instructions for use by or in connection with an instruction execution system, apparatus, or device (such as a computer or data processor circuit), in Figure 6 In the example shown, computer-readable media may include non-transitory computer-readable storage media, which may be any media that can contain or store instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0069] Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein may be improved signaling.

[0070] Depending on the desired configuration, the subject matter described herein may be implemented in a system, apparatus, method, and / or article. For example, a base station and user equipment (or one or more components thereof) and / or the processes described herein may be implemented using one or more of the following operations: 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 executable and / or interpretable on a programmable system, the programmable system including at least one programmable processor, which may be dedicated or general purpose, coupled to receive data and instructions from a storage system, at least one input device, and at least one output device and to send data and instructions thereto. These computer programs (also referred to as programs, software, software applications, applications, components, program codes, or codes) include machine instructions for programmable processors and may be implemented in high-level procedural and / or object-oriented programming languages ​​and / or in assembly / machine languages. As used herein, the term "computer-readable medium" refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions. Similarly, systems that may include a processor and a memory coupled to the processor are also described herein. The memory may include one or more programs that cause the processor to perform one or more operations described herein.

[0071] Although some variations have been described in detail above, other modifications or additions are possible. In particular, in addition to the features and / or variations set forth herein, other features and / or variations may also be provided. Furthermore, the above implementations may be directed to various combinations and subcombinations of the disclosed features and / or combinations and subcombinations of several other features disclosed above. Other embodiments are within the scope of the following claims.

[0072] If desired, the different functions discussed herein may be performed in different orders and / or simultaneously with each other. In addition, if desired, one or more of the above functions may be optional or may be combined. Although various aspects of some embodiments are stated in the independent claims, other aspects of some embodiments include other combinations of features from the described embodiments and / or dependent claims with features of the independent claims, rather than just the combinations explicitly stated in the claims. It should also be noted herein that although exemplary embodiments are described above, these descriptions should not be considered to have a limiting meaning. On the contrary, several changes and modifications may be made without departing from the scope of some embodiments defined in the appended claims. Other embodiments are within the scope of the following claims. The term "based on" includes "at least based on". Unless otherwise specified, the use of "for example" means "such as for example".

Claims

1. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to at least: receiving a message from a user equipment capability management function UCMF, the message comprising an indicator, wherein the indicator is associated with a user equipment capability identifier UE capability ID, and wherein the indicator has a first indicator value, the first indicator value indicating a current user equipment capability identifier UE capability ID and being a current indicator value different from a second indicator value, the second indicator value indicating an outdated user equipment capability identifier UE capability ID; In response to receiving the first indicator value and comparing the first indicator value with the second indicator value, prohibiting use of the obsolete user equipment capability identifier UE capability ID associated with the second indicator value; as well as A message including the current user equipment capability identifier UE capability ID is sent to a radio access network RAN. 2 . The apparatus of claim 1 , wherein the apparatus is further caused to store at least the first indicator value.

3. An apparatus according to any one of claims 1 to 2, wherein the apparatus is further configured to at least: compare the second indicator value with the first indicator value to determine whether the second indicator value matches the first indicator value when the apparatus receives a registration request including the outdated user equipment capability identifier UE capability ID associated with the second indicator value, and / or when checking one or more user equipment capability identifiers UE capability IDs stored for registered user equipment.

4. The apparatus according to any one of claims 1 to 2, wherein the apparatus is further configured to at least: send a message to the radio access network RAN ​​to trigger acquisition of user equipment capability information for a user equipment UE. 5 . The apparatus of claim 4 , wherein the message is sent when the apparatus does not include a user equipment capability identifier (UE capability ID) associated with the second indicator value in its cache.

6. An apparatus according to any one of claims 1 to 2, wherein the apparatus is further configured to at least: assign to a user equipment UE the current user equipment capability identifier UE capability ID associated with user equipment capability information including at least one radio capability, wherein the current user equipment capability identifier UE capability ID is associated with the first indicator value.

7. The apparatus according to claim 6, wherein the assigned current user equipment capability identifier UE capability ID is sent to the user equipment UE in the following items: a registration accept message, a configuration update message, a globally unique temporary identifier reallocation command message, or another non-access layer signaling message.

8. An apparatus according to any one of claims 1 to 2, wherein the apparatus is further caused to at least: send the current user equipment capability identifier UE capability ID and / or the first indicator value to the radio access network RAN ​​so that the radio access network RAN ​​can prohibit the use of the obsolete user equipment capability identifier UE capability ID associated with the second indicator value, and / or the apparatus is further caused to at least: store the current user equipment capability identifier UE capability ID associated with the first indicator value.

9. The apparatus according to claim 8, wherein the apparatus is further caused to at least: send the current user equipment capability identifier UE capability ID and / or the first indicator value to the radio access network RAN ​​via an N2 interface or an S1 interface message.

10. The apparatus according to any one of claims 1 to 2, wherein the apparatus is further configured to at least: send context information towards one or more user equipments UE, the context information comprising the obsolete user equipment capability identifier UE capability ID associated with the second indicator value.

11. The apparatus according to any one of claims 1 to 2, wherein the first indicator value is sent towards the radio access network RAN.

12. An apparatus according to any one of claims 1 to 2, wherein the apparatus is included in a core network node, an access and mobility management function AMF and / or a mobility management entity, or includes the core network node, the access and mobility management function AMF and / or the mobility management entity.

13. An apparatus for communication, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to at least: receiving a message, the message comprising a user equipment capability identifier UE capability ID, wherein the user equipment capability identifier UE capability ID is associated with an indicator, and wherein the indicator has a first indicator value, the first indicator value indicating a current user equipment capability identifier UE capability ID and being a current indicator value different from a second indicator value, the second indicator value indicating an outdated user equipment capability identifier UE capability ID; as well as The current user equipment capability identifier UE capability ID is stored in association with user equipment capability information UE capability information, wherein the user equipment capability information UE capability information includes at least one radio capability.

14. The apparatus according to claim 13, wherein the apparatus is further caused to at least: send a registration request to a core network via a radio access network RAN, the registration request comprising the current user equipment capability identifier UE capability ID associated with the first indicator value.

15. The apparatus according to claim 14, wherein the apparatus is further caused to at least: in response to the received user equipment capability identifier UE capability ID, prohibit the use of the obsolete user equipment capability identifier UE capability ID associated with the second indicator value.

16. The apparatus according to claim 15, wherein prohibiting the use of the obsolete user equipment capability identifier UE capability ID comprises: The outdated user equipment capability identifier UE capability ID is deleted.

17. An apparatus according to any one of claims 13 to 16, wherein the apparatus is further configured to at least: cache the outdated user equipment capability identifier UE capability ID associated with the second indicator value after receiving the user equipment capability identifier UE capability ID, the cache including corresponding user equipment capability information.

18. The apparatus according to any one of claims 13 to 16, wherein the user equipment capability identifier UE capability ID is received via: a registration accept message, or a configuration update message, or a globally unique temporary identifier reallocation command message, or another non-access stratum signaling message.

19. The apparatus according to any one of claims 13 to 16, wherein the current user equipment capability identifier UE capability ID is sent to a radio access network RAN.

20. The apparatus according to any one of claims 13 to 16, wherein the apparatus is included in or includes a user equipment UE.

21. A method of communication, comprising: receiving a message from a user equipment capability management function UCMF, the message comprising an indicator, wherein the indicator is associated with a user equipment capability identifier UE capability ID, and wherein the indicator has a first indicator value, the first indicator value indicating a current user equipment capability identifier UE capability ID and being a current indicator value different from a second indicator value, the second indicator value indicating an outdated user equipment capability identifier UE capability ID; In response to receiving the first indicator value and comparing the first indicator value with the second indicator value, prohibiting use of the obsolete user equipment capability identifier UE capability ID associated with the second indicator value; as well as A message including the current user equipment capability identifier UE capability ID is sent to a radio access network RAN.

22. The method according to claim 21, further comprising: The first indicator value is stored.

23. The method according to any one of claims 21 to 22, further comprising: When a registration request including the outdated user equipment capability identifier UE capability ID associated with the second indicator value is received, and / or when checking against one or more user equipment capability identifiers UE capability IDs stored for registered user equipment UE, the second indicator value is compared with the first indicator value to determine whether the second indicator value matches the first indicator value.

24. The method according to any one of claims 21 to 22, further comprising: A message is sent to the radio access network RAN ​​to trigger the acquisition of user equipment capability information for the user equipment UE.

25. The method of claim 24, wherein the message is sent when the cache does not include a user equipment capability identifier (UE capability ID) associated with the second indicator value.

26. The method according to any one of claims 21 to 22, further comprising: The current user equipment capability identifier UE capability ID associated with user equipment capability information including at least one radio capability is assigned to the user equipment UE, wherein the current user equipment capability identifier UE capability ID is associated with the first indicator value.

27. The method according to claim 26, wherein the assigned current user equipment capability identifier UE capability ID is sent to the user equipment UE in the following items: a registration accept message, or a configuration update message, or a globally unique temporary identifier reallocation command message, or another non-access layer signaling message.

28. The method according to any one of claims 21 to 22, further comprising: sending the current user equipment capability identifier UE capability ID and / or the first indicator value to the radio access network RAN ​​so that the radio access network RAN ​​can prohibit use of the obsolete user equipment capability identifier UE capability ID associated with the second indicator value and / or store the current user equipment capability identifier UE capability ID associated with the first indicator value.

29. The method according to claim 28, further comprising: The current user equipment capability identifier UE capability ID and / or the first indicator value are sent to the radio access network RAN ​​via an N2 interface or an S1 interface message.

30. The method according to any one of claims 21 to 22, further comprising: Context information is sent towards one or more user equipments UE, the context information comprising the obsolete user equipment capability identifier UE capability ID associated with the second indicator value.

31. The method according to any of claims 21 to 22, wherein the first indicator value is sent towards the Radio Access Network, RAN.

32. A method of communication, comprising: receiving a message, the message comprising a user equipment capability identifier UE capability ID, wherein the user equipment capability identifier UE capability ID is associated with an indicator, and wherein the indicator has a first indicator value, the first indicator value indicating a current user equipment capability identifier UE capability ID and being a current indicator value different from a second indicator value, the second indicator value indicating an outdated user equipment capability identifier UE capability ID; as well as The current user equipment capability identifier UE capability ID is stored in association with user equipment capability information UE capability information, wherein the user equipment capability information UE capability information includes at least one radio capability.

33. The method of claim 32, further comprising: A registration request is sent to a core network via a radio access network RAN, the registration request including the current user equipment capability identifier UE capability ID associated with the first indicator value.

34. The method of claim 33, further comprising: In response to the received user equipment capability identifier UE capability ID, use of the obsolete user equipment capability identifier UE capability ID associated with the second indicator value is prohibited.

35. The method according to claim 34, wherein prohibiting the use of the obsolete user equipment capability identifier UE capability ID comprises: The outdated user equipment capability identifier UE capability ID is deleted.

36. The method according to any one of claims 32 to 35, further comprising: After receiving the user equipment capability identifier UE capability ID, the outdated user equipment capability identifier UE capability ID associated with the second indicator value is cached, the cache comprising corresponding user equipment capability information.

37. The method according to any one of claims 32 to 35, wherein the user equipment capability identifier UE capability ID is received via: a registration accept message, or a configuration update message, or a globally unique temporary identifier reallocation command message, or another non-access stratum signaling message.

38. The method according to any one of claims 32 to 35, wherein the current user equipment capability identifier UE capability ID is sent to a radio access network RAN.

39. An apparatus for communication, comprising: means for receiving a message from a user equipment capability management function UCMF, the message comprising an indicator, wherein the indicator is associated with a user equipment capability identifier, UE capability ID, and wherein the indicator has a first indicator value, the first indicator value indicating a current user equipment capability identifier, UE capability ID, and being a current indicator value different from a second indicator value, the second indicator value indicating an outdated user equipment capability identifier, UE capability ID; means for inhibiting use of the obsolete user equipment capability identifier, UE capability ID, associated with the second indicator value in response to receiving the first indicator value and comparing the first indicator value with the second indicator value; as well as Means for sending a message comprising said current user equipment capability identifier UE capability ID to a radio access network RAN.

40. Apparatus according to claim 39, wherein the apparatus comprises means for performing any one of claims 21 to 30.

41. An apparatus for communication, comprising: means for receiving a message, the message comprising a user equipment capability identifier, UE capability ID, wherein the user equipment capability identifier, UE capability ID, is associated with an indicator, and wherein the indicator has a first indicator value, the first indicator value indicating a current user equipment capability identifier, UE capability ID, and being a current indicator value different from a second indicator value, the second indicator value indicating an outdated user equipment capability identifier, UE capability ID; as well as A means for storing the current user equipment capability identifier UE capability ID in association with user equipment capability information UE capability information, the user equipment capability information UE capability information comprising at least one radio capability.

42. Apparatus according to claim 41, wherein the apparatus comprises means for performing any one of claims 32 to 38.

43. A non-transitory computer readable storage medium comprising program code, the program code causing operations when executed, the operations comprising: receiving a message from a user equipment capability management function UCMF, the message comprising an indicator, wherein the indicator is associated with a user equipment capability identifier UE capability ID, and wherein the indicator has a first indicator value, the first indicator value indicating a current user equipment capability identifier UE capability ID and being a current indicator value different from a second indicator value, the second indicator value indicating an outdated user equipment capability identifier UE capability ID; In response to receiving the first indicator value and comparing the first indicator value with the second indicator value, prohibiting use of the obsolete user equipment capability identifier UE capability ID associated with the second indicator value; as well as A message including the current user equipment capability identifier UE capability ID is sent to a radio access network RAN.

44. A non-transitory computer readable storage medium comprising program code, the program code causing operations when executed, the operations comprising: receiving a message, the message comprising a user equipment capability identifier UE capability ID, wherein the user equipment capability identifier UE capability ID is associated with an indicator, and wherein the indicator has a first indicator value, the first indicator value indicating a current user equipment capability identifier UE capability ID and being a current indicator value different from a second indicator value, the second indicator value indicating an outdated user equipment capability identifier UE capability ID; as well as The current user equipment capability identifier UE capability ID is stored in association with user equipment capability information UE capability information, wherein the user equipment capability information UE capability information includes at least one radio capability.

Images