CN112369056A

CN112369056A - Apparatus and method operable to recover user equipment capability identity

Info

Publication number: CN112369056A
Application number: CN201980045328.6A
Authority: CN
Inventors: 林晖闵
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-02-19
Filing date: 2019-12-31
Publication date: 2021-02-12
Anticipated expiration: 2039-12-31
Also published as: CN112369056B; WO2020168834A1

Abstract

An apparatus and method operable to recover user equipment capability identities are provided, which can provide good communication performance and high reliability. A method operable to recover a user equipment capability identity of a user equipment comprises: receiving an indication from a network node, wherein the indication comprises: indicating whether a type of user equipment capability identity is to be used, and performing an indication, wherein performing an indication comprises: the user equipment uses the PLMN specific user equipment capability identity when the user equipment has a public land mobile network specific user equipment capability identity and a manufacturer specific user equipment capability identity.

Description

Apparatus and method operable to recover user equipment capability identity

Background of the disclosure

1. Field of the disclosure

The present disclosure relates to the field of communication systems, and more particularly, to an apparatus and method operable to recover User Equipment (UE) capability Identification (ID).

2. Description of the related Art

A Universal Terrestrial Radio Access Network (UTRAN) is a radio access network of a Universal Mobile Telecommunications System (UMTS), wherein the UTRAN consists of Radio Network Controllers (RNCs) and node base stations, i.e. radio base stations. The node base stations communicate wirelessly with the mobile terminals, and the radio network controller controls the node base stations. The radio network controller is also connected to a Core Network (CN). Evolved UTRAN (E-UTRAN) is an evolution of UTRAN towards a high data rate, low delay and packet optimized radio access network. Furthermore, the E-UTRAN consists of interconnected evolved node base stations that are also connected to an evolved packet core network (EPC). The E-UTRAN is also known as Long Term Evolution (LTE) and is standardized under the third Generation partnership project (3 GPP).

Different user equipment capabilities are specified in view of a wide range of user equipment implementations. The user equipment capabilities are divided into a number of parameters, which are transmitted from the user equipment at the connection set-up and when the user equipment capabilities change during the ongoing connection. The network may then use the user equipment capabilities to select the configuration supported by the user equipment.

In current systems, when registration or registration updates, the capabilities of the terminal are reported to the access network, which then sends the capabilities of the terminal to the core network for storage. When the terminal initiates a connection establishment request, the access network requests the capability information of the terminal from the core network, and then provides configuration for the terminal according to the capability information of the terminal.

As terminals support more and more features, the capability information of the terminals will become larger and larger, which will bring about a huge signaling overhead. In addition, the core network needs to store the capability information of all terminal registrations, which brings more challenges to the core network.

Therefore, there is a need for an apparatus and method operable to recover user equipment capability identities that can provide good communication performance and high reliability.

Disclosure of Invention

It is an object of the present disclosure to propose an apparatus and method operable to recover a user equipment capability identity, which is capable of providing good communication performance and high reliability.

In a first aspect of the disclosure, a user equipment operable to recover a user equipment capability identification includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to control the transceiver to receive an indication from the network node, wherein the indication comprises: indicating whether a type of user equipment capability identification is to be used, and the processor is configured to perform the indicating, wherein performing the indicating comprises: the user equipment uses a Public Land Mobile Network (PLMN) specific user equipment capability identity when the user equipment has both a PLMN specific user equipment capability identity and a manufacturer specific user equipment capability identity.

In a second aspect of the disclosure, a method operable to recover a user equipment capability identification of a user equipment, comprises: receiving an indication from a network node, wherein the indication comprises: indicating whether a type of user equipment capability identity is to be used, and performing an indication, wherein performing an indication comprises: the user equipment uses the PLMN specific user equipment capability identity when the user equipment has a public land mobile network specific user equipment capability identity and a manufacturer specific user equipment capability identity.

In a third aspect of the disclosure, a network node operable to recover user equipment capability identification includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to control the transceiver to transmit an indication to the user equipment, wherein the indication comprises: indicating whether a type of user equipment capability identification is to be used, and the processor is configured to request the user equipment to perform the indication, wherein performing the indication comprises: the processor requests the user equipment to use a Public Land Mobile Network (PLMN) specific user equipment capability identity when the user equipment has the PLMN specific user equipment capability identity and the manufacturer specific user equipment capability identity.

In a fourth aspect of the present disclosure, a method operable to recover user equipment capability identification of a network node, comprises: sending an indication to a user equipment, wherein the indication comprises: indicating whether a type of user equipment capability identity is to be used, and requesting the user equipment to perform the indication, wherein performing the indication comprises: when the user equipment has a Public Land Mobile Network (PLMN) specific user equipment capability identification and a manufacturer specific user equipment capability identification, the network node requests the user equipment to use the PLMN specific user equipment capability identification.

In a fifth aspect of the disclosure, a non-transitory machine-readable storage medium has instructions stored thereon, which when executed by a computer, cause the computer to perform the above-described method.

In a sixth aspect of the present disclosure, a terminal device includes: a processor and a memory configured to store a computer program. The processor is configured to execute a computer program stored in the memory to perform the above-described method.

In a seventh aspect of the disclosure, a network node comprises: a processor and a memory configured to store a computer program. The processor is configured to execute a computer program stored in the memory to perform the above-described method.

In an eighth aspect of the disclosure, a chip comprises a processor configured to invoke and run a computer program stored in a memory to cause a device in which the chip is installed to perform the above method.

In a ninth aspect of the present disclosure, a computer-readable storage medium has stored therein a computer program for causing a computer to execute the above method.

In a tenth aspect of the present disclosure, a computer program product comprises a computer program and the computer program causes a computer to perform the above method.

An eleventh aspect of the present disclosure is a computer program that causes a computer to execute the above method.

Brief Description of Drawings

In order to more clearly illustrate embodiments of the present disclosure or related art, the following drawings will be described in briefly introduced embodiments. It is apparent that the drawings are only some embodiments of the disclosure and that other drawings can be derived by those of ordinary skill in the art from these drawings without paying for them.

Fig. 1 is a user equipment and a network node operable to recover a user equipment capability identity according to an embodiment of the present disclosure.

Fig. 2 is a flow chart illustrating a method operable to recover a user equipment capability identification of a user equipment in accordance with an embodiment of the present disclosure.

Fig. 3 is a flow chart illustrating a method operable to recover a user equipment capability identification of a network node according to an embodiment of the present disclosure.

Fig. 4 is a schematic diagram of an exemplary illustration of a deletion execution procedure of a user equipment capability identification according to an embodiment of the disclosure.

Fig. 5 is a block diagram of a wireless communication system in accordance with an embodiment of the present disclosure.

Detailed description of the embodiments

Embodiments of the present disclosure are described in detail below with reference to the accompanying drawings by technical subject matter, structural features, attained objects, and effects. In particular, the terminology used in the embodiments of the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure.

In some embodiments, some form of active signalling of the user equipment radio capability will be investigated, which may also rely on an active representation of the user equipment capability. In some embodiments, the solution may take into account that the device may have certain features upgraded, for example due to a new Software (SW) version or the disabling of certain wireless capabilities. Some alternatives to this efficient representation are as follows: 1. using a hash function over the user equipment capabilities; 2. identifying a component or all components of a software version (IMEI SV), i.e., a model approval number (TAC) and a Software Version Number (SVN), using an international mobile equipment; and 3. use the newly defined identifier. In some embodiments, there are two types of user equipment capability identities to represent user equipment wireless capabilities: a Public Land Mobile Network (PLMN) specific user equipment capability identity and a manufacturer specific user equipment capability identity. Some embodiments of the present disclosure address the problem of how a user equipment determines to use a PLMN-specific capability identity or a manufacturer-specific capability identity.

Fig. 1 illustrates that in some embodiments, a user equipment 10 and a network node 20 operable to recover a user equipment capability identity are provided according to embodiments of the present disclosure. The user equipment 10 may comprise a processor 11, a memory 12 and a transceiver 13. The network node 20 may comprise a processor 21, a memory 22 and a transceiver 23. The

processor

11 or 21 may be configured to implement the proposed functions, processes and/or methods described in this specification. The radio interface protocol layer may be implemented in the

processor

11 or 21. The memory 12 or 22 is operatively coupled with the

processor

11 or 21 and stores various information to operate the

processor

11 or 21. The

transceiver

13 or 23 is operatively coupled with the

processor

11 or 21, and the

transceiver

13 or 23 transmits and/or receives wireless signals.

The

processor

11 or 21 may comprise an Application Specific Integrated Circuit (ASIC), other chipset, logic circuit and/or data processing device. The memory 12 or 22 may include Read Only Memory (ROM), Random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. The

transceiver

13 or 23 may include a baseband circuit to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. These modules may be stored in memory 12 or 22 and executed by

processor

11 or 21. The memory 12 or 22 may be implemented within the

processor

11 or 21 or external to the

processor

11 or 21, in which case the memory 12 or 22 may be communicatively coupled to the

processor

11 or 21 via various means as is known in the art.

A solution of the disclosed embodiments is to propose an apparatus and method operable to recover a user equipment capability identity, which can provide good communication performance and high reliability.

Depending on which layer of the protocol hierarchy a given capability information relates to, the user equipment capabilities may be divided into two main groups of capability categories: access Stratum (AS) capabilities and non-access stratum (NAS) capabilities.

Access Stratum (AS) capabilities: these capabilities are access technology related parts of the capability information, such as terminal power class, supported frequency bands, etc. The eNodeB requires AS capabilities.

Non-access stratum (NAS) capability: the set of capability information holds non-access specific parts of the user equipment capabilities, e.g. supported security algorithms. The evolved packet core network (EPC) uses NAS capabilities.

In some embodiments, the processor 11 is configured to control the transceiver 13 to receive an indication from the network node 20, wherein the indication comprises: indicating whether a type of user equipment capability identity is to be used, and the processor 11 is configured to perform the indicating, wherein performing the indicating comprises: the PLMN specific user equipment capability identity is used by the user equipment 10 when the user equipment 10 has a Public Land Mobile Network (PLMN) specific user equipment capability identity and a manufacturer specific user equipment capability identity. Furthermore, in some embodiments, the user equipment 10 indicates a PLMN-specific user equipment capability identification to the network node 20.

In some embodiments, when the processor 11 enters a state where no valid user data is available at the user equipment 10, the processor 11 deletes the PLMN specific capability identification. Specifically, the state is a 5GS mobility management-deregistered.no subscriber permanent identity (5 GMM-registered. no-SUPI) state.

In some embodiments, the main functions of the 5GS mobility management (5GMM) sublayer are to support identification, security, mobility and general message transport for user equipment. Another function of the 5GMM sublayer is to provide connection management services to other sublayers. In the 5GS mobility management-DEREGISTERED (5GMM-DEREGISTERED) state, no 5GMM context is established and the network node is not aware of the location of the user equipment and is therefore not reachable by the network node. To establish a 5GMM context, the user equipment needs to initiate an initial registration procedure. The 5GMM-DEREGISTERED state is subdivided into a plurality of sub-states. The following sub-states are not applicable for non-3 GPP access: a)5GS mobility management-deregistered limited SERVICE (5 GMM-deregistered.limimed-SERVICE), b)5GS mobility management-deregistered.plmn SEARCH (5GMM-deregistered.plmn-SEARCH), c)5GMM-deregistered.no-SUPI, d)5GS mobility management-deregistered.no-CELL-AVAILABLE, and e)5GS mobility management-deregistered.emergency call INACTIVE (5 GMM-deregistered.allec-INACTIVE). Valid user data is available to the user equipment except for the 5 gmmderegsertised no-SUPI substate before the user equipment enters the substate. The 5 GMM-registered no-SUPI substate is selected in the user equipment if the user equipment has no available valid user data (subscriber identity module (SIM)/Universal Subscriber Identity Module (USIM) is not available, SIM/USIM is considered invalid by the user equipment) and a cell has been selected. no-SUPI substate is not applicable to non-3 GPP access.

In some embodiments, the processor 11 deletes the PLMN specific capability identity when the processor 11 detects that a Universal Subscriber Identity Module (USIM) is removed from the user equipment. In some embodiments, the processor 11 deletes the PLMN-specific capability identity when the processor 11 detects that a new USIM is inserted into the user equipment 10, and the processor 11 indicates the manufacturer-specific user equipment capability identity to the network node 20 when the processor 11 registers with the network node 20. In some embodiments, when the processor 11 detects that the same USIM is removed from the user equipment 10 and reinserted into the user equipment 10, the processor 11 deletes the PLMN specific capability identification, and when the processor 11 registers with the network node 20, the processor 11 indicates the manufacturer specific user equipment capability identification to the network node 20.

In some embodiments, if the processor 11 roams to a different PLMN, when the processor 11 registers with the network node 20, the processor 11 indicates the manufacturer specific user equipment capability identification to the network node 20 and the processor 11 deletes or maintains the PLMN specific capability identification stored in the user equipment 10. In some embodiments, if the user equipment 10 reverts to the previous PLMN, the processor 11 uses the PLMN specific capability identification if the manufacturer specific user equipment capability identification is maintained or used. In some embodiments, the indication comprises type information of the user equipment capability identification (the type information of the user equipment capability identification comprises at least one of a PLMN specific user equipment capability identification, a manufacturer specific user equipment capability identification), deleting the PLMN specific user equipment capability identification, deleting the manufacturer specific user equipment capability identification, ignoring the PLMN specific user equipment capability identification, and reusing the PLMN specific user equipment capability identification. In some embodiments, the indication is provided by radio resource control signaling or non-access stratum signaling.

In some embodiments, the processor 11 is configured to control the transceiver 13 to receive a NAS message from a core network entity of the network node 20, and the NAS message comprises a user equipment configuration update (UCU) associated with the user equipment capability identity invalidation or deletion.

In some embodiments, the UCU includes using 1 bit to indicate that the user equipment is invalid or deleted for all user equipment capability identities stored by the PLMN. In some embodiments, the UCU includes a flag indicating which user device capability identifier stored by the user device is invalid or deleted. In some embodiments, the UCU includes a flag indicating that the user equipment capability identification in a specific area is invalid or deleted, and the specific area is a specific registration area, a Tracking Area (TA) list, or a geographical area.

In some embodiments, the processor 11 is configured to initiate an initial NAS message comprising the user equipment capability identification. In some embodiments, the initial NAS message comprises a registration request message or a service request message. In some embodiments, the processor 11 is configured to control the transceiver 13 to receive a response message from the core network entity in response to the initial NAS message, and the response message comprises the user equipment capability identity invalid or deleted. In some embodiments, the processor 21 is configured to control the transceiver 23 to transmit an indication to the user equipment 10, wherein the indication comprises: indicating whether a type of user equipment capability identity is to be used, and the processor 21 is configured to request the user equipment 10 to perform the indication, wherein performing the indication comprises: when the user equipment 10 has a Public Land Mobile Network (PLMN) specific user equipment capability identity and a manufacturer specific user equipment capability identity, the processor 21 requests the user equipment to use the PLMN specific user equipment capability identity. Furthermore, in some embodiments, the processor 21 requests the user equipment 10 to indicate a PLMN-specific user equipment capability identification to the network node 20.

In some embodiments, the processor 21 requests the user equipment 10 to delete the PLMN specific capability identification when the user equipment 10 enters a state in which no valid user data is available for the user equipment 10. Specifically, the state is a 5 GMM-registered no-SUPI state. In some embodiments, the processor 21 requests the user equipment 10 to delete the PLMN specific capability identity when the user equipment 10 detects that a Universal Subscriber Identity Module (USIM) is removed from the user equipment 10. In some embodiments, the processor 21 requests the user equipment 10 to delete the PLMN specific capability identity when the user equipment 10 detects that a new USIM is inserted into the user equipment 10, and the processor 21 requests the user equipment 10 to indicate the manufacturer specific user equipment capability identity to the network node 20 when the user equipment 10 registers with the network node 20. In some embodiments, the processor 21 requests the user equipment 10 to delete the PLMN-specific capability identity when the user equipment 10 detects that the same universal subscriber identity module USIM is removed from the user equipment 10 and inserted into the user equipment 10 again, and the processor 21 requests the user equipment 10 to indicate the manufacturer-specific user equipment capability identity to the network node 20 when the user equipment 10 registers with the network node 20.

In some embodiments, if the user equipment 10 roams to a different PLMN, when the user equipment 10 registers with the network node 20, the processor 21 requests the user equipment 10 to indicate the manufacturer specific user equipment capability identity to the network node 20 and the processor 21 requests the user equipment 10 to delete or maintain the PLMN specific capability identity stored in the user equipment 10. In some embodiments, if the user equipment 10 reverts to the previous PLMN, the processor 21 requests the user equipment 10 to use the PLMN specific capability identification if the manufacturer specific user equipment capability identification is maintained or used. In some embodiments, the indication comprises type information of the user equipment capability identification (the type information of the user equipment capability identification comprises at least one of a PLMN specific user equipment capability identification, a manufacturer specific user equipment capability identification), deleting the PLMN specific user equipment capability identification, deleting the manufacturer specific user equipment capability identification, ignoring the PLMN specific user equipment capability identification, and reusing the PLMN specific user equipment capability identification. In some embodiments, the indication is provided by radio resource control signaling or non-access stratum signaling.

In some embodiments, the network node 20 comprises a user equipment capability management function (UCMF) entity and a Core Network (CN) entity, the core network entity and the UCMF entity having a direct or indirect connection. In some embodiments, the UCMF entity is configured to detect that the user equipment capability identity is invalid or cleared, and to send a notification message to notify the core network entity of a condition associated with the user equipment capability identity being invalid or cleared. In some embodiments, the invalid or purged user equipment capability identity is an identity for a particular user equipment, one, some or all user equipments belonging to a particular PLMN, or for one, some or all user equipments belonging to a particular user equipment manufacturer, or if the user equipment has multiple identities, the invalid or purged user equipment capability identity has one or some identities.

In some embodiments, if the core network entity already stores the invalid or removed user equipment capability identity, the core network entity deletes the invalid or removed user equipment capability identity and information associated with the invalid or removed user equipment capability identity. In some embodiments, if the core network entity does not have a valid identity for a particular user equipment or set of capabilities, the core network entity fails to retrieve an invalid or purged user equipment capability identity and/or capabilities thereof from the UCMF entity. In some embodiments, the core network entity is configured to notify the user equipment of a NAS message comprising a user equipment configuration update (UCU) associated with the user equipment capability identity being invalid or deleted.

In some embodiments, the UCU includes using 1 bit to indicate that the user equipment is invalid or deleted for all user equipment capability identities stored by the PLMN. In some embodiments, the UCU includes a flag indicating which user device capability identifier stored by the user device is invalid or deleted. In some embodiments, the UCU includes a flag indicating that the user equipment capability identification in a specific area is invalid or deleted, and the specific area is a specific registration area, a Tracking Area (TA) list, or a geographical area. In some embodiments, the processor 21 is configured to receive an initial NAS message from the user equipment 10 comprising an identification of user equipment capabilities. In some embodiments, the initial NAS message comprises a registration request message or a service request message. In some embodiments, the core network entity cannot understand the user equipment capability identity, has no capability information related to the user equipment capability identity, or can not retrieve the user equipment capability identity and/or the capability information related to the user equipment capability identity from the UCMF entity.

In some embodiments, the core network entity is configured to notify the user equipment 10 of a response message in response to the initial NAS message, and the response message includes the user equipment capability identity invalid or deleted. In some embodiments, the core network entity is configured to inform the radio access network entity of the network node that no user equipment capability identity or a capability related to the user equipment capability identity is available, or to inform the radio access network entity of the network node of an indication to delete the user equipment capability identity if the radio access network entity stores the user equipment capability identity; or the core network entity is configured to send a message to the access network entity without the user equipment capability identity and/or the capabilities related to the user equipment capability identity. In some embodiments, the access network entity is configured to retrieve the user equipment capability identification from the user equipment 10 using a radio resource control message or a NAS message.

In some embodiments, after the access network entity retrieves the user equipment capability identification from the user equipment using a radio resource control message or a NAS message, the user equipment deletes the user equipment capability identification, or if there is no user equipment capability identification, the user equipment 10 deletes all identifications associated with the PLMN. In some embodiments, the radio access network entity is configured to receive user equipment capability information from the user equipment, wherein the user equipment capability information comprises a user equipment capability identity and/or other type of user equipment capability identity different from the user equipment capability identity.

In some embodiments, the radio access network entity is configured to inform the core network entity of the user equipment capability information. In some embodiments, the core network entity is configured to store user equipment capability information. In some embodiments, the core network entity is configured to inform the UCMF entity of user equipment capability information.

Fig. 2 illustrates a method 200 operable to recover a user equipment capability identification of a user equipment in accordance with an embodiment of the present disclosure. The method 200 comprises the following steps: block 202, receiving an indication from a network node, wherein the indication comprises: indicating whether a type of user equipment capability identification is to be used, and block 204, performing the indication, wherein performing the indication comprises: the user equipment uses a Public Land Mobile Network (PLMN) specific user equipment capability identity when the user equipment has both a PLMN specific user equipment capability identity and a manufacturer specific user equipment capability identity.

In some embodiments, the user equipment deletes the PLMN specific capability identity when the user equipment enters a state in which no valid user data is available to the user equipment. Specifically, the state is a 5 GMM-registered no-SUPI state. In some embodiments, the user equipment deletes the PLMN-specific capability identity when the user equipment detects that a Universal Subscriber Identity Module (USIM) is removed from the user equipment. In some embodiments, the user equipment deletes the PLMN-specific capability identity when the user equipment detects that a new USIM is inserted into the user equipment, and indicates the manufacturer-specific user equipment capability identity to the network node when the user equipment registers with the network node. In some embodiments, the user equipment deletes the PLMN-specific capability identity when the user equipment detects that the same USIM is removed from the user equipment and reinserted into the user equipment, and the user equipment indicates the manufacturer-specific user equipment capability identity to the network node when the user equipment registers with the network node.

In some embodiments, if the user equipment roams to a different PLMN, the user equipment indicates the manufacturer specific user equipment capability identity to the network node when the user equipment registers with the network node, and the user equipment deletes or maintains the PLMN specific capability identity stored in the user equipment. In some embodiments, if the user equipment returns to the previous PLMN, the user equipment uses the PLMN specific capability identity if the manufacturer specific user equipment capability identity is maintained or used. In some embodiments, the indication comprises type information of the user equipment capability identification (the type information of the user equipment capability identification comprises at least one of a PLMN specific user equipment capability identification, a manufacturer specific user equipment capability identification), deleting the PLMN specific user equipment capability identification, deleting the manufacturer specific user equipment capability identification, ignoring the PLMN specific user equipment capability identification, and reusing the PLMN specific user equipment capability identification. In some embodiments, the indication is provided by radio resource control signaling or non-access stratum signaling.

In some embodiments, the method further comprises: a NAS message is received from a core network entity of a network node, and the NAS message includes a user equipment configuration update (UCU) associated with a user equipment capability identity invalidation or deletion. In some embodiments, the UCU includes using 1 bit to indicate that the user equipment is invalid or deleted for all user equipment capability identities stored by the PLMN. In some embodiments, the UCU includes a flag indicating which user device capability identifier stored by the user device is invalid or deleted. In some embodiments, the UCU includes a flag indicating that the user equipment capability identification in a specific area is invalid or deleted, and the specific area is a specific registration area, a Tracking Area (TA) list, or a geographical area. In some embodiments, the method further comprises: an initial NAS message is initiated that includes an identification of user equipment capabilities.

In some embodiments, the initial NAS message comprises a registration request message or a service request message. In some embodiments, the method further comprises: a response message is received from the core network entity in response to the initial NAS message, and the response message includes the user equipment capability identity invalid or deleted.

Fig. 3 illustrates a method 300 operable to recover user equipment capability identification of a network node according to an embodiment of the present disclosure. The method 300 includes: block 302, an indication is sent to a user equipment, wherein the indication comprises: indicating whether a type of user equipment capability identification is to be used, and block 304 requesting the user equipment to perform the indication, wherein performing the indication comprises: when the user equipment has a Public Land Mobile Network (PLMN) specific user equipment capability identification and a manufacturer specific user equipment capability identification, the network node requests the user equipment to use the PLMN specific user equipment capability identification.

In some embodiments, the network node requests the user equipment to delete the PLMN-specific capability identity when the user equipment enters a state in which no valid user data is available for the user equipment. Specifically, the state is a 5 GMM-registered no-SUPI state. In some embodiments, the network node requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that a Universal Subscriber Identity Module (USIM) is removed from the user equipment. In some embodiments, the network node requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that a new universal subscriber identity module USIM is inserted into the user equipment, and the network node requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node when the user equipment registers with the network node. In some embodiments, the network node requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that the same universal subscriber identity module USIM is removed from the user equipment and inserted into the user equipment again, and the network node requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node when the user equipment registers with the network node.

In some embodiments, if the user equipment roams to a different PLMN, when the user equipment registers with the network node, the network node requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node, and the network node requests the user equipment to delete or maintain the PLMN-specific capability identity stored in the user equipment. In some embodiments, if the user equipment returns to the previous PLMN, the network node requests the user equipment to use the PLMN specific capability identity if the manufacturer specific user equipment capability identity is maintained or used. In some embodiments, the indication comprises type information of the user equipment capability identification (the type information of the user equipment capability identification comprises at least one of a PLMN specific user equipment capability identification, a manufacturer specific user equipment capability identification), deleting the PLMN specific user equipment capability identification, deleting the manufacturer specific user equipment capability identification, ignoring the PLMN specific user equipment capability identification, and reusing the PLMN specific user equipment capability identification. In some embodiments, the indication is provided by radio resource control signaling or non-access stratum signaling.

In some embodiments, the network node comprises a user equipment capability management function (UCMF) entity and a Core Network (CN) entity, the core network entity and the UCMF entity having a direct or indirect connection. In some embodiments, the UCMF entity is configured to detect that the user equipment capability identity is invalid or cleared, and to send a notification message to notify the core network entity of a condition associated with the user equipment capability identity being invalid or cleared. In some embodiments, the invalid or purged user equipment capability identity is an identity for a particular user equipment, one, some or all user equipments belonging to a particular PLMN, or for one, some or all user equipments belonging to a particular user equipment manufacturer, or if the user equipment has multiple identities, the invalid or purged user equipment capability identity has one or some identities. In some embodiments, if the core network entity already stores the invalid or removed user equipment capability identity, the core network entity deletes the invalid or removed user equipment capability identity and information associated with the invalid or removed user equipment capability identity. In some embodiments, if the core network entity does not have a valid identity for a particular user equipment or set of capabilities, the core network entity fails to retrieve an invalid or purged user equipment capability identity and/or capabilities thereof from the UCMF entity.

In some embodiments, the core network entity is configured to notify the user equipment of a NAS message comprising a user equipment configuration update (UCU) associated with the user equipment capability identity being invalid or deleted. In some embodiments, the UCU includes using 1 bit to indicate that the user equipment is invalid or deleted for all user equipment capability identities stored by the PLMN. In some embodiments, the UCU includes a flag indicating which user device capability identifier stored by the user device is invalid or deleted. In some embodiments, the UCU includes a flag indicating that the user equipment capability identification in a specific area is invalid or deleted, and the specific area is a specific registration area, a Tracking Area (TA) list, or a geographical area.

In some embodiments, the method further comprises: an initial NAS message is received from a user equipment including an identification of user equipment capabilities. In some embodiments, the initial NAS message comprises a registration request message or a service request message. In some embodiments, the core network entity cannot understand the user equipment capability identity, has no capability information related to the user equipment capability identity, or can not retrieve the user equipment capability identity and/or the capability information related to the user equipment capability identity from the UCMF entity. In some embodiments, the core network entity is configured to notify the user equipment of a response message in response to the initial NAS message, and the response message includes the user equipment capability identity invalid or deleted.

In some embodiments, the core network entity is configured to inform the radio access network entity of the network node that no user equipment capability identity or a capability related to the user equipment capability identity is available, or to inform the radio access network entity of the network node of an indication to delete the user equipment capability identity if the radio access network entity stores the user equipment capability identity; or the core network entity is configured to send a message to the access network entity without the user equipment capability identity and/or the capabilities related to the user equipment capability identity. In some embodiments, the access network entity is configured to retrieve the user equipment capability identification from the user equipment using a radio resource control message or a NAS message. In some embodiments, the user equipment deletes the user equipment capability identification after the access network entity retrieves the user equipment capability identification from the user equipment using the radio resource control message or the NAS message, or deletes all identifications associated with the PLMN if there is no user equipment capability identification.

In some embodiments, the radio access network entity is configured to receive user equipment capability information from the user equipment, wherein the user equipment capability information comprises a user equipment capability identity and/or other type of user equipment capability identity different from the user equipment capability identity. In some embodiments, the radio access network entity is configured to inform the core network entity of the user equipment capability information. In some embodiments, the core network entity is configured to store user equipment capability information. In some embodiments, the core network entity is configured to inform the UCMF entity of user equipment capability information.

Fig. 4 shows an exemplary illustration of a deletion execution procedure of a user equipment capability identification according to an embodiment of the present disclosure. The embodiment of the disclosure provides that the terminal is instructed to delete the allocated capability identification information through NAS signaling or RRC signaling. The NAS signaling includes a registration procedure and a terminal configuration update procedure. The RRC signaling includes a terminal capability acquisition reconfiguration procedure.

In some embodiments, the improved method is to match specific terminal capability information with the capability identification, and only save the capability identification information of the terminal when the terminal reports and the network saves the terminal capability. In certain cases, the network deletes the capability identification information of the terminal locally, e.g. the network is implemented locally or the network fails. In this case, the network needs to inform the terminal to delete the assigned capability identifier.

In some embodiments, the network may indicate to the user equipment whether the identified type will be used. The detailed indication may be: 1) type information, such as a PLMN-specific capability identity or a manufacturer-specific capability identity, 2) delete the PLMN-specific capability identity, 3) delete the manufacturer-specific capability identity, 4) ignore the PLMN-specific capability identity, and/or reuse the PLMN-specific identity. The indication may be provided to the user equipment by radio resource control signaling or NAS signaling.

In some embodiments, the detailed process is as follows. The following are the steps of three alternatives.

Alternative 1(Alt 1): and (5) network initiation. The CN entity initiates the procedure actively.

Condition 1: step 1: the UCMF entity detects that the capability identification of the user equipment is invalid or cleared, and the UCMF sends a notification message to notify the core network of the situation. The invalid or cleared capability identity may be an identity for a specific user equipment, or one/some/all user equipments belonging to a specific PLMN, or one/some/all user equipments belonging to a specific user equipment manufacturer. Alternatively, if the user equipment has multiple identities, the capability identity may be one or some identities. Step 2: if the core network has a stored capability identity, the core network entity deletes the identity(s) and associated information.

Or condition 2: step 3-4: if the core network entity does not have a valid identity for a specific user equipment or set of capabilities and the core network entity fails to retrieve the capability identity and/or capabilities from the UCMF.

And 5-6: the core network entity informs the user equipment that the capability identity is invalid or deleted through a NAS message (e.g., a user equipment configuration update). Specifically, option 1: the 1 bit is used to indicate that the user equipment is invalid or deleted for all capability identities stored by the PLMN. Alternative 2: indicating which capability identification(s) stored by the user equipment is (are) invalid or deleted. Alternative 3: indicating that the identity in a particular area, e.g. a particular registration area, TA list, geographical area, is invalid or deleted.

Alternative 2(Alt 2): the user equipment initiates the NAS. The user equipment initiates the procedure with the NAS message.

Step 1: the user equipment initiates an initial NAS message, including a capability identifier, such as a registration request message; or the user equipment initiates a service request message.

Step 2: the CN entity cannot understand the capability identity or has no capability information related to the capability identity. Or step 3: the CN entity cannot retrieve the capability identity and/or the related capability information from the UCMF.

And 4, step 4: the CN entity informs the user equipment that the capability identity is invalid or deleted in a response message to the initial NAS message. The detailed information is the same as in alternative 1.

Alternative (Alt 3): the user equipment initiates RRC. The user equipment initiates the procedure through an RRC message.

Step 1: the user equipment initiates an initial NAS message including a capability identification, e.g. a registration request message, a service request message.

And 4, step 4: the CN entity informs the RAN that no capability identity or capability is not available, or if the RAN stores a capability identity, informs the RAN of an indication to delete the capability identity, or the CN entity sends a RAN message without capability identity and/or the CN entity sends a RAN message without capability.

And 5: the RAN node retrieves the user equipment capabilities from the user equipment using radio resource control messages. Optionally, as in step 5 of alternative 1, capability identification related information may be included.

Step 6: the user equipment deletes the identity associated with the information in step 5. If no capability identification related information is available in step 5, the user equipment deletes all identifications associated with the PLMN.

And 7: the radio access network entity is configured to receive user equipment capability information from the user equipment, wherein the user equipment capability information comprises a user equipment capability identity and/or other types of user equipment capability identities different from the user equipment capability identity. That is, the user equipment capability information has capabilities as requested in step 5 or other types of capability identification (e.g., manufacturer identification).

And 8: the radio access network entity is configured to inform the core network entity of the user equipment capability information. And step 9: the core network entity is configured to store user equipment capability information. Step 10: the core network entity is configured to inform the UCMF entity of user equipment capability information.

In the above embodiments, the core network entity may refer to an access and mobility management function (AMF). The capability identifier refers to a PLMN assigned capability identifier or a manufacturer assigned identifier. The CN entity and the UCMF may have a direct or indirect connection.

In the embodiment of the disclosure, the device and the method which are operable to recover the capability identification of the user equipment can provide good communication performance and high reliability. Embodiments of the present disclosure are a combination of techniques/procedures that may be employed in the 3GPP specifications to create a final product.

Fig. 5 is a block diagram of an example system 700 for wireless communication in accordance with an embodiment of the disclosure. The embodiments described herein may be implemented in a system using any suitably configured hardware and/or software. Fig. 5 shows a system 700. The system 700 includes Radio Frequency (RF) circuitry 710, baseband circuitry 720, application circuitry 730, memory/storage 740, display 750, camera 760, sensors 770, and input/output (I/O) interface 780, coupled to each other at least as shown.

The application circuitry 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., a graphics processor and an application processor). The processor may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to implement various applications and/or operating systems running on the system.

Baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may comprise a baseband processor. The baseband circuitry may handle various wireless control functions that enable communication with one or more wireless networks through the radio frequency circuitry. The wireless control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, and the like. In some embodiments, the baseband circuitry may provide communications compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMANs), Wireless Local Area Networks (WLANs), Wireless Personal Area Networks (WPANs). Embodiments in which the baseband circuitry is configured to support wireless communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

In various embodiments, baseband circuitry 720 may include circuitry that operates with signals that are not strictly considered to be within a baseband frequency. For example, in some embodiments, the baseband circuitry may include circuitry that operates with signals having an intermediate frequency, where the intermediate frequency is between the baseband frequency and the radio frequency.

The radio frequency circuitry 710 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the radio frequency circuitry may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. In various embodiments, the radio frequency circuitry 710 may include circuitry that operates with signals that are not strictly considered to be within a radio frequency. For example, in some embodiments, the radio frequency circuitry may include circuitry that operates with signals having an intermediate frequency, where the intermediate frequency is between a baseband frequency and a radio frequency.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part as one or more of radio frequency circuitry, baseband circuitry, and/or application circuitry. As used herein, "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, application circuitry, and/or memory/storage may be implemented together on a system on a chip (SOC).

Memory/storage 740 may be used to load and store data and/or instructions, for example, for a system. The memory/storage of one embodiment may comprise any combination of suitable volatile memory (e.g., Dynamic Random Access Memory (DRAM)) and/or non-volatile memory (e.g., flash memory). In various embodiments, the input/output interface 780 may include one or more user interfaces designed to enable a user to interact with the system and/or peripheral component interfaces designed to enable peripheral components to interact with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. The peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, and a power interface.

In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, baseband circuitry and/or radio frequency circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

In various embodiments, display 750 may include displays such as liquid crystal displays and touch screen displays. In various embodiments, system 700 may be a mobile computing device, such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, and the like. In various embodiments, the system may have more or fewer components and/or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

One of ordinary skill in the art understands that each unit, algorithm, and step described and disclosed in the embodiments of the present disclosure is implemented using electronic hardware or a combination of electronic hardware and software for a computer. Whether these functions are run in hardware or software depends on the conditions and design requirements of the application of the solution.

Those of ordinary skill in the art may implement the functionality of each particular application in different ways without departing from the scope of the present disclosure. A person skilled in the art will understand that he/she may refer to the working processes of the systems, devices and units in the above embodiments, since the working processes of the systems, devices and units are substantially the same. For convenience and brevity, these operations will not be described in detail.

It should be understood that the systems, devices, and methods disclosed in the embodiments of the present disclosure may be implemented in other ways. The above embodiments are merely exemplary. The division of cells is based on logic functions only, while other divisions exist in the implementation. Multiple units or components may be combined or integrated in another system. It is also possible to omit or skip certain features. On the other hand, the mutual coupling, direct coupling or communicative coupling shown or discussed is operated through some ports, devices or units, whether indirectly or through electrical, mechanical or other forms of communication.

Units that are separate components for illustration are physically separate or not. The unit for displaying is a physical unit or not, i.e. located in one place or distributed over a plurality of network units. Some or all of the elements are used for purposes of the embodiments. Furthermore, each functional unit in each embodiment may be integrated in one processing unit, may be physically independent, or may be integrated in one processing unit having two or more units.

If the software functional unit is implemented, used, or sold as a product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solutions proposed by the present disclosure can be implemented basically or partially in the form of software products. Alternatively, portions of the technical solutions that are advantageous for the conventional techniques may be implemented in the form of software products. The software product in a computer is stored in a storage medium that includes a plurality of commands for a computing device (e.g., a personal computer, server, or network device) to perform all or a portion of the steps disclosed in embodiments of the present disclosure. The storage medium includes a USB disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a floppy disk, or other medium capable of storing program code.

While the present disclosure has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the disclosure is not to be limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

1. A user equipment, UE, operable to recover a user equipment capability identification, ID, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

control the transceiver to receive an indication from a network node, wherein the indication comprises: indicating whether a type of user equipment capability identification is to be used; and

performing the instructing, wherein performing the instructing comprises: the processor uses a public land mobile network, PLMN, specific user equipment capability identification when the user equipment has the PLMN specific user equipment capability identification and a manufacturer specific user equipment capability identification.

2. The user equipment of claim 1, wherein the processor deletes the PLMN-specific capability identification when the processor enters a state in which no valid user data is available to the user equipment.

3. The user equipment of claim 1 or 2, wherein the processor deletes the PLMN-specific capability identity when the processor detects that a universal subscriber identity module, USIM, is removed from the user equipment.

4. The user equipment according to any of claims 1 to 3, wherein the processor deletes the PLMN specific capability identity when the processor detects that a new Universal Subscriber Identity Module (USIM) is inserted into the user equipment, and indicates the manufacturer specific user equipment capability identity to the network node when the processor registers with the network node.

5. The user equipment according to any of claims 1 to 4, wherein the processor deletes the PLMN specific capability identity when the processor detects that the same Universal Subscriber Identity Module (USIM) is removed from the user equipment and reinserted into the user equipment, and indicates the manufacturer specific user equipment capability identity to the network node when the processor registers with the network node.

6. The user equipment of any of claims 1-5, wherein, if the processor roams to a different PLMN, when the processor registers with the network node, the processor indicates the manufacturer-specific user equipment capability identification to the network node, and the processor deletes or maintains the PLMN-specific capability identification stored in the user equipment.

7. The user equipment of claim 6, wherein the processor uses the PLMN specific capability identification if the manufacturer specific user equipment capability identification is maintained or used if the user equipment reverts to a previous PLMN.

8. The user equipment of any of claims 1-7, wherein the indication comprises: -type information of the user equipment capability identification comprising at least one of the PLMN specific user equipment capability identification and the manufacturer specific user equipment capability identification, -deleting the PLMN specific user equipment capability identification, -deleting the manufacturer specific user equipment capability identification, -ignoring the PLMN specific user equipment capability identification, and-reusing the PLMN specific user equipment capability identification.

9. The user equipment of any of claims 1 to 8, wherein the indication is provided by radio resource control, RRC, signaling or non-access stratum, NAS, signaling.

10. A method operable to recover a user equipment capability identity of a user equipment, UE, comprising:

receiving an indication from a network node, wherein the indication comprises: indicating whether a type of user equipment capability identification is to be used; and

performing the instructing, wherein performing the instructing comprises: the UE uses a public land Mobile network, PLMN, specific user equipment capability identity when the user equipment has the PLMN specific user equipment capability identity and a manufacturer specific user equipment capability identity.

11. The method of claim 10, wherein the user equipment deletes the PLMN-specific capability identity when the user equipment enters a state in which no valid user data is available for the user equipment.

12. The method according to claim 10 or 11, wherein the user equipment deletes the PLMN-specific capability identity when the user equipment detects that a universal subscriber identity module, USIM, is removed from the user equipment.

13. The method according to any of claims 10 to 12, wherein the user equipment deletes the PLMN-specific capability identity when the user equipment detects that a new universal subscriber identity module USIM is inserted into the user equipment, and indicates the manufacturer-specific user equipment capability identity to the network node when the user equipment registers with the network node.

14. The method according to any of claims 10 to 13, wherein the user equipment deletes the PLMN-specific capability identity when the user equipment detects that the same universal subscriber identity module USIM is removed from the user equipment and reinserted into the user equipment, and indicates the manufacturer-specific user equipment capability identity to the network node when the user equipment is registered with the network node.

15. The method according to any of claims 10-14, wherein if the user equipment roams to a different PLMN, the user equipment indicates the manufacturer specific user equipment capability identity to the network node when the user equipment registers with the network node, and the user equipment deletes or maintains the PLMN specific capability identity stored in the user equipment.

16. The method of claim 15, wherein if the user equipment returns to a previous PLMN, the user equipment uses the PLMN-specific capability identity if the manufacturer-specific user equipment capability identity is maintained or used.

17. The method of any of claims 10-16, wherein the indicating comprises: -type information of the user equipment capability identification comprising at least one of the PLMN specific user equipment capability identification and the manufacturer specific user equipment capability identification, -deleting the PLMN specific user equipment capability identification, -deleting the manufacturer specific user equipment capability identification, -ignoring the PLMN specific user equipment capability identification, and-reusing the PLMN specific user equipment capability identification.

18. The method of any of claims 10 to 17, wherein the indication is provided by radio resource control, RRC, signaling or non-access stratum, NAS, signaling.

19. A network node operable to recover user equipment capability identification, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

control the transceiver to transmit an indication to a user equipment, wherein the indication comprises: indicating whether a type of user equipment capability identification is to be used; and

requesting the user equipment to execute the indication, wherein executing the indication comprises: the processor requests the user equipment to use a public land mobile network, PLMN, specific user equipment capability identity when the user equipment has the PLMN specific user equipment capability identity and a manufacturer specific user equipment capability identity.

20. The network node of claim 19, wherein the processor requests the user equipment to delete the PLMN-specific capability identification when the user equipment enters a state in which no valid user data is available to the user equipment.

21. The network node according to claim 19 or 20, wherein the processor requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that a universal subscriber identity module, USIM, is removed from the user equipment.

22. The network node according to any of claims 19 to 21, wherein the processor requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that a new universal subscriber identity module USIM is inserted into the user equipment, and the processor requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node when the user equipment is registered with the network node.

23. The network node according to any of claims 19 to 22, wherein the processor requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that the same universal subscriber identity module USIM is removed from the user equipment and reinserted into the user equipment, and the processor requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node when the user equipment is registered with the network node.

24. The network node of any of claims 19 to 23, wherein, if the user equipment roams to a different PLMN, when the user equipment registers with the network node, the processor requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node, and the processor requests the user equipment to delete or maintain the PLMN-specific capability identity stored in the user equipment.

25. The network node of claim 24, wherein if the user equipment returns to a previous PLMN, the processor requests the user equipment to use the PLMN-specific capability identity if the manufacturer-specific user equipment capability identity is maintained or used.

26. The network node of any of claims 19 to 25, wherein the indication comprises: -type information of the user equipment capability identification comprising at least one of the PLMN specific user equipment capability identification and the manufacturer specific user equipment capability identification, -deleting the PLMN specific user equipment capability identification, -deleting the manufacturer specific user equipment capability identification, -ignoring the PLMN specific user equipment capability identification, and-reusing the PLMN specific user equipment capability identification.

27. The network node of any of claims 19 to 26, wherein the indication is provided by radio resource control, RRC, signaling or non-access stratum, NAS, signaling.

28. A method operable to recover a user equipment capability identity of a network node, comprising:

sending an indication to a user equipment, wherein the indication comprises: indicating whether a type of user equipment capability identification is to be used; and

requesting the user equipment to execute the indication, wherein executing the indication comprises: when the user equipment has a public land mobile network, PLMN, specific user equipment capability identity and a manufacturer specific user equipment capability identity, the network node requests the user equipment to use the PLMN specific user equipment capability identity.

29. The method of claim 28, wherein the network node requests the user equipment to delete the PLMN-specific capability identity when the user equipment enters a state in which no valid user data is available for the user equipment.

30. The method according to claim 28 or 29, wherein the network node requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that a universal subscriber identity module, USIM, is removed from the user equipment.

31. The method according to any of claims 28 to 30, wherein the network node requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that a new universal subscriber identity module USIM is inserted into the user equipment, and the network node requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node when the user equipment registers with the network node.

32. The method according to any of claims 28 to 31, wherein the network node requests the user equipment to delete the PLMN-specific capability identity when the user equipment detects that the same universal subscriber identity module USIM is removed from the user equipment and reinserted into the user equipment, and the network node requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node when the user equipment is registered with the network node.

33. The method according to any of claims 28-32, wherein if the user equipment roams to a different PLMN, when the user equipment registers with the network node, the network node requests the user equipment to indicate the manufacturer-specific user equipment capability identity to the network node, and the network node requests the user equipment to delete or maintain the PLMN-specific capability identity stored in the user equipment.

34. The method of claim 33, wherein, if the user equipment returns to a previous PLMN, the network node requests the user equipment to use the PLMN-specific capability identity if the manufacturer-specific user equipment capability identity is maintained or used.

35. The method of any of claims 28-34, wherein the indication comprises: type information of the user equipment capability identification including at least one of the PLMN specific user equipment capability identification, the manufacturer specific user equipment capability identification, deleting the PLMN specific user equipment capability identification, deleting the manufacturer specific user equipment capability identification, ignoring the PLMN specific user equipment capability identification, and reusing the PLMN specific user equipment capability identification.

36. The method of any of claims 28 to 35, wherein the indication is provided by radio resource control, RRC, signaling or non-access stratum, NAS, signaling.

37. A non-transitory machine-readable storage medium having instructions stored thereon, which when executed by a computer, cause the computer to perform the method of any of claims 10-18 and 28-36.

38. A terminal device, comprising: a processor and a memory configured to store a computer program, the processor being configured to execute the computer program stored in the memory to perform the method of any of claims 10 to 18.

39. A network node, comprising: a processor and a memory configured to store a computer program, the processor being configured to execute the computer program stored in the memory to perform the method of any of claims 28 to 36.

40. A chip, comprising:

a processor configured to invoke and run a computer program stored in memory to cause a device in which the chip is installed to perform the method of any of claims 10 to 18 and 28 to 36.

41. A computer-readable storage medium storing a computer program, wherein the computer program causes a computer to perform the method of any one of claims 10 to 18 and 28 to 36.

42. A computer program product comprising a computer program, wherein the computer program causes a computer to perform the method of any one of claims 10 to 18 and 28 to 36.

43. A computer program, wherein the computer program causes a computer to perform the method of any one of claims 10 to 18 and 28 to 36.