RU2789445C1 - Method for control of identifiers of terminal device authorities and communication device - Google Patents

Abstract

FIELD: telecommunication technologies.

SUBSTANCE: invention relates to telecommunication technologies, namely to a method for control of identifiers of terminal device authorities and a communication device. The second communication device can perform an operation corresponding to an identifier of terminal device authorities in accordance with received information about control of the identifier of terminal device authorities in such a way that both a network and a terminal device are coordinated in use of the identifier of terminal device authorities. Options of implementation of the invention provide a method for control of identifiers of terminal device authorities, as well as a communication device. The control method includes implementation of the first operation related to the identifier of terminal device authority and including at least one of following actions: removal or termination of action of the identifier of terminal device authority, change in an identifier of terminal device authority of the first type in context of the terminal device for an identifier of terminal device authority of the second type, as well as transmission of information about control of the identifier of terminal device authority.

EFFECT: increase in the efficiency of control of information of identifiers of terminal device authorities.

18 cl, 14 dwg

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority on the basis of Chinese Patent Application No. 201910108736.3, filed February 3, 2019, and incorporated herein by reference in its entirety.

FIELD OF TECHNOLOGY

[0002] This invention relates to telecommunication technologies, namely, to a method for managing terminal device authority identifiers and to a communication device.

BACKGROUND OF THE INVENTION

[0003] As networks evolve, terminals have to maintain more and more privileges and, accordingly, notify networks of their additional privileges. However, the growth in the volume of proxy messages increases the load on the wireless interfaces.

[0004] In order to reduce the overhead of the permission messages of the terminal devices, you can define specific permission identifiers for each terminal device. A terminal's permission identifier (which may be referred to as a permission identifier for short) may be used to identify the permission set of the terminal. There is a one-to-one correspondence between a terminal's permission identifier and a terminal's permission set, and a terminal's permission set can be obtained by matching with a terminal's permission identifier. The amount of information about the permission ID of the terminal device is less than the amount of information about the permission of the terminal device, which reduces the amount of transmitted permission signals.

[0005] The tag's proxy ID information may be set by the network or the tag's manufacturer. One set of tag permissions may simultaneously include both tag permission ID information set by the network and tag permission ID information set by the tag manufacturer.

[0006] Because a tag may include information about a plurality of tag credentials, effectively managing such tag permissions information is a technical problem that has not been addressed in the prior art.

SUMMARY OF THE INVENTION

[0007] Embodiments of the present invention provide a method for managing the credentials of a terminal device, as well as a communication device, to solve the problem of efficiently managing information about the credentials of a terminal device.

[0008] The present invention solves the above technical problem as follows:

[0009] The first embodiment of the present invention implements a tag authority ID management method applied to a first communication device, including:

performing the first operation associated with the endpoint's authorization identifier and including at least one of the following:

deleting or suspending a terminal's authorization identifier;

changing the permission identifier of the first type terminal in the context of the terminal to the permission identifier of the second type terminal;

transmission of information about the management of the authority ID of the end device.

[0010] A second embodiment of the present invention implements a tag authority ID management method applied to a second communication device, including:

obtaining information about the management of the authority identifier of the end device, which includes at least one of the following information blocks:

indication information about the removal or suspension of the authority identifier of the terminal device;

the authorization identifier of the end device to be removed or suspended;

a first block of indication information about changing a permission identifier of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device;

a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal;

the identification information of the network being the updated network to which the authorization identifier of the terminal device is applied;

the identification information of the network being the newly added network to which the authorization identifier of the terminal is applied;

the identification information of the network, which is the network to which the authorization identifier of the terminal device does not apply;

performing a second operation related to the permission ID of the terminal based on the management information of the permission ID of the terminal.

[0011] A third embodiment of the present invention implements a tag authority ID management method applied to a third communication device, including:

transfer of all end device permission identifiers corresponding to the current end device permissions, where

the current permissions of the terminal device is the set of permissions of the terminal device in the first network;

the tag's permission ID includes at least the network tag's permission id and/or the factory tag's permission id.

[0012] A fourth embodiment of the present invention implements a tag authority ID management method applied to a fourth communication device, including:

if the second condition is met, the transmission of request information, which includes at least one of the following information blocks: information about the type of authorization ID of the terminal device, information of the first request, request information of the factory authorization identifier of the terminal device, and request information about the presence of the factory authorization identifier of the terminal device, Where

information about the type of the authorization identifier of the terminal device is used to obtain the corresponding authorization identifier of the terminal device;

the first request information is used to query all types of tag permission IDs, and the tag permission ID is a tag permission ID corresponding to the current permission of the tag;

the second condition assumes that there is no factory endpoint authorization identifier.

[0013] The fifth embodiment of the present invention implements a tag authority ID management method applied to a fifth communication device, including:

obtaining request information including at least one of the following information blocks: information about the type of permission identifier of the terminal device, information of the first request, information of the request information of the factory permission identifier of the terminal device, and information of the request information about the presence of the factory permission identifier of the terminal device, where the type information the terminal's permission identifier is used to obtain the corresponding terminal's permission identifier; the first request information is used to request all types of terminal authorization identifiers; and the tag's permission ID is a tag's permission id corresponding to the current permission of the tag;

transmitting the authorization ID information of the terminal based on the request information.

[0014] A sixth embodiment of the present invention provides a communication device including:

an executing module configured to perform the first operation associated with the endpoint's authorization identifier, which includes at least one of the following:

deleting or suspending a terminal's authorization identifier;

changing the permission identifier of the first type terminal in the context of the terminal to the permission identifier of the second type terminal;

transmission of information about the management of the authority ID of the end device.

[0015] A seventh embodiment of the present invention provides a communication device including:

the first receiving module configured to receive end device proxy identity management information that includes at least one of the following information blocks:

indication information about the removal or suspension of the authority identifier of the terminal device;

the authorization identifier of the end device to be removed or suspended;

a first block of indication information about changing a permission identifier of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device;

a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal;

the identification information of the network being the updated network to which the authorization identifier of the terminal device is applied;

the identification information of the network being the newly added network to which the authorization identifier of the terminal is applied;

the identification information of the network, which is the network to which the authorization identifier of the terminal device does not apply;

an executing module configured to perform a second operation related to the permission ID of the terminal device based on the management information of the permission ID of the terminal device.

[0016] An eighth embodiment of the present invention provides a communication device including:

a sending module configured to send all end device permission identifiers corresponding to the end device's current permissions, where

the current permissions of the terminal device is the set of permissions of the terminal device in the first network;

the terminal's proxy identifier includes at least the terminal's network proxy identifier type and/or the terminal's factory authorization type.

[0017] A ninth embodiment of the present invention provides a communication device including:

a transmitting module configured under the second condition to transmit request information including at least one of the following information blocks: information about the type of permission ID of the terminal device, information of the first request, request information of the factory permission ID of the terminal device, and request information about the presence of factory authority identifier of the end device, where

information about the type of the authorization identifier of the terminal device is used to obtain the corresponding authorization identifier of the terminal device;

the first request information is used to query all types of tag permission IDs, and the tag permission ID is a tag permission ID corresponding to the current permission of the tag;

the second condition assumes that there is no factory endpoint authorization identifier.

[0018] A tenth embodiment of the present invention provides a communication device including:

a receiving module configured to receive request information including at least one of the following information blocks: information about the type of permission ID of the terminal device, information of the first request, request information of the factory permission ID of the terminal device, and request information about the presence of the factory permission ID of the terminal device where information about the type of the terminal's permission identifier is used to obtain the corresponding permission identifier of the terminal; the first request information is used to request all types of terminal authorization identifiers; and the tag's permission ID is a tag's permission id corresponding to the current permission of the tag;

a sending module configured to send information about the authority ID of the terminal device based on the request information.

[0019] An eleventh embodiment of the present invention provides a communication device including a processor, a memory, and a computer program that is stored in the memory and can run on the processor. The computer program, during its execution on the processor, implements the steps of the above-described method for managing tag authority identifiers.

[0020] A twelfth embodiment of the present invention provides a computer-readable storage medium containing a computer program that, during its execution on a processor, implements the steps of the above-described method for managing tag credentials.

[0021] Embodiments of the present invention solve the problem of efficient management of tag authority ID information and uniform use of tag authority identifiers on both the network side and the tag side.

BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Other advantages of the invention will become apparent to those skilled in the art based on the following detailed description of possible embodiments of the invention. The accompanying drawings are given only as an illustration of the main ideas of the embodiments of the present invention and do not impose any restrictions on the present invention. In all accompanying drawings, the same reference numbers correspond to the same components. Description of accompanying drawings:

[0023] FIG. 1 is a generalized flowchart of a method for managing tag credentials in accordance with Embodiment 1 of the present invention;

[0024] FIG. 2 is a generalized flowchart of a method for managing tag credentials in accordance with Embodiment 2 of the present invention;

[0025] FIG. 3 is a generalized flowchart of a method for managing tag credentials in accordance with Embodiment 3 of the present invention;

[0026] FIG. 4 is a general flow diagram of a method for managing tag credentials in accordance with Embodiment 4 of the present invention;

[0027] In FIG. 5 is a general flow diagram of a method for managing tag credentials in accordance with Embodiment 5 of the present invention;

[0028] In FIG. 6 is a generalized flowchart of a method for managing tag authority identifiers for a first application scenario in accordance with one embodiment of the present invention;

[0029] FIG. 7 is a generalized flowchart of a method for managing tag authority identifiers for a second use case, in accordance with one embodiment of the present invention;

[0030] FIG. 8 is a generalized flowchart of a method for managing tag authority identifiers for a third application scenario, in accordance with one embodiment of the present invention;

[0031] In FIG. 9 is a schematic block diagram of a communication device in accordance with one embodiment of the present invention;

[0032] FIG. 10 is a schematic block diagram of a terminal device in accordance with one embodiment of the present invention;

[0033] FIG. 11 is a schematic block diagram of a terminal device in accordance with another embodiment of the present invention;

[0034] FIG. 12 is a schematic block diagram of a communication device in accordance with yet another embodiment of the present invention;

[0035] FIG. 13 is a schematic block diagram of a terminal device in accordance with a further embodiment of the present invention;

[0036] FIG. 14 is a schematic block diagram of a terminal device in accordance with another further embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

[0037] The technical solutions used in the embodiments of the present invention are described below clearly and in full, with reference to the corresponding accompanying drawings. It is obvious that the described embodiments are possible, but not exhaustive for this invention. All other embodiments of the present invention, obtained by those skilled in the art based on the embodiments described without creative effort, are included in the scope of legal protection for this invention.

[0038] In the description and claims in this application, the term "includes" and any other variations thereof are not meant to be exclusive, so, for example, processes, methods, systems, articles, or devices that include a sequence of actions or components are not necessarily limited to directly listed actions and components, but may include other actions or components not listed or not explicitly inherent in such processes, methods, systems, products or devices. Also in the description and claims, the use of "and/or" denotes the presence of at least one of the related entities, for example, "A and/or B" denotes any of the following three options: only A, only B, or both A and B.

[0039] In embodiments of the invention, terms such as "example" or "for example" are used to represent examples, illustrations, or explanations. Any options or designs identified by the terms "example" or "for example" in the embodiments of this invention should not be construed as preferable or more advantageous than other options or designs. In particular, the words "example" or "for example" denote specific implementations of the relevant concept.

[0040] The technologies described herein are not limited to the 5th generation system (5th-generation, 5G) and subsequent communication systems, as well as the long-term evolution system (Long Term Evolution, LTE) or the LTE-Advanced (LTE-Advanced , LTE-A) and can be used in various wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Channel Division Multiple Access Frequency Division Multiple Access, FDMA, Orthogonal Frequency Division Multiple Access, OFDMA, Single-carrier Frequency-Division Multiple Access, SC-FDMA) and others.

[0041] The terms "system" and "network" are commonly used interchangeably. A CDMA system may include radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). UTRA technology includes wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other variants of code division multiple access CDMA. A TDMA system may include radio technologies such as Global System for Mobile Communication (GSM). The OFDMA system may include radio technologies such as Ultra Mobile Broadband (UMB), evolved UTRA (Evolved-UTRA, E-UTRA), IEEE 802.11 (Wireless Fidelity, Wi-Fi), IEEE 802.16 (World Interoperability for Microwave Access, WiMAX), IEEE 802.20 and Flash-OFDM. UTRA and E-UTRA technologies are part of the Universal Mobile Telecommunications System (UMTS). LTE technology and extensions of LTE technology (eg, LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM technologies are taken from the documentation of the 3rd Generation Partnership Project (3GPP) consortium. Information about CDMA2000 and UMB technologies is taken from the documentation of the consortium "3rd Generation Partnership Project 2" (3rd Generation Partnership Project 2, 3GPP2). The methods described in this description of the invention can be used both in the above systems and radio technologies, and in other systems and radio technologies.

[0042] For a better understanding of the embodiments of the present invention, the following technical details are first described.

[0043] 1. Terminal Authority

[0044] First, it should be noted that the terminal device authority can be divided into radio access authority and core network access authority. The terminal device may announce the radio access authority of the terminal device upon request of the network. In addition, the tag may announce the core network access authorization of the tag during registration. A terminal may support multiple bands (Band) and frequencies (frequency). With the introduction of technologies such as carrier aggregation (CA) and dual connection (Dual Connectivity, DC), it becomes necessary to organize various combinations of bands, which can vary significantly between different terminal device manufacturers, which leads to a huge variety of radio access rights. In addition, as networks evolve, more and more functions are required that require different powers and radio capabilities. For each network function, the end device must inform the network whether the corresponding function is supported.

[0045] 2. Terminal Authority ID Information

[0046] In order to reduce the overhead of endpoint permission messages, specific permission IDs can be defined for each endpoint. A terminal's permission identifier (which may be referred to as a permission identifier for short) may be used to identify the permission set of the terminal. There is a one-to-one correspondence between a terminal's permission identifier and a terminal's permission set, and a terminal's permission set can be obtained by matching with a terminal's permission identifier. A method for optimizing terminal permission signaling is for the terminal to report to the network only information about an identifier indicating the permission set of the terminal. The network can derive a set of tag permissions based on a mapping with the tag permission ID information. The amount of information about the permission ID of the terminal device is less than the amount of information about the permission of the terminal device, which reduces the amount of transmitted permission signals. The function can be attributed to optimizing the powers of the terminal device.

[0047] The tag's proxy ID information may be set by the network or the tag's manufacturer.

[0048] If the tag's proxy ID information is set by the tag's manufacturer, then the tag can simply inform the network of the tag's proxy ID information by the tag's manufacturer. If the tag's permission ID information is set by the network, then the tag needs to notify the network of the tag's permission set, so that the network in turn sends the tag's permission id information to the tag obtained by matching with the tag's permission set. Thus, these two methods correspond to different network behavior and different network powers.

[0049] One set of terminal permissions may contain either a terminal permission identifier assigned by the network and a terminal permission identifier assigned by the terminal device manufacturer, or only a terminal device permission identifier assigned by the network, or only a terminal device permission identifier assigned by the terminal manufacturer. device, or may not contain the end device's authority identifier.

[0050] The tag's permission ID, set by the tag's manufacturer, may be referred to as the factory tag's permission id. The terminal authority identifier defined by the network may be referred to as the network terminal authority identifier.

[0051] In order to optimize terminal credentials signaling, the following issues need to be addressed:

[0052] Problem 1: When a terminal device provides the network with the factory permission ID information of the terminal device, the network may not know that there is a match between the factory permission ID information of the terminal device and the permission set of the terminal device. In this case, the network can first obtain the permission information of the terminal device and then provide the terminal device with the appropriate information about the network permission identifier of the terminal device. In this way, the terminal device and the network will be able to obtain a set of permissions of the terminal device based on a mapping with the information about the network identifier of the permission of the terminal device. Next, the network can learn the correspondence between the factory permission ID information of the terminal device and the permission set of the terminal device from the auxiliary server of the manufacturer of the terminal device, and instruct the terminal device to use the factory permission ID information of the terminal device. However, it remains unclear how to move from the tag's network permission ID information to the tag's factory permission ID information.

[0053] Problem 2: A terminal's network proxy identity information may apply to a plurality of Public Land Mobile Networks (PLMNs). If a PLMN is no longer in use, it remains unclear whether a new applicable PLMN should be added or an applicable PLMN should be updated.

[0054] If necessary, in the embodiments of the present invention, the acquisition procedure can be understood as obtaining from a configuration, receiving, obtaining by receiving on request, obtaining by self-learning, obtaining by logical restoration of missing information, or obtaining by processing the received information depending on actual needs. Embodiments of the present invention do not impose any restrictions. For example, if any part of the indication information is not received from the device, then it can be concluded that the device does not support this permission.

[0055] It should be noted that, in embodiments of the present invention, transmission may include broadcasting, broadcasting via a system message, or returning a response upon receipt of a request.

[0056] In one embodiment of the present invention, a communication network element may be a physical device, a network function, or a network element.

[0057] One terminal device may store information about one or more authority identifiers of the terminal device.

[0058] In one embodiment of the present invention, the terms "terminal authority", "terminal authority information", and "terminal authority set" may be synonymous.

[0059] In one embodiment of the present invention, the terms "proxy ID information", "terminal proxy ID information", and "terminal proxy identification information" may be synonymous.

[0060] In one embodiment of the present invention, the tag's network proxy identifier may also be referred to as the tag's network-defined proxy identifier.

[0061] In one embodiment of the present invention, the tag's factory proxy identifier may also be referred to as the tag's proxy identifier as defined by the tag's manufacturer.

[0062] In one of the embodiments of the present invention, the credentials of the terminal device can be understood as the current credentials of the terminal device. The current permission identifier of the terminal device can be understood as at least one of the following information blocks: information about the permission identifier of the terminal device corresponding to the current set of permissions of the terminal device, information about the actual permission identifier of the terminal device, the current permission identifier of the terminal device, the current permission identifier of the terminal device , passed by the end device to the network, and the end device's current authority ID provided by the network.

[0063] In one embodiment of the present invention, the network is an access network for terminal devices and may be a network or dedicated network of a network (mobile) operator, or a public communication network or a closed private communication network. In one of the embodiments of the present invention, the wireless communication network may be at least a public network or a private network. The network network identifier may be a public network identifier (eg, a PLMN ID) or a private network identifier (eg, a non-public network (NPN) identifier and/or a PLMN ID used in a private network).

[0064] In one embodiment of the present invention, a private network refers to a private communications network. A private network may also be referred to as a private communications network. A private network can include at least one of the following deployment methods: a physical private network, a virtual private network, and a private network within a public network. In one embodiment, the private network is a Closed Access Group (CAG). The CAG may include a group of terminals.

[0065] In one embodiment of the present invention, a private network may include a closed private network or be considered a closed private network. A closed private network can be one of the following types: closed private communication network, closed network, local area network (Local Area Network, LAN), closed virtual private network (Private Virtual Private Network, PVPN), isolated communication network, dedicated communication network, and etc. It should be noted that embodiments of the present invention do not impose restrictions on naming methods.

[0066] In one embodiment of the present invention, public network refers to a public communication network. The public network may also be referred to as a public communications network or otherwise. It should be noted that embodiments of the present invention do not impose restrictions on naming methods.

[0067] In one of the embodiments of the present invention, the communication device may include a communication network element and/or terminal device.

[0068] In one embodiment of the present invention, the communication network element may include a core network element and/or a radio access network element.

[0069] In embodiments of the present invention, the core network element (CN element) may include, but is not limited to, at least one of the following: core network device, core network node, core network function, core network element, control entity Access Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Serving Gate Way , SGW), Packet Data Network Gate Way (PDN-GW), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Support Node Serving GPRS Support Node (SGSN), General Packet Radio Service (GPRS), Gateway GPRS Support Node, GGSN) and a network radio access device.

[0070] In embodiments of the present invention, a Radio Access Network (RAN) element may include, but is not limited to, at least one of the following elements: a radio access network device, a radio access network node, a radio access network function, a radio access network block, 3GPP radio access network, non-3GPP radio access network, Centralized Unit (CU), Distributed Unit (DU), base station, evolved Node B (evolved Node B, eNB), 5G base station (gNB ), Radio Network Controller (RNC), Base Station (NodeB), Non-3GPP Inter Working Function (N3IWF), Access Controller (AC), Access Point Device ( Access Point, AP), Wireless Local Area Networks (WLAN), or N3IWF.

[0071] The base station may be a base transceiver station (Base Transceiver Station, BTS) in the global system for mobile communication (Global System for Mobile communication, GSM) or code division multiple access (CDMA) network, basic a station (NodeB) in a WCDMA network, an evolved NodeB (eNB or eNodeB) in an LTE network, or a 5G NodeB (gNB). Embodiments of the present invention do not impose any restrictions.

[0072] In embodiments of the present invention, the UE is a terminal device. The terminal device may include a relay that supports the function of the terminal device, or an auxiliary terminal device that supports the function of the relay. The terminal device may also be referred to as user equipment (User Equipment, UE). The terminal device may be a subscriber device such as a mobile phone, tablet computer (Tablet Personal Computer), laptop (Laptop Computer), personal digital assistant (Personal Digital Assistant, PDA), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or on-board device of the vehicle. It should be noted that in some embodiments of the present invention, there are no restrictions on the type of terminal device.

[0073] FIG. 1 shows a method for managing tag authority IDs according to Embodiment 1 of the present invention applied to a first communication device. The first communication device includes at least a first communication network element (eg, a first network element CN or a first network element RAN). The control method includes the following steps:

[0074] Step 11. Performing a first operation associated with the permission identifier of the terminal device and including at least one of the following:

[0075] (1) Removing or suspending the authorization identifier of a terminal.

[0076] In particular, the first communication device deletes the tag's permission identifier or suspends the tag's permission identifier in the tag's context stored on the first communication device. For example, if the first communication device stores both the stub's network proxy ID and the stub's factory proxy ID, then the stub's network proxy id may be deleted or the stub's network proxy id may be suspended and allowed to communicate with other communication devices. the end device's factory authorization identifier may be used.

[0077] (2) Changing the permission ID of the first type terminal in the context of the terminal device to the permission ID of the second type terminal.

[0078] Optionally, the first type may be considered to be the network proxy identifier type of the terminal, and the second type may be considered to be the factory authority identifier type of the terminal, or the first type may be considered to be the factory authority identifier type of the terminal, and the second type may be considered to be the network authority identifier type of the endpoint. devices.

[0079] (3) Transmission of information about the management of the authority identifier of the terminal device.

[0080] Specifically, the first communication device transmits the permission ID management information of the terminal device to other communication devices. Other communication devices include, for example, another terminal device or a network element RAN of the first network.

[0081] In this embodiment of the present invention, the first communication device performs an operation related to the permission ID of the terminal device in order to manage the proxy ID of the terminal device so that the network and the terminal device consistently use the proxy ID of the terminal device.

[0082] In one embodiment, the first communication device that performs the first operation associated with the terminal's proxy identifier is a core network element.

[0083] In one embodiment, the first communication device that performs the first operation associated with the terminal's proxy identifier is a radio access network element.

[0084] In one embodiment, the tag's authority ID management information includes at least one of the following information blocks:

[0085] (1) Indicative information about the removal or suspension of the authorization identifier of the terminal device.

[0086] In one embodiment, the first communication device instructs the other communication device to remove the tag's permission identifier or suspend the tag's permission identifier. The tag's proxy ID may be a network tag's proxy ID.

[0087] (2) Authority ID of the terminal to be removed or suspended.

[0088] In one embodiment, if it is desired to remove a portion of a tag's permission set or suspend a portion of a tag's permission set, then the tag's permission identifiers that were requested to be removed or suspended may be transmitted. The tag's proxy ID may be a network tag's proxy ID.

[0089] (3) The first block of indication information about changing the permission ID of the first type terminal in the context of the terminal to the permission ID of the second type terminal.

[0090] (4) The second block of indication information about the transmission of the permission ID of the second type terminal device, if it is necessary to transmit the permission ID of the terminal device.

[0091] (5) Identification information of the network, which is the updated network to which the authorization identifier of the terminal device is applied.

[0092] Assume, for example, that the identity of the network to which the authority identifier of the terminal device is applied includes network identifier 1 and network identifier 2. Wherein, the network identification information transmitted by the first communication device includes network identifier 3 and network ID is 4, and the network is the updated network to which the Endpoint Authority ID applies. In this case, the terminal may, based on the received network identity information, add network ID 3 and network ID 4 to the network identity of the network to which the authority ID of the terminal device is applied.

[0093] (6) Identification information of the network being the newly added network to which the authorization identifier of the terminal device is applied.

[0094] Let, for example, the identification information of the network to which the authority identifier of the terminal device applies include network identifier 1 and network identifier 2. Wherein, the network identification information transmitted by the first communication device includes network identifier 3, and the network is the newly added network to which the end device's permission identifier applies. In this case, the terminal device can, based on the received network identity information, change the network identity information of the network to which the authority identifier of the terminal device is applied. The modified identity of the network to which the Endpoint Authority ID applies will include Network ID 1, Network ID 2, and Network ID 3.

[0095] (7) Identification information of the network, which is the network to which the terminal authorization identifier does not apply.

[0096] Let, for example, the identification information of the network to which the authority identifier of the terminal device applies include network identifier 1 and network identifier 2. Wherein, the network identification information transmitted by the first communication device includes network identifier 2, and the network is the network to which the end device's permission identifier does not apply. In this case, the terminal device can, based on the received network identity information, change the network identity information of the network to which the authority identifier of the terminal device is applied. The modified identity of the network to which the Endpoint Authority ID applies will include Network ID 1.

[0097] In one embodiment, the network may be a public network and the network identifier is a PLMN identifier.

[0098] In another implementation, the network may be a private network and the network identifier may be one of the following types: PLMN ID (eg, PLMN ID with MNC 999) and NPN ID; PLMN ID and CSG ID; or NPN ID.

[0099] In one implementation, the first type is the tag's network proxy ID type, and the second type is the tag's factory proxy ID type.

[00100] In one embodiment, the tag's proxy ID is a network tag's proxy ID. That is, performing the first operation associated with the proxy identity of the terminal includes performing the first operation associated with the network proxy identifier of the terminal.

[00101] In one embodiment, if the first condition is met, the first operation associated with the terminal's permission identifier is performed, where the first condition includes at least one of the following situations:

(1) Endpoint Permission Network ID configured for Endpoint;

(2) received a set of terminal permissions corresponding to the factory permission identifier of the terminal;

(3) a match is obtained between the factory permission ID of the terminal device and the permission set of the terminal device, and the permission set of the terminal device is consistent with the current permission of the terminal device;

(4) received a factory end device permission ID corresponding to the current end device permission.

[00102] The current permission of the terminal device is the set of permissions of the terminal device in the first network.

[00103] In one embodiment, the first communication device obtains and stores the tag's factory proxy ID information, but is unaware of the tag's permission set corresponding to the tag's factory proxy ID, and therefore assigns the tag's network proxy ID to the terminal. However, at a later time, a set of terminal permissions corresponding to the factory permission identifier of the terminal device can be obtained. In this case, the first communication device already knows that the tag has information about the tag's factory proxy ID and can instruct the tag to remove the network proxy ID of the tag or suspend the network proxy ID of the tag. In cases where the end device is required to transmit the end device's proxy ID, the end device sends information about the end device's factory proxy ID.

[00104] In another embodiment, the first communication device does not receive the tag's factory proxy ID information and therefore assigns the tag's network proxy ID to the tag. However, at a later date, a factory endpoint authorization identifier corresponding to the current endpoint authorization can be obtained. In this case, the first communication device is unaware of whether the terminal device has information about the factory authorization identifier of the terminal device. After determining that the terminal has information about the factory proxy ID of the terminal, the first communication device may instruct the terminal to remove the network proxy ID of the terminal or suspend the network proxy ID of the terminal. In cases where the end device is required to transmit the end device's proxy ID, the end device sends information about the end device's factory proxy ID.

[00105] In one embodiment, if the tag's permission ID management information includes at least the tag's permission ID suspension indication information and/or the permission ID of the tag to be suspended,

then, after the transmission of the permission ID management information of the terminal device, the restoration information of the permission ID management of the terminal device, which is used to recover the permission ID of the terminal device which has been suspended, is further transmitted.

[00106] The tag's proxy ID management recovery information includes at least the tag's proxy ID recovery indication and/or the tag's proxy ID to be restored.

[00107] In one embodiment, prior to performing the first operation associated with the terminal's credential identifier, the method further includes the following:

if the second condition is met, the transmission of request information, including at least one of the following information blocks:

(1) information about the type of the terminal's permission identifier, which is used to obtain the corresponding terminal's permission identifier;

(2) first request information, which is used to request all types of tag permission IDs, where the tag permission ID is a tag permission ID corresponding to the current permission of the tag;

(3) request information of the factory authorization identifier of the terminal device;

(4) query information about the presence of a factory authorization identifier of the terminal.

[00108] The second condition assumes that there is no factory tag authority identifier.

[00109] In one embodiment, the tag's permission ID is a tag's permission ID corresponding to the current tag's permission, and the current tag's permission is the permission set of the tag in the first network.

[00110] In one embodiment, the tag's proxy ID type includes at least the tag's factory proxy ID type and the tag's network proxy ID type.

[00111] In this embodiment of the present invention, the first communication device performs an operation related to the permission ID of the terminal device in order to manage the permission ID of the terminal device so that the network and the terminal device consistently use the permission ID of the terminal device.

[00112] FIG. 2 shows a method for managing tag authority IDs according to Embodiment 2 of the present invention applied to a second communication device. The second communication device includes at least a terminal device and a second communication network element (eg, a first network element RAN or a first network element CN). The control method includes the following steps.

[00113] Step 21: Obtain tag's proxy ID management information, including at least one of the following information blocks:

indication information about the removal or suspension of the authority identifier of the terminal device;

the authorization identifier of the end device to be removed or suspended;

a first block of indication information about changing a permission identifier of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device;

a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal;

the identification information of the network being the updated network to which the authorization identifier of the terminal device is applied;

the identification information of the network being the newly added network to which the authorization identifier of the terminal is applied;

the identity of the network, which is the network to which the terminal authorization identifier does not apply.

[00114] Step 22: Perform a second operation related to the permission ID of the terminal based on the management information of the permission ID of the terminal.

[00115] In one embodiment, the tag's proxy ID is the tag's network proxy ID. In particular, obtaining information about the management of the proxy ID of the terminal device includes obtaining information about the management of the network proxy ID of the terminal device. Performing a second operation related to the tag's proxy ID based on the tag's proxy ID management information includes performing a second operation related to the tag's network proxy ID based on the tag's network proxy ID management information.

[00116] In one embodiment, performing a second operation associated with a tag's proxy ID based on the tag's proxy ID management information includes:

if the third condition is met, performing a second operation related to the permission ID of the terminal device based on the management information of the permission ID of the terminal device.

[00117] The third condition includes at least one of the following situations:

the terminal device goes into standby mode;

the end device returns to connect mode from standby mode;

the end device is disconnected from the first network;

the terminal device resets its registration in the first network;

the terminal registers for the first time in the first network;

the end device connects to the first network for the first time.

[00118] In one embodiment, if the third condition is met, the second operation related to the tag's permission ID is performed based on the tag's permission ID management information, but not immediately after receiving the tag's permission ID management information. In other words, the endpoint's authority ID management information does not take effect immediately upon receipt, but after some delay.

[00119] However, in some other embodiments of the present invention, the second operation associated with the tag's proxy ID may be performed immediately after receiving the tag's proxy ID management information. It is easy to understand that from the point of view of the core network element in the first network, the terminal device provides the network permission identifier of the terminal device upon initial registration, and the core network element receives the permission set of the terminal device by matching with the network permission identifier of the terminal device. The core network element is aware of the permission set of the end device and always stores the context of the end device unless the end device is disconnected from the network. The end device shall only transmit the end device's authority identifier when it first connects to the first network. In this case, if the tag deletes the tag's network proxy ID or suspends the tag's network proxy ID based on the received tag's proxy ID management information, the tag sends the tag's factory proxy ID information.

[00120] It is easy to understand that, from the point of view of the radio access network element in the first network, after the transition of the terminal device to the idle mode, the core network element no longer stores the context of the terminal device. Accordingly, the tag only needs to retransmit the tag's credential identifier when returning to connect mode. In this case, if the tag deletes the tag's network proxy ID or suspends the tag's network proxy ID based on the received tag's proxy ID management information, the tag sends the tag's factory proxy ID information.

[00121] In one embodiment, if the tag's permission ID management information includes the tag's permission ID to be deleted or suspended, then performing the second operation associated with the tag's permission ID based on the the terminal device's permission identifier management includes deleting or suspending the terminal device's permission identifier specified in the terminal device's permission identifier management information.

[00122] In one embodiment, if the tag's permission ID management information includes a first block of pointing information, then performing a second operation related to the tag's permission ID based on the tag's permission ID management information includes changing Permission ID of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device.

[00123] In one embodiment, if the tag's proxy ID management information includes a second block of pointing information, then performing a second operation related to the tag's proxy ID based on the tag's proxy ID management information includes transmitting a second type of end device permission identifier, if it is necessary to transmit the end device permission identifier.

[00124] In one implementation, performing the second operation associated with the tag's proxy ID, based on the tag's proxy ID management information, includes at least one of the following:

performing a corresponding operation on the network proxy ID of the terminal device based on the proxy ID management information of the terminal device;

performing an appropriate operation on the factory proxy ID of the terminal based on the proxy ID management information of the terminal;

transfer of the factory authorization identifier of the terminal device;

transmitting a permission identifier of a terminal of the second type;

updating the network to which the end device's network permission ID applies.

[00125] In one embodiment, if the tag's permission ID management information includes indication information about deleting or suspending the tag's permission ID, then

performing an appropriate operation on the network proxy ID of the terminal based on the management information of the proxy ID of the terminal device includes at least one of the following: deleting or suspending the network proxy ID of the terminal device, or deleting or suspending the network information to which it applies network authority identifier of the terminal device.

[00126] Optionally, if the tag's network proxy ID is present, delete the tag's network proxy ID or suspend the TS's network proxy ID and/or remove information about the network to which the tag's network proxy ID applies or suspend information about the network to which the network permission identifier of the terminal device applies. If a plurality of network authorization identifiers of a terminal device are present, then all network authorization identifiers of the terminal device are deleted or all network authorization identifiers of the terminal device are suspended and/or information about the network to which all network authorization identifiers of the terminal device apply is deleted or the information about the network to which all of the endpoint's network permission identifiers apply.

[00127] In one embodiment, if the tag's proxy ID management information includes the identity of the network being the updated network to which the tag's proxy ID is applied, then

performing a corresponding operation on the network proxy ID of the terminal device based on the management information of the proxy ID of the terminal device includes updating the network to which the network proxy ID of the terminal device is applied based on the network identification information.

[00128] In one embodiment, if the tag's proxy ID management information includes the identity of the network being the newly added network to which the tag's proxy ID is applied, then

performing a corresponding operation on the network proxy ID of the terminal device based on the proxy ID management information of the terminal device includes adding network identification information to those networks to which the network proxy ID of the terminal device is applied.

[00129] In one embodiment, if the tag's proxy ID management information includes the identification information of a network that is a network to which the tag's proxy ID does not apply, then

performing a corresponding operation on the network proxy ID of the terminal device based on the management information of the proxy ID of the terminal device includes deleting the network identity from those networks to which the network proxy ID of the terminal device is applied.

[00130] In one embodiment, after receiving the tag's permission ID management information, it further obtains the tag's permission ID management recovery information used to recover the permission id of the terminal that has been suspended, wherein

the restoring tag's permission ID management information includes at least the tag's permission ID recovery pointing information and/or the tag's permission ID to be restored.

[00131] In one embodiment, prior to obtaining the tag's proxy identity management information, the following is additionally performed:

obtaining request information that includes at least one of the following information blocks:

terminal device permission ID type information, first request information, terminal device permission factory ID request information, and terminal device permission factory ID request information, where information about the terminal device permission ID type is used to obtain the corresponding terminal device permission ID; the first request information is used to request all types of terminal authorization identifiers; and the tag's permission ID is a tag's permission id corresponding to the current permission of the tag;

transmitting the authorization ID information of the terminal based on the request information.

[00132] In one implementation, the tag's permission identifier is the tag's permission identifier corresponding to the current permission of the tag, and

the current permission of the end device is the set of permissions of the end device in the first network.

[00133] In one embodiment, the tag's proxy ID type includes at least the tag's factory proxy ID type and the tag's network proxy ID type.

[00134] In one implementation, if the request information includes information about the type of the terminal's credential identifier, then

the tag's permission ID information includes the corresponding tag's permission id.

[00135] In one embodiment, if the request information includes the request information of the tag's factory credential ID, then

The terminal's permission identifier information includes at least one of the following information blocks: a factory permission identifier of a terminal, an indication of the presence of a factory permission of a terminal, or an indication of the absence of a factory permission of a terminal.

[00136] In one implementation, if the request information includes request information about the presence of a factory authorization identifier of the terminal, then

the terminal's proxy ID information includes indication information of the presence of a factory proxy identifier of the terminal or an indication of absence of a factory proxy identifier of the terminal.

[00137] In one embodiment, if the request information includes first request information, then

the terminal's permission identifier information includes all types of terminal's permission identifiers corresponding to the current permission of the terminal.

[00138] In this embodiment of the present invention, the second communication device performs an operation related to the permission ID of the terminal device based on the permission ID management information of the terminal device transmitted by the network side in order to manage the permission ID of the terminal device so that the network and the terminal device agree used the permission ID of the target device.

[00139] FIG. 3 shows a method for managing tag authority IDs according to Embodiment 3 of the present invention applied to a third communication device. The third communication device includes at least a terminal device and a second communication network element (eg, a first network element RAN or a first network element CN). The control method includes the following steps.

[00140] Step 31: Transmit all tag permission identifiers corresponding to the tag's current permissions.

[00141] The current credentials of the terminal are the set of credentials of the terminal in the first network;

the tag's permission ID includes at least the network tag's permission id and/or the factory tag's permission id.

[00142] In one implementation, if the fourth condition is met, all tag permission identifiers corresponding to the tag's current permissions are transmitted, where the fourth condition includes at least one of the following situations:

the terminal device goes into standby mode;

the end device returns to connect mode from standby mode;

the end device is disconnected from the first network;

the terminal device resets its registration in the first network;

the terminal registers for the first time in the first network;

the end device connects to the first network for the first time.

[00143] In one embodiment, the transmission of all tag authority identifiers corresponding to the current authority of the terminal device includes the transmission to the core network element of all tag authority identifiers corresponding to the current authority of the terminal device in an encrypted context.

[00144] In this embodiment of the present invention, the third communication device transmits to the network side all tag permission IDs corresponding to the current permission of the tag device, so that the network side can determine what type of tag permission ID should be applied and how best to manage the tag permission ID, and the network and end device have consistently used the end device's authority identifier.

[00145] FIG. 4 shows a method for managing tag authority IDs according to Embodiment 4 of the present invention applied to a fourth communication device. The fourth communication device includes at least a first communication network element (eg, a first network element CN or a first network element RAN). The control method includes the following steps.

[00146] Act 41: If the second condition is met, send request information including at least one of the following information blocks:

information about the type of identifier of the authority of the end device;

first request information;

request information of the factory authorization identifier of the terminal device;

request information about the presence of a factory authorization identifier of the end device.

[00147] The information about the tag's permission ID type is used to obtain the corresponding tag's permission ID.

[00148] The first request information is used to query all types of tag permission IDs, and the tag permission ID is a tag permission ID corresponding to the current permission of the tag.

[00149] The second condition assumes that there is no factory tag authority identifier.

[00150] In one implementation, the tag's permission identifier is a tag's permission identifier corresponding to the current tag's permission, and

the current permission of the end device is the set of permissions of the end device in the first network.

[00151] In one implementation, the tag's proxy ID type includes at least the tag's factory proxy ID type and the tag's network proxy ID type.

[00152] In this embodiment of the present invention, the fourth communication device requests the tag's proxy ID so that the network and the tag consistently use the tag's proxy ID.

[00153] FIG. 5 shows a method for managing tag authority IDs according to Embodiment 5 of the present invention applied to a third communication device. The third communication device includes at least a terminal device and a second communication network element (eg, a first network element RAN or a first network element CN). The control method includes the following steps.

[00154] Step 51: Obtain request information including at least one of the following information blocks:

information about the type of identifier of the authority of the end device;

first request information;

request information of the factory authorization identifier of the terminal device;

request information about the presence of a factory authorization identifier of the end device.

[00155] The tag permission type information is used to obtain the corresponding tag permission id, the first request information is used to query all types of tag permission ids, and the tag permission id is the tag permission id corresponding to the current tag permission.

[00156] Act 52: Transmit the tag's credential ID information based on the request information.

[00157] In one implementation, the tag's permission ID is the tag's permission ID corresponding to the current permission of the tag, and

the current permission of the end device is the permission of the end device in the first network.

[00158] In one embodiment, the tag's permission ID type includes at least the tag's factory permission ID type and the tag's network proxy ID type.

[00159] In one embodiment, if the request information includes information about the type of the terminal's credential identifier, then

the tag's permission ID information includes the corresponding tag's permission id.

[00160] In one implementation, if the request information includes the request information of the tag's factory credential ID, then

The terminal's permission identifier information includes at least one of the following information blocks: a factory permission identifier of a terminal, an indication of the presence of a factory permission of a terminal, or an indication of the absence of a factory permission of a terminal.

[00161] In one embodiment, if the request information includes first request information, then

the terminal's permission identifier information includes all types of terminal's permission identifiers corresponding to the current permission of the terminal.

[00162] In one embodiment, if the request information includes request information about the presence of a factory authorization identifier of the terminal, then

the terminal's proxy ID information includes indication information of the presence of a factory proxy identifier of the terminal or an indication of absence of a factory proxy identifier of the terminal.

[00163] The method for managing tag authority IDs in this embodiment of the present invention is described below with reference to relevant use cases.

[00164] In this embodiment of the present invention, the third communication device transmits, upon request from the network side, information about the authority ID of the terminal device so that the network and the terminal device consistently use the authority identifier of the terminal device.

[00165] Embodiment of Application Scenario 1.

[00166] In this embodiment of this application scenario, the process of deleting or suspending the authorization network ID information of a terminal device by a core network element is mainly described. As shown in FIG. 6, the method for managing tag authority IDs in this embodiment of the present invention includes the following steps.

[00167] Act 61: The core network element transmits to the terminal device, via the radio access network element, information about the control of the authority identifier of the terminal device.

[00168] The tag's proxy ID management information is presented in the embodiment of FIG. 1 and is therefore not described in detail here.

[00169] In this embodiment of the present invention, the core network element may, if necessary, transmit to the terminal device information about the management of the network authority identity of the terminal device.

[00170] In this embodiment of the present invention, the core network element uses a tag configuration change request message to convey tag network proxy identity management information.

[00171] Act 62: The tag performs a second operation related to the tag's permission ID based on the tag's permission ID management information.

[00172] The process for performing the second operation associated with the tag's credential identifier is shown in the embodiment of FIG. 2 and is therefore not described in detail here.

[00173] Step 63: In this embodiment of the present invention, if the core network element uses a tag change request message to convey tag network proxy identity management information, then the tag additionally needs to send a change request response to the core network end device configuration.

[00174] Action 64: Reset the connection between the terminal and the network.

[00175] Steps 65-67. When the third condition is met (the third condition is described in the embodiment of FIG. 2 and therefore is not described in detail here), the tag transmits the tag's factory proxy ID information.

[00176] In particular, the terminal device sends to the network a connection process completion message for Radio Resource Control (RRC) containing information about the factory authorization identifier of the terminal device.

[00177] Act 68: The radio access network element transmits to the core network element a primary UE message containing information about the terminal's factory proxy identifier.

[00178] Embodiment of Application Scenario 2.

[00179] In this embodiment of this application scenario, the process of deleting or suspending the authorization network ID information of a terminal device by a core network element is mainly described. As shown in FIG. 7, the method for managing tag authority IDs in this embodiment of the present invention includes the following steps.

[00180] Act 71: The core network element transmits to the terminal via the radio access network element information about the control of the authority identifier of the terminal.

[00181] The tag's proxy ID management information is presented in the embodiment of FIG. 1 and is therefore not described in detail here.

[00182] In this embodiment of the present invention, the core network element may, if necessary, convey to the terminal device the management information of the network authority identity of the terminal device.

[00183] In this embodiment of the present invention, the core network element uses a tag configuration change request message to convey tag network proxy identity management information.

[00184] Act 72: The terminal device performs a second operation related to the permission ID of the terminal device based on the management information of the permission ID of the terminal device.

[00185] The process for performing the second operation associated with the tag's credential identifier is shown in the embodiment of FIG. 2 and is therefore not described in detail here.

[00186] Step 73: In this embodiment of the present invention, if the core network element uses the tag's configuration change request message to convey tag's proxy network identity management information, then the tag should additionally send a change request response to the core network. end device configuration.

[00187] Action 74: The terminal disconnects from the network or resets its registration with the network.

[00188] Act 75: If the third condition is met (the third condition is described in the FIG. 2 embodiment and therefore not described in detail here), the tag transmits the tag's factory proxy ID information.

[00189] In particular, the terminal device sends to the core network element via the radio access network element an initial registration request message or a connection request message containing information about the factory authorization identifier of the terminal device.

[00190] Act 76: The core network element sends an initial request to establish a context message to the radio access network element containing information about the terminal's factory proxy identity.

[00191] Embodiment of Application Scenario 3.

[00192] In this embodiment of this application scenario, the process of transmitting information about all the credentials of the terminal device corresponding to the current credentials of the terminal device is mainly described. As shown in FIG. 8, the method for managing tag authority IDs in this embodiment of the present invention includes the following steps.

[00193] Act 81: When the fourth condition is met, information is transmitted about all tag permission identifiers corresponding to the current tag permission (this process is described in the embodiment of FIG. 3 and is therefore not described in detail here).

[00194] The tag's proxy ID includes at least the tag's network proxy ID type and/or the tag's factory proxy ID type.

[00195] In particular, the terminal device sends to the core network element via the radio access network element an initial registration request message, a connection request message, or a Tracking Area Update Request (TAU) message containing the factory authorization identifier of the terminal device and / or the Network Permission ID of the end device.

[00196] The core network element may choose to use one of the types of terminal authority identifiers.

[00197] Act 82: The core network element sends to the radio access network element an initial request to establish a context message containing a factory tag proxy ID and/or a network tag proxy ID selected by the core network element.

[00198] As shown in FIG. 9, one embodiment of the present invention further provides a communication device 90. The communication device 90 may be, among other things, a first communication network element (eg, a first network element CN or a first network element RAN). Communication device 90 includes:

an executing module 91 configured to perform a first operation associated with the terminal's authorization identifier and comprising at least one of the following:

deleting or suspending a terminal's authorization identifier;

changing the permission identifier of the first type terminal in the context of the terminal to the permission identifier of the second type terminal;

transmission of information about the management of the authority ID of the end device.

[00199] In one embodiment, the tag's proxy identity management information includes at least one of the following information blocks:

indication information about the removal or suspension of the authority identifier of the terminal device;

the authorization identifier of the end device to be removed or suspended;

a first block of indication information about changing a permission identifier of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device;

a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal;

the identification information of the network being the updated network to which the authorization identifier of the terminal device is applied;

the identification information of the network being the newly added network to which the authorization identifier of the terminal is applied;

the identity of the network, which is the network to which the terminal authorization identifier does not apply.

[00200] In one embodiment, the tag's proxy ID is a network tag's proxy ID.

[00201] In one embodiment, the executing module 91 is configured, with the first condition met, to perform the first operation associated with the terminal's authority identifier, the first condition including at least one of the following situations:

Endpoint has been configured with a Network Permission ID of Endpoint;

received a set of terminal device permissions corresponding to the factory permission identifier of the terminal device;

a match is obtained between the factory permission identifier of the terminal device and the permission set of the terminal device, and the permission set of the terminal device is consistent with the current permission of the terminal device;

received factory endpoint permission ID corresponding to the current endpoint permission.

[00202] The current permission of the terminal device is the set of permissions of the terminal device in the first network.

[00203] In one embodiment, if the tag's permission ID management information includes at least the tag's permission ID suspension indication information and/or the permission ID of the tag to be suspended.

[00204] The communication device further includes:

the first transmission module configured to perform the following action: after transmission of the permission ID management information of the terminal device, transmission of recovery information about the permission ID management of the terminal device, used to restore the permission ID of the terminal device, which was suspended, is transmitted.

[00205] The tag's permission ID management recovery information includes at least the tag's permission ID recovery indication information and/or the tag's permission ID to be restored.

[00206] In one embodiment, the communication device is a core network element or a radio access network element.

[00207] In one embodiment, the communications device further includes:

a second transmission module configured, under the second condition, to transmit request information including at least one of the following information blocks: terminal authorization ID type information, first request information, terminal authorization factory ID request information, and availability request information the factory authorization identifier of the target device.

[00209] The information about the tag's permission ID type is used to obtain the corresponding tag's permission ID.

[00209] The first request information is used to query all types of tag permission IDs, and the tag permission ID is a tag permission ID corresponding to the current permission of the tag.

[00210] The second condition assumes that there is no factory tag authority identifier.

[00211] In one implementation, the tag's permission ID is the tag's permission ID corresponding to the current tag's permission, and

the current permission of the end device is the set of permissions of the end device in the first network.

[00212] In one implementation, the tag's permission ID type includes at least the tag's factory permission ID type and the tag's network proxy ID type.

[00213] As shown in FIG. 10, one embodiment of the present invention further provides a communication device 100. The communication device 100 includes at least a terminal device and a second communication network element (eg, a first network element RAN or a first network element CN). In the control method, communication device 100 includes:

the first receiving module 101 configured to obtain terminal device proxy ID management information including at least one of the following information blocks:

indication information about the removal or suspension of the authority identifier of the terminal device;

the authorization identifier of the end device to be removed or suspended;

a first block of indication information about changing a permission identifier of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device;

a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal;

the identification information of the network being the updated network to which the authorization identifier of the terminal device is applied;

identification information of the network, which is the first added network to which the identifier of the powers of the terminal device is applied;

the identification information of the network, which is the network to which the authorization identifier of the terminal device does not apply;

an executing module 102 configured to perform a second operation related to the permission ID of the terminal device based on the management information of the permission ID of the terminal device.

[00214] In one embodiment, the tag's proxy ID is the tag's network proxy ID.

[00215] In one embodiment, the executing module 102 is configured, subject to the third condition, to perform a second operation related to the tag's proxy ID based on the tag's proxy ID management information.

[00216] The third condition includes at least one of the following situations:

the terminal device goes into standby mode;

the end device returns to connect mode from standby mode;

the end device is disconnected from the first network;

the terminal device resets its registration in the first network;

the terminal registers for the first time in the first network;

the end device connects to the first network for the first time.

[00217] In one implementation, the execution module 102 does at least one of the following:

performing a corresponding operation on the network proxy ID of the terminal device based on the proxy ID management information of the terminal device;

performing an appropriate operation on the factory proxy ID of the terminal based on the proxy ID management information of the terminal;

transfer of the factory authorization identifier of the terminal device;

transmitting a permission identifier of a terminal of the second type;

updating the network to which the end device's network permission ID applies.

[00218] In one embodiment, if the tag's permission ID management information includes the tag's permission ID to be deleted or suspended, then the executing module 102 is configured to delete or suspend the tag's permission ID specified in the authority ID management information of the terminal.

[00219] In one embodiment, if the tag's permission ID management information includes a first block of pointing information, then the execution module 102 is configured to change the first type of tag's permission ID in the context of the tag to the second type's tag permission ID.

[00220] In one embodiment, if the tag's permission ID management information includes a second block of pointing information, then the execution module 102 is configured to send a second type of tag permission ID if the tag's permission ID needs to be sent.

[00221] In one of the implementation options, if the information about managing the powers of the terminal device includes index information about the deletion or suspension of the identifier of the powers of the terminal device, then the executing module 102 is configured to perform at least one of the following actions: deleting or suspension The actions of the network identifier are the powers of the terminal device or the deletion or suspension of the information about the network to which the network identifier of the powers of the terminal device is applied.

[00222] In one embodiment, if the tag's proxy ID management information includes the identity of the network being the updated network to which the tag's proxy ID is applied, then the executing module 102 is configured to update the network to which the network ID is applied. the credentials of the end device, based on network identification information.

[00223] In one of the implementation options, if the information about the management of the end of the terminal device includes the identification information of the network, which is the first added to the network, to which the identifier of the end of the terminal device is applied, then the executing module 102 is configured to add identification information of the network to those networks to those networks to which the network identifier is applied to the powers of the end device.

[00224] In one of the implementation options, if the information about the management of the end of the terminal device includes the identification information of the network, which is a network that does not apply the identifier of the powers of the terminal device, then the executing module 102 is configured to delete the identification information of the network from those networks, to which the Endpoint Authority Network ID applies.

[00225] In one embodiment, communication device 100 further includes:

a second receiving module, configured to receive recovery information about the permission ID management of the terminal device, used to restore the permission ID of the terminal device, which has been suspended.

[00226] The restoring information on the management of the identifier of the powers of the terminal device includes at least the index information about the restoration of the identifier of the end of the terminal device and/or the identifier of the powers of the terminal device, which is required to restore.

[00227] In one of the implementation options, the communication device 100 additionally includes:

a third receiving module configured to receive request information including at least one of the following information blocks:

information on the type of identifier of the powers of the tip of the end device, the information of the first request, the information of the query of the factory identifier of the powers of the tip and the information about the presence of the factory identifier of the powers of the end device, where information on the type of identifier of the terminal device is used to obtain the appropriate identifier of the powers of the terminal device; Information of the first request is used to request all types of identifiers of the powers of the terminal device; and the identifier of the powers of the terminal device is the identifier of the powers of the terminal device corresponding to the current powers of the terminal device;

The transfer of information about the identifier is the powers of the tip of the information based on the request.

[00228] In one of the implementation options, the identifier of the end of the terminal device is the identifier of the powers of the terminal device corresponding to the current powers of the terminal device, and the current powers of the terminal device is a set of powers of the terminal device in the first network.

[00229] In one implementation, the tag's proxy ID type includes at least the tag's factory proxy ID type and the tag's network proxy ID type.

[00230] In one implementation, if the request information includes information about the type of the terminal's credential identifier, then

the tag's permission ID information includes the corresponding tag's permission id.

[00231] In one implementation, if the request information includes the request information of the tag's factory credential ID, then

The terminal's permission identifier information includes at least one of the following information blocks: a factory permission identifier of a terminal, an indication of the presence of a factory permission of a terminal, or an indication of the absence of a factory permission of a terminal.

[00232] In one implementation, if the request information includes request information about the presence of a tag's factory credential identifier, then

the terminal's proxy ID information includes indication information of the presence of a factory proxy identifier of the terminal or an indication of absence of a factory proxy identifier of the terminal.

[00233] In one embodiment, if the request information includes first request information, then

the terminal's permission identifier information includes all types of terminal's permission identifiers corresponding to the current permission of the terminal.

[00234] As shown in FIG. 11, one embodiment of the present invention further provides a communication device 110 that includes, among other things, a terminal device and a second communication network element (eg, a first network element RAN or a first network element CN). Communication device 110 includes:

a transmitting module 111 configured to transmit all tag authority identifiers corresponding to the tag's current authority, where

the current permissions of the terminal device is the set of permissions of the terminal device in the first network;

the tag's permission ID includes at least the network tag's permission id and/or the factory tag's permission id.

[00235] In one embodiment, the transmitter module 111 is configured with a fourth condition to transmit all tag authority identifiers corresponding to the tag's current authority, where the fourth condition includes at least one of the following situations:

the terminal device goes into standby mode;

the end device returns to connect mode from standby mode;

the end device is disconnected from the first network;

the terminal device resets its registration in the first network;

the terminal registers for the first time in the first network;

the end device connects to the first network for the first time.

[00236] In one embodiment, the transmitter module 111 is configured to send to the core network element all tag authority identifiers corresponding to the tag's current authority in an encrypted context.

[00237] As shown in FIG. 12, one embodiment of the present invention further provides communication device 120. Communication device 120 may be, among other things, a first communication network element (eg, a first network element CN or a first network element RAN). Communication device 120 includes:

the transmission module 121 configured under the second condition to transmit request information including at least one of the following information blocks: authorization ID type information of the terminal device, first request information, factory authorization ID request information of the terminal device, and availability request information the factory authorization identifier of the target device.

[00238] The information about the tag's permission ID type is used to obtain the corresponding tag's permission ID.

[00239] The first request information is used to query all types of tag permission IDs, and the tag permission ID is a tag permission ID corresponding to the current permission of the tag.

[00240] The second condition assumes that there is no factory tag authority identifier.

[00241] In one implementation, the tag's permission ID is the tag's permission ID corresponding to the current permission of the tag, and

the current permission of the end device is the set of permissions of the end device in the first network.

[00242] In one implementation, the tag's permission ID type includes at least the tag's factory permission ID type and the tag's network proxy ID type.

[00243] As shown in FIG. 13, one embodiment of the present invention further provides a communication device 130. The communication device 130 may be, among other things, a terminal device or a second communication network element (e.g., a first network RAN element or a first network element CN). Communication device 130 includes:

the receiving module 131 configured to receive request information including at least one of the following information blocks: information about the type of permission ID of the terminal device, information of the first request, request information of the factory permission ID of the terminal device, and request information about the presence of the factory permission ID of the terminal device. devices, where information about the type of the permission identifier of the terminal device is used to obtain the corresponding permission identifier of the terminal device; the first request information is used to request all types of terminal authorization identifiers; and the tag's permission ID is a tag's permission id corresponding to the current permission of the tag;

a transmitting module 132 configured to transmit the authorization ID information of the terminal device based on the request information.

[00244] In one embodiment, the tag's permission ID is the tag's permission ID corresponding to the current tag's permission, and the current tag's permission is the permission of the tag in the first network.

[00245] In one embodiment, the tag's permission ID type includes at least the tag's factory permission ID type and the tag's network proxy ID type.

[00246] In one implementation, if the request information includes information about the type of the terminal's credential identifier, then

the tag's permission ID information includes the corresponding tag's permission id.

[00247] In one embodiment, if the request information includes the request information of the terminal's factory credential identifier, then

The terminal's permission identifier information includes at least one of the following information blocks: a factory permission identifier of a terminal, an indication of the presence of a factory permission of a terminal, or an indication of the absence of a factory permission of a terminal.

[00248] In one embodiment, if the request information includes first request information, then

the terminal's permission identifier information includes all types of terminal's permission identifiers corresponding to the current permission of the terminal.

[00249] In one implementation, if the request information includes request information about the presence of a factory authorization identifier of the terminal device, then

the terminal's proxy ID information includes indication information of the presence of a factory proxy identifier of the terminal or an indication of absence of a factory proxy identifier of the terminal.

[00250] FIG. 14 is a schematic block diagram of a terminal device in accordance with another embodiment of the present invention. The terminal device 140 includes, among other things, components such as an RF unit 141, a network module 142, an audio output 143, an input unit 144, a sensor 145, a display 146, a user input unit 147, an interface unit 148, a memory 149, a processor 1410, and power supply 1411. Those skilled in the art will appreciate that the terminal structure shown in FIG. 14 is not the only possible one. The terminal device may include more or fewer components than shown in the figure, combine some components, or have a different arrangement of components. In this embodiment of the present invention, the terminal device may be, among other things, a mobile phone, tablet computer, laptop, personal digital assistant, vehicle on-board device, wearable device, pedometer or the like.

[00251] The RF unit 141 is configured to receive terminal device proxy ID management information including at least one of the following information blocks:

indication information about the removal or suspension of the authority identifier of the terminal device;

the authorization identifier of the end device to be removed or suspended;

a first block of indication information about changing a permission identifier of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device;

a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal;

the identification information of the network being the updated network to which the authorization identifier of the terminal device is applied;

the identification information of the network being the newly added network to which the authorization identifier of the terminal is applied;

the identity of the network, which is the network to which the terminal authorization identifier does not apply.

[00252] The processor 1410 is configured to perform a second operation related to the tag's proxy ID based on the tag's proxy ID management information.

[00253] Alternatively,

the RF unit 141 can be configured to send all tag authority identifiers corresponding to the tag's current authority, where

the current permissions of the terminal device is the set of permissions of the terminal device in the first network;

the tag's permission ID includes at least the network tag's permission id and/or the factory tag's permission id.

[00254] Alternatively,

the RF unit 141 can be configured to receive request information including at least one of the following information blocks: tag permission ID type information, first request information, tag factory permission ID request information, and factory permission ID request information. terminal device, where information about the type of permission identifier of the terminal device is used to obtain the corresponding permission identifier of the terminal device; the first request information is used to request all types of terminal authorization identifiers; and the terminal's permission identifier is the terminal's permission identifier corresponding to the current permission of the terminal, and

the processor 1410 can be configured to send information about the authorization identifier of the terminal device based on the information of the request.

[00255] It should be understood that in this embodiment of the present invention, the RF unit 141 can be configured to receive and transmit signals in the process of receiving/transmitting information or in the process of calling, and after receiving downlink information from the base station, can transmit information about downlink to processor 1410 for processing and may transmit uplink data to the base station. Typically, the RF unit 141 includes, among other things, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the RF unit 141 may further communicate with the network and other devices via a wireless communication system.

[00256] The terminal device provides wireless broadband Internet access to the user through the network module 142, such as helping the user to send and receive e-mail, surf the web, and access streaming media.

[00257] The audio output 143 can convert the audio data received by the RF unit 141 or the network module 142 or stored in the memory 149 into an audio signal and reproduce this audio signal as sound. In addition, audio output 143 may also provide an audio output (eg, to sound an alert when a call or message is received) associated with a particular function performed by terminal device 140. Audio output 143 includes a speaker, buzzer, telephone, and the like.

[00258] The input unit 144 is configured to receive an audio or video signal. The input unit 144 may include a graphics processing unit (GPU) 1441 and a microphone 1442. The graphics processor 1441 processes graphic data of a still image or video captured by an image capturing device (eg, a camera) in an image capture mode or a video capture mode. . The processed image frame may be displayed on display 146. The image frame processed by GPU 1441 may be stored in memory 149 (or other storage medium) or transmitted by RF unit 141 or network module 142. Microphone 1442 may receive sound and convert the sound into audio data. The processed audio data can be output converted into a telephone call format suitable for transmission of such audio data by the RF unit 141 to the mobile base station.

[00259] Terminal 140 may further include at least one sensor 145, such as an optical sensor, motion sensor, or other sensor. In particular, the optical sensor may include a light sensor and a proximity sensor. The light sensor may adjust the brightness of the display panel 1461 depending on the ambient light, and the proximity sensor may turn off the display panel 1461 and/or the backlight when the user brings the terminal device 140 to the ear. An accelerometer as a kind of motion sensor can determine accelerations in all directions (usually along three axes), determine the magnitude and direction of gravity when the terminal device is stationary, recognize the position of the terminal device in space (for example, to switch the screen between portrait and landscape modes, computer games and calibration of the position of the magnetometer in space), as well as perform functions related to vibration recognition (for example, for a pedometer and touches) and other tasks. The sensor 145 may further include a fingerprint sensor, a pressure sensor, an iris scanner, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like. A detailed description is not provided in this document.

[00260] The display 146 is configured to display information entered by the user or information provided to the user. The display 146 may include a display panel 1461, which may be implemented as a liquid crystal display (Liquid Crystal Display, LCD), organic LED (Organic Light-Emitting Diode, OLED), or their equivalents.

[00261] User input block 147 may be configured to receive digital or character information and generate a key input associated with user settings and the mobile terminal control function. In particular, the user input unit 147 may include a touch pad 1471 and other input devices 1472. The touch pad 1471, also referred to as a touch screen, may recognize a touch operation performed by a user on or near the touch panel (e.g., an operation performed by a user on the 1471 touchpad or next to the 1471 touchpad using any appropriate object or accessory such as a finger or stylus). The touch panel 1471 may be composed of two parts: a touch detection device and a touch controller. The touch detection device detects the direction of touching the screen by the user, detects the signal transmitted by the touch operation, and transmits the signal to the touch controller. The touch controller receives touch information from the touch detection device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 1410, and receives and executes the command sent by the processor 1410. In addition, the touch pad 1471 can be implemented in a variety of ways, for example, resistive, capacitive, infrared, or surface acoustic waves. In addition to the touchpad 1471, the user input unit 147 may also include other input devices 1472. In particular, other input devices 1472 may include, but are not limited to, a mechanical keyboard, a function key (e.g., a volume key or a power/ power off), trackball, mouse and joystick. A detailed description is not provided in this document.

[00262] In addition, the touch panel 1471 may include a display panel 1461. After the touch panel 1471 has detected a touch operation on or near the touch panel, the touch panel 1471 passes the touch operation to the processor 1410 to determine the type of touch event. The processor 1410 then provides the appropriate rendering on the display panel 1461 depending on the type of touch event. Although in FIG. 14, the touch panel 1471 and the display panel 1461 are used as two independent components to implement the input and output functions of the terminal device, the touch panel 1471 and the display panel 1461 may be integrated to implement the input and output functions of the terminal device in some embodiments of the present invention. This document does not impose restrictions on this aspect.

[00263] Interface box 148 serves as an interface between an external device and terminal device 140. For example, an external device may include a wired or wireless headphone port, an external power (or charger) port, a wired or wireless data port, a for a memory card, a port for connecting a device with a recognition module, an input / output port (input / output, I / O) of an audio signal, an input / output port (I / O) of a video signal, an input / output port for a headset and their analogues. Interface unit 148 may be configured to receive input (eg, information or power) from an external device and transmit the received input to one or more elements of terminal device 140, or to exchange data between terminal device 140 and an external device.

[00264] Memory 149 can be configured to store software and various data. The memory 149 may advantageously include a program storage area and a data storage area. The program storage area may contain an operating system, an application program required for the operation of at least one function (for example, a sound playback function and a display function), and so on. The data storage area may contain data created based on the use of a mobile phone (such as audio data and a phone book). In addition, memory 149 may include high speed random access memory or additional non-volatile memory, such as at least one magnetic disk storage device, flash memory, or other volatile solid state storage device.

[00265] The processor 1410 is the control center of the terminal device and uses various interfaces and lines to connect all components of the terminal device. By starting or executing the software and/or module stored in memory 149 and by retrieving data stored in memory 149, processor 1410 performs various functions and data processing of the terminal device, which provides general monitoring at the terminal device. Processor 1410 may include one or more processors. The processor 1410 may further integrate an application processor and a modem processor. The application processor mainly performs tasks related to the operating system, user interfaces, application programs, and so on. The modem processor primarily performs radio related tasks. Obviously, it is not necessary to integrate the modem processor into the 1410 processor.

[00266] End device 140 may further include a power supply 1411 (eg, a battery) that supplies power to all components. If necessary, the power supply 1411 can be logically connected to the processor 1410 using the power management system. This allows functions such as charge control, discharge control, and power management to be realized with the power management system.

[00267] In addition, the terminal device 140 includes some functional modules that are not shown in this document. A detailed description is not provided in this document.

[00268] One embodiment of the present invention further provides a communication device including a processor and a memory. In this embodiment of the present invention, the communication device further includes a computer program that is stored in memory and can be run on a processor. When a computer program is executed by a processor, the computer program implements the following step:

performing the first operation associated with the endpoint's authorization identifier and including at least one of the following:

deleting or suspending a terminal's authorization identifier;

changing the permission identifier of the first type terminal in the context of the terminal to the permission identifier of the second type terminal;

transmission of information about the management of the authority ID of the end device.

[00269] Optionally, the terminal's proxy ID management information may include at least one of the following information blocks:

indication information about the removal or suspension of the authority identifier of the terminal device;

the authorization identifier of the end device to be removed or suspended;

a first block of indication information about changing a permission identifier of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device;

a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal;

the identification information of the network being the updated network to which the authorization identifier of the terminal device is applied;

the identification information of the network being the newly added network to which the authorization identifier of the terminal is applied;

the identity of the network, which is the network to which the terminal authorization identifier does not apply.

[00270] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

if the first condition is met, the first operation associated with the endpoint's permission identifier is performed, where the first condition includes at least one of the following situations:

Endpoint has been configured with a Network Permission ID of Endpoint;

received a set of terminal device permissions corresponding to the factory permission identifier of the terminal device;

a match is obtained between the factory permission identifier of the terminal device and the permission set of the terminal device, and the permission set of the terminal device is consistent with the current permission of the terminal device;

received factory endpoint permission ID corresponding to the current endpoint permission.

[00271] The current permission of the terminal device is the set of permissions of the terminal device in the first network.

[00272] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

if the permission ID management information of the terminal device includes at least indication information about the suspension of the permission ID of the terminal device and/or the permission ID of the terminal device to be suspended;

then after the transmission of the permission ID management information of the terminal device, the transmission of the restoration permission ID management information of the terminal device is additionally performed, which is used to restore the permission ID of the terminal device, which was suspended, and

the restoring tag's permission ID management information includes at least the tag's permission ID recovery pointing information and/or the tag's permission ID to be restored.

[00273] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

before performing the first operation associated with the authorization identifier of the target device, the following is additionally performed:

if the second condition is met, the transmission of request information, including at least one of the following information blocks: information about the type of authorization identifier of the terminal device, information of the first request, information about the request of the factory authorization identifier of the terminal device, and information about the request about the presence of the factory authorization identifier of the terminal device.

[00274] The information about the tag's permission ID type is used to obtain the corresponding tag's permission ID.

[00275] The first request information is used to request all types of tag permission IDs, and the tag permission ID is a tag permission ID corresponding to the current permission of the tag.

[00276] The second condition assumes that there is no factory tag authority identifier.

[00277] Optionally, the tag permission ID is the tag permission ID corresponding to the current permission of the tag, and

the current permission of the end device is the set of permissions of the end device in the first network.

[00278] Optionally, the tag's proxy ID type includes at least the tag's factory proxy ID type and the tag's network proxy ID type.

[00279] One embodiment of the present invention further provides a terminal device including a processor and memory. In this embodiment of the present invention, the terminal device further includes a computer program that is stored in memory and can run on a processor. When a computer program is executed by a processor, the computer program implements the following steps:

obtaining information about the management of the authority identifier of the end device, which includes at least one of the following information blocks:

indication information about the removal or suspension of the authority identifier of the terminal device;

the authorization identifier of the end device to be removed or suspended;

a first block of indication information about changing a permission identifier of a first type terminal device in the context of a terminal device to a permission identifier of a second type terminal device;

a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal;

the identification information of the network being the updated network to which the authorization identifier of the terminal device is applied;

the identification information of the network being the newly added network to which the authorization identifier of the terminal is applied;

the identification information of the network, which is the network to which the authorization identifier of the terminal device does not apply;

performing a second operation related to the permission ID of the terminal based on the management information of the permission ID of the terminal.

[00280] Optionally, the tag's proxy ID may be a network tag's proxy ID.

[00281] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

performing a second operation related to the permission ID of the terminal device based on the management information of the permission ID of the terminal device, including the following actions:

if the third condition is met, performing a second operation related to the permission ID of the terminal device based on the management information of the permission ID of the terminal device.

[00282] The third condition includes at least one of the following situations:

the terminal device goes into standby mode;

the end device returns to connect mode from standby mode;

the end device is disconnected from the first network;

the terminal device resets its registration in the first network;

the terminal registers for the first time in the first network;

the end device connects to the first network for the first time.

[00283] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

performing a second operation associated with the terminal's proxy ID based on the terminal's proxy ID management information, including at least one of the following:

performing a corresponding operation on the network proxy ID of the terminal device based on the proxy ID management information of the terminal device;

performing an appropriate operation on the factory proxy ID of the terminal based on the proxy ID management information of the terminal;

transfer of the factory authorization identifier of the terminal device;

transmitting a permission identifier of a terminal of the second type;

updating the network to which the end device's network permission ID applies.

[00284] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

if the terminal's permission ID management information includes the permission ID of the terminal to be deleted or suspended, then

performing a second operation related to the permission ID of the terminal based on the permission ID management information of the terminal device includes deleting or suspending the permission ID of the terminal device indicated in the permission ID management information of the terminal device.

[00285] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

if the permission ID management information of the terminal device includes the first block of pointing information, then performing a second operation related to the permission ID of the terminal device based on the permission ID management information of the terminal device includes changing the permission ID of the first type terminal device in the context of the terminal device to the authorization identifier of the terminal device of the second type;

if the tag's permission ID management information includes a second block of pointing information, then performing a second operation related to the tag's permission ID based on the tag's permission ID management information includes transmitting a second type of tag's permission ID, if necessary pass the authorization identifier of the end device.

[00286] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

if the terminal device's permission identifier management information includes indication information about the deletion or suspension of the terminal device's permission identifier, then

performing an appropriate operation on the network proxy ID of the terminal based on the management information of the proxy ID of the terminal device includes at least one of the following: deleting or suspending the network proxy ID of the terminal device, or deleting or suspending the network information to which it applies network authority identifier of the terminal device.

[00287] Optionally, when the computer program is executed by the processor, the computer program further implements the following steps:

if the terminal device's proxy ID management information includes the identity of the network being the updated network to which the terminal's proxy ID is applied, then performing a corresponding operation on the network proxy ID of the terminal based on the proxy ID management information of the terminal includes updating the network to which the network tag authority ID is applied based on the network identity;

if the terminal device's proxy ID management information includes the identification information of the network being the newly added network to which the terminal's proxy ID is applied, then performing a corresponding operation on the network proxy ID of the terminal based on the proxy ID management information of the terminal includes adding network identification information to those networks to which the terminal authorization network identifier applies;

if the terminal device's proxy ID management information includes the identification information of a network that is a network to which the terminal's proxy ID does not apply, then performing a corresponding operation on the network proxy ID of the terminal based on the proxy ID management information of the terminal includes deleting network identification information from those networks to which the terminal authorization network identifier applies.

[00288] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

after receiving the permission ID management information of the terminal device, additionally, recovery information about the permission ID management of the terminal device is obtained, which is used to restore the permission ID of the terminal device that has been suspended, and

the restoring tag's permission ID management information includes at least the tag's permission ID recovery pointing information and/or the tag's permission ID to be restored.

[00289] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

before receiving information about the management of the authorization identifier of the end device, the following is additionally performed:

obtaining request information that includes at least one of the following information blocks:

terminal device permission ID type information, first request information, terminal device permission factory ID request information, and terminal device permission factory ID request information, where information about the terminal device permission ID type is used to obtain the corresponding terminal device permission ID; the first request information is used to request all types of terminal authorization identifiers; and the tag's permission ID is a tag's permission id corresponding to the current permission of the tag;

transmitting the authorization ID information of the terminal based on the request information.

[00290] Optionally, the tag's permission ID is the tag's permission id corresponding to the current tag's permission, and

the current permission of the end device is the set of permissions of the end device in the first network.

[00291] Optionally, the tag's proxy ID type includes at least the tag's factory proxy ID type and the tag's network proxy ID type.

[00292] Optionally, if the request information includes information about the tag's permission identifier type, then

the tag's permission ID information includes the corresponding tag's permission id.

[00293] Optionally, if the request information includes the request information of the factory authorization identifier of the terminal device, then

The terminal's permission identifier information includes at least one of the following information blocks: a factory permission identifier of a terminal, an indication of the presence of a factory permission of a terminal, or an indication of the absence of a factory permission of a terminal.

[00294] Optionally, if the request information includes request information about the presence of a factory authorization identifier of the terminal device, then

the terminal's proxy ID information includes indication information of the presence of a factory proxy identifier of the terminal or an indication of absence of a factory proxy identifier of the terminal.

[00295] Optionally, if the request information includes the first request information, then

the terminal's permission identifier information includes all types of terminal's permission identifiers corresponding to the current permission of the terminal.

[00296] One embodiment of the present invention further provides a terminal device including a processor and memory. In this embodiment of the present invention, the terminal device further includes a computer program that is stored in memory and can run on a processor. When a computer program is executed by a processor, the computer program implements the following step:

transfer of all end device permission identifiers corresponding to the current end device permissions, where

the current permissions of the terminal device is the set of permissions of the terminal device in the first network;

the tag's permission ID includes at least the network tag's permission id and/or the factory tag's permission id.

[00297] Optionally, when the computer program is executed by the processor, the computer program further implements the following step:

if the fourth condition is met, all endpoint permission identifiers corresponding to the current endpoint permission are transmitted, where the fourth condition includes at least one of the following situations:

the terminal device goes into standby mode;

the end device returns to connect mode from standby mode;

the end device is disconnected from the first network;

the terminal device resets its registration in the first network;

the terminal registers for the first time in the first network;

the end device connects to the first network for the first time.

[00298] One embodiment of the present invention further provides a communications device including a processor and a memory. In this embodiment of the present invention, the communication device further includes a computer program that is stored in memory and can be run on a processor. When a computer program is executed by a processor, the computer program implements the following step:

if the second condition is met, the transmission of request information, including at least one of the following information blocks: information about the type of authorization identifier of the terminal device, information of the first request, information about the request of the factory authorization identifier of the terminal device, and information about the request about the presence of the factory authorization identifier of the terminal device.

[00299] The information about the tag's permission ID type is used to obtain the corresponding tag's permission ID.

[00300] The first request information is used to query all types of tag permission IDs, and the tag permission ID is a tag permission ID corresponding to the current permission of the tag.

[00301] The second condition assumes the absence of a factory authorization identifier of the terminal device.

[00302] Optionally, the tag's permission ID is the tag's permission id corresponding to the current tag's permission, and

the current permission of the end device is the set of permissions of the end device in the first network.

[00303] Optionally, the tag's proxy ID type includes at least the tag's factory proxy ID type and the tag's network proxy ID type.

[00304] One embodiment of the present invention further provides a terminal device including a processor and memory. In this embodiment of the present invention, the terminal device further includes a computer program that is stored in memory and can run on a processor. When a computer program is executed by a processor, the computer program implements the following steps:

obtaining request information including at least one of the following information blocks: information about the type of permission identifier of the terminal device, information of the first request, information of the request information of the factory permission identifier of the terminal device, and information of the request information about the presence of the factory permission identifier of the terminal device, where the type information the terminal's permission identifier is used to obtain the corresponding terminal's permission identifier; the first request information is used to request all types of terminal authorization identifiers; and the tag's permission ID is a tag's permission id corresponding to the current permission of the tag;

transmitting the authorization ID information of the terminal based on the request information.

[00305] Optionally, the tag's permission ID is the tag's permission id corresponding to the current tag's permission, and

the current permission of the end device is the permission of the end device in the first network.

[00306] Optionally, the tag's proxy ID type includes at least the tag's factory proxy ID type and the tag's network proxy ID type.

[00307] Optionally, if the request information includes information about the terminal's credential identifier type, then

the tag's permission ID information includes the corresponding tag's permission id.

[00308] Optionally, if the request information includes the request information of the factory authorization identifier of the terminal device, then

The terminal's permission identifier information includes at least one of the following information blocks: a factory permission identifier of a terminal, an indication of the presence of a factory permission of a terminal, or an indication of the absence of a factory permission of a terminal.

[00309] Optionally, if the request information includes the first request information, then

the terminal's permission identifier information includes all types of terminal's permission identifiers corresponding to the current permission of the terminal.

[00310] Optionally, if the request information includes request information about the presence of a factory authorization identifier of the terminal device, then

the terminal's proxy ID information includes indication information of the presence of a factory proxy identifier of the terminal or an indication of absence of a factory proxy identifier of the terminal.

[00311] One embodiment of the present invention further provides a computer-readable storage medium. A computer program is stored on the computer-readable storage medium, which, during its execution on the processor, implements the steps of an embodiment of a method for managing credentials of a terminal device with the same technical effects. To avoid repetition, the detailed description is no longer provided in this document. The computer-readable storage medium can be, for example, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk.

[00312] It should be noted that the terms "comprises", "includes" and any other variations thereof are not meant to be exclusive, so, for example, processes, methods, products, or devices that include a set of elements are not necessarily limited to the items directly listed, but may include other elements not listed or explicitly inherent in such processes, methods, products or devices. Unless otherwise restricted, an element preceded by "includes..." does not preclude the existence of other identical elements in processes, methods, articles, or devices that include such element.

[00313] Based on the above description of the implementations, it will be apparent to those skilled in the art that the methods in the above embodiments may be implemented as software in combination with the required common hardware platform, or as hardware alone. However, in most cases the described embodiments are preferred. Accordingly, the technical solutions described herein may be implemented as a software product alone or in combination with the prior art. A computer program product is stored on a storage medium (e.g., ROM/RAM, magnetic disk, or optical disk) and includes several instructions for a terminal device (which may be a mobile phone, computer, server, air conditioner). , network device or equivalent) in order to implement the method described in the embodiments of the present invention.

[00314] Those skilled in the art will appreciate that the blocks and algorithms in the examples described with reference to embodiments of the present invention may be implemented using electronic hardware or a combination of computer software and electronic hardware. The implementation of these functions through hardware or software depends on specific technical tasks and technical limitations. Specialists in the art can use various ways to implement the described functions for each specific technical problem, which are also included in the scope of legal protection for this invention.

[00315] It will be apparent to those skilled in the art that for convenience and brevity of the detailed description of the operation of the above system, device, and unit, reference may be made to the corresponding process in the above embodiments of this method without repeating the description.

[00316] It should be understood that the apparatus and method described in the embodiments of this invention may have other implementations. In particular, the described embodiment of the apparatus only serves as an example. For example, blocking serves only to logically separate functions and in practice can be implemented in a different way. For example, many blocks or components may be combined or integrated into another system, and some elements may be omitted or excluded. In addition, the mutual interfaces, direct interfaces, and communication channels shown or described may be implemented using certain interfaces. Indirect interfaces or communication channels between devices or units can be implemented in electronic, mechanical or other forms.

[00317] Blocks described as separate parts may or may not be physically separated, and parts shown as separate blocks may or may not be physical blocks, may be adjacent, or may be distributed across multiple network elements. Some or all of the blocks may be selected based on the actual requirements of the technical task to achieve a technical effect.

[00318] In addition, functional units in embodiments of the present invention may be fully or partially integrated into a single processing unit, or be separate physical units.

[00319] If the functions are implemented as a software functional block and sold or used as a separate product, then such functions may be stored on a computer-readable storage medium. Accordingly, the technical solutions described herein may be implemented as a software product alone or in combination with the prior art. The computer program product is stored on a storage medium and contains a set of instructions to enable a computing device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the actions in accordance with the method described in the embodiments of the present invention. The above storage medium can be any storage medium capable of storing program code, including a USB flash drive, removable hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk.

[00320] It will be apparent to those skilled in the art that all or some of the processes according to the methods described in the embodiments of this invention may be implemented as a computer program that controls associated hardware. The program may be stored on a computer-readable medium. When the program is executed, the steps of the embodiments of this method may be performed. The above storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), random access memory (Random Access Memory, RAM), or the like.

[00321] It is obvious that the described options can be implemented in the form of hardware, software, firmware, middleware, microcode, or combinations thereof. In the case of a hardware implementation, any module, block, auxiliary unit, auxiliary module or other component can be made in the form of one or more application specific integrated circuits (Application Specific Integrated Circuit, ASIC), digital signal processors (Digital Signal Processor, DSP), digital signal processing devices (DSP Device, DSPD), programmable logic devices (Programmable Logic Device, PLD), programmable logic integrated circuits (Field-Programmable Gate Array, FPGA), general purpose processors, controllers, microcontrollers, microprocessors and other electronic components or their combinations to implement the functions described in this invention.

[00322] In the case of software implementation, the methods described in embodiments of this invention may be implemented as modules (eg, processes or functions) that perform the functions that are described in this invention. The software code may be stored in memory and executed by a processor. Memory can be implemented both inside the processor and outside the processor.

[00323] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the above specific embodiments. The above specific implementation options are only illustrative and not restrictive. As indicated herein, those skilled in the art may develop other embodiments based on the same principles and therefore within the scope of protection for this invention.

Claims (103)

1. A method for managing terminal device authority identifiers applied to a first communication device, wherein the first communication device includes at least one of the following: a core network element (CN element) of the first network or a Radio Access Network (RAN) element of the first networks and which includes: performing the first operation associated with the endpoint's authorization identifier and including at least one of the following: deleting or suspending a terminal's authorization identifier; changing the permission identifier of the first type terminal in the context of the terminal to the permission identifier of the second type terminal; transmitting the permission ID management information of the terminal device to another terminal device or another RAN element of the first network; where the terminal's proxy identity management information includes at least one of the following information blocks: indication information about the removal or suspension of the authority identifier of the terminal device; the authorization identifier of the end device to be removed or suspended; the second block of indication information about the transmission of the authority identifier of the terminal device of the second type, if it is necessary to transmit the authority identifier of the terminal device. 2. The method of claim 1, wherein the tag's proxy identifier is a network tag's proxy identifier. 3. The method of claim. 1, where, if the first condition is met, the first operation associated with the authorization identifier of the terminal device is performed, and the first condition includes at least one of the following situations: Endpoint has been configured with a Network Permission ID of Endpoint; received a set of terminal device permissions corresponding to the factory permission identifier of the terminal device; a match is obtained between the factory permission identifier of the terminal device and the permission set of the terminal device, and the permission set of the terminal device is consistent with the current permission of the terminal device; received factory endpoint permission ID corresponding to the current endpoint permission, where the current permission of the end device is the set of permissions of the end device in the first network. 4. The method according to claim 1, where if the terminal device's permission identifier management information includes at least the terminal device's permission identifier suspension indication information and/or the permission identifier of the terminal device to be suspended, then after the transmission of the permission ID management information of the terminal device, the transmission of the restoration permission ID management information of the terminal device is additionally performed, which is used to restore the permission ID of the terminal device, which was suspended, and the restoring tag's permission ID management information includes at least the tag's permission ID recovery pointing information and/or the tag's permission ID to be restored. 5. The method of claim. 1, where before performing the first operation associated with the authorization identifier of the terminal device, the following is additionally performed: if the second condition is met, the transmission of request information, which includes at least one of the following information blocks: information about the type of authorization identifier of the terminal device, information of the first request, information about the request of the factory authorization identifier of the terminal device, and request information about the presence of the factory authorization identifier of the terminal device, Where information about the type of the authorization identifier of the terminal device is used to obtain the corresponding authorization identifier of the terminal device; the first request information is used to query all types of tag permission IDs, and the tag permission ID is a tag permission ID corresponding to the current permission of the tag; the second condition assumes that there is no factory endpoint authorization identifier. 6. The method according to claim 5, where the endpoint's permission identifier is the endpoint's permission identifier corresponding to the current permission of the endpoint, and the current endpoint permission is the set of endpoint permissions on the first network, and/or the endpoint permission ID type includes at least the endpoint factory permission ID type and the network endpoint permission ID type. 7. A terminal device authority ID management method applied to a second communication device, wherein the second communication device includes at least one of the following: a core network element (CN element) of the first network or a Radio Access Network (RAN) element of the first network , and including: obtaining information about the management of the authority identifier of the end device, which includes at least one of the following information blocks: indication information about the removal or suspension of the authority identifier of the terminal device; the authorization identifier of the end device to be removed or suspended; a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal; performing a second operation related to the permission ID of the terminal device based on the management information of the permission ID of the terminal device, wherein performing the second operation associated with the tag's permission ID based on the tag's permission ID management information includes at least one of the following: performing a corresponding operation on the network proxy ID of the terminal device based on the proxy ID management information of the terminal device; performing an appropriate operation on the factory proxy ID of the terminal based on the proxy ID management information of the terminal; transfer of the factory authorization identifier of the terminal device; transmitting a permission identifier of a terminal of the second type; updating the network to which the end device's network permission ID applies. 8. The management method of claim 7, wherein the tag's proxy ID is a network tag's proxy ID. 9. The management method of claim 7, wherein performing the second operation associated with the tag's permission ID based on the tag's permission ID management information includes: if the third condition is met, perform the second operation associated with the permission ID of the terminal device based on the management information of the permission ID of the terminal device, where the third condition includes at least one of the following situations: the terminal device goes into standby mode; the end device returns to connect mode from standby mode; the end device is disconnected from the first network; the terminal device resets its registration in the first network; the terminal registers for the first time in the first network; the end device connects to the first network for the first time. 10. The control method according to claim 7, where if the permission ID management information of the terminal device includes the permission ID of the terminal device to be deleted or suspended, then performing a second operation related to the permission ID of the terminal device based on the permission ID management information of the terminal device includes deleting or suspending the permission ID of the terminal device specified in the management information of the permission ID of the terminal device; if the permission ID management information of the terminal device includes the first block of pointing information, then performing a second operation related to the permission ID of the terminal device based on the permission ID management information of the terminal device includes changing the permission ID of the first type terminal device in the context of the terminal device to the authorization identifier of the terminal device of the second type; if the tag's permission ID management information includes a second block of pointing information, then performing a second operation related to the tag's permission ID based on the tag's permission ID management information includes transmitting a second type of tag's permission ID, if necessary pass the authorization identifier of the end device. 11. The control method according to claim 7, where if the terminal device's permission identifier management information includes indication information about the deletion or suspension of the terminal device's permission identifier, then performing an appropriate operation on the network proxy ID of the terminal based on the management information of the proxy ID of the terminal device includes at least one of the following: deleting or suspending the network proxy ID of the terminal device, or deleting or suspending the network information to which it applies network authority identifier of the terminal device. 12. The control method according to claim 7, where if the terminal device's proxy ID management information includes the identity of the network being the updated network to which the terminal's proxy ID is applied, then performing a corresponding operation on the network proxy ID of the terminal based on the proxy ID management information of the terminal includes updating the network to which the network tag authority ID is applied based on the network identity; if the terminal device's proxy ID management information includes the identification information of the network being the newly added network to which the terminal's proxy ID is applied, then performing a corresponding operation on the network proxy ID of the terminal based on the proxy ID management information of the terminal includes adding network identification information to those networks to which the terminal authorization network identifier applies; if the terminal device's proxy ID management information includes the identification information of a network that is a network to which the terminal's proxy ID does not apply, then performing a corresponding operation on the network proxy ID of the terminal based on the proxy ID management information of the terminal includes deleting network identification information from those networks to which the terminal authorization network identifier applies. 13. The control method according to claim 7, where after receiving the permission ID management information of the terminal device, additionally, recovery information about the permission ID management of the terminal device is obtained, which is used to restore the permission ID of the terminal device that has been suspended, and the restoring tag's permission ID management information includes at least the tag's permission ID recovery pointing information and/or the tag's permission ID to be restored. 14. The control method according to claim 7, where before receiving information about the management of the authorization identifier of the end device, the following is additionally performed: obtaining request information including at least one of the following information blocks: information about the type of permission identifier of the terminal device, information of the first request, information of the request information of the factory permission identifier of the terminal device, and information of the request information about the presence of the factory permission identifier of the terminal device, where the type information the terminal's permission identifier is used to obtain the corresponding terminal's permission identifier; the first request information is used to request all types of terminal authorization identifiers; and the tag's permission ID is a tag's permission id corresponding to the current permission of the tag; transmitting the authorization ID information of the terminal based on the request information. 15. The control method according to claim 14, where the endpoint's permission identifier is the endpoint's permission identifier corresponding to the current permission of the endpoint, and the current permission of the terminal device is the set of permissions of the terminal device in the first network; and/or the endpoint permission ID type includes at least the endpoint factory permission ID type and the network endpoint permission ID type. 16. The control method according to claim 15, where if the request information includes information about the terminal's credential identifier type, then the tag's permission ID information includes a corresponding tag's permission id; or if the request information includes the request information of the factory authorization identifier of the terminal device, then the terminal's permission ID information includes at least one of the following information blocks: a factory permission identifier of the terminal, an indication of the presence of a factory permission of the terminal, or an indication of the absence of a factory permission of the terminal; or if the request information includes request information about the presence of a factory authorization identifier of the terminal device, then the terminal's proxy ID information includes an indication of the existence of a factory proxy of the terminal or an indication of the absence of a factory proxy of the terminal; or if the request information includes the first request information, then the terminal's permission identifier information includes all types of terminal's permission identifiers corresponding to the current permission of the terminal. 17. Communication device, including: an executing module configured to perform the first operation associated with the endpoint's authorization identifier, which includes at least one of the following: deleting or suspending a terminal's authorization identifier; changing the permission identifier of the first type terminal in the context of the terminal to the permission identifier of the second type terminal; transmitting information about the management of the authority ID of the terminal device; where the authority ID management information of the terminal includes at least one of: indication information about the removal or suspension of the authority identifier of the terminal device; the authorization identifier of the end device to be removed or suspended; the second block of indication information about the transmission of the authority identifier of the terminal device of the second type, if it is necessary to transmit the authority identifier of the terminal device. 18. Communication device, including: the first receiving module configured to receive end device proxy identity management information that includes at least one of the following information blocks: indication information about the removal or suspension of the authority identifier of the terminal device; the authorization identifier of the end device to be removed or suspended; a second block of indication information about transmitting a proxy ID of a second type terminal if it is necessary to transmit a proxy ID of the terminal; And an executing module configured to perform a second operation related to the permission ID of the target device based on the management information of the permission ID of the terminal device, where the executing module is additionally configured to do at least one of the following: performing a corresponding operation on the network proxy ID of the terminal device based on the proxy ID management information of the terminal device; performing an appropriate operation on the factory proxy ID of the terminal based on the proxy ID management information of the terminal; transfer of the factory authorization identifier of the terminal device; transmitting a permission identifier of a terminal of the second type; updating the network to which the end device's network permission ID applies.

Images