CN117478332A

CN117478332A - PIN management method and device, first terminal and first equipment

Info

Publication number: CN117478332A
Application number: CN202210863475.8A
Authority: CN
Inventors: 吕华章; 谢振华
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-07-20
Filing date: 2022-07-20
Publication date: 2024-01-30
Also published as: WO2024017195A1

Abstract

The application discloses a PIN management method, a PIN management device, a first terminal and first equipment, which belong to the technical field of communication, and the PIN management method in the embodiment of the application comprises the following steps: the method comprises the steps that a first terminal sends first information to first equipment, wherein the first information comprises a PIN identifier and identification information of at least one second terminal; the first information is used for requesting to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier.

Description

PIN management method and device, first terminal and first equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a PIN management method, a PIN management device, a first terminal and first equipment.

Background

In the personal networking network (Personal IoT Network, PIN), a PIN network element (PIN element with management capability, PEMC, such as a terminal) with a management function can manage the PIN, and in the related art, there may be a problem that the terminal as the PEMC cannot manage the PIN due to shutdown, arrearage and other reasons.

Disclosure of Invention

The embodiment of the application provides a PIN management method, a PIN management device, a first terminal and first equipment, which can configure at least two PEMC for one PIN, so that the PIN can be managed by using at least two PEMC, and the flexibility of PIN management is improved.

In a first aspect, a PIN management method is provided, the method comprising:

the method comprises the steps that a first terminal sends first information to first equipment, wherein the first information comprises a PIN identifier and identification information of at least one second terminal;

the first information is used for requesting to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier.

In a second aspect, there is provided a PIN management device for use with a first terminal, the device comprising:

the first sending module is used for sending first information to the first equipment, wherein the first information comprises a PIN identifier and identification information of at least one second terminal;

In a third aspect, a PIN management method is provided, the method comprising:

the method comprises the steps that first equipment obtains first information from a first terminal, wherein the first information comprises a PIN identifier and identification information of at least one second terminal, and the first information is used for requesting the at least one second terminal to be configured as an administrator of a PIN corresponding to the PIN identifier;

The first device determines whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier according to the first information.

In a fourth aspect, there is provided a PIN management apparatus for use with a first device, the apparatus comprising:

the terminal comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring first information from a first terminal, wherein the first information comprises a PIN identifier and identification information of at least one second terminal, and the first information is used for requesting to configure the at least one second terminal as an administrator of a PIN corresponding to the PIN identifier;

and the second determining module is used for determining whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier according to the first information.

In a fifth aspect, there is provided a first terminal comprising a processor and a memory storing a program or instructions executable on the processor, which program or instructions when executed by the processor implement the steps of the method as described in the first aspect.

In a sixth aspect, a first terminal is provided, including a processor and a communication interface, where the communication interface is configured to send first information to a first device, where the first information includes a PIN identifier and identification information of at least one second terminal; the first information is used for requesting to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier.

In a seventh aspect, there is provided a first device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the third aspect.

An eighth aspect provides a first device, including a processor and a communication interface, where the communication interface is configured to obtain first information from a first terminal, where the first information includes a PIN identifier, and identification information of at least one second terminal, where the first information is configured to request that the at least one second terminal be configured as an administrator of a PIN corresponding to the PIN identifier; the processor is used for determining whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier according to the first information.

In a ninth aspect, there is provided a communication system comprising: a first terminal operable to perform the steps of the PIN management method according to the first aspect, and a first apparatus operable to perform the steps of the PIN management method according to the third aspect.

In a tenth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method according to the first aspect, or performs the steps of the method according to the third aspect.

In an eleventh aspect, there is provided a chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being for running a program or instructions to implement the method according to the first aspect or to implement the method according to the third aspect.

In a twelfth aspect, there is provided a computer program/program product stored in a storage medium, the computer program/program product being executed by at least one processor to implement the steps of the PIN management method as described in the first aspect, or to implement the steps of the PIN management method as described in the third aspect.

In the embodiment of the application, a first terminal sends first information to first equipment, wherein the first information comprises a PIN identifier and identification information of at least one second terminal; the first information is used for requesting to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier. The first terminal sends the request information to the first device to request to configure at least one second terminal as the administrator of the PIN corresponding to the PIN identifier, so that the addition of the administrator of the PIN can be realized, the administrator of one PIN is not limited to one administrator any more, and a plurality of administrators are adopted to manage the same PIN, so that the flexibility of PIN management can be improved.

Drawings

Fig. 1 is a schematic structural diagram of a communication system to which the embodiment of the present application can be applied;

fig. 2 is a flowchart of a PIN management method provided in an embodiment of the present application;

FIG. 3 is a schematic diagram of the architecture of a PIN in an embodiment of the application;

fig. 4 is a flowchart of another PIN management method provided in an embodiment of the present application;

FIG. 5 is one of the flowcharts of the newly added PIN manager in an embodiment of the present application;

FIG. 6 is a second flowchart of a newly added PIN manager in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a PIN management device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of another PIN management device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 10 is a schematic hardware structure of a terminal according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally intended to be used in a generic sense and not to limit the number of objects, for example, the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access) OFDMA), single-carrier frequency division multiple access (SC-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. Note that, the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include a base station, a WLAN access point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiments of the present application, only a base station in an NR system is described as an example, and the specific type of the base station is not limited.

The PIN management method, the PIN management device, the terminal and the network side device provided by the embodiment of the application are described in detail below through some embodiments and application scenes thereof with reference to the accompanying drawings.

Referring to fig. 2, the PIN management method provided in the embodiment of the present application may be executed by a first terminal. As shown in fig. 2, the PIN management method performed by the first terminal may include the steps of:

step 201, a first terminal sends first information to a first device, wherein the first information comprises a PIN identifier and identification information of at least one second terminal;

wherein the first information may have at least one of the following effects:

1) An administrator for requesting to configure the at least one second terminal as a PIN corresponding to the PIN identifier;

2) A PIN manager for determining whether to configure the at least one second terminal as a PIN identifier;

3) For the first device to determine whether to configure the at least one second terminal as a PIN administrator for the PIN corresponding to the PIN identifier, such that the first device may determine whether to configure the at least one second terminal as an administrator for the PIN corresponding to the PIN identifier based on the first information.

Wherein the PIN identifier is used to identify the PIN, for example: the PIN identifier may include at least one of identification information such as a PIN ID, a PIN name, PIN description information, and the like.

In the related art, PIN is a network based on and composed and derived from a number of increasing consumer internet of things devices. These devices may be either wearable devices (i.e., devices on a person such as cameras, headphones, watches, headphones, health monitors, etc.) or internet of things devices in the home (e.g., smart lights, cameras, thermostats, door sensors, voice assistants, speakers, refrigerators, washing machines, etc.). Users use these personal internet of things devices primarily at home or around the body to create a personal internet of things network.

Generally, PIN is commonly used in home, office, and like settings. The Internet of things devices deployed in the scenes can realize interconnection, communicate with each other and acquire services, so that the Internet of things devices are called personal networking. Meanwhile, the internet of things device in the PIN can access a communication network (such as a 5G system (5 GS)) through the device with a gateway function in the PIN by a certain mechanism and an implementation mode, access other servers of the network or complete the service.

As shown in fig. 3, all the enabling network elements (enabling) in the PIN framework in the related art are called an enabling layer, which can be regarded as a design of an application layer, and are located on an Operating System (OS), for example: a client or an APP; alternatively, the enabler may be a capability of the operating system OS, as part of the operating system, to provide services; alternatively, the enabler may be considered a chip capability, located on the modem chip module.

As shown in fig. 3, the PIN framework in the embodiment of the present application generally includes the following PIN network elements (PINs):

PIN network element (PIN Element with Management Capability, PEMC) with management function: the entire PIN may be managed, for example, one PIN is added to the PIN managed by the PEMC;

PIN network element (PIN element with Gateway capability, PEGC) with gateway function: responsible for routing the traffic of the PINs to the destination, e.g., one PIN is to communicate with other PINs in the PIN, then routing can be done by PEGC;

the above described functions of PEMC or PEGC may also be PIN application client (PIN client) on PEMC or PIN client on PEGC.

PIN server (server): for authorizing the establishment of a PIN or for authorizing the updating of a PIN, e.g., modifying the name of a PIN or adding a new member to a PIN. Typically PEMC triggers a PIN setup request and then the PIN server verifies that this setup request is passed. Meanwhile, the PIN server can also be used for PINE to request to search for a PIN, or searching for PEMC corresponding to the PIN, and the like. Another name for PIN server may be called PIN management function (PIN Management Function, PIN MF) entity.

The enable layers shown in the figures, such as the PEMC enable layer, may be considered as one client of the PEMC, such as a PIN client or PEMC client.

The first terminal may be a terminal corresponding to an administrator with an existing PIN, for example: the administrator of the PIN formed by the devices in a certain room may be a homeowner, and in this case, the first terminal may be a terminal device such as a mobile phone, a watch, an AR, or a VR of the homeowner, or a terminal associated with the identity information of the homeowner.

The first device may be a PIN network element or a PIN server (server) with a management function, and for convenience of explanation, in the following embodiments of the present application, the first device is exemplified by the PIN server.

Optionally, the first terminal is an administrator of the PIN corresponding to the PIN identifier, for example: the first device receives first information sent by the first terminal, wherein the first information comprises at least one second terminal, the at least one second terminal requests to become an administrator of the PIN corresponding to the PIN identifier, the first device can configure the second terminal as the administrator of the PIN corresponding to the PIN identifier, or the first device can perform identity verification on the second terminal and configure the authenticated second terminal as the administrator of the PIN corresponding to the PIN identifier.

The process of the first device performing identity verification on the second terminal may be that the identification information of the second terminal is matched with a trusted member list, if the identification information of the second terminal is found in the trusted member list, it may be determined that the second terminal passes the identity verification, in implementation, the trusted member list may include trusted member information of a PIN corresponding to a PIN identifier, or the trusted member list may include information of an administrator who has completed registration, for example: in the case where the second terminal performs administrator registration of the PIN corresponding to the PIN identifier, the trusted member list has identification information of the second terminal. For example, a group of second terminals may each be registered with the first device using their respective terminal identity (user permanent identifier (SUbs cription Permanent Identifier, SUPI), general public user identity (Generic Public Subscription Identifier, GPSI), etc.) or PIN client ID, which may then be set by the first device as a trusted member of a PIN. When a first terminal requests that at least one second terminal be set as an administrator of the PIN, the first device needs to verify the trusted identities of the second terminals. The list of trusted identities may also be stored in a unified data format repository (Unified Data Repository, UDR), with the first device carrying at least one second terminal identifier to verify the trusted identity in the UDR.

For example: trusted members of the first PIN and the second PIN stored in the UDR are shown in table 1 below:

in table 1 above, the PIN identifier of the first PIN is local.abc.pin, the PIN identifier of the second PIN is aaa.pin, and the trusted members of the PINs corresponding to local.abc.pin include terminal 1, terminal 2, and terminal 3; the trusted members of the PINs corresponding to the aaa.pin include terminal 1, terminal 3 and terminal 5.

It should be noted that, the trusted members, the administrator identities, the PIN administrator, and the like mentioned in the embodiments of the present application refer to the trusted members, the administrator identities, and the PIN administrator of the PIN corresponding to the PIN identifier carried in the first information, and the trusted members, the administrator identities, and the PIN administrator of other PINs are not in the scope of consideration of the present application.

That is, the trusted member in the first member list mentioned in the following embodiments of the present application may specifically be a trusted member in the trusted member list corresponding to the PIN identifier carried in the first information, or the first member list specifically refers to a trusted member list corresponding to the PIN identifier carried in the first information; similarly, the member having the administrator identity in the second member list mentioned in the embodiment of the present application may specifically be a member having the administrator identity having the PIN corresponding to the PIN identifier carried in the first information in the administrator identity list, or the second member list specifically refers to a member list having the administrator identity having the PIN corresponding to the PIN identifier carried in the first information.

In this embodiment, an existing PEMC (i.e., a first terminal) of a PIN stores a PIN identifier of the PIN in advance, and when a new PEMC (i.e., a second terminal) needs to be added to the PIN, the existing PEMC may send first information to a PIN server (i.e., a first device) to carry the PIN identifier and identification information of the new PEMC that needs to be added in the first information, so that the first device may determine whether to configure the second terminal as an administrator of the PIN corresponding to the PIN identifier.

As an optional embodiment, the identification information of the at least one second terminal includes at least one of:

the device identity of the at least one second terminal, for example: the identification information of the at least one second terminal comprises a general public user identity (Generic Public Subscription Identifier, GPSI) of each PEMC to be added; or other identifier of the terminal, such as a PIN client identifier (PIN client ID) installed on the terminal.

At least one device group identifier, where the device group identifier is used to indicate a trusted member group where the at least one second terminal is located, and a terminal in the trusted member group is a terminal with a trusted identity, for example: the identification information of the at least one second terminal includes a trust membership group ID (trust member group ID), and the PEMC that needs to be added is located in trust member group identified by trust member group ID. For example, all staff terminals in an office constitute a trusted group of members, and then the staff terminals are considered as trusted members of the corporate PIN. The benefit of setting up the trusted membership group is that terminals can be categorized into different trusted membership groups without putting all terminals into one large trusted membership group for ease of management. The members in the different trusted member groups can be authorized to become administrators of the different PINs, thereby enabling differentiated management of the members in the different trusted member groups.

In a possible implementation manner, the first device can distinguish each second terminal according to the device identifier of the at least one second terminal, so that each second terminal can be identified and/or verified based on the device identifier to determine whether to configure each second terminal as PEMC.

In one possible implementation manner, the first device is capable of distinguishing the device group where the at least one second terminal is located according to the device group identifier of the at least one second terminal, so that all second terminals in the group can be identified and/or verified based on the device group identifier to determine whether to configure all second terminals in the device group as PEMCs.

As an alternative embodiment, the first information is carried in a PIN creation request message or a PIN update request message.

In this embodiment, the first information may be transmitted using a PIN create request message or a PIN update request message in the related art, that is, an identifier of at least one second terminal may be carried at the time of PIN creation or PIN update to request setting them as a PIN administrator.

As an optional embodiment, the PIN management method further includes:

The first terminal receives a first response from the first device, wherein the first response comprises a configuration result of an administrator of the PIN of the at least one second terminal, the configuration result indicates that a third terminal is configured as the administrator of the PIN corresponding to the PIN identification, and/or the configuration result indicates that a fourth terminal is not configured as the administrator of the PIN corresponding to the PIN identification, the third terminal comprises all or part of the at least one second terminal, or the fourth terminal comprises all or part of the at least one second terminal;

and the first terminal respectively determines whether the at least one second terminal is an administrator of the PIN corresponding to the PIN identification according to the first response.

The first response may be a response to the first information, or a response to a PIN create request message or a PIN update request message carrying the first information. The configuration result in the first response may instruct the first device which part of the at least one second terminal is configured as an administrator of the PIN, such as: the configuration information includes identification information of an administrator of the at least one second terminal that is determined to be configured as the target PIN, or which part of the at least one second terminal is not configured as an administrator of the PIN, such as: the configuration information includes identification information of an administrator of the at least one second terminal that is determined not to be configured as the target PIN, or which part of the at least one second terminal is configured as the administrator of the PIN, and the other part is not configured as a configuration result of the administrator of the PIN, such as: the configuration information includes first identification information of the at least one second terminal, which is determined to be configured as an administrator of the target PIN, and indication information of the second terminals corresponding to the first identification information, which is configured as an administrator of the target PIN, and the configuration information further includes second identification information of the at least one second terminal, which is determined to be not configured as an administrator of the target PIN, and indication information of the second terminals corresponding to the second identification information, which is not configured as an administrator of the target PIN.

In this embodiment, the first terminal may further receive a configuration result of the PIN administrator of the at least one second terminal from the first device, and determine, based on the configuration result, which second terminals are configured as the PIN administrator, and which second terminals are not configured as the PIN administrator. For example: if a part of the second terminals are configured as administrators of the PIN, the first device gives the second terminal identification of the part and indicates that the second terminals are configured as administrators; if a portion of the second terminals are not configured as administrators of the PIN, the first device gives an identification of the second terminals of the portion and indicates that these second terminals are not configured as administrators.

Wherein, for an administrator of the at least one second terminal that is not configured to be a PIN, the first response may further include a reason why the second terminal is not configured to be an administrator of the PIN, for example: failing authentication (e.g., the terminal does not qualify as an administrator), or the number of administrators of the PIN reaching an upper limit, etc. At this time, the reason may be output at the first terminal, wherein there are various ways in which the first terminal outputs the reason, for example: the text content and/or the icon of the cause is displayed through the display screen, or the audio of the cause is output through the speaker.

As an optional implementation manner, in a case where the configuration result indicates that the fourth terminal is not configured as a PIN administrator corresponding to the PIN identifier, the method further includes:

the first terminal outputs indication information for indicating that the fourth terminal fails to be configured as a cause of a PIN administrator corresponding to the PIN identifier.

In this embodiment, when the first terminal requests the first device to configure at least one second terminal as the PIN manager corresponding to the PIN identifier, the first terminal may output, for a fourth terminal that is not successfully configured as the PIN manager corresponding to the PIN identifier, instruction information to instruct the fourth terminal that is not configured as the PIN manager corresponding to the PIN identifier. Thus, the user can make corresponding adjustments according to the indication information, for example: the indication information indicates that the fourth terminal is not configured as the PIN administrator corresponding to the PIN identifier, because the fourth terminal does not belong to the trusted member list, at this time, the user may first perform trusted member-related registration on the fourth terminal to add identification information of the fourth terminal in the trusted member list, and then send first information related to the fourth terminal (that is, the first information may include identification information of the four terminals of the PIN identifier Fu Kedi) to the first device by using the first terminal, so that the first device adds the fourth terminal as the PIN administrator corresponding to the PIN identifier according to the first information.

In addition, for the second terminal that has been successfully configured as the PIN administrator corresponding to the PIN identifier, the target configuration information of the PIN corresponding to the PIN identifier may be sent to the second terminal, so that the second terminal can participate in the management of the PIN corresponding to the PIN identifier.

As an optional implementation manner, in a case where the configuration result indicates that the third terminal is configured as an administrator of the PIN corresponding to the PIN identifier, the method further includes:

the first terminal sends target configuration information to the third terminal, wherein the target configuration information comprises at least one of the following items:

the PIN identifier;

description information of the PIN corresponding to the PIN identifier;

user member information in the PIN corresponding to the PIN identifier;

configuration information of the PIN corresponding to the PIN identifier;

and service information provided by the PIN corresponding to the PIN identifier.

The configuration information of the PIN corresponding to the PIN identifier may include a basic configuration of the PIN, such as a PIN ID, a name of the PIN, a service (such as a print service, a smart screen, a projection, etc.) that the PIN can provide, member information in the PIN (such as all PIN IDs in the PIN, an IP address of the PIN, etc.), a PEGC ID or a PEGC IP address in the PIN, etc. Since the second terminal becomes an administrator of the PIN, the configuration of the associated PIN must also be updated to this administrator.

In this embodiment, the first terminal transmits the target configuration information to the newly added PEMC, so that the complexity of the newly added PEMC to acquire the target configuration information can be reduced.

Of course, in the implementation, the target configuration information may also be sent to the newly added PEMC through a PIN with a gateway function or a wireless communication function in the PIN, which is not limited herein.

Referring to fig. 4, another PIN management method provided in the embodiment of the present application corresponds to the PIN management method provided in the embodiment of the method shown in fig. 2, where an execution subject of the PIN management method provided in the embodiment of the method shown in fig. 2 is a first terminal, and an execution subject of the PIN management method provided in the embodiment of the method shown in fig. 4 is a first device, and a procedure of the PIN management method executed by the first device in the embodiment of the present application may refer to a procedure of the PIN management method executed by the first terminal in the embodiment of the method shown in fig. 2.

As shown in fig. 4, the PIN management method performed by the first device may include the steps of:

step 401, a first device obtains first information from a first terminal, where the first information includes a PIN identifier and identification information of at least one second terminal, where the first information is used to request that the at least one second terminal be configured as an administrator of a PIN corresponding to the PIN identifier.

Step 402, the first device determines whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier according to the first information.

The meaning and the effect of the first information, the first terminal, the second terminal, the first device, and the PIN are the same as those of the first information, the first terminal, the second terminal, the first device, and the PIN in the embodiment of the method shown in fig. 2, and are not described herein.

In this embodiment of the present invention, the first device may determine, according to first information from the first terminal, whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier, so that multiple administrators may be configured for one PIN, so that multiple administrators may jointly implement management of one PIN, and flexibility of PIN management is improved.

As an optional implementation manner, the first terminal is an administrator of the PIN corresponding to the PIN identifier.

a device identification of the at least one second terminal;

and the equipment group identifier is used for indicating a trusted member group where the at least one second terminal is located, and the terminals in the trusted member group are terminals with trusted identities.

The first information includes at least one second terminal that requests to be an administrator of the PIN corresponding to the PIN identifier, and in the step 402, the first device may directly configure the second terminal included in the first information as an administrator of the PIN corresponding to the PIN identifier, or may authenticate the second terminal included in the first information, and configure the authenticated second terminal as an administrator of the PIN corresponding to the PIN identifier, and may not configure the second terminal that does not pass authentication as an administrator of the PIN corresponding to the PIN identifier.

As an optional implementation manner, the first device determines whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier according to the first information, including:

the first equipment performs identity verification on the at least one second terminal according to the first information;

in the case that the third terminal passes the authentication, the first device determines to configure the third terminal as an administrator of the PIN corresponding to the PIN identifier, and/or in the case that the fourth terminal does not pass the authentication, the first device determines not to configure the fourth terminal as an administrator of the PIN corresponding to the PIN identifier, wherein the at least one second terminal includes the third terminal and/or the fourth terminal.

The authentication of the at least one second terminal may be to verify whether the at least one second terminal is a trusted terminal, and/or to verify whether the at least one second terminal has a management authority of a PIN corresponding to a PIN identifier, or the like. In this embodiment of the present application, the third terminal that is the at least one second terminal and passes authentication, and the fourth terminal that is the at least one second terminal and does not pass authentication.

In this way, when the third terminal in the at least one second terminal passes the authentication, the third terminal can be configured as the PEMC, and when the fourth terminal in the at least one second terminal does not pass the authentication, the fourth terminal is not configured as the PEMC, so that the probability of configuring the untrusted terminal as the PEMC can be reduced, and the security performance of the PIN is improved.

Optionally, the first device performs identity verification on the at least one second terminal according to the first information, including:

the first device searches the identification information of the at least one second terminal in a pre-stored first member list and/or second member list;

the first device determining that the third terminal is configured as an administrator of the PIN corresponding to the PIN identifier in the case that the third terminal passes the authentication, and/or the first device determining that the fourth terminal is not configured as an administrator of the PIN corresponding to the PIN identifier in the case that the fourth terminal does not pass the authentication, including:

the first device determines that the third terminal passes the identity verification when the identification information of the third terminal is found in the first member list and/or the second member list, and/or determines that the fourth terminal fails the identity verification when the identification information of the fourth terminal is not found in the first member list and/or the second member list;

Wherein the first member list includes identification information of trusted members and the second member list includes identification information of members having administrator identities.

In an implementation, the first member list includes identification information of the trusted member, so that if identification information of the third terminal is found in the first member list, it can be determined that the third terminal belongs to the trusted member, and complexity of verifying the trusted member is reduced.

The second member list includes the identification information of the member having the administrator identity, so that if the identification information of the third terminal is found in the second member list, it can be determined that the third terminal has been registered as the administrator identity of the PIN, and the complexity of verifying the terminal having the administrator identity is reduced.

It should be noted that, in implementation, the first member list and/or the second member list may be stored in advance in the first device, but may also be stored in other network side devices in the communication network, such as: it is assumed that the first device is a PIN server and the first and/or second member lists are stored in a unified data format repository (Unified Data Repository, UDR) or a unified data management entity (Unified Data Management, UDM). At this time, the first device may search the first member list and/or the second member list for the identification information of the at least one second terminal through other network side devices in the communication network, which is not limited herein.

As an optional implementation manner, the PIN management method provided in the embodiment of the present application further includes: the method further comprises the steps of:

the first device searches the identification information of the at least one second terminal according to the PIN identifier in a third prestored member list, wherein the third member list comprises the identification information of the terminal of the administrator which is configured to be the PIN corresponding to the PIN identifier;

and under the condition that the identification information of a fifth terminal is found in the third member list, the first equipment screens out terminals except the fifth terminal in the at least one second terminal, wherein the terminals except the fifth terminal in the at least one second terminal comprise the third terminal and/or the fourth terminal.

The third member list stores the terminal identifiers of the administrators configured to be the PINs corresponding to the PIN identifiers carried in the first information, and the terminal identifiers of the administrators configured to be the target PINs in the history period may be stored in the third member list.

For example: assuming that the third member list stores the correspondence between the identifiers of the target PINs and the terminals 1 and 2, respectively, when the first terminal (or the terminal 2) sends first information to the first device, for example, the first terminal sends a PIN update request (including a PIN ID) in which, if the identifier information of the terminal 1 and the terminal 3 is carried and both terminals are requested to be configured as administrators, the first device searches the third member list for the identifier information of the terminal 1 and the identifier information of the terminal 3, and based on the identifier information of the terminal 1 associated with the PIN identifier found in the third member list, this means that the terminal 1 is already configured as an administrator of the PIN, identity verification is not performed on the terminal 1 and the subsequent operation related to configuring the PIN administrator, but only the terminal 3 is performed for the terminal 1, so that the terminal 1 does not need to be reconfigured as an administrator. If the terminal 3 passes the authentication, determining to configure the terminal 3 as an administrator of the target PIN; if the terminal 3 fails the authentication, it is determined that the terminal 3 is not configured as an administrator of the target PIN.

In this way, for the fifth terminal that has been configured as the manager identity of the target PIN, repeated authentication and manager identity configuration thereof can be avoided.

As an optional embodiment, the PIN management method further includes:

the first device stores identification information of a terminal configured as an administrator of the PIN corresponding to the PIN identifier in association with the PIN identifier in a third member list.

Wherein the third member list may be stored in the first device, and possibly in other devices in the communication network, for example: UDR, etc., are not particularly limited herein.

In an implementation, the first device may update the third member list, where each time a terminal is determined to be configured as an administrator of the PIN corresponding to the PIN identifier, so that the updated third member list includes an association relationship between the PIN identifier and all administrators of the target PIN (i.e., PINs corresponding to the PIN identifier). In this way, the first device can synchronously update the terminal of the administrator that has been configured as the target PIN.

For example: when the first terminal transmits the first information to the first device, the first device carries the identification information of the terminal 1 and the terminal 2, and if the first device determines, based on the first information, the identity of the administrator configuring both the terminal 1 and the terminal 2 as the target PIN (i.e., the PIN corresponding to the PIN identifier), the terminal 1 and the terminal 2 are respectively associated with the PIN identifier and stored in the third member list.

As an optional implementation manner, after the first device performs authentication on the at least one second terminal according to the first information, the method further includes:

the first device sends a first response to the first terminal, where the first response includes a configuration result of an administrator of the PIN of the at least one second terminal, the configuration result indicates that a third terminal is configured as the administrator of the PIN corresponding to the PIN identification, and/or the configuration result indicates that a fourth terminal is not configured as the administrator of the PIN corresponding to the PIN identification, and the third terminal includes all or part of the at least one second terminal, or the fourth terminal includes all or part of the at least one second terminal.

In an implementation, the configuration result of the administrator of the PIN of the at least one second terminal may indicate which second terminals are configured as the administrator of the PIN, and/or indicate which second terminals are not configured as the administrator of the PIN.

Further, for the second terminals that are not configured as administrators of the PIN, the reasons why these second terminals are not configured as administrators of the PIN may also be indicated in the configuration result of the administrators of the PIN of the at least one second terminal, for example: the fourth terminal does not belong to a trusted member and/or the fourth terminal does not have an administrator identity for the PIN described above, etc.

The effect of the first terminal in acquiring the first response is the same as that of the embodiment of the method shown in fig. 2, and will not be described herein.

As an alternative embodiment, in case the first response indicates that the third terminal passes the authentication, the method further comprises:

the first device transmits target configuration information to at least one of the first terminal and the third terminal, the target configuration information including at least one of:

the PIN identifier;

description information of the PIN corresponding to the PIN identifier;

user member information in the PIN corresponding to the PIN identifier;

configuration information of the PIN corresponding to the PIN identifier;

In this embodiment, similar to the effect of the first terminal sending the target configuration information to the third terminal in the embodiment of the method shown in fig. 2, the difference includes that in this embodiment, the first device may send the target configuration information to the third terminal, or the first device may send the target configuration information to the first terminal first, and then the first terminal forwards the target configuration information to the third terminal, so that the third terminal can implement a PIN management function according to the target configuration information after obtaining the target configuration information, which is not described herein again.

In order to facilitate the explanation of the PIN management method provided in the embodiment of the present application, the PIN management method provided in the embodiment of the present application is exemplified by the following application scenario:

scene one

As shown in fig. 5, assuming that the first terminal is a PEMC of a target PIN, the first device is a PIN server of the target PIN, and the second terminal is a new (additional) PEMCs. The PIN management method provided by the embodiment of the application may include the following steps:

step 1, the PEMC sends a PIN creation request message to the first device, wherein the PIN creation request message carries identification information of a target PIN and identification information of Additional PEMCs, and the identification information of the Additional PEMCs is an administrator who wants to request to configure a terminal corresponding to the identification information as the PIN.

Step 2, the PIN server verifies whether the additional PEMCs belong to trusted members.

The PIN server may check, when receiving additional PEMC GPSI (or PIN client ID), with UDR (or other network side device in 5 GS) whether the PEMC determined according to additional PEMC GPSI is included in the trusted member, and if additional PEMC GPSI corresponds to PEMC included in the trusted member, determine that the additional PEMC passes the verification.

And step 3, the PIN server sends a PIN create response message to the PEMC.

If the trusted member is verified, the additional PEMC also obtains the administrator identity of the target PIN, and if the trusted member is verified, the reason related to the verification failure can be displayed on a display screen of the PEMC.

In this embodiment, the identification information of the additional PEMCs may be the ID of each additional PEMC, such as GPSI. Alternatively, the identification information of the additional PEMCs may be a group identification of all the additional PEMCs, such as trust member group ID.

If some of the additional PEMC's pass verification, become administrators, the PIN server may indicate the GPSI or PIN client ID of these PEMC's to account for their administrator being PINs; while for failed, their identifiers may or may not be indicated, i.e., the failed PEMC is thrown away, leaving naturally the failed PEMC.

Scene two

As shown in fig. 6, assume that the first terminal is a PEMC of a target PIN, the first device is a PIN server of the target PIN, the second terminal is a newly added (additional) PEMCs, and the list of trusted members is stored in the UDR. The PIN management method provided by the embodiment of the application may include the following steps:

And step 1, inquiring PIN list information and/or PIN information.

Prior to this step, the additional PEMC may be registered as an administrator identity of the target PIN, so that the PIN list information and/or the PIN information obtained by the query in this step may include the additional PEMC.

Step 2, a PIN update request message triggered by the PEMC, where the PIN update request message carries identification information of the additional PEMC and identification information of the target PIN, for example: PIN ID, PIN name, PIN description information, PIN service information, time information, etc.

And step 3, inquiring the trusted member by the PIN server.

In this step, when the PIN server receives additional PEMC GPSIs, the PIN server first determines whether there is a newly added PEMC in the PIN list information and/or the PIN information, and if so, the PIN server checks with the UDR whether the newly added PEMC is included in the trusted members of the PEMCs identified by PEMC gps is, and other PEMCs that are not newly requested to be added (i.e., the PEMCs corresponding to the fifth terminal in the existing administrator identity list of the PIN) are ignored.

And 4, the PIN server sends a PIN updating response message to the PEMC.

According to the PIN management method provided by the embodiment of the application, the execution subject can be a PIN management device. In the embodiment of the present application, a PIN management device is described by taking a PIN management method performed by the PIN management device as an example.

Referring to fig. 7, a PIN management device provided in the embodiment of the present application may be a device in a first terminal, and as shown in fig. 7, the PIN management device 700 may include the following modules:

a first sending module 701, configured to send first information to a first device, where the first information includes a PIN identifier and identification information of at least one second terminal;

Optionally, the first terminal is an administrator of the PIN corresponding to the PIN identifier.

Optionally, the identification information of the at least one second terminal includes at least one of:

a device identification of the at least one second terminal;

Optionally, the first information is carried in a PIN creation request message or a PIN update request message.

Optionally, the PIN management device 700 further includes:

a first receiving module, configured to receive a first response from the first device, where the first response includes a configuration result of an administrator of a PIN of the at least one second terminal, the configuration result indicating that a third terminal is configured as the administrator of the PIN corresponding to the PIN identification, and/or the configuration result indicating that a fourth terminal is not configured as the administrator of the PIN corresponding to the PIN identification, the third terminal including all or part of the at least one second terminal, or the fourth terminal including all or part of the at least one second terminal;

And the first determining module is used for respectively determining whether the at least one second terminal is an administrator of the PIN corresponding to the PIN identification according to the first response.

Optionally, in the case where the configuration result indicates that the third terminal is configured as an administrator of the PIN corresponding to the PIN identification, the PIN management apparatus 700 further includes:

the PIN identifier;

description information of the PIN corresponding to the PIN identifier;

user member information in the PIN corresponding to the PIN identifier;

configuration information of the PIN corresponding to the PIN identifier;

Optionally, in a case where the configuration result indicates that the fourth terminal is not configured as the PIN manager corresponding to the PIN identifier, the PIN management apparatus 700 further includes:

and the output module is used for outputting indication information, wherein the indication information is used for indicating that the fourth terminal cannot be configured as a reason of a PIN manager corresponding to the PIN identifier.

The PIN management device 700 provided in this embodiment of the present application can implement each process of the method embodiment shown in fig. 2, and can obtain the same beneficial effects, so that repetition is avoided, and no further description is given here.

Referring to fig. 8, another PIN management apparatus provided in the embodiment of the present application may be an apparatus in a first device, and as shown in fig. 8, the PIN management apparatus 800 may include the following modules:

an obtaining module 801, configured to obtain first information from a first terminal, where the first information includes a PIN identifier and identification information of at least one second terminal, where the first information is used to request that the at least one second terminal be configured as an administrator of a PIN corresponding to the PIN identifier;

a second determining module 802, configured to determine, according to the first information, whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier.

a device identification of the at least one second terminal;

Optionally, the second determining module 802 includes:

the authentication unit is used for carrying out identity authentication on the at least one second terminal according to the first information;

a determining unit, configured to determine that the third terminal is configured as an administrator of the PIN corresponding to the PIN identifier if the third terminal passes the authentication, and/or determine that the fourth terminal is not configured as an administrator of the PIN corresponding to the PIN identifier if the fourth terminal does not pass the authentication, where the at least one second terminal includes the third terminal and/or the fourth terminal.

Optionally, the verification unit is specifically configured to search for identification information of the at least one second terminal in a pre-stored first member list and/or a second member list, where the first member list includes identification information of trusted members, and the second member list includes identification information of members with administrator identities;

the determining unit is specifically configured to determine that, when identification information of the third terminal is found in the first member list and/or the second member list, the third terminal passes the authentication, and/or determine that, when identification information of the fourth terminal is not found in the first member list and/or the second member list, the fourth terminal fails the authentication.

Optionally, the PIN management device 800 further includes:

a searching module, configured to search, in a third pre-stored member list, identification information of the at least one second terminal according to the PIN identifier, where the third member list includes identification information of terminals of an administrator that have been configured to be a PIN corresponding to the PIN identifier;

and the screening module is used for screening out terminals except the fifth terminal in the at least one second terminal under the condition that the identification information of the fifth terminal is found in the third member list, wherein the terminals except the fifth terminal in the at least one second terminal comprise the third terminal and/or the fourth terminal.

Optionally, the PIN management device 800 further includes:

and a storage module, configured to store identification information of a terminal configured as an administrator of the PIN corresponding to the PIN identifier in association with the PIN identifier in a third member list.

Optionally, the PIN management device 800 further includes:

and a third sending module, configured to send a first response to the first terminal, where the first response includes a configuration result of an administrator of the PIN of the at least one second terminal, the configuration result indicates that a third terminal is configured as the administrator of the PIN corresponding to the PIN identifier, and/or the configuration result indicates that a fourth terminal is not configured as the administrator of the PIN corresponding to the PIN identifier, and the third terminal includes all or part of the at least one second terminal, or the fourth terminal includes all or part of the at least one second terminal.

Optionally, in the case that the first response indicates that the third terminal passes the authentication, the PIN management device 800 further includes:

a fourth transmitting module, configured to transmit target configuration information to at least one of the first terminal and the third terminal, where the target configuration information includes at least one of:

the PIN identifier;

description information of the PIN corresponding to the PIN identifier;

user member information in the PIN corresponding to the PIN identifier;

configuration information of the PIN corresponding to the PIN identifier;

The PIN management device 800 provided in the embodiment of the present application can implement each process of the method embodiment shown in fig. 4, and can obtain the same beneficial effects, so that repetition is avoided, and no further description is provided herein.

The PIN management device in the embodiment of the application may be an electronic device, for example, an electronic device with an operating system, or may be a component in an electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

The PIN management device provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in fig. 2 or fig. 4, and achieve the same technical effects, so that repetition is avoided, and no further description is given here.

Optionally, as shown in fig. 9, the embodiment of the present application further provides an electronic device 900, including a processor 901 and a memory 902, where the memory 902 stores a program or instructions that can be executed on the processor 901, for example, when the electronic device 900 is used as the first terminal, the program or instructions implement, when executed by the processor 901, the steps in the method embodiment shown in fig. 2, and achieve the same technical effects. When the electronic device 900 is used as the first device, the program or the instructions when executed by the processor 901 implement the steps of the method embodiment shown in fig. 4, and achieve the same technical effects, and for avoiding repetition, a detailed description is omitted herein.

The embodiment of the application also provides a first terminal, which comprises a processor and a communication interface, wherein the communication interface is used for sending first information to first equipment, and the first information comprises a PIN identifier and identification information of at least one second terminal; the first information is used for requesting to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier.

The first terminal embodiment corresponds to the method embodiment on the first terminal side, and each implementation process and implementation manner of the method embodiment are applicable to the first terminal embodiment, and the same technical effects can be achieved. Specifically, fig. 10 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present application.

The terminal 1000 includes, but is not limited to: at least some of the components of the radio frequency unit 1001, the network module 1002, the audio output unit 1003, the input unit 1004, the sensor 1005, the display unit 1006, the user input unit 1007, the interface unit 1008, the memory 1009, and the processor 1010, etc.

Those skilled in the art will appreciate that terminal 1000 can also include a power source (e.g., a battery) for powering the various components, which can be logically connected to processor 1010 by a power management system so as to perform functions such as managing charge, discharge, and power consumption by the power management system. The terminal structure shown in fig. 10 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine some components, or may be arranged in different components, which will not be described in detail herein.

It should be understood that in the embodiment of the present application, the input unit 1004 may include a graphics processing unit (Graphics Processing Unit, GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes at least one of a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 can include two portions, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In this embodiment, after receiving downlink data from the network side device, the radio frequency unit 1001 may transmit the downlink data to the processor 1010 for processing; in addition, the radio frequency unit 1001 may send uplink data to the network side device. In general, the radio frequency unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 1009 may be used to store software programs or instructions and various data. The memory 1009 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 1009 may include volatile memory or nonvolatile memory, or the memory 1009 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 1009 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, and the like, and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 1010.

Wherein the radio frequency unit 1001 or the network module 1002 is configured to send first information to a first device, where the first information includes a PIN identifier and identification information of at least one second terminal;

Optionally, the terminal is an administrator of the PIN corresponding to the PIN identifier.

a device identification of the at least one second terminal;

Optionally, the radio frequency unit 1001 or the network module 1002 is further configured to receive a first response from the first device, where the first response includes a configuration result of an administrator of the PIN of the at least one second terminal, the configuration result indicates that a third terminal is configured as an administrator of the PIN corresponding to the PIN identification, and/or the configuration result indicates that a fourth terminal is not configured as an administrator of the PIN corresponding to the PIN identification, the third terminal includes all or part of the at least one second terminal, or the fourth terminal includes all or part of the at least one second terminal;

and a processor 1010, configured to determine, according to the first response, whether the at least one second terminal is an administrator of the PIN corresponding to the PIN identifier.

Optionally, in the case that the configuration result indicates that the third terminal is configured as an administrator of the PIN corresponding to the PIN identifier, the radio frequency unit 1001 or the network module 1002 is further configured to send target configuration information to the third terminal, where the target configuration information includes at least one of the following:

The PIN identifier;

description information of the PIN corresponding to the PIN identifier;

user member information in the PIN corresponding to the PIN identifier;

configuration information of the PIN corresponding to the PIN identifier;

Optionally, in a case where the configuration result indicates that the fourth terminal is not configured as the PIN manager corresponding to the PIN identifier, at least one of the audio output unit 1003 and the display unit 1006 is further configured to output indication information for indicating a reason why the fourth terminal cannot be configured as the PIN manager corresponding to the PIN identifier.

The above terminal 1000 can implement the process implemented by each model in the PIN management device 700 shown in fig. 7, and can achieve the same technical effects, and for avoiding repetition, a detailed description is omitted herein.

The embodiment of the application also provides first equipment, which comprises a processor and a communication interface, wherein the communication interface is used for acquiring first information from a first terminal, the first information comprises a PIN identifier and identification information of at least one second terminal, and the first information is used for requesting to configure the at least one second terminal as an administrator of a PIN corresponding to the PIN identifier; the processor is used for determining whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier according to the first information.

The first device embodiment corresponds to the method embodiment shown in fig. 4, and each implementation procedure and implementation manner of the method embodiment shown in fig. 4 are applicable to the first device embodiment, and the same technical effects can be achieved.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the program or the instruction implement each process of the method embodiment shown in fig. 2 or fig. 4, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, to implement each process of the method embodiment shown in fig. 2 or fig. 4, and to achieve the same technical effect, so that repetition is avoided, and no further description is given here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product, which is stored in a storage medium, and executed by at least one processor to implement the respective processes of the method embodiments shown in fig. 2 or fig. 4, and achieve the same technical effects, and are not repeated herein.

The embodiment of the application also provides a communication system, which comprises: the PIN management system comprises a first terminal and a first device, wherein the first terminal can be used for executing the steps of the PIN management method shown in fig. 2, and the first device can be used for executing the steps of the PIN management method shown in fig. 4.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. The personal internet of things network PIN management method is characterized by comprising the following steps of:

2. The method of claim 1, wherein the first terminal is an administrator of a PIN corresponding to the PIN identifier.

3. The method of claim 1, wherein the identification information of the at least one second terminal comprises at least one of:

a device identification of the at least one second terminal;

4. The method of claim 1, wherein the first information is carried in a PIN creation request message or a PIN update request message.

5. The method according to any one of claims 1 to 4, further comprising:

6. The method according to claim 5, wherein in case the configuration result indicates that the third terminal is configured as an administrator of the PIN to which the PIN identification corresponds, the method further comprises:

the PIN identifier;

description information of the PIN corresponding to the PIN identifier;

User member information in the PIN corresponding to the PIN identifier;

configuration information of the PIN corresponding to the PIN identifier;

7. The method according to claim 5, wherein in case the configuration result indicates that the fourth terminal is not configured as a PIN administrator corresponding to the PIN identifier, the method further comprises:

8. The personal internet of things network PIN management method is characterized by comprising the following steps of:

9. The method of claim 8, wherein the first terminal is an administrator of a PIN corresponding to the PIN identifier.

10. The method of claim 8, wherein the identification information of the at least one second terminal comprises at least one of:

a device identification of the at least one second terminal;

11. The method of claim 8, wherein the first information is carried in a PIN creation request message or a PIN update request message.

12. A method according to any of claims 8 to 11, wherein the first device determining from the first information whether to configure the at least one second terminal as an administrator of the PIN corresponding to the PIN identifier comprises:

13. The method of claim 12, wherein the first device authenticating the at least one second terminal based on the first information comprises:

14. The method of claim 13, wherein the method further comprises:

15. The method according to any one of claims 8 to 14, further comprising:

16. The method of claim 12, wherein after the first device authenticates the at least one second terminal based on the first information, the method further comprises:

17. The method according to claim 16, wherein in case the first response indicates that the third terminal passes the authentication, the method further comprises:

The PIN identifier;

description information of the PIN corresponding to the PIN identifier;

user member information in the PIN corresponding to the PIN identifier;

18. A personal internet of things network PIN management device, applied to a first terminal, the device comprising:

19. The apparatus as recited in claim 18, further comprising:

20. The apparatus according to claim 19, wherein in case the configuration result indicates that the third terminal is configured as an administrator of the PIN to which the PIN identification corresponds, the apparatus further comprises:

the second sending module is configured to send target configuration information to the third terminal, where the target configuration information includes at least one of the following:

the PIN identifier;

description information of the PIN corresponding to the PIN identifier;

user member information in the PIN corresponding to the PIN identifier;

configuration information of the PIN corresponding to the PIN identifier;

21. The apparatus according to claim 19, wherein in case the configuration result indicates that the fourth terminal is not configured as a PIN administrator corresponding to the PIN identifier, the apparatus further comprises:

22. A personal internet of things network PIN management apparatus for use with a first device, the apparatus comprising:

23. The apparatus of claim 22, wherein the second determining module comprises:

24. The apparatus of claim 23, wherein the apparatus comprises;

the verification unit is specifically configured to:

searching identification information of the at least one second terminal in a pre-stored first member list and/or second member list;

the determining unit is specifically configured to:

25. The apparatus as recited in claim 24, further comprising:

26. The apparatus according to any one of claims 22 to 25, further comprising:

27. The apparatus as recited in claim 23, further comprising:

28. The apparatus of claim 27, wherein in the event that the first response indicates that the third terminal passes the authentication, the apparatus further comprises:

the PIN identifier;

description information of the PIN corresponding to the PIN identifier;

user member information in the PIN corresponding to the PIN identifier;

29. A first terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the personal internet of things PIN management method of any one of claims 1 to 7.

30. A first device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the personal internet of things PIN management method of any one of claims 8 to 17.

31. A readable storage medium, characterized in that the readable storage medium stores thereon a program or instructions, which when executed by a processor, implements the personal internet of things network PIN management determination method according to any one of claims 1 to 7, or the steps of the personal internet of things network PIN management method according to any one of claims 8 to 17.