Information processing method and apparatus, communication device, and readable storage medium

Abstract

This application discloses an information processing method, apparatus, communication device, and readable storage medium, belonging to the field of communication technology. The information processing method in this application includes: a terminal performing operations related to activating and / or deactivating subscriber data based on the number of device identifiers on the terminal.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an information processing method, apparatus, communication equipment, and readable storage medium. Background Technology

[0002] In existing networks, terminal device identifiers are pre-configured on the terminal. For the Universal Subscriber Identity Module (USIM), the IMEI is pre-configured on the SIM card slot, and the USIM is automatically bound to the corresponding terminal device identifier after insertion. Existing networks may initiate device identifier verification for the terminal during registration to prevent unauthorized terminals from accessing the network via the operator's USIM. In private network scenarios, a terminal may have multiple certificates and / or subscription data. However, the number of pre-configured terminal device identifiers on the terminal may be less than the number of certificates and / or subscription data on the terminal. This results in some certificates and / or subscription data not having a bound terminal device identifier. When a terminal uses these certificates and / or subscription data to access the network, it will fail the network's terminal device identifier verification. These issues need to be addressed. Summary of the Invention

[0003] This application provides an information processing method, apparatus, communication device, and readable storage medium, which can support network verification of terminal device identification on the one hand, and reduce the waste of device identification on the other hand.

[0004] In a first aspect, an information processing method is provided, comprising: a terminal performing operations related to activating and / or deactivating subscriber data based on the number of device identifiers of the terminal;

[0005] The subscriber data includes at least one of the following: certificates, contract data.

[0006] Secondly, an information processing method is provided, applied to a network-side device, comprising: sending a first indication information to a terminal, the first indication information being used to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required.

[0007] Thirdly, an information processing apparatus is provided, comprising: a first execution module, configured to perform operations related to activating and / or deactivating subscriber data based on the number of device identifiers of the terminal;

[0008] The subscriber data includes at least one of the following: certificates, contract data.

[0009] Fourthly, an information processing apparatus is provided, comprising: a first sending module, wherein the first indication information is used to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required.

[0010] Fifthly, an information processing method is provided, comprising: upon determining that a second condition is met, a terminal performs a first operation; wherein the first operation includes at least one of the following: binding a device identifier to first subscriber data, and sending the device identifier to a first network;

[0011] The second condition includes at least one of the following: the first subscriber data is subscriber data activated on the terminal; the terminal uses the first subscriber data to access the first network; the first network requires device identification verification of the terminal; and the device identification is a valid terminal device identification in the first network.

[0012] The device identifier is the device identifier bound to the first subscriber's data;

[0013] The subscriber data includes at least one of the following: certificates, contract data.

[0014] A sixth aspect provides an information processing method, comprising: upon determining that a third condition is met, a terminal performs a second operation, the second operation comprising at least one of the following:

[0015] Set the first device identifier to an invalid device identifier in the first network;

[0016] The first subscriber's data is not bound to the first device identifier;

[0017] When the first subscriber data is bound to the first device identifier, access to the first network using the first subscriber data is prohibited;

[0018] When the first subscriber data is bound to the first device identifier, the first subscriber data is activated for scenarios where the device resides and / or accesses the first network.

[0019] If the first subscriber data has already been bound to the first device identifier, unbind the first subscriber data from the first device identifier;

[0020] Bind the second device identifier to the first subscriber data;

[0021] If the first subscriber data is not bound to a device identifier, then bind a device identifier to the first subscriber data;

[0022] The third condition includes one of the following: receiving first information from the first network and confirming that the first device identifier is not a legitimate device identifier of the first network;

[0023] The first information is used to indicate at least one of the following: the terminal device is invalid, or the device identifier of the terminal is invalid;

[0024] The subscriber data includes at least one of the following: certificates, contract data.

[0025] In a seventh aspect, an information processing apparatus is provided, the apparatus including a second execution module;

[0026] The second execution module is configured to, upon determining that a second condition is met, have the terminal perform a first operation; wherein the first operation includes at least one of the following: binding a device identifier to first subscriber data, and sending the device identifier to a first network; wherein the second condition includes at least one of the following: the first subscriber data is subscriber data activated on the terminal, the terminal uses the first subscriber data to access the first network, the first network requires device identifier verification of the terminal, the device identifier is a valid terminal device identifier in the first network, and the device identifier is the device identifier bound to the first subscriber data; the subscriber data includes at least one of the following: a certificate, and subscription data.

[0027] Eighthly, an information processing apparatus is provided, characterized in that the apparatus includes a third execution module; the third execution module is configured to, upon determining that a third condition is met, have a terminal perform a second operation, the second operation including at least one of the following:

[0028] Set the first device identifier to an invalid device identifier in the first network;

[0029] The first subscriber's data is not bound to the first device identifier;

[0030] When the first subscriber data is bound to the first device identifier, access to the first network using the first subscriber data is prohibited;

[0031] When the first subscriber data is bound to the first device identifier, the first subscriber data is activated for scenarios where the device resides and / or accesses the first network.

[0032] If the first subscriber data has already been bound to the first device identifier, unbind the first subscriber data from the first device identifier;

[0033] Bind the second device identifier to the first subscriber data;

[0034] If the first subscriber data is not bound to a device identifier, then bind a device identifier to the first subscriber data;

[0035] The third condition includes one of the following: receiving first information from the first network and confirming that the first device identifier is not a legitimate device identifier of the first network;

[0036] The first information is used to indicate at least one of the following: the terminal device is invalid, or the device identifier of the terminal is invalid;

[0037] The subscriber data includes at least one of the following: certificates, contract data.

[0038] A ninth aspect provides a terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the information processing method as described in the first aspect, or the steps of the information processing method as described in the fifth aspect, or the steps of the information processing method as described in the sixth aspect.

[0039] In a tenth aspect, a network-side device is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the information processing method as described in the second aspect.

[0040] Eleventhly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the fifth aspect, or the steps of the method as described in the sixth aspect.

[0041] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the fifth aspect, or the steps of the method as described in the sixth aspect.

[0042] In a thirteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a non-transient storage medium, the program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the fifth aspect, or the steps of the method as described in the sixth aspect.

[0043] In the embodiments of this application, when a terminal needs to be assigned a new temporary terminal identifier, or when a terminal needs to change its temporary terminal identifier, the first message sent to the network can reduce the impact on the network and reduce paging conflicts. Attached Figure Description

[0044] Figure 1This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0045] Figure 2 This is a flowchart illustrating an information processing method according to an embodiment of this application;

[0046] Figure 3 This is a flowchart illustrating another information processing method according to an embodiment of this application;

[0047] Figure 3A This is a flowchart illustrating another information processing method according to an embodiment of this application;

[0048] Figure 3B This is a flowchart illustrating another information processing method according to an embodiment of this application;

[0049] Figure 4 This is a flowchart illustrating the registration process in Embodiment 1 of this application;

[0050] Figure 5 This is a schematic diagram of the structure of an information processing device according to an embodiment of this application;

[0051] Figure 6 This is a schematic diagram of the structure of another information processing device according to an embodiment of this application;

[0052] Figure 6A This is a schematic diagram of the structure of another information processing device according to an embodiment of this application;

[0053] Figure 6B This is a schematic diagram of the structure of another information processing device according to an embodiment of this application;

[0054] Figure 7 This is a structural diagram of another communication device according to an embodiment of this application;

[0055] Figure 8 This is a schematic diagram of the structure of a terminal according to an embodiment of this application;

[0056] Figure 9 This is a schematic diagram of the structure of a network-side device according to an embodiment of this application. Detailed Implementation

[0057] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0058] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0059] Figure 1 This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include smartwatches, wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0060] In one alternative embodiment of this application, "capable" can mean at least one of the following: allow, support, prefer, or have priority in having capability. "Inability" can mean at least one of the following: disallow, not support, disallow, not prefer, or lack of capability.

[0061] In one optional embodiment of this application, obtaining or acquiring can be understood as acquiring from configuration, receiving, receiving after a request, acquiring through self-learning, inferring from unreceived information, or acquiring after processing received information. The specific method can be determined according to actual needs, and this embodiment does not limit this. For example, if a certain capability indication information sent by the device is not received, it can be inferred that the device does not support that capability.

[0062] In one optional embodiment of this application, the transmission may include a broadcast, a system message broadcast, or a response to a request followed by a return.

[0063] In one alternative embodiment of this application, "alone" and "independent" can mean the same thing and can be used interchangeably.

[0064] In one optional embodiment of this application, the communication device may include at least one of the following: network-side devices (including communication network elements) and terminals.

[0065] In one optional embodiment of this application, the communication network element may include at least one of the following: a core network element and a radio access network element.

[0066] In one optional embodiment of this application, a core network element (CN element) may embody one of the following: core network equipment, core network communication equipment, core network node, core network function, or core network unit. The core network elements, core network equipment, core network communication equipment, core network nodes, core network functions, and / or core network units may include, but are not limited to, at least one of the following: Mobility Management Entity (MME), Access Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Serving Gateway (SGW), PDN Gateway (PDN Gateway), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Serving GPRS Support Node (SGSN), Gateway GPRS Support Node (GGSN), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), and Application Function (AF), Equipment Identity Registration. Register (EIR).

[0067] In one optional embodiment of this application, the radio access network element (CN element) can embody one of the following: RAN equipment, RAN communication equipment, RAN node, RAN function, RAN unit. The RAN element, RAN equipment, RAN communication equipment, RAN node, and / or RAN function can include, but are not limited to, at least one of the following: 3GPP radio access network, non-3GPP radio access network, Centralized Unit (CU), Distributed Unit (DU), base station, evolved Node B (eNB), 5G base station (gNB), Radio Network Controller (RNC), base station (NodeB), Non-3GPP Interworking Function (N3IWF), Access Controller (AC) node, Access Point (AP) equipment, or Wireless Local Area Networks (WLAN) node, Non-3GPP Interworking Function (N3IWF).

[0068] In this application embodiment, the following problems need to be solved:

[0069] Question 1: When the amount of subscriber data (such as network certificates and / or subscription data) on a terminal exceeds the number of device identifiers, the terminal will fail to pass the network's terminal device identifier verification when accessing the network using only a portion of the subscriber data. It's easy to think of configuring a device identifier for each subscriber data entry. However, since a terminal can dynamically download multiple subscriber data entries, and the terminal's device identifiers are often pre-configured, it may still be insufficient to ensure that each subscriber data entry has a dedicated device identifier. Furthermore, the number of subscriber data entries that a terminal can simultaneously activate is limited, for example, registering with two networks at the same time. Therefore, configuring a device identifier for each subscriber data entry is a significant waste. One solution is for the terminal to maintain a large amount of subscriber data, but the number of simultaneously activated subscriber data entries should not exceed the terminal's device identifier limit. This addresses the issue of whether the network can support device identifier verification for the terminal while minimizing the waste of device identifiers.

[0070] Question 2: For non-UICC type subscriber data, which is stored on the terminal device (e.g., a virtual card) and not physically inserted or removed from the card slot, the binding between device identifiers and subscriber data can be flexibly established. Some device identifiers on the terminal are allowed to roam, while others are not. In a roaming scenario, even if roaming-allowed subscriber data is used, using a non-roaming device identifier may prevent access to the roaming network. This is because the roaming network may verify the device and find the device identifier invalid, leading to access failure. Therefore, the issue of how to bind subscriber data and device identifiers still needs to be resolved.

[0071] In one optional embodiment of this application, the network is a mobile communication network.

[0072] In one optional embodiment of this application, the device identifier is equivalent to the terminal device identifier.

[0073] In an optional embodiment of the present invention, activation can also be referred to as: valid, enabled. Invalid can mean not enabled, not present. In an optional embodiment of the present invention, a subscriber data invalid deregistration status, such as 5GMM-DEREGISTERED.NO-SUPI, indicates that the terminal has no corresponding valid subscriber data (e.g., USIM is unavailable, or subscriber data is unavailable).

[0074] In one optional embodiment of this application, idle time may be included.

[0075] In one optional embodiment of this application, the idle or available device identifier includes: a device identifier not bound to subscriber data, and a device identifier not in a registered state. For example, a terminal can use its device identifier to initiate emergency registration. In this case, in one implementation, even if the device identifier is not bound to any subscriber data, the device identifier is considered to be occupied and cannot be bound to subscriber data again. When the device identifier goes to register, the terminal can consider the device identifier to have returned to an idle state.

[0076] In an optional embodiment of the present invention, the subscriber data may be used for at least one of the following: terminal access to the network, network authentication and / or authorization of terminal access, and network identification of the terminal.

[0077] In an optional embodiment of the present invention, the network corresponding to the subscriber data is the network to which the terminal is subscribed. For example, if the terminal is subscribed to network A, the subscriber data corresponding to network A can be obtained before the subscriber data can be used to access network A and / or other networks that allow roaming.

[0078] In an optional embodiment of the invention, the certificate in the subscriber data is the subscriber's network certificate. In one embodiment, a set of subscriber data includes one or a set of certificates.

[0079] In an optional embodiment of the present invention, the subscription data in the subscriber data is the subscriber's subscription information on the subscription network. The subscription data may be a collection of the subscriber's subscription information for a set of network services, such as at least one of the following: voice, SMS, and data traffic.

[0080] In one implementation, subscriber data includes a terminal subscriber identifier. In this case, the terminal subscriber identifier can be a permanent terminal subscriber identifier (such as a SUPI (Subscription Permanent Identifier), IMSI).

[0081] In one implementation, a subscriber's data includes a network or a group of networks.

[0082] In one implementation, non-UICC type subscriber data may include at least one of the following: a virtual card, subscriber data stored on a terminal device. The subscriber data may be, for example, subscriber data from a non-public network.

[0083] In an optional embodiment of the present invention, a non-UICC type device identifier refers to a device identifier specifically for non-UICC type subscriber data;

[0084] In an optional embodiment of the present invention, the UICC type device identifier refers to a device identifier specifically for subscriber data that is not a UICC type.

[0085] A terminal device may have at least one of the following device identifiers: a device identifier of type UICC, or a device identifier of type non-UICC.

[0086] In an optional embodiment of the present invention, the network information includes at least one of the following: a network identifier and a network type. The network type includes at least one of the following: a public network (such as a PLMN) and a non-public network. The non-public network includes: an independent non-public network (such as an SNPN (Stand-alone Non-Public Network)) and an integrated non-public network (such as a PNI NPN (Public Network Integrated Non-Public Network)).

[0087] Each subscriber data pair is applied to an end-user identifier and / or a network, wherein each set of subscriber data can be used for a registration.

[0088] In an optional embodiment of the present invention, subscriber data of the Universal Integrated Circuit Card (UICC) type includes subscriber data stored in the UICC. UICC type subscriber data may be, for example, subscriber data in USIM format. UICC type subscriber data may be referred to as USIM.

[0089] In an optional embodiment of the present invention, non-UICC type subscriber data includes subscriber data that is not stored in UICC;

[0090] In an optional embodiment of the invention, subscriber data can be represented as a USIM, and a record in the subscriber data list is, for example, an entry of the "list of subscriber data" with the SNPN identity of the SNPN.

[0091] In one optional embodiment of this application, a subscriber can be understood as a UE, and a terminal with multiple subscribers can be represented as multiple UEs. From the network's perspective, a subscriber is a UE. When a terminal accesses the network through data from multiple subscribers, from the network's perspective, the terminal is multiple UEs.

[0092] In an optional embodiment of the present invention, the user or subscriber is a subscriber; generally, one subscriber can correspond to one certificate. One subscriber represents one UE. It is easy to understand that when a terminal device has multiple subscribers, it can represent multiple UEs.

[0093] In an optional embodiment of the present invention, the terminal user identifier may be a user terminal identifier (UE identifier);

[0094] In one optional embodiment of this application, the temporary terminal identifier includes: a temporary terminal user identifier and a temporary UE identifier.

[0095] In one optional embodiment of this application, the number of subscriber data that the terminal is simultaneously active represents the number of subscriber data that the terminal is simultaneously active (e.g., in an active state).

[0096] In one optional embodiment of this application, activated subscriber data or subscriber data that has been activated can both indicate subscriber data that is in an active state.

[0097] In one optional embodiment of this application, "accessing a network" means at least one of the following: residing in a network, selecting a network, or registering with a network. For example, accessing a first network can mean selecting, residing in, and / or registering with a first network.

[0098] In one optional embodiment of this application, the binding of subscriber data with device identifier includes: when accessing the network using the subscriber data, the device identifier provided to the network is the device identifier bound to the subscriber data.

[0099] In an optional embodiment of the present invention, the presentation (e.g., display) includes the presentation via the terminal's human-machine interface (MMI). Optionally, the human-machine interface can be a display unit of the terminal, which may include a display panel, and can be configured using a liquid crystal display, organic light-emitting diode, or the like. Optionally, "presentation" can be understood as displaying on the display unit.

[0100] The information processing method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0101] See Figure 2 , Figure 2 This is a flowchart of an information processing method provided in an embodiment of this application, which is applied to a terminal (such as a UE, ME). Figure 2 As shown, the method includes the following steps:

[0102] Step 21: The terminal performs activation and / or deactivation operations on subscriber data based on the number of device identifiers of the terminal;

[0103] The subscriber data includes at least one of the following: certificates, contract data.

[0104] In one implementation, the device identifier of the terminal is pre-configured in the terminal or obtained from the terminal manufacturer's server. A terminal may have one or more device identifiers.

[0105] Optionally, the terminal performs activation and / or deactivation of subscriber data operations based on the number of device identifiers, including at least one of the following:

[0106] The number of subscriber data activated simultaneously by the terminal is less than and / or equal to the total number of device identifiers of the terminal;

[0107] At most, a terminal can bind one device identifier to one subscriber data.

[0108] The terminal determines the number of subscriber data that can be activated simultaneously based on the number of device identifiers of the terminal.

[0109] The terminal determines the number of remaining subscriber data that can be activated simultaneously based on the number of idle device identifiers of the terminal.

[0110] Based on the number of device identifiers of the terminal, the terminal presents at least one of the following: the number of subscriber data that can be activated simultaneously, and the remaining number of subscriber data that can be activated simultaneously.

[0111] The terminal binds a device identifier to each activated subscriber's data;

[0112] When a terminal deactivates subscriber data, it unbinds the subscriber data from its corresponding device identifier.

[0113] When the terminal needs to activate the second subscriber data and there is no available device identifier, activate the first subscriber data.

[0114] The first subscriber data includes at least one of the following: activated subscriber data, and subscriber data already bound to a device identifier. In one embodiment, the first subscriber data may be deactivated subscriber data selected by the end user. The second subscriber data may be inactive subscriber data.

[0115] In one implementation, the unbound device identifier can be bound to other subscriber data.

[0116] In one implementation, a device identifier bound to one subscriber's data cannot be bound to other subscriber data.

[0117] The binding of subscriber data with device identifier includes at least one of the following: the terminal device identifier corresponding to the subscriber data is the device identifier; when the terminal accesses the network using the subscriber data, the terminal device identifier provided to the network is the subscriber bundle data bound to it.

[0118] In one implementation, the idle device identifier includes device identifiers that are not bound in the terminal.

[0119] For example, when no USIM is inserted into the USIM slot, the device identifier corresponding to the slot can be considered to be free.

[0120] For example, if the UICC has not downloaded eSIM, the device identifier corresponding to the UICC can be considered idle.

[0121] In one implementation, the idle device identifier can be used to bind a non-UICC type certificate and / or contract.

[0122] Optionally, the terminal determines the number of subscriber data that can be activated simultaneously based on the number of device identifiers of the terminal, including at least one of the following:

[0123] The terminal determines the maximum number of subscriber data that can be activated simultaneously based on the total number of terminal device identifiers.

[0124] The number of subscriber data that a terminal can activate simultaneously is less than and / or equal to the total number of device identifiers of the terminal.

[0125] In one implementation, after the step of determining the number of subscriber data that can be activated simultaneously, at least one of the following is presented: the number of subscriber data that can be activated simultaneously, the total number of device identifiers;

[0126] And / or,

[0127] After determining the number of remaining subscriber data that can be activated simultaneously, at least one of the following is presented: the number of remaining subscriber data that can be activated simultaneously, and the number of idle device identifiers.

[0128] In one implementation, the user chooses which subscriber data to activate or deactivate.

[0129] Optionally, the subscriber data includes at least one of the following: UICC type subscriber data, non-UICC type subscriber data, and subscriber data stored on the terminal device.

[0130] Optionally, the device identifier includes one of the following:

[0131] Device identifiers specific to subscriber data that are not UICC type;

[0132] Non-UICC subscriber data and UICC type subscriber data, common device identifier.

[0133] Optionally, the type of device identifier includes at least one of the following: Permanent Equipment Identifier (PEI), International Mobile Station Equipment Identity (IMEI), and International Mobile Station Equipment Identity and Software Version number (IMEISv).

[0134] Optionally, the terminal's operation of activating and / or deactivating subscriber data based on the number of device identifiers includes at least one of the following: Under a first condition, the terminal performs the operation of activating and / or deactivating subscriber data based on the number of device identifiers; wherein the first condition includes at least one of the following:

[0135] The network requires device identification verification of the terminal;

[0136] The amount of subscriber data stored and / or inserted on the terminal exceeds the number of device identifiers on the terminal.

[0137] In one implementation, the network requirement to verify the device identifier of the terminal includes the network requirement to verify the device identifier of the terminal corresponding to the subscriber data.

[0138] In one implementation, the network corresponding to the subscriber data includes at least one of the following: a network that uses the subscriber data for access and / or registration, and a contract network corresponding to the subscriber data.

[0139] Optionally, the method further includes at least one of the following:

[0140] Receive first indication information from the network, the first indication information being used to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required;

[0141] Receive a registration rejection reason from the network, the registration rejection reason being used to indicate that the terminal device is illegitimate;

[0142] Receive an identification request from the network, the identification request being used to request the device identification of the terminal.

[0143] In one implementation, the terminal can first attempt to register with the network. When the network requests the terminal's device identifier, the terminal can determine that the network needs to verify the terminal's device identifier.

[0144] In one implementation, the terminal may first attempt to register with the network. If the terminal fails to provide the network with its device identifier and / or receives a registration failure reason from the network, where the registration failure reason indicates that the terminal device is illegitimate, the terminal may determine that the network needs to verify the terminal's device identifier.

[0145] Optionally, activating subscriber data or having subscriber data activated includes at least one of the following:

[0146] The subscriber data is in a valid or activated state;

[0147] It can trigger the terminal to search for the network corresponding to the subscriber data;

[0148] The subscriber data enables access to or registration on the network.

[0149] The terminal accesses the network through the subscriber data and is in a registered state on the network;

[0150] The terminal accesses the network through the subscriber data and the state of the network does not include the deregistration state where the subscriber data is invalid;

[0151] The subscriber (e.g., UE) corresponding to the subscriber data is in a deregistered state on the network, and the deregistered state does not include the deregistered state where the subscriber data is invalid;

[0152] and / or

[0153] Deactivating subscriber data or having subscriber data deactivated includes at least one of the following:

[0154] The subscriber data is invalid.

[0155] The terminal cannot be triggered to search for the network corresponding to the subscriber data;

[0156] The terminal accesses the network through the subscriber data and is in a deregistered state in the network, or in a deregistered state where the subscriber data is invalid;

[0157] The subscriber (e.g., UE) corresponding to the subscriber data is in a deregistered state on the network, or the subscriber corresponding to the subscriber data is in a deregistered state where the subscriber data is invalid on the network.

[0158] In one implementation, after the terminal deactivates the subscriber data, it may not delete the data and may still retain the deactivated subscriber data.

[0159] In one embodiment, being able to access the network through the subscriber data includes at least one of the following: being able to register for the network using the subscriber data, the subscriber corresponding to the subscriber data being in a registered state on the network, and being able to use the network services using the subscriber data.

[0160] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0161] Optionally, the terminal performs activation and / or deactivation of subscriber data operations based on the number of device identifiers of the terminal, including at least one of the following:

[0162] The terminal performs operations to activate and / or deactivate non-UICC type subscriber data based on the number of non-UICC type device identifiers of the terminal;

[0163] The terminal performs operations to activate and / or deactivate UICC type subscriber data based on the number of device identifiers of the terminal's UICC type.

[0164] Optionally, if the second condition is determined to be met, the terminal performs a first operation; wherein the first operation includes at least one of the following:

[0165] Bind device identifier to the first subscriber's data.

[0166] Send the device identifier to the first network;

[0167] The second condition includes at least one of the following:

[0168] The first subscriber data is the subscriber data activated on the terminal.

[0169] The terminal accesses the first network using first subscriber data.

[0170] The first network requires device identification verification of the terminal.

[0171] The device identifier is a valid terminal device identifier in the first network.

[0172] The device identifier is the device identifier bound to the first subscriber's data;

[0173] The subscriber data includes at least one of the following: certificates, contract data.

[0174] Optionally, binding the device identifier for the first subscriber data includes: binding a valid terminal device identifier in the first network to the first subscriber data in the scenario of accessing the first network.

[0175] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0176] Optionally, if the third condition is determined to be met, the terminal performs the second operation;

[0177] The second operation includes at least one of the following:

[0178] Set the first device identifier to an invalid device identifier in the first network;

[0179] The first subscriber's data is not bound to the first device identifier;

[0180] When the first subscriber data is bound to the first device identifier, access to the first network using the first subscriber data is prohibited;

[0181] When the first subscriber data is bound to the first device identifier, the first subscriber data is activated for scenarios where the device resides and / or accesses the first network.

[0182] If the first subscriber data has already been bound to the first device identifier, unbind the first subscriber data from the first device identifier;

[0183] Bind the second device identifier to the first subscriber data;

[0184] If the first subscriber data is not bound to a device identifier, then bind a device identifier to the first subscriber data;

[0185] The third condition includes one of the following: receiving first information from the first network and confirming that the first device identifier is not a legitimate device identifier of the first network;

[0186] The first information is used to indicate at least one of the following: the terminal device is invalid, or the device identifier of the terminal is invalid;

[0187] The subscriber data includes at least one of the following: certificates, contract data.

[0188] Optionally, the third condition may also include at least one of the following:

[0189] The terminal uses the first subscriber's data to access the first network;

[0190] Before receiving the first information from the first network, the terminal sends the first device identifier to the first network;

[0191] The device identifier bound to the first subscriber's data is the first device identifier;

[0192] The terminal registers with the first network, and the registration is a non-urgent registration.

[0193] Optionally, the first device identifier includes at least one of the following: a terminal device identifier bound to the first subscriber data, a terminal device identifier provided to the first network, and a terminal device identifier that the first network confirms is invalid;

[0194] and / or

[0195] The second device identifier is a valid terminal device identifier in the first network;

[0196] and / or

[0197] When the first subscriber data is not bound to a device identifier, the device identifier bound to the first subscriber data is a valid terminal device identifier in the first network.

[0198] Optionally, setting the first device identifier as an invalid device identifier for the first network includes at least one of the following: prohibiting access to the first network using the first device identifier; prohibiting the sending of the first device identifier to the first network; and prohibiting binding the first device identifier to the subscriber data when accessing the first network using subscriber data.

[0199] The first subscriber data not being bound to the first device identifier includes: in scenarios where the first subscriber data is accessed through the first network, the first subscriber data is not bound to the first device identifier;

[0200] and / or

[0201] If the first subscriber data is already bound to the first device identifier, unbinding the first subscriber data from the first device identifier includes: for scenarios used to access the first network, if the first subscriber data is already bound to the first device identifier, unbinding the first subscriber data from the first device identifier.

[0202] and / or

[0203] The step of binding the second device identifier to the first subscriber data includes: for scenarios used to access the first network, binding the second device identifier to the first subscriber data;

[0204] and / or

[0205] When the first subscriber data is not bound to a device identifier, binding a device identifier to the first subscriber data includes: for scenarios used to access the first network, when the first subscriber data is not bound to a device identifier, binding a device identifier to the first subscriber data.

[0206] Optionally, setting the first device identifier to an invalid device identifier for the first network is only applicable to scenarios where access to the first network is not urgently registered;

[0207] and / or

[0208] The scenarios used for accessing the first network do not include the scenario of emergency registration of the first network.

[0209] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0210] It is easy to understand that this embodiment can support the network to verify the device identification of the terminal on the one hand, and reduce the waste of device identification on the other hand.

[0211] See Figure 3 , Figure 3 This is a flowchart illustrating an information processing method provided in an embodiment of this application. This method is applied to network-side devices (such as CN network elements (e.g., AMF, or EIR), or RAN network elements). Figure 3 As shown, the method includes the following steps:

[0212] Step 31: Send a first indication message to the terminal, the first indication message being used to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required.

[0213] When the network-side device is a RAN element, it can send the first indication information to the terminal via System Information Broadcast (SIB). It is easy to understand that this embodiment can, on the one hand, support the network in verifying the terminal's device identification, and on the other hand, reduce the waste of device identification resources.

[0214] See Figure 3A , Figure 3A This is a flowchart of another information processing method provided in an embodiment of this application, which is applied to a terminal (such as a UE, ME). Figure 3A As shown, the method includes the following steps:

[0215] Step 301: If the second condition is met, the terminal performs the first operation;

[0216] The first operation includes at least one of the following:

[0217] Bind device identifier to the first subscriber's data.

[0218] Send the device identifier to the first network;

[0219] The second condition includes at least one of the following:

[0220] The first subscriber data is the subscriber data activated on the terminal.

[0221] The terminal accesses the first network using first subscriber data.

[0222] The first network requires device identification verification of the terminal.

[0223] The device identifier is a valid terminal device identifier in the first network.

[0224] The device identifier is the device identifier bound to the first subscriber's data;

[0225] The subscriber data includes at least one of the following: certificates, contract data.

[0226] In one implementation, the first subscriber data binding device identifier is defined as follows:

[0227] The first subscriber data is the subscriber data activated on the terminal.

[0228] The terminal accesses the first network using first subscriber data.

[0229] The first network requires device identification verification of the terminal.

[0230] The device identifier is a valid terminal device identifier in the first network;

[0231] In one implementation, the device identifier is sent to the first network when the second condition includes at least one of the following:

[0232] The first subscriber data is the subscriber data activated on the terminal.

[0233] The terminal accesses the first network using first subscriber data.

[0234] The first network requires device identification verification of the terminal.

[0235] The device identifier is a valid terminal device identifier in the first network.

[0236] The device identifier is the device identifier for the first subscriber's data binding.

[0237] Optionally, binding the device identifier for the first subscriber data includes: binding a valid terminal device identifier in the first network to the first subscriber data in the scenario of accessing the first network.

[0238] In one implementation, the operation of binding the first subscriber data to a valid terminal device identifier in the first network is effective in scenarios where the data is used to access the first network. For example, in scenarios where the data is used to access the second network, the data bound to the first subscriber data could be a valid terminal device identifier in the second network.

[0239] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0240] See Figure 3B , Figure 3B This is a flowchart of another information processing method provided in an embodiment of this application, which is applied to a terminal (such as a UE, ME). Figure 3B As shown, the method includes the following steps:

[0241] Step 302: If the third condition is satisfied, the terminal performs a second operation, which includes at least one of the following:

[0242] Set the first device identifier to an invalid device identifier in the first network;

[0243] The first subscriber's data is not bound to the first device identifier;

[0244] When the first subscriber data is bound to the first device identifier, access to the first network using the first subscriber data is prohibited;

[0245] When the first subscriber data is bound to the first device identifier, the first subscriber data is activated for scenarios where the device resides and / or accesses the first network.

[0246] If the first subscriber data has already been bound to the first device identifier, unbind the first subscriber data from the first device identifier;

[0247] Bind the second device identifier to the first subscriber data;

[0248] If the first subscriber data is not bound to a device identifier, then bind a device identifier to the first subscriber data;

[0249] The third condition includes one of the following: receiving first information from the first network and confirming that the first device identifier is not a legitimate device identifier of the first network;

[0250] The first information is used to indicate at least one of the following: the terminal device is invalid, or the device identifier of the terminal is invalid;

[0251] The subscriber data includes at least one of the following: certificates, contract data.

[0252] In one implementation, binding the first subscriber data to the second device identifier includes changing the binding of the first subscriber data to the second device identifier when the first subscriber data is already bound to the first device identifier.

[0253] Optionally, the third condition further includes at least one of the following:

[0254] The terminal uses the first subscriber's data to access the first network;

[0255] Before receiving the first information from the first network, the terminal sends the first device identifier to the first network;

[0256] The device identifier bound to the first subscriber's data is the first device identifier;

[0257] The terminal registers with the first network, and the registration is a non-urgent registration.

[0258] Optionally, the first device identifier includes at least one of the following: a terminal device identifier bound to the first subscriber data, a terminal device identifier provided to the first network, and a terminal device identifier that the first network confirms is invalid;

[0259] and / or

[0260] The second device identifier is a valid terminal device identifier in the first network;

[0261] and / or

[0262] When the first subscriber data is not bound to a device identifier, the device identifier bound to the first subscriber data is a valid terminal device identifier in the first network.

[0263] Optionally, setting the first device identifier as an invalid device identifier for the first network includes at least one of the following: prohibiting access to the first network using the first device identifier; prohibiting the sending of the first device identifier to the first network; and prohibiting binding the first device identifier to the subscriber data when accessing the first network using subscriber data.

[0264] The first subscriber data not being bound to the first device identifier includes: in scenarios where the first subscriber data is accessed through the first network, the first subscriber data is not bound to the first device identifier;

[0265] and / or

[0266] If the first subscriber data is already bound to the first device identifier, unbinding the first subscriber data from the first device identifier includes: for scenarios used to access the first network, if the first subscriber data is already bound to the first device identifier, unbinding the first subscriber data from the first device identifier.

[0267] and / or

[0268] The step of binding the second device identifier to the first subscriber data includes: for scenarios used to access the first network, binding the second device identifier to the first subscriber data;

[0269] and / or

[0270] When the first subscriber data is not bound to a device identifier, binding a device identifier to the first subscriber data includes: for scenarios used to access the first network, when the first subscriber data is not bound to a device identifier, binding a device identifier to the first subscriber data.

[0271] Optionally, setting the first device identifier to an invalid device identifier for the first network is only applicable to scenarios where access to the first network is not urgently registered;

[0272] and / or

[0273] The scenarios used for accessing the first network do not include the scenario of emergency registration of the first network.

[0274] In one implementation, emergency registration is an exception. In non-emergency registration scenarios, the first device identifier is an invalid terminal device identifier within the first network. However, in emergency registration scenarios, the first device identifier can still be used to access the first network.

[0275] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0276] For ease of understanding, specific embodiments are provided below: Figure 4 As shown, the registration process triggered by the relevant terminal may include:

[0277] Step 01: The terminal uses the first subscriber data to send a registration request message to the network-side device (hereinafter referred to as AMF as an example).

[0278] Step 02: The AMF receives a mobile registration request message. The AMF sends an identification request to the terminal, which is used to request the terminal's device identifier.

[0279] Step 03, in one mode, the terminal's first subscriber data does not have a device identifier, and an identifier response is sent to the AMF, the response message indicating no identifier (e.g., no identity).

[0280] In another approach, the terminal's first subscriber data has a device identifier (i.e., a first device identifier), and sends an identifier response to the AMF, the response message including the device identifier (i.e., the first device identifier) ​​of the terminal bound to the subscriber data.

[0281] Step 04: When no identifier is received, the AMF sends a registration rejection message to the terminal, including the reason for the registration rejection. The reason for the registration rejection is used to indicate that the terminal device is illegitimate.

[0282] Upon receiving the terminal's device identifier, the AMF can request the EIR to verify the terminal's device identifier. If the EIR verification fails, the AMF sends a registration rejection message to the terminal, including the reason for the rejection. The reason for the rejection indicates that the terminal device is illegitimate.

[0283] From the above, the terminal can determine that the network requires device identification verification of the terminal.

[0284] In addition, the terminal can also perform a second operation, specifically as follows: Figure 3B As described above.

[0285] It should be noted that the information processing method provided in this application embodiment can be executed by an information processing device, or by a control module within that information processing device for executing the information processing method. This application embodiment uses an information processing device executing the information processing method as an example to illustrate the information processing device provided in this application embodiment.

[0286] See Figure 5 , Figure 5 This is a schematic diagram of the structure of an information processing device provided in an embodiment of this application. Figure 5 As shown, the information processing device 50 includes:

[0287] The first execution module 51 is used to perform related operations for activating and / or deactivating subscriber data based on the number of device identifiers of the terminal;

[0288] The subscriber data includes at least one of the following: certificates, contract data.

[0289] In one implementation, the device identifier of the terminal is pre-configured in the terminal or obtained from the terminal manufacturer's server. A terminal may have one or more device identifiers.

[0290] Optionally,

[0291] The first execution module is specifically used to execute at least one of the following:

[0292] The number of subscriber data activated at the same time is less than and / or equal to the total number of device identifiers of the terminal;

[0293] At most, one device identifier can be bound to one subscriber data.

[0294] The number of subscriber data that can be activated simultaneously is determined based on the number of device identifiers of the terminal.

[0295] The number of remaining subscriber data that can be activated simultaneously is determined based on the number of idle device identifiers of the terminal.

[0296] Based on the number of device identifiers of the terminal, at least one of the following is presented: the number of subscriber data that can be activated simultaneously, and the remaining number of subscriber data that can be activated simultaneously.

[0297] For each activated subscriber, a device identifier is bound to it;

[0298] When deactivating subscriber data, unbind the subscriber data from its corresponding device identifier;

[0299] When the terminal needs to activate the second subscriber data and there is no available device identifier, activate the first subscriber data.

[0300] The first subscriber data includes at least one of the following: activated subscriber data, and subscriber data that has been bound to a device identifier.

[0301] In one implementation, the first subscriber data may be subscriber data that the end user has selected to deactivate. The second subscriber data may be subscriber data that has not been activated.

[0302] In one implementation, the unbound device identifier can be bound to other subscriber data.

[0303] In one implementation, a device identifier bound to one subscriber's data cannot be bound to other subscriber data.

[0304] The binding of subscriber data with device identifier includes at least one of the following: the terminal device identifier corresponding to the subscriber data is the device identifier; when the terminal accesses the network using the subscriber data, the terminal device identifier provided to the network is the subscriber bundle data bound to it.

[0305] In one implementation, the idle device identifier includes device identifiers that are not bound in the terminal.

[0306] For example, when no USIM is inserted into the USIM slot, the device identifier corresponding to the slot can be considered to be free.

[0307] For example, if the UICC has not downloaded eSIM, the device identifier corresponding to the UICC can be considered idle.

[0308] In one implementation, the idle device identifier can be used to bind a non-UICC type certificate and / or contract.

[0309] Optionally, the terminal determines the number of subscriber data that can be activated simultaneously based on the number of device identifiers of the terminal, including at least one of the following:

[0310] The terminal determines the maximum number of subscriber data that can be activated simultaneously based on the total number of terminal device identifiers.

[0311] The number of subscriber data that a terminal can activate simultaneously is less than and / or equal to the total number of device identifiers of the terminal.

[0312] In one embodiment, the device further includes a presentation module, wherein,

[0313] The presentation module is used to present at least one of the following: the number of subscriber data that can be activated simultaneously, and the total number of device identifiers;

[0314] And / or,

[0315] The presentation module is used to present at least one of the following: the number of remaining subscriber data that can be activated simultaneously, and the number of idle device identifiers.

[0316] In one implementation, the user chooses which subscriber data to activate or deactivate.

[0317] Optionally, the subscriber data includes at least one of the following: UICC type subscriber data, non-UICC type subscriber data, and subscriber data stored on the terminal device.

[0318] Optionally, the device identifier includes one of the following:

[0319] Device identifiers specific to subscriber data that are not UICC type;

[0320] Non-UICC subscriber data and UICC type subscriber data, common device identifier.

[0321] Optionally, the type of the device identifier includes at least one of the following: PEI, IMEI, IMEISv.

[0322] Optionally, the first execution module is configured to perform operations related to activating and / or deactivating subscriber data based on the number of device identifiers, provided that a first condition is met; wherein the first condition includes at least one of the following:

[0323] The network requires device identification verification of the terminal;

[0324] The amount of subscriber data stored and / or inserted on the terminal exceeds the terminal's device identifier limit. In one implementation, the network's requirement to verify the terminal's device identifier includes the network requiring device identifier verification for the terminal corresponding to the subscriber data.

[0325] In one implementation, the network corresponding to the subscriber data includes at least one of the following: a network that uses the subscriber data for access and / or registration, and a contract network corresponding to the subscriber data.

[0326] Optionally, the device further includes a receiving module;

[0327] The receiving module is used to receive first indication information from the network, the first indication information being used to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required;

[0328] and / or

[0329] The receiving module is used to receive a registration rejection reason from the network, and the registration rejection reason is used to indicate that the terminal device is invalid.

[0330] and / or

[0331] The receiving module is used to receive an identification request from the network, and the identification request is used to request the device identification of the terminal.

[0332] In one implementation, the terminal can first attempt to register with the network. When the network requests the terminal's device identifier, the terminal can determine that the network needs to verify the terminal's device identifier.

[0333] In one implementation, the terminal may first attempt to register with the network. If the terminal fails to provide the network with its device identifier and / or receives a registration failure reason from the network, where the registration failure reason indicates that the terminal device is illegitimate, the terminal may determine that the network needs to verify the terminal's device identifier.

[0334] Optionally, activating subscriber data or having subscriber data activated includes at least one of the following:

[0335] The subscriber data is in a valid or activated state;

[0336] It can trigger the terminal to search for the network corresponding to the subscriber data;

[0337] The subscriber data enables access to or registration on the network.

[0338] The terminal accesses the network through the subscriber data and is in a registered state on the network;

[0339] The terminal accesses the network through the subscriber data and the state of the network does not include the deregistration state where the subscriber data is invalid;

[0340] The subscriber corresponding to the subscriber data is in a deregistered state on the network, and the deregistered state does not include the deregistered state where the subscriber data is invalid.

[0341] and / or

[0342] Deactivating subscriber data or having subscriber data deactivated includes at least one of the following:

[0343] The subscriber data is invalid.

[0344] The terminal cannot be triggered to search for the network corresponding to the subscriber data;

[0345] The terminal accesses the network through the subscriber data and is in a deregistered state in the network, or in a deregistered state where the subscriber data is invalid;

[0346] The subscriber corresponding to the subscriber data is in a deregistered state on the network, or the subscriber corresponding to the subscriber data is in a deregistered state where the subscriber data is invalid.

[0347] In one implementation, after the terminal deactivates the subscriber data, it may not delete the data and may still retain the deactivated subscriber data.

[0348] In one embodiment, being able to access the network through the subscriber data includes at least one of the following: being able to register for the network using the subscriber data, the subscriber corresponding to the subscriber data being in a registered state on the network, and being able to use the network services using the subscriber data.

[0349] The terminal performs activation and / or deactivation of subscriber data operations based on the number of device identifiers of the terminal, including at least one of the following:

[0350] The terminal performs operations to activate and / or deactivate non-UICC type subscriber data based on the number of non-UICC type device identifiers of the terminal;

[0351] The terminal performs operations to activate and / or deactivate UICC type subscriber data based on the number of device identifiers of the terminal's UICC type.

[0352] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0353] See Figure 6 , Figure 6 This is a schematic diagram of another information processing device provided in an embodiment of this application. For example... Figure 6 As shown, the information processing device 60 includes:

[0354] The first sending module, wherein the first indication information is used to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required.

[0355] In this embodiment of the application, the information processing device 60 is capable of implementing the present application. Figure 3 The various processes implemented in the method embodiments shown, and the same beneficial effects achieved, will not be described again here to avoid repetition.

[0356] See Figure 6A , Figure 6A This is a schematic diagram of the structure of an information processing device provided in an embodiment of this application. Figure 6A As shown, the information processing device 600 includes:

[0357] The second execution module 601 is used to execute the first operation when it is determined that the second condition is met.

[0358] The first operation includes at least one of the following:

[0359] Bind device identifier to the first subscriber's data.

[0360] Send the device identifier to the first network;

[0361] The second condition includes at least one of the following:

[0362] The first subscriber data is the subscriber data activated on the terminal.

[0363] The terminal accesses the first network using first subscriber data.

[0364] The first network requires device identification verification of the terminal.

[0365] The device identifier is a valid terminal device identifier in the first network.

[0366] The device identifier is the device identifier bound to the first subscriber's data;

[0367] The subscriber data includes at least one of the following: certificates, contract data.

[0368] In one implementation, the first subscriber data binding device identifier is defined as follows:

[0369] The first subscriber data is the subscriber data activated on the terminal.

[0370] The terminal accesses the first network using first subscriber data.

[0371] The first network requires device identification verification of the terminal.

[0372] The device identifier is a valid terminal device identifier in the first network;

[0373] In one implementation, the device identifier is sent to the first network when the second condition includes at least one of the following:

[0374] The first subscriber data is the subscriber data activated on the terminal.

[0375] The terminal accesses the first network using first subscriber data.

[0376] The first network requires device identification verification of the terminal.

[0377] The device identifier is a valid terminal device identifier in the first network.

[0378] The device identifier is the device identifier for the first subscriber's data binding.

[0379] Optionally, binding the device identifier for the first subscriber data includes: binding a valid terminal device identifier in the first network to the first subscriber data in the scenario of accessing the first network.

[0380] In one implementation, the operation of binding the first subscriber data to a valid terminal device identifier in the first network is effective in scenarios where the data is used to access the first network. For example, in scenarios where the data is used to access the second network, the data bound to the first subscriber data could be a valid terminal device identifier in the second network.

[0381] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0382] See Figure 6B , Figure 6B This is a schematic diagram of the structure of an information processing device provided in an embodiment of this application. Figure 6B As shown, the information processing device 602 includes:

[0383] The third execution module 603 is used to perform the second operation when it is determined that the third condition is met.

[0384] The second operation includes at least one of the following:

[0385] Set the first device identifier to an invalid device identifier in the first network;

[0386] The first subscriber's data is not bound to the first device identifier;

[0387] When the first subscriber data is bound to the first device identifier, access to the first network using the first subscriber data is prohibited;

[0388] When the first subscriber data is bound to the first device identifier, the first subscriber data is activated for scenarios where the device resides and / or accesses the first network.

[0389] If the first subscriber data has already been bound to the first device identifier, unbind the first subscriber data from the first device identifier;

[0390] Bind the second device identifier to the first subscriber data;

[0391] If the first subscriber data is not bound to a device identifier, then bind a device identifier to the first subscriber data;

[0392] The third condition includes one of the following: receiving first information from the first network and confirming that the first device identifier is not a legitimate device identifier of the first network;

[0393] The first information is used to indicate at least one of the following: the terminal device is invalid, or the device identifier of the terminal is invalid;

[0394] The subscriber data includes at least one of the following: certificates, contract data.

[0395] In one implementation, binding the first subscriber data to the second device identifier includes changing the binding of the first subscriber data to the second device identifier when the first subscriber data is already bound to the first device identifier.

[0396] Optionally, the third condition further includes at least one of the following:

[0397] The terminal uses the first subscriber's data to access the first network;

[0398] Before receiving the first information from the first network, the terminal sends the first device identifier to the first network;

[0399] The device identifier bound to the first subscriber's data is the first device identifier;

[0400] The terminal registers with the first network, and the registration is a non-urgent registration.

[0401] Optionally, the first device identifier includes at least one of the following: a terminal device identifier bound to the first subscriber data, a terminal device identifier provided to the first network, and a terminal device identifier that the first network confirms is invalid;

[0402] and / or

[0403] The second device identifier is a valid terminal device identifier in the first network;

[0404] and / or

[0405] When the first subscriber data is not bound to a device identifier, the device identifier bound to the first subscriber data is a valid terminal device identifier in the first network.

[0406] Optionally, setting the first device identifier as an invalid device identifier for the first network includes at least one of the following: prohibiting access to the first network using the first device identifier; prohibiting the sending of the first device identifier to the first network; and prohibiting binding the first device identifier to the subscriber data when accessing the first network using subscriber data.

[0407] The first subscriber data not being bound to the first device identifier includes: in scenarios where the first subscriber data is accessed through the first network, the first subscriber data is not bound to the first device identifier;

[0408] and / or

[0409] If the first subscriber data is already bound to the first device identifier, unbinding the first subscriber data from the first device identifier includes: for scenarios used to access the first network, if the first subscriber data is already bound to the first device identifier, unbinding the first subscriber data from the first device identifier.

[0410] and / or

[0411] The step of binding the second device identifier to the first subscriber data includes: for scenarios used to access the first network, binding the second device identifier to the first subscriber data;

[0412] and / or

[0413] When the first subscriber data is not bound to a device identifier, binding a device identifier to the first subscriber data includes: for scenarios used to access the first network, when the first subscriber data is not bound to a device identifier, binding a device identifier to the first subscriber data.

[0414] Optionally, setting the first device identifier to an invalid device identifier for the first network is only applicable to scenarios where access to the first network is not urgently registered;

[0415] and / or

[0416] The scenarios used for accessing the first network do not include the scenario of emergency registration of the first network.

[0417] In one implementation, emergency registration is an exception. In non-emergency registration scenarios, the first device identifier is an invalid terminal device identifier within the first network. However, in emergency registration scenarios, the first device identifier can still be used to access the first network.

[0418] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0419] like Figure 7 As shown, this application embodiment also provides a communication device 70, including a processor 71, a memory 72, and a program or instructions stored in the memory 72 and executable on the processor 71. When the program or instructions are executed by the processor 71, they implement the various processes of the above-described information processing method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0420] Figure 8 A schematic diagram of the hardware structure of a terminal 800 according to an embodiment of this application.

[0421] The terminal 800 includes, but is not limited to, components such as: radio frequency unit 801, network module 802, audio output unit 803, input unit 804, sensor 805, display unit 806, user input unit 807, interface unit 808, memory 809, and processor 810.

[0422] Those skilled in the art will understand that the terminal 800 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 810 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 8 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0423] It should be understood that, in this embodiment, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042. The GPU 8041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 807 includes a touch panel 8061 and other input devices 8072. The touch panel 8061 is also called a touch screen. The touch panel 8061 may include a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0424] In this embodiment, the radio frequency unit 801 receives downlink data from the network-side device and processes it for the processor 810; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0425] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 809 may include high-speed random access memory and non-volatile memory, wherein the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0426] Processor 810 may include one or more processing units; optionally, processor 810 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 810.

[0427] The processor 810 is configured to perform operations related to activating and / or deactivating subscriber data based on the number of device identifiers of the terminal; wherein the subscriber data includes at least one of the following: certificate, subscription data.

[0428] Optionally, the processor 810 is specifically used to perform at least one of the following:

[0429] The number of subscriber data activated at the same time is less than and / or equal to the total number of device identifiers of the terminal;

[0430] At most, one device identifier can be bound to one subscriber data.

[0431] The number of subscriber data that can be activated simultaneously is determined based on the number of device identifiers of the terminal.

[0432] The number of remaining subscriber data that can be activated simultaneously is determined based on the number of idle device identifiers of the terminal.

[0433] Based on the number of device identifiers of the terminal, at least one of the following is presented: the number of subscriber data that can be activated simultaneously, and the remaining number of subscriber data that can be activated simultaneously.

[0434] For each activated subscriber, a device identifier is bound to it;

[0435] When deactivating subscriber data, unbind the subscriber data from its corresponding device identifier;

[0436] When the terminal needs to activate the second subscriber data and there is no available device identifier, activate the first subscriber data.

[0437] The first subscriber data includes at least one of the following: activated subscriber data, and subscriber data that has been bound to a device identifier.

[0438] Optionally, determining the number of subscriber data that can be activated simultaneously based on the number of device identifiers of the terminal includes at least one of the following:

[0439] The maximum amount of subscriber data that can be activated simultaneously is determined based on the total number of device identifiers of the terminals.

[0440] The number of subscriber data that a terminal can activate simultaneously is less than and / or equal to the total number of device identifiers of the terminal.

[0441] Optionally, the display unit 806 is used to present at least one of the following: the number of subscriber data that can be activated simultaneously, and the total number of device identifiers;

[0442] And / or,

[0443] The display unit 806 is used to present at least one of the following: the number of remaining subscriber data that can be activated simultaneously, and the number of idle device identifiers.

[0444] Optionally, the subscriber data includes at least one of the following: UICC type subscriber data, non-UICC type subscriber data, and subscriber data stored on the terminal device.

[0445] Optionally, the device identifier includes one of the following:

[0446] Device identifiers specific to subscriber data that are not UICC type;

[0447] Non-UICC subscriber data and UICC type subscriber data, common device identifier.

[0448] Optionally, the type of the device identifier includes at least one of the following: PEI, IMEI, IMEISv.

[0449] Optionally, the processor 810 is configured to perform operations related to activating and / or deactivating subscriber data based on the number of device identifiers, provided that a first condition is met; wherein the first condition includes at least one of the following:

[0450] The network requires device identification verification of the terminal;

[0451] The amount of subscriber data stored and / or inserted on the terminal exceeds the number of device identifiers on the terminal.

[0452] Optionally, the radio frequency unit 801 is configured to receive first indication information from the network, the first indication information being configured to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required;

[0453] And / or,

[0454] Radio frequency unit 801 is used to receive a registration rejection reason from the network, the registration rejection reason being used to indicate that the terminal device is illegitimate;

[0455] And / or,

[0456] The radio frequency unit 801 is used to receive an identification request from the network, the identification request being used to request the acquisition of the device identification of the terminal.

[0457] Optional,

[0458] Activating subscriber data or having subscriber data activated includes at least one of the following:

[0459] The subscriber data is in a valid or activated state;

[0460] It can trigger the terminal to search for the network corresponding to the subscriber data;

[0461] The subscriber data enables access to or registration on the network.

[0462] The terminal accesses the network through the subscriber data and is in a registered state on the network;

[0463] The terminal accesses the network through the subscriber data and the state of the network does not include the deregistration state where the subscriber data is invalid;

[0464] The subscriber corresponding to the subscriber data is in a deregistered state on the network, and the deregistered state does not include the deregistered state where the subscriber data is invalid.

[0465] and / or

[0466] Deactivating subscriber data or having subscriber data deactivated includes at least one of the following:

[0467] The subscriber data is invalid.

[0468] The terminal cannot be triggered to search for the network corresponding to the subscriber data;

[0469] The terminal accesses the network through the subscriber data and is in a deregistered state in the network, or in a deregistered state where the subscriber data is invalid;

[0470] The subscriber corresponding to the subscriber data is in a deregistered state on the network, or the subscriber corresponding to the subscriber data is in a deregistered state where the subscriber data is invalid.

[0471] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0472] Optionally, the processor 810 is configured to perform the first operation if it is determined that the second condition is met;

[0473] The first operation includes at least one of the following:

[0474] Bind device identifier to the first subscriber's data.

[0475] Send the device identifier to the first network;

[0476] The second condition includes at least one of the following:

[0477] The first subscriber data is the subscriber data activated on the terminal.

[0478] The terminal accesses the first network using first subscriber data.

[0479] The first network requires device identification verification of the terminal.

[0480] The device identifier is a valid terminal device identifier in the first network.

[0481] The device identifier is the device identifier bound to the first subscriber's data;

[0482] The subscriber data includes at least one of the following: certificates, contract data.

[0483] Optionally, binding the device identifier for the first subscriber data includes: binding a valid terminal device identifier in the first network to the first subscriber data in the scenario of accessing the first network.

[0484] Optionally, the subscriber data may further include at least one of the following: a terminal subscriber identifier, and information about the network corresponding to the subscriber data.

[0485] Optionally, the processor 810 is configured to perform a second operation upon determining that a third condition is met, the second operation including at least one of the following:

[0486] Set the first device identifier to an invalid device identifier in the first network;

[0487] The first subscriber's data is not bound to the first device identifier;

[0488] When the first subscriber data is bound to the first device identifier, access to the first network using the first subscriber data is prohibited;

[0489] When the first subscriber data is bound to the first device identifier, the first subscriber data is activated for scenarios where the device resides and / or accesses the first network.

[0490] If the first subscriber data has already been bound to the first device identifier, unbind the first subscriber data from the first device identifier;

[0491] Bind the second device identifier to the first subscriber data;

[0492] If the first subscriber data is not bound to a device identifier, then bind a device identifier to the first subscriber data;

[0493] The third condition includes one of the following: receiving first information from the first network and confirming that the first device identifier is not a legitimate device identifier of the first network;

[0494] The first information is used to indicate at least one of the following: the terminal device is invalid, or the device identifier of the terminal is invalid;

[0495] The subscriber data includes at least one of the following: certificates, contract data.

[0496] Optionally, the third condition may also include at least one of the following:

[0497] The terminal uses the first subscriber's data to access the first network;

[0498] Before receiving the first information from the first network, the terminal sends the first device identifier to the first network;

[0499] The device identifier bound to the first subscriber's data is the first device identifier;

[0500] The terminal registers with the first network, and the registration is a non-urgent registration.

[0501] Optionally, the first device identifier includes at least one of the following: a terminal device identifier bound to the first subscriber data, a terminal device identifier provided to the first network, and a terminal device identifier that the first network confirms is invalid;

[0502] and / or

[0503] The second device identifier is a valid terminal device identifier in the first network;

[0504] and / or

[0505] When the first subscriber data is not bound to a device identifier, the device identifier bound to the first subscriber data is a valid terminal device identifier in the first network.

[0506] Optionally, setting the first device identifier as an invalid device identifier for the first network includes at least one of the following: prohibiting access to the first network using the first device identifier; prohibiting the sending of the first device identifier to the first network; and prohibiting binding the first device identifier to the subscriber data when accessing the first network using subscriber data.

[0507] The first subscriber data not being bound to the first device identifier includes: in scenarios where the first subscriber data is accessed through the first network, the first subscriber data is not bound to the first device identifier;

[0508] and / or

[0509] If the first subscriber data is already bound to the first device identifier, unbinding the first subscriber data from the first device identifier includes: for scenarios used to access the first network, if the first subscriber data is already bound to the first device identifier, unbinding the first subscriber data from the first device identifier.

[0510] and / or

[0511] The step of binding the second device identifier to the first subscriber data includes: for scenarios used to access the first network, binding the second device identifier to the first subscriber data;

[0512] and / or

[0513] When the first subscriber data is not bound to a device identifier, binding a device identifier to the first subscriber data includes: for scenarios used to access the first network, when the first subscriber data is not bound to a device identifier, binding a device identifier to the first subscriber data.

[0514] Optionally, setting the first device identifier to an invalid device identifier for the first network is only applicable to scenarios where access to the first network is not urgently registered;

[0515] and / or

[0516] The scenarios used for accessing the first network do not include the scenario of emergency registration of the first network.

[0517] This application describes the terminal 800 provided in the embodiment, which can achieve... Figure 2 or Figure 3A or Figure 3B The various processes of the information processing method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0518] This application also provides a network-side device. For example... Figure 9 As shown, the network-side device 1100 includes: a processor 1101, a transceiver 1102, a memory 1103, a user interface 1104, and a bus interface, wherein:

[0519] In this embodiment of the invention, the network-side device 1100 further includes: a computer program stored on a memory 1103 and executable on a processor 1101, the computer program being executed by the processor 1101. Figure 3 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0520] exist Figure 9 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1101) and memory (memory 1103). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1102 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, the user interface 1104 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0521] The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 can store the data used by the processor 1101 when performing operations.

[0522] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described information processing method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0523] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0524] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above information processing method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0525] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0526] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0527] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network-side device, etc.) to execute the methods described in the various embodiments of this application.

[0528] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. An information processing method, characterized in that, include: The terminal performs activation and / or deactivation operations on subscriber data based on the number of device identifiers of the terminal; The subscriber data includes at least one of the following: certificates, contract data; The terminal performs the following operations to activate and / or deactivate subscriber data based on the number of device identifiers: The terminal determines the number of subscriber data that can be activated simultaneously based on the total number of device identifiers of the terminal. The number of subscriber data that a terminal can activate simultaneously is less than and / or equal to the total number of device identifiers of the terminal.

2. The method according to claim 1, characterized in that, After determining the number of subscriber data that can be activated simultaneously, at least one of the following is presented: the number of subscriber data that can be activated simultaneously, and the total number of device identifiers.

3. The method according to claim 1 or 2, characterized in that, The terminal's operation of activating and / or deactivating subscriber data based on the number of device identifiers further includes: the terminal determining the number of remaining subscriber data that can be activated simultaneously based on the number of idle device identifiers of the terminal. After determining the number of remaining subscriber data that can be activated simultaneously, at least one of the following is presented: the number of remaining subscriber data that can be activated simultaneously, and the number of idle device identifiers.

4. The method according to claim 1 or 2, characterized in that, The subscriber data includes at least one of the following: UICC type subscriber data, non-UICC type subscriber data, and subscriber data stored on the terminal device.

5. The method according to claim 1 or 2, characterized in that, The device identifier includes one of the following: Device identifiers specific to subscriber data that are not UICC type; Non-UICC subscriber data and UICC type subscriber data, common device identifier.

6. The method according to claim 1 or 2, characterized in that, The device identifier type includes at least one of the following: Permanent User Equipment Identifier (PEI), International Mobile Equipment Identifier (IMEI), International Mobile Equipment Identifier (IMEI) and Software Version Number (IMEISv).

7. The method according to claim 1 or 2, characterized in that, The terminal's actions to activate and / or deactivate subscriber data based on the number of device identifiers include at least one of the following: Under a first condition, the terminal performs the activation and / or deactivation of subscriber data based on the total number of device identifiers; wherein the first condition includes at least one of the following: The network requires device identification verification of the terminal; The amount of subscriber data stored and / or inserted on the terminal exceeds the total number of device identifiers on the terminal.

8. The method according to claim 1, characterized in that, The method further includes at least one of the following: Receive first indication information from the network, the first indication information being used to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required; Receive a registration rejection reason from the network, the registration rejection reason being used to indicate that the terminal device is illegitimate; Receive an identification request from the network, the identification request being used to request the device identification of the terminal.

9. The method according to any one of claims 1 to 2 and 8, characterized in that, Activating subscriber data or having subscriber data activated includes at least one of the following: The subscriber data is in a valid or activated state; It can trigger the terminal to search for the network corresponding to the subscriber data; The subscriber data enables access to or registration on the network. The terminal accesses the network through the subscriber data and is in a registered state on the network; The terminal accesses the network through the subscriber data and the state of the network does not include the deregistration state where the subscriber data is invalid; The subscriber corresponding to the subscriber data is in a deregistered state on the network, and the deregistered state does not include the deregistered state where the subscriber data is invalid.

10. The method according to claim 1 or 2, characterized in that, The subscriber data also includes at least one of the following: terminal subscriber identifier, and information about the network corresponding to the subscriber data.

11. The method according to claim 1 or 2, characterized in that, The terminal performs activation and / or deactivation of subscriber data operations based on the number of device identifiers of the terminal, including at least one of the following: The terminal performs operations to activate and / or deactivate non-UICC type subscriber data based on the number of non-UICC type device identifiers of the terminal; The terminal performs operations to activate and / or deactivate UICC type subscriber data based on the number of device identifiers of the terminal's UICC type.

12. An information processing device, characterized in that, The device includes: The first execution module is used to perform operations related to activating and / or deactivating subscriber data based on the number of device identifiers on the terminal. The subscriber data includes at least one of the following: certificates, contract data; The first execution module is specifically used to execute: The number of subscriber data that can be activated simultaneously is determined based on the total number of device identifiers of the terminal. The number of subscriber data that a terminal can activate simultaneously is less than and / or equal to the total number of device identifiers of the terminal.

13. The apparatus according to claim 12, characterized in that, The device also includes a presentation module, wherein... The presentation module is used to present at least one of the following: the number of subscriber data that can be activated simultaneously, and the total number of device identifiers.

14. The apparatus according to claim 13, characterized in that, The first execution module is also specifically used to perform: determining the number of remaining subscriber data that can be activated simultaneously based on the number of idle device identifiers of the terminal; The presentation module is also used to present at least one of the following: the number of remaining subscriber data that can be activated simultaneously, and the number of idle device identifiers.

15. The apparatus according to any one of claims 12-14, characterized in that, The subscriber data includes at least one of the following: subscriber data of the Universal Integrated Circuit Card (UICC) type, subscriber data of the non-UICC type, and subscriber data stored on the terminal device.

16. The apparatus according to any one of claims 12-14, characterized in that, The device identifier includes one of the following: Device identifiers specific to subscriber data that are not UICC type; Non-UICC subscriber data and UICC type subscriber data, common device identifier.

17. The apparatus according to any one of claims 12-14, characterized in that, The device identifier type includes at least one of the following: PEI, IMEI, IMEISv.

18. The apparatus according to any one of claims 12-14, characterized in that, The first execution module is configured to perform operations related to activating and / or deactivating subscriber data based on the total number of device identifiers, provided that a first condition is met; wherein the first condition includes at least one of the following: The network requires device identification verification of the terminal; The amount of subscriber data stored and / or inserted on the terminal exceeds the total number of device identifiers on the terminal.

19. The apparatus according to claim 12, characterized in that, The device also includes a receiving module; The receiving module is used to receive first indication information from the network, the first indication information being used to indicate one of the following: device identification verification of the terminal is required, or device identification verification of the terminal is not required; And / or, The receiving module is used to receive a registration rejection reason from the network, and the registration rejection reason is used to indicate that the terminal device is invalid. And / or, The receiving module is used to receive an identification request from the network, and the identification request is used to request the device identification of the terminal.

20. The apparatus according to any one of claims 12 to 14, 19, characterized in that, Activating subscriber data or having subscriber data activated includes at least one of the following: The subscriber data is in a valid or activated state; It can trigger the terminal to search for the network corresponding to the subscriber data; The subscriber data enables access to or registration on the network. The terminal accesses the network through the subscriber data and is in a registered state on the network; The terminal accesses the network through the subscriber data and the state of the network does not include the deregistration state where the subscriber data is invalid; The subscriber corresponding to the subscriber data is in a deregistered state on the network, and the deregistered state does not include the deregistered state where the subscriber data is invalid.

21. The apparatus according to any one of claims 12-14, characterized in that, The subscriber data also includes at least one of the following: terminal subscriber identifier, and information about the network corresponding to the subscriber data.

22. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the information processing method as described in any one of claims 1 to 11.

23. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the information processing method as described in any one of claims 1 to 11.

Images